Then I noticed that time stamps on your sever has changed from 06-Dec-2018 to 08-Jan-2019. My first thougt was: WTF ... malware infection or something else?
Last modified today! https://download.opensuse.org/repositories/home:/stevenpusser/Debian_Testing/amd64/palemoon_28.2.2~repack-1_amd64.deb.mirrorlist
What's the reason for new .deb package files on server?
- Pale Moon guru
- Posts: 23006
- Joined: Sun, 28 Aug 2011, 17:27
- Location: 58°2'16"N 14°58'31"E
"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
In Fedora/RHEL/CentOS, one normally uses a dash to separate the application version from the package iteration. For example, from my Fedora COPR for Pale Moon:
Code: Select all
If I make any changes to how it is packaged/bundled/released in the rpm, I would make it a -2.
The package release counter starts over at 1 (silly human languages) when upstream releases a new version, but some projects do actually start at rpm release 0.
One of the automatic Buster rebuilds failed recently, but I think it was earlier than the 8th. I just hit a link called "trigger rebuild" in that case, if all the other build requirements are met.
Stable versions of distros don't see that kind of rebuilding churn. Debian uses the same sort of convention, where the "-n" number denotes a packaging revision, as other distros. If I did revise the debian/copyright file in 28.2.0, I would have incremented that to a -2, but decided to wait until 28.3.0 so I wouldn't push a fairly pointless update of 28.2.0 to everyone. Some people still have limited bandwidth.
Is it apt showing that it's a newer version based on the build date, or some other package updater?
Code: Select all
apt list --upgradeable
The automatic rebuilds should quiet down once Buster enters a harder freeze, though.
The previously-built packages from the 17th are still available--I hope they are still compatible.
Who is online
Users browsing this forum: No registered users and 6 guests