Canonical way to upgrade an existing nfsroot?
Steffen Grunewald
Steffen.Grunewald at aei.mpg.de
Tue Sep 6 17:13:34 CEST 2016
On Tue, 2016-09-06 at 16:08:57 +0200, Thomas Lange wrote:
> >>>>> On Tue, 6 Sep 2016 16:05:04 +0200, Steffen Grunewald <Steffen.Grunewald at aei.mpg.de> said:
>
> > from scratch. I'm running into Debian bug #830229 now (jessie/koeln, 044+109-1).
> > This did happen before as well (044+105-2) but I didn't notice, and stretch
> > seems to be unaffected (so this may actually be a policy/dpkg issue?).
> I also think that this bug is more a dpkg bug.
Well, you don't "backport" a sid package without asking for trouble sometimes.
The "rm_conffiles" line in debian/dracut.maintscript seems to require a newer
dpkg, indeed...
Checking the differences between dpkg-maintscript-helper scripts in dpkg 1.17.27
(jessie) and 1.18.10 (stretch), one quickly finds a bunch of
- dpkg --compare-versions "$2" le-nl "$LASTVERSION"; then
+ dpkg --compare-versions -- "$2" le-nl "$LASTVERSION"; then
replacements - which seem to be closely related.
dracut's maintscripts seem to make use of that.
I found that you have created a backport for jessie but don't distribute that via
jessie/koeln?
You might tweak the dracut.maintscript (if it's required at all) ...
- S
More information about the linux-fai
mailing list