[opensuse-factory] harcoded requires to module-init-tools

older
[opensuse-factory] Where tom get...

Cristian Rodríguez

2 Mar 2012 2 Mar '12

18:18

Hi: There are hardcoded requires on package module-init-tools Problem: kmod-compat-5-1.2.x86_64 conflicts with module-init-tools provided by module-init-tools-3.15-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of module-init-tools-3.15-1.2.x86_64 deinstallation of pm-utils-1.4.1-16.1.x86_64 deinstallation of mpt-firmware-1.0-249.2.noarch deinstallation of kernel-desktop-3.3.rc5-2.1.x86_64 deinstallation of ipw-firmware-9-11.3.noarch deinstallation of mkinitrd-2.7.0-52.1.x86_64 deinstallation of pm-utils-ndiswrapper-1.4.1-16.1.x86_64 deinstallation of bootsplash-branding-openSUSE-12.2-4.18.noarch deinstallation of bootsplash-3.3-176.4.x86_64 deinstallation of cifs-utils-5.3-2.1.x86_64 deinstallation of splashy-0.3.13-32.1.x86_64 deinstallation of suspend-1.0-13.2.x86_64 deinstallation of splashy-branding-openSUSE-0.3.13-32.1.x86_64 deinstallation of ksplashx-branding-openSUSE-12.2-4.18.noarch deinstallation of kdebase4-workspace-branding-openSUSE-12.2-3.4.x86_64 Solution 2: do not install kmod-compat-5-1.2.x86_64 This of course prevents using kmod-compat as a permanent replacement of module-init-tools , also kmod-compat does not include /etc/depmod.d /etc/depmod.d/00-system.conf /etc/modprobe.d /etc/modprobe.d/00-system.conf /etc/modprobe.d/10-unsupported-modules.conf /etc/modprobe.d/99-local.conf /usr/lib/module-init-tools /usr/lib/module-init-tools/driver-check.sh /usr/lib/module-init-tools/weak-modules /usr/lib/module-init-tools/weak-modules2 which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely. My proposal is to remove hardcoded package name requires and make rpm to generate requirements on modprobe, lsmod etc when needed automatically. thoughts ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Show replies by date

Frederic Crozat

5 Mar 5 Mar

09:02

Le vendredi 02 mars 2012 à 15:18 -0300, Cristian Rodríguez a écrit :

...

Hi:

There are hardcoded requires on package module-init-tools

Problem: kmod-compat-5-1.2.x86_64 conflicts with module-init-tools provided by module-init-tools-3.15-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of module-init-tools-3.15-1.2.x86_64 deinstallation of pm-utils-1.4.1-16.1.x86_64 deinstallation of mpt-firmware-1.0-249.2.noarch deinstallation of kernel-desktop-3.3.rc5-2.1.x86_64 deinstallation of ipw-firmware-9-11.3.noarch deinstallation of mkinitrd-2.7.0-52.1.x86_64 deinstallation of pm-utils-ndiswrapper-1.4.1-16.1.x86_64 deinstallation of bootsplash-branding-openSUSE-12.2-4.18.noarch deinstallation of bootsplash-3.3-176.4.x86_64 deinstallation of cifs-utils-5.3-2.1.x86_64 deinstallation of splashy-0.3.13-32.1.x86_64 deinstallation of suspend-1.0-13.2.x86_64 deinstallation of splashy-branding-openSUSE-0.3.13-32.1.x86_64 deinstallation of ksplashx-branding-openSUSE-12.2-4.18.noarch deinstallation of kdebase4-workspace-branding-openSUSE-12.2-3.4.x86_64 Solution 2: do not install kmod-compat-5-1.2.x86_64

This of course prevents using kmod-compat as a permanent replacement of module-init-tools , also kmod-compat does not include

