On Sat, 29 Mar 2003 19:57, Tommaso Moroni wrote:
> I'm maintaining two Debian packages and both have an upstream bug, which
> I've already reported to the upstream authors. The bug fixes will be
> included in the next upstream release.
> My question is:
> Should I wait for a new upstream release or
On Saturday 29 March 2003 14:22, Andrew Stribblehill wrote:
> Quoting Tommaso Moroni <[EMAIL PROTECTED]> (2003-03-29 06:57:00 GMT):
> > Should I wait for a new upstream release or should I apply the fixes to
> > the current packages to get rid of those bugs as soon as possible?
>
> I consider it my
Quoting Tommaso Moroni <[EMAIL PROTECTED]> (2003-03-29 06:57:00 GMT):
> Should I wait for a new upstream release or should I apply the fixes to the
> current packages to get rid of those bugs as soon as possible?
I consider it my duty to apply bug-fixes that I've patched to the
Debian packages I
On Saturday 29 March 2003 14:22, Andrew Stribblehill wrote:
> Quoting Tommaso Moroni <[EMAIL PROTECTED]> (2003-03-29 06:57:00 GMT):
> > Should I wait for a new upstream release or should I apply the fixes to
> > the current packages to get rid of those bugs as soon as possible?
>
> I consider it my
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I'm maintaining two Debian packages and both have an upstream bug, which I've
>already reported to the upstream authors. The bug fixes will be included in
>the next upstream release.
>My question is:
>Should I wait for a new upstream re
Quoting Tommaso Moroni <[EMAIL PROTECTED]> (2003-03-29 06:57:00 GMT):
> Should I wait for a new upstream release or should I apply the fixes to the
> current packages to get rid of those bugs as soon as possible?
I consider it my duty to apply bug-fixes that I've patched to the
Debian packages I
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I'm maintaining two Debian packages and both have an upstream bug, which I've
>already reported to the upstream authors. The bug fixes will be included in
>the next upstream release.
>My question is:
>Should I wait for a new upstream re
Hi!
I'm maintaining two Debian packages and both have an upstream bug, which I've
already reported to the upstream authors. The bug fixes will be included in
the next upstream release.
My question is:
Should I wait for a new upstream release or should I apply the fixes to the
current packages
On Sat, Mar 29, 2003 at 08:22:02AM +0100, Marc Haber wrote:
> I am currently preparing packages for rrfw, a network statistics tool like
> mrtg and cricket but much more flexible. rrfw needs a whole bunch of perl
> packages that are not even in unstable, so these packages need to go into
> Debian
Hi!
I'm maintaining two Debian packages and both have an upstream bug, which I've
already reported to the upstream authors. The bug fixes will be included in
the next upstream release.
My question is:
Should I wait for a new upstream release or should I apply the fixes to the
current packages
Hi all!
I am trying to dive head first into the world of Debian development. As
such, this is my first post to any developer-related mailing list. I
thought the mentor list would be appropriate, as I probably need a
little more hand-holding than the normal development lists are meant to
provide. I
I've taken some time during this weekend to learn a bit of debian
packaging system, and i've debianized starvoyager, a star-trek themed
game licenced under BSD/LGPL:
http://www.srcf.ucam.org/~ret28/
The result is available here:
http://idanso.dyndns.org/maps/sv/
On Sat, Mar 29, 2003 at 08:22:02AM +0100, Marc Haber wrote:
> I am currently preparing packages for rrfw, a network statistics tool like
> mrtg and cricket but much more flexible. rrfw needs a whole bunch of perl
> packages that are not even in unstable, so these packages need to go into
> Debian
Hi all!
I am trying to dive head first into the world of Debian development. As
such, this is my first post to any developer-related mailing list. I
thought the mentor list would be appropriate, as I probably need a
little more hand-holding than the normal development lists are meant to
provide. I
I've taken some time during this weekend to learn a bit of debian
packaging system, and i've debianized starvoyager, a star-trek themed
game licenced under BSD/LGPL:
http://www.srcf.ucam.org/~ret28/
The result is available here:
http://idanso.dyndns.org/maps/sv/
--
To UNSUBSCRIBE, email to [E
Hello,
could someone please sponsor this locale package for mozilla? It is
based on mozilla-locale-gl-es, which is already in Debian, so there
shouldn't be much trouble with it.
Package: mozilla-locale-sl
Version: 1.3-1
Priority: optional
Section: x11
Maintainer: Jure Cuhalev <[EMAIL PROTECTED]>
Hi Carlo!
You wrote:
> I have two packages, 'atoms' and 'horae'. horae depends on atoms and
> perl-tk and in the original tarball, it contains perl module
> subdirectories which generate installed perl modules and man pages which
> would overwrite the ones in the perl-tk and atoms packages.
>
>
Hello,
could someone please sponsor this locale package for mozilla? It is
based on mozilla-locale-gl-es, which is already in Debian, so there
shouldn't be much trouble with it.
Package: mozilla-locale-sl
Version: 1.3-1
Priority: optional
Section: x11
Maintainer: Jure Cuhalev <[EMAIL PROTECTED]>
Hi Carlo!
You wrote:
> I have two packages, 'atoms' and 'horae'. horae depends on atoms and
> perl-tk and in the original tarball, it contains perl module
> subdirectories which generate installed perl modules and man pages which
> would overwrite the ones in the perl-tk and atoms packages.
>
>
Hi,
I am currently preparing packages for rrfw, a network statistics tool
like mrtg and cricket but much more flexible. rrfw needs a whole bunch
of perl packages that are not even in unstable, so these packages need
to go into Debian before rrfw can enter Debian.
Is it OK to upload perl modules g
On Thu Mar 27, 07:46pm +0100, Frank Küster wrote:
> # apt-get --purge remove netenv
> [...]
Yes, this should purge your debconf questions. However, his is left as
an exercise to the maintainer; there's a handy db_purge command after
you've sourced /usr/share/debconf/confmodule.sh which purges debc
21 matches
Mail list logo
