[maemo-developers] Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
From: Ed Bartosh eduard.bartosh at nokia.comDate: Tue Jul 1 11:10:51 EEST 2008
- Previous message: Wiki page of the day: "USB networking" and "USB networking with Debian"
- Next message: Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2008-06-30 at 22:58 +0200, ext Thomas Schmidt wrote: > Hi, > > I finally managed to build Gnumeric in the diablo autobuilder, but the > package itself is not installable on Diablo because the autobuilder > picked up the latest version of libglade2-dev from the extras(-devel) > repository (version 1:2.6.2-1indt1). This causes a dependency on > libglade2-0 (>= 1:2.6.2-1indt1) in the binary package. > > The package that presumably will be used for updating the tablets to the > next ITOS version, osso-software-version-rx[34]4 depends on fixed > versions of all pre-installed libraries, in this case libglade2-0 > (=1:2.4.0-1osso2). > > The application-manager now of course refuses to install the gnumeric > package because this would mean that libglade2-0 would have to be > updated, this itself would at least work in red-pill-mode, but the next > step is that updating libglade2-0 would implicitly cause the removal of > osso-software-version-rx[34]4, which is not supported by the application > manager and would be most likely a very, very bad idea as it would break > updates to the next ITOS. > > So what can be done to fix this situation!? > The obvious way is to ask libglade mainteiners to fix this issue. They can ask Niels to remove libglade from repo and rebuild all dependent packages. I don't see this as a huge problem, rather as business as usual for repository mainteiners. We just need to fix this and move on. > The only idea i have is to remove all libraries and packages whose > installation conflicts with osso-software-version-rx[34]4 from > (diablo)-extras(-devel) and reject further uploads of such packages > before they get into extras-devel and cause such breakage. > If community would decide to introduce some checks into builder we can do that. I already have 2 candidates - check for categories and this one. > btw: Do not get me wrong, i generally like the autobuilder and the > concept of source-only uploads, it is working mostly well, but it has a > few rough edges. ;-) > Well, many things have rough edges :) Repository full of not buildable packages without sources is much worse than this issue, IMHO. Regards, --- Ed
- Previous message: Wiki page of the day: "USB networking" and "USB networking with Debian"
- Next message: Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]