Apparently I have killed a working nfsroot by naively running "apt-get upgrade".
What's the canonical way to keep a nfsroot updated? Would it be sufficient
to "hold" the dracut* packages so their postinst scripts don't fail?
Thanks,
S
--
Steffen Grunewald, Cluster Administrator
Max Planck Insti
On Tue, 2016-09-06 at 15:51:06 +0200, Steffen Grunewald wrote:
> Apparently I have killed a working nfsroot by naively running "apt-get
> upgrade".
> What's the canonical way to keep a nfsroot updated? Would it be sufficient
> to "hold" the dracut* packages so their postinst scripts don't fail?
T
> On Tue, 6 Sep 2016 15:51:06 +0200, Steffen Grunewald
> said:
> What's the canonical way to keep a nfsroot updated? Would it be sufficient
> to "hold" the dracut* packages so their postinst scripts don't fail?
I always rebuild my nfsroot. If you save the base.tar.xz before
calli
> On Tue, 6 Sep 2016 16:05:04 +0200, Steffen Grunewald
> 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
On Tue, 2016-09-06 at 16:08:57 +0200, Thomas Lange wrote:
> > On Tue, 6 Sep 2016 16:05:04 +0200, Steffen Grunewald
> > 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 notic
> On Tue, 6 Sep 2016 17:13:34 +0200, Steffen Grunewald
> said:
> 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) ...
Because jessie/koeln already includes the
On Tue, 2016-09-06 at 17:17:44 +0200, Thomas Lange wrote:
> > On Tue, 6 Sep 2016 17:13:34 +0200, Steffen Grunewald
> > said:
>
> > I found that you have created a backport for jessie but don't
> distribute that via
> > jessie/koeln?
> > You might tweak the dracut.maintscript
> On Wed, 7 Sep 2016 10:10:20 +0200, Steffen Grunewald
> said:
> Identical in what sense?
The content is identical, only the version numers are different.
> Also, one may want to add [trusted=yes] to the fai-project.org apt
line... (is this already in
> the manual?)
No. T
