[opensuse] kernel install conflicts -- Can I safely ignore them?
Guys, I working to update my kernel and I have run into the following conflict: # rpm -ivh ../noarch/kernel-source-2.6.31.12-2.1.noarch.rpm Preparing... ########################################### [100%] file /etc/rpm/macros.kernel-source from install of kernel-source-2.6.31.12-2.1 conflicts with file from package kernel-source-2.6.25.20-0.7 file /usr/lib/rpm/kernel-module-subpackage from install of kernel-source-2.6.31.12-2.1 conflicts with file from package kernel-source-2.6.25.20-0.7 The files are text files, and I'm almost willing to bet they would be identical, but don't know, so I'm concerned enough to beg for help before I do something dumb like forcing this into place. The kernel is from: http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... and I was interesting in checking it out. On all prior kernel installs where I have had multiple kernels installed (with rpm -ivh), I've never received this error before ... and I regularly have 2-3 different kernel packages installed. I guess the problem is most likely a packaging problem, but don't know enough about suse kernel packaging to be sure. So what say the kernel experts, Can I safely ignore the conflict and overwrite the above files safely? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-04-14 21:04, David C. Rankin wrote:
and I was interesting in checking it out. On all prior kernel installs where I have had multiple kernels installed (with rpm -ivh), I've never received this error before ... and I regularly have 2-3 different kernel packages installed.
Do you really need the sources of all? I
guess the problem is most likely a packaging problem, but don't know enough about suse kernel packaging to be sure.
So what say the kernel experts, Can I safely ignore the conflict and overwrite the above files safely?
I would say report on bugzilla, but is is not an stock kernel. Report to that home owner. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkvGGRsACgkQU92UU+smfQUpOgCaAwQYzSqJrhOnyrDbvr3CgYWA rTEAoI9VqIAefWGscbRWi150SVaiMUAA =Wa1K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/14/2010 02:35 PM, Carlos E. R. wrote:
On 2010-04-14 21:04, David C. Rankin wrote:
and I was interesting in checking it out. On all prior kernel installs where I have had multiple kernels installed (with rpm -ivh), I've never received this error before ... and I regularly have 2-3 different kernel packages installed.
Do you really need the sources of all?
I
Yes, at least I think so, for fglrx, virtualbox module compilation, and who knows what all other requirements the various srpms have that I fairly regularly compile...
guess the problem is most likely a packaging problem, but don't know enough about suse kernel packaging to be sure.
So what say the kernel experts, Can I safely ignore the conflict and overwrite the above files safely?
I would say report on bugzilla, but is is not an stock kernel. Report to that home owner.
Yes, This is where the Novell OBS really has a problem that needs to be addressed. Novell relies on OBS to a great extent to keep packages for releases current, but then if there is ever a problem with an OBS package, Novell treats you like you have the plague... If it wasn't for OBS, packman, etc.. openSuSE releases would be out of date less than 3 months after they were released. I understand the business model of relying on users to build updates for releases and I think it is a good idea, but there needs to be a mechanism in place for bug reporting and resolution when problems arise with OBS packages. One would think Novell would jump at the chance to handle bug resolution of OBS packages. After all, an overwhelming part of the work required to update the package has already been done by the user and with little additional effort (resources), Novell could lend a hand review the build details and solve any issues with the package and then give it the "official stamp" and market the fact that opensuse packages are current through XYZ version based on the OBS build. I see it as a very positive win-win for both Novell and the community. The current process of e-mail the user that built the package and hope he can (or will) address the issue. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-15 00:54, David C. Rankin wrote:
On 04/14/2010 02:35 PM, Carlos E. R. wrote:
I would say report on bugzilla, but is is not an stock kernel. Report to that home owner.
Yes,
This is where the Novell OBS really has a problem that needs to be addressed. Novell relies on OBS to a great extent to keep packages for releases current, but then if there is ever a problem with an OBS package, Novell treats you like you have the plague... If it wasn't for OBS, packman, etc.. openSuSE releases
Notice that there is a big difference between a "normal" OBS repository, and a "home" one. These are private/public playgrounds, not intented for general distribution. That said, I agree that there are no clear channel and procedures for communicating/solving bugs in OBS packages. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvGwesACgkQja8UbcUWM1y4fQEAiWkj3ii0u83GRKYWwrQOYWxg KUbQ8EfTaTbGFeZgqZQA/Rv3VLoEDwXhq8RhFg4+n6GQV7UiP+9ff6an2Iz8MMq5 =wXOr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* David C. Rankin (drankinatty@suddenlinkmail.com) [20100415 00:55]:
but there needs to be a mechanism in place for bug reporting and resolution when problems arise with OBS packages. [...] One would think Novell would jump at the chance to handle bug resolution of OBS packages.
First of all you need to draw a line between devel projects like Base:System and home projects. Home projects are the playground of their respective owner and no other is responsible. If you use packages from there you're the only one to blame. After all, if these were packages offered from some random site you would contact the site owner and not the company that hosts the server. Most packages in devel projects have a bugowner and you can assign reports in bugzilla to them. You get the maintainer via 'osc maintainer <project> <package>' but osc only gets you the name, not the full address so you're better off checking via the web.
Novell could lend a hand review the build details and solve any issues with the package and then give it the "official stamp" and market the fact that opensuse packages are current through XYZ version based on the OBS build.
No company could afford the resources to do such a thing! Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-15 14:41, Philipp Thomas wrote: ...
Most packages in devel projects have a bugowner and you can assign reports in bugzilla to them. You get the maintainer via 'osc maintainer <project> <package>' but osc only gets you the name, not the full address so you're better off
That's not the proper way way to find them for a reporter. A reporter (me, for instance) might not be a buildservice user (I am not) and have not 'osc' installed (I don't), so it is impossible for us to find anybody using 'osc'. You have to define a better, user accessible, method of finding maintainers. All buildservice projects should have a mandatory html directory with a mandatory index.html in which we could find the purpose and target of the repo, and reporting/contacting info, at least. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvH/hEACgkQja8UbcUWM1wgVQD+KMFSFyxu1Y/xTi0QnIG9nvD8 O3IVAZz1oDJIarldJGMA/jqKwh3nuTn3KbhgQpxIMwmuK8AzCJfrgGrkrQ9bPdns =XNDI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Carlos E. R.
All buildservice projects should have a mandatory html directory with a mandatory index.html in which we could find the purpose and target of the repo, and reporting/contacting info, at least.
+1 -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 16 Apr 2010 08:05:05 +0200, "Carlos E. R."
All buildservice projects should have a mandatory html directory with a mandatory index.html in which we could find the purpose and target of the repo, and reporting/contacting info, at least.
Such a list would IMO be the ideal target for email address harvesters. But you should still enter this feature request in openfate. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Philipp Thomas
On Fri, 16 Apr 2010 08:05:05 +0200, "Carlos E. R."
wrote: All buildservice projects should have a mandatory html directory with a mandatory index.html in which we could find the purpose and target of the repo, and reporting/contacting info, at least.
Such a list would IMO be the ideal target for email address harvesters. But you should still enter this feature request in openfate.
Perhaps the addresses should be presented as a graphic rather than text and maybe even with distorted letters?? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-04-16 21:20, Philipp Thomas wrote:
On Fri, 16 Apr 2010 08:05:05 +0200, "Carlos E. R." <> wrote:
All buildservice projects should have a mandatory html directory with a mandatory index.html in which we could find the purpose and target of the repo, and reporting/contacting info, at least.
Such a list would IMO be the ideal target for email address harvesters. But you should still enter this feature request in openfate.
It needs not be an email. It can be a form to be filled, as many webpages use. It could be a central form server for the buildservice. As to openfate, I do not use it, I have my reasons (stated elsewere). - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkvIx1kACgkQU92UU+smfQXmMwCdGj3qwzFOmaJzrMAf24KE5aeY MzwAn0xz9NNQ8tU1GHEsYM9EnLdYKYAo =B/E/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 16 Apr 2010 22:23:53 +0200, "Carlos E. R."
As to openfate, I do not use it, I have my reasons (stated elsewere).
Somebody has to do it and such a request has to come from the comunity to have any weight. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Apr 14, 2010 at 02:04:45PM -0500, David C. Rankin wrote:
Guys,
I working to update my kernel and I have run into the following conflict:
# rpm -ivh ../noarch/kernel-source-2.6.31.12-2.1.noarch.rpm Preparing... ########################################### [100%] file /etc/rpm/macros.kernel-source from install of kernel-source-2.6.31.12-2.1 conflicts with file from package kernel-source-2.6.25.20-0.7 file /usr/lib/rpm/kernel-module-subpackage from install of kernel-source-2.6.31.12-2.1 conflicts with file from package kernel-source-2.6.25.20-0.7
The files are text files, and I'm almost willing to bet they would be identical, but don't know, so I'm concerned enough to beg for help before I do something dumb like forcing this into place.
The kernel is from:
http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor...
and I was interesting in checking it out. On all prior kernel installs where I have had multiple kernels installed (with rpm -ivh), I've never received this error before ... and I regularly have 2-3 different kernel packages installed. I guess the problem is most likely a packaging problem, but don't know enough about suse kernel packaging to be sure.
So what say the kernel experts, Can I safely ignore the conflict and overwrite the above files safely?
kernel-source is the source, and not a binary package. The binary packages are capable to be installed in parallel, kernel-source was not really designed for it. The files probably did not change that much. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/14/2010 02:36 PM, Marcus Meissner wrote:
kernel-source is the source, and not a binary package. The binary packages are capable to be installed in parallel, kernel-source was not really designed for it. The files probably did not change that much.
Ciao, Marcus
That's what I needed! Thanks Marcus. Initially, I thought the new source would simply install in /usr/src/linux-<version no.> and then the symlink for 'linux' and 'linux-obj' would be used to point to the active kernel. Right now I have both linux-2.6.25.20-0.5 and linux-2.6.25.20-0.7 sources installed (no linux-2.6.25.20-0.5-obj) and that works fine. That's what prompted the initial concern. Thanks again. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R.
-
Carlos E. R.
-
David C. Rankin
-
Marcus Meissner
-
Patrick Shanahan
-
Philipp Thomas
-
Philipp Thomas