Comment # 5 on bug 1204434 from C J

Adding schubi@suse.com as he was responsible for the pam update that broke
this, so that he can tell us if he thinks if pam is the responsible package or
if this happened elsewhere.

Nothing was in the pam package changelog and I have also looked into the
factory mailing list snapshot details. Nothing.

So I guess the changelog was not properly done by upstream?

-------------

When a package update introduces changes that will break system config files I
think this should happen:

-> Zypper should spit out a RED warning that package XYZ introduces changes
that might break /etc/environment, etc...

This way we can know where to look.

(complicated because it requires upstream to inform of the change, + spec file
&  zypper awareness).

So let's start with with a new SPEC or OBS Changelog section called i.ex :
CLI/API/ABI breaking changes.

-> zypper can then spit this out as a warning in RED.

Thanks.