Re: [Fink-users] Re: [Fink-devel] autoconf2.5

2003-01-17 Thread jfm 

On Friday, Jan 17, 2003, at 21:09 Europe/Brussels, Kow K wrote:


In my case, it worked out when I updated autoconf2.5 after updating 
automake, without using "fink update-all".

That should be correct, but stuphead and gbiff (still in 10.1..) 
"Depend" on automake...
So same problem for automake, for those who have one of those packages.

JF Mertens



---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Re: [Fink-users] Re: [Fink-devel] autoconf2.5

2003-01-17 Thread Kow K 
I wasn't clear enough, it seems. I performed "fink update automake" 
first, and then "fink update autoconf2.5". This fixed up the 
circulairty problem.

Kow

On Friday, January 17, 2003, at 12:50 PM, Michèle Garoche wrote:


Le vendredi, 17 jan 2003, à 21:09 Europe/Paris, Kow K a écrit :


In my case, it worked out when I updated autoconf2.5 after updating 
automake, without using "fink update-all".
Yes, but then if you run selfupdate-cvs, Fink redeselect autoconf2.5 
and reselect autoconf25. Quadrature of circle.

What should I do exactly? I have a bunch of packages to update since 
14th:

The following 13 packages will be installed or updated:
 autoconf25 automake docbook-dtd gal21 gal21-shlibs nano opensp3
 opensp3-shlibs openssl openssl-dev openssl-shlibs scrollkeeper
 xfonts-shinonome
The following 7 additional packages will be installed:
 autoconf2.5 automake1.6 gnome-libs-dev libtool14 libtool14-shlibs 
libxslt
 libxslt-shlibs

On Friday, January 17, 2003, at 11:55 AM, Martin Costabel wrote:


There are problems with the new autoconf2.5:

- automatic updating doesn't work, autoconf25 has to be 
force-removed first.

- Provides: autoconf25-2.54 doesn't look right. Shouldn't this be 
just autoconf25. Or is there now a versioning mechanism for virtual 
packages? In any case, I am unable to remove the dummy 
autoconf25-2.54-2, because then nothing would Provide autoconf25.

%fink list autoconf2
 i   autoconf2.5  2.54-1  System for generating configure scripts
 i   autoconf25   2.54-2  Upgrade package -> autoconf2.5
 autoconf25-2.54  [virtual package]

--
Martin
Martin, any idea?

Michèle




---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts 
will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit 
encryption.
Get a guide 
here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users




---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Re: [Fink-users] Re: [Fink-devel] autoconf2.5

2003-01-17 Thread Michèle Garoche 

Le vendredi, 17 jan 2003, à 21:09 Europe/Paris, Kow K a écrit :


In my case, it worked out when I updated autoconf2.5 after updating 
automake, without using "fink update-all".
Yes, but then if you run selfupdate-cvs, Fink redeselect autoconf2.5 
and reselect autoconf25. Quadrature of circle.

What should I do exactly? I have a bunch of packages to update since 
14th:

The following 13 packages will be installed or updated:
 autoconf25 automake docbook-dtd gal21 gal21-shlibs nano opensp3
 opensp3-shlibs openssl openssl-dev openssl-shlibs scrollkeeper
 xfonts-shinonome
The following 7 additional packages will be installed:
 autoconf2.5 automake1.6 gnome-libs-dev libtool14 libtool14-shlibs 
libxslt
 libxslt-shlibs

On Friday, January 17, 2003, at 11:55 AM, Martin Costabel wrote:


There are problems with the new autoconf2.5:

- automatic updating doesn't work, autoconf25 has to be force-removed 
first.

- Provides: autoconf25-2.54 doesn't look right. Shouldn't this be 
just autoconf25. Or is there now a versioning mechanism for virtual 
packages? In any case, I am unable to remove the dummy 
autoconf25-2.54-2, because then nothing would Provide autoconf25.

%fink list autoconf2
 i   autoconf2.5  2.54-1  System for generating configure scripts
 i   autoconf25   2.54-2  Upgrade package -> autoconf2.5
 autoconf25-2.54  [virtual package]

--
Martin
Martin, any idea?

Michèle




---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

[Fink-users] Re: [Fink-devel] autoconf2.5

2003-01-17 Thread Kow K 
In my case, it worked out when I updated autoconf2.5 after updating 
automake, without using "fink update-all".

Kow

On Friday, January 17, 2003, at 11:55 AM, Martin Costabel wrote:

There are problems with the new autoconf2.5:

- automatic updating doesn't work, autoconf25 has to be force-removed 
first.

- Provides: autoconf25-2.54 doesn't look right. Shouldn't this be just 
autoconf25. Or is there now a versioning mechanism for virtual 
packages? In any case, I am unable to remove the dummy 
autoconf25-2.54-2, because then nothing would Provide autoconf25.

%fink list autoconf2
 i   autoconf2.5  2.54-1  System for generating configure scripts
 i   autoconf25   2.54-2  Upgrade package -> autoconf2.5
 autoconf25-2.54  [virtual package]

--
Martin




---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts 
will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit 
encryption. Get a guide 
here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel




---
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
___
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users