Ubuntu 16.04, 16.10, 17.04, 18.04 Debian 8, 9 Pale Moon repositories

[strikematch]

Please show again

Code: Select all

cat /etc/apt/sources.list

Sure. It's the default plus two of the three repos you mentioned in a previous post:

Code: Select all

root@focal:~# cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ focal main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ focal-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse

I only intend to use this jail for Pale Moon and Brave, but if you think adding focal-backports is still advisable in that scenario I'll add it.

[Pentium4User]

It is okay now.

[stevepusser]

Looks like Debian testing and Sid have just dropped gcc-8 and 9 from their repos, so I'll have to switch to gcc-10 for those builds.

At the same time, I'll probably mess with some of the Ubuntu build depends, so if you get an update notice for 29.0.1-2 packages, they aren't really urgent, so you can hold off if strapped for bandwidth.

I'll probably set up a separate test repo for GTK 3 builds, too, that will be seen as a higher version--something like palemoon-29.0.1-2gtk3. If they work well, maybe I'll switch to GTK 3 for the main repo.

[RoestVrijStaal]

Yes, on Feb 3. See this thread to see how to remove the expired key and get the new one: viewtopic.php?f=37&t=26106

Thanks for the explanation. I asked to be sure that the key was not comprised. (Updating works smooth again)

[stevepusser]

Yes, on Feb 3. See this thread to see how to remove the expired key and get the new one: viewtopic.php?f=37&t=26106

Thanks for the explanation. I asked to be sure that the key was not comprised. (Updating works smooth again)

I have no problems at all with users asking relevant questions about security. I just wish the OBS could have watched the keys to make sure they wouldn't expire, but hey, it's a completely free service--where am I going to find better?

[bgstack15]

In my experience with the OpenSUSE Build Service, if an apt repository is not re-built due to a lack of new/rebuilt packages, then an old apt repo will still point to an outdated GPG key. The main project's GPG key is rotated. But if, e.g., a Debian 9 repository has only one package in it which was last built before the GPG key rotated, the Debian 9 repo then points to the now-expired and possibly even deleted GPG key. I had to trigger a package rebuild which then rebuilt the apt repo. I think the OBS has an option to merely regenerate the apt repo without having to rebuild packages though. But with all the UI changes it's hard to keep track of the feature set.