severity 454975 important thanks On Sat, Dec 08, 2007 at 10:04:00PM +0100, Guido Guenther wrote: > Hi, > On Sat, Dec 08, 2007 at 07:57:36PM +0100, Kurt Roeckx wrote: > > On Sat, Dec 08, 2007 at 07:22:09PM +0100, Guido Guenther wrote: > > > On Sat, Dec 08, 2007 at 04:33:10PM +0100, Kurt Roeckx wrote: > > > > reopen 454975 > > > > notfixed 454975 0.2.0-2 > > > > thanks > > > > > > > > Hi, > > > > > > > > The .pc file had versioned Depends. Your package now has: > > > > Depends: libgnutls-dev, libgtk-vnc-1.0-0 (= 0.2.0-2), libgtk2.0-dev > > > > > > > > So it doesn't have the proper version requirements. > > > The versions in sid and lenny all match the requirements, so we don't > > > need a versioned dependency or am I missing something? > > > > That's no excuse for not adding that information. > Is this part of policy somewhere? You can't get the wrong dependencies > so what would this buy?
The upstream maintainer puts time into saying what version requirements there are. It's normal that you put those same version requirements into your Depends/Build Depends. The problem here is installing your package together with a version that's not high enough will cause problems. Even if upstream doesn't do it, it still makes sense to add them. This makes sure that people know what version requirements there are. This might be for instance be interesting for people who want to backport things. Note that in your Build-Depends you for instance have: libgnutls-dev (>= 1.6.3-1) I'm not sure where that version requirement comes from, but it probably means that you should have the same version requirement in the -dev package (and .pc file). And 1.6 for instance is not in stable/etch. Also note that a version requirement on libgtk2.0-dev isn't needed since the 2.0 is already in the package name. Anyway, I don't consider this RC anymore, so I've lowered the severity. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
