>
> Should we ask Craig Small <[EMAIL PROTECTED]> to sync those .ex files with
> Lintian ?
>
actually he should sync them with debhelper.
>
> Should we ask Craig Small <[EMAIL PROTECTED]> to sync those .ex files with
> Lintian ?
>
actually he should sync them with debhelper.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote:
> >
> >> This is no different from working with a bunch of coders and everyone
> >> agreeing
> >> on a common code formatting.
> >
> > Talk to the maintainer of debhelper ?
> >
>
> dh_make is NOT maintained by Joey Hess, the d
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote:
> >
> >> This is no different from working with a bunch of coders and everyone
> >> agreeing
> >> on a common code formatting.
> >
> > Talk to the maintainer of debhelper ?
> >
>
> dh_make is NOT maintained by Joey Hess, the
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote:
> > Talk to the maintainer of debhelper ?
>
> dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has
> nothing to do with it.
Write to [EMAIL PROTECTED] or file a bug against it.
--
Christian Surchi |
>
>> This is no different from working with a bunch of coders and everyone
>> agreeing
>> on a common code formatting.
>
> Talk to the maintainer of debhelper ?
>
dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has
nothing to do with it.
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote:
> > Talk to the maintainer of debhelper ?
>
> dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has
> nothing to do with it.
Write to [EMAIL PROTECTED] or file a bug against it.
--
Christian Surchi |
>
>> This is no different from working with a bunch of coders and everyone
>> agreeing
>> on a common code formatting.
>
> Talk to the maintainer of debhelper ?
>
dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has
nothing to do with it.
--
To UNSUBSCRIBE, email to
On Thu, Nov 01, 2001 at 10:56:25AM -0500, Steve M. Robbins wrote:
> On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote:
> > Hi,
> >
> > I'm building my first packages with shared library.
> >
> > This is what my postinst states:
> >
> >
> > case "$1" in
> > configure)
> >
On Thu, Nov 01, 2001 at 08:18:20PM -0800, Sean 'Shaleh' Perry wrote:
>
> On 01-Nov-2001 Eric Van Buggenhaut wrote:
> > Hi,
> >
> > I'm building my first packages with shared library.
> >
> > This is what my postinst states:
>
> Lintian is a collection of stupid shell scripts. It tries to catch
On Thu, Nov 01, 2001 at 10:56:25AM -0500, Steve M. Robbins wrote:
> On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote:
> > Hi,
> >
> > I'm building my first packages with shared library.
> >
> > This is what my postinst states:
> >
> >
> > case "$1" in
> > configure)
> >
On Thu, Nov 01, 2001 at 08:18:20PM -0800, Sean 'Shaleh' Perry wrote:
>
> On 01-Nov-2001 Eric Van Buggenhaut wrote:
> > Hi,
> >
> > I'm building my first packages with shared library.
> >
> > This is what my postinst states:
>
> Lintian is a collection of stupid shell scripts. It tries to catc
On 01-Nov-2001 Eric Van Buggenhaut wrote:
> Hi,
>
> I'm building my first packages with shared library.
>
> This is what my postinst states:
Lintian is a collection of stupid shell scripts. It tries to catch thr common
cases and does a pretty good job. My best suggestion is to write your code
On 01-Nov-2001 Eric Van Buggenhaut wrote:
> Hi,
>
> I'm building my first packages with shared library.
>
> This is what my postinst states:
Lintian is a collection of stupid shell scripts. It tries to catch thr common
cases and does a pretty good job. My best suggestion is to write your cod
On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote:
> > case "$1" in
> > configure)
> > ldconfig
>
>
> > W: iiwusynth: postinst-unsafe-ldconfig
>
> > Sorry, I don't get it !
>
> Lintian is cannot parse shell scripts, it checks for some common
> variants, and warns if your ver
> case "$1" in
> configure)
> ldconfig
> W: iiwusynth: postinst-unsafe-ldconfig
> Sorry, I don't get it !
Lintian is cannot parse shell scripts, it checks for some common
variants, and warns if your version didn't match what it expected.
Since you do the right thing, just ignore this
On Thu, Nov 01, 2001 at 04:18:46PM +0100, Christian Surchi wrote:
> On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote:
> > > case "$1" in
> > > configure)
> > > ldconfig
> >
> >
> > > W: iiwusynth: postinst-unsafe-ldconfig
> >
> > > Sorry, I don't get it !
> >
> > Lintian is
On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote:
> Hi,
>
> I'm building my first packages with shared library.
>
> This is what my postinst states:
>
>
> case "$1" in
> configure)
> ldconfig
> ;;
>
> abort-upgrade|abort-remove|abort-deconfigure)
>
> ;;
Hi,
I'm building my first packages with shared library.
This is what my postinst states:
case "$1" in
configure)
ldconfig
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
Still lintian complains ab
On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote:
> Hi,
>
> I'm building my first packages with shared library.
>
> This is what my postinst states:
>
>
> case "$1" in
> configure)
> ldconfig
> ;;
>
> abort-upgrade|abort-remove|abort-deconfigure)
>
> ;;
On Thu, Nov 01, 2001 at 04:18:46PM +0100, Christian Surchi wrote:
> On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote:
> > > case "$1" in
> > > configure)
> > > ldconfig
> >
> >
> > > W: iiwusynth: postinst-unsafe-ldconfig
> >
> > > Sorry, I don't get it !
> >
> > Lintian i
On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote:
> > case "$1" in
> > configure)
> > ldconfig
>
>
> > W: iiwusynth: postinst-unsafe-ldconfig
>
> > Sorry, I don't get it !
>
> Lintian is cannot parse shell scripts, it checks for some common
> variants, and warns if your ve
> case "$1" in
> configure)
> ldconfig
> W: iiwusynth: postinst-unsafe-ldconfig
> Sorry, I don't get it !
Lintian is cannot parse shell scripts, it checks for some common
variants, and warns if your version didn't match what it expected.
Since you do the right thing, just ignore this
Hi,
I'm building my first packages with shared library.
This is what my postinst states:
case "$1" in
configure)
ldconfig
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
Still lintian complains a
On Tue, Sep 04, 2001 at 01:53:31PM +0200, Domenico Andreoli wrote:
> On Mon, Sep 03, 2001 at 01:22:01PM -0500, Steve Langasek wrote:
> > On Mon, 3 Sep 2001, Drew Parsons wrote:
> >
> [...]
> >
> > Check the contents of the postinst script in the binary package. The
> > #DEBHELPER# line gets repl
On Mon, Sep 03, 2001 at 01:22:01PM -0500, Steve Langasek wrote:
> On Mon, 3 Sep 2001, Drew Parsons wrote:
>
[...]
>
> Check the contents of the postinst script in the binary package. The
> #DEBHELPER# line gets replaced with debhelper hints based on the various dh_*
> commands you've called, and
On Tue, Sep 04, 2001 at 01:53:31PM +0200, Domenico Andreoli wrote:
> On Mon, Sep 03, 2001 at 01:22:01PM -0500, Steve Langasek wrote:
> > On Mon, 3 Sep 2001, Drew Parsons wrote:
> >
> [...]
> >
> > Check the contents of the postinst script in the binary package. The
> > #DEBHELPER# line gets rep
On Mon, Sep 03, 2001 at 01:22:01PM -0500, Steve Langasek wrote:
> On Mon, 3 Sep 2001, Drew Parsons wrote:
>
[...]
>
> Check the contents of the postinst script in the binary package. The
> #DEBHELPER# line gets replaced with debhelper hints based on the various dh_*
> commands you've called, an
On Mon, 3 Sep 2001, Drew Parsons wrote:
> W: meschach: postinst-has-useless-call-to-ldconfig
> (and do I need to put dpkg-shlibdeps in debian/rules somewhere? It seems
> fine without it)
> My postinst is:
> #!/bin/sh
> # meschach.postinst, runs ldconfig
> set -e
> case "$1" in
>configu
On Mon, 3 Sep 2001, Drew Parsons wrote:
> W: meschach: postinst-has-useless-call-to-ldconfig
> (and do I need to put dpkg-shlibdeps in debian/rules somewhere? It seems
> fine without it)
> My postinst is:
> #!/bin/sh
> # meschach.postinst, runs ldconfig
> set -e
> case "$1" in
>config
On Mon, Sep 03, 2001 at 02:08:00PM +0200, Domenico Andreoli wrote:
> >
> > But I've noticed just now as I prepare a new upload that lintain complains,
> > saying,
> >
> > W: meschach: postinst-has-useless-call-to-ldconfig
> >
>
> anyway there was a bug (#109721) and lintian reported this warnin
On Mon, Sep 03, 2001 at 08:44:40PM +1000, Drew Parsons wrote:
> My package meschach has a shared library. Previously, I called ldconfig in
> the postinst to get the library registered (it was made mandatory in Policy
> 2.4.1.0).
>
> But I've noticed just now as I prepare a new upload that lintain
On Mon, Sep 03, 2001 at 02:08:00PM +0200, Domenico Andreoli wrote:
> >
> > But I've noticed just now as I prepare a new upload that lintain complains,
> > saying,
> >
> > W: meschach: postinst-has-useless-call-to-ldconfig
> >
>
> anyway there was a bug (#109721) and lintian reported this warni
My package meschach has a shared library. Previously, I called ldconfig in
the postinst to get the library registered (it was made mandatory in Policy
2.4.1.0).
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach: postinst-has-useless-call-to-ldconfig
On Mon, Sep 03, 2001 at 08:44:40PM +1000, Drew Parsons wrote:
> My package meschach has a shared library. Previously, I called ldconfig in
> the postinst to get the library registered (it was made mandatory in Policy
> 2.4.1.0).
>
> But I've noticed just now as I prepare a new upload that lintai
My package meschach has a shared library. Previously, I called ldconfig in
the postinst to get the library registered (it was made mandatory in Policy
2.4.1.0).
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach: postinst-has-useless-call-to-ldconfig
36 matches
Mail list logo
