[Bug 153146] Re: failing on cups package

2008-10-29 Thread Jean-Baptiste Lallement
According to the latest mail from the reporter: - no such problems in hardy. All clear. cheers mate L. - This is fixed. Thanks for your time and don't hesitate to submit any new bug. ** Changed in: update-manager (Ubuntu) Status: Incomplete = Fix Released -- failing on cups

[Bug 153146] Re: failing on cups package

2008-10-28 Thread Jean-Baptiste Lallement
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance. -- failing on cups

[Bug 153146] Re: failing on cups package

2007-10-23 Thread datakid
Michael, very much appreciate your help, and I apologise that I haven't replied sooner. Unfortunately it is a work computer and I only come in twice a week. Updates are happening smoothly, please find file attached as requested. ** Attachment added: broken /var/lib/dpkg/info/cupsys.list

[Bug 153146] Re: failing on cups package

2007-10-17 Thread Michael Vogt
Thanks for this additional information. It seems like the cupsys package got corrupted. To workaround the issue you can run: $ sudo mv /var/lib/dpkg/info/cupsys.list /var/lib/dpkg/info/cupsys.list.broken $ sudo apt-get install --reinstall cupsys That should fix the problem. Please also attach

[Bug 153146] Re: failing on cups package

2007-10-16 Thread Michael Vogt
Thanks for your bugreport. Could you please attach the file /var/log/apt/term.log to this report? Thanks, Michael ** Changed in: update-manager (Ubuntu) Assignee: (unassigned) = Michael Vogt (mvo) Status: New = Incomplete -- failing on cups package

[Bug 153146] Re: failing on cups package

2007-10-16 Thread datakid
Please find term.log attached as requested. Note that computer was powered down unexpectedly during an update - dog tripped over the extension cord. It was after this that update stopped working. I'm pretty sure that happened about line number 1731. ** Attachment added: term.log