> Debian Bug Tracking System <email address hidden> [2005-08-19
> 07:53]:
>
> This is an automatic notification regarding your Bug report #323890:
> base-config: db_fset bug *still* exists, which was filed against the
> base-config package.
>
> It has been closed by one of the developers, namely Steve Langasek
> <email address hidden>.
>
> Content-Type: text/plain; charset=us-ascii Content-Disposition:
> inline Content-Transfer-Encoding: quoted-printable
>
> Version: 2.71
>
> On Fri, Aug 19, 2005 at 06:47:30AM +0200, Lukas Ruf wrote:
> > Package: base-config Version: 2.70 Severity: serious
>
> > the bug db_fset *still* exists!
>
> No, it doesn't. This bug is fixed in base-config 2.71, available
> from incoming.debian.org.
>
today at around 06h am (CET), I run the usual update/upgrade cycle on
my latop.
there, the following message appeared:
grave bugs of base-config (2.69 -> 2.70) <done>
#323863 - base-config: line 59: syntax error near unexpected token `db_fset'
Summary:
base-config(1 bug)
Now, run the same update/upgrade cycle and get the same message on
another box.
But I see: the "done" message appears alread for 2.69 -> to 2.70
although the bug has been fixed obviously only in 2.71.
Hence, my reporting was caused by the message already for 2.69 ->
2.70 although it's been fixed for 2.70 -> 2.71.
So, when base-config 2.71 will have made its way from
incoming.debian.org to the repository for common update/upgrade, the
bug will disappear -- most presumably.
Message-ID: <email address hidden>
Date: Fri, 19 Aug 2005 08:07:43 +0200
From: Lukas Ruf <email address hidden>
To: <email address hidden>
Subject: Re: Bug#323890 acknowledged by developer (Re: Bug#323890: base-config: db_fset bug *still*
exists)
> Debian Bug Tracking System <email address hidden> [2005-08-19 Disposition: Transfer- Encoding: quoted-printable debian. org.
> 07:53]:
>
> This is an automatic notification regarding your Bug report #323890:
> base-config: db_fset bug *still* exists, which was filed against the
> base-config package.
>
> It has been closed by one of the developers, namely Steve Langasek
> <email address hidden>.
>
> Content-Type: text/plain; charset=us-ascii Content-
> inline Content-
>
> Version: 2.71
>
> On Fri, Aug 19, 2005 at 06:47:30AM +0200, Lukas Ruf wrote:
> > Package: base-config Version: 2.70 Severity: serious
>
> > the bug db_fset *still* exists!
>
> No, it doesn't. This bug is fixed in base-config 2.71, available
> from incoming.
>
today at around 06h am (CET), I run the usual update/upgrade cycle on
my latop.
there, the following message appeared:
grave bugs of base-config (2.69 -> 2.70) <done>
#323863 - base-config: line 59: syntax error near unexpected token `db_fset'
Summary:
base-config(1 bug)
Now, run the same update/upgrade cycle and get the same message on
another box.
But I see: the "done" message appears alread for 2.69 -> to 2.70
although the bug has been fixed obviously only in 2.71.
Hence, my reporting was caused by the message already for 2.69 ->
2.70 although it's been fixed for 2.70 -> 2.71.
So, when base-config 2.71 will have made its way from
incoming.debian.org to the repository for common update/upgrade, the
bug will disappear -- most presumably.
Thanks!
wbr, www.lpr. ch> | Ad Personam wiki.lpr. ch> | Restaurants, Bars and Clubs www.rawip. org> | Low Level Network Programming email.rawip. org> | How to write emails
Lukas
--
Lukas Ruf <http://
rbacs <http://
Raw IP <http://
Style <http://