core/shadow/.md5sum

05a85f1ea6bf26aec66a91b5f98a51b0  login.defs
be8f69c2701118093af3d7f3bc02af16  pwck
3c3a1fbfae01534de2c8bbd566200dce  shadow-4.1.0.patch
dd6ca3ac424b447962d7a7af923b7bda  shadow-4.1.0.tar.bz2
shadow: update to 4.1.0 With 4.1.0-1 the default behaviour of shadow is restored and a patch from Gentoo [1] removed. It may be debatable whether useradd should create a new group with the same name as the username if the primary group is not specified with -g, or not. For now we will follow the CRUX principle to use vanila packages whenever possible. However, there are plans to change something in that direction [2]. [1] http://bugs.gentoo.org/show_bug.cgi?id=128715 [2] http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2007-December/006252.html 2008-01-29 10:31:30 +01:00			`05a85f1ea6bf26aec66a91b5f98a51b0 login.defs`
create branch for 2.2 2006-02-23 16:26:10 +01:00			`be8f69c2701118093af3d7f3bc02af16 pwck`
shadow: update to 4.1.0 With 4.1.0-1 the default behaviour of shadow is restored and a patch from Gentoo [1] removed. It may be debatable whether useradd should create a new group with the same name as the username if the primary group is not specified with -g, or not. For now we will follow the CRUX principle to use vanila packages whenever possible. However, there are plans to change something in that direction [2]. [1] http://bugs.gentoo.org/show_bug.cgi?id=128715 [2] http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2007-December/006252.html 2008-01-29 10:31:30 +01:00			`3c3a1fbfae01534de2c8bbd566200dce shadow-4.1.0.patch`
			`dd6ca3ac424b447962d7a7af923b7bda shadow-4.1.0.tar.bz2`