[Fink-devel] MatchPackageRegEx

Cool feature, but i don't like the name of the setting... it is confusing. "Will match?" then do what? Ignore those, or choose those? :) (i presume choose) How about something like DefaultPackageMatch: Newbies who don't know what a regex is can just put ssl there, and it will all make sense a

[Fink-devel] Fink::FinkVersion dependency fixed

I've changed the test target so that setup.sh will be run before the tests. It uses t/basepath as the basepath. This should make available for testing all the programs and libraries in fink and allows one to run the tests without having fink previously installed. Fink::FinkVersion is now generat

Re: [Fink-devel] Failed make test

On Thu, Nov 20, 2003 at 07:33:50PM -0500, David R. Morrison wrote: > Well, this one is easy to understand, but I'm not sure how to fix it. > > In the "fink" CVS module, we have a file perlmod/Fink/FinkVersion.pm.in . > That is processed with some sed magic in the setup.sh script. So naturally, >

Re: [Fink-devel] "make test" failure report (run on CVS HEAD, just now)

On Thu, Nov 20, 2003 at 10:20:21AM -0500, David R. Morrison wrote: > ./Command/failure...# Failed test (./Command/failure.t at line 106) > # Failed test (./Command/failure.t at line 156) > # got: undef > # expected: '1069341580' > # Looks like you failed 2 tests of 45.

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

On Thu, Nov 20, 2003 at 10:06:10AM -0500, Benjamin Reed wrote: > >Doesn't matter. The test-harness-pm probably isn't using UNINST=1 so > >its probably shadowed by the original version in 5.6.0, too. > > Uninstalling the original version in 5.6.0 is against Fink policy > though. Shouldn't it sti

Re: [Fink-devel] sources for xc-20031117.tar.bz2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 20, 2003, at 4:14 PM, Anthony DeRobertis wrote: And http://cvs.debian.org/debian-cd/Attic/pkg-order makes interesting reading. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pkg-order&archive=yes as well. "Hi, I have asked pkg-orde

Re: [Fink-devel] Failed make test

And by the way, apparently the reason you're not seeing the other errors I saw (and reported here today, albeit belatedly), is that you ran "make test" as an ordinary user and the dubious tests were skipped, whereas I ran "sudo make test" (thus mimicking the behavior of fink when it installs the f

Re: [Fink-devel] Failed make test

Well, this one is easy to understand, but I'm not sure how to fix it. In the "fink" CVS module, we have a file perlmod/Fink/FinkVersion.pm.in . That is processed with some sed magic in the setup.sh script. So naturally, there is a "compile failure" when FinkVersion.pm is invoked. -- Dave Da

Re: [Fink-devel] selfupdate-cvs broken?

Darian Lanx wrote: Please note. If you are using the "unstable" package manager versioned 0.17.1 and you are NOT behind a firewall or a developer, please use fink selfupdate-rsync to switch to the now preferred rsync method and then fink selfupdate subsequently. CVS updating is only a last reso

[Fink-devel] Failed make test

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Here is the output. The CVS up -Pd is maybe 5 minutes old mule:~/tmpdir/fink$ make test ./00compile.NOK 31# Failed test (./00compile.t at line 20) # got: 'Can't locate Fink/FinkVersion.pm in @INC (@INC contains: ../p

Re: [Fink-devel] selfupdate-cvs broken?

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Anthony DeRobertis wrote: Please note. If you are using the "unstable" package manager versioned 0.17.1 and you are NOT behind a firewall or a developer, please use fink selfupdate-rsync to switch to the now preferred rsync method and then fi

Re: [Fink-devel] selfupdate-cvs broken?

This is in the FAQ: http://fink.sourceforge.net/faq/usage-fink.php#cvs-busy I'd bet the problem isn't in x11-wm On Thursday, November 20, 2003, at 03:57 PM, Anthony DeRobertis wrote: U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-2.4.15-11.patch U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-no-gnome-2

Re: [Fink-devel] selfupdate-cvs broken?

yes x11-wm isn't the problem, those are all Us look for an other letter higher up -TS On 20-Nov-03, at 1:57 PM, Anthony DeRobertis wrote: U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-2.4.15-11.patch U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-no-gnome-2.4.15-11.info U 10.3/unstable/main/finkinfo

Re: [Fink-devel] sources for xc-20031117.tar.bz2

On Nov 20, 2003, at 14:47, Alexander K. Hansen wrote: This can happen if the upstream site (and mirrors) removes the tarball before it gets mirrored onto the master (opendarwin) site. I got bitten this way by pkg-order, which has apparently been purged by Debian. http://archive.debian.org/d

[Fink-devel] selfupdate-cvs broken?

U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-2.4.15-11.patch U 10.3/unstable/main/finkinfo/x11-wm/fvwm2-no-gnome-2.4.15-11.info U 10.3/unstable/main/finkinfo/x11-wm/icewm-1.2.2-1.info U 10.3/unstable/main/finkinfo/x11-wm/icewm-1.2.2-1.patch U 10.3/unstable/main/finkinfo/x11-wm/icewm-basic-1.2.2-1.inf

