Yesterday I put my name on the applicant list for the New Maintainer
program, and I was wondering: Is it too early to put my name on the Debian
Key Signing Coordination Page to start looking for someone to sign my key
for the identification phase? And if it's not, and someone reading this is
locat
On Mon, Dec 11, 2000 at 01:59:31PM +0100, Michael Moerz wrote:
> Just in case that I have detected an unattandend maintainer
> who hasn't fixed bugs at least for half a year and never
> answeres to direct mails ( have been waiting for an answere
> now more than a month ), what should I do?
Speak
On Mon, 11 Dec 2000, Toni Mueller wrote:
> Hello,
Hi Tony,
> I'm in the process of qualifying for a Debian Maintainer and need
> to deliver some working packages. I've done some, but have problems
> understanding how the toolchain works (so my Build-Depends and Depends
> are out of line). Where
Hello,
I'm in the process of qualifying for a Debian Maintainer and need
to deliver some working packages. I've done some, but have problems
understanding how the toolchain works (so my Build-Depends and Depends
are out of line). Where do these ${shlibs...} et al get set, and how?
Is there a wa
Hello,
On Mon, Dec 11, 2000 at 01:53:35PM +0100, Bas Zoetekouw wrote:
> > Does the md5 sum of the .orig.tar.gz have to be the same as the one of
> > the upstream tarball ?
> Aren't the orig.tar.gz's packed with gzip -9? If that is the case, the
> md5sum would almost always change, since most ups
Hi Jérôme!
You wrote:
> Does the md5 sum of the .orig.tar.gz have to be the same as the one of
> the upstream tarball ?
Aren't the orig.tar.gz's packed with gzip -9? If that is the case, the
md5sum would almost always change, since most upstream developers just
use the default compression.
--
Hi!
Just in case that I have detected an unattandend maintainer
who hasn't fixed bugs at least for half a year and never
answeres to direct mails ( have been waiting for an answere
now more than a month ), what should I do?
I am really interested in fixing that outstanding bugs and
I would like t
On Mon, Dec 11, 2000 at 01:59:31PM +0100, Michael Moerz wrote:
> Just in case that I have detected an unattandend maintainer
> who hasn't fixed bugs at least for half a year and never
> answeres to direct mails ( have been waiting for an answere
> now more than a month ), what should I do?
Speak
On Mon, 11 Dec 2000, Toni Mueller wrote:
> Hello,
Hi Tony,
> I'm in the process of qualifying for a Debian Maintainer and need
> to deliver some working packages. I've done some, but have problems
> understanding how the toolchain works (so my Build-Depends and Depends
> are out of line). Where
Hello,
I'm in the process of qualifying for a Debian Maintainer and need
to deliver some working packages. I've done some, but have problems
understanding how the toolchain works (so my Build-Depends and Depends
are out of line). Where do these ${shlibs...} et al get set, and how?
Is there a w
Hi Jérôme!
You wrote:
> Does the md5 sum of the .orig.tar.gz have to be the same as the one of
> the upstream tarball ?
Aren't the orig.tar.gz's packed with gzip -9? If that is the case, the
md5sum would almost always change, since most upstream developers just
use the default compression.
--
Hello,
On Mon, Dec 11, 2000 at 01:53:35PM +0100, Bas Zoetekouw wrote:
> > Does the md5 sum of the .orig.tar.gz have to be the same as the one of
> > the upstream tarball ?
> Aren't the orig.tar.gz's packed with gzip -9? If that is the case, the
> md5sum would almost always change, since most up
Hi!
Just in case that I have detected an unattandend maintainer
who hasn't fixed bugs at least for half a year and never
answeres to direct mails ( have been waiting for an answere
now more than a month ), what should I do?
I am really interested in fixing that outstanding bugs and
I would like
Hi,
I had many discussions with developers and I still cannot state about
the following question:
Does the md5 sum of the .orig.tar.gz have to be the same as the one of
the upstream tarball ?
Some people ofter unpack the upstream tarball and rename the directory
so that the latter comply with t
Hi,
I'm taking over the Sympa mailing list manager with the agreement of its
previous maintainer.
This mailing list manager comes with a web software that stores archives
in the HTML form.
My main problem is storing html archives and bounces: I had a deep look
into the Debian Policy and the FHS
Hi,
I had many discussions with developers and I still cannot state about
the following question:
Does the md5 sum of the .orig.tar.gz have to be the same as the one of
the upstream tarball ?
Some people ofter unpack the upstream tarball and rename the directory
so that the latter comply with
Hi,
I'm taking over the Sympa mailing list manager with the agreement of its
previous maintainer.
This mailing list manager comes with a web software that stores archives
in the HTML form.
My main problem is storing html archives and bounces: I had a deep look
into the Debian Policy and the FHS
17 matches
Mail list logo
