Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145

2023-06-27 Thread Giuseppe Sacco
Hi Luca,

Il giorno mar, 27/06/2023 alle 00.04 +0100, Luca Boccassi ha scritto:
> The solution is provided in that bug:
> 
> > Since convert-usrmerge can be run in a chroot on the NFS server maybe it 
> > would be easier to just make it fail if the
> > root is NFS-mounted.
> 
> Just like in the overlay or container cases, instead of converting the
> client, convert the server first.

Thank you for pointing this out, I did not really understand that sentence
until now. So there is a workaround when your NFS server is a Linux machine
and you may use chroot on it, at least.

Thank you,
Giuseppe



Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145

2023-06-26 Thread Luca Boccassi
On Mon, 26 Jun 2023 at 23:45, Giuseppe Sacco  wrote:
>
> Hi Marco,
>
> Il giorno lun, 26/06/2023 alle 23.10 +0200, Marco d'Itri ha scritto:
> > On Jun 26, Giuseppe Sacco  wrote:
> > > Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run
> > > automatically. See #842145 for details.
> > What is the purpose of opening this new bug about the same issue?
>
> The original bug report does not offer any details, nor solution about the
> problem. Moreover, it does mention a problem about an old debian release
> (stretch). This is a quite old bug that probably people think it cannot be
> really still open.
> A new report, about bookworm, may probably be more easily found in an Internet
> search.

The solution is provided in that bug:

> Since convert-usrmerge can be run in a chroot on the NFS server maybe it 
> would be easier to just make it fail if the
> root is NFS-mounted.

Just like in the overlay or container cases, instead of converting the
client, convert the server first.

Kind regards,
Luca Boccassi



Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145

2023-06-26 Thread Giuseppe Sacco
Hi Marco,

Il giorno lun, 26/06/2023 alle 23.10 +0200, Marco d'Itri ha scritto:
> On Jun 26, Giuseppe Sacco  wrote:
> > Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run
> > automatically. See #842145 for details.
> What is the purpose of opening this new bug about the same issue?

The original bug report does not offer any details, nor solution about the
problem. Moreover, it does mention a problem about an old debian release
(stretch). This is a quite old bug that probably people think it cannot be
really still open.
A new report, about bookworm, may probably be more easily found in an Internet
search.

BTW, 7 years ago you wrote that you didn't had any environment to test this.
If this still stands, I may give you access to this machine, if required. Just
send me a private e-mail with an ssh public key. Or, I may try any suggestion
you might have.

Bye,
Giuseppe



Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145

2023-06-26 Thread Marco d'Itri
On Jun 26, Giuseppe Sacco  wrote:

> Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run
> automatically. See #842145 for details.
What is the purpose of opening this new bug about the same issue?

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145

2023-06-26 Thread Giuseppe Sacco
Package: usrmerge
Version: 35
Severity: normal

Dear Maintainer,
while upgrading a diskless system, I've got this message:

root@aristotele:~# dpkg --configure --pending
Configurazione di usrmerge (35)...

Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run
automatically. See #842145 for details.

E: usrmerge failed.
dpkg: errore nell'elaborare il pacchetto usrmerge (--configure):
 il sottoprocesso installato pacchetto usrmerge script post-installation ha 
restituito lo stato di errore 1
Si sono verificati degli errori nell'elaborazione:
 usrmerge


stopping the upgrade. In fact, the upgrade cannot continue with usrmerge 
enable. I tried removing usrmerge
and putting it on hold using dpkg --set-selections, but then "apt upgrade" stop 
again here:

preparativi per estrarre .../usr-is-merged_35_all.deb...


**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
**


dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/usr-is-merged_35_all.deb (--unpack):
 il sottoprocesso nuovo pacchetto usr-is-merged script pre-installation ha 
restituito lo stato di errore 1
Si sono verificati degli errori nell'elaborazione:
 /var/cache/apt/archives/usr-is-merged_35_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


and the whole process cannot go any further.

Bye,
Giuseppe

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages usrmerge depends on:
ii  libfile-find-rule-perl  0.34-3
ii  perl    5.36.0-7

usrmerge recommends no packages.

usrmerge suggests no packages.

-- no debconf information