Re: [Fink-devel] sources for xc-20031117.tar.bz2

Randal L. Schwartz wrote: "Alexander" == Alexander K Hansen <[EMAIL PROTECTED]> writes: Alexander> I don't believe that there's an automatic method: I usually wind up Alexander> grep'ing to find stuff like this. Ahh, found it. Paging Benjamin Reed <[EMAIL PROTECTED]>... your xfree86.info file

Re: [Fink-devel] sources for xc-20031117.tar.bz2

> "Alexander" == Alexander K Hansen <[EMAIL PROTECTED]> writes: Alexander> I don't believe that there's an automatic method: I usually wind up Alexander> grep'ing to find stuff like this. Ahh, found it. Paging Benjamin Reed <[EMAIL PROTECTED]>... your xfree86.info file is broken - mentionin

Re: [Fink-devel] sources for xc-20031117.tar.bz2

This can happen if the upstream site (and mirrors) removes the tarball before it gets mirrored onto the master (opendarwin) site. I got bitten this way by pkg-order, which has apparently been purged by Debian. I believe that testing has historically relied on users reporting bad links or peop

Re: [Fink-devel] Phasing out references to Mac OS X 10.1 (Doc Maintainers?)

One place where we shouldn't touch the existing reference is the package database page: 10.1 users should have available exactly what versions of packages exist for them. Unless we want just to have a separate 10.1-specific document which includes that information. That would involve a fair a

[Fink-devel] Re: [Fink-users] libmikmod 3.1.10-2: Bad Download URL in .info File

This happens: fink-devel is the place to send messages about unmaintained packages -- I've cc'ed them. On Thursday, November 20, 2003, at 01:45 PM, Emily Jackson wrote: The download URL for this package () leads to a file with the

Re: [Fink-devel] "WARNING: Unable to parse ..." after upgrade

You're right, it probably should. What is currently in 0.17.1 should work with virtually all versions of rsync (as long as 'rsync' is really rsync). But, an explicit path is more reliable. Rob On Wed, Nov 19, 2003 at 10:35:20PM -0800, Ben Hines wrote: > Really fink should not be calling 'rsync'

Re: [Fink-devel] Phasing out references to Mac OS X 10.1 (Doc Maintainers?)

I see postings on the lists every so often for people who are still on 10.1.x, but I'm not against this. In any case we need to update the docs for 10.3-specific issues, particularly the Running X11 document. On Thursday, November 20, 2003, at 12:54 PM, Darian Lanx wrote: -BEGIN PGP SIGNED

Re: [Fink-devel] Phasing out references to Mac OS X 10.1 (Doc Maintainers?)

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 David R. Morrison wrote: I disagree. As far as I know, our 10.1 distribution still works. Anyone who bought a Mac or a copy of OS X prior to September 2002 and who did not choose to pay for an upgrade will still be running 10.1. We can de-emphas

Re: [Fink-devel] Phasing out references to Mac OS X 10.1 (Doc Maintainers?)

I disagree. As far as I know, our 10.1 distribution still works. Anyone who bought a Mac or a copy of OS X prior to September 2002 and who did not choose to pay for an upgrade will still be running 10.1. We can de-emphasize it, sure, but it is already de-emphasized. -- Dave

[Fink-devel] sources for xc-20031117.tar.bz2

I'm curious about how packages get commited, and yet the source for that package doesn't seem to be in *any* of the places listed for sources. In particular, xc-20031117.tar.bz2 can't be found anywhere, and I've tried repeatedly for the past 24 hours. Do the packages committed get tested to ensu

[Fink-devel] Phasing out references to Mac OS X 10.1 (Doc Maintainers?)

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hello all. Is anyone opposed to phasing out all references to Mac OS X 10.1 ? This would of course also put you, Alexander and htodd on the line to look into the docu and FAQ. Sometimes 10.1 might be needed to state something but on the download

[Fink-devel] Re: -fast flag ?

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 jfm wrote: Hi, I see packages coming up in 10.3 that set the '-fast' flag _ eg, agrep, in the patch (after correcting 644 to 755 in the first install command and fixing the second...) My understanding is that some mechanism would then be needed in

[Fink-devel] -fast flag ?

Hi, I see packages coming up in 10.3 that set the '-fast' flag _ eg, agrep, in the patch (after correcting 644 to 755 in the first install command and fixing the second...) My understanding is that some mechanism would then be needed in fink to automatically add the appropriate -mcpu and -mtune fl

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 TheSin wrote: | David is the Project lead :) If he is asking then the fink-core doesn't | know :) | I am the project lead? Gee thank you Justin ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) Comment: Using GnuPG with Thunderbird

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

Benjamin Reed wrote: > Uninstalling the original version in 5.6.0 is against Fink policy > though. Shouldn't it still be finding ours first if we're setting > PERL5LIB? I don't know the exact problem here, but from a clean bootstrap we do not set PERL5LIB. The failures weren't from bootstrap thou

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

