On 04/26/2018 11:50 AM, Anton Derbenev wrote:
> 1. Actually, in our old repository setup, there are package versions like "8.16+zjessie+nmu1". You can see the combination of "forking" and NMU concepts here, and upgrades are handled in an interesting manner. While comparison-wise squeeze < wheezy, wheezy > jessie - so "z" is added to make wheezy < zjessie. It would continue for stretch, e.g. zjessie < zstretch... As suggested in the document you mentioned, handling "forking" with the debXuY format would introduce a reusable ordering and that I picked up to replace "zjessie".
"-zjessie" was me having not having paid enough attention to realize that there were
better solutions. eg. "+bpoX.Y" for backports.
When thinking about numbers, I found it useful to make a diagram of repositories,
and supported upgrade paths. The look to see that version numbers of rebuilds for newer repos
would need to compare to ensure that "newer" repos, have "newer" versions.
By "newer" I mean, A newer than B when "dpkg --compare-versions A '>' B" is true.
- References:
- Re: NSLS-II Debian Repository in 2018 Anton Derbenev
- Re: NSLS-II Debian Repository in 2018 Ralph Lange
- Re: NSLS-II Debian Repository in 2018 Anton Derbenev
- Navigate by Date:
- Prev:
Re: NSLS-II Debian Repository in 2018 Anton Derbenev
- Next:
rtems_cpu_usage_report Matt Rippa
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: NSLS-II Debian Repository in 2018 Anton Derbenev
- Next:
Re: NSLS-II Debian Repository in 2018 Konrad, Martin
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|