Re: HEADSUP Maintainers: Stale packages on sourceware
On 2014-10-29 08:42, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? Not having heard any, I have just removed all stale packages from sourceware, and plan to continue doing so periodically going forward. -- Yaakov
Re: HEADSUP Maintainers: Stale packages on sourceware
On 10/29/2014 6:42 AM, Yaakov Selkowitz wrote: Do maintainers have any objections to these being removed? Fine with me. -- David Rothenberger daver...@acm.org
Re: HEADSUP Maintainers: Stale packages on sourceware
Op 29-10-2014 14:42 Yaakov Selkowitz schreef: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? No. -- Erwin Waterlander http://waterlan.home.xs4all.nl/
Re: HEADSUP Maintainers: Stale packages on sourceware
2014-10-29 14:42 GMT+01:00 Yaakov Selkowitz: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? No problem. Regards, Frank
Re: HEADSUP Maintainers: Stale packages on sourceware
On Oct 29 08:42, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? Not at all. Please note that the cygwin package 1.7.31-3 is not accessible via setup right now because I neglected to add it as prev version to setup.hint. I just fixed that on sourceware. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp7w2sI2QHHP.pgp Description: PGP signature
Re: HEADSUP Maintainers: Stale packages on sourceware
On Wed, Oct 29, 2014 at 08:42:12AM -0500, Yaakov Selkowitz wrote: Do maintainers have any objections to these being removed? No objection from me. I'll try and remember to clear off old versions myself when uploading in future.
Re: HEADSUP Maintainers: Stale packages on sourceware
Yaakov Selkowitz writes: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? As far as my packages are involved, these were kept mostly to allow a manual downgrade of gcc to the previous version. I that is removed as well, they can go. The other bunch of stale packages are inherited from Chuck Wilson, but I don't know if they still serve a purpose. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: HEADSUP Maintainers: Stale packages on sourceware
Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? I don't have any objection for my packages (lftp, screen, socat, stunnel). I had actually just noticed these old tarballs on one of the Cygwin mirrors, and was going to ask about them. In my opinion, they should be automatically removed once they're no longer installable. If some maintainers aren't comfortable with that, then maybe the old package files could be removed after a wait of, say, 3 months. But that could take some bookkeeping, and really it's hard to think of a case when it would be important to do. Andrew
Re: HEADSUP Maintainers: Stale packages on sourceware
On 10/29/2014 07:42 AM, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? No complaints from me (and on seeing this email, I manually removed stale files for packages I maintain, such as dash and diffutils) -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: HEADSUP Maintainers: Stale packages on sourceware
Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? No objections for my affected packages (smartmontools). Christian
Re: HEADSUP Maintainers: Stale packages on sourceware
On 10/29/2014 2:42 PM, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? Yaakov In general no problem, just one question: x86_64/release/glpk/glpk-4.48-1.tar.bz2 x86_64/release/glpk/glpk-4.52-1.tar.xz x86_64/release/glpk/glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 x86_64/release/glpk/glpk-debuginfo/glpk-debuginfo-4.52-1.tar.xz x86_64/release/glpk/libglpk-devel/libglpk-devel-4.48-1.tar.bz2 x86_64/release/glpk/libglpk-devel/libglpk-devel-4.52-1.tar.xz are there as, for example: ./glpk-4.48-1-src.tar.bz2 ./glpk-4.48-1.tar.bz2 ./glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 ./libglpk-devel/libglpk-devel-4.48-1.tar.bz2 ./libglpk33/libglpk33-4.48-1.tar.bz2 where all uploaded together. Will upset complain if we leave only ./glpk-4.48-1-src.tar.bz2 ./glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 ./libglpk33/libglpk33-4.48-1.tar.bz2 Regards Marco
Re: HEADSUP Maintainers: Stale packages on sourceware
On 10/29/2014 21:42, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? Yaakov Since you looked in the setup.hint, nope, go ahead and remove them. signature.asc Description: OpenPGP digital signature
Re: HEADSUP Maintainers: Stale packages on sourceware
On 29/10/14 13:42, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? Thank you for looking into this. I'm happy for older versions of my packages to be removed. Cheers, Dave.
Re: HEADSUP Maintainers: Stale packages on sourceware
On 10/29/2014 9:42 AM, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? No objection. Ken
Re: HEADSUP Maintainers: Stale packages on sourceware
On 2014-10-29 16:59, Marco Atzeri wrote: On 10/29/2014 2:42 PM, Yaakov Selkowitz wrote: Please find attached a list of old package tarballs which are not listed anywhere in setup.ini, meaning that they are not listed as a previous, current, or test package, and cannot be installed with setup. These files consume a total of over 1.3Gib. Do maintainers have any objections to these being removed? In general no problem, just one question: x86_64/release/glpk/glpk-4.48-1.tar.bz2 x86_64/release/glpk/glpk-4.52-1.tar.xz x86_64/release/glpk/glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 x86_64/release/glpk/glpk-debuginfo/glpk-debuginfo-4.52-1.tar.xz x86_64/release/glpk/libglpk-devel/libglpk-devel-4.48-1.tar.bz2 x86_64/release/glpk/libglpk-devel/libglpk-devel-4.52-1.tar.xz are there as, for example: ./glpk-4.48-1-src.tar.bz2 ./glpk-4.48-1.tar.bz2 ./glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 ./libglpk-devel/libglpk-devel-4.48-1.tar.bz2 ./libglpk33/libglpk33-4.48-1.tar.bz2 where all uploaded together. Will upset complain if we leave only ./glpk-4.48-1-src.tar.bz2 ./glpk-debuginfo/glpk-debuginfo-4.48-1.tar.bz2 ./libglpk33/libglpk33-4.48-1.tar.bz2 No. This is actually a common case, where an old DLL ABI version (and its -src) remains for compatibility with packages which still depend on it, but the corresponding -devel/-doc/etc. eventually get pushed into stale status.
