-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
R14 RC1 is finally out the door!
http://trinity-announce.pearsoncomputing.net/?0::30
This means the merge window for R14 RC2 is now OPEN. Please commit any
outstanding patches at this time.
This merge window will close 11/26/2014 to allow for R14 RC2 build and
release. Please concentrate all efforts on the unresolved bugs blocking
Bug 2014.
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlRs7KYACgkQLaxZSoRZrGGu7wDdF1lrSVs0NGoOKtKLNy405IdG
ZQ2XaQsB554CiQDeIK3uREMA7R2KbHcsMgmlaWQTCS57Fml/IyMQRQ==
=X3nZ
-----END PGP SIGNATURE-----
You almost certainly don't need to read this.
I'm posting this here for the record in case someone
wants to check TDE for circular dependencies in future.
Bugs have been filed for all circular dependencies
found in a standard --with-recommendations TDE R14 RC1
Wheezy install.
(1) Why check for circular dependencies
Although apt and dpkg do their best to handle any circular
dependencies they encounter, circular dependencies can cause
problems and a generally discouraged.
(2) How to get rid of circular dependencies
Usually one finds the least important dependency in the circle
and changes it to a recommendation.
If you're dealing with a maze rather than a circle you may
to have convert several dependencies.
(3) tsort non-method
I first thought of using tsort on the dependencies listed
in Packages.gz. However versioned dependencies, provides,
conflicts, etc make this impractical.
(4) Recommended elegant automatic method
foreach PACKAGE in TRINITY {
start with a minimal (non-TDE) base system
install PACKAGE and all its dependencies
remove just PACKAGE
}
There should be no errors installing or removing.
However this method is somewhat time consuming even if
you arrange it to use snapshots in a chroot so you can
quickly revert to your minimal base system.
(5) Grungy manual method
Due to time constraints I used the following method for
TDE R14 RC1.
start with a non-TDE base system
let TARGET be a list of all installed packages
apt-get --install-recommends install desktop-base-trinity kde-trinity
while (true) {
let CURRENT be a list of all installed packages
let REMOVE be TARGET (join -v) CURRENT
let BUSY = false
do {
foreach PACKAGE in REMOVE {
Try to remove PACKAGE, if successful set BUSY = true
}
while (BUSY);
break if only TARGET packages are installed
manually figure out why no remaining package is removable
note and remove any set of co-dependent packages
}
This is overall a lot faster than the automatic method but
it requires more manual work. The first time the removals
stalled there were 76 packages still awaiting removal and
you then have to look through these to find the loops.
(6) Loops found in Wheezy TDE R14 RC1
(a) Bug #2194
kcontrol-trinity
konqueror-nsplugins-trinity
konqueror-trinity
konsole-trinitytdebase-trinity
ksmserver-trinity
tdebase-runtime-data-common-trinity
(b) Bug #2197
libkcal2b-trinity
libtdepim1a-trinity
(c) Pre-existing Debian Bug #626319
gnuift
gnuift-perl
Alexandre, E.,
would it be possible for you to create a slightly modified version of the KSplash default theme with "rounded" corners?
I would like to compare a "rounded square" and a "full" square and see which one looks better. I think a rounded
splashscreen may look a little better at login.
The file to modify are in tdebase/ksplashml/pics/themes/default, probably only splash_top.png and splash_bottom.png
Thanks
Michele
Tim, Slavek,
while working on bug 1850, I noticed that in tdebase/kcontrol there is an "accessibility" folder that is not used at all
(not even built). By the content of it, it is either an older version or a temporary development version of the "access"
folder, which is the KControl module for Regional & Accessibility --> Accessibility.
Removing the folder does not cause any build problem, but before doing that I thought I would ask in case any of you had
more information about it.
If there are no objections, I will proceed to remove it.
Cheers
Michele
Hi,
I made a new TDE logo, just to see what it could be, so I want to have your impressions on it.
I used as a base the aKregator icon from the KFaenza icon theme. I remove the logo in the middle and replaced it by TDE base logo, from the moon svg background. I used cooler blue color gradient than the original to replace the orange of the aKregator logo.
Tell me what you think! Thank you!
-Alexandre
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
After much consideration I have decided it would be safest to require our
developers to formalize their open-source contributions with a CLA.
The CLA on the main TDE site does not transfer copyright or do anything
objectionable like Canonical's old CLA did; it simply formalizes the
long-standing intuitive agreement between open-source contributors and
open-source projects. Specifically, contributors grant a license to use,
redistribute, modify, etc. the contributed work under our approved
open-source licenses (sadly this formalization is required even though
most people would think contributing to an open source project
automatically granted those rights!), waive any patent rights they may
otherwise hold for the contribution (some people contribute then sue for
high damages), etc. Fairly standard stuff but in the increasingly
litigious environment of the United States the risks are just too high to
continue without a CLA.
I have not arrived at this decision lightly, but have tried to keep the
CLA as minimal as possible while protecting the project. I don't believe
the CLA grants any further rights to the project than already intuitively
granted when people contribute to an open source project; if I am in error
please let me know ASAP!
Until I get feedback from the core team this is not mandatory for anyone
who has already contributed to the project. Above all I do not want to
alienate the core development team without whom this project would not be
possible.
The agreements (and rationale) are available here:
https://www.trinitydesktop.org/cla/
Thank you for your consideration,
Timothy Pearson
Trinity Desktop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlQ//XAACgkQLaxZSoRZrGH4YQDeIfueuXHs5kOZWWs8cvkeQgPJ
jOJmkwmyVHMNPwDgtittrcLJjTacpbAEnRaCagrlBEZWSQkyzGLoSQ==
=ppdv
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
The main pearsoncomputing.net Email server (which also hosts the TDE
mailing lists) will be going down for scheduled maintenance shortly
(11/06/2014 16:00 GMT). Estimated termination of scheduled maintenance is
11/07/2014 05:00 GMT.
During this window I will (in addition to many other changes) be
addressing the sporadic list delivery issues to specific addresses
relating to DKIM implementation on certain service providers. It is hoped
that these upgrades will stabilize the lists somewhat and make them easier
to use.
The list software interfaces will not be changing, and no list archives
will be lost.
Thank you for your patience!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlRblwoACgkQLaxZSoRZrGFevwDgttq886bSgjT2+Kq/A5Hj8uIA
hKCyZxu2SA6v5gDdHuXgpU3ba+Ae7A+2bvh6/xiwQfJF6g/iaEC7Ag==
=ClQc
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Slavek, all,
When building TDE on Debian Jessie I have run into several instances where
tdebase FTBFS due to the recent changes in CMake policy CMP0046. Setting
the OLD behavior repairs the problem.
Are there any drawbacks to setting CMP0046 OLD globally? If not can one
of the CMake gurus here please push a proper patch to the cmake module
ASAP?
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlQyFioACgkQLaxZSoRZrGET/wDeLn3j3AwlGR+gzz6UfWh54BqD
twCjpFoz79D+nADcD99Wj3aPT1LjXpsry4upoilcdxShhVi39nYSPQ==
=F97K
-----END PGP SIGNATURE-----
