HEADSUP Maintainers: Stale packages on sourceware

[Yaakov Selkowitz]

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.