mintupgrade update results in "The unit files have no installation config..." #122
Description
Distribution
Linux Mint 22.1
Package version
Cinnamon 6.4.8
Graphics hardware in use
Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
Frequency
Always
Bug description
I manage my mother's computer remotely over SSH. I typically perform an aptitude update, aptitude upgrade and aptitude safe-upgrade. I prefer aptitude because it seems to have the best solver for dependency problems of all the package manager tools.
Today I noticed the following during the update. It looks like there is something a bit sideways for the unit files for mintupdate.
Package manager: /bin/aptitude
...
Current status: 2 (+2) upgradable, 85981 (+48) new.
The following packages will be upgraded:
mint-upgrade-info mintupdate
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,532 kB of archives. After unpacking 24.6 kB will be used.
Get: 1 http://packages.linuxmint.com xia/main amd64 mint-upgrade-info all 1.2.9 [933 kB]
Get: 2 http://packages.linuxmint.com xia/main amd64 mintupdate all 7.0.7.1 [598 kB]
Fetched 1,532 kB in 1s (2,071 kB/s)
(Reading database ... 397828 files and directories currently installed.)
Preparing to unpack .../mint-upgrade-info_1.2.9_all.deb ...
Removing previous content in /usr/share/mint-upgrade-info...
Unpacking mint-upgrade-info (1.2.9) over (1.2.8) ...
Preparing to unpack .../mintupdate_7.0.7.1_all.deb ...
Unpacking mintupdate (7.0.7.1) over (7.0.7) ...
Setting up mint-upgrade-info (1.2.9) ...
Setting up mintupdate (7.0.7.1) ...
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Processing triggers for libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.4) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1+mint1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Steps to reproduce
aptitude update && aptitude upgrade && aptitude safe-upgrade
Expected behavior
Clean installation of mintupdate.
Additional information
mintupdate version is 7.0.7.1.
sudo apt-get install --reinstall mintupdate can trigger the issue, too.
$ sudo apt-get install --reinstall mintupdate
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/598 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 397829 files and directories currently installed.)
Preparing to unpack .../mintupdate_7.0.7.1_all.deb ...
Unpacking mintupdate (7.0.7.1) over (7.0.7.1) ...
Setting up mintupdate (7.0.7.1) ...
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Processing triggers for libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.4) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1+mint1) ...
Processing triggers for man-db (2.12.0-4build2) ...