I sent you all the failures in my message. -TS On 20-Nov-03, at 7:47 AM, Michael G Schwern wrote: Again, unless I can see the failure report this is complete guesswork. smime.p7s Description: S/MIME cryptographic signature PGP.sig Description: This is a digitally signed message part

[Fink-devel] guile-1.4-7

when doing an update-all, guile-1.4-7 told me that gcc 3.1 was needed; the installation process did not accept the newly installed gcc 3.3 (august 2003 patch) I then used the "sudo gcc_select 3" command which made the update work. After tat , I returned to "sudo gcc_select 3.3" Regards Rolan

[Fink-devel] "make test" failure report (run on CVS HEAD, just now)

./00compile.ok ./Base/initialize...ok ./Base/paramok ./Base/param_booleanok ./Command/cat...ok ./Command/chowname..ok ./Command/commands..ok ./Command/exports...ok ./Command/failure...# Failed test (./Co

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

David is the Project lead :) If he is asking then the fink-core doesn't know :) -TS On 20-Nov-03, at 7:47 AM, Michael G Schwern wrote: Yes, I know. As mentioned the fink-core guys are aware of it and it looks like the testing packages will be going into bootstrap. smime.p7s Description:

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

I think most of these are mine, and I haven't updated perl mods since WWDC since I didn't know how i was gonna handle this. -TS On 20-Nov-03, at 7:35 AM, David R. Morrison wrote: -- Dave P.S. Fink claims that my test-harness-pm, test-inline-pm, and test-simple-pm packages are up to date.

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

> Run "perl -MTest::Harness -wle 'print $Test::Harness::VERSION'" and let me > know what it says. 2.26 > If its less than 2.00 then you have a shadowing > problem. Check "perldoc -l Test::Harness" to find out what file Perl is > loading for Test::Harness. /sw/lib/perl5/Test/Harness.pm -- D

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

Michael G Schwern wrote: P.S. Fink claims that my test-harness-pm, test-inline-pm, and test-simple-pm packages are up to date. Doesn't matter. The test-harness-pm probably isn't using UNINST=1 so its probably shadowed by the original version in 5.6.0, too. Uninstalling the original version in 5.6

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

On Thu, Nov 20, 2003 at 09:35:38AM -0500, David R. Morrison wrote: > > To fix, try reinstalling Test::Harness from > > http://search.cpan.org/dist/Test-Harness/ and use "make install UNINST=1" > > to make sure the old version is deleted. > > This is not The Fink Way (TM). :) No, this is The Try

[Fink-devel] Perl testing docs

Here's some links to tutorials about how Perl's testing system works. Test::Tutorial. Enough to get you going. perldoc Test::Tutorial http://search.cpan.org/dist/Test-Simple/lib/Test/Tutorial.pod Test::Simple. The simplest possible testing library. One function. Good place to s

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

> To fix, try reinstalling Test::Harness from > http://search.cpan.org/dist/Test-Harness/ and use "make install UNINST=1" > to make sure the old version is deleted. This is not The Fink Way (TM). :) We need robust fink packages for 5.6.0 which install the Test:: code in whatever way its going to

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

On Thu, Nov 20, 2003 at 08:28:04AM -0500, David R. Morrison wrote: > On the other hand, very few of the fink developers have any experience with > any of the perl testing stuff. This makes it hard to even know how to > report a failure. At the very least just cut & paste the failing portion of th

Re: [Fink-devel] Fwd: Your message to fink-core awaits moderator approval

TheSin wrote: I agree and the same with gnome-core Yeah, I've fixed it and signed up both fink-core and fink-gnome-core to gmane so we should get archives. -- Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/ gpg: 6401 D02A A35F 55E9 D7DD 71C5 52EF A366 D3F6 65FE "You can scoff, Lis

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

well 50% of the ppl couldn't install from HEAD, which is bad and posting to fink-devel won't help unless you write it, we had most of the project admins and some others looking into it, but we have no idea how these .t files work and COmmand.pm isn't even being used. And they won't be forgotte

Re: [Fink-devel] Fwd: Your message to fink-core awaits moderator approval

I agree and the same with gnome-core -TS On 19-Nov-03, at 11:27 PM, Ben Hines wrote: This is not acceptible. fink-core is listed as maintainer for a ton of fink packages, the address needs to be accepting email. For that matter, the list should be open to all who want to monitor and aid wit

Re: [Fink-devel] Don't disable tests. Report the failure. (was Re: fink ChangeLog,1.181,1.182 Makefile,1.4,1.5)

I completely agree that tests should not be disabled. On the other hand, very few of the fink developers have any experience with any of the perl testing stuff. This makes it hard to even know how to report a failure. My saga yesterday evening started when -- in the interests of trying out someb

Re: [Fink-devel] "WARNING: Unable to parse ..." after upgrade

Ben Hines <[EMAIL PROTECTED]> wrote: > Really fink should not be calling 'rsync'. It should be using > /usr/bin/rsync in any case, just like every single other external call > in fink does. I see no reason to deviate and trust whatever program a > user has that might be called rsync. > > -Ben