For the last three beta releases, the deb packages on updates.signal.org are deleted post the new release.
I maintain the AUR Package for beta releases, and this breaks the package in the interim while I work on the new release.
While there might be legit reasons for deleting old releases (security fixes!), I'd prefer if this wasn't applied to all releases.
Post the 1.18.0beta.5 release the beta.4 download URL gives a 404
Same issue also reported on stable releases: https://aur.archlinux.org/packages/signal-desktop-bin/
:+1:
This is really annoying, please at least let the last 1-3 releases online.
Yes, in particular in light of issues like https://github.com/signalapp/Signal-Desktop/issues/3422 -- I just ran into this, wanted to downgrade until 1.25.3 is available, but 1.25.1 is already gone.
This would be great.
:+1:
Is signal using reprepro for the repository management? Because of so, this is a known limitation of reprepro, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570623
Hey Signal, PLEASE notice this? :) Thank you!
Bumping this for visibility!
I'm probably gonna get banned for bumping, but it's worth it
The reprepro issue linked above mentions this:
(You can also enable tracking with the options to not remove old packages, but that will only keep the files in the pool and not in any apt-getable index).
Can this be enabled perhaps? The package doesn't have to be in the index, just in the pool for the build to continue working.
Hi, Signal, can you guys please fix this? As mentioned in the above command the package doesn't have to be in the index, just in the pool for the build to continue working.
I found this because my AUR update 404'd. Signal, please fix this.
YOOOO Signal, how is this not fixed yet?
On Fri, Feb 26, 2021 at 7:29 AM Yogesh notifications@github.com wrote:
I found this because my AUR update 404'd. Signal, please fix this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/signalapp/Signal-Desktop/issues/2882#issuecomment-786716651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIBDYXY3SINDJ3H4IBBSDTTA646VANCNFSM4GBVTYDA
.
Can we at least get some sort of update showing that this issue has at least been considered?
Most helpful comment
I'm probably gonna get banned for bumping, but it's worth it