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. T
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.
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.
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.3
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.
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 hav
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
> 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 objectio
On Oct 28 12:41, Ken Brown wrote:
> On 8/16/2014 3:04 AM, Achim Gratz wrote:
> >Yaakov Selkowitz writes:
> >>Thanks for the reminder. Where did we leave off wrt breaking out
> >>perl_vendor?
> >
> >I've offered a practical way to do this for everyone to test on a 32bit
> >install. If that works a
