Hi,
Le dim 22/12/2002 à 19:40, Steve Langasek a écrit :
> On Sun, Dec 22, 2002 at 07:13:40PM +0100, Sebastien Chaumat wrote:
>
> > My package in stable and testing is in version 2.1.
> > In unstable it is version 3.0-1.
> > 3.0-2 is already in the pool for unstable.
&
Hi,
My package in stable and testing is in version 2.1.
In unstable it is version 3.0-1.
3.0-2 is already in the pool for unstable.
I need to upload a package vith version >=3.0 to stable-proposed-update.
Which version should I upload to stable?
When I try to upload in stable a version identica
Hi,
Le dim 22/12/2002 à 19:40, Steve Langasek a écrit :
> On Sun, Dec 22, 2002 at 07:13:40PM +0100, Sebastien Chaumat wrote:
>
> > My package in stable and testing is in version 2.1.
> > In unstable it is version 3.0-1.
> > 3.0-2 is already in the pool for unstable.
&
Hi,
My package in stable and testing is in version 2.1.
In unstable it is version 3.0-1.
3.0-2 is already in the pool for unstable.
I need to upload a package vith version >=3.0 to stable-proposed-update.
Which version should I upload to stable?
When I try to upload in stable a version identica
Hi,
Is there a kind of global changelog that explain the most significant
diff between stable and testing (a kind of digest)?
The interest would be to allow new maintainers (who weren't following
the developpement from the last release of stable) to avoid spending too
much time discovering
Hi,
Is there a kind of global changelog that explain the most significant
diff between stable and testing (a kind of digest)?
The interest would be to allow new maintainers (who weren't following
the developpement from the last release of stable) to avoid spending too
much time discoverin
[EMAIL PROTECTED] wrote:
I plan to distribute a custom kernel for the installation bootdisk of
replicator. This is mainly a monolitic kernel with all network cards
drivers plus some networking option.
My question is : can I compile this by hand and then only release the
binary (along with
Hello there,
I plan to distribute a custom kernel for the installation bootdisk of
replicator. This is mainly a monolitic kernel with all network cards
drivers plus some networking option.
My question is : can I compile this by hand and then only release the
binary (along with the right .c
[EMAIL PROTECTED] wrote:
>> I plan to distribute a custom kernel for the installation bootdisk of
>>replicator. This is mainly a monolitic kernel with all network cards
>>drivers plus some networking option.
>>
>> My question is : can I compile this by hand and then only release the
>>binary
Hello there,
I plan to distribute a custom kernel for the installation bootdisk of
replicator. This is mainly a monolitic kernel with all network cards
drivers plus some networking option.
My question is : can I compile this by hand and then only release the
binary (along with the right .
Hello,
thanks for this short/efficient anwser.
[EMAIL PROTECTED] wrote:
this
may change in the future if my proposition to debian policy are
accepted. Do you think this is possible?
What proposition?
To replicate a Debian system we need to know which configuration files
are repl
Hello,
thanks for this short/efficient anwser.
[EMAIL PROTECTED] wrote:
>>this
>> may change in the future if my proposition to debian policy are
>>accepted. Do you think this is possible?
>>
>
> What proposition?
>
To replicate a Debian system we need to know which configuration fil
Hello,
I'm about to upload replicator (replicator.sourceforge.net at present)
on master but I have some questions:
- there's no postrm script yet althougth there's a real need for that.
Should I write it before uploading?
- I'd like to engage many discussion about replicator on debian list
Hello,
I'm about to upload replicator (replicator.sourceforge.net at present)
on master but I have some questions:
- there's no postrm script yet althougth there's a real need for that.
Should I write it before uploading?
- I'd like to engage many discussion about replicator on debian lists
14 matches
Mail list logo
