On Mon, Apr 14, 2025 at 10:29:59AM +0200, Michael J Gruber wrote: > Rajeesh K V venit, vidit, dixit 2025-04-14 06:19:33: > > > During the upgrade I've noticed this message output in the console: > > > /usr/sbin cannot be merged, /usr/sbin/arptables points to > > > /etc/alternatives/arptables > > > I assume it's related to > > > https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin but I'm not > > > sure if anything needs to be fixed. > > > > I have upgraded a system yesterday and noticed similar ‘/usr/sbin > > cannot be merged’ error due to /usr/sbin/extlinux. Removed > > syslinux-extlinux after upgrade. > > It's not an error, just an informational message about something that > is to be expected. Maybe the wording isn't clear enough? It seems the message should be improved. This is not the first time this has come up. be enough? We can't write a lot of text here, because scriptlet output should be brief. Would changing "cannot be merged" to "cannot be merged yet" help? I filed [1] with that. > > How do one attempt to do sbin merge manually? I've read the change > > proposal, but it doesn't seem to mention if there's any command/tool > > to attempt the merge. > > According to the proposal, scope, 1.3, a posttrans scriptlet in > filesystem checks that automatically and retries the merge. > > `rpm -q --scripts filesystem` confirms that the scriptlet is in place. > If you really want to you can extract the posttrans scriptlet from there > and run it through lua. There is no need to AFAICT. > > A simpler check is `find /usr/sbin /usr/local/sbin -type f` which shows > you everything that is *not* symlinked already. > > `ls -l /usr/local/sbin` shows me that it is a directory symlink already, > whereas `ls -l /usr/sbin` shows me many symlinks plus the files from the > find command. Once all packages have adjusted and there are only > symlinks inside that subdir, the posttrans scriptlet will replace the > dir itself by a symlink (as it has done for `/usr/local/sbin` already). Yes, exactly. There is still a bunch (~100) of packages with files under /usr/sbin. I actually sent an email today [2] about this before stumbling on this thread. The most common reason is FTBFS packages. If we rebuild those, the majority of cases will be fixed. Zbyszek [1] https://src.fedoraproject.org/rpms/filesystem/pull-request/23 [2] https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/AORJTGITL7MJJBSPXFFMZGWXENLCVYDR/ -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
