tde-devels

devels@trinitydesktop.org

8 participants
3849 discussions

Change in the repo?
by Diego Vadell 31 Dec '19

31 Dec '19

Hi everyone! I'm upgrading trinty (just apt update) and got this message: E: Repository ' http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org' E: Repository ' http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Label' value from 'Trinity Desktop Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' E: Repository ' http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' Should I continue? Thanks! And happy new year for you all!!

2 2

Re: [trinity-devel] Change in the repo?
by midi-pascal 31 Dec '19

31 Dec '19

On 2019-12-31 9:54 a.m., Slávek Banko wrote: > On Tuesday 31 of December 2019 15:17:28 Diego Vadell wrote: >> Hi everyone! >> >> I'm upgrading trinty (just apt update) and got this message: >> >> E: Repository ' >> http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu >> bionic InRelease' changed its 'Origin' value from >> 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org' >> E: Repository ' >> http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu >> bionic InRelease' changed its 'Label' value from 'Trinity Desktop >> Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' >> E: Repository ' >> http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu >> bionic InRelease' changed its 'Suite' value from 'bionic' to '' >> >> >> Should I continue? >> Thanks! And happy new year for you all!! > Hi Diego, > > in conjunction with the release of R14.0.7, changes have been made to the > primary archive. The repository is now managed by the reprepro tool. As a > result, InRelease files are now generated. And also Contents files useful > for apt-file are generated. That is why Origin and Label has changed, the > Suite is not set when it is the same as the distribution name (Codename) > and a new GPG signing key is used. See: > > https://wiki.trinitydesktop.org/Release_Notes_For_R14.0.7 > > Cheers Hi Slávek, Thanks for the link! I did not noticed the changes to the sources.list file. TDE is now upgraded and is up and running. Thanks and a happy new year to all TDE enthusiasts!

2 1

Re: [trinity-devel] Change in the repo?
by midi-pascal 31 Dec '19

31 Dec '19

Hi, Same problem here. On 2019-12-31 9:17 a.m., Diego Vadell wrote: > Hi everyone! > > I'm upgrading trinty (just apt update) and got this message: > > E: Repository > 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu > bionic InRelease' changed its 'Origin' value from > 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org > <http://trinitydesktop.org>' > E: Repository > 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu > bionic InRelease' changed its 'Label' value from 'Trinity Desktop > Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' > E: Repository > 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu > bionic InRelease' changed its 'Suite' value from 'bionic' to '' > > > Should I continue? > Thanks! And happy new year for you all!! > >

1 0

tdelibs errors, dependencies, and CMake options (Gentoo again)
by E. Liddell 30 Dec '19

30 Dec '19

The good news is that 14.0.6 builds for me quite happily, although the ebuild code for switching aRts support on is temporarily broken. I haven't tried 14.0.7 yet. The bad news is that the git source won't build for me. The error is unenlightening: [1010/2200] cd /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999_build/doc/tdespell && /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999_build/kdoctools/meinproc --srcdir=/var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999/kdoctools --check --cache index.cache.bz2 /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999/doc/tdespell/index.docbook FAILED: doc/tdespell/index.cache.bz2 cd /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999_build/doc/tdespell && /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999_build/kdoctools/meinproc --srcdir=/var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999/kdoctools --check --cache index.cache.bz2 /var/tmp/portage/trinity-base/tdelibs-9999/work/tdelibs-9999/doc/tdespell/index.docbook (Full build log available upon request.) There don't seem to have been any git commits touching kdoctools, tdespell, or anything else related in quite a long time. Or is this because I'm trying to build without udisks support (see below)? Does anyone have any insight, or is it time to file a bug? Now, the other things about the git source: A comparison of multiple versions of CMakeLists.txt shows that the WITH_UDISKS and WITH_UDISKS2 options are being removed. Are they supposed to be subsumed into WITH_TDEHWLIB, or is udisks2 going to be an absolute requirement for building TDE in the future? (Minimalist configurations are quite common in Gentoo, so I need to get this right.) There are three new options: WITH_PCSC, WITH_PKCS, and WITH_CRYPTSETUP, one of which has a not-very-useful description. My understanding is that: WITH_PCSC offers support for smartcards and requires the pcsc-lite library WITH_PKCS offers support for PKCS#11 crypto and requires (I think) the library packaged by Gentoo as dev-libs/pkcs11-helper WITH_CRYPTSETUP offers support for filesystem encryption(?) using sys-fs/cryptsetup(?) Am I missing anything, or misunderstanding any of these options? E. Liddell

