This one time, at band camp, Matt Zimmerman said:
> Ah, I understand. This is presumably a bug in one of the underlying
> tools, then. Do you run aclocal/autoconf/automake during the build?
> If so, any one of the files pulled in by those tools could have
> changed. You can probably narrow it do
On Sun, Sep 21, 2003 at 08:15:37PM -0400, Stephen Gran wrote:
> Since it is not, I was wondering if others had seen this before.
> Building previous versions of this program (albeit with different
> versions of the various tools) did not produce this lintian warning.
> In fact this prompted me
This one time, at band camp, Frank Thomas said:
> I have the same problem with my KSetiSpy package and remove rpath with
> the chrpath program.
Ah, thank you. I will look into it. Maybe there is something going on
with the KDE build system?
--
-
This one time, at band camp, Matt Zimmerman said:
> On Sun, Sep 21, 2003 at 03:44:42PM -0400, Stephen Gran wrote:
>
> > 6) W: kcdlabel: binary-or-shlib-defines-rpath ./usr/bin/kcdlabel
> > /usr/X11R6/lib
> > [...]
> > It's 6 that bothers me. Is this some odd libtool oddity with X that can
> > be
This one time, at band camp, Matt Zimmerman said:
> Ah, I understand. This is presumably a bug in one of the underlying
> tools, then. Do you run aclocal/autoconf/automake during the build?
> If so, any one of the files pulled in by those tools could have
> changed. You can probably narrow it do
Hi!
Stephen Gran wrote:
> I am having a strange issue with disabling rpath in one of my packages.
> ./configure is run with --disable-rpath, but linitan still gives me:
[..]
I have the same problem with my KSetiSpy package and remove rpath with the
chrpath program.
-Frank
On Sun, Sep 21, 2003 at 03:44:42PM -0400, Stephen Gran wrote:
> 6) W: kcdlabel: binary-or-shlib-defines-rpath ./usr/bin/kcdlabel
> /usr/X11R6/lib
> [...]
> It's 6 that bothers me. Is this some odd libtool oddity with X that can
> be ignored, or is it something real that I should worry about? I
On Sun, Sep 21, 2003 at 08:15:37PM -0400, Stephen Gran wrote:
> Since it is not, I was wondering if others had seen this before.
> Building previous versions of this program (albeit with different
> versions of the various tools) did not produce this lintian warning.
> In fact this prompted me
This one time, at band camp, Frank Thomas said:
> I have the same problem with my KSetiSpy package and remove rpath with
> the chrpath program.
Ah, thank you. I will look into it. Maybe there is something going on
with the KDE build system?
--
-
This one time, at band camp, Matt Zimmerman said:
> On Sun, Sep 21, 2003 at 03:44:42PM -0400, Stephen Gran wrote:
>
> > 6) W: kcdlabel: binary-or-shlib-defines-rpath ./usr/bin/kcdlabel /usr/X11R6/lib
> > [...]
> > It's 6 that bothers me. Is this some odd libtool oddity with X that can
> > be igno
Hi!
Stephen Gran wrote:
> I am having a strange issue with disabling rpath in one of my packages.
> ./configure is run with --disable-rpath, but linitan still gives me:
[..]
I have the same problem with my KSetiSpy package and remove rpath with the
chrpath program.
-Frank
--
To UNSUBSCRIBE,
Andreas Metzler:
> You could conditionally move the existing configuration file in the
> preinst to the new location.
Thanks. I'm doing something similar with a non-conffile for another of
my packages, so I'll just copy the working code from that. I was just
unsure whether I was allowed to do it
On Sun, Sep 21, 2003 at 03:44:42PM -0400, Stephen Gran wrote:
> 6) W: kcdlabel: binary-or-shlib-defines-rpath ./usr/bin/kcdlabel /usr/X11R6/lib
> [...]
> It's 6 that bothers me. Is this some odd libtool oddity with X that can
> be ignored, or is it something real that I should worry about? I don
Hello all,
I am having a strange issue with disabling rpath in one of my packages.
./configure is run with --disable-rpath, but linitan still gives me:
1) W: kcdlabel source: newer-standards-version 3.6.1
2) W: kcdlabel source: configure-generated-file-in-source config.status
3) W: kcdlabel sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can someone describe quickly what the filter acutally does? I don't know
procmail and would like to add filters in kmail directly for this without
calling an external app for every mail.
Thanks.. Dominik.
Am Sonntag, 21. September 2003 03:24 schrie
Andreas Metzler:
> You could conditionally move the existing configuration file in the
> preinst to the new location.
Thanks. I'm doing something similar with a non-conffile for another of
my packages, so I'll just copy the working code from that. I was just
unsure whether I was allowed to do it
Hello all,
I am having a strange issue with disabling rpath in one of my packages.
./configure is run with --disable-rpath, but linitan still gives me:
1) W: kcdlabel source: newer-standards-version 3.6.1
2) W: kcdlabel source: configure-generated-file-in-source config.status
3) W: kcdlabel sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can someone describe quickly what the filter acutally does? I don't know
procmail and would like to add filters in kmail directly for this without
calling an external app for every mail.
Thanks.. Dominik.
Am Sonntag, 21. September 2003 03:24 schrie
On Sun, Sep 21, 2003 at 03:16:32PM +0100, Peter Karlsson wrote:
> A new version of a package that I maintain has changed the name of the
> default configuration file. I want to propagate this name change, but
> how do I handle it properly? AFAICT, I'm not allowed to touch conffiles
> in the maintai
Matthias Urlichs wrote:
> > As packages are normally upgraded through the life of a system I train
> > people to always say 'Y' to the replace a conffile question. Sure
> > this may leave the system in a generic and locally unworkable state.
>
> So why not "N"? That may leave the package, at wors
Hi!
A new version of a package that I maintain has changed the name of the
default configuration file. I want to propagate this name change, but
how do I handle it properly? AFAICT, I'm not allowed to touch conffiles
in the maintainer scripts, but this would mean that the old
configuration would j
On Sunday 21 September 2003 14:44, John Belmonte wrote:
> This is wishful thinking. Don't you think its going to become common
> for a virus to make a random insignificant change to its payload to
> thwart this?
Oh absolutely :)
This is possibly OT for the 'mentors' list... there are plenty of
Ismael Valladolid Torres wrote:
The point with Jarno's script, is that it will be very easy for us to
kick out future viruses, as long as we get md5sums for them.
This is wishful thinking. Don't you think its going to become common
for a virus to make a random insignificant change to its payl
On Sun, Sep 21, 2003 at 03:16:32PM +0100, Peter Karlsson wrote:
> A new version of a package that I maintain has changed the name of the
> default configuration file. I want to propagate this name change, but
> how do I handle it properly? AFAICT, I'm not allowed to touch conffiles
> in the maintai
Matthias Urlichs wrote:
> > As packages are normally upgraded through the life of a system I train
> > people to always say 'Y' to the replace a conffile question. Sure
> > this may leave the system in a generic and locally unworkable state.
>
> So why not "N"? That may leave the package, at wors
Hi!
A new version of a package that I maintain has changed the name of the
default configuration file. I want to propagate this name change, but
how do I handle it properly? AFAICT, I'm not allowed to touch conffiles
in the maintainer scripts, but this would mean that the old
configuration would j
On Sunday 21 September 2003 14:44, John Belmonte wrote:
> This is wishful thinking. Don't you think its going to become common
> for a virus to make a random insignificant change to its payload to
> thwart this?
Oh absolutely :)
This is possibly OT for the 'mentors' list... there are plenty of
Ismael Valladolid Torres wrote:
The point with Jarno's script, is that it will be very easy for us to
kick out future viruses, as long as we get md5sums for them.
This is wishful thinking. Don't you think its going to become common
for a virus to make a random insignificant change to its payload
El sábado, 20 de septiembre de 2003, a las 21:24, Dossy escribe:
> Seems to do a great job of blocking, without having to kick up an
> external program for every single message (other than procmail itself,
> of course).
The point with Jarno's script, is that it will be very easy for us to
kick out
El sábado, 20 de septiembre de 2003, a las 21:24, Dossy escribe:
> Seems to do a great job of blocking, without having to kick up an
> external program for every single message (other than procmail itself,
> of course).
The point with Jarno's script, is that it will be very easy for us to
kick out
30 matches
Mail list logo
