Package: libsidplay1
Severity: serious
Justification: policy 9.1
On Sat, Sep 07, 2002 at 12:04:16AM -0300, Carlos Laviola wrote:
> A package that I maintain -- mp3blaster -- doesn't include libsidplay1 as
> a dependency, even though it links against it. I hadn't noticed that
> because I thought
Hi,
A package that I maintain -- mp3blaster -- doesn't include libsidplay1
as a dependency, even though it links against it. I hadn't noticed that
because I thought everything was working fine, as I hadn't tried to
install the package on a cleaner system or a chroot or anything.
Anyway: should I
Package: libsidplay1
Severity: serious
Justification: policy 9.1
On Sat, Sep 07, 2002 at 12:04:16AM -0300, Carlos Laviola wrote:
> A package that I maintain -- mp3blaster -- doesn't include libsidplay1 as
> a dependency, even though it links against it. I hadn't noticed that
> because I thought
Hi,
A package that I maintain -- mp3blaster -- doesn't include libsidplay1
as a dependency, even though it links against it. I hadn't noticed that
because I thought everything was working fine, as I hadn't tried to
install the package on a cleaner system or a chroot or anything.
Anyway: should I
On Wed, Sep 04, 2002 at 08:19:36PM -0700, Zack Weinberg wrote:
> Hi,
>
> I've re-done the zangband package, intending to fix bug #159039 which
> makes the game completely unplayable, but in the process I fixed a
> bunch more (all but #141684, I believe).
>
> I do not have the time to become a Deb
On Wed, Sep 04, 2002 at 08:19:36PM -0700, Zack Weinberg wrote:
> Hi,
>
> I've re-done the zangband package, intending to fix bug #159039 which
> makes the game completely unplayable, but in the process I fixed a
> bunch more (all but #141684, I believe).
>
> I do not have the time to become a De
On Fri, Sep 06, 2002 at 01:23:38PM +0100, Ross Burton wrote:
> I have packaged ESR's doclifter package for Debian, and would like
> someone to have a look at the packaging for me. Someone who has
> packaged Python before would be good, as it depends on Python 2.2. When
> I run lintian I get one m
Hi,
I have packaged ESR's doclifter package for Debian, and would like
someone to have a look at the packaging for me. Someone who has
packaged Python before would be good, as it depends on Python 2.2. When
I run lintian I get one message I am worried about -- "strange
interpreter" -- it appears
On Fri, Sep 06, 2002 at 10:06:37AM +0100, Colin Watson wrote:
> On Fri, Sep 06, 2002 at 11:09:38AM +0200, Sven LUTHER wrote:
> > I wish to be able, in a package postinst, to be able to know the
> > previously installed version of the package, so i can take different
> > actions depending of the ver
On Fri, Sep 06, 2002 at 01:23:38PM +0100, Ross Burton wrote:
> I have packaged ESR's doclifter package for Debian, and would like
> someone to have a look at the packaging for me. Someone who has
> packaged Python before would be good, as it depends on Python 2.2. When
> I run lintian I get one
Hi,
I have packaged ESR's doclifter package for Debian, and would like
someone to have a look at the packaging for me. Someone who has
packaged Python before would be good, as it depends on Python 2.2. When
I run lintian I get one message I am worried about -- "strange
interpreter" -- it appear
On Fri, Sep 06, 2002 at 11:09:38AM +0200, Sven LUTHER wrote:
> I wish to be able, in a package postinst, to be able to know the
> previously installed version of the package, so i can take different
> actions depending of the version we are replacing.
>
> I suppose it is also possible to easily di
Hello, ...
I wish to be able, in a package postinst, to be able to know the
previously installed version of the package, so i can take different
actions depending of the version we are replacing.
I suppose it is also possible to easily distinguish between a first time
install and an upgrade.
Is
On Fri, Sep 06, 2002 at 10:06:37AM +0100, Colin Watson wrote:
> On Fri, Sep 06, 2002 at 11:09:38AM +0200, Sven LUTHER wrote:
> > I wish to be able, in a package postinst, to be able to know the
> > previously installed version of the package, so i can take different
> > actions depending of the ve
On Fri, Sep 06, 2002 at 09:45:26AM +0200, Andrea Mennucc wrote:
>
> hi
>
> for your info: there is also a 'memtest86' package
>
> that is instead a kernel-like program
Yes, I know. This one is different, you do not have to boot the box with
it. You can use it in a running system.
This was _
hi
for your info: there is also a 'memtest86' package
that is instead a kernel-like program
bye
a.
On Thu, Sep 05, 2002 at 11:27:12AM +0200, Oliver Kurth wrote:
> Hello!
>
> I need sponsor(s) for my packages:
>
> memtester: A utility for testing the memory subsystem
> This is a new pack
On Fri, Sep 06, 2002 at 11:09:38AM +0200, Sven LUTHER wrote:
> I wish to be able, in a package postinst, to be able to know the
> previously installed version of the package, so i can take different
> actions depending of the version we are replacing.
>
> I suppose it is also possible to easily d
Hello, ...
I wish to be able, in a package postinst, to be able to know the
previously installed version of the package, so i can take different
actions depending of the version we are replacing.
I suppose it is also possible to easily distinguish between a first time
install and an upgrade.
Is
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Sep 06, 2002 at 09:45:26AM +0200, Andrea Mennucc wrote:
>
> hi
>
> for your info: there is also a 'memtest86' package
>
> that is instead a kernel-like program
Yes, I know. This one is different, you do not have to boot the box with
it. You can use it in a running system.
This was
hi
for your info: there is also a 'memtest86' package
that is instead a kernel-like program
bye
a.
On Thu, Sep 05, 2002 at 11:27:12AM +0200, Oliver Kurth wrote:
> Hello!
>
> I need sponsor(s) for my packages:
>
> memtester: A utility for testing the memory subsystem
> This is a new pac
22 matches
Mail list logo