/etc/depmod.d /etc/depmod.d/00-system.conf /etc/modprobe.d /etc/modprobe.d/00-system.conf /etc/modprobe.d/10-unsupported-modules.conf /etc/modprobe.d/99-local.conf /usr/lib/module-init-tools /usr/lib/module-init-tools/driver-check.sh /usr/lib/module-init-tools/weak-modules /usr/lib/module-init-tools/weak-modules2

which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

Well, the "unsupported modules" patch in module-init-tools needs to be ported to kmod, if we want to replace module-init-tools with kmod. -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dominique Leuenberger a.k.a DimStar

09:11

Quoting Frederic Crozat :

...

Le vendredi 02 mars 2012 à 15:18 -0300, Cristian Rodríguez a écrit :

...
which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

Well, the "unsupported modules" patch in module-init-tools needs to be ported to kmod, if we want to replace module-init-tools with kmod.

For SLE or for openSUSE? What does 'supported' mean on openSUSE? If you mean for SLE: sorry, wrong audience: we do not care about this here. For openSUSE: there is nothing called 'supprted' or 'unsupported'. The whole distro is 'supported' in a 'best-effort' way. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Frederic Crozat

09:23

Le lundi 05 mars 2012 à 04:11 -0500, Dominique Leuenberger a.k.a DimStar a écrit :

...

Quoting Frederic Crozat :

...
Le vendredi 02 mars 2012 à 15:18 -0300, Cristian Rodríguez a écrit :

...
which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

Well, the "unsupported modules" patch in module-init-tools needs to be ported to kmod, if we want to replace module-init-tools with kmod.

For SLE or for openSUSE? What does 'supported' mean on openSUSE? If you mean for SLE: sorry, wrong audience: we do not care about this here.

I'd like us (openSUSE) making sure we try to work with SLE in mind too (since SLE is based on openSUSE), not against it (at least, when it doesn't mean a lot of work dumped on openSUSE). Of course, a solution could also be to reach module-init-tools maintainer or the person who wrote the patch for module-init-tools and ask him to port it to kmod. And nothing prevent people/admin to activate such feature on openSUSE.. -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dominique Leuenberger a.k.a DimStar

09:29

Quoting Frederic Crozat :

...

Le lundi 05 mars 2012 à 04:11 -0500, Dominique Leuenberger a.k.a DimStar a écrit :

...
Quoting Frederic Crozat :

...
Le vendredi 02 mars 2012 à 15:18 -0300, Cristian Rodríguez a écrit :

...
which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

Well, the "unsupported modules" patch in module-init-tools needs to be ported to kmod, if we want to replace module-init-tools with kmod.

For SLE or for openSUSE? What does 'supported' mean on openSUSE? If you mean for SLE: sorry, wrong audience: we do not care about this here.

I'd like us (openSUSE) making sure we try to work with SLE in mind too (since SLE is based on openSUSE), not against it (at least, when it doesn't mean a lot of work dumped on openSUSE). Of course, a solution could also be to reach module-init-tools maintainer or the person who wrote the patch for module-init-tools and ask him to port it to kmod.

I agree: not to work 'against' SLE, but being blocked by stuff which is for SLE is wrong for openSUSE. If it's an easy hack/fix, let's move it on... otherwise, if SLE folks care about it, they should also port the functionality or stick to the previous technology that works for them... That's what I have in mind when stating that openSUSE must not stall because of SLE decisions (This is actually the only way we can prove that *WE* as a community control openSUSE, and not the SLE-PM) Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andreas Jaeger

6 Mar 6 Mar

08:34

On Monday, March 05, 2012 10:29:56 Dominique Leuenberger a.k.a DimStar wrote:

...

Quoting Frederic Crozat :

...
Le lundi 05 mars 2012 à 04:11 -0500, Dominique Leuenberger a.k.a DimStar

a écrit :

...
Quoting Frederic Crozat :

...
Le vendredi 02 mars 2012 à 15:18 -0300, Cristian Rodríguez a écrit :

...
which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

Well, the "unsupported modules" patch in module-init-tools needs to be ported to kmod, if we want to replace module-init-tools with kmod.

