Re: uploading to stable
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.
> > I need to upload a package vith version >=3.0 to stable-proposed-update.
> > Which version should I upload to stable?
> Why do you say that you NEED to upload such a version to
> stable-proposed-updates? Do you understand that, even if it is accepted
> by the archive software, such a version jump will not be accepted by the
> stable release manager?
Because replicator's version is supposed to match the debian's version
it is build for :
replicator 2.1 can replicate debian 2.1,2.2
replicator 3.0 can replicate debian 3.0
> > When I try to upload in stable a version identical to the unstable one
> > it is rejected :(
> > How can I proceed to upload a recent version to stable (the best would
> > be 3.0-2) ?
> The versions should be stable <= testing <= unstable. This means the
> archive scripts will not let you upload a package to stable until the
> package in testing has been updated.
thanks for this explanation.
> It's also not possible to use the exact same package version twice when
> uploading. You must use a unique package version for each upload, while
> still meeting the version requirements above.
But how to deal with changelog then? Does that mean I must keep an old 3.0
version around to upload it to stable when 3.0-2 will hit testing?