This bug was fixed in the package python-apt - 0.7.4ubuntu7.5
---
python-apt (0.7.4ubuntu7.5) hardy-proposed; urgency=low
* aptsources/__init__.py, aptsources/distinfo.py:
- run apt_pkg.init() when aptsources gets imported and not
the distinfo function (LP: #239458)
-- M
This bug was fixed in the package update-manager - 1:0.87.31
---
update-manager (1:0.87.31) hardy-proposed; urgency=low
* no changes upload with a current version from python-apt
to fix sparc upgrades from dapper to hardy (LP: #239458)
-- Michael VogtTue, 27 Jan 2009 11:04
** Tags added: verification-done
** Tags removed: verification-failed verification-needed
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Well I have successfully updated to Hardy on sparc architecture. Had a
few issues that were somewhat easily solvable. First, I could not get a
virgin install of Gutsy to install (I figured out why later). So I
installed a virgin install of Feisty. I then upgraded to Gutsy at which
time I could
I have a Sun Ultra E2 that I can use as a test system. I will install
Gutsy, update it, setup a few services and then attempt to upgrade it to
Hardy and see how it goes. I will report my findings here once
completed.
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launch
That sounds exactly what my server did. I really wish sparc was still
mainstream supported. I can see why you would do away with ppc, but a
lot of old sun sparc gear is still very useful ;) Guess I will wait
until the EOL day and upgrade then and see what happens.
--
Getting upgrade prerequisi
It worked ok for me on a Sun V100 ...but I tried to upgrade a sparc
clone and it didn't work at all - it upgraded...and then it wouldn't boot
Luke J Militello wrote:
> Hi, I have a Sun E420R running gutsy and as is it approaching EOL, I
> would like to upgrade it to hardy so I can get LTS suppor
Hi, I have a Sun E420R running gutsy and as is it approaching EOL, I
would like to upgrade it to hardy so I can get LTS support. However, I
did attempt this once and it had disastrous results. It would seem the
upgrade took, but upon rebooting the server, about half way through the
startup, the c
Hi Martin,
I removed xvnc-viewer, which triggered the removal of the ubuntu-desktop
package. After that the upgrade was able to proceed BUT the server
didn't come up after reboot - it freezes at "booting linux..." - looking
around seems to be a problem with the swap partition - anyway that is a
Hello g-rob,
g-rob [2009-01-30 13:12 -]:
> Works; but only when the ubuntu-desktop metapackage is removed;
> otherwise unresolvable dependency problems seem to occur
Can you be more specific, please?
Thanks, Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Develop
Works; but only when the ubuntu-desktop metapackage is removed;
otherwise unresolvable dependency problems seem to occur
Chris Jones wrote:
> testing with --proposed on a sparc64 dapper machine it is now able to
> upgrade the machine.
>
>
--
Getting upgrade prerequisites for system upgrade fail
testing with --proposed on a sparc64 dapper machine it is now able to
upgrade the machine.
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Martin,
It seems to work going from gutsy --> hardy on sparc
I'll let you know for dapper --> hardy
Thanks!!
Robert
Martin Pitt wrote:
> Accepted python-apt into hardy-proposed, please test and give feedback
> here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
> documentatio
Accepted python-apt into hardy-proposed, please test and give feedback
here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: python-apt (Ubuntu Hardy)
Status: In Progress => Fix Committed
** T
I looked into ths today and it turns out the bug is really that pyhton-
apt in hardy-updates calls apt_pkg.init() at the wrong point. So both a
new python-apt and a rebuild of update-manager will be required.
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Chan
** Changed in: update-manager (Ubuntu Hardy)
Assignee: (unassigned) => Michael Vogt (mvo)
Status: Fix Released => In Progress
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received this bug notification because you are a member o
Heurm - I tried the various workarounds listed above but none of them
did the trick on my dapper sparc. Also I can't upgrade my gutsy sparc to
hardy either -- I'll post logs for the gutsy upgrade to this ticket when
I get a chance.
--
Getting upgrade prerequisites for system upgrade failed
https:
According to the recent duplicate ( bug 303926 ) the upgrade from dapper
to hardy on Sparc is still failing.
** Tags added: verification-failed
** Tags removed: verification-needed
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received thi
Copied to hardy-updates. It has been verified that the new update-
manager can successfully upgrade 7.10 to 8.04 without noticeable
regressions. Unfortunately it could not be verified from a third party
that this bug is really fixed, but we strongly believe it is. If you
still have problems, please
** Description changed:
Binary package hint: update-manager
Description:Ubuntu 6.06.2 LTS
Release:6.06
update-manager-core_0.56
- TEST CASE (with powerpc):
+ TEST CASE (with sparc):
1. use a sparc dapper
2. run "sudo do-release-upgrade -d"
3. watch it fail because it c
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: update-manager (Ubuntu Hardy)
Status: In Progress => Fix Committed
** Tags added: v
As a workaround you can run:
$ find /tmp -name "DistUpgrade.cfg.dapper"
then cd into that dir, apply the patch manually and run
$ sudo ./dist-upgrade --mode=server
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received this bug notification
Here is the relevant diff:
=== modified file 'DistUpgrade/DistUpgrade.cfg.dapper'
--- DistUpgrade/DistUpgrade.cfg.dapper 2008-06-20 17:57:39 +
+++ DistUpgrade/DistUpgrade.cfg.dapper 2008-06-24 20:10:21 +
@@ -43,7 +43,6 @@
SourcesList=prerequists-sources.dapper.list
SourcesList-ia64=pre
** Description changed:
Binary package hint: update-manager
Description:Ubuntu 6.06.2 LTS
Release:6.06
update-manager-core_0.56
+
+ TEST CASE (with powerpc):
+ 1. use a sparc dapper
+ 2. run "sudo do-release-upgrade -d"
+ 3. watch it fail because it can not fetch the required
This is not relevant for intrepid (closing the intrepid task therefore)
only for hardy.
** Changed in: update-manager (Ubuntu)
Status: New => Invalid
--
Getting upgrade prerequisites for system upgrade failed
https://bugs.launchpad.net/bugs/239458
You received this bug notification becaus
Thanks for your bugreport.
This is fixed in my bzr branch and I will do a upload with the fixed
update-manager to hardy-proposed.
** Changed in: update-manager (Ubuntu Hardy)
Importance: Undecided => Medium
Status: New => In Progress
--
Getting upgrade prerequisites for system upgrade
26 matches
Mail list logo
