Re: [Fink-devel] FinkCommander 0.5.5 (huh?)

I am getting the following errors when tryin to selfupdate through finkcommander (0.5.5 built in Xcode): I will now run the cvs command to retrieve the latest package descriptions. The 'su' command will be used to run the cvs command as the user 'koen'. After that, the core packages will be up

Re: [Fink-devel] FinkCommander 0.5.5 (huh?)

monipol wrote: > On 04/11/2009, at 20:09, Martin Costabel wrote: >> monipol wrote: >> [] >>> Here's the download URL: >>> https://sourceforge.net/projects/finkcommander/files/FinkCommander/0.5.5/FinkCommander_0.5.5.dmg/download >> Where are the sources for this release? > > I committed the patches

Re: [Fink-devel] FinkCommander 0.5.5 (huh?)

On 04/11/2009, at 20:09, Martin Costabel wrote: > monipol wrote: > [] >> Here's the download URL: >> https://sourceforge.net/projects/finkcommander/files/FinkCommander/0.5.5/FinkCommander_0.5.5.dmg/download > > Where are the sources for this release? I committed the patches about half an hour ago,

Re: [Fink-devel] FinkCommander 0.5.5 (huh?)

monipol wrote: [] > Here's the download URL: > > https://sourceforge.net/projects/finkcommander/files/FinkCommander/0.5.5/FinkCommander_0.5.5.dmg/download Where are the sources for this release? -- Martin -- Let Crysta

[Fink-devel] FinkCommander 0.5.5 (huh?)

Hello, all. I'm about to release FinkCommander 0.5.5. Nope, you're not dreaming! I've just joined the FinkCommander project and I hope I've done everything right in this release. :) FinkCommander is now a fully universal binary (i386, ppc, x86_64, ppc64) thanks to Madd the Sane, it tells whe

Re: [Fink-devel] FinkCommander breakage

On 9/25/06, Philip Lamb <[EMAIL PROTECTED]> wrote: > I just updated to Fink 0.25.0, and it appears that FinkCommander no > longer knows how to deal with the database of installed and available > packages. > > For example, after updating or removing a package, FinkCommander > still lists the old pac

[Fink-devel] FinkCommander breakage

I just updated to Fink 0.25.0, and it appears that FinkCommander no longer knows how to deal with the database of installed and available packages. For example, after updating or removing a package, FinkCommander still lists the old package as installed. It appears that a 'fink index' and/

Re: [Fink-devel] FinkCommander

On Monday, January 27, 2003, at 05:23 AM, David R. Morrison wrote: Ben Hines and I have been working on improving the release process, at least from the technical point of view (creating the binary installer and so on). These improvements include a script Ben wrote to automate I just found

Re: [Fink-devel] FinkCommander

The scripts CVS module is, in my opinion, the best place to store checklists of any kind about the release process. agreed. In terms of timing of announements, though, we need to be careful. WIth this recent release, for example, we unfortunately kept finding little problems with the binary

Re: [Fink-devel] FinkCommander

Ben Hines and I have been working on improving the release process, at least from the technical point of view (creating the binary installer and so on). These improvements include a script Ben wrote to automate the creation of the binary installer, as well as various updates we have made to the HO

Re: [Fink-devel] FinkCommander

At 18:10 Uhr -0800 26.01.2003, Ben Hines wrote: Does anyone object to including FinkCommander on the next Fink .dmg? It is pretty mature these days. I am thinking it would be separate from the .pkg, perhaps in a "FinkCommander" folder with its own readme files and such. Sounds OK I guess. BT

Re: [Fink-devel] FinkCommander

I'm all for it! [EMAIL PROTECTED] writes: >Does anyone object to including FinkCommander on the next Fink .dmg? It >is pretty mature these days. > >I am thinking it would be separate from the .pkg, perhaps in a >"FinkCommander" folder with its own readme files and such. -=[JFH] Justin F. Halle

Re: [Fink-devel] FinkCommander

On Sunday, January 26, 2003, at 09:10 PM, Ben Hines wrote: Does anyone object to including FinkCommander on the next Fink .dmg? It is pretty mature these days. I'm for it. --- This SF.NET email is sponsored by: SourceForge Enterprise Editio

[Fink-devel] FinkCommander

Does anyone object to including FinkCommander on the next Fink .dmg? It is pretty mature these days. I am thinking it would be separate from the .pkg, perhaps in a "FinkCommander" folder with its own readme files and such. -Ben --- This SF.

Re: [Fink-devel] FinkCommander feedback...

At 19:48 Uhr +0100 25.11.2002, jfm wrote: On Monday, Nov 25, 2002, at 19:32 Europe/Brussels, Max Horn wrote: However, there is a catch: to submit the item, the user has to be logged in on the sourceforge site. So, you'd also have to query the users SF.net username and password, then authentica

Re: [Fink-devel] FinkCommander feedback...

true enough, but if the finkcommander users email was the finkcommander mailing list. well then we'd just be assuming they are on the list which could very likely not be true. Well it's an idea i guess. [EMAIL PROTECTED] writes: >That is a serious run on sentence, justin. :) > >Anyway that would

Re: [Fink-devel] FinkCommander feedback...

That is a serious run on sentence, justin. :) Anyway that wouldn't really work.. Users need their own accounts so they will get our requests for more information.. -Ben On Monday, November 25, 2002, at 10:45 AM, Justin Hallett wrote: or if we made a finkcommander user perhaps or made the sf u

Re: [Fink-devel] FinkCommander feedback...

this is true but it has to be done somehow i believe it is a cookie on your system with that browser and since FC wouldn't necessarily use your browser for a POST request it'd need it's own as Max suggested. [EMAIL PROTECTED] writes: >It is still true with the new 'remember' facility on SF ? >I've

