[Warning] remaster breakage

[Forum Admin anticapitalista]

As from this date (end of 2022 Greek time) an update of Debian package adduser followed by remaster will lead to a message like demo user is not allowed.
You can upgrade all apps except adduser.
Same for 64 and 32 bit.
Installed sid systems do not seem to have this issue.
Not sure if installing adduser and then persist will also break.

Added: To revert

1. Use the rollback option by typing rollback at boot menu
2. In a terminal sudo apt-mark hold adduser
3. sudo apt-update && sudao apt dist-upgrade (you should see a message showing that adduser is being held)
4. Remaster as usual

• This topic was modified 4 months, 1 week ago by anticapitalista. Reason: added revert information

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member marcelocripe]

Helpful

Up

0

::

You can upgrade all apps except adduser.

Thank you very much for letting us know about this issue on ‘adduser’.

Could you please let us know which is the problematic version of ‘adduser’?

Have a good new year.

– – – – –

You can upgrade all apps except adduser.

Muito obrigado por nos avisar sobre este problema no ‘adduser’.

Por favor, você poderia nos informar qual é a versão problemática do ‘adduser’?

Tenha um bom ano novo.

[Forum Admin anticapitalista]

Helpful

Up

1

::

Could you please let us know which is the problematic version of ‘adduser’?

The one that will be upgraded in Debin sidd

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member ile]

Helpful

Up

1

::

marcelocripe
adduser (3.130) unstable; urgency=low

deluser’s –no-preseve-root option is deprecated, and it will be
removed after Debian bullseye. deluser will in the future completely
refuse to delete the root user. If you want to delete root, you need
to use other tools.

We are planning to deprecate and remove the GROUPHOMES and LETTERHOMES
configuration options. They help big installations, but nowadays those
installations are probably using a directory service like LDAP and Active
Directory to manage their users and do not use adduser anyway. If you’re
using one of these options and want them to stay, please write that to
#1025623 and let us know. Some kind of help and committment, for example
verified autopkgtest scripts, would be appreciated and make it easier for
us to keep the feature around.

We are planning to deprecate and remove the QUOTAUSER configuration
option. If you’re using this, please write that to #1026898 and let us
know. Some kind of help and committment, for example verified autopkg
testscripts, would be appreciated and make it easier for us to keep
the feature around.

There have been some changes to –disabled-password and –disabled-login,
documented in adduser(8). Maintainers using these options with adduser
–system in their maintainer scripts should review their scripts and
check whether the default is enough and the options can be removed.

The –gecos option is being renamed to –comment to get aligned with
passwd’s terminology. –gecos will continue to work throughout the
bookworm cycle.

The NEWS entry for 3.124, shown below, was added to give more explanation
about the addition of the users group as a supplementary group to a newly
created user. This change was inconsistently documented in adduser(8),
this inconsistency was fixed in adduser 3.130.

— Marc Haber <mh+debian-packages@zugschlus.de> Sun, 25 Dec 2022 17:11:31 +0100

adduser (3.124) unstable; urgency=medium

As pointed out in #678615, adduser has behaved somewhat inconsistently
in the past, using the users group (GID 100) only if USERGROUPS was set
to the non-default ‘no’. This has been changed as documented in
adduser.conf(5): If USERGROUPS is yes, the newly created user will now
be added as a supplementary group; if USERGROUPS is no, users will be the
primary group. If you want to restore the old behavior, set USERGROUPS=yes,
leave USERS_GROUP empty and set USERS_GID to “-1”.

(this NEWS entry has been added retroactively with adduser 3.130)

[Member Xunzi_23]

Helpful

Up

0

::

Thanks for info,
lucky I gave a probable windoze refugee an older demo version.

• This reply was modified 4 months, 1 week ago by Xunzi_23.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

As from this date (end of 2022 Greek time) an update of Debian package adduser followed by remaster will lead to a message like demo user is not allowed.

Thanks for the warning.
However I am not clear how this breakage shows up in practice.
I have upgraded adduser to version 3.130 before I saw this warning and subsequently remastered. I do not seem to notice any issue in result. Under what condition will this issue surface?
My system is Full antiX 22 SID runit. Default user is demo.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

This has happened to me on 2 frugal installs of antiX-sid (one 32bit the other 64bit).
Neither are running persistence.
I do a General remaster.
User is demo and the default passwords have not changed.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

I appreciate response and thanks for the added rollback solution to the original post.
However what I am not clear on is how to make this issue show up, how to make it manifest itself. In my case I am not able to recreate symptoms so far. All seems to work normally, having remastered after upgrade and rebooted such remastered SID antiX.
The only difference I have from default that password for demo had been changed before to other than password ‘demo’.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

olsztyn wrote:

…
The only difference I have from default that password for demo had been changed before to other than password ‘demo’.

Perhaps this is the difference.
Do you have any persist files? rootfs/homefs

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

Perhaps this is the difference.
Do you have any persist files? rootfs/homefs

No, I do not have any persistence files. Running without persistence.
Should I create persistence files so I can see this issue?

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

@olsztyn – can you remember if you chose to keep the old adduser.conf file when prompted?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

@olsztyn – can you remember if you chose to keep the old adduser.conf file when prompted?

I do not remember that exactly to be sure. But good likelihood is that I did keep the old adduser.conf, not replaced. This is my conjecture at this point. What should I see in adduser.conf to identify the change? I do not think I have the prior version to compare.

Update:
Just checked the timestamp of adduser.conf. It is old. 2022-10-17. Looks like the original one.

• This reply was modified 4 months, 1 week ago by olsztyn.
• This reply was modified 4 months, 1 week ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

The older adduser.conf has entries that have not been commented eg

DHOME=/home rather than #DHOME=/home

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

The older adduser.conf has entries that have not been commented eg

DHOME=/home rather than #DHOME=/home

Confirmed. I have the original adduser.conf. Not replaced.
I will comment them out and remaster to see the issue.

Update:
Commented out DHOME, GROUPHOMES and LETTERHOMES, remastered with the new adduser.conf, rebooted and I still do not see any malfunctioning.
Adduser version is 3.130. Remaster still appears to start fine.
Running out of ideas how to create this issue.

• This reply was modified 4 months, 1 week ago by olsztyn.
• This reply was modified 4 months, 1 week ago by olsztyn.
• This reply was modified 4 months, 1 week ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member marcelocripe]

Helpful

Up

0

::

Ile, thank you very much for your detailed explanations.

– – – – –

Ile, muito obrigado por suas explicações detalhadas.

[Author]

Posts