Hi,

On 2/11/19 2:15 PM, Marek Marczykowski-Górecki wrote:
> Source: xen
> Severity: normal
> 
> Dear Maintainer,
> 
> Driver domain running Debian buster does not work, because
> xendriverdomain service is missing. Upstream xen have
> /etc/init.d/xendriverdomain (and equivalent xendriverdomain.service)
> that starts `xl devd` process responsible for setting up backend
> devices.
> 
> Source package contains related comment in debian/not-installed:
> 
>     # It is not clear why we have our own init scripts etc. in Debian.
>     # We should probably transition to using the upstream ones and
>     # fix any bugs we encounter.
>     etc/init.d/xendriverdomain
>     etc/init.d/xencommons
>     etc/init.d/xen-watchdog
>     etc/init.d/xendomains
>     etc/default/xencommons
> 
> I think this should be fixed exactly this way - switch to upstream
> startup scripts, instead of Debian-specific ones.
> Also, upstream provide systemd startup files.

Please see:

https://alioth-lists.debian.net/pipermail/pkg-xen-devel/2019-February/007673.html

https://alioth-lists.debian.net/pipermail/pkg-xen-devel/2019-February/007702.html

A number of the things above are currently being done.

If you want to help testing, please subscribe to the team mailing list
for progress updates.

On top of improving the situation, the basic fundamental reason why we
can't have same init scripts in Debian and upstream, is that Debian has
extra machinery to make it possible to have previous and next packages
coinstalled during release upgrades, and we also have to deal with a few
extra special cases because of that. This concept does not exist in the
upstream world.

Nonetheless, there is some attempt going on to bring them closer
together, but as you can read in the above links, not all of that
happened yet.

Thanks,
Hans

Reply via email to