On Mon, 13 Jan 2014 09:13:18 +1100 NeilBrown <neilb@suse.de> wrote:
On Mon, 06 Jan 2014 13:41:32 +0100 Tomáš Chvátal <tchvatal@suse.cz> wrote:
..... State: accepted 2013-12-10T20:59:43 jeff_mahoney Comment: i'm not thrilled with this, but it seems necessary.
History: new 2013-12-10T20:59:16 jeff_mahoney declined 2013-12-10T03:10:06 jeff_mahoney new 2013-12-10T02:52:21 neilbrown
filesystems:e2fsprogs has the new e2fsprogs-mini.spec etc. We still need someone to osc linkpac filesystems e2fsprogs filesystems e2fsprogs-mini and to propagate that to openSUSE:Factory etc. Who can do that?
NeilBrown
For the Factory it does it by itself.
For the filesystems I shall do it now.
Thanks for creating filesystems:e2fsprogs-mini.
It doesn't seem that Factory has done anything by itself. Do we have to wait a particular amount of time, so does it need to be reminded or something? ?? Any help anyone could provide in moving this along would be greatly appreciated.
NeilBrown
I wondered what had happened about this but noticed that SLE:12 seem to have libtirpc compiled correctly so maybe I didn't care. But then I realised that I did care... So I checked the opensuse-packaging archive (I'm not subscribed and some mail clients don't reply properly to some lists) and found from Stephan Kulow http://lists.opensuse.org/opensuse-packaging/2014-01/msg00043.html ------ I have no idea what the actual purpose of this change is actually. libtirpc already links krb5 in factory - wasn't that your goal? ------ If you wonder why I didn't reply with my goal, it is because I never saw the email - sorry. I then went to find out what had changed to allow things to work now and found in pam.spec (in openSUSE:Factory:pam and SUSE:SLE-12:GA:pam) #BuildRequires: pkgconfig(libtirpc) where there used to be BuildRequires: pkgconfig(libtirpc) There is no mention of this change in pam.changes and I cannot bring myself to try fighting with "osc log" as it has always disappointed in the past. I don't cannot assign blame (not that blame serves much purpose, so just as well). So it seems that the change from 2.5 years ago: Mon Jun 27 15:29:11 CEST 2011 - kukuk@suse.de - Update to version 1.1.4 * pam_securetty: Honour console= kernel option, add noconsole option * pam_limits: Add %group syntax, drop change_uid option, add set_all option * Lot of small bug fixes * Add support for libtirpc - Build against libtirpc has been partly reverted. Are you OK with that Thorsten?? But back to Stephan's question: what is the actual purpose of e2fsprogs-mini? The purpose was to allow the build dependency cycle: https://build.opensuse.org/project/repository_state/openSUSE:Factory/standar... to be manageable *without* breaking pam. pam needs libtirpc libtirpc (now) need krb5-mini-devel krb5-mini-devel needs libcom_err-devel which pulls in e2fsprogs which in turn pulls in makeinfo and tex and .... So the purpose of e2fsprogs-mini was that krb5-mini-devel could depend on libcom_err-mini-devel which would not have that 'tex' dependency. So if Thorsten is happy with pam not supporting libtirpc I guess we can leave Factory and SLE12 as they are, and it would be really nice if those same fixes could get into openSUSE:13.1, because secure NFS is still broken in that release. If, however, Thorsten (or anyone) thinks that pam really needs libtirpc support, then I would ask that - e2fsprogs-mini be propagated to openSUSE:Factory - krb5-mini be changed to depend on libcom_err-mini-devel - pam be un-broken so that it builds with libtirpc again. Thanks, NeilBrown