Processing of apr_1.3.3-2_i386.changes

2009-02-24 Thread Archive Administrator
apr_1.3.3-2_i386.changes uploaded successfully to localhost along with the files: apr_1.3.3-2.dsc apr_1.3.3-2.diff.gz libapr1_1.3.3-2_i386.deb libapr1-dev_1.3.3-2_i386.deb libapr1-dbg_1.3.3-2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to

apr_1.3.3-2_i386.changes ACCEPTED

2009-02-24 Thread Debian Installer
Accepted: apr_1.3.3-2.diff.gz to pool/main/a/apr/apr_1.3.3-2.diff.gz apr_1.3.3-2.dsc to pool/main/a/apr/apr_1.3.3-2.dsc libapr1-dbg_1.3.3-2_i386.deb to pool/main/a/apr/libapr1-dbg_1.3.3-2_i386.deb libapr1-dev_1.3.3-2_i386.deb to pool/main/a/apr/libapr1-dev_1.3.3-2_i386.deb

Bug#508144: marked as done (bad description of libapr1-dbg)

2009-02-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Feb 2009 19:47:09 + with message-id e1lc3ff-00087g...@ries.debian.org and subject line Bug#508144: fixed in apr 1.3.3-2 has caused the Debian Bug report #508144, regarding bad description of libapr1-dbg to be marked as done. This means that you claim that the

Bug#492295: marked as done (apr_1.3.2-1(mips/experimental): FTBFS: test failure)

2009-02-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Feb 2009 19:47:09 + with message-id e1lc3ff-00087e...@ries.debian.org and subject line Bug#492295: fixed in apr 1.3.3-2 has caused the Debian Bug report #492295, regarding apr_1.3.2-1(mips/experimental): FTBFS: test failure to be marked as done. This means that you