2 2

building TDE... almost done, but not quite ....
by Ilya Dogolazky 28 Dec '19

28 Dec '19

Hello! I followed the instructions in the buildscripts/README.txt file and after 1 day and 10 hours on a modern 16 cores workstation the script 99_build_TDE.sh gave me the message "#### Building process for TDE completed ####" I completed the last steps, namely *) ./create_repo.sh *) add deb [trusted=yes] file:/........./3_repo stretch main (I planned to use buster initially, but switched back to stretch due to some technical problems with the workstation, so it is not a typo here, it's really stretch) *) sudo apt update (messages are looking good, no errors, plenty of compiled packages visible) and now is the great moment to install the self compiled TDE onto the prepared clean machine, the very same workstation, so I'm typing "sudo apt install tde-trinity" and.... Package tde-trinity is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'tde-trinity' has no installation candidate As a matter of fact apt is right: this package is nowhere to find, neither in 2_build nor in 3_repo (both of which are full of .deb files, 923 each) So my question is as usual: how do I proceed now? I never did the installation of TDE in a "package by package" way, I always used the very same "tde-trinity" meta package. Cheers, Ilya D.

4 9

Screenshots for R14.0.7 release
by Michele Calgaro via trinity-devel 27 Dec '19

27 Dec '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi everyone, we are getting ready for a new R14.0.7 release. So as done in the past a couple of times, if anyone wants to contribute new screenshots of their desktop using TDE, please feel free to email them to us. We will look into them and perhaps select some for the R14.0.7 Release Notes page on the wiki. Those not selected will be added to the wiki as done in the past. Thanks a lot in advance and Merry Christmas to all! Cheers Michele -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl4GHTEACgkQKnW3yore 1c8d6w//VrKmyNgXQF9E/yZHJplLRygLyhEt068wmzKVU/oaa+tL7BqEqTcdYTvZ DOMgp9XfLbMkuhUb6fMTjgxtDRM1GzoQ3eLgt1NGmL3xtmX69QIXMA/InbATgYdL bdE7IGqrqp0e3WrPO7tJzOJMdT2fne+dEH9W/IVqpjohvEcNBHpoZU3KCiwcv7Qa xZcBC7k7ecjMwPbxZKGFPrX8EH/8Zz2BtsdGQi7oFSz6i6SedUDClnlpGPT13l31 e6/1EsBQm6T9dtrSDHEPRfuPpSvF7xIxb7+NgdJZHeblOaTR7nC+S+bGDbvHWn91 /FKw5nq0Q37U9kwW1coj61kzCKTR7VIeiyG90dDQNVUzG4iG4pBcx/vwidIrwHHD W+qRnwPVD7lhTJwQxzMxiNoIKcHdqTRrumge+6BUlgUbn9/A/UTOrXImyfhNFVxa WqaG1KnUuCFMaa1edVXEm5UJFNpLWZ8iZvksJBWg7uCmkIwUlY7M+uTyaOHbWyB1 giEX0+COcJjvbAgXe4pwM+Xb9IC/QrTfp2tYO2vZYclIEwHBI6SWuaLEf7aT7RTm xZoBtvDtnylEAAV/iE9tverMorZ+rHPk3V0ZZAk54BG+DQuZZrSml6Auw6Y8gpsr OgPXrBXfe9g2yfDgGt9Lp6+9Kmx1zzQW1oOXP48L/BD9hTWhjr8= =9z2e -----END PGP SIGNATURE-----

1 0

background image settings
by Ilya Dogolazky 21 Dec '19

21 Dec '19

Hello ! I'm trying to setup my self-compiled copy of TDE. I opened "Trinity Control Center" and then "Appearance & Themes" and then "Background". There I selected a picture "Aghi" (showing some green tree branches) and pressed "Apply" (then spent like 10 mins for similar steps, never mind these) As you can see on the screenshot https://i.paste.pics/7kbai.png the background is not changed at all, it's some kind of default picture being there from the very beginning. On my real computer with TDE from official repository there is no such problem, so I suppose I might have either installed or started TDE in some wrong way on this hacking clean system (which is running inside a docker container, so not even systemd is present there). My question is: what process/daemon can be missed or maybe some other reason for this wrong background behaviour ? Just to explain why I so much care about background on a development system: it's about bug #3059 (X11 resources leak). After some research I'm almost sure it's about slide show on background window and now I just want to reproduce this bug in "clean lab conditions". Cheers, Ilya D.

3 3

build scripts again
by Ilya Dogolazky 12 Dec '19

12 Dec '19

Hello! Last week I tried out TDE building scripts: for example 99_build_TDE.sh which successfully finished its work in 38 hours. But later that week I looked into 0_logs/build_result.log and found there some "[FAILED]" messages for ten packages ("k3b-i18n", "k9copy", "kaffeine", "kasablanca", "katapult", "kbarcode", "kbfx", "kbibtex", "kbiff", "kpilot"). Later I tried to run the same script in "local mode" ("-l" flag in BUILD_DEFAULT_OPTIONS variable of _config.sh) but it seems the modules don't see the compilation results of the previously compiled modules. And I didn't find any way in the scripts for them to see. So here are some questions about building scripts: 0) Do I understand correctly that "modules" (as this word is used in command "build_module" for example in 06_applications_03.sh script) are corresponding 1-to-1 to debian source packages on the one hand and to git submodules of TDE/tde repository on the other hand? 1) What exactly is the mechanism used while building with "pbuilder" (i.e. WITHOUT "-l") for the module A to use package B built in one of the previous modules? 2) Does something similar exist while building everything in "local mode" (i.e. WITH "-l") on a clean machine? I see there only the *.deb files, but they don't seem to be installed immediately after creation and then the next step is about to start already and *.deb files are just left there not installed. 3) Is there any simple way to disable colored output which is very nice on the terminal, but quite disturbing while reading logs in a file? 4) Is there a way to stop let's say 99_build_TDE.sh script if a single module compilation failed? 5) Sometimes I see the following lines in the log file (using "show log" -sl option and piping output into a file): dpkg-checkbuilddeps: error: Unmet build dependencies: tdelibs14-trinity-dev [and many more -I.D.] dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) Building completed SUCCESSFULLY [in green color -I.D.] Does this combination (package can't be built, but it's kinda success nevertheless) have any sense or is it some kind of error in the scripts? The meaning of all these questions for me is to understand how to create an environment, where I can rebuild the whole TDE in a reliable way (run a single command and be sure that its success indicates nothing went wrong and everything is built) on a clean machine. Thanks! -- Ilya D.

