From the hpn site, openssh-4.3p2 should use hpn12. I've tested it and it works fine in the ebuild. Attached is the simple ebuild patch.
Created attachment 88484 [details, diff] openssh-4.3_p2-r2.patch Patch to update hpn in openssh-4.3_p2-r1.ebuild from hpn11 to hpn12.
the hpn patch conflicted with securid so i had to tweak things a little 4.3_p2-r2 now in portage, thanks
If X509 and not hpn it does not compile. Please consider apply the "${FILESDIR}"/${P}-x509-hpn-glue.patch only if use hpn.
it wont build anyway openssh-4.3_p2-r2 doesnt build here with HPN patches. ... * Applying openssh-4.3p2-hpn12.diff.gz ... * Failed Patch: openssh-4.3p2-hpn12.diff.gz ! * ( /var/tmp/portage/openssh-4.3_p2-r2/temp/14144.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/openssh-4.3_p2-r2/temp/openssh-4.3p2-hpn12.diff.gz-14144.out !!! ERROR: net-misc/openssh-4.3_p2-r2 failed. Call stack: ebuild.sh, line 1539: Called dyn_unpack ebuild.sh, line 711: Called src_unpack openssh-4.3_p2-r2.ebuild, line 78: Called epatch '/var/tmp/portage/openssh-4.3_p2-r2/distdir/openssh-4.3p2-hpn12.diff.gz' eutils.eclass, line 333: Called die ... the output file (snippet): PIPE_COMMAND: gzip -dc /var/tmp/portage/openssh-4.3_p2-r2/distdir/openssh-4.3p2-hpn12.diff.gz > /var/tmp/portage/openssh-4.3_ p2-r2/temp/14144.patch PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/openssh-4.3_p2-r2/temp/14144.patch ======================================= patching file openssh-4.3p2-hpn12/HPN12-README can't find file to patch at input line 53 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --new-file -p openssh-4.3p2.canonical/buffer.c openssh-4.3p2-hpn12/buffer.c |*** openssh-4.3p2.canonical/buffer.c 2005-03-14 07:22:26.000000000 -0500 |--- openssh-4.3p2-hpn12/buffer.c 2006-04-05 13:49:35.000000000 -0400 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored
Created attachment 88763 [details] Patch Error File This is the patch error file that gets created when net-misc/openssh-4.3_p2-r2 USE="hpn pam stftploggin tcpd -X509 -chroot -ipv6 -kerberos -ldap -libedit -skey -smartcard -static"
*** Bug 136224 has been marked as a duplicate of this bug. ***
Reopen.
dont re-open bugs that are fixed
(In reply to comment #8) > dont re-open bugs that are fixed I am so confused! This fix caused a problem. Why not dealing with it until it fully workable? It is not the first time that I see that... 1. A bug is opened. 2. A solution is provided for the bug, but has bugs. 3. Now the problem begins. a. There are some developers that continue the discussion on the bug originaly opened, until they resolve all issues. b. There are some developers that request a new bug to be opened to every problem they introduced in fixing the original bug. The expected behavior is a, and it is the most appropriate for users how follow the initial bug, until it fully resolved. (In reply to comment #8) > dont re-open bugs that are fixed But this bug is not fixed... So it can be reopened....
no, your tree is out of date i fixed the issue before you started posting to this bug
(In reply to comment #10) > no, your tree is out of date > > i fixed the issue before you started posting to this bug So it would have been nice if you had left here a message... We cannot read your mind... And if you don't put a new revision for an ebuild, the overlay is used. So something like: "Updated in portage, please resync" will make people very happy, without a great effort from your part.
(In reply to comment #10) > no, your tree is out of date > > i fixed the issue before you started posting to this bug > no, my tree was updated at 3:10am CST this morning (6/10/2006) and the bug still exists. Thanks for trying.
Dear vapier@gentoo.org What should I understand from your last modification? Is this somekind of hint that I don't understand?
this bug is about adding new hpn patch, not about build failures
