What had to be done in /app-admin/osiris/: cp osiris-4.2.2.ebuild osiris-4.2.3.ebuild cd files sed 's/4.2.2/4.2.3/g' osiris-4.2.2-externaldb.patch > osiris-4.2.3-externaldb.patch cp osirisd-4.2.2 osirisd-4.2.3 cp osirismd-4.2.2 osirismd-4.2.3 cp osirismd_confd-4.2.2 osirismd_confd-4.2.3 cp osirisd_confd-4.2.2 osirisd_confd-4.2.3 Well, it doesn't seem useful to attach the ebuild as it's just renamed.
BTW: It runs stable on x86. I ran a scheduled scan every two minutes and had no problems at all. Session rekeying (after rebooting) also worked fine.
1. Why was it changed to maintainer-needed@gentoo.org? 2. What about dragonheart? 3. How can I find out who's the maintainer for a package?
(In reply to comment #2) > 1. Why was it changed to maintainer-needed@gentoo.org? > 2. What about dragonheart? > 3. How can I find out who's the maintainer for a package? > # cat /usr/portage/app-admin/osiris/metadata.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <herd>no-herd</herd> <longdescription>A program that monitors hosts for changes with detailed logs ofthe changes.</longdescription> </pkgmetadata> The above answers all your 3 questions, I guess.
D'oh! :/ Thanks.
Still no maintainer :(
This seems to fail with db-4.5, doesn't it?
Indeed: ../../src/libosirisdb/libosirisdb.a(osirisdb.o): In function `osi_scan_db_open': osirisdb.c:(.text+0x177a): undefined reference to `db_env_create_4002' osirisdb.c:(.text+0x17b6): undefined reference to `db_create_4002' osirisdb.c:(.text+0x17cd): undefined reference to `db_create_4002' osirisdb.c:(.text+0x17e2): undefined reference to `db_create_4002' osirisdb.c:(.text+0x17f9): undefined reference to `db_create_4002' ../../src/libosirisdb/libosirisdb.a(osirisdb.o): In function `osi_db_open': osirisdb.c:(.text+0x19f7): undefined reference to `db_create_4002' ../../src/libosirisdb/libosirisdb.a(osirisdb.o):osirisdb.c:(.text+0x1a84): more undefined references to `db_create_4002' follow collect2: ld return exit-code 1 make[4]: *** [osirismd] Error 1 make[4]: Leaving directory `/var/tmp/portage/app-admin/osiris-4.2.3/work/osiris-4.2.3/src/osirismd' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/app-admin/osiris-4.2.3/work/osiris-4.2.3/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/app-admin/osiris-4.2.3/work/osiris-4.2.3' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/app-admin/osiris-4.2.3/work/osiris-4.2.3' make: *** [console] Fehler 2 * * ERROR: app-admin/osiris-4.2.3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2506: Called die * The specific snippet of code: * emake console || die "management build failed" * The die message: * management build failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portagelog/app-admin:osiris-4.2.3:20080221-194850.log'. * The ebuild environment file is located at '/var/tmp/portage/app-admin/osiris-4.2.3/temp/environment'. * This ebuild is from an overlay: '/root/OVERLAY/' *
(In reply to comment #6) > This seems to fail with db-4.5, doesn't it? Well yeah the patch is faulty, this needs to use db-use eclass.
I tired fixing bug #176222 but it is not obvious on how to fix. If you can provide something that works here, I'll add it!
Well, if you just run ./configure && make, it compiles like a charm. What do we need the patch for?!
Sorry for bugspam, I mean: osiris-4.2.2-externaldb.patch
(In reply to comment #10) > Well, if you just run ./configure && make, it compiles like a charm. > What do we need the patch for?! > Sorry Craig, I was not CC'd on this bug (feel free to CC me next time if you are seeking a response) Based on previous comments, I assume that osiris-4.2.3 didn't compile..and so, I tested it (as described in Comment #0) and it failed in the same way that bug 176222 fails. =/
Created attachment 170703 [details] osiris-4.2.3.ebuild Osiris brings its own db (osiris-4.2.3/src/db-4.2.52) I added mod_ports again, excluded the externaldb.patch and eautoreconf. I real dev should review this...the ebuild looks a bit messed up.
darkside: the metadata.xml does not list you as mainatainer, please change accordingly.
(In reply to comment #13) > Created an attachment (id=170703) [edit] > osiris-4.2.3.ebuild > > Osiris brings its own db (osiris-4.2.3/src/db-4.2.52) > I added mod_ports again, excluded the externaldb.patch and eautoreconf. I real > dev should review this...the ebuild looks a bit messed up. > Well, it compiled for me. I added it to the tree. (In reply to comment #14) > darkside: the metadata.xml does not list you as mainatainer, please change > accordingly. > Uhh, why? ;) I do not wish to be the Gentoo maintainer, just a member of the 'treecleaner' group. More info: https://bugs.gentoo.org/show_bug.cgi?id=245479#c2
