Daniel Macks | 1 Mar 2005 04:55

Re: dists/10.3/unstable/main/finkinfo/libs/perlmods archive-zip-pm.info,1.1,1.2

Chris Dolan committed:
>
>  * change perl variant list to 581,584,586 (the ones I can test easily)

Testing is good! However, we have to be careful not to break upgrade
paths when removing perl-versions. When a Type: perl subtype "XXX" is
removed from the .info repository, users may still have that package's
foo-pmXXX* set installed. That means we need to keep the various
Replaces/Conflicts against that once-but-no-longer-present XXX set in
whatever XXY sets remain.

OTOH, we've cooked up a new filysystem layout for perl modules that
will mean all the man3 for all perl-versions of a -pmXXX can
coexist. That will mean the -man splitoff will no longer be needed for
most perlmod packages. Details to follow when we finish figuring them
out:)

In the mean time...

Chris Dolan committed (snipping throughout the diff)
> --- archive-zip-pm.info	18 Jan 2005 07:04:44 -0000	1.1
> +++ archive-zip-pm.info	24 Feb 2005 03:33:24 -0000	1.2
>  Version: 1.14
> -Revision: 1
> -Type: perl (5.8.0 5.8.1 5.8.4)
> +Revision: 2
> +Type: perl (5.8.1 5.8.4 5.8.6)
>   Package: %N-man
> - Conflicts: %{Ni}580-man, %{Ni}581-man, %{Ni}584-man
> - Replaces: %{Ni}580-man, %{Ni}581-man, %{Ni}584-man
(Continue reading)

Chris Dolan | 1 Mar 2005 14:24

Re: dists/10.3/unstable/main/finkinfo/libs/perlmods archive-zip-pm.info,1.1,1.2

Dan,

Thanks for pointing that out.  I had not sufficiently thought through 
the consequences of dropping support for 5.8.0.  I'll add back the 
Replaces/Conflicts in my various packages as you suggested.

Good news about the perl man versioning, too.  I approve of the idea.  
I'm guessing installing a version of Perl will also add a profile.d 
entry to append a perl-versioned dir to the init.[c]sh manpath?

Chris

On Feb 28, 2005, at 9:55 PM, Daniel Macks wrote:

> Chris Dolan committed:
>>
>>  * change perl variant list to 581,584,586 (the ones I can test 
>> easily)
>
> Testing is good! However, we have to be careful not to break upgrade
> paths when removing perl-versions. When a Type: perl subtype "XXX" is
> removed from the .info repository, users may still have that package's
> foo-pmXXX* set installed. That means we need to keep the various
> Replaces/Conflicts against that once-but-no-longer-present XXX set in
> whatever XXY sets remain.
>
> OTOH, we've cooked up a new filysystem layout for perl modules that
> will mean all the man3 for all perl-versions of a -pmXXX can
> coexist. That will mean the -man splitoff will no longer be needed for
> most perlmod packages. Details to follow when we finish figuring them
(Continue reading)

Hanspeter Niederstrasser | 1 Mar 2005 22:59
Picon

Firefox 1.0.1 crash on startup

I'm trying to update the firefox package to 1.0.1 but keep running into 
a bus error on startup.  Can someone try locally updating to firefox 
1.0.1 and seeing if they also get a bus error when trying to run the 
program?  The only thing that should need to be done in the .info file 
is to change the package version to 1.0.1, and the new MD5SUM is 
"ebaea974fea9460ab7050fff76b41cb1".  That should get you the new source 
file to compile.  The two executables to try are %p/bin/firefox (the 
normal run script) and %p/lib/firefox/firefox-bin (the actual 
executable).  Thanks.

