Bug 329901

Created attachment 175812 [details]
y2logs right after package installation error

Installation failed withthe following message:

"Failed to install required packages."

Ralf, do you know anything about why those packages are not on medias?

A better solution would be not to require 32bit packages on 64bit OS, wouldn't it?

No - that's actually correct requirement, see Bug 64808.

(In reply to comment #2 from Jiri Suchomel)
> Ralf, do you know anything about why those packages are not on medias?
No I have no idea why that has been done. This is really bad. They are at least missing on the x86_64-DVD and the KDE-CD. They seem only to be available on DVD 2 of the DVD9 media.

Probably Lars knows if there is a specific reason for this.

(In reply to comment #4 from Jiri Suchomel)
> No - that's actually correct requirement, see Bug 64808.

Shouldn't this be solved by the dependency solver? A 64 bit OS shouldn't require any 32bit libraries/binaries on it's own (if it does, something is broken). AFAIK 32bit packages have 32bit Requires (e.g. nspluginwrapper) so I don't need 32bit PAM/NSS until I install some 32bit application which uses PAM/NSS.

> Probably Lars knows if there is a specific reason for this.

Well this means that yast ldap setup is broken for x86_64.

Petr (comment 6):

I don't know - if you know of better solution, push the correct one - on the packager's side probably. But now we have a problem with current solution that needs to be fixed first.

The same problem is with missing pam_krb5-32bit...

*** Bug 330674 has been marked as a duplicate of this bug. ***

I don't think this is really critical, because you can skip the LDAP settings
and configure it afterwards in the running system.

But we can provide an online update for x86_64 bit systems, which requires 
pam_krb5-32bit
pam_ldap-32bit
nss_ldap-32bit
for all x86_64 systems, even if they don't use LDAP. So the packages are
installed via online update bevore the yast2 user module starts.

I will prepare a Patchinfo for this asap. Coolo, can you give me a swamp-id,
please? So we can close this as "fixed" for 10.3 when the patch is released.

----

Back to Jiří­: currently the normal pam-packages don't require the *32bit
packages - so this is even a bug in the pam-packages or in the yast2-module. I
think, the 32bit-packages are _only_ needed, if we have other 32bit
applications running on the system. So perhaps we need an additional check (for
example: "32bit pattern selected") before yast requires the 32bit-modules or
the modules should only be installed if they are available (recommended).

I think it is critical because with current situation users with x86_64 just can't use YaST modules to configure LDAP (or Kerberos, which is the other bug; additionally please check also availability of samba-client-32bit and  samba-winbind-32bit). Of course, when the packages will be available via YOU, it should work even during installation because the online update source is registered before.


Please first solve this bug, and than create another one where we could discuss the solution that should be used in YaST after 10.3

(In reply to comment #7 from Jiří­ Suchomel)
> > Probably Lars knows if there is a specific reason for this.
> 
> Well this means that yast ldap setup is broken for x86_64.
> 
> Petr (comment 6):
> 
> I don't know - if you know of better solution, push the correct one - on the
> packager's side probably. But now we have a problem with current solution that
> needs to be fixed first.

One reliable solution could be to make PAM and NSS packages require all other versions possible on a given system (although personally I still don't like the idea of 32bit garbage on primarily 64bit system). The solver would then automatically install both (all) packages. Also checks when creating media should capture situation like this. What do you think, Ralf?

Lars, no I can't start maintenance. You could use 13500 if we get the patchinfo in today

Lars, yet another missing package is pam_thinkfinger-32bit. To summarize, I know of:

pam_thinkfinger-32bit (required by yast2-fingerprint-reader)
pam_ldap-32bit, nss_ldap-32bit (yast2-ldap-client)
pam_krb5-32bit, krb5-32bit (yast2-kerberos-client)
samba-client-32bit, samba-winbind-32bit (yast2-samba-client)

Additionally, these YaST modules require *-x86 packages for ia64, *-64bit packages for ppc64 and *-32bit ones for s390_64. I haven't checked medias for other archs.

Jiri, where is the list of yast requires?

yast2-fingerprint-reader is not part of the installation,no?

> where is the list of yast requires?

The packages are not required for starting the module, they are installed by specific yast module when needed.

> yast2-fingerprint-reader is not part of the installation

No, it is not. But this is not only problem of installation; without the packages such yast module wants to install, it won't work. There's no difference if the module is started during installation or later.

After installation you can register ftp and download just fine.

I want to have an always uptodate list of requires, so I can add the needed packages always on medium.

> I want to have an always uptodate list of requires, so I can add the needed
> packages always on medium.

And where do you have the current list for YaST packages (so I can see what's missing on it)?
Or, Jiri: do you know of anything like that?

The list is here:
http://svn.opensuse.org/viewcvs/yast/trunk/extra-packages?view=markup

The list contains packages for yast2-ldap-client and yast2-kerberos-client.

It misses the packages for yast2-samba-client and yast2-fingerprint-reader (-> my fault).

(I just updated the list to reflect the current status of these YaST modules.)

Patchinfo and missing packages are released (patch-libiniparser-32bit-4488.xml).

FYI: The patch is marked as optional - so it will be selected by default, but users can deselect it.

=> fixed.

*** Bug 344668 has been marked as a duplicate of this bug. ***

*** Bug 346977 has been marked as a duplicate of this bug. ***