Re: bad archive handling (was: Re: GNOME 2.8 on ia64 completely hosed?)
On Tue, Nov 30, 2004 at 11:46:57AM +0100, Andreas Barth wrote:
> * Martin-Éric Racine (q-funk@iki.fi) [041130 11:25]:
> > That is a flaw in the way the archive is handled. Instead of accepting sources
> > _only_ and starting the build for all architectures simultaneously, the archive
> > immediately installs whichever architecture was used for the developer's build,
> > which puts all other architectures behind, until someone got around signing and
> > installing the build for each architecture manually and that sometimes can take
> > days, on less popular architectures with fewer Build Masters monitoring the job.
> >
> > In other words, the current way of uploading things ain't working. Let's fix it.
>
> The problem is a bit different: E.g. gnome consists of arch-all and
> arch-any packages. Currently, as soon as the arch-all package is
> uploaded, it is installed for all architectures. The solution would be
> to install it only for the architectures where also an arch-any package
> has been installed - and you need to get wise if the package has only
> arch-all packages or not.
No the real solution to this is to have the archive software accept multiple
copies of a same package, and not remove the older arch:all packages when
there are still arch:any package from the same source package in the archive.
Ex: foo is arch: all, bar is arch: any, both come from the foo source package.
foo 2 is uploaded on powerpc, all arches autobuilder are a bit laggy or
whatever, and a number of them miss that days dinstall or whatever. The next
day, foo 2 is in the archive, and bar 2 for the arches that made it, and bar 1
for the others. If there is a strict dependency between arch and foo, the
package is uninstallable on all arches that didn't make it, which is something
which can take quite some time depending on the autobuilder and the
availability of the maintainer. The correct solution would be to keep foo 1 in
the archive until all autobuilders have catched up, and there is no bar 1 in
the archive anymore.
> (However, it has mostly been solved now, as package are built from
> incoming, so if the upload does not happen to near to cron.daily time,
> it mostly works.)
This is a recurring problem though.
Friendly,
Sven Luther
Reply to: