On Thu, Jan 14, 2010 at 05:39:03PM +0100, Jens Seidel wrote: > On Thu, Jan 14, 2010 at 01:06:01PM +0100, Martin Jansa wrote: > > On Thu, Jan 14, 2010 at 12:38:03PM +0100, Jens Seidel wrote: > > > probably it is already known but there is a file conflict among libbz2-1 > > > and > > > bzip2. I got after opkg upgrade (SHR unstable): > > > > > > Collected errors: > > > * Package busybox-mountall wants to install file /etc/default/mountall > > > But that file is already provided by package * > > > util-linux-ng-mountall > > > * Package libbz2-1 wants to install file /usr/lib/libbz2.so.1 > > > But that file is already provided by package * bzip2 > > > * Package libbz2-1 wants to install file /usr/lib/libbz2.so.1.0.5 > > > But that file is already provided by package * bzip2 > > > * Package libbz2-1 wants to install file /usr/lib/libbz2.so.1 > > > But that file is already provided by package * bzip2 > > > * Package libbz2-1 wants to install file /usr/lib/libbz2.so.1.0.5 > > > But that file is already provided by package * bzip2 > > > > Please write also package versions in bug reports :) > > > > because mine works ok > > > > Reinstalling bzip2 (1.0.5-r2.4) on root... > > Reinstalling libbz2-1 (1.0.5-r2.4) on root... > > You're of course right! I noticed missing versions numbers after I send the > mail too :-)) > > Maybe it would be a good idea to patch opkg to report it in the output I > copied.
Yeah, it could be usefull.. > From the install log: > > <quote> > Installing libbz2-1 (1.0.5-r2.4) to root... > Upgrading bzip2 on root from 1.0.5-r0.4 to 1.0.5-r2.4... > Downloading > http://build.shr-project.org/shr-unstable/ipk//armv4t/bzip2_1.0.5-r2.4_armv4t.ipk > Installing libbz2-1 (1.0.5-r2.4) to root... > </quote> > So it looks like libbz2-1 1.0.5-r2.4 gets installed the first time and bzip2 > got upgraded from 1.0.5-r0.4 to 1.0.5-r2.4. Yeah it's what I sort of expected.. libbz2 is dependency of bzip2 and opkg wants to upgrade it first.. but in that time there is still bzip2 with libbz included on filesystem. Not sure how to fix this properly :/. > Is there no check in OpenEmbedded to ensure that file conflicts cannot > happen? There is such a check for Debian ... I think no.. as all packages are just prepared in tmp dir and bitbake cannot check all .opks in feed (especially as you can have there some older version which is known to be incompatible with new .opk build). Regards, -- uin:136542059 jid:[email protected] Jansa Martin sip:[email protected] JaMa _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
