>
> second, i get the lintian warning:
> W: modlogan: binary-or-shlib-defines-rpath ./usr/bin/modlogan
> /usr/lib/modlogan
>
rpath encodes the entire path to a lib in the binary. This would prevent it
from being used on a system which had the lib somewhere else.
>
> second, i get the lintian warning:
> W: modlogan: binary-or-shlib-defines-rpath ./usr/bin/modlogan
> /usr/lib/modlogan
>
rpath encodes the entire path to a lib in the binary. This would prevent it
from being used on a system which had the lib somewhere else.
--
To UNSUBSCRIBE, email to
hi,
first, dpkg-shlibdeps checks a few shared objects files which
resides in the packages own subdir in /usr/lib, since they are
just some sort of plugins, but shlibdeps complains:
dpkg-shlibdeps: warning: format of libmla_mdata_netmask.so not
recognized
and this without about a dozen of files. w
[cc and reply-to more appropriate list]
Richard Atterer <[EMAIL PROTECTED]> writes:
> On Sat, Sep 15, 2001 at 10:42:59AM +0200, Robert Bihlmeyer wrote:
[doc-html-w3]
> > That package is in non-free. IIRC the issue is that you can't modify
> > the standards. Which is somewhat understandable, but s
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> > The last xstr upload being some 2+ weeks ago, perhaps the build log
> > has expired? No bug report ... maybe it fell through the cracks?
> sorry, but what does this sentence mean?
If something is compiled successfully, it is uploaded the next day
On Sun, Sep 16, 2001 at 09:11:24PM +0300, Baruch Even wrote:
> > (taken from debian/rules)
> > ---
> > clean:
> > rm -f eroaster Makefile configure.cache configure.log
> > configure.status constants.py ecat.py
> You wrote configure.status and configure.cache where the files are
> config.st
On Sun, Sep 16, 2001 at 07:32:19PM +0200, Martin Butterweck wrote:
> hi,
> lintian gives me the following errormessage:
> ---
> mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
> E: eroaster source: autoconf-generated-file-in-source config.status
> N:
> N: Leaving config.cache/status causes autobuild
* Martin Butterweck <[EMAIL PROTECTED]> [010916 20:56]:
> hi,
> lintian gives me the following errormessage:
> ---
> mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
> E: eroaster source: autoconf-generated-file-in-source config.status
> E: eroaster source: autoconf-generated-file-in-source config.cach
hi,
first, dpkg-shlibdeps checks a few shared objects files which
resides in the packages own subdir in /usr/lib, since they are
just some sort of plugins, but shlibdeps complains:
dpkg-shlibdeps: warning: format of libmla_mdata_netmask.so not
recognized
and this without about a dozen of files.
[cc and reply-to more appropriate list]
Richard Atterer <[EMAIL PROTECTED]> writes:
> On Sat, Sep 15, 2001 at 10:42:59AM +0200, Robert Bihlmeyer wrote:
[doc-html-w3]
> > That package is in non-free. IIRC the issue is that you can't modify
> > the standards. Which is somewhat understandable, but
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> > The last xstr upload being some 2+ weeks ago, perhaps the build log
> > has expired? No bug report ... maybe it fell through the cracks?
> sorry, but what does this sentence mean?
If something is compiled successfully, it is uploaded the next da
hi,
lintian gives me the following errormessage:
---
mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
E: eroaster source: autoconf-generated-file-in-source config.status
N:
N: Leaving config.cache/status causes autobuilders problems config.cache
N: and config.status are produced by GNU autoconf's c
On Sun, Sep 16, 2001 at 09:11:24PM +0300, Baruch Even wrote:
> > (taken from debian/rules)
> > ---
> > clean:
> > rm -f eroaster Makefile configure.cache configure.log
> > configure.status constants.py ecat.py
> You wrote configure.status and configure.cache where the files are
> config.s
On Sun, Sep 16, 2001 at 07:32:19PM +0200, Martin Butterweck wrote:
> hi,
> lintian gives me the following errormessage:
> ---
> mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
> E: eroaster source: autoconf-generated-file-in-source config.status
> N:
> N: Leaving config.cache/status causes autobuil
* Martin Butterweck <[EMAIL PROTECTED]> [010916 20:56]:
> hi,
> lintian gives me the following errormessage:
> ---
> mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
> E: eroaster source: autoconf-generated-file-in-source config.status
> E: eroaster source: autoconf-generated-file-in-source config.cac
hi,
lintian gives me the following errormessage:
---
mb:~/debian$lintian -i eroaster_2.0.11-1.dsc
E: eroaster source: autoconf-generated-file-in-source config.status
N:
N: Leaving config.cache/status causes autobuilders problems config.cache
N: and config.status are produced by GNU autoconf's
* Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [20010916 09:12]:
> > with a diff against the orig.tar.gz. Can I somehow re-upload the
> > orig.tar.gz for x.y when uploading x.y-2?
>
> No, unless the orig.tar.gz of the -1 version has been deleted for
> some reason,
On Sun, 16 Sep 2001, peter karlsson wrote:
> An NMU upload for a package that I am adopting was uplodad as if it was
> a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
I hate when people do that...
> with a diff against the orig.tar.gz. Can I somehow re-upload the
> orig.tar
* Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [20010916 09:12]:
> > with a diff against the orig.tar.gz. Can I somehow re-upload the
> > orig.tar.gz for x.y when uploading x.y-2?
>
> No, unless the orig.tar.gz of the -1 version has been deleted for
> some reason,
Hi!
An NMU upload for a package that I am adopting was uplodad as if it was
a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
with no diffs or orig.tar.gz. I wish to upload a new version, correct
with a diff against the orig.tar.gz. Can I somehow re-upload the
orig.tar.gz for x
On Sun, 16 Sep 2001, peter karlsson wrote:
> An NMU upload for a package that I am adopting was uplodad as if it was
> a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
I hate when people do that...
> with a diff against the orig.tar.gz. Can I somehow re-upload the
> orig.ta
Hi!
An NMU upload for a package that I am adopting was uplodad as if it was
a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
with no diffs or orig.tar.gz. I wish to upload a new version, correct
with a diff against the orig.tar.gz. Can I somehow re-upload the
orig.tar.gz for
22 matches
Mail list logo