|Summary:||[Science overlay] omniORBpy version 3.6 ebuild|
|Product:||Gentoo Linux||Reporter:||Mikael Morin <morin-mikael>|
|Component:||New packages||Assignee:||Default Assignee for New Packages <maintainer-wanted>|
|Package list:||Runtime testing required:||---|
The failing omniORBpy ebuild file.
This ebuild works
Description Mikael Morin 2011-08-11 22:03:30 UTC
Hello, I'm trying to create an ebuild for omniORBpy: http://omniorb.sourceforge.net/ I'll attach the ebuild file that I managed to produce so far. However, there is a conflict with omniORB as both are installing the same file. I've tried to remove the offending file in the pkg_preinst function, but it doesn't seem to work, and I can't manage to log any message to the console to see what happens. Any help is appreciated. Reproducible: Always Steps to Reproduce: 1.Merge omniORB (anyway, omniORBpy depends on it) from the regular portage repository. 2.Merge omniORBpy using ebuild command. Actual Results: $ ebuild ./omniORBpy-3.6.ebuild merge [... bla bla ...] * Detected file collision(s): * * /usr/lib64/python2.7/site-packages/omniidl_be/__init__.py * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-misc/omniORB-4.1.4-r1 * /usr/lib64/python2.7/site-packages/omniidl_be/__init__.py * * Package 'net-misc/omniORBpy-3.6' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. Expected Results: No file collision
Comment 1 Mikael Morin 2011-08-11 22:04:24 UTC
Created attachment 282957 [details] The failing omniORBpy ebuild file.
Comment 2 Jesus Rivero (RETIRED) 2011-08-13 15:05:43 UTC
Hey Mikael, Skimming through the ebuild you sent, I got to this line: CONFLICTING_FILE="$(python_get_lib_dir)/site-packages/omniidl_be/__ini__.py" If this is the ebuild you are testing, then I think you missed a 't' in the filename -> '__ini__.py' Regards,
Comment 3 Mikael Morin 2011-08-13 16:23:37 UTC
(In reply to comment #2) > Hey Mikael, > > Skimming through the ebuild you sent, I got to this line: > CONFLICTING_FILE="$(python_get_lib_dir)/site-packages/omniidl_be/__ini__.py" > > If this is the ebuild you are testing, then I think you missed a 't' in the > filename -> '__ini__.py' > > Regards, Right, thank you for noticing the typo. Unfortunately, it doesn't work any better once fixed. And I can't debug this if I don't get some basic loging working.
Comment 4 Mikael Morin 2011-09-09 21:31:18 UTC
Created attachment 286005 [details] This ebuild works The problem was that the conflict checking code is run before pkg_preinst. Thus my pkg_preinst function removing the conflicting file was never run. In the attached ebuild, the conflicting file is removed in the src_install function. There is no more conflict, and the package is installed without problem.
Comment 5 Mikael Morin 2011-09-17 21:27:40 UTC
Looks like this is a duplicate of Bug 166738. As I have made an ebuild for this, maybe this can be integrated into the science overlay? Changing the summary: From: "New ebuild: omniORBpy and conflicting files" to "[Science overlay] omniORBpy version 3.6 ebuild"
Comment 6 Patrice Clement 2016-10-11 08:35:46 UTC
In the science overlay. Closing.