tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

Notes on checking for circular dependencies
by Mike Bird 21 Nov '14

21 Nov '14

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

2 1

"Round-off" default splash screen
by Michele Calgaro 18 Nov '14

18 Nov '14

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

2 3

Unused folder in kcontrol
by Michele Calgaro 13 Nov '14

13 Nov '14

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

2 1

New TDE logo idea proposal
by Alexandre 12 Nov '14

12 Nov '14

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

6 7

Contributor License Agreements
by Timothy Pearson 09 Nov '14

09 Nov '14

-----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-----

4 22

Email server maintenance
by Timothy Pearson 07 Nov '14

07 Nov '14

-----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-----

1 1

CMake CMP0046 changes
by Timothy Pearson 06 Nov '14

06 Nov '14

-----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-----

3 7

[trinity-devel] Problem with update of libsvnqt4-trinity
by Werner Bast 05 Nov '14

05 Nov '14

hi, i tried to update my nightly-build recently but the package libsvnqt4-trinity stays unupdated with the following erromsg: ---------------- nstallArchives() failed: (Reading database ... (Reading database ... 5%% (Reading database ... 10%% (Reading database ... 15%% (Reading database ... 20%% (Reading database ... 25%% (Reading database ... 30%% (Reading database ... 35%% (Reading database ... 40%% (Reading database ... 45%% (Reading database ... 50%% (Reading database ... 55%% (Reading database ... 60%% (Reading database ... 65%% (Reading database ... 70%% (Reading database ... 75%% (Reading database ... 80%% (Reading database ... 85%% (Reading database ... 90%% (Reading database ... 95%% (Reading database ... 100%% (Reading database ... 1154314 files and directories currently installed.) Preparing to replace libsvnqt4-trinity 4:14.0.0-r200-0ubuntu12.04.0+pr25 (using .../libsvnqt4-trinity_4%%3a14.0.0-r205-0ubuntu12.04.0+pr25_amd64.deb) ... Unpacking replacement libsvnqt4-trinity ... dpkg: error processing /var/cache/apt/archives/libsvnqt4-trinity_4%%3a14.0.0-r205-0ubuntu12.04.0+pr25_amd64.deb (--unpack): trying to overwrite '/opt/trinity/lib/libsvnqt.so.4.2.2', which is also in package tdesvn-trinity 4:14.0.0-r205-0ubuntu12.04.0+pr25 No apport report written because MaxReports is reached already dpkg-deb (subprocess): subprocess data was killed by signal (Broken pipe) dpkg-deb: error: subprocess <decompress> returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libsvnqt4-trinity_4%%3a14.0.0-r205-0ubuntu12.04.0+pr25_amd64.deb Error in function: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ------------------------- So, its impossible to upgrade this package. Could you please correct this error Thanks Werner

1 0

Divided libtool × libtool-bin
by Slávek Banko 04 Nov '14

04 Nov '14

Hi all, we have another unwelcome message: libtool (2.4.2-1.11) unstable; urgency=medium * Non-maintainer upload. * Drop libtool's dependency on libtool-bin. * Add libtool-bin dependency on libtool. * Make libtool Multi-Arch: foreign. Closes: #682045. * Bump standards version to 3.9.6. -- Matthias Klose <doko@.........> Tue, 14 Oct 2014 19:21:11 +0200 This means that the packages that need to building libtool will need to have a set to variant dependency: "libtool-bin | libtool". I suggest to wait for a change in tde-packaging before we know what all packages will be affected. Now I ran into this problem with pytdeextensions and bibletime. We will see what will follow. We'll see whether it will be appropriate to wait for the change after RC1. -- Slávek

3 6

Improvements to the "Patches from GIT" web page
by Michele Calgaro 30 Oct '14

30 Oct '14

The new "patches from GIT" page looks good and so does the search field at the bottom. Anyhow IMO there are still a few things to fix: 1) email addresses are shown in full, which is not that good being a page available without any login. It would be advisable to remove them, both from the committer column and the Log message column (for signed-off commits). 2) I believe the correct name of the committer column should be "Author" 3) The page still displays with problems if the width of the browser window is small enough (the blue left side menu overlaps the page contents) 4) The search field would probably be better if it was at the top, since it does not take up much page space. At the moment we need to scroll the whole page if we want to search for a particular commit 5) the 'page navigation' (the one saying 'Now viewing patches...') would be better if it had links to the next and previous adjacent pages as in most search engines (something like [1], [2], [3], .... to make it clear) 6) IMO, the name "Patches from GIT" is misleading for new users, as I already said in a previous email. Would be better to call it "GIT Commits" or "Commit history" or something with "commit" in it Hope this is useful. Cheers Michele

3 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels