ke, 2005-08-31 kello 17:31 -0400, Daniel Jacobowitz kirjoitti:
> On Thu, Sep 01, 2005 at 12:27:58AM +0300, Lars Wirzenius wrote:
> > Now I'm glad I didn't mark it critical. *Blush* A bad thinko on my part,
> > I completely misremembered how grep works with regard to exit codes.
> > Sorry. (I need t
On Thu, Sep 01, 2005 at 12:27:58AM +0300, Lars Wirzenius wrote:
> Now I'm glad I didn't mark it critical. *Blush* A bad thinko on my part,
> I completely misremembered how grep works with regard to exit codes.
> Sorry. (I need to learn to stop filing bugs when it gets late.)
>
> However, it now st
ke, 2005-08-31 kello 16:19 -0400, Daniel Jacobowitz kirjoitti:
> On Wed, Aug 31, 2005 at 10:55:53PM +0300, Lars Wirzenius wrote:
> > if grep -v '^/lib64$' /etc/ld.so.conf > /etc/ld.so.conf-amd64-libs-tmp;
> > then
> > chmod 0644 /etc/ld.so.conf-amd64-libs-tmp
> > mv /etc/ld.so.conf-amd64-libs-t
On Wed, Aug 31, 2005 at 10:55:53PM +0300, Lars Wirzenius wrote:
> if grep -v '^/lib64$' /etc/ld.so.conf > /etc/ld.so.conf-amd64-libs-tmp;
> then
> chmod 0644 /etc/ld.so.conf-amd64-libs-tmp
> mv /etc/ld.so.conf-amd64-libs-tmp /etc/ld.so.conf
> else
> rm -f /etc/ld.so.conf
> fi
>
> I'm pretty
Package: amd64-libs
Version: 1.2
I was tempted to make this "Severity: critical", but since I doubt the
bug will manifest itself anytime soon, I'm leaving it as normal. I hope
this was the right thing to do.
While testing amd64-libs-dev with piuparts, I noticed
that /usr/lib64/libncurses.so.5 is
5 matches
Mail list logo
