Package: dpkg-dev
Version: 1.14.23
Severity: normal
I've just found that if I pass '-v0' to dpkg-buildpackage (meaning 'include
changelog since version 0'), then -v0 parameter is not passed to
dpkg-genchanges.
This is caused by the line
if ($since) { push @change_opts, "-v$since" }
because if $
> On Tue, Jan 24, 2006 at 06:43:02PM +0300, Nikita V. Youshchenko wrote:
> > dpkg-shlibdeps calls ldd, which will just fail if LD_LIBRARY_PATH
> > won't point to directories with local libraries.
>
> That's not true. ldd will just happily print "libfoo.so.1 =&g
> On Tue, Jan 24, 2006 at 06:05:43PM +0300, Nikita V. Youshchenko wrote:
> > > On Sun, Jan 22, 2006 at 10:14:16PM +0100, Frank Lichtenheld wrote:
> > > Comment to myself: The current patch probably breaks dh_shlibdeps
> > > -l option because it doesn't
> On Sun, Jan 22, 2006 at 10:14:16PM +0100, Frank Lichtenheld wrote:
> > I've implemented this option. Patch and new script (since the patch is
> > garbled with a little code clean-up I did while going through the
> > script) are attached.
> >
> > Comments and/or testing welcome.
>
> Comment to my
Hello people.
> > > objdump isn't a solution either, while it sometimes can read the
> > > other shared library, it doesn't provide the linker search patch
> > > which is of critical importance to get this stuff right.
> >
> > Hmm...
> > But what for is that search path?
> > As far as I understand
> On Sun, Dec 04, 2005 at 12:42:40AM +0300, Nikita V. Youshchenko wrote:
> > Devscripts may handle this situation by just picking not
> > $package_$version_$arch.changes, but instead find the file that
> > matches $package_$version_*.changes pattern.
> > In one of the
> I tried to reproduce the situation where 'source+arch' appears, but
> failed.
>
> And, as far as I can read the code, dpkg-cross version of
> dpkg-buildpackage should not do this.
>
> First, before doing any .changes processing, it checks if there are
> exactly two files that match pattern ${pack
Hi,
> > > If dpkg-cross is installed, it provides it's own dpkg-buildpackage,
> > > which potentially replaces the *_${arch}.changes file with
> > > *_source+${arch}.changes. When debuild calls helpers like lintian or
> > > debsign, these will fail because debuild assumes the
> > > *_${arch}.chang
> On Sat, Aug 20, 2005 at 11:32:07PM +0400, Nikita V. Youshchenko wrote:
> > > Package: dpkg-cross, devscripts, dpkg-dev
> > > Severity: normal
> > >
> > > If dpkg-cross is installed, it provides it's own dpkg-buildpackage,
> > > which
> objdump isn't a solution either, while it sometimes can read the other
> shared library, it doesn't provide the linker search patch which is of
> critical importance to get this stuff right.
Hmm...
But what for is that search path?
As far as I understand, dpkg-shlibdeps should just get NEEDED so
> Package: dpkg-cross, devscripts, dpkg-dev
> Severity: normal
>
> If dpkg-cross is installed, it provides it's own dpkg-buildpackage,
> which potentially replaces the *_${arch}.changes file with
> *_source+${arch}.changes. When debuild calls helpers like lintian or
> debsign, these will fail beca
11 matches
Mail list logo
