Am Mi., 30. Dez. 2020 um 14:57 Uhr schrieb Marc Haber
<mh+debian-packa...@zugschlus.de>:
>
> Package: debspawn
> Version: 0.4.1-1
> Severity: minor
>
> Hi,
>
> I recently tried to use debspawn build building into a slightly outdated
> image of Debian sid and received a message that dsrun didn't like the
> "--suite sid" option that was given to it. Updating the image solved the
> issue for me.
>
> I suspect that the "outside" debspawn calls things that are inside the
> image, and while the outside debspawn was a 0.4.1, the inside was still
> at 0.4.0 or even older and the interface between the outside and inside
> code changed with the 0.4.0 to 0.4.1 transition. If my suspicion is
> true, than this might also apply to images of testing or stable, but
> without the possibility of just fixing this by updating the image.
>
> I understand that this issue is probably hard to fix, but if it doesn't
> seem possible to just inject the code needed on the inside from the
> outside at run time (therefore forcing them to be in sync, but possibly
> introducing python version issues) then there should be at least a more
> helpful error message than just bombing out with a usage message of an
> internal tool.
Hi!
I'll probably address this properly in future by making this
automatic, but this kind of issue can be fixed relatively easily by
running `debspawn update <suite>` - that will make sure older images
run with newer debspawn versions.
In the long run, this step should either happen in postinst for the
deb package, or, even better, debspawn could auto-update older images
on the first time they are used.
For now though, the debspawn update command has to be run manually (or
via cron scripts - on my system I have a few systemd timer units which
update debspawn container automatically, which is probably why I
hadn't noticed this issue immediately).
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