4 8

[trinity-devel] cannot install TDE in openSUSE Tumbleweed
by Felix Miata 04 Dec '19

04 Dec '19

Trinity cannot be added without breaking most Trinity packages because repos have updated libIlm* from required v2_3 to v2_4. :( -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

pre-built extra dependencies
by Ilya Dogolazky 02 Dec '19

02 Dec '19

Hello! According to build instructions in https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/ma… (the item 9.1 there) I tried to do the following steps: *) apt-key adv --keyserver pool.sks-keyservers.net --recv-key A04BE668 *) added "deb http://mirror.ppa.trinitydesktop.org/trinity-sb stretch deps-r14" into /etc/apt/sources.list *) apt update The "apt-key" command printed this and finished successfully: Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/apt-key-gpghome.XvV2j9eAug/gpg.1.sh --keyserver pool.sks-keyservers.net --recv-key A04BE668 gpg: key 608F5293A04BE668: 7 signatures not checked due to missing keys gpg: key 608F5293A04BE668: public key "Slvek Banko <slavek.banko(a)axis.cz>" imported gpg: Total number processed: 1 gpg: imported: 1 But the "apt update" failed with the following message: Get:6 http://mirror.ppa.trinitydesktop.org/trinity-sb stretch InRelease [40.8 kB] Err:6 http://mirror.ppa.trinitydesktop.org/trinity-sb stretch InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C93AF1698685AD8B Reading package lists... W: GPG error: http://mirror.ppa.trinitydesktop.org/trinity-sb stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C93AF1698685AD8B E: The repository 'http://mirror.ppa.trinitydesktop.org/trinity-sb stretch InRelease' is not signed. My question is if I misunderstood the instructions somehow and if not, how to continue from there? Cheers, Ilya D.

4 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels