-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 20, 2007, at 7:54 AM, Koen van der Drift wrote:
>
>> I see it :-)
>>
>> []
>>> Patch: %n.patch
>> []
>>
>
> D'oh! thanks,
>
> - Koen.
You should also use the newer PatchFile field instead of just Patch.
You then have to use a PatchFile-MD5
>I see it :-)
>
>[]
>> Patch: %n.patch
>[]
>
D'oh! thanks,
- Koen.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/
On 20 Sep 2007, at 11:39, Koen van der Drift wrote:
> On Sep 20, 2007, at 1:14 AM, Martin Costabel wrote:
>> I would guess that somewhere in your info file (in the part that
>> you didn't deem "relevant") you have another patch line that
>> causes the error.
>
>
> I don't see anything, but he
Koen van der Drift wrote:
> On Sep 20, 2007, at 1:14 AM, Martin Costabel wrote:
>
>> While I might be able to believe that fink could change its mind on
>> a percent expansion between dumpinfo and build, I don't see any way
>> how the two interpretations you are showing can come from the same
On Sep 20, 2007, at 1:14 AM, Martin Costabel wrote:
>
> While I might be able to believe that fink could change its mind on
> a percent expansion between dumpinfo and build, I don't see any way
> how the two interpretations you are showing can come from the same
> source line ("sed -e ...|
Koen van der Drift wrote:
[]
> exile:~ koen$ fink dumpinfo -finfofile -fpackage -fpatchscript -pni -
> pa bio-emboss-pm586
[]
> sed -e 's|@PREFIX@|/sw|g' < /sw/fink/dists/local/main/finkinfo/
> libs/perlmods/bio-emboss-pm.patch | patch -p1
[and]
> It does (copy-paste error), but still the
On Sep 19, 2007, at 9:36 PM, Jean-François Mertens wrote:
> What happens if (after "fink index -f" to be sure),
> you do a "fink dumpinfo -finfofile -fpackage -fpatchscript -pni -
> pa" for the file ?
that returns:
exile:~ koen$ fink dumpinfo -finfofile -fpackage -fpatchscript -pni -
pa bio-
On Sep 19, 2007, at 9:17 PM, Jean-François Mertens wrote:
> doesn't this need a redirection to standard input ?
> ie:
> < %a/%{ni}.patch
> ?
It does (copy-paste error), but still the same error:
patch -p1 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
_
On 20 Sep 2007, at 03:17, Jean-François Mertens wrote:
>> sed -e 's|@PREFIX@|%p|g' %a/%{ni}.patch | patch -p1
>>
>>
>
> doesn't this need a redirection to standard input ?
> ie:
> < %a/%{ni}.patch
>
But this doesn't explain the percent expansion that seems to happen...
You don't have a
> Hard to know for sure without seeing more of the .info file,
> especially the Package and Type lines. Check with 'fink dumpinfo
> -finfofile bio-emboss-pm586' to make sure you're editing the correct
> .info file?
>
That command returns the file I'm editing. The relevant part of the
info file
On 20 Sep 2007, at 02:53, Koen van der Drift wrote:
(adding myself from previous msg):
> But I still the following error:
>
> patch -p1 emboss-pm586.patch
> sh: line 1: /sw/fink/dists/local/main/finkinfo/libs/perlmods/bio-
> emboss-pm586.patch: No such file or directory
Then:
>> Hard to know for
On Tue, Sep 18, 2007 at 09:22:37PM -0400, Koen van der Drift wrote:
>
> On Sep 18, 2007, at 11:43 AM, Alexander K. Hansen wrote:
>
> > PatchScript: sed -e 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
>
> Hmm, since the package is versioned (perlmodule), based on other
> versioned packages, I cha
On Sep 18, 2007, at 11:43 AM, Alexander K. Hansen wrote:
> PatchScript: sed -e 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
Hmm, since the package is versioned (perlmodule), based on other
versioned packages, I changed it slightly to:
sed -e 's|@PREFIX@|%p|g' <%a/%{ni}.patch | patch -p1
But I
>oops. No -i:
>
>PatchScript: sed -e 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
>
>
>Shouldn't barge in on these technical issues when I can't get to my Mac. :-(
I'm not at my Mac either right now, but will try this later tonight. Thanks all
for the suggestions,
- Koen.
Alexander K. Hansen wrote:
> John Ridgway wrote:
>
>> No, you can't use %p in a patch file. The preferred method,
>> apparently, is to put something like:
>> @PREFIX@ in the patch file where you would want %p, then use:
>>
>> PatchScript: sed 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
>>
>>
John Ridgway wrote:
> No, you can't use %p in a patch file. The preferred method,
> apparently, is to put something like:
> @PREFIX@ in the patch file where you would want %p, then use:
>
> PatchScript: sed 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
>
>
OK, that's "righter" than what I had. :
Koen van der Drift wrote:
> Hi,
>
> Is it possible to use %p in a patch file? I vaguely remember a while ago
> there was a reason not to do this, but I forgot exactly what. I haven't been
> following the latest developments of the project either, so I don't know if
> this has been changed.
>
>
No, you can't use %p in a patch file. The preferred method,
apparently, is to put something like:
@PREFIX@ in the patch file where you would want %p, then use:
PatchScript: sed 's|@PREFIX@|%p|g' <%a/%n.patch | patch -p1
in your .info file.
See the packaging manual.
Peace
- John
On Sep 18,
Hi,
Is it possible to use %p in a patch file? I vaguely remember a while ago there
was a reason not to do this, but I forgot exactly what. I haven't been
following the latest developments of the project either, so I don't know if
this has been changed.
Basically, what I need to do is to update
19 matches
Mail list logo
