Public SourceMage Discussion List

[Ladislav Hagara <ladislav.hagara AT unob.cz>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

if you use test grimoire you have probably found out that I updated 
util-linux, coreutils and shadow.
Because there are a lot of changes I write this email to inform/warn you.

It all started by updating stable branch of util-linux to version 
2.13.1. [1]
In reality it is not an util-linux but an util-linux-ng.
Last util-linux 2.12r is from 2005-09-24 and util-linux-ng was added to 
test grimoire on 2007-07-23 (as test branch of util-linux).
Problem of util-linux-ng is that it do not install /bin/kill.
It is not a problem if you use bash shell because bash contains builtin 
kill.
Our init scripts contains only "kills" without path so builtin kill from 
bash is used.
Problem is if you use shell which do not provide builtin kill, so bug 
14247 was filed [2].

During updating coreutils to 6.10 I decided to use kill from coreutils. [3]
We had not used this kill, we used to patch coreutils to remove it.
Problem of new coreutils is that it no longer installed "su" by default. [4]

I decided to use "su" from package shadow, so I removed our patch for 
removing su from shadow. [5]

Now it needs testing. First problem I run up against was with /etc/pam.d/su.
After "sorcery system-update" I could not use "su" because /etc/pam.d/su 
was missing.
Originally it was installed by coreutils, now it is installed by shadow.
In install queue the shadow was located (by chance) before coreutils so 
shadow installed its pam.d/su and later on coreutils removed it.
I fixed this by [6] I temporarily added coreutils to DEPENDS of shadow 
to prevent removing of pam.d/su.

I am sure other problems will emerge.
Just now I found out that "su" works differently.
If I am login as ordinary user and use "su" there are some problems with 
PATH and root (after this su) can not run sorcery commands.
If I run "su -" all works like before.
No idea if this is a bug or feature of su from shadow.

Please, if you have problems with this update, write it to this list so 
we can discuss it.
I have no idea if for example selinux suport is not broken.
Some discussion already has come up in sm-commit mailing list. [7]

Thanks.

[1] 
http://scmweb.sourcemage.org/gitweb.cgi?p=smgl/grimoire.git;a=commit;h=2f3c4faab05126323515eb880ad2d63cfcff1849
[2] http://bugs.sourcemage.org/show_bug.cgi?id=14247
[3] 
http://scmweb.sourcemage.org/gitweb.cgi?p=smgl/grimoire.git;a=commit;h=07ff8e4da5963d01ad6beacfe995a5a83ad3ad82
[4] 
http://lists.gnu.org/archive/html/coreutils-announce/2008-01/msg00001.html
[5] 
http://scmweb.sourcemage.org/gitweb.cgi?p=smgl/grimoire.git;a=commit;h=1f352cf08cbc9a7a929ddaeab9089c4166b695f9
[6] 
http://scmweb.sourcemage.org/gitweb.cgi?p=smgl/grimoire.git;a=commit;h=cc401f4df42da5f17211eaf333dde26af1f598a1
[7] https://lists.ibiblio.org/sympa/arc/sm-commit/2008-January/014919.html

- --
Ladislav Hagara
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHmTlrxNd3hwNeF68RAkg/AJ0de7wHYseJ2dPHwKTZicghOu33+ACgkgmx
uXrtIOmiUbVyx4aR5lARPqM=
=cAuA
-----END PGP SIGNATURE-----