As a followup, how could I go about debugging this?  The output from 
--enable-debug would not mean much to me (I'm not a programmer).  The 
1.0 patch applied cleanly and 1.0 -> 1.0.1 was mainly a security 
release, not a feature upgrade.  I checked the diff between the two 
sources and nothing jumped out at me as being new yet somehow related to 
the porting patch in Fink.

Hanspeter

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Alexander K. Hansen | 2 Mar 2005 02:29
Picon

Re: strange terminal output after fink commands


On Mar 1, 2005, at 7:23 PM, Koen van der Drift wrote:

> Hi,
>
> After today's update, I get strange output in my terminal after each 
> fink command:
>
> ModusOperandi:~ koen$ fink index
> Reading package info...
> Updating package index... done.
> 2005-03-01 19:17:53.176 osascript[8407] CFLog (21): Error loading 
> /Library/Application Support/DivXNetworks/liblame3.92.dylib:  error 
> code 0, error number 2 (dyld: osascript can't open library: 
> /Library/Application Support/DivXNetworks/liblame3.92.dylib  (No such 
> file or directory, errno = 2)
> )
> 2005-03-01 19:17:53.181 osascript[8407] CFLog (21): Error loading 
> /Library/Application Support/DivXNetworks/liblame3.92.dylib:  error 
> code 0, error number 2 (dyld: osascript can't open library: 
> /Library/Application Support/DivXNetworks/liblame3.92.dylib  (No such 
> file or directory, errno = 2)
> )
>
> and that many times repeated.  No idea why it wants to load liblame.
>
>
> ModusOperandi:~ koen$ fink -V
> Package manager version: 0.24.1
> Distribution version: 0.7.1.cvs
(Continue reading)

Daniel Macks | 2 Mar 2005 02:56

Re: strange terminal output after fink commands

On 09 November 2004, Ben Hines said:
> 
> perl5.8.4-core does not install /sw/bin/perl, but its Config.pm has: 
> startperl='#!/sw/bin/perl'. This messes up my help2man package. I tell 
> it PERL is /sw/bin/perl5.8.4 but then it asks for $Config{startperl} 
> and perl says /sw/bin/perl. So it no work. I want it to use fink perl 
> if its there.
> 
> Shouldn't fink perl584 be configured with /sw/bin/perl5.8.4 as the 
> startpath?

I see that drm has fixed this a day or two ago.

dan

--

-- 
Daniel Macks
dmacks <at> netspace.org
http://www.netspace.org/~dmacks

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Alexander K. Hansen | 2 Mar 2005 03:01
Picon

Re: strange terminal output after fink commands


On Mar 1, 2005, at 8:41 PM, Koen van der Drift wrote:

>
> On Mar 1, 2005, at 8:29 PM, Alexander K. Hansen wrote:
>
>> Odd.  Did you check whether it happens after other commands?
>>
>
> So far I tested:
>
> fink index
> fink configure
> fink list installed
> fink remove
>
> and it happens in every case.
>
> - Koen.
>
>
>
>

But how about non-fink commands?

-AH

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
(Continue reading)

Koen van der Drift | 2 Mar 2005 03:06
Picon
Favicon
Gravatar

Re: strange terminal output after fink commands


On Mar 1, 2005, at 9:01 PM, Alexander K. Hansen wrote:

> But how about non-fink commands?
>
>

I tested a few non-fink commands (ls, apt-get update, locate), and it 
doesn't happen.

- Koen.

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Daniel Macks | 2 Mar 2005 03:21

Re: startperl with perl584

Wow, way to screw up your mailer, dan!

On Tue, Mar 01, 2005 at 08:56:27PM -0500, Daniel Macks wrote:
> On 09 November 2004, Ben Hines said:
> > 
> > perl5.8.4-core does not install /sw/bin/perl, but its Config.pm has: 
> > startperl='#!/sw/bin/perl'. This messes up my help2man package. I tell 
> > it PERL is /sw/bin/perl5.8.4 but then it asks for $Config{startperl} 
> > and perl says /sw/bin/perl. So it no work. I want it to use fink perl 
> > if its there.
> > 
> > Shouldn't fink perl584 be configured with /sw/bin/perl5.8.4 as the 
> > startpath?
> 
> I see that drm has fixed this a day or two ago.
> 
> dan

--

-- 
Daniel Macks
dmacks <at> netspace.org
http://www.netspace.org/~dmacks

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Alexander K. Hansen | 2 Mar 2005 03:35
Picon

Re: strange terminal output after fink commands


On Mar 1, 2005, at 9:06 PM, Koen van der Drift wrote:

>
> On Mar 1, 2005, at 9:01 PM, Alexander K. Hansen wrote:
>
>> But how about non-fink commands?
>>
>>
>
> I tested a few non-fink commands (ls, apt-get update, locate), and it 
> doesn't happen.
>
> - Koen.
>
>

Hmmm...very odd.  I guess the obvious thing to do is to try hunting 
down whatever has linked that dylib.

otool -L <library>  | grep liblame3.92.dylib

would be the basis of something to try--<library> is the library you're 
evaluating.  There's probably a good way to do this via a shell script, 
but I don't have it right off the top of my head right now.

--AH

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
(Continue reading)

TheSin | 2 Mar 2005 03:48
Favicon

Re: strange terminal output after fink commands

do you have growl installed?  Cause that would call oascript which 
seems to be broken.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 1-Mar-05, at 7:06 PM, Koen van der Drift wrote:

>
> On Mar 1, 2005, at 9:01 PM, Alexander K. Hansen wrote:
>
>> But how about non-fink commands?
>>
>>
>
> I tested a few non-fink commands (ls, apt-get update, locate), and it 
> doesn't happen.
>
> - Koen.
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
(Continue reading)


Gmane