Hello!
I'm trying to create nessus-bin-3.2.0 ebuild.
I've downloaded Nessus-3.2.0-suse10.0.i586.rpm, checked its md5 sum, and
I've done just a `cp nessus-bin-3.0.5.ebuild nessus-bin-3.2.0.ebuild`.
But even scr_unpack() fails:
Unpacking Nessus-3.2.0-suse10.0.i586.rpm to
/tmp/portage/net-analyzer
are correct without
having to resort to ugly symlinks, although nessusd does complain about
no
version information available in libssl and libcrypto.
Oh' thanks a lot for the information.
nessus from suse10 does not starts at all for me.
--
Vladimir Rusinov
Voronezh, Russia
UNIX Admin
On Friday 21 March 2008 10:11:30 Vladimir Rusinov wrote:
How can I fix this?
Sorry, I can't tell you how, but I can concur with your findings.
I've tried 3 different 3.2.0 release RPMs and rpmoffset/rpm2targz can't parse
any of them. However the 3.0.5 suse10 RPM does work.
I'm going to look
system,
or the like. Here's an example of the daily mail I get when I run esync
as a cron job and mail myself the output:* Importing old portage tree
* Doing '/usr/bin/emerge sync' now
* Doing 'eupdatedb' now
* esearch-index generated in 4 minute(s) and 23 second(s)
* indexed 10357 ebuilds
On 3/21/08, Mike Williams [EMAIL PROTECTED] wrote:
On Friday 21 March 2008 10:11:30 Vladimir Rusinov wrote:
How can I fix this?
Sorry, I can't tell you how, but I can concur with your findings.
I've tried 3 different 3.2.0 release RPMs and rpmoffset/rpm2targz can't
parse
any of them.
On Friday 21 March 2008 18:27:27 Vladimir Rusinov wrote:
Well, I've noticed that rpm.eclass tries to use rpm2cpio first. I've
installed rpm package and it unpacks and installs now.
I have not yet tested installed packages, but anyway I'll submit the ebuild
and comments to bugzilla after few
6 matches
Mail list logo
