Hello!
According to build instructions in https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/mas... (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@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.
Ilya Dogolazky wrote:
My question is if I misunderstood the instructions somehow and if not, how to continue from there?
pull the same way the new key C93AF1698685AD8B and continue. The one mentioned there seems to be Slaveks personal key while C93AF1698685AD8B used for signing is dedicated to TDE only.
But if you are building the whole project from scratch, why would you need the repository at all?!
regards
On Sunday 01 of December 2019 22:37:08 deloptes wrote:
Ilya Dogolazky wrote:
My question is if I misunderstood the instructions somehow and if not, how to continue from there?
pull the same way the new key C93AF1698685AD8B and continue. The one mentioned there seems to be Slaveks personal key while C93AF1698685AD8B used for signing is dedicated to TDE only.
But if you are building the whole project from scratch, why would you need the repository at all?!
regards
Hi,
note from Deloptes is correct - previously the repository was signed by my personal key, while it is now signed by the general key reserved for TDE. See instructions on the wiki:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
Ilya, I totally understand that you don't need to deal with building build-deps, but you want to focus on packages that are standard part of TDE git repository. Therefore, it makes sense to use apt repository for at least the deps-r14 component.
Cheers
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2019/12/02 09:14 AM, Sl�vek Banko wrote:
On Sunday 01 of December 2019 22:37:08 deloptes wrote:
Ilya Dogolazky wrote:
My question is if I misunderstood the instructions somehow and if not, how to continue from there?
pull the same way the new key C93AF1698685AD8B and continue. The one mentioned there seems to be Slaveks personal key while C93AF1698685AD8B used for signing is dedicated to TDE only.
But if you are building the whole project from scratch, why would you need the repository at all?!
regards
Hi,
note from Deloptes is correct - previously the repository was signed by my personal key, while it is now signed by the general key reserved for TDE. See instructions on the wiki:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
Ilya, I totally understand that you don't need to deal with building build-deps, but you want to focus on packages that are standard part of TDE git repository. Therefore, it makes sense to use apt repository for at least the deps-r14 component.
Cheers
Hi Ilya, sorry for the error in the README file, obviously I have failed to update the key as Emanoil (deloptes) has pointed out. Will rectify that and update. If you encounter any error, please keep reporting things here. I will address, although under heavy work load at the moment.
Cheers Michele
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Ilya, sorry for the error in the README file, obviously I have failed to update the key as Emanoil (deloptes) has pointed out. Will rectify that and update. If you encounter any error, please keep reporting things here. I will address, although under heavy work load at the moment.
Rectified already :-) Cheers Michele
-
deloptes -
Ilya Dogolazky -
Michele Calgaro via trinity-devel -
Slávek Banko