Still the first error occurred upgrading packages in my NomadBSD — Problematic file: /usr/local/bin/chattr. The full story:
Installing updates...
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity...
The following 1 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
e2fsprogs-nobootfsck: 1.46.4_1 -> 1.46.5
Number of packages to be upgraded: 1
[1/1] Upgrading e2fsprogs-nobootfsck from 1.46.4_1 to 1.46.5...
pkg: e2fsprogs-nobootfsck-1.46.5 conflicts with e2fsprogs-1.46.2 (installs files into the same place). Problematic file: /usr/local/bin/chattr
Command finished with errors!
I have no idea how to check and fix this chattr (11728 bytes, 9 Oct 2021). I do not remember the purpose of e2fsprogs-nobootfsck, perhaps it is required by db5 upgraded from 5.3.28_7 to 5.3.28_8 today with the warning:
The db5 port currently does not have a maintainer. As a result, it is
more likely to have unresolved issues, not be up-to-date, or even be removed in
the future. To volunteer to maintain this port, please create an issue at:
https://bugs.freebsd.org/bugzilla
More information about port maintainership is available at:
https://docs.freebsd.org/en/articles/contributing/#ports-contributing
===> NOTICE:
This port is deprecated; you may wish to reconsider installing it:
EOLd, potential security issues, maybe use db18 instead.
It is scheduled to be removed on or after 2022-06-30.
So I installed the new db18 successfully and was going to remove the old db5, but refrained from uninstalling also six depended apps: apr, evolution-dtat-server, libreoffice, pidgin, redland, and serf.
Still nothing crashed, should I do not worry or can I do something?
I had the same pkg upgrading issue. The command I used was
sudo pkg upgrade -f e2fsprogs-nobootfsck
to force the upgrade. No issues as of yet. I did remove pidgin previously as I no longer use it anyways. So far no issues. I did upgrade to db18 as well.
Just uninstalled Pidgin 2.14.8_1 with pidgin-otr: 4.0.2_1, and tried to upgrade e2fsprogs-nobootfsck from 1.46.4_1 to 1.46.5 — unsuccessfully, the same Problematic file: /usr/local/bin/chattr
Oh, DSBMC removed! With dsbmc-cli, dsbmc.desktop, etc. Although locate finds them, while database is still not re-indexed.
I tried to install dsbmc, yet it requires e2fsprogs, removed by e2fsprogs-nobootfsck. Octopkg:
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 5 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
dsbmc: 1.2_1
dsbmc-cli: 0.4
dsbmd: 1.11.4
e2fsprogs: 1.46.5
fusefs-ext2: 0.0.10_3
Number of packages to be installed: 5
Fetching [1/3] dsbmc-cli-0.4.pkg
Fetching [2/3] dsbmc-1.2_1.pkg
Fetching [3/3] dsbmd-1.11.4.pkg
Checking integrity...
- e2fsprogs-1.46.5 conflicts with e2fsprogs-nobootfsck-1.46.5 on /usr/local/bin/chattr
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 7 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
e2fsprogs-nobootfsck: 1.46.5
Installed packages to be REINSTALLED:
pkg-1.17.5
Number of packages to be removed: 1
Number of packages to be reinstalled: 1
[1/7] Deinstalling e2fsprogs-nobootfsck-1.46.5...
If and only if you are deleting e2fsprogs forever,
remember to delete /usr/local/etc/mke2fs.conf .
[1/7] Deleting files
[32m
[m
[32m[m
[2/7] Installing e2fsprogs-1.46.5...
===========================================================================
Warning: installing mke2fs.conf in /usr/local/etc/mke2fs.conf.e2fsprogs-new
Check to see if you need to update your /usr/local/etc/mke2fs.conf .
[3/7] Installing fusefs-ext2-0.0.10_3...
[4/7] Installing dsbmd-1.11.4...
[5/7] Reinstalling pkg-1.17.5...
[6/7] Installing dsbmc-cli-0.4...
[7/7] Installing dsbmc-1.2_1...
Building cache database of MIME types
Message from e2fsprogs-1.46.5:
--
Note: this is a modified version of the e2fsprogs package, not the official
package. Report all building and run-time trouble that originates in the
package to the port maintainer, mandree@FreeBSD.org.
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
Then I tried to install e2fsprogs-nobootfsck, but it removed e2fsprogs and dsbmc:
The following 7 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
dsbmc: 1.2_1
dsbmc-cli: 0.4
dsbmd: 1.11.4
e2fsprogs: 1.46.5
fusefs-ext2: 0.0.10_3
New packages to be INSTALLED:
e2fsprogs-nobootfsck: 1.46.5
Installed packages to be REINSTALLED:
pkg-1.17.5
Number of packages to be removed: 5
Number of packages to be installed: 1
Number of packages to be reinstalled: 1
[1/7] Deinstalling dsbmc-1.2_1...
[2/7] Deinstalling dsbmc-cli-0.4...
[3/7] Deinstalling dsbmd-1.11.4...
[4/7] Deinstalling fusefs-ext2-0.0.10_3...
[5/7] Deinstalling e2fsprogs-1.46.5...
If and only if you are deleting e2fsprogs forever,
remember to delete /usr/local/etc/mke2fs.conf .
[32m
[m
[6/7] Reinstalling pkg-1.17.5...
[7/7] Installing e2fsprogs-nobootfsck-1.46.5...
===========================================================================
Warning: installing mke2fs.conf in /usr/local/etc/mke2fs.conf.e2fsprogs-new
Check to see if you need to update your /usr/local/etc/mke2fs.conf .
Building cache database of MIME types
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
Message from e2fsprogs-nobootfsck-1.46.5:
--
Note: this is a modified version of the e2fsprogs package, not the official
package. Report all building and run-time trouble that originates in the
package to the port maintainer, mandree@FreeBSD.org.
Perhaps e2fsprogs-nobootfsck does not tolerate DSBMC.
From what I see, e2fsprogs and the packages that depend on it installed just fine. Is there any package you try install that depends on
e2fsprogs-nobootfsck?
Perhaps e2fsprogs-nobootfsck is still independent, sorry, I do not know how to check dependency for sure.
Uninstalled e2fsprogs-nobootfsck and then reinstalled DSBMC (with dsbmc-cli, dsbmd, fusefs-ext2, e2fsprogs) successfully, but DSBMC refuses to start with the same fatal error warning: No such file or directory.
I guessed that is because dsbmd.socket is not set up yet. So I rebooted my NomadBSD, and indeed — all the files, menus, and DSBMC icon are in place now.
pkg takes care of dependencies. It doesn’t allow you to install a package without making sure its dependencies are installed as well, unless you use some special flags. If pkg doesn’t exit with an error, you don’t have to do anything.
I thought you ran into a rare case where package X requires package Y, which conflicts with package Z.
