| Anonymous | Login | Signup for a new account | 12-11-2005 14:31 GMT |
| Main | My View | View Issues | Change Log |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000006 | [cAos-2] Packages – Dependancy Issues | block | always | 04-22-05 07:48 | 10-18-05 09:09 | ||||
| Reporter | Maarten Stolte | View Status | public | ||||||
| Assigned To | Denis Pilon | ||||||||
| Priority | high | Resolution | fixed | ||||||
| Status | closed | Product Version | 2.0 | ||||||
| Summary | 0000006: buildroot cannot be installed due to conflicts between modutils and module-init-tools | ||||||||
| Description |
this is the error i get after running Transaction Check Error: file /sbin/depmod conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/generate-modprobe.conf conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/insmod conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/insmod.static conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/lsmod conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/modinfo conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/modprobe conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /sbin/rmmod conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man5/modprobe.conf.5.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/depmod.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/insmod.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/lsmod.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/modinfo.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/modprobe.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 file /usr/share/man/man8/rmmod.8.gz conflicts between attempted installs of module-init-tools-3.1-4.caos and modutils-2.4.26-16 |
||||||||
| Additional Information |
I used ‘yum –installroot /scsi/caos_2_master/ groupinstall buildroot’ to try and get a buildroot setup in the clean (empty) directory /scsi2/caos_2_master. My yum.conf is: [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=caos-release installonlypkgs=linux linux-smp kernel kernel-smp exactarch=1 [core] name=cAos2 core system repository baseurl=http://caos.nplus1.net/cAos-2/core/$basearch [^] [ext-current] name=cAos2 extended current system repository baseurl=http://caos.nplus1.net/cAos-2/ext/current/$basearch [^] [ext-autobuilder] name=cAos2 extended autobuilder system repository baseurl=http://caos.nplus1.net/cAos-2/ext/autobuilder/$basearch [^] |
||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Relationships | ||||||
|
||||||
| Notes | |
|
(0000009) Greg Kurtzer 04-22-05 14:08 |
I updated the yum group on mirror.caosity.org. This will soon propagate to the rest of the mirrors. Please test. Thanks. |
|
(0000012) Denis Pilon 04-22-05 23:18 |
Should really be assiged to MEJ…he needs to remove it from the core directory as it is already removed from cvs |
|
(0000013) Greg Kurtzer 04-22-05 23:36 |
Agreed… I created an account for MEJ, and prepopulated it with this little gift. |
|
(0000014) Maarten Stolte 04-23-05 09:41 |
afaik this is fixed by Greg now? |
|
(0000015) Greg Kurtzer 04-23-05 13:31 |
Fixed yes, but modutils should still be removed from the core repository. It is obsolete, and no longer in cvs. tnx 🙂 |
|
(0000034) Michael Jennings 04-27-05 15:59 |
Has someone decided where to keep the buildroot? Are folks downloading it from caos.nplus1.net now? |
|
(0000035) Greg Kurtzer 04-27-05 16:03 |
Do we need to distribute them now that they can be easily produced with a yum groupinstall? If so, then I would suggest cvs.caosity.org. |
|
(0000036) Michael Jennings 04-27-05 16:04 |
Care to add more detail to that? 🙂 If one can create one’s very own buildroot image using "yum groupinstall," I’d think that would be a candidate for an entry in the Wiki. Wouldn’t you agree? |
|
(0000037) Greg Kurtzer 04-27-05 16:09 |
Is the yum groupinstall method deemed by the powers that be as the proper public solution for buildroot maintaince? I want to know if I posision it in the wiki as the primary solution, or an alternative. |
|
(0000040) Michael Jennings 04-27-05 17:53 |
I don’t care all that much, but there is something to be said for publicizing the exact build tree which was used…. |
|
(0000041) Greg Kurtzer 04-27-05 18:23 |
Considering that the buildroots were never *really* published anonymously (restricted rsyncd access), why not just make a weekly tarball on mirror, and then have yum be the default… If that is ok, I will document the yum method, and you guys work out how to publish the images. I can then pull to mirror. Cool? |
|
(0000044) Michael Jennings 04-27-05 20:31 |
Tarball bad. Don’t forget that there is great utility in being able to sync only changed files in the buildroot, particularly to clean up after a build. I’m not sure there’s really a need to restrict rsync access to the buildroot. Why was that done? |
|
(0000045) Greg Kurtzer 04-27-05 20:38 |
That was done because the rsyncd could not drop privs to a non-root because of the /dev tree. We didn’t want just anyone connecting to it. The idea was system security. |
|
(0000046) Michael Jennings 04-27-05 20:46 |
But now with udev, is that still an issue? |
|
(0000047) Greg Kurtzer 04-27-05 20:48 |
Well, do you have anything in your /dev directory? The yum group buildroot contains dev-minimal, which is 35 various nods. Maybe we can just get rid of that, but I think that most, if not all packages will fail without /dev/null. |
|
(0000052) Maarten Stolte 04-28-05 06:16 |
how about only providing an initial tarball, and a delta one for the changes to it? If the delta gets too big, we can then refresh the initial tarball. For this to work we might have to make it clear what is what, so maybe version the buildroot like this: caos-buildroot-2.N ? |
|
(0000054) Michael Jennings 04-28-05 17:46 |
I guess we can settle for rsync’ing the tarball. Where should I put it? /cAos-2/install? Perhaps a new /caos-2/build directory? |
|
(0000055) Greg Kurtzer 04-28-05 18:15 |
cAos-2/buildroots would be my preference. |
|
(0000056) Michael Jennings 04-28-05 18:17 |
cAos-2/buildroots/ARCH/? |
|
(0000057) Greg Kurtzer 04-28-05 18:19 |
Now do we want to have buildroot versions, or just a single image? cAos-2/buildroots/$arch/buildroot-$version.tar.gz Otherwise: cAos-2/buildroots/buildroot.$arch.tar.gz should work just fine. |
|
(0000060) Michael Jennings 04-28-05 20:57 |
Please test: http://master.caosity.org/cAos-2/buildroots/buildroot.i386.tar.bz2 [^] |
|
(0000061) Greg Kurtzer 04-29-05 07:11 |
works for me! thanks! Just to come back to the issue… Has modutils and other old/obsoloete packages been removed from the core/arch repository? Confirmation from dpilon and KainX please. |
|
(0000071) Greg Kurtzer 05-04-05 09:42 |
I have heard back from the KainX on this… still waiting on dpilon. 😉 |
|
(0000100) Greg Kurtzer 05-28-05 03:26 |
dpilon? please respond… |
|
(0000197) Denis Pilon 10-14-05 19:33 |
modutils is not in the x86_64 core…so there should be no one waiting for me on this issue. GMK, can you make a buildroot-x86_64.tar.gz so people can download ? DP |
|
(0000204) Maarten Stolte 10-18-05 09:09 |
This one has been resolved by now. |
