Re: Package versioning and upgrades
On Mar 27, 2015, at 10:25 PM, Lennart Sorensen wrote: So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie This used to work, but doesn't seem to any more… I'm at a loss. wheezy: 0.6.4-1.1-1-wheezy wheezy-daily: 0.6.4-12-0c60cc-wheezy jessie: 0.6.4-1.1-1 jessie-daily: 0.6.4-12-0c60cc Checking the 'wheezy' and 'jessie' packages: $ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 $ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 So ISN'T true! What did I miss? -- Geologists recently discovered that earthquakes are nothing more than Bruce Schneier and Chuck Norris communicating via a roundhouse kick-based cryptosystem. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ba468aa8-4378-495d-a2e3-639f1835d...@bayour.com
Re: Package versioning and upgrades
On May 7, 2015, at 12:17 PM, Andreas Ronnquist wrote:
# dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc echo
true
# dpkg --compare-versions 0.6.4-12-0c60cc~wheezy lt 0.6.4-12-0c60cc echo
true
true
I can't use '~' for the separator, because I want/need full source
each time. I _could_ mess with the options to git-buildpackage etc,
but it's so much simpler (for me and everyone else who want to do
the build on their own) to just use this.
But I've been using dash for 'many months' and as I said, it used
to work.
And I still don't get it - nothing is still supposed to be higher than
something, right?
Besides, how do I go from 0.6.4-1.1-1-wheezy to something~wheezy?
dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-2~wheezy echo
match || echo no match
no match
Here, the basic part of the version is 0.6.4-1.1-1 versus 0.6.4-1.1-2
(which to my eyes is supposed to be higher). It's just the 'suffix'
('-wheezy' and '~wheezy') that differs.
--
As soon as you find a product that you really like,
they will stop making it.
- Wilson's Law
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/5f79f7db-eba1-4736-bdc1-e34c7734d...@bayour.com
Re: Package versioning and upgrades
On Thu, May 07, 2015 at 01:46:16PM +0200, Turbo Fredriksson wrote:
On May 7, 2015, at 12:17 PM, Andreas Ronnquist wrote:
# dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc echo
true
# dpkg --compare-versions 0.6.4-12-0c60cc~wheezy lt 0.6.4-12-0c60cc echo
true
true
I can't use '~' for the separator, because I want/need full source
each time. I _could_ mess with the options to git-buildpackage etc,
but it's so much simpler (for me and everyone else who want to do
the build on their own) to just use this.
But I've been using dash for 'many months' and as I said, it used
to work.
No it never has. It can't ever work with dash.
And I still don't get it - nothing is still supposed to be higher than
something, right?
Besides, how do I go from 0.6.4-1.1-1-wheezy to something~wheezy?
dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-2~wheezy echo
match || echo no match
no match
Here, the basic part of the version is 0.6.4-1.1-1 versus 0.6.4-1.1-2
(which to my eyes is supposed to be higher). It's just the 'suffix'
('-wheezy' and '~wheezy') that differs.
Exactly. ~ is special and means essentially that the suffix is less
than nothing. It is used by backports and experimental and such.
There is nothing else you can use that works the same way.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150507115805.gv24...@csclub.uwaterloo.ca
Re: Package versioning and upgrades
On Thu, 7 May 2015 11:55:11 +0200, Turbo Fredrikssontu...@bayour.com wrote: On Mar 27, 2015, at 10:25 PM, Lennart Sorensen wrote: So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie This used to work, but doesn't seem to any more… I'm at a loss. wheezy: 0.6.4-1.1-1-wheezy wheezy-daily: 0.6.4-12-0c60cc-wheezy jessie: 0.6.4-1.1-1 jessie-daily: 0.6.4-12-0c60cc Checking the 'wheezy' and 'jessie' packages: $ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 $ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 So ISN'T true! What did I miss? Use instead: # dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc echo true # dpkg --compare-versions 0.6.4-12-0c60cc~wheezy lt 0.6.4-12-0c60cc echo true true http://stackoverflow.com/questions/4510640/command-line-what-is-the-purpose-of -- Andreas Rönnquist mailingli...@gusnan.se gus...@gusnan.se -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150507121755.56e80...@debian-workstation.lan
Re: Package versioning and upgrades
Turbo Fredriksson tu...@bayour.com writes: Checking the 'wheezy' and 'jessie' packages: $ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 $ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 So ISN'T true! What did I miss? Never did work like that. Just to prove the point, on a lenny system (as I'd expect) I also get: =-=-=-=- phil@apu:~$ dpkg --version Debian `dpkg' package management program version 1.14.31 (i386). This is free software; see the GNU General Public License version 2 or later for copying conditions. There is NO warranty. See dpkg --license for copyright and license details. phil@apu:~$ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 phil@apu:~$ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 =-=-=-=- could you perhaps have been using a terminal with fonts that make ~ (tilde) and - (minus) difficult to distinguish? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Package versioning and upgrades
On Thu, May 07, 2015 at 11:55:11AM +0200, Turbo Fredriksson wrote: On Mar 27, 2015, at 10:25 PM, Lennart Sorensen wrote: So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie This used to work, but doesn't seem to any more… I'm at a loss. wheezy: 0.6.4-1.1-1-wheezy wheezy-daily: 0.6.4-12-0c60cc-wheezy jessie: 0.6.4-1.1-1 jessie-daily: 0.6.4-12-0c60cc Checking the 'wheezy' and 'jessie' packages: $ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 $ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 So ISN'T true! What did I miss? ~ and - is not the same thing. ~ is special in version numbers. [0]lsorense@caffeine(~) dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 [0]lsorense@caffeine(~) dpkg --compare-versions 0.6.4-1.1-1~wheezy lt 0.6.4-1.1-1; echo $? 0 -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150507115436.gu24...@csclub.uwaterloo.ca
Re: Package versioning and upgrades
Turbo Fredriksson tu...@bayour.com (2015-05-07): On Mar 27, 2015, at 10:25 PM, Lennart Sorensen wrote: So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie This used to work, but doesn't seem to any more… I'm at a loss. wheezy: 0.6.4-1.1-1-wheezy wheezy-daily: 0.6.4-12-0c60cc-wheezy jessie: 0.6.4-1.1-1 jessie-daily: 0.6.4-12-0c60cc Checking the 'wheezy' and 'jessie' packages: $ dpkg --compare-versions 0.6.4-1.1-1-wheezy lt 0.6.4-1.1-1; echo $? 1 $ dpkg --compare-versions 0.6.4-12-0c60cc-wheezy lt 0.6.4-12-0c60cc; echo $? 1 So ISN'T true! What did I miss? Reaching debian-mentors@ or debian-user@ instead of debian-boot@, I suppose. Mraw, KiBi. signature.asc Description: Digital signature
Re: Package versioning and upgrades
On Mon, Mar 30, 2015 at 06:50:22AM +0200, Cyril Brulebois wrote: Wouter Verhelst wou...@debian.org (2015-03-28): Alternatively, you could use release version numbers rather than code names: 0.6.3-1.3-1~Debian7 (rather than wheezy), and 0.6.3-1.3-1~Debian8 (rather than jessie) Using the same scheme as stable security updates might be a good idea instead of inventing another versioning scheme? Meaning ~deb7u1 or +deb7u1 for the first upload to wheezy, ~deb7u2 or +deb7u2 for the next one; as for jessie, use ~deb8u1 or +deb8u1 for the first upload, etc. And people better not rely on these being in alphabetical order, they'll run into trouble transitioning 9 and 10. The advantage of code names is that no one would assume jessie is later in alphabetical order than wheezy. Protection for idiots. -- hendrik -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150330132735.gb9...@topoi.pooq.com
Re: Package versioning and upgrades
On Mon, Mar 30, 2015 at 09:27:35AM -0400, Hendrik Boom wrote: And people better not rely on these being in alphabetical order, they'll run into trouble transitioning 9 and 10. The advantage of code names is that no one would assume jessie is later in alphabetical order than wheezy. deb9u1 is less than deb10u2 according to dpkg, so it works fine. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150330134045.gg29...@csclub.uwaterloo.ca
Re: Package versioning and upgrades
On Mon, Mar 30, 2015 at 06:50:22AM +0200, Cyril Brulebois wrote: Wouter Verhelst wou...@debian.org (2015-03-28): Alternatively, you could use release version numbers rather than code names: 0.6.3-1.3-1~Debian7 (rather than wheezy), and 0.6.3-1.3-1~Debian8 (rather than jessie) Using the same scheme as stable security updates might be a good idea instead of inventing another versioning scheme? Meaning ~deb7u1 or +deb7u1 for the first upload to wheezy, ~deb7u2 or +deb7u2 for the next one; as for jessie, use ~deb8u1 or +deb8u1 for the first upload, etc. Yes that is an even better idea. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150330134115.gh29...@csclub.uwaterloo.ca
Re: Package versioning and upgrades
On Mar 30, 2015, at 6:50 AM, Cyril Brulebois wrote: Meaning ~deb7u1 or +deb7u1 for the first upload to wheezy, ~deb7u2 or +deb7u2 for the next one; as for jessie, use ~deb8u1 or +deb8u1 for the first upload, etc. I used to do something like that, but because the 'Dailies' is directly from the git release, git-buildpackage wouldn't create a tar ball that worked. It refused to create one because there was [to much] difference between the '.orig.tar.gz' (which was/is based on the 'Released') one and the code that's in there (in the source directory) now. This is because all packages is called '0.6.3' as base. 0.6.3-1~wheezy vs. 0.6.3-40-0f7d2a-wheezy Although the latter one is 'almost 0.6.4'… So from this, and from what is the Debian GNU/Linux packaging standards (what I remember from it :), it looks like the latter one only have Debian GNU/Linux updates, not source. Which isn't the case... In the Dailies this is not a problem (to have the tilde), because that really is a correct, new source. But I should probably change that to, just for consistency... Also, S3 can't handle '+' in the filename, so I have to remember to make hard links (or copies) of the file, but with a space instead of a +! And most of the times I forgot about that, so... Also, because the 'Dailies' for Wheezy and Jessie are _identical_ (down to the last byte - source vise at least, including the debian directory), I thought it was smarter to use the original suggestion - 'nothing is higher than something'… So having two different versions (after the ~ or +), doesn't make much sense - they indicate that there's a difference between the packages. Which was my first mistake - I started counting from the one for the first version I created on each platform and that, in part, gave me this problem in the first place - if I hadn't, maybe I would have discovered the problem earlier… The original suggestion takes all that into account - * it makes it easier to see that the packages are identical, * there's no plus to screw up S3, * there's no tilde to mess with the 'orig.tar.gz' file and * the upgrade path works. The only downside is that I can't easily find only Jessie packages with a simple find in my repository :). But I can live with that, there's other ways to find that out (that are only slightly more time consuming :D But I thank everyone for their suggestion. I really DO appreciate it! But for me the case is closed :). -- Life sucks and then you die signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Package versioning and upgrades
Wouter Verhelst wou...@debian.org (2015-03-28): Alternatively, you could use release version numbers rather than code names: 0.6.3-1.3-1~Debian7 (rather than wheezy), and 0.6.3-1.3-1~Debian8 (rather than jessie) Using the same scheme as stable security updates might be a good idea instead of inventing another versioning scheme? Meaning ~deb7u1 or +deb7u1 for the first upload to wheezy, ~deb7u2 or +deb7u2 for the next one; as for jessie, use ~deb8u1 or +deb8u1 for the first upload, etc. Mraw, KiBi. signature.asc Description: Digital signature
Re: Package versioning and upgrades
On Fri, Mar 27, 2015 at 05:25:51PM -0400, Lennart Sorensen wrote: On Fri, Mar 27, 2015 at 09:46:06PM +0100, Turbo Fredriksson wrote: Since ZoL (ZFS On Linux) isn't yet in Debian GNU/Linux, I've been doing my own packages for ZoL in that package repo. This include changes to the installer (debian-installer, base-installer, grub-installer, partman-target and partman-zfs). But because the Debian GNU/Linux git repo refuses force pushes, they latest versions is now in the ZoL GIT repo (https://github.com/zfsonlinux/debian-installers). But I think I've painted myself into a corner regarding the upgrade path. I have four repos: wheezy = The released ZoL version for Wheezy wheezy-daily= The GIT master releases of ZoL for Wheezy jessie = The released ZoL version for Jessie jessie-daily= The GIT master releases of ZoL for Jessie So basically, the packages in 'wheezy' and 'jessie' are identical, except they're compiled on the different versions of Debian GNU/Linux. Same for 'wheezy-daily' vs. 'jessie-daily'. Identical, in the meaning that it uses the exact same codebase/version and patch set of ZoL, just compiled for different libraries on two different platform version. But certain upgrade paths isn't working (which isn't much of a surprise actually - didn't quite think this through I guess): UPGRADE PATHSTATUS VERSION COMPARE wheezy = wheezy-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-38-7d90f5-wheezy wheezy = jessie= NO0.6.3-1.3-1~wheezy lt 0.6.3-1.3-1~jessie wheezy = jessie-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-35-7d90f5-jessie wheezy-daily = jessie = NO0.6.3-38-7d90f5-wheezy lt 0.6.3-1.3-1~jessie wheezy-daily = jessie-daily= NO0.6.3-38-7d90f5-wheezy lt 0.6.3-35-7d90f5-jessie jessie = jessie-daily = YES 0.6.3-1.3-1~jessie lt 0.6.3-35-7d90f5-jessie The versions here is the actually versions currently in the repository, and the result (YES/NO) is the status of dpkg --compare-versions. I suppose the big problem you have is that jessie is alphabetically lower than wheezy. My question now is: How do I setup/change the versioning so that all of these upgrade paths work? Well you can solve the wheezy to jessue upgradesm but I don't think you can solve wheezy-daily = jessie, since that really is a downgrade. Doing this in intermediate steps isn't a problem, but I prefer not to use epochs if possible (even if that would be the simplest solution :)... If you were to do this: Change 0.6.3-1.3-1~wheezy to 0.6.3-1.3-2~wheezy Change 0.6.3-1.3-1~jessie to 0.6.3-1.3-2 Change 0.6.3-38-7d90f5-wheezy to 0.6.3-39-7d90f5~wheezy Change 0.6.3-35-7d90f5-jessie to 0.6.3-39-7d90f5 So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie, and bump the main packaging version up to make the new versions higher than they were before. Alternatively, you could use release version numbers rather than code names: 0.6.3-1.3-1~Debian7 (rather than wheezy), and 0.6.3-1.3-1~Debian8 (rather than jessie) -- It is easy to love a country that is famous for chocolate and beer -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328061024.ga7...@grep.be
Re: Package versioning and upgrades
On Fri, Mar 27, 2015 at 09:46:06PM +0100, Turbo Fredriksson wrote: Since ZoL (ZFS On Linux) isn't yet in Debian GNU/Linux, I've been doing my own packages for ZoL in that package repo. This include changes to the installer (debian-installer, base-installer, grub-installer, partman-target and partman-zfs). But because the Debian GNU/Linux git repo refuses force pushes, they latest versions is now in the ZoL GIT repo (https://github.com/zfsonlinux/debian-installers). But I think I've painted myself into a corner regarding the upgrade path. I have four repos: wheezy = The released ZoL version for Wheezy wheezy-daily= The GIT master releases of ZoL for Wheezy jessie = The released ZoL version for Jessie jessie-daily= The GIT master releases of ZoL for Jessie So basically, the packages in 'wheezy' and 'jessie' are identical, except they're compiled on the different versions of Debian GNU/Linux. Same for 'wheezy-daily' vs. 'jessie-daily'. Identical, in the meaning that it uses the exact same codebase/version and patch set of ZoL, just compiled for different libraries on two different platform version. But certain upgrade paths isn't working (which isn't much of a surprise actually - didn't quite think this through I guess): UPGRADE PATH STATUS VERSION COMPARE wheezy = wheezy-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-38-7d90f5-wheezy wheezy = jessie= NO0.6.3-1.3-1~wheezy lt 0.6.3-1.3-1~jessie wheezy = jessie-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-35-7d90f5-jessie wheezy-daily = jessie = NO0.6.3-38-7d90f5-wheezy lt 0.6.3-1.3-1~jessie wheezy-daily = jessie-daily= NO0.6.3-38-7d90f5-wheezy lt 0.6.3-35-7d90f5-jessie jessie = jessie-daily = YES 0.6.3-1.3-1~jessie lt 0.6.3-35-7d90f5-jessie The versions here is the actually versions currently in the repository, and the result (YES/NO) is the status of dpkg --compare-versions. I suppose the big problem you have is that jessie is alphabetically lower than wheezy. My question now is: How do I setup/change the versioning so that all of these upgrade paths work? Well you can solve the wheezy to jessue upgradesm but I don't think you can solve wheezy-daily = jessie, since that really is a downgrade. Doing this in intermediate steps isn't a problem, but I prefer not to use epochs if possible (even if that would be the simplest solution :)... If you were to do this: Change 0.6.3-1.3-1~wheezy to 0.6.3-1.3-2~wheezy Change 0.6.3-1.3-1~jessie to 0.6.3-1.3-2 Change 0.6.3-38-7d90f5-wheezy to 0.6.3-39-7d90f5~wheezy Change 0.6.3-35-7d90f5-jessie to 0.6.3-39-7d90f5 So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie, and bump the main packaging version up to make the new versions higher than they were before. UPGRADE PATHSTATUS VERSION COMPARE wheezy = wheezy-daily = YES 0.6.3-1.3-2~wheezy lt 0.6.3-39-7d90f5~wheezy wheezy = jessie= YES 0.6.3-1.3-2~wheezy lt 0.6.3-1.3-2 wheezy = jessie-daily = YES 0.6.3-1.3-2~wheezy lt 0.6.3-39-7d90f5 wheezy-daily = jessie = NO0.6.3-39-7d90f5~wheezy lt 0.6.3-1.3-2 wheezy-daily = jessie-daily= YES 0.6.3-39-7d90f5~wheezy lt 0.6.3-39-7d90f5 jessie = jessie-daily = YES 0.6.3-1.3-2 lt 0.6.3-39-7d90f5 So by only using ~wheezy on the wheezy versions and using nothing on jessie, the jessie version is ALWAYS higher, since ~anything is automatically less than nothing (this is why backports and such use that in their version suffix). The only unsolvable case is the one that is an actual downgrade, which there is no way to solve automatically. If someone wants to do that they will have to force downgrading to the older version. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150327212551.ge29...@csclub.uwaterloo.ca
Package versioning and upgrades
Since ZoL (ZFS On Linux) isn't yet in Debian GNU/Linux, I've been doing my own packages for ZoL in that package repo. This include changes to the installer (debian-installer, base-installer, grub-installer, partman-target and partman-zfs). But because the Debian GNU/Linux git repo refuses force pushes, they latest versions is now in the ZoL GIT repo (https://github.com/zfsonlinux/debian-installers). But I think I've painted myself into a corner regarding the upgrade path. I have four repos: wheezy = The released ZoL version for Wheezy wheezy-daily= The GIT master releases of ZoL for Wheezy jessie = The released ZoL version for Jessie jessie-daily= The GIT master releases of ZoL for Jessie So basically, the packages in 'wheezy' and 'jessie' are identical, except they're compiled on the different versions of Debian GNU/Linux. Same for 'wheezy-daily' vs. 'jessie-daily'. Identical, in the meaning that it uses the exact same codebase/version and patch set of ZoL, just compiled for different libraries on two different platform version. But certain upgrade paths isn't working (which isn't much of a surprise actually - didn't quite think this through I guess): UPGRADE PATHSTATUS VERSION COMPARE wheezy = wheezy-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-38-7d90f5-wheezy wheezy = jessie= NO0.6.3-1.3-1~wheezy lt 0.6.3-1.3-1~jessie wheezy = jessie-daily = YES 0.6.3-1.3-1~wheezy lt 0.6.3-35-7d90f5-jessie wheezy-daily = jessie = NO0.6.3-38-7d90f5-wheezy lt 0.6.3-1.3-1~jessie wheezy-daily = jessie-daily= NO0.6.3-38-7d90f5-wheezy lt 0.6.3-35-7d90f5-jessie jessie = jessie-daily = YES 0.6.3-1.3-1~jessie lt 0.6.3-35-7d90f5-jessie The versions here is the actually versions currently in the repository, and the result (YES/NO) is the status of dpkg --compare-versions. My question now is: How do I setup/change the versioning so that all of these upgrade paths work? Doing this in intermediate steps isn't a problem, but I prefer not to use epochs if possible (even if that would be the simplest solution :)... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4f9ba4ca-37e8-452e-99e8-6964faf84...@bayour.com
Re: Package versioning and upgrades
On Mar 27, 2015, at 10:25 PM, Lennart Sorensen wrote: So always use ~wheezy suffix when building for wheezy and use no suffix when building for jessie, and bump the main packaging version up to make the new versions higher than they were before. Awesome, thank you! The only unsolvable case is the one that is an actual downgrade You're of course right. Didn't think about that. I don't really know how to solve that though. If one have chosen to run latest on Wheezy, but wants to run released on Jessie, I probably have to force a manual downgrade. Thanx for the help! This sounds like a very good plan! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/9397e9c6-842c-4a06-bc93-2b12d2e37...@bayour.com
