Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-06-22 Thread Andreas Beckmann
On 14/06/2023 19.04, Andreas Beckmann wrote: I've prepared a NMU with three changes: Uploaded to DELAYED/10: debianutils (5.7-0.5) unstable; urgency=medium . * Non-maintainer upload. * update-shells: Do not create duplicate entries in /etc/shells. * update-shells: Manage

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-06-14 Thread Andreas Beckmann
Control: unmerge -1 Control: reassign -1 debianutils 5.7-0.4 Control: affects -1 + src:9base Control: tag -1 patch pending On 13/06/2023 07.26, Helmut Grohne wrote: The entry is added by /usr/lib/usrmerge/convert-etc-shells (which is the policy violation this bug has been merged into). The

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-06-12 Thread Helmut Grohne
Hi Andreas, On Mon, Jun 12, 2023 at 07:40:32PM +0200, Andreas Beckmann wrote: > > It's a 12 byte difference. That's not 9base's entries. What you see here > > is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it. > > Thus force-merging. > > No, it's "/usr/bin/rc\n". Huh! I stand

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-06-12 Thread Andreas Beckmann
Now I'm really confused: I start with an unmerged sid chroot, install 9base there. Then I remove /etc/unsupported-skip-usrmerge-conversion and install usrmerge. Now /etc/shells contains # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-06-12 Thread Andreas Beckmann
On 09/05/2023 16.55, Helmut Grohne wrote: Control: forcemerge 1033167 -1 Control: affects 1033167 + 9base Hi Andreas, On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package leaves modifications in /etc/shells after upgrading from

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-05-09 Thread Andreas Beckmann
On 09/05/2023 16.55, Helmut Grohne wrote: 9base/bookworm no longer does, because it now uses dpkg-triggers to Good to know that there is a better way nowadays ... >From the attached log (scroll to the bottom...): 0m45.2s ERROR: FAIL: After purging files have been modified: /etc/shells

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-05-09 Thread Helmut Grohne
Control: forcemerge 1033167 -1 Control: affects 1033167 + 9base Hi Andreas, On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package leaves modifications > in /etc/shells after upgrading from bullseye to bookworm and purging the >

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

2023-05-09 Thread Andreas Beckmann
Package: 9base Version: 1:6-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package leaves modifications in /etc/shells after upgrading from bullseye to bookworm and purging the package. 9base/bullseye called