As part of 'fink configure', HEAD now offers to enable/disable the
unstable entries in /sw/etc/fink.conf:Trees. Default is to leave
current settings unchanged. When enabling, the unstable analog of
each presently-enabled stable tree is appended to the Trees field.
Please test, fix wording of the
Hi Corey!
On 5 Dec 2006, at 02:13, Corey Halpin wrote:
On 2006-12-03, Roland Kuhn wrote:
Just out of curiosity I wanted to install gnupg 2.0.1, so I updated
the info files for libgpg-error, libassuan and libksba8 and added a
gnupg2 package; all *.{info,patch} attached. It works for me (TM).
On 2006-12-05, Roland Kuhn wrote:
Well, that was easy. Now, after also installing pinentry-gtk, of
course, I can decrypt my mails in kmail and even use kwatchgnupg. But
one thing is still missing: I cannot verify my X.509 signatures
because of 'Not enough information to check
That's great!
I wonder whether, when a user has changed the Trees entry, fink
should automatically do a selfupdate at the end of 'fink configure'?
-- Dave
On Dec 5, 2006, at 12:30 AM, Daniel Macks wrote:
As part of 'fink configure', HEAD now offers to enable/disable the
unstable entries
Hi Corey!
On 5 Dec 2006, at 18:09, Corey Halpin wrote:
On 2006-12-05, Roland Kuhn wrote:
Well, that was easy. Now, after also installing pinentry-gtk, of
course, I can decrypt my mails in kmail and even use kwatchgnupg. But
one thing is still missing: I cannot verify my X.509 signatures
Doing a selfupdate automatically after reconfiguring to use unstable
would make sense, since users have to do that anyway if they're using
rsync updating. (and going the other way it would still be a good
idea)
On 12/5/06, David R. Morrison [EMAIL PROTECTED] wrote:
That's great!
I wonder
On Dec 5, 2006, at 11:03 AM, TheSin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
also on this topic, it's a long standing issue and I keep
forgetting to mention it, but when you do the selfupdate from
stable to unstable fink dies on gettext you ened to manually do
fink
On Dec 1, 2006, at 12:18 AM, David Reiser wrote:
On Nov 30, 2006, at 7:36 AM, Chris Zubrzycki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 29, 2006, at 10:22 PM, David Reiser wrote:
Configure checks for the presence of 2 versions of libsoup, and if
neither is present,
Hi,
While trying to download the fink version in cvs, I don't see
anything updated, and the fink version listed is fink-0.24.26, while
my local fink is already at 0.25-2. I am following these
instructions: http://fink.sourceforge.net/doc/cvsaccess/index.php as
linked from the homepage.
On 12/5/06, Koen van der Drift [EMAIL PROTECTED] wrote:
Hi,
While trying to download the fink version in cvs, I don't see
anything updated, and the fink version listed is fink-0.24.26, while
my local fink is already at 0.25-2. I am following these
instructions:
On Dec 5, 2006, at 8:38 PM, Alexander Hansen wrote:
fink selfupdate-cvs should do it. Any chance you're still stuck on
10.4-transitional ?
That's not what I meant, sorry for the confusion. I would like to
install fink in HEAD.
- Koen.
On 12/5/06, Koen van der Drift [EMAIL PROTECTED] wrote:
On Dec 5, 2006, at 8:38 PM, Alexander Hansen wrote:
fink selfupdate-cvs should do it. Any chance you're still stuck on
10.4-transitional ?
That's not what I meant, sorry for the confusion. I would like to
install fink in HEAD.
-
On Dec 5, 2006, at 8:50 PM, Alexander Hansen wrote:
Ah. It's been working for me. How old is your checkout?
The file VERSION is from 20 September, an says 0.24.26.cvs.
- Koen.
-
Take Surveys. Earn Cash. Influence the
On 12/5/06, Koen van der Drift [EMAIL PROTECTED] wrote:
On Dec 5, 2006, at 8:50 PM, Alexander Hansen wrote:
Ah. It's been working for me. How old is your checkout?
The file VERSION is from 20 September, an says 0.24.26.cvs.
- Koen.
I really meant the age on your local machine.
--
Koen van der Drift wrote:
On Dec 5, 2006, at 8:50 PM, Alexander Hansen wrote:
Ah. It's been working for me. How old is your checkout?
The file VERSION is from 20 September, an says 0.24.26.cvs.
According to cvs log, the VERSION that says 0.25.99.cvs dates from 16
September and hasn't
Charles Lepple wrote:
On 12/4/06, Robert T Wyatt [EMAIL PROTECTED] wrote:
Cool! I think the simplest implementation would be to send a successful
build or install message to the maintainer
Hi,
I also like this idea, but I think any build reports should also
include the
16 matches
Mail list logo
