| View previous topic :: View next topic |
| Author |
Message |
cjubon
Guru
Joined: 03 Jul 2007
Posts: 450
Location: Vienna/Europe
|
 Posted: Mon Feb 18, 2008 9:01 pm Post subject: emerge kssh: "Could not apply relink.patch!" [SOLV |
 |
|
Howdy,
I recently re-emerged net-misc/kssh, which built fine but gave me the following message: | emerge kssh wrote: | * Messages for package net-misc/kssh-0.7:
* Could not apply relink.patch! |
Is that a bug? A problem?
Thanks in advance.
_________________
Mandrake Dec 2001 · Debian "Woody" Aug 2002 · Gentoo Jan 2004 · Funtoo Oct 2009
Last edited by cjubon on Tue Feb 19, 2008 3:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Tue Feb 19, 2008 1:46 am Post subject: |
|
|
The ebuild doesn't reference that patch, and a bugzilla search came up with this (amongst other hits):
media-libs/alsa-lib-1.0.3b-r2: relink.patch can't be applied
So apparently it has nothing to do with kssh, but rather libtool. What's odd is how ancient this "bug" is.
[edit] Maybe I should clarify: this pops up all over the place. It comes from the libtool.eclass, which attempts to patch ltmain.sh. If the relink patch doesn't apply, portage will just continue on and issues a warning.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
cjubon
Guru
Joined: 03 Jul 2007
Posts: 450
Location: Vienna/Europe
|
| Posted: Tue Feb 19, 2008 10:50 am Post subject: |
|
|
didymos, thank you for your answer. I did a quick search for "kssh" on b.g.o before I posted. Just good to know that it's not a security issue that should have been patched w/ that patch. Anyhow, should I file a bug?
_________________
Mandrake Dec 2001 · Debian "Woody" Aug 2002 · Gentoo Jan 2004 · Funtoo Oct 2009 |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Tue Feb 19, 2008 1:00 pm Post subject: |
|
|
No, don't file a bug. It's technically not a bug. The devs know that in some cases, that patch just won't apply, which is why the eclass doesn't abort if that happens. If you look at the eclass you see these comments:
| Quote: |
# Critical patch, but could be applied ...
# FIXME: Still need a patch for ltmain.sh > 1.4.0
|
so most of the time a failure will mean that either upstream patched it themselves already or it's the wrong version and the patch can't be applied at all.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
cjubon
Guru
Joined: 03 Jul 2007
Posts: 450
Location: Vienna/Europe
|
| Posted: Tue Feb 19, 2008 2:04 pm Post subject: |
|
|
Nice, thank you. Good occasion for me to dive into the "Gentoo Developer Guide", section about eclasses. Never knew what they are...
_________________
Mandrake Dec 2001 · Debian "Woody" Aug 2002 · Gentoo Jan 2004 · Funtoo Oct 2009 |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Tue Feb 19, 2008 4:19 pm Post subject: |
|
|
They're basically like ebuild libraries so people don't have to keep re-inventing or cutting-and-pasting solutions to common problems. You just add "inherit some_eclass" and then you can use the functions in the eclass or trigger things by setting some environment variable. They're also kind of like standards documents or specifications in that they contain the rules for the "Gentoo way" to do things, like the various kde eclasses.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
|
Networking & Security
