Ditto apr1 and aprutil1 (was Two identically-named libtool directories)
On Sat, Feb 07, 2009 at 01:58:24PM -0500, Christopher Faylor wrote: We have two libtool directories with two setup.hints in ~release/_obsolete and ~release. This is causing problems. It seems like things have been like this since at least November and no one was complaining because upset threw out the _obsolete package in favor of a newer one thanks purely to the fragile sort order directory inspection. That has changed now thanks to last week's problems. People are complaining about getting out-of-date versions of libtool. Maybe I'll figure out the intent two seconds after sending this message but I can't see any reason to have two packages with identical names in the release so I have deleted the _obsolete/libtool packages. Looks like even error-checking for upset is in order. Two more culprits. I don't understand why these duplicate named directories and setup.hints were created. Package names are supposed to be unique so it was basically luck (and an upset bug) that the _obsolete directories were quietly overridden before. I've removed _obsolete/apr1 and _obsolete/aprutil1. cgf
Re: Ditto apr1 and aprutil1 (was Two identically-named libtool directories)
On 2/7/2009 11:22 AM, Christopher Faylor wrote: On Sat, Feb 07, 2009 at 01:58:24PM -0500, Christopher Faylor wrote: We have two libtool directories with two setup.hints in ~release/_obsolete and ~release. This is causing problems. It seems like things have been like this since at least November and no one was complaining because upset threw out the _obsolete package in favor of a newer one thanks purely to the fragile sort order directory inspection. That has changed now thanks to last week's problems. People are complaining about getting out-of-date versions of libtool. Maybe I'll figure out the intent two seconds after sending this message but I can't see any reason to have two packages with identical names in the release so I have deleted the _obsolete/libtool packages. Looks like even error-checking for upset is in order. Two more culprits. I don't understand why these duplicate named directories and setup.hints were created. Package names are supposed to be unique so it was basically luck (and an upset bug) that the _obsolete directories were quietly overridden before. I've removed _obsolete/apr1 and _obsolete/aprutil1. apr1 and aprutil1 packages are supposed to be in the _obsolete category. The other packages should be in libapr1 and libaprutil1. -- David Rothenberger daver...@acm.org enhance, v.: To tamper with an image, usually to its detriment.
Re: Ditto apr1 and aprutil1 (was Two identically-named libtool directories)
On Sat, Feb 07, 2009 at 01:09:35PM -0800, David Rothenberger wrote: On 2/7/2009 11:22 AM, Christopher Faylor wrote: On Sat, Feb 07, 2009 at 01:58:24PM -0500, Christopher Faylor wrote: We have two libtool directories with two setup.hints in ~release/_obsolete and ~release. This is causing problems. It seems like things have been like this since at least November and no one was complaining because upset threw out the _obsolete package in favor of a newer one thanks purely to the fragile sort order directory inspection. That has changed now thanks to last week's problems. People are complaining about getting out-of-date versions of libtool. Maybe I'll figure out the intent two seconds after sending this message but I can't see any reason to have two packages with identical names in the release so I have deleted the _obsolete/libtool packages. Looks like even error-checking for upset is in order. Two more culprits. I don't understand why these duplicate named directories and setup.hints were created. Package names are supposed to be unique so it was basically luck (and an upset bug) that the _obsolete directories were quietly overridden before. I've removed _obsolete/apr1 and _obsolete/aprutil1. apr1 and aprutil1 packages are supposed to be in the _obsolete category. The other packages should be in libapr1 and libaprutil1. They were but they were spread out in two different locations in the ftp area. cgf
