Hi, On Thu, 01 Oct 2015 at 17:53:21 +0100, Gianfranco Costamagna wrote: > Hi, I could own the bug no problem, just I would like to avoid > stealing the package to Helmut! Fair enough :-) > - dpkg shows that a default configuration file has changed, asking me how to proceed This is because /etc/default/dropbear (from dropbear-run) is modified by the postinst script to add NO_START=1 if the OpenSSH server is installed. (In fact ‘d/dropbear-run.dropbear.default’ is empty and content is added by the postinst script.) FWIW, dropbear have had this behavior since 2007 at least (the starting year of its git repo). I wish I knew a better way achieve the same thing. > - there is a lintian error about conf files in usr (that might be > mounted in read only mode) (this is an old issue) Yes, this is a regression from 2014.64-1. In the first version of my packages (until 5 days ago) I used to no longer mark this file as a conf file, but you pointed out that you couldn't upgrade from Wheezy and after further investigation it seems that dpkg chokes on the double change of package name (dropbear vs. dropbear-initramfs) and file name (/usr/… file moved to /etc + creation of a symlink in /usr). That's why I propose to proceed in two steps and keep that lintian error until Strech. (See the lintian override comment, or message #117 of this bug.) > since I'm unsure about the first, and since I need to dpkg -f the > files, I would like to ask you to go for experimental and wait for > some automatic piuparts test Sure :-) > (or manual of course). > > I know I asked you to go for unstable, but I'm not confident enough > about my review > > (and I can't run piuparts successfully). I tried hard to make piupart happy, but wasn't successful at it either. The further I got was to upgrade seamlessly (/etc/default/dropbear aside) from clean (short of dialog, busybox, and initramfs-tools) Jessie chroot. And ensure that nothing is remaining after removal. Cheers, -- Guilhem.
Attachment:
signature.asc
Description: PGP signature