[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson
I can still confirm this issue on an upgrade (7.04 to gutsy-rc) started
16-Oct afternoon US Pacific time.  I hit the original python-apt issue,
but the install continued behind the error window.  When it finally
aborted, it ran 'dpkg --configure -a' which eventually failed and can no
longer be started because of the following error:

dpkg: parse error, in file `/var/lib/dpkg/status' near line 33397 package 
`libc6':
 `triggers-pendi' is not allowed for third (status) word in `status' field

Will attach what files I can still find.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /var/log/dist-upgrade/main.log
   http://launchpadlibrarian.net/10053549/main.log

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /var/log/dist-upgrade/main_pre_req.log
   http://launchpadlibrarian.net/10053572/main_pre_req.log

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /var/log/dist-upgrade/term.log
   http://launchpadlibrarian.net/10053573/term.log

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /var/log/dist-upgrade/apt.log
   http://launchpadlibrarian.net/10053547/apt.log

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /var/lib/dpkg/status
   http://launchpadlibrarian.net/10053578/status

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson

** Attachment added: /etc/apt/sources.list
   http://launchpadlibrarian.net/10053612/sources.list

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread fx5
Hi Chris,
thanks for your bug-report, but i think, it is not the same bug.

The update of dpkg failed. I don't know the reason (IOError? maybe a harddisk 
problem?)
-
Preparing to replace dpkg 1.13.24ubuntu6 (using 
.../dpkg_1.14.5ubuntu16_i386.deb) ...
Unpacking replacement dpkg ...
i386.deb) ...
dpkg-deb (subprocess): error in buffer_read(stream): failed to write to pipe in 
copy: Input/output error
dpkg-deb: subprocess paste returned error exit status 2
dpkg: error processing /var/cache/apt/archives/dpkg_1.14.5ubuntu16_i386.deb 
(--unpack):
 short read in buffer_copy (backend dpkg-deb during 
`./usr/share/locale/sk/LC_MESSAGES/dpkg.mo')
Errors were encountered while processing:
 /var/cache/apt/archives/dpkg_1.14.5ubuntu16_i386.deb


Now you still have the old dpkg which has no clue how to handle triggers. First 
thing you have to do is to update your dpkg-package.
This will fail because of the trigger in `/var/lib/dpkg/updates/0006'.
To get it working again, you can try to remove the line
 Triggers-Pending: ldconfig
and replace the line
 Status: install ok triggers-pending
by
 Status: install ok installed

now you can run
 dpkg -i /var/cache/apt/archives/dpkg_1.14.5ubuntu16_i386.deb
 apt-get --reinstall install libc6
 dpkg --configure -a
 apt-get dist-upgrade

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-17 Thread Chris Nelson
Thanks fx5.  After a bit more looking, I had come to the same conclusion
and tried the dpkg install again (after editing /var/lib/dpkg/status),
and the error repeated.  It turned out to be a bad copy of
dpkg_1.14.5ubuntu16_i386.deb in /var/cache/apt/archives.  I downloaded a
new copy and installed it, changed back /var/lib/dpkg/status, and things
are moving along better now.

I guess I had jumped to my conclusion too quickly after seeing the
similarities to the earlier posts.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-16 Thread Deepak Sarda
I think I've been affected by this problem too. Now I'm half through
upgrading Kubuntu to Gutsy and am stuck because none of the dpkg stuff
works. Based on suggestions above, I tried 'apt-get install python-apt'
but it said 'E: dpkg was interrupted, you must manually run 'dpkg
--configure -a' to correct the problem.'

So I ran 'dpkg --configure -a' but I get this error:

dpkg: parse error, in file `/var/lib/dpkg/updates/0003' near line 2 package 
`libc6':
 `triggers-pendi' is not allowed for third (status) word in `status' field

I understand from the above comments that a new python-apt makes dpkg
understand the triggers field. But how do I install this new python-apt
since installing anything needs me to run 'dpkg --configure'. Seems to
me that I'm stuck in a chicken-and-egg situation :(

I tried restarting the update but it couldn't get a lock on the package db. Is 
it okay to delete the stuff in /var/lib/dpkg/updates/* and resume the upgrade? 
Any suggestions appreciated.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-16 Thread fx5
1. When did you start update?
The bug should be fixed.
Please post your /etc/apt/sources.list
Maybe you use a mirror that is not updated yet.
What does apt-cache policy python-apt say?

2. Try this:
 cd /var/cache/apt/archives/
 sudo dpkg -i python-central_0.5.15ubuntu2_all.deb
 sudo dpkg -i python-apt_0.7.3.1ubuntu4_*.deb# Or the version number you 
 have
 sudo dpkg -i dpkg_1.14.5ubuntu16_*.deb
 sudo dpkg --configure -a
 sudo apt-get dist-upgrade

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-16 Thread Deepak Sarda
These are the uncommented lines in my sources.list

deb http://tw.archive.ubuntu.com/ubuntu/ gutsy main restricted multiverse 
universe
deb http://tw.archive.ubuntu.com/ubuntu/ gutsy-updates main restricted 
multiverse universe
deb http://tw.archive.ubuntu.com/ubuntu/ gutsy-security main restricted 
multiverse universe
deb http://tw.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted 
multiverse universe
deb http://archive.canonical.com/ubuntu gutsy partner
deb http://archive.ubuntu.com/ubuntu/ gutsy-proposed restricted main multiverse 
universe
-
I started the upgrade on 16th at around 9pm singapore time (1pm GMT). As you 
say, perhaps the taiwan mirror wasn't yet in sync. But then again, the versions 
of the deb files in the apt cache match those you gave in your steps above.

I can't carry out the steps you suggested since running 'dpkg -i' on any 
package gives me this error:
--
 dpkg: parse error, in file `/var/lib/dpkg/updates/0003' near line 2 package 
`libc6':
 `triggers-pendi' is not allowed for third (status) word in `status' field
--

Do you think there's some way I can force a package install without
worrying about the pending libc6 package? Or roll-back that libc6
upgrade? Or even manually extract the relevant bits from python-
central*.deb, python-apt*deb  dpkg*deb and overwrite the filesystem
with contents from those packages?

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-15 Thread Timo Jyrinki
FlagMan: No, sorry, I misread the logs, my latest addendum did not have
anything to do with this bug.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-15 Thread Michael Vogt
This is fixed with the upload of the latest python-apt (from today). It
will ensure that a version of dpkg is available that understands about
triggers.

Thanks and sorry for the trouble,
 MIchael

** Changed in: update-manager (Ubuntu)
   Status: Confirmed = Fix Released

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-14 Thread FlagMan

@fx5:
triggers may well be the reason, they have just recently been added: 
http://lists.debian.org/debian-dpkg/2007/08/msg9.html

What makes me a bit suspicious is that we all seem to have a
truncated third status word in /var/lib/dpkg/updates/00?? , namely:
triggers-pendi instead of triggers-pending
(look at the various term.log files)

Anyway, I added two other duplicates.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-14 Thread fx5
python-apt is packaged with python-central.
python-central use dpkg-query to read the package-fields (like Python-Version).
dpkg-query seems to fail, because it is the old (feisty-) version that does 
know about triggers.
There is a trigger-status for libc6.

But I don't understand, how this trigger-status is done when dpkg is not 
updated yet.
I tried to find out, but I don't know how this works.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-14 Thread fx5
@FlagMan
 triggers-pendi instead of triggers-pending

When returning an error, dpkg calculates the length of the error-message
by the length of the last word it was looking for. This word is
removal-failed, 14 chars.

(Found in fields.c, line 58)

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-13 Thread FlagMan
@ Timo:
Why do you think this is related?

FWIW:
I can confirm this bug, too.
Encountered it yesterday while doing an upgrade from 7.04 to gutsy-rc.

I get the exact same error as the original poster, beginning with:

dpkg-query: Fehler beim Parsen, in Datei »/var/lib/dpkg/updates/0013« nahe 
Zeile 2 Paket »libc6«:
 »triggers-pendi« ist nicht erlaubt für drittes (Status-)Wort im Feld »status«

and unfortunately, by now /var/lib/dpkg/updates is empty, too.

There were a lot of packages that didn't resolve afterwards, so I consider this 
bug somewhat
critical to upgrading. 
Anyway, I will try the suggestions above.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 146943] Re: Update to gutsy failed

2007-10-13 Thread FlagMan
Oh well,
a simple:

sudo apt-get install python-apt

did fix it without a reboot. All the previously held back packages installed
automatically. Not so critical then. 
Irritating, rather...

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-09 Thread Timo Jyrinki
This was probably related, too, pseudo-translated to English:

Reading changelogs... Done
apt-listchanges: Sending: root: apt-listchanges: news from timo-laptop
sh: /usr/sbin/sendmail: not found
Traceback (most recent call last):
  File /usr/bin/apt-listchanges, line 219, in module
main()
  File /usr/bin/apt-listchanges, line 203, in main
apt_listchanges.mail_changes(config.email_address, news, subject)
  File /usr/share/apt-listchanges/apt_listchanges.py, line 104, in mail_change
s
fh.write(message.as_string())
IOError: [Errno 32] Broken pipe

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-08 Thread Mathias Gug
I've seen the same error during an upgrade to gusty, with python-
apt_0.7.3.1ubuntu2.

I've fixed it with apt-get install python-apt after I rebooted, which
caused all the unconfigured packages to be configured.

I've attached /var/lib/dpkg/status

** Attachment added: status - mathiaz
   http://launchpadlibrarian.net/9882470/status

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-07 Thread Timo Jyrinki
Bug 146956 has some extra logs, unfortunately I neither catched the
/var/lb/dpkg/updates/... file. I fixed the installation with manually
sudo dpkg -i:ing the python-apt package in /var/cache/apt/archives/ and
then sudo dpkg --configure -a.

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-01 Thread Michael Vogt
Thanks for your bugreport. Please attach the files in /var/log/dist-
upgrade/* to this report. Thanks, Michael

** Changed in: update-manager (Ubuntu)
   Status: New = Incomplete

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 146943] Re: Update to gutsy failed

2007-10-01 Thread Michael Vogt
Can you also please attach /var/lib/dpkg/updates/0031 and
/var/lib/dpkg/status ?

-- 
Update to gutsy failed
https://bugs.launchpad.net/bugs/146943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs