WARNING: Unable to parse "<<" in
"/sw/fink/dists/unstable/crypto/finkinfo/php4-apache2-ssl.info".
can we add a line or something i just can't find the issue with this
one?
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in
this is an excellent point, i didn't have a reason for the plus 10,
just figured it was to be on the safe side and it didn't hurt none, but
this is true, even as a build dep it changes the deb.
On 11-Nov-03, at 9:14 PM, Peter O'Gorman wrote:
David R. Morrison wrote:
Just a followup to my previ
I personally just stop maintaining them, I think that is better then
submitting untested pkgs :)
On 11-Nov-03, at 7:25 PM, Koen van der Drift wrote:
Hi,
Some of my packages have different info files for 10.3, 10.2-gcc3.3
and 10.2. I have upgraded to 10.3, so how do I test/maintain the
.info
David R. Morrison wrote:
Just a followup to my previous message. I've now noticed that the only
change which was made to the package was to remove a BuildDepends on
dlcompat, not a Depends. That shouldn't have required a change to the
revsion number at all!!!
I feel the need to disagree with you
Hi,
Some of my packages have different info files for 10.3, 10.2-gcc3.3 and
10.2. I have upgraded to 10.3, so how do I test/maintain the .info
files for the other systems? For instance when a new upstream version
is released I can only test it on 10.3, but have no means to test it on
other sy
Hi!
I would love to help out, except that What exactly do package maintainers do?
Thanks,
Paul
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Ja
On Tue, Nov 11, 2003 at 11:14:59AM +0100, Max Horn wrote:
> Am Montag, 10.11.03 um 04:05 Uhr schrieb Stefan Langerman:
>
> >The packaging manual section 2.1 says:
> > The name of package description files must be the full package
> > name plus the extension ".info".
> >And section 1.2 says:
> >
Hmm. On the rsync update this morning, fink was updated, said something
about switching to 10.3, and now my 5000 packages are down to 800.
Did the latest update get rid of "unstable"? I can't remember where
I enabled that.
Or is the Right Thing Happening?
--
Randal L. Schwartz - Stonehenge C
Darian Lanx wrote:
[]
If Apple would not cripple basically every open source package that
they put into OSX, Fink could get away with a lot less packages, and
this would make it more attractive.
I beg to differ. Apple has a lot of work keeping their own system sane
and on respectable version nu
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
If Apple would not cripple basically every open source package that they
put into OSX, Fink could get away with a lot less packages, and this
would make it more attractive.
I beg to differ. Apple has a lot of work keeping
Am Dienstag, 11.11.03 um 03:56 Uhr schrieb Michael G Schwern:
Update of /cvsroot/fink/fink/t/PkgVersion
In directory sc8-pr-cvs1:/tmp/cvs-serv17986/t/PkgVersion
Added Files:
get_perl.t sed-4.0.5-1.info
Log Message:
* PkgVersion.pm: Change below broke get_perl_dir_arch(), didn't
Yo folks,
I think it would be preferable to move any discussions about commits
mails from fink-commits to fink-devel. They are very easy to miss
between the dozens of commit mails we get all the time.
As such, I've removed the special posting exceptions for everybody who
had them before. Pleas
On Nov 9, 2003, at 7:05 PM, Stefan Langerman wrote:
Has the policy changed?
Yes. You can use either but name.info is preferred.
-Ben
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
When trying to run Eterm I get the following message:
root# Eterm
dyld: Eterm version mismatch for library: /sw/lib/libImlib2.1.dylib
(compatibility version of user: 2.0.0 greater than library's version:
0.0.0)
I think I need a newer version of Imlib2 to be compiled to match Clef's
new Eterm en
I would also warn against hastily changing all info files in order to
paper over a bug that is not completely understood. The case:
Problems with mv and trailing slashes. There were reports that during
package installation, some mv commands of directories failed. One idea
was that mv was allerg
David R. Morrison wrote:
No, rather the texinfo package should be updated.
This has been on my to-do list for a while.
Recent versions of texinfo require recent versions of gettext. Since the
newest gettext has a binary compatibility change from fink's gettext,
we need a gettext2 package in or
Just a followup to my previous message. I've now noticed that the only
change which was made to the package was to remove a BuildDepends on
dlcompat, not a Depends. That shouldn't have required a change to the
revsion number at all!!!
-- Dave
-
Dear fink developers,
I've just spent 10 minutes chasing down the cause of a bug report I received
from a user.
Here's the cause: somebody edited one of my packages in 10.3/unstable,
removing the dlcompat dependency and increasing the revision number by 10.
Unfortunately they did not change the
> No, rather the texinfo package should be updated.
This has been on my to-do list for a while.
Recent versions of texinfo require recent versions of gettext. Since the
newest gettext has a binary compatibility change from fink's gettext,
we need a gettext2 package in order to update texinfo. T
Am Montag, 10.11.03 um 04:30 Uhr schrieb Stefan Langerman:
The 10.3 tree includes a texinfo package, version 4.2, but Mac OS 10.3
already includes texinfo 4.6.
[...]
Some packages like tetex depend on texinfo. Shouldn't there be
a system-texinfo in case we want to use 4.6 included in Mac OS?
No, r
Am Montag, 10.11.03 um 04:05 Uhr schrieb Stefan Langerman:
The packaging manual section 2.1 says:
The name of package description files must be the full package
name plus the extension ".info".
And section 1.2 says:
The full name of a package is all three items concatenated,
with dashes in
21 matches
Mail list logo
