> Debian Bug Tracking System <[EMAIL PROTECTED]> [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 PROTECTED]>. > > 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. Thanks! wbr, Lukas -- Lukas Ruf <http://www.lpr.ch> | Ad Personam rbacs <http://wiki.lpr.ch> | Restaurants, Bars and Clubs Raw IP <http://www.rawip.org> | Low Level Network Programming Style <http://email.rawip.org> | How to write emails -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
