TODO

Buster, Feb 1

Todays big topic: init scripts

• Review init scripts in the package and see if we can drop modified old versions and use upstream ones. related Also touches the systemd discussion, and also related 799986 selinux and tmpdirs and systemd
• xen-tools: warning: something called deprecated script /usr/lib/xen-common/bin/xen-toolstack -> this is from the init scripts see knorrie/init branch
• today 851654 xenconsoled gets shut off unexpectedly
• depend on network start: 798510 xendomains at boot dependencies
• check and close, by design 506407 /etc/init.d/xend doesn't terminate all processes -> related: /etc/init.d/xen stop/restart does not touch xenstored. Is this 'by design'? -> Yes, otherwise you lose state.
• Hans: Improve confusing "[warn] Not running within Xen or no compatible utils ... (warning)." in init script.
• 903494 xendomains script not working properly this looks like a defect, but I have no experience with this myself
• 826871 boot dependency with nfs-kernel-server

The rest:

• 15m Try out the new xen grub config blah and confirm it really works as expected (tm).
• 15m Write NEWS about several things: What to do for the meltdown/spectre ongoing things? .. .. what other things do we want to have in NEWS?
• Tracker: look at lintian errors, reproducability etc?
• today bash autocompletion clearly doesn't work

Interesting things in the build output:

• #23 dpkg-shlibdeps: warning: symbol [...] found in none of the libraries
• #22 dpkg-shlibdeps: warning: package could avoid a useless dependency [...]
• #21 (closed) dpkg-gensymbols: warning: some libraries disappeared in the symbols file: libxentoolcore-4.10.so.1

Interesting bts to look at:

• today 912381 pygrub is borken
• today 862236 Ian says: "I think such a change is buster material."

If we're really bored:

• 866380 xen-bugtool: missing xen.util python module

Other

• 4.8 900746 xl causes a Segmentation fault got pinged
• Discussion: what to do with non trivial bug reports? Debian Xen team people do not cover all use cases by their own usage (and can't test all of it). How to best filter/prepare for upstream? How to work together with upstream (there's no support process there...)?

Upstream

• gnttab max frames... -> reproduce, use log_once to improve upstream error reporting when it happens, send patch upstream.
• tools-xs-test-hardening -> Debian doesn't need the patch now, ask ubuntu to upstream it.
• default bridge spoofing -> Make upstream patch to just remove all of it to force a discussion? At least exclude for ovs.