On Wed, Jan 15, 2025 at 8:32 AM Greg Troxel <g...@lexort.com> wrote:
> Please let us know when it appears on the GNU ftp site. The pkgsrc > entry is pointing at that, and I don't want to flip to github and back. > > (I realize ftp upload credential fixing may not be super fast...) > This is not likely to happen, so it is best to change the download link to GitHub permanently. I have changed the links at https://www.gnu.org/software/libcdio/#Download Longer story: I first ran into the problem when updating libcdio paranoia and the experience it was unpleasant. I opened a RT (request tracker) ticket that was maybe cool in the 1990's but nowadays seems a little antiquated. In fact, I noticed that you used the mailing list rather than use savannah's "tasks" page. I got a response through the klunky system after a few days; eventually, someone responded with a link to some instructions and I found I had to now attach a public key to the savannah project now, and possibly also notify a person to register this as well. I added a public key to the savannah project, and also had to change the code used to upload and gpg-sign the package. The code that needs to used has changed over releases, yet again This is probably the 3rd time I have had to change the upload code. You then need to wait 5-10 minutes for a "cron" job to run. It checks and copies. If something is wrong, there is little feedback information about what exactly is wrong, (For example, the public key used is xxx, but I have recorded public key yyy). So to fix this I would probably need human help, which, from my last experiences was slow, grudging, and somewhat unsatisfactory. So in short, adding code to ftp.gnu.org and RT support can get phased out from libcdio. am sorry to see it go. At this point, if you look at the bulk of the GPL software that FSF lists, you'll see I think that the majority of it is not stored on or using ftp.gnu.org.