Re: [Fink-devel] FinkCommander feedback...

On Monday, Nov 25, 2002, at 19:32 Europe/Brussels, Max Horn wrote: However, there is a catch: to submit the item, the user has to be logged in on the sourceforge site. So, you'd also have to query the users SF.net username and password, then authenticate to the site, store the cookie you get

Re: [Fink-devel] FinkCommander feedback...

or if we made a finkcommander user perhaps or made the sf user name/password in the configure options I think opening the bug tracker to the public isn't 100% bad but I think it's fine the way it is now and we'd need a way to check bugs first to make sure it's not already reported, but I think in t

Re: [Fink-devel] FinkCommander feedback...

At 9:35 Uhr -0700 25.11.2002, Justin Hallett wrote: is there any way to interact with the sf.net tracker and get FC to acctually submit the bug it's self? I thought about that, too. It is possible in theory, by sending the HTTP POST etc. However, there is a catch: to submit the item, the user

Re: [Fink-devel] FinkCommander feedback...

is there any way to interact with the sf.net tracker and get FC to acctually submit the bug it's self? [EMAIL PROTECTED] writes: >As such, I wonder if it would be possible to change the Feedback >feature yet again a bit... maybe one could provide a "Report a bug" >command, which would open the l

[Fink-devel] FinkCommander feedback...

Regarding the FinkCommmander feedback issue.. In the last few days, I have gotten a lot of feedback mails sent via FinkCommander that constitute bug reports. That's not so nice for me, as it's quite hard to track issues sent to me via email - they easily get lost in the suffle (I get hundreds

[Fink-devel] FinkCommander 0.2.0 Released

I have made a new release of FinkCommander available on SourceForge, this time in both binary and source code form. Either one can be downloaded directly from the FinkCommander home page: http://finkcommander.sourceforge.net/index.php The most significant new feature is a filter for searchin

[Fink-devel] FinkCommander 0.1.3 Released

There is a new release of FinkCommander available at: http://sourceforge.net/project/showfiles.php?group_id=48896&release_id=83199 You can access this link from FinkCommander's new SourceForge web site at: http://finkcommander.sourceforge.net/ The most significant change is that FC now allows

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

On Thursday, March 21, 2002, at 10:16 PM, Jeremy Higgs wrote: > One suggestion that I have, though... Thanks for the suggestions. I've put them in my TODO file. My initial reactions: > Perhaps when you click on the name of > a package, the program should show the information immediately, in

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

On 22/3/02 3:47 PM, "Steven Burr" <[EMAIL PROTECTED]> wrote: > > On Thursday, March 21, 2002, at 07:38 AM, Max Horn wrote: > >> Seems as if Preferences.nib is missing from CVS, I can't compile it >> without that. > > Sorry. I ran into the same problem when I did a test run on my kids' > Mac a

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

On Thursday, March 21, 2002, at 07:38 AM, Max Horn wrote: > Seems as if Preferences.nib is missing from CVS, I can't compile it > without that. Sorry. I ran into the same problem when I did a test run on my kids' Mac and thought I had fixed it. I think the repository is in good shape now.

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

On Thursday, March 21, 2002, at 02:29 PM, Steven Burr wrote: > I'd like to make sure I avoid this problem in the future, so I have a > question for the group. Once SourceForge support removes the directory > from the repository, can I safely commit in the future without first > moving build

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

At 9:33 Uhr -0500 21.03.2002, Benjamin Reed wrote: >Steven Burr [[EMAIL PROTECTED]] wrote: >> I'd like to make sure I avoid this problem in the future, so I have a >> question for the group. Once SourceForge support removes the directory >> from the repository, can I safely commit in the futur

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

Seems as if Preferences.nib is missing from CVS, I can't compile it without that. Cheers, Max -- --- Max Horn Software Developer email: phone: (+49) 6151-494890 ___ Fink-devel

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

Steven Burr [[EMAIL PROTECTED]] wrote: > I'd like to make sure I avoid this problem in the future, so I have a > question for the group. Once SourceForge support removes the directory > from the repository, can I safely commit in the future without first > moving build out of the Project Build

Re: [Fink-devel] FinkCommander now available by CVS at SourceForge

On Thursday, March 21, 2002, at 05:34 AM, Max Horn wrote: > you should remove the "build" directory from CVS! It really doesn't > belong there. Since it's a bit tricky (err, impossible) to remove > directories from CVS, you should file a support request with > SourceForge, telling them your pr

[Fink-devel] FinkCommander now available by CVS at SourceForge

FinkCommander now has its own repository on SourceForge. You can access it by anonymous CVS as follows: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/finkcommander login   cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/finkcommander co FinkCommander Thanks to Ben Hines, who showed me the error

[Fink-devel] FinkCommander 0.1.2

FinkCommander v. 0.1.2 is now available for download at: http://homepage.mac.com/sburr/ A column showing whether packages are unstable as well as a few other enhancements have been added. As always, comments are welcome.

Re: [Fink-devel] FinkCommander v. 0.1.1

Just wanted to say that while I haven't yet had a chance to take a look at FinkCommander, I am glad to see somebody is putting some effort in such a software. Go on :-) Max -- --- Max Horn Software Developer email: phone:

Re: [Fink-devel] FinkCommander v. 0.1.1

Personally I think this looks great. Thanks a lot. Also, if you uploaded this to the CVS, it would be really easily to get the newest version since the dev tools have built in CVS tools. > Although it appears from the discussion that this is unlikely to go > anywhere in the near future, I wanted

[Fink-devel] FinkCommander v. 0.1.1

Although it appears from the discussion that this is unlikely to go anywhere in the near future, I wanted to take one more shot at putting out something that might actually work on a system other than my iBook and my kids' G3. If any of you still have the patience to try it after yesterday's