I had this from hardy - lucid. One pinned rdiff-backup package
triggered a requirement on a specific old version of python, which
caused heck to break loose.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was in the same situation for the Intrepid-Jaunty upgrade, with the
jaunty repository pinned to priority 50. Arguably the situation
improved, since the upgrade did not crash, but it only upgraded a
limited number of packages (including the new kernel). Also after
upgrade finished and after
** Changed in: update-manager (Ubuntu)
Target: None = later
--
Pinned hardy repository causes update-manger to fail but shows no error message
https://bugs.launchpad.net/bugs/203659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm this. Followed the steps in the previous post and got
identical output. Log files to follow.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
Pinned hardy repository causes update-manger to fail but shows no error message
** Attachment added: apt.log
http://launchpadlibrarian.net/13406199/apt.log
--
Pinned hardy repository causes update-manger to fail but shows no error message
https://bugs.launchpad.net/bugs/203659
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: main.log
http://launchpadlibrarian.net/13406203/main.log
--
Pinned hardy repository causes update-manger to fail but shows no error message
https://bugs.launchpad.net/bugs/203659
You received this bug notification because you are a member of Ubuntu
Bugs, which is
