Here is the current status of the mpich/hdf5/lam migration.
lam is currently building on m68k, after which point hdf5 needs to be
requeued on m68k, and then once it builds various other packages will need
requeues on m68k because they're blocked waiting for hdf5.
The following packages still need
On Fri, 2005-09-30 at 17:43 +0100, Matthew Vernon wrote:
> I've been preparing to upgrade some woody systems to sarge, and
> colleagues have pointed out to me that the syntax that md5sum outputs
> has changed. This will break my backup and mirroring arrangements.
> Looking in the BTS, I see bug
Hi,
I've been preparing to upgrade some woody systems to sarge, and
colleagues have pointed out to me that the syntax that md5sum outputs
has changed. This will break my backup and mirroring arrangements.
Looking in the BTS, I see bugs 164591 and 164889; md5sum has been fixed
(at least in exp
On Fri, Sep 30, 2005 at 12:14:14PM +0100, Adam D. Barratt wrote:
> > It appears that the wireless-tools package is still frozen
> > even though sarge has already been released. Therefore
> > the newer packages won't enter testing. Could you unfreeze
> > it?
>
> wireless-tools is frozen because it
Guus Sliepen wrote, Friday, September 30, 2005 11:33 AM
> It appears[0] that the wireless-tools package is still frozen
> even though sarge has already been released. Therefore
> the newer packages won't enter testing. Could you unfreeze
> it
[...]
> [0] http://packages.qa.debian.org/w/wireless-to
Hello,
It appears[0] that the wireless-tools package is still frozen even
though sarge has already been released. Therefore the newer packages
won't enter testing. Could you unfreeze it, or if I'm writing to the
wrong people, tell me who I should contact?
[0] http://packages.qa.debian.org/w/wirel
On Fri, Sep 30, 2005 at 12:49:15AM -0700, Blars Blarson wrote:
> nntp 1.5.12.1-19 fixed the release criitcal bug 61 days ago, but it
> has not propigated to testing. The pts claims this is because it is
> buggy.
http://bugs.debian.org/260732
This bug is listed as "done", but the bug closure mess
nntp 1.5.12.1-19 fixed the release criitcal bug 61 days ago, but it
has not propigated to testing. The pts claims this is because it is
buggy.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an o
8 matches
Mail list logo