MantisBT - Doomseeker
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004062Doomseeker[All Projects] Bugpublic2022-12-19 16:042024-11-03 19:16
ReportergeNia 
Assigned ToBlzut3 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformPCOSUbuntuOS Version22.04
Product Version 
Target VersionFixed in Version 
Summary0004062: E: Repository «http://debian.drdteam.org/ stable InRelease» is not signed.
DescriptionA friend of mine uses Ubuntu 22.04 32 bit and he cannot get Doomseeker from drdteam repository.

E: Repository 'http://debian.drdteam.org/ stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-12-19 16:04geNiaNew Issue
2022-12-19 17:36WubTheCaptainNote Added: 0022536
2022-12-19 17:44WubTheCaptainNote Added: 0022537
2022-12-19 17:45WubTheCaptainNote Edited: 0022537bug_revision_view_page.php?bugnote_id=22537#r13781
2022-12-19 17:46WubTheCaptainNote Edited: 0022537bug_revision_view_page.php?bugnote_id=22537#r13782
2022-12-19 18:08WubTheCaptainNote Added: 0022539
2022-12-19 18:09WubTheCaptainNote Edited: 0022539bug_revision_view_page.php?bugnote_id=22539#r13789
2022-12-19 18:10WubTheCaptainNote Edited: 0022539bug_revision_view_page.php?bugnote_id=22539#r13790
2022-12-19 18:18WubTheCaptainNote Edited: 0022539bug_revision_view_page.php?bugnote_id=22539#r13791
2022-12-19 18:21WubTheCaptainNote Edited: 0022539bug_revision_view_page.php?bugnote_id=22539#r13792
2022-12-19 18:27WubTheCaptainNote Edited: 0022536bug_revision_view_page.php?bugnote_id=22536#r13794
2022-12-19 18:28WubTheCaptainNote Edited: 0022536bug_revision_view_page.php?bugnote_id=22536#r13795
2022-12-19 18:33WubTheCaptainNote Added: 0022540
2022-12-19 18:35WubTheCaptainNote Edited: 0022540bug_revision_view_page.php?bugnote_id=22540#r13797
2022-12-19 18:36WubTheCaptainNote Edited: 0022540bug_revision_view_page.php?bugnote_id=22540#r13798
2022-12-19 18:37WubTheCaptainNote Edited: 0022540bug_revision_view_page.php?bugnote_id=22540#r13799
2022-12-19 18:40WubTheCaptainNote Edited: 0022540bug_revision_view_page.php?bugnote_id=22540#r13800
2022-12-19 18:40WubTheCaptainNote Edited: 0022540bug_revision_view_page.php?bugnote_id=22540#r13801
2022-12-19 19:58Blzut3Note Added: 0022543
2022-12-19 20:00Blzut3Assigned To => Blzut3
2022-12-19 20:00Blzut3Statusnew => confirmed
2022-12-20 02:44Blzut3Note Added: 0022544
2022-12-20 02:44Blzut3Statusconfirmed => feedback
2022-12-20 17:41geNiaNote Added: 0022545
2022-12-20 17:41geNiaStatusfeedback => assigned
2022-12-20 21:53Blzut3Note Added: 0022547
2022-12-20 21:54Blzut3Note Edited: 0022547bug_revision_view_page.php?bugnote_id=22547#r13806
2022-12-21 16:02geNiaNote Added: 0022549
2022-12-21 19:20WubTheCaptainNote Added: 0022551
2022-12-21 19:21WubTheCaptainNote Edited: 0022551bug_revision_view_page.php?bugnote_id=22551#r13808
2022-12-21 19:23WubTheCaptainNote Edited: 0022551bug_revision_view_page.php?bugnote_id=22551#r13809
2022-12-21 19:25WubTheCaptainNote Edited: 0022551bug_revision_view_page.php?bugnote_id=22551#r13810
2022-12-21 19:49WubTheCaptainNote Added: 0022552
2022-12-21 19:58WubTheCaptainNote Edited: 0022552bug_revision_view_page.php?bugnote_id=22552#r13812
2022-12-21 20:02WubTheCaptainNote Added: 0022553
2022-12-22 06:05Blzut3Note Added: 0022555
2022-12-22 20:11geNiaNote Added: 0022556
2022-12-23 03:04Blzut3Note Added: 0022557
2022-12-23 03:07Blzut3Note Added: 0022558
2022-12-23 03:07Blzut3Statusassigned => resolved
2022-12-23 03:07Blzut3Resolutionopen => no change required
2024-11-03 19:16ZalewaStatusresolved => closed

