Devuan bug report logs - #850
Document Daedalus->Excalibur usrmerge before upgrade in Release Notes

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Package: libsane1
Version: 

When upgrading from Daedalus to Excalibur, the usrmerge configure step fails on following files provided by libsane1 package:

/usr/lib/udev/hwdb.d/20-sane.hwdb
/usr/lib/udev/rules.d/60-libsane1.rules
/usr/lib/udev/rules.d/99-libsane1.rules

When this happens in su/sudo environment, the user can not escalate priviledges anymore because packages providing PAM authentication are not correctly upgraded yet.

Hotfix: Reboot to recovery console and delete mentioned files manually, then:
# apt-get install -f
# apt-get dist-upgrade
and reboot.

Circumvention: Execute "apt-get dist-upgrade" from root shell.

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 850@bugs.devuan.org (full text, mbox, reply):

Control: reassign -1 devuan-project
Control: severity -1 critical
Control: Document Daedalus->Excalibur usrmerge before upgrade in Release Notes

Sachy,

Thanks for taking the time to report this.

I have been unable to reproduce in a daedalus VM with libsane1
installed. However, I suspect it is an ordering thing. I think users will need
to

 1) apt install usrmerge/daedalus
 2) sed -i s/daedalus/excalibur/ /etc/apt/sources.list
 3) apt update
 4) apt dist-upgrade

That is something we will need to specify clearly in the Release Notes.

But there are still merged-usr changes coming through from ceres which may
simplify that process. When we get to the freeze, we can review further.

I don't think there is a bug in libsane1 as such, so reassigning.

Mark

Message #21 received at 850@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Dear Mark,

that can be it - I did not installed usrmerge on Daedalus manually and proceeded directly by updating sources.list.

So its my user error -> sorry for false report.

Totally agree on need to specify the correct steps in big, bold text in the Release notes. Lot of people will ignore/forget it anyway...

Regards,
sachy



V 20240609 1649, Mark Hindley napsal(a):
> Control: reassign -1 devuan-project
> Control: severity -1 critical
> Control: Document Daedalus->Excalibur usrmerge before upgrade in Release Notes
> 
> Sachy,
> 
> Thanks for taking the time to report this.
> 
> I have been unable to reproduce in a daedalus VM with libsane1
> installed. However, I suspect it is an ordering thing. I think users will need
> to
> 
>  1) apt install usrmerge/daedalus
>  2) sed -i s/daedalus/excalibur/ /etc/apt/sources.list
>  3) apt update
>  4) apt dist-upgrade
> 
> That is something we will need to specify clearly in the Release Notes.
> 
> But there are still merged-usr changes coming through from ceres which may
> simplify that process. When we get to the freeze, we can review further.
> 
> I don't think there is a bug in libsane1 as such, so reassigning.
> 
> Mark

[signature.asc (application/pgp-signature, inline)]

Message #26 received at 850@bugs.devuan.org (full text, mbox, reply):

Sachy,

On Sun, Jun 09, 2024 at 08:02:07PM +0200, sachy wrote:
> So its my user error -> sorry for false report.

Absolutely not. A really useful report.

We are all feeling our way through the usrmerge process and it is still unclear
exactly how it will finish. Whatever that it, we need to ensure users are
clearly informed how to navigate it once excalibur is released.

I really appreciate you taking the time.

Best wishes

Mark

Send a report that this bug log contains spam.