Dist-upgrade Edgy-->Feisty has incorrect URL

[Daniel O'Donnell]

Binary package hint: update-manager

Running Update manager this morning for the Feisty update, I get an error message:

Error during update

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

Failed to fetch http://archive.ubuntustudio.org/ubuntustudio/dists/edgy/main/binary-i386/Packages.gz 404 Not Found
Failed to fetch http://archive.ubuntustudio.org/ubuntustudio/dists/edgy/main/source/Sources.gz 404 Not Found

When I check these URLs, it looks like there is no //edgy/ directory, only //feisty/. Could this be a typo somewhere?

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full contents of your '/etc/apt/sources.list' file? Thanks in advance.

[Daniel O'Donnell (daniel-odonnell)]

See attached.

[Daniel O'Donnell (daniel-odonnell)]

Done.

On Thu, 2007-04-19 at 17:42 +0000, Brian Murray wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add the full contents of your
> '/etc/apt/sources.list' file? Thanks in advance.
>
> ** Changed in: update-manager (Ubuntu)
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
--
Daniel Paul O'Donnell, PhD
Department Chair and Associate Professor of English
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Chair, Text Encoding Initiative http://www.tei-c.org/

Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox [phone]
Fax [phone]
Email: <email address hidden>
WWW: http://people.uleth.ca/~daniel.odonnell/

[Andrew Hunter (rexbron)]

Rejected as Ubuntu Studio has not released for fiesty yet. It should be standard practise to remove _ALL_ non-offical repos before dist-upgrading.

[C.Kontros (coryisatm)]

Those repos do not exist.

[Andrew Hunter (rexbron)]

Actually I was mistaken, as all the ubuntu studio meta packages are in fiesty and are installable. It is the art packages that are not.

[Joe Jaxx (joejaxx)]

The reason this bug was rejected was because the ubuntustudio-meta package nor its children do not set anything in the sources.list file.

[Daniel O'Donnell (daniel-odonnell)]

Should this not be added to the documentation or automated? It seems to
me that it is a fatal flaw if it isn't advertised or documented.
Certainly I didn't see the answer and I'm not a complete newbie.

-dan

On Thu, 2007-04-19 at 20:06 +0000, Andrew Hunter wrote:
> Rejected as Ubuntu Studio has not released for fiesty yet. It should be
> standard practise to remove _ALL_ non-offical repos before dist-
> upgrading.
>
--
Daniel Paul O'Donnell, PhD
Department Chair and Associate Professor of English
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Chair, Text Encoding Initiative http://www.tei-c.org/

Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox [phone]
Fax [phone]
Email: <email address hidden>
WWW: http://people.uleth.ca/~daniel.odonnell/

[C.Kontros (coryisatm)]

In the end its moot as the package hasnt been released and the entries your sources.lits entries dont exist.

[Daniel O'Donnell (daniel-odonnell)]

On Thu, 2007-04-19 at 22:18 +0000, C.Kontros wrote:
> In the end its moot as the package hasnt been released and the entries
> your sources.lits entries dont exist.

I don't mean this specific URL, I mean the necessity of stripping your
sources.list to the bare minimum in order to do a dist. upgrade. Using a
big button on upgrade manager for "dist. upgrade" implies that you can
press it and get your dist. upgraded. In fact, if what I'm understanding
here is correct, you actually need to reduce your sources.list to an
official minimum.

This is not a major problem for anybody with experience (though the need
to do so is not prominently documented at the same place you click on
the button or in the readme that pops up), but it is a command-line user
task that is unnecessary and might scare off novice users.

My proposal for the short term is that a prominent note be added to the
pop up window that appears after you select dist. upgrade from the
upgrade manager asking you to comment out anything but the official
repositories.

For the longer term, why not build and use a temporary sources.list for
the upgrade? This would make the whole process invisible to the user and
is well worth doing.

-dan

>
--
Daniel Paul O'Donnell, PhD
Department Chair and Associate Professor of English
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Chair, Text Encoding Initiative http://www.tei-c.org/

Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox [phone]
Fax [phone]
Email: <email address hidden>
WWW: http://people.uleth.ca/~daniel.odonnell/

[Andrew Hunter (rexbron)]

I think it is reasonable to expect a user to remove anything they added to something like the sources.list if they are competent enough to put it their in the first place.

[Daniel O'Donnell (daniel-odonnell)]

On Fri, 2007-20-04 at 14:02 +0000, Andrew Hunter wrote:
> I think it is reasonable to expect a user to remove anything they added
> to something like the sources.list if they are competent enough to put
> it their in the first place.

Yes and no. Automatix adds a fair bit, for example, without real user
intervention. Increasingly we are seeing scripts--designed to make
Ubuntu easier for non-specialists to use--that automatically modify
configuration files like sources.list.

In my view this is to be applauded--the most important part of "Just
Works" is that users shouldn't have to involve themselves with
configuration files to do basic and predictable tasks.

This is a pan-Ubuntu approach--see the various discussions we've been
having about the xorg configuration file and wide-screen monitors. It is
not hard to produce a mod line and insert it in xorg.conf--but you
shouldn't have to.

It is especially important that this be done at upgrade and
installation, IMO. This is the whole point behind the automatic notice
in the upgrade manager that a new distribution is available. It is also
not hard to type apt-get dist-upgrade at a console: but we use update
manager because it is more user oriented and the task is extremely
predictable.