Notes
(0022536)
WubTheCaptain   
2022-12-19 17:36   
(edited on: 2022-12-19 18:28)
DRDTeam APT repository works on Debian bookworm/sid. Didn't test on Ubuntu 22.04.
Your error message is missing the preceding "W: GPG error:" message from APT? Did your friend import the repository key?
$ cat /etc/apt/preferences.d/drdteam.pref
# apt_preferences(5) file from the drdteam-archive-keyring package
Package: *
Pin: origin debian.drdteam.org
Pin-Priority: 100

$ cat /etc/apt/sources.list.d/drdteam.sources
# sources.list(5) file from the drdteam-archive-keyring package
Types: deb deb-src
URIs:'https://debian.drdteam.org/ [^]'
Suites: stable
Components: multiverse
Signed-By: /usr/share/keyrings/drdteam-archive-keyring.gpg
Enabled: yes

$ gpg --show-keys /usr/share/keyrings/drdteam-archive-keyring.gpg
pub   rsa2048/0x392203ABAF88540B 2012-05-08 [SC]
      Key fingerprint = 0D8F 900A B77B B504 F2C6  9E7A 3922 03AB AF88 540B
uid                              Braden Obrzut <admin@maniacsvault.net>
sub   rsa2048/0x5A3EE478F1967822 2012-05-08 [E]

Get:1'https://debian.drdteam.org [^]' stable/multiverse amd64 doomseeker-zandronum amd64 46 [197 kB]

Fetched 197 kB in 1s (225 kB/s)
Selecting previously unselected package doomseeker-zandronum.
(Reading database ... 190456 files and directories currently installed.)
Preparing to unpack .../doomseeker-zandronum_46_amd64.deb ...
Unpacking doomseeker-zandronum (46) ...
Setting up doomseeker-zandronum (46) ...

Nudging this issue towards 0003601:0021894 as a related issue, however. The documentation on DRDTeam repository page (using apt-key and apt-add-repository) is a bit dated.
PS: Project: "Doomseeker" → "Site" may be appropriate.
(0022537)
WubTheCaptain   
2022-12-19 17:44   
(edited on: 2022-12-19 17:46)
NB: You can manually configure APT as above, but my suggested way to configure the DRDTeam repository (automatically) is to use the drdteam-archive-keyring package (above), available in 0003601 attachments as source code, until the package becomes distributed from DRDTeam (as a download). At the time of writing this, there's no official binary distribution of it (yet) or user documentation (for building the package).
$ dpkg -l drdteam-archive-keyring
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                    Version      Architecture Description
+++-=======================-============-============-===============================================================

ii  drdteam-archive-keyring 2012.05.08+0 all          OpenPGP archive keys for the DRD Team Debian Package 
Repository
(0022539)
WubTheCaptain   
2022-12-19 18:08   
(edited on: 2022-12-19 18:21)
PS for manual APT configurations: Deviating from above examples, instead please prefer to use the /usr/local/share/keyrings/drdteam-archive-keyring.gpg path, if you're not using a Debian/Ubuntu package (drdteam-archive-keyring). You may need to create the /usr/local/share/keyrings/ directory first. Files and directories should be owned by root:staff.
(0022540)
WubTheCaptain   
2022-12-19 18:33   
(edited on: 2022-12-19 18:40)
By the way, theoretically the DRD Team repository is unsupported on Ubuntu 22.04 (and Debian), because the packages are acclaimed to have been built on Ubuntu 18.04 LTS (which has standard support until 2023-04-26). Not going to debate here if the supported versions at the third-party repository (DRD Team) should change, because it's another issue for the "Site" project, for which the "Doomseeker" project on the tracker can't provide first-party support (from developers).
(0022543)
Blzut3   
2022-12-19 19:58   
@WubTheCaptain, the DRD Team repo absolutely supports all currently supported Ubuntu releases. I use it myself and I upgrade to the 6-month Ubuntu release usually on day 1.

However, support for 32-bit in the DRD Team repo will end April 26th as the last version of Ubuntu to have official support in any capacity was 18.04. I know Debian still supports 32-bit, but GZDoom is already blocking 32-bit from building (without source edits), most projects don't test it anymore, and I'll be looking to start support 64-bit ARM around then (three architectures is too much for my manual process). To be clear I won't be pulling down the downloads on that day, but new 32-bit builds may stop being published starting then.

@geNia, did you mean to say that your friend was running 18.04, or is there an unofficial build of Ubuntu for 32-bit somewhere? Not that it would change my support plans, but I would be curious to know about it for personal reasons anyhow.

With all that said, I'm confirming that there is an issue with the 32-bit metadata at the moment and will look into it.
(0022544)
Blzut3   
2022-12-20 02:44   
OK, looks like my test setup was just missing a package. Ensure that software-properties-common, wget, and gpg packages are installed and instructions on site should work fine for Ubuntu 18.04 and Debian 11.
(0022545)
geNia   
2022-12-20 17:41   
Nevermind the 32 bit thing, he uses amd64 and didn't know that until now. He wasn't even sure if his old PC is 64 bit.

I ended up building Doomseeker myself and distribute it alongside Q-Zandronum to avoid such problems. People may still need to install dependencies, but those are available in secure repos.
(0022547)
Blzut3   
2022-12-20 21:53   
(edited on: 2022-12-20 21:54)
Can your friend give you the output of the apt-key command? It seems likely that command failed for some reason.

The instructions are based on what's available on base installs of the OS so shouldn't need to do any dependency installing. That said it is possible to have more minimal than base installs (i.e. containers).
(0022549)
geNia   
2022-12-21 16:02   
My friend removed the drdteam repo already since he doesn't need it anymore. Does he need to add it again? Can you post exact commands you want to try?
(0022551)
WubTheCaptain   
2022-12-21 19:20   
(edited on: 2022-12-21 19:25)
I believe Blzut3 meant the following command found on DRD Team repository web page:
Quote from DRD Team Debian Package Repository
wget -O-'https://debian.drdteam.org/drdteam.gpg [^]' | sudo apt-key add -

Beware, this compromises your system's apt-secure(8). The apt-key utility has also been deprecated; Ubuntu 22.04 is the last version to supposedly support it, with the exception of apt-key del still being slightly supported.
To secure a compromised APT after adding a key when the repository is no longer used or needed or uses the drdteam-archive-keyring package (secure APT), sudo apt-key del 0x392203ABAF88540B. Highly recommending this for any system that no longer uses the DRD Team repository, so that the key cannot be used to verify packages from your distribution's official archives.
(0022552)
WubTheCaptain   
2022-12-21 19:49   
(edited on: 2022-12-21 19:58)
The above 0004062:0022551 said, I would not bother your tech illiterate friend to do more than sudo apt-key del 0x392203ABAF88540B to reverse the damage caused to his system's security by the DRD Team's instructions (also because he doesn't need the repository anymore). If he didn't know his system is running the amd64 distribution, chances are he doesn't know if he's running Ubuntu 22.04 or 22.10.
Blzut3 can try to replicate the issue in OP on Ubuntu 22.10, where apt-key add is no longer supported. (I didn't test.)
0004062:0022543 hinted the DRD Team repository is manually maintained. It also doesn't support Debian source packages (0003604). The whole repository and its processes, from maintainership to user documentation, needs a rework, imho. Then the issue at OP should also become irrelevant.
This apt-key add stuff needs to go away anyway in the current era, it's a known issue.
(0022553)
WubTheCaptain   
2022-12-21 20:02   
I wish we had a more well maintained third-party (or even a first-party) repository than the DRD Team one, but as of writing this, we don't. The mature resolution would be to fix the grievances myself by setting up another APT repository, but alas, I'm not willing to pay the costs or the effort alone.
(0022555)
Blzut3   
2022-12-22 06:05   
WubTheCaptain is correct on the command. I am noticing now that the Doomseeker website never had that command on its download page, so perhaps that's where the issue stems? If that command was skipped you'd get exactly the error you gave. Also if wget or apt-key failed.

If your friend has no interest in using the repo, which will be useful to get updates delivered, that's fine just let me know that this ticket can be closed.
(0022556)
geNia   
2022-12-22 20:11   
Yeah, my friend doesn't want to mess with it anymore. You can close the ticket, but I believe that the repo issue should be resolved.
Also, why don't you upload doomseeker to main repos like the ubuntu one?
(0022557)
Blzut3   
2022-12-23 03:04   
The problem with getting into the distro repositories is that they won't deliver upgrades. So if we got 1.3.3 in, it would have to be 1.3.3 for the entire 5 years Ubuntu LTS is supported. Unless some kind of exception is worked out. When you combine that with some pedantic packaging rules I personally don't find it to worthwhile. (To be clear most of them are well thought out and I can fully understand why they're there, but they are counter to what the average user would expect. For example, this community generally considers it OK to ship Doom themed graphics like the player sprite as part of the program, but Debian would consider that problematic. They're not wrong, but it means we couldn't provide Doomseeker as we intend through that channel.)

It would be nice if there was an easier way to add third party repos (it would certainly help if the Qt version of the software sources dialog didn't crash when adding a key for example). Although it might be possible to extend WubTheCaptains work on building a key package to provide a standalone deb that can be installed to add the repo (similar to say epel-release in AlmaLinux).
(0022558)
Blzut3   
2022-12-23 03:07   
The issue with the Doomseeker website not having the right instructions can be folded into 0003601. Since we should probably change the instructions to something that doesn't trigger the deprecation warning on the latest releases anyway no sense addressing it with this ticket.