wrong repo

[gianni]

Binary package hint: update-manager

updating to 10.10, the process stops.

Error during update

A problem occurred during the update. This is usually some sort of network problem, please check your network connection and retry.

W:Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/maverick/main/binary-amd64/Packages.gz 404 Not Found
, W:Failed .... etc.

indeed in ports/ubuntu there are no amd64 neither i386 repos, only this:

 binary-armel/ 09-Sep-2010 12:19 -
 binary-ia64/ 09-Sep-2010 12:19 -
 binary-powerpc/ 09-Sep-2010 12:19 -
 binary-sparc/ 09-Sep-2010 12:19 -
 debian-installer/ 30-Apr-2010 17:01 -
 dist-upgrader-all/ 03-Sep-2010 14:03 -
 i18n/ 22-Jun-2010 18:03 -
 installer-armel/ 06-Sep-2010 02:03 -
 installer-powerpc/ 05-Sep-2010 22:03 -
 source/ 09-Sep-2010 12:19 -

deleting these links in sources.list doens't help, they are reactiveted by the upgrade process again

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager-core 1:0.134.10
ProcVersionSignature: Ubuntu 2.6.32-25.43-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 9 13:34:48 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: update-manager

[dazza5000 (darran-kelinske)]

Gianni,

Thank you for reporting this bug, does the computer you are upgrading have a working network configured and in use while you are attempting to upgrade?

Darran

[gianni (gbarberi)]

Sure it has, and downloads the 1' part of upgrade, as I stated, the source
generated by the process points to a nonexistent path

On Sep 9, 2010 4:05 PM, "drizzle" <email address hidden> wrote:

Gianni,

Thank you for reporting this bug, does the computer you are upgrading
have a working network configured and in use while you are attempting to
upgrade?

Darran

--
wrong repo
https://bugs.launchpad.net/bugs/633959
You received this bug notification because yo...

[Robert Roth (evfool)]

Thank you for reporting this bug to Ubuntu. Maverick reached EOL on 10 April, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[gianni (gbarberi)]

did you notice the date of my post ???

On Wed, Apr 11, 2012 at 9:50 PM, Robert Roth <email address hidden> wrote:

> Thank you for reporting this bug to Ubuntu. Maverick reached EOL on 10
> April, 2012.
> Please see this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> I've tried recreating this bug with Oneiric and was unable to, given the
> information you've provided. Please either a) upgrade and test or b)
> increase the verbosity of the steps to recreate it so we can try again.
>
> Please feel free to report any other bugs you may find.
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/633959
>
> Title:
> wrong repo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/633959/+subscriptions
>

[Robert Roth (evfool)]

Yes, it is really old, and that is why I'm asking, to find out if the bug has been fixed, resolved by an update, or if it still exists, to get some more information to be able to fix it.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[gianni (gbarberi)]

Ah, your email name explains a lot ;-)
On Apr 12, 2012 8:15 AM, "Robert Roth" <email address hidden> wrote:

> Yes, it is really old, and that is why I'm asking, to find out if the bug
> has been fixed, resolved by an update, or if it still exists, to get some
> more information to be able to fix it.
> ---
> Ubuntu Bug Squad volunteer triager
> http://wiki.ubuntu.com/BugSquad
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/633959
>
> Title:
> wrong repo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/633959/+subscriptions
>

[Robert Roth (evfool)]

This bug report is being closed due to your comments regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad