On Wed, Mar 30, 2011 at 07:45:57PM +0200, Serafeim Zanikolas wrote: > Hi Bill, > > On Wed, Mar 30, 2011 at 05:46:27PM +0200, Bill Allombert wrote [edited]: > > As far as I understand, this is a warning, not an anormal termination. > > Yes, we could check the return value of open, but it this instance I > > feel that the warning is legitimate. > > Agreed, but the user that sees the warning cannot tell that. > > > For example, if the user set up a cron job that automatically update their > > system, > > it can alert them that there is a conflict. > > > > Please note that this bug was also reported as #555790. I am still not > > quite sure > > how to address it. > > Perhaps add a msg to make it clear that it is normal under certain > circumstances (along the lines of "failed to open xxx (this is normal if > dpkg was running at the same time)". This will save you from having to deal > with such bug reports in the future.
Well, I have already changed the warning to read: "popcon: file $dpkg_db/$pkg.list is missing\n" Cheers, -- Bill. <[email protected]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
