Welcome to SparkyLinux forumsZapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl
Started by TRon, January 11, 2023, 02:30:22 AM
Quote from: TRon on January 11, 2023, 02:30:22 AM[....] A short while ago useradd was updated, which contained a lot of warning information during installation. I would like to know the details.
apt changelog adduser
Quote from: TRon on January 11, 2023, 02:30:22 AM[....] Today "something" (I can't even say what for sure) was bypassing the APT update manager and issued a load of warnings during about that during installation. Also for that I would like to know the details.
grep "upgrade" /var/log/dpkg.log
grep "install" /var/log/dpkg.log
apt show adduser
Quote from: TRon on January 12, 2023, 03:48:14 AMThank you very much for your quick reaction AxL.It was indeed the package adduser (and not the command useradd) that I have wrongfully mentioned. My apologies and thank you for the correction.The way in which you showed how to provide more information proofed to be informative (thank you for that, as I did not know them all). I will use those solutions more often.
Quote from: TRon on January 12, 2023, 03:48:14 AM[....] Alas, during 'installation' of the packages I mentioned (by using your commands I can now take an educated guess that the second one that emitted warnings was the update for dpkg) the sparky-upgrade shell emitted warnings that I (after the fact) can't seem to reproduce.I assume (?) this is because the package manager or package itself detects that during installation/upgrade thereseem to be a "issue" and/or "situation" that deserves enough attention from the user to issue a warning (or a set of warnings).So far, the only place where such a warning can be seen (to my knowledge) is the sparky-upgrade-shell itself ?
Quote from: TRon on January 12, 2023, 03:48:14 AM[....] It is in a similar fashion that sometimes the sparky-upgrade shell asks to choose from a selection (yes/no/ignore, select a number of your choice) during the installation of a package. Also there I seem unable to reproduce the choice (and what choices where presented) that was made during the installation process.
Quote from: TRon on January 12, 2023, 03:48:14 AMI understand the importance of the release notes of a package/update but unfortunately those (for me, perhaps my noobness) do not shed a light on what was so important to inform me about when the upgrade-shell ran.So please forgive me when I repeat the question if it is possible to reproduce or if there is any more information available about what the sparky-upgrade tool (e.g. package manager) emits in the shell during an upgrade/installation ?
Log started: 2023-01-10 12:10:06(Reading database ... 199219 files and directories currently installed.)Preparing to unpack .../archives/adduser_3.130_all.deb ...Unpacking adduser (3.130) over (3.129) ...Setting up adduser (3.130) ...Installing new version of config file /etc/adduser.conf ...Installing new version of config file /etc/deluser.conf ...[....]
Quote from: AxL on January 12, 2023, 07:15:54 PMIf instead of using sparky-upgrade. You simply use a terminal with sudo apt update && sudo apt dist-upgrade (Personally, I always upgrade this way. I have never used sparky-upgrade). You could also see those messages/issues you mention (only if the package has to inform you, about some important change or modification).
Quote from: AxL on January 12, 2023, 07:15:54 PMIn this case you mention, it is because the package update will overwrite the configuration files/options. And it gives you the option to keep your custom configuration.
Quote from: AxL on January 12, 2023, 07:15:54 PMYou can check something else in:Code Select Expand/var/log/apt/history.log or /var/log/apt/term.log
/var/log/apt/history.log or /var/log/apt/term.log
Preparing to unpack .../dpkg_1.21.17_amd64.deb ...Unpacking dpkg (1.21.17) over (1.21.13) ...Setting up dpkg (1.21.17) ...␛[1mdpkg␛[0m: ␛[1;33mwarning␛[0m: This system uses merged-usr-via-aliased-dirs, going behind dpkg's␛[1mdpkg␛[0m: ␛[1;33mwarning␛[0m: back, breaking its core assumptions. This can cause silent file␛[1mdpkg␛[0m: ␛[1;33mwarning␛[0m: overwrites and disappearances, and its general tools misbehavior.␛[1mdpkg␛[0m: ␛[1;33mwarning␛[0m: See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>.
Quote from: TRon on January 13, 2023, 06:21:32 AMThank you again very much for your reply AxL.
Quote from: TRon on January 24, 2023, 10:55:49 AM[....] Thank you very much for mentioning those tools. They are really a great addition to your other suggestions and offer exactly some of the (additional) details that I am/was looking for.
View the most recent posts on the forum