Bug#378077: Bug#379077 closed by Oleksandr Moskalenko <malex@debian.org> (Bug#379077: fixed in scribus-ng 1.3.3.2.dfsg-2)
- To: Philip Hands <phil@hands.com>
- Cc: 378077@bugs.debian.org
- Subject: Bug#378077: Bug#379077 closed by Oleksandr Moskalenko <malex@debian.org> (Bug#379077: fixed in scribus-ng 1.3.3.2.dfsg-2)
- From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
- Date: Sat, 29 Jul 2006 11:34:36 +0100
- Message-id: <[🔎] 20060729103436.GR26034@lkcl.net>
- Reply-to: Luke Kenneth Casson Leighton <lkcl@lkcl.net>, 378077@bugs.debian.org
- In-reply-to: <44CB184A.90406@hands.com>
- References: <E1G6ZVg-0005eW-Le@spohr.debian.org> <E1G3jrw-00074D-N2@lkcl.net> <handler.379077.D379077.115412115728313.notifdone@bugs.debian.org> <20060728233859.GP26034@lkcl.net> <44CABBA6.90608@hands.com> <20060729024909.GQ26034@lkcl.net> <44CB184A.90406@hands.com>
On Sat, Jul 29, 2006 at 09:11:54AM +0100, Philip Hands wrote:
> Luke Kenneth Casson Leighton wrote:
> > On Sat, Jul 29, 2006 at 02:36:38AM +0100, Philip Hands wrote:
> >
> >>Luke Kenneth Casson Leighton wrote:
> >>
> >>>um... i just checked the scribus-ng/debian/depend file,
> >>>for scribus-ng-1.3.3.2.dfsg/debian/control
> >>>
> >>>it doesn't have liblcms1 (>=1.13) as a dependency.
> >>>
> >>>is there something about the way that dependencies work that i don't
> >>>know about (quite likely) - are Depends auto-generated from their
> >>>-dev build-depends?
> >>
> >>The ${shlibs:Depends} bit is magic that gets replaced by all the shared
> >>libraries that you built the package against, when you built it.
> >
> >
> > yaay!
> >
> >
> >>Is that the answer to your question?
> >
> >
> > yup!
> >
> > ok - how would it be possible for that to end up with liblcms1.08
> > as the "Depends", but still have liblcms1.13 in the -dev thing?
> >
> > somehow, scribus-ng-1.3.3.2-dfsg1 has ended up with build-dep of
> > 1.13-dev but a Depend of 1.08.
>
> Well, the build-dep is set by the maintainer, whereas the Depend is set
> automatically.
>
> I know there was talk of making the auto-detection somehow determine the
> actual dependencies by analysing the functions being called by the program,
> and then working out the minimum library version that provides those (in an
> attempt to fix the problem where a program that would happily work with
> version 1 of a library, ends up with a dependency on version 100, just
> because the maintainer has that version of the -dev package installed) but
> I thought that was still science fiction.
sounds like complete twaddle, to me :)
... kick out of a build because the function's missing, yes.
try to install versions of a library to detect the required minimum?
i'll see it when i believe it.
> Does the dependency actualy work?
nope.
> Can you run scribus with 1.08?
nope - because there's a function missing.
how the heck he managed to get it to work i really don't know.
i think he built it on sarge or something.
> To me it looks like someone has managed to force the package to build when
> they had -dev.1.08 installed, presumably by running the rules file
> directly, rather than using debuild or some such. If it all works then the
> build-dep is a bug. If it doesn't, then it needs rebuilding.
a rebuild still shows Depends: liblcms1 >= 1.08
which is why i'm complaining to this guy because he doesn't understand
that there's a problem.
> I suppose you could check some of these theories by grabbing the source,
> and building it yourself.
yehh, i've already installed liblcms1.15 to get working with the
package, otherwise i would.
and i need a working scribus-ng more than i need the maintainer to
understand the problem.
l.
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
Reply to: