Re: Downgrading a package to get it into upcoming release
On Tue, 16 Feb 2010, Antonin Kral wrote: Epochs as well as +reverted will definitely work but looks a bit too hackish to me. Epochs have been designed precisely for this. It's not hackish... but they are somewhat ugly and some users do not understand them. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100217082430.ga21...@rivendell
Re: Downgrading a package to get it into upcoming release
On Wed, Feb 17, 2010 at 09:24:30AM +0100, Raphael Hertzog wrote: On Tue, 16 Feb 2010, Antonin Kral wrote: Epochs as well as +reverted will definitely work but looks a bit too hackish to me. Epochs have been designed precisely for this. It's not hackish... but they are somewhat ugly and some users do not understand them. imho epochs are intended for dealing with new versions that don't sort properly compared to previous versions, not for forcing users to downgrade their packages to a previous version, which could cause data loss and other non-fun stuff. sean signature.asc Description: Digital signature
Re: Downgrading a package to get it into upcoming release
On Wed, 17 Feb 2010, sean finney wrote: On Wed, Feb 17, 2010 at 09:24:30AM +0100, Raphael Hertzog wrote: On Tue, 16 Feb 2010, Antonin Kral wrote: Epochs as well as +reverted will definitely work but looks a bit too hackish to me. Epochs have been designed precisely for this. It's not hackish... but they are somewhat ugly and some users do not understand them. imho epochs are intended for dealing with new versions that don't sort properly compared to previous versions, not for forcing users to downgrade their packages to a previous version, which could cause data loss and other non-fun stuff. It all depends on how long the bad version has been available and in which distribution it was. Imposing this if the package was already in stable would be stupid, but in sid it's common that people upload experimental packages in it and then use an epoch to revert that. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100217195034.ga24...@rivendell
Re: Downgrading a package to get it into upcoming release
On Tue, 16 Feb 2010, Antonin Kral wrote: Hi all, I am looking for some advise / opinions. I am working with guys from MongoDB project to get stable package in Debian. We have currently version 1.3.1 in unstable, this is considered as development branch which is not very stable. Is there any way how to reasonably push older version (1.2.x which is considered stable), which has not been in Debian before to enable its inclusion in upcoming Debian freeze/stable release? You could use epochs to make the old version have a newer version number according to dpkg. I don't know how distasteful that is, though. -- Asheesh. -- Your temporary financial embarrassment will be relieved in a surprising manner. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1002161209520.10...@localhost
Re: Downgrading a package to get it into upcoming release
On Tue, 16 Feb 2010 at 17:04:17 +0100, Antonin Kral wrote: We have currently version 1.3.1 in unstable, this is considered as development branch which is not very stable. If you consider one of your packages to be unsuitable for a stable release, you should ensure that it has a release critical (serious, grave or critical) bug to stop it from propagating to testing automatically. In this case it'd be appropriate to file a bug against version 1.3.1, mongodb: 1.3.x unsuitable for stable in maintainer's opinion, then close it in version 1:1.2.x (assuming you use epochs as someone else suggested). I see mongodb has accumulated high-severity bugs at an impressive rate already, though, so it's in no immediate danger of migrating... S -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216172457.ga15...@reptile.pseudorandom.co.uk
Re: Downgrading a package to get it into upcoming release
hi, On Tue, Feb 16, 2010 at 12:10:16PM -0500, Asheesh Laroia wrote: You could use epochs to make the old version have a newer version number according to dpkg. I don't know how distasteful that is, though. it also might be a bit disruptive for those who have already installed the newer version of this package, don't know if you care about that. if you do, a suggestion: * keep the current development version in unstable * report an RC bug against the development version to keep it from testing, and ask the release team to boot it from testing if it's already there. * upload a new stable version to unstable, using a different naming scheme for source and binary packages, complete with the respective conflicts/replaces/provides etc. (i.e. Binary: mongodb-1.2) * once debian has released squeeze, upload transitional packages to force users to migrate to the development version. sean signature.asc Description: Digital signature
Re: Downgrading a package to get it into upcoming release
On 16/02/2010 17:04, Antonin Kral wrote: Hi all, I am looking for some advise / opinions. I am working with guys from MongoDB project to get stable package in Debian. We have currently version 1.3.1 in unstable, this is considered as development branch which is not very stable. Is there any way how to reasonably push older version (1.2.x which is considered stable), which has not been in Debian before to enable its inclusion in upcoming Debian freeze/stable release? 1) Can the two programs be installed together? If yes, simply build a MongoDB1.2 and a MongoDB1.3. If not, then you should use epochs: upload MongoDB 1:1.2 to unstable, and MongoDB 1:1.3 to experimental. -- Jean-Christophe Dubacq -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b7ad49b.4070...@free.fr
Re: Downgrading a package to get it into upcoming release
On Tue, 16 Feb 2010 18:23:39 +0100 Jean-Christophe Dubacq wrote: On 16/02/2010 17:04, Antonin Kral wrote: Hi all, I am looking for some advise / opinions. I am working with guys from MongoDB project to get stable package in Debian. We have currently version 1.3.1 in unstable, this is considered as development branch which is not very stable. Is there any way how to reasonably push older version (1.2.x which is considered stable), which has not been in Debian before to enable its inclusion in upcoming Debian freeze/stable release? 1) Can the two programs be installed together? If yes, simply build a MongoDB1.2 and a MongoDB1.3. If not, then you should use epochs: upload MongoDB 1:1.2 to unstable, and MongoDB 1:1.3 to experimental. all of these seem like rather complicated solutions. wouldn't it be a bit simpler to ask for removal from both testing and unstable, then once that happens, upload the old (known stable) version of the package? mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216125234.203850ce.michael.s.gilb...@gmail.com
Re: Downgrading a package to get it into upcoming release
On Tue, 16 Feb 2010 12:52:34 -0500 Michael Gilbert wrote: On Tue, 16 Feb 2010 18:23:39 +0100 Jean-Christophe Dubacq wrote: On 16/02/2010 17:04, Antonin Kral wrote: Hi all, I am looking for some advise / opinions. I am working with guys from MongoDB project to get stable package in Debian. We have currently version 1.3.1 in unstable, this is considered as development branch which is not very stable. Is there any way how to reasonably push older version (1.2.x which is considered stable), which has not been in Debian before to enable its inclusion in upcoming Debian freeze/stable release? 1) Can the two programs be installed together? If yes, simply build a MongoDB1.2 and a MongoDB1.3. If not, then you should use epochs: upload MongoDB 1:1.2 to unstable, and MongoDB 1:1.3 to experimental. all of these seem like rather complicated solutions. wouldn't it be a bit simpler to ask for removal from both testing and unstable, then once that happens, upload the old (known stable) version of the package? oh, you would probably need a conflicts with the newer version and a README.Debian to explain what to do for users with the new version already installed. mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216125516.a68441f8.michael.s.gilb...@gmail.com
Re: Downgrading a package to get it into upcoming release
On 2010-02-16 18:55 +0100, Michael Gilbert wrote: all of these seem like rather complicated solutions. wouldn't it be a bit simpler to ask for removal from both testing and unstable, then once that happens, upload the old (known stable) version of the package? oh, you would probably need a conflicts with the newer version and a README.Debian to explain what to do for users with the new version already installed. Except that these users will never even see it if the version in the archive is lower than the one they have installed. Your proposal seems like a non-starter to me. Sven -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iq9xt5t0@turtle.gmx.de
Re: Downgrading a package to get it into upcoming release
On 2/16/10, Sven Joachim wrote: On 2010-02-16 18:55 +0100, Michael Gilbert wrote: all of these seem like rather complicated solutions. wouldn't it be a bit simpler to ask for removal from both testing and unstable, then once that happens, upload the old (known stable) version of the package? oh, you would probably need a conflicts with the newer version and a README.Debian to explain what to do for users with the new version already installed. Except that these users will never even see it if the version in the archive is lower than the one they have installed. Your proposal seems like a non-starter to me. how about versioning it something like 1.3.1-1+reverted1.2.1? mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8e2a98be1002161021p25e2a651kb6866337a0123...@mail.gmail.com
Re: Downgrading a package to get it into upcoming release
* Simon McVittie s...@debian.org [2010-02-16 20:26] wrote: bug to stop it from propagating to testing automatically. In this case it'd be appropriate to file a bug against version 1.3.1, mongodb: 1.3.x unsuitable for stable in maintainer's opinion, then close it in version 1:1.2.x (assuming you use epochs as someone else suggested). Absolutely, I've already filled that bug. I will probably go down the path of building another binary package (mongodb-1.2) which I'll then make obsolete, as Sean suggested. Epochs as well as +reverted will definitely work but looks a bit too hackish to me. Anyway, I would like to than everybody for suggestions. I see mongodb has accumulated high-severity bugs at an impressive rate already, though, so it's in no immediate danger of migrating... And it looked like pretty quiet afternoon at the beginning :) Some of them are more about personal taste / point of view I would say. Thanks, Antoni -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216214736.gb5...@bobek.cz
