Re: libwww0 dependency problem on new architecture

[Lennert Buytenhek <buytenh@wantstofly.org>]

On Sat, Aug 27, 2005 at 10:15:36PM +0200, Lennert Buytenhek wrote:

> While trying to bootstrap debian sarge for a new architecture*, I'm
> having some problems while building the w3c-libwww package.
> 
> In short, the regular sarge arm libwww0 package has the following
> control directives:
> 	Depends: libc6 (>= 2.3.2-1), libgcc1 (>= 1:3.3.1-1), zlib1g (>= 1:1.1.4)
> 	Conflicts: libwww-ssl0
> 
> But the version that I get when I do dpkg-buildpackage ends up with
> the following directives:
> 	Depends: libc6 (>= 2.3.2.ds1-21), libwww-ssl0 (>= 5.4.0), zlib1g (>= 1:1.2.1)
> 	Conflicts: libwww-ssl0
> 
> For one, my package doesn't depend on libgcc1 (why?), but the more
> serious problem is that when I build the package, it both depends on
> and conflicts with libwww-ssl0!

Actually, if I try to rebuild sarge w3c-libwww on a clean sarge
install, I also get the depends+conflicts overlap:

	Depends: libc6 (>= 2.3.2.ds1-21), libwww-ssl0 (>= 5.4.0), zlib1g (>= 1:1.2.1)
	Conflicts: libwww-ssl0

Is this a package bug?


cheers,
Lennert