Message ID | 1367614740-20751-1-git-send-email-tim.gardner@canonical.com |
---|---|
State | New |
Headers | show |
On 05/03/2013 01:59 PM, Tim Gardner wrote: > There is a fair amount of concern that in certain cases > an upgraded system could be left with a regressed and > unbootable system if the new kernel replaces the last > bootable kernel, e.g., it does not have a different ABI. > > Signed-off-by: Tim Gardner <tim.gardner@canonical.com> > --- > debian/rules.d/1-maintainer.mk | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk > index 0aa7e4f..9e0de1b 100644 > --- a/debian/rules.d/1-maintainer.mk > +++ b/debian/rules.d/1-maintainer.mk > @@ -103,9 +103,10 @@ diffupstream: > startnewrelease: > dh_testdir > @nextminor=$(shell expr `echo $(revision) | awk -F. '{print $$2}'` + 1); \ > + nextmajor=$(shell expr `echo $(revision) | awk -F. '{print $$1}'` + 1); \ > now="$(shell date -R)"; \ > - echo "Creating new changelog set for $(abi_release).$$nextminor..."; \ > - echo -e "$(src_pkg_name) ($(abi_release).$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > + echo "Creating new changelog set for $(release)-$$nextmajor.$$nextminor..."; \ > + echo -e "$(src_pkg_name) ($(release)-$$nextmajor.$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Do not edit directly. Autogenerated at release." >> \ > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Use the printchanges target to see the curent changes." \ >
On 05/03/2013 01:59 PM, Tim Gardner wrote: > There is a fair amount of concern that in certain cases > an upgraded system could be left with a regressed and > unbootable system if the new kernel replaces the last > bootable kernel, e.g., it does not have a different ABI. > > Signed-off-by: Tim Gardner <tim.gardner@canonical.com> > --- > debian/rules.d/1-maintainer.mk | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk > index 0aa7e4f..9e0de1b 100644 > --- a/debian/rules.d/1-maintainer.mk > +++ b/debian/rules.d/1-maintainer.mk > @@ -103,9 +103,10 @@ diffupstream: > startnewrelease: > dh_testdir > @nextminor=$(shell expr `echo $(revision) | awk -F. '{print $$2}'` + 1); \ > + nextmajor=$(shell expr `echo $(revision) | awk -F. '{print $$1}'` + 1); \ > now="$(shell date -R)"; \ > - echo "Creating new changelog set for $(abi_release).$$nextminor..."; \ > - echo -e "$(src_pkg_name) ($(abi_release).$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > + echo "Creating new changelog set for $(release)-$$nextmajor.$$nextminor..."; \ > + echo -e "$(src_pkg_name) ($(release)-$$nextmajor.$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Do not edit directly. Autogenerated at release." >> \ > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Use the printchanges target to see the curent changes." \ >
On 05/03/2013 01:59 PM, Tim Gardner wrote: > There is a fair amount of concern that in certain cases > an upgraded system could be left with a regressed and > unbootable system if the new kernel replaces the last > bootable kernel, e.g., it does not have a different ABI. > > Signed-off-by: Tim Gardner <tim.gardner@canonical.com> > --- > debian/rules.d/1-maintainer.mk | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk > index 0aa7e4f..9e0de1b 100644 > --- a/debian/rules.d/1-maintainer.mk > +++ b/debian/rules.d/1-maintainer.mk > @@ -103,9 +103,10 @@ diffupstream: > startnewrelease: > dh_testdir > @nextminor=$(shell expr `echo $(revision) | awk -F. '{print $$2}'` + 1); \ > + nextmajor=$(shell expr `echo $(revision) | awk -F. '{print $$1}'` + 1); \ > now="$(shell date -R)"; \ > - echo "Creating new changelog set for $(abi_release).$$nextminor..."; \ > - echo -e "$(src_pkg_name) ($(abi_release).$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > + echo "Creating new changelog set for $(release)-$$nextmajor.$$nextminor..."; \ > + echo -e "$(src_pkg_name) ($(release)-$$nextmajor.$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Do not edit directly. Autogenerated at release." >> \ > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Use the printchanges target to see the curent changes." \ >
On 05/03/2013 01:59 PM, Tim Gardner wrote: > There is a fair amount of concern that in certain cases > an upgraded system could be left with a regressed and > unbootable system if the new kernel replaces the last > bootable kernel, e.g., it does not have a different ABI. > > Signed-off-by: Tim Gardner <tim.gardner@canonical.com> > --- > debian/rules.d/1-maintainer.mk | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk > index 0aa7e4f..9e0de1b 100644 > --- a/debian/rules.d/1-maintainer.mk > +++ b/debian/rules.d/1-maintainer.mk > @@ -103,9 +103,10 @@ diffupstream: > startnewrelease: > dh_testdir > @nextminor=$(shell expr `echo $(revision) | awk -F. '{print $$2}'` + 1); \ > + nextmajor=$(shell expr `echo $(revision) | awk -F. '{print $$1}'` + 1); \ > now="$(shell date -R)"; \ > - echo "Creating new changelog set for $(abi_release).$$nextminor..."; \ > - echo -e "$(src_pkg_name) ($(abi_release).$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > + echo "Creating new changelog set for $(release)-$$nextmajor.$$nextminor..."; \ > + echo -e "$(src_pkg_name) ($(release)-$$nextmajor.$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Do not edit directly. Autogenerated at release." >> \ > $(DEBIAN)/changelog.new; \ > echo " CHANGELOG: Use the printchanges target to see the curent changes." \ >
diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk index 0aa7e4f..9e0de1b 100644 --- a/debian/rules.d/1-maintainer.mk +++ b/debian/rules.d/1-maintainer.mk @@ -103,9 +103,10 @@ diffupstream: startnewrelease: dh_testdir @nextminor=$(shell expr `echo $(revision) | awk -F. '{print $$2}'` + 1); \ + nextmajor=$(shell expr `echo $(revision) | awk -F. '{print $$1}'` + 1); \ now="$(shell date -R)"; \ - echo "Creating new changelog set for $(abi_release).$$nextminor..."; \ - echo -e "$(src_pkg_name) ($(abi_release).$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ + echo "Creating new changelog set for $(release)-$$nextmajor.$$nextminor..."; \ + echo -e "$(src_pkg_name) ($(release)-$$nextmajor.$$nextminor) UNRELEASED; urgency=low\n" > $(DEBIAN)/changelog.new; \ echo " CHANGELOG: Do not edit directly. Autogenerated at release." >> \ $(DEBIAN)/changelog.new; \ echo " CHANGELOG: Use the printchanges target to see the curent changes." \
There is a fair amount of concern that in certain cases an upgraded system could be left with a regressed and unbootable system if the new kernel replaces the last bootable kernel, e.g., it does not have a different ABI. Signed-off-by: Tim Gardner <tim.gardner@canonical.com> --- debian/rules.d/1-maintainer.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)