For SLE or for openSUSE? What does 'supported' mean on openSUSE? If you mean for SLE: sorry, wrong audience: we do not care about this here.

I'd like us (openSUSE) making sure we try to work with SLE in mind too (since SLE is based on openSUSE), not against it (at least, when it doesn't mean a lot of work dumped on openSUSE). Of course, a solution could also be to reach module-init-tools maintainer or the person who wrote the patch for module-init-tools and ask him to port it to kmod.

I agree: not to work 'against' SLE, but being blocked by stuff which is for SLE is wrong for openSUSE. If it's an easy hack/fix, let's move it on... otherwise, if SLE folks care about it, they should also port the functionality or stick to the previous technology that works for them...

That's what I have in mind when stating that openSUSE must not stall because of SLE decisions (This is actually the only way we can prove that *WE* as a community control openSUSE, and not the SLE-PM)

I agree with Dominique, patches for SLE should not block openSUSE development. The patch can be added whenever SLE needs it - by some engineers getting paid for SLE - and we should just move on. Dominique, if you ever see openSUSE stalling because of SLE decisions, tell me! I don't want to see that either. Let's just be friendly citiziens and inform our downstream SLE about this. I'll ping those guys that wrote the module-init-tools unsupported patch so that they have this on their radar. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andreas Jaeger

08:38

On Friday, March 02, 2012 19:18:43 Cristian Rodríguez wrote:

...

Hi:

There are hardcoded requires on package module-init-tools

Problem: kmod-compat-5-1.2.x86_64 conflicts with module-init-tools provided by module-init-tools-3.15-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of module-init-tools-3.15-1.2.x86_64 deinstallation of pm-utils-1.4.1-16.1.x86_64 deinstallation of mpt-firmware-1.0-249.2.noarch deinstallation of kernel-desktop-3.3.rc5-2.1.x86_64 deinstallation of ipw-firmware-9-11.3.noarch deinstallation of mkinitrd-2.7.0-52.1.x86_64 deinstallation of pm-utils-ndiswrapper-1.4.1-16.1.x86_64 deinstallation of bootsplash-branding-openSUSE-12.2-4.18.noarch deinstallation of bootsplash-3.3-176.4.x86_64 deinstallation of cifs-utils-5.3-2.1.x86_64 deinstallation of splashy-0.3.13-32.1.x86_64 deinstallation of suspend-1.0-13.2.x86_64 deinstallation of splashy-branding-openSUSE-0.3.13-32.1.x86_64 deinstallation of ksplashx-branding-openSUSE-12.2-4.18.noarch deinstallation of kdebase4-workspace-branding-openSUSE-12.2-3.4.x86_64 Solution 2: do not install kmod-compat-5-1.2.x86_64

This of course prevents using kmod-compat as a permanent replacement of module-init-tools , also kmod-compat does not include

/etc/depmod.d /etc/depmod.d/00-system.conf /etc/modprobe.d /etc/modprobe.d/00-system.conf /etc/modprobe.d/10-unsupported-modules.conf /etc/modprobe.d/99-local.conf /usr/lib/module-init-tools /usr/lib/module-init-tools/driver-check.sh /usr/lib/module-init-tools/weak-modules /usr/lib/module-init-tools/weak-modules2

which will likely break something else, additionally it does not handle suse addition "unsupported modules" which IMHO has no pĺace whatsoever here anyway.If there is such thing as unsupported module in openSUSE, it should warn laud at load time in the kernel message log about this fact or simple be excluded from the distribution completely.

The patch is not needed for openSUSE but for SLE. IF somebody adds it, fine - but let's move forward.

...

My proposal is to remove hardcoded package name requires and make rpm to generate requirements on modprobe, lsmod etc when needed automatically.

thoughts ?

Sounds fine to me, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

4428

Age (days ago)

4432

Last active (days ago)

List overview

Download

6 comments

4 participants

participants (4)

Andreas Jaeger
Cristian Rodríguez
Dominique Leuenberger a.k.a DimStar
Frederic Crozat