Hi,
can you help and advise how to proceed. I want to push a PR, but I have done
some changes on cmake.
I have never pushed such PR and I am a bit confused cause it seems cmake is
outside of the main package (kplayer).
I committed the changes for cmake in cmake and was thinking to commit iun
kplayer but got some doubts.
# repo-master/tde/1_git/tde/main/applications/kplayer$ git status
On branch issue/1/kplayer
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: cmake (new commits)
Untracked files:
(use "git add <file>..." to include in what will be committed)
.project
no changes added to commit (use "git add" and/or "git commit -a")
# repo-master/tde/1_git/tde/main/applications/kplayer$ git diff
diff --git a/cmake b/cmake
index 8668335..bcfb5b2 160000
--- a/cmake
+++ b/cmake
@@ -1 +1 @@
-Subproject commit 8668335711fa13cec276552d75bfbb4285c7edb0
+Subproject commit bcfb5b2b09fe32b35b65aee16697992648cd740e
Thanks in advance
I'm trying to fix some Gentoo packaging stuff, since Fat-Zer hasn't touched his overlay
in nearly a year and only ever provided live ebuilds (= packages that install directly from
git main branch, not from released versions). There are a bunch of details in the
packaging apparatus that haven't been changed in a long time, and I'm pretty sure that
some of those details are incorrect.
Specific questions:
Permitted licenses for tqt are still listed in the ebuild as "QPL-1.0 GPL-2 GPL-3",
unchanged from qt3. Am I correct in remembering that QPL (Trolltech's proprietary
license) is no longer valid for tqt?
What is the actual version number of tqt? Of tqtinterface? Historically, these followed
a different version scheme from the main desktop, but that seems to have changed.
Currently, I'm dealing with the version numbers, certain directory and file names, and a
Gentoo SLOT (mechanism for tracking multiple versions of the same package installed
in parallel) inconsistently, and I would like to clean things up.
What, exactly, are msg2qm and qembed? The ebuild I inherited for tqt builds them
separately, with comments reading "# Make the msg2qm[/qembed] utility (not made
by default)", and furthermore the build mechanism is currently broken. I need to know
whether or not fixing it is worth the effort. Are these utilities used for building and/or
running anything?
More to come as I work my way through the tree, if I don't just give up and crawl away
into a corner somewhere the way I did the last two times I tried this.
E. Liddell
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!
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