-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/9/10 3:29 AM, Trevor Harmon wrote:
> I've created a new plugin that bumps the upstream version to the latest
stable release (2.2.1) and also fixes the aforementioned bug. However,
my attempts to contact the maintainer (in early June) have been
un
On Aug 9, 2010, at 9:07 AM, Alexander Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 8/9/10 6:01 AM, Daniel E. Macks wrote:
>> Many dozens of perl5.10.0 variants of perlmodule packages don't build
>> on 10.6/i386 (i.e., the 32-bit side of the "universal" system-perl)
>> b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/9/10 6:01 AM, Daniel E. Macks wrote:
> Many dozens of perl5.10.0 variants of perlmodule packages don't build
> on 10.6/i386 (i.e., the 32-bit side of the "universal" system-perl)
> because they all clone the same CompileScript for Build.PL that do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/9/10 3:29 AM, Trevor Harmon wrote:
> Hi,
>
> The maven.info package is still using Maven 2.0.10, which was released a year
> and a half ago. The package also has a bug that causes some Maven plugins to
> fail because they can't find the mvn exe
Many dozens of perl5.10.0 variants of perlmodule packages don't build
on 10.6/i386 (i.e., the 32-bit side of the "universal" system-perl)
because they all clone the same CompileScript for Build.PL that does
not pass the single-arch tricks. I'm fixing them because they're
broken. I have contacted ma
Koen van der Drift said:
> Dear Fink team,
>
> Unfortunately, due to time restrictions and other obligations, I am
> unable to keep maintaining my packages.
>
> Feel free to take them over, and/or unmaintain them in cvs.
I claimed a few, set the rest to maintainer:none.
> Many thanks,
And tha
Hi,
The maven.info package is still using Maven 2.0.10, which was released a year
and a half ago. The package also has a bug that causes some Maven plugins to
fail because they can't find the mvn executable.
I've created a new plugin that bumps the upstream version to the latest stable
release
John Davison wrote:
[]
> So 1.2.5 would be valid, but 0.1.2.5 isn’t.
>
> It would seem that
> “/sw/src/libpng3-1.2.5-2/libpng-1.2.5/scripts/Makefile.darwin” is broken.
On MacOSX 10.3 ("Panther") for which the package was made, this "bug"
did not lead to an error; it gave a compatibility version
