Dear Fink developers,
A side-effect of the way in which we updated to 10.6 was that a number of
packages have existed both in the stable and unstable trees, which were
completely identical other than a restriction on Distribution or Architecture.
This is against Fink policy, since it has the
Dear Sjors,
I'm not convinced that you have correctly diagnosed the crashes you have seen.
The shared libraries of libjpeg and libjpeg8 have different names, and the
dynamic linker cannot possibly confuse them. There is a remote possibility
that some other library is confusing symbols between
Peter,
Let me refer you to a section of the Fink Packaging Manual
http://www.finkproject.org/doc/packaging/policy.php?phpLang=en#sharedlibs which
explains how shared libraries are packaged in fink. Basically, you need to use
fink's Splitoff mechanism to divide your package into a few others.
On Jun 24, 2010, at 8:21 AM, Alexander Hansen wrote:
And why are you marking it as BuildDependsOnly: true? That's normally
reserved for header packages.
He probably did that to get rid of a validator warning, since he does have
header files in his package.
-- Dave
On Jun 24, 2010, at 8:37 AM, Alexander Hansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The experimental apt-shlibs violates the Shlibs policy.
Experimental:
$ dpkg -L apt-shlibs
/.
/sw
/sw/lib
/sw/lib/libapt-inst.1.1.0.dylib
/sw/lib/libapt-pkg.4.8.0.dylib
/sw/share
Jack,
Actually, leaving the old variants of python in place is perfectly OK. There
may be people still using old versions of python (on 10.4 or 10.5) and leaving
these variants for them is fine. Of course, if a maintainer stops being able
to test new versions of the package with old versions
of that was that py23 variants should be depreciated.
Jack
On Sat, Jun 26, 2010 at 09:33:39AM -0600, David R. Morrison wrote:
Jack,
Actually, leaving the old variants of python in place is perfectly OK.
There may be people still using old versions of python (on 10.4 or 10.5) and
leaving
Dear fink developers,
Fink's cryptographic directory crypto has been moved to become a subdirectory
of main, in both the stable and unstable trees.
It is no longer necessary to put something into the crypto directory just
because it depends on something else in the crypto directory. The
Anybody have any ideas about this one? The missing symbol appears to be
present in /sw/lib/libpng.dylib (the one installed by fink's libpng3 package).
Begin forwarded message:
From: Peter Dyballa peter_dyba...@freenet.de
Date: July 5, 2010 1:33:10 PM MDT
To: d...@finkproject.org
Subject:
On Jul 5, 2010, at 4:08 PM, Alexander Hansen wrote:
OK. That explains the issue: The Xquartz release candidate that you're
using libpng14 rather than libpng12, and xfig isn't building against
fink's libpng3 as it should.
As you pointed out, xfig is actually linking to libpng from X11
Anyway, the new revision xfig-3.2.5-1013 should fix this for you.
-- Dave
On Jul 5, 2010, at 4:31 PM, David R. Morrison wrote:
On Jul 5, 2010, at 4:08 PM, Alexander Hansen wrote:
OK. That explains the issue: The Xquartz release candidate that you're
using libpng14 rather than
On Jul 9, 2010, at 7:31 AM, Hanspeter Niederstrasser wrote:
[1] Why the buildworld is building the ptex-base from stable is a whole
other issue, and I have no idea as to why it's doing this. It does
build ptex-base/unstable, but likes to build and use anew
ptex-base/stable in the
The only resolution that I see is to move texlive* and ptex* to stable. Are
they ready?
-- Dave
On Jul 9, 2010, at 1:37 PM, Hanspeter Niederstrasser wrote:
On 7/9/10 11:58 AM, Tomoaki Okayama wrote:
Hi,
At Fri, 9 Jul 2010 08:07:03 -0600,
David R. Morrison wrote:
On Jul 9, 2010
Has anybody seen this error before?
Begin forwarded message:
From: John Davison jmdavi...@optonline.net
Date: August 7, 2010 2:20:59 PM PDT
To: dmr...@users.sourceforge.net
Subject: libpng3-1:1.2.5-2
Feedback: not good
--
Package manager version: 0.21.3
Distribution version:
0.7.1
As Martin Costabel pointed out, both your fink installation and that libpng
package are 6 years out of date. The FAQ should help you figure out how to
update, or if not, people on the fink-users mailing list can help.
-- Dave
On Aug 8, 2010, at 9:19 AM, John Davison wrote:
I noticed the
If I could make a small suggestion on this thread. Fink's support for 10.4
will end fairly soon, so it would not be such a bad thing if gcc 4.5.1 only
runs on 10.5 and 10.6.
-- Dave
On Aug 11, 2010, at 5:36 PM, Jack Howarth wrote:
On Wed, Aug 11, 2010 at 07:48:45PM -0400, Alexander
copy the extant gcc45.patch to gcc45-10.4.patch
commit the 10.5 and 10.6-relevant files (gcc45.patch, gcc45.info,
gcc45-x86_64.info) from the tracker
?
That way we will have the updated gcc45 in 10.5 and 10.6, with the
option to update it in 10.4.
On 8/11/10 9:19 PM, David R. Morrison wrote
On Aug 18, 2010, at 12:14 PM, Sjors Gielen wrote:
Op 18 aug 2010, om 17:47 heeft Benjamin Reed het volgende geschreven:
I'm obviously a supporter of Fink, being one of the core maintainers
and all, but I think trying to package fink with a frontend would be a
nightmare. First, what do you
On Aug 23, 2010, at 12:21 PM, Kees Bakker wrote:
PS and BTW. If the Fink packages were build as fat binaries for i386 and ppc
I would never have tried to use my own framework.
Let me comment about why we don't do this. For a large percentage of open
source packages (the figure 80% is
This sounds like something which should be added to the FAQ if its not there
already.
Also, I'm wondering if we should maybe enhance that validator test so that if
it finds a Shlibs with an incomplete pathname, it gives additional advice (such
as what Ben wrote in this email...)
-- Dave
Are you using the i386 or x86_64 architecture of fink?
On Sep 27, 2010, at 9:35 PM, BABA Yoshihiko wrote:
Hi all,
I installed r-base, then tried to install its packages inside R environment,
with the error below. The binary version of R didn't have such error. Would
it be Fink's problem?
Anyway, I suspect from your error message that you are using 10.6-i386. The R
environment, on the other hand, is making calls to gcc with no arch flag so it
defaults to x86_64, and your libraries are not compatible with that...
-- Dave
On Sep 27, 2010, at 9:43 PM, David R. Morrison wrote
On Sep 30, 2010, at 7:45 AM, Alexander Hansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/29/10 5:08 PM, Ebrahim Mayat wrote:
Hello list
With reference to my submission (#3074237) for fluidsynth-1.1.2, I have
come across a compatibility version issue.
As similarly
(switching to fink-devel)
On Oct 25, 2010, at 9:43 AM, Alexander Hansen wrote:
Start by downloading the Java Developer Package from connect.apple.com,
which now contains the headers. If that doesn't work, then cmake is
going to need to be updated further to cope with the new state of
conTeXt is already present in both fink's tetex and texlive packages.
The dependency issues with tetex and texlive are very complex, and I
do not believe we should accept a separate conTeXt package into fink.
-- Dave
On Feb 7, 2011, at 8:57 AM, Alexander Hansen wrote:
-BEGIN PGP
The original poster showed us a transcript, in which fink tried to do
the swapping, but failed, delivering the dreaded circular
dependencies error message.
-- Dave
On Feb 18, 2011, at 10:01 AM, Daniel Macks wrote:
On Fri, 18 Feb 2011 17:13:37 0100, Martin Costabel wrote:
Alexander
Hello fink-devel.
This user has 10.6 + Xquartz and -- in spite of the builddepends on xmkmf --
has the build fail due to Imake issues, namely
Imake.tmpl: No such file or directory
Anybody have any suggestions here?
-- Dave
Begin forwarded message:
From: Mattia Vaccari
The problem with this approach is that it short-circuits one of Fink's security
features (the checking of MD5sum for source files) and it also short-circuits
Fink's storage of source files in its own archive to guard against the day when
the source file is no longer available from the original
Sounds good to me.
-- Dave
On Apr 20, 2011, at 12:16 PM, Alexander Hansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
3.7 Source Policy
Sources should normally be downloaded from the location(s) that the
upstream developer(s) use, and any modifications for Fink should be
Hi Max, my apologies. This only got half-implmented last night and I was going
to send out an email after it was finished, but I can explain it now.
Our strategy for handling EOL for 10.4 is to place copies of all .info/.patch
files into this 10.4-EOL subdirectory of finkinfo, and then to
There was a recent revision to the transfig package which introduced the use of
fink's flag-sort package. However, it seems to have a problem on 10.6: see
below. Anybody have any advice about it?
-- Dave
Begin forwarded message:
From: Densmore, Jeffery D j...@lanl.gov
Date: July 19,
Jeffery: please see the question at the bottom:
Begin forwarded message:
From: Alexander Hansen alexanderk.han...@gmail.com
Date: July 19, 2011 1:01:21 PM PDT
To: David R. Morrison d...@finkproject.org
Cc: Fink fink-devel fink-devel@lists.sourceforge.net, j...@lanl.gov
Subject: Re: [Fink
Jack,
Many of our package maintainers will now be faced with trying to
maintain a package across several distributions, and in cases where
there doesn't need to be a difference, the maintenance is easier if
the foo.info files are identical.
So generally, copying the same version, revision,
, Jul 21, 2011 at 09:45:05AM -0700, David R. Morrison wrote:
Jack,
Many of our package maintainers will now be faced with trying to
maintain a package across several distributions, and in cases where
there doesn't need to be a difference, the maintenance is easier if
the
foo.info files
In a discussion on irc this morning, there was a general consensus to bring
Python 2.6 and 2.7 forward to 10.7, but not to bring Python 2.5 forward. I
subsequently put the python26 and python27 packages into the 10.7 tree.
What about perl? Should we bring perl 5.8.8 forward, or leave it out?
21, 2011, at 11:16 AM, Daniel Macks wrote:
On Thu, 21 Jul 2011 11:00:03 -0700, David R. Morrison wrote:
In a discussion on irc this morning, there was a general consensus to
bring Python 2.6 and 2.7 forward to 10.7, but not to bring Python 2.5
forward. I subsequently put the python26
On Sep 15, 2011, at 7:05 AM, Sébastien Maret wrote:
Le 15 sept. 2011 à 15:51, Alexander Hansen a écrit :
We probably don't want just to dump packages into stable without doing a
little testing to make sure they all actually work. ;-) One option would
be something like the following:
So at the very least, we should put a news item on the fink webpage warning
users that fink on 10.6 is currently incompatible with Xcode 4.2, and
suggesting a downgrade to Xcode 3.2.6.
Another short-term measure would be to put a test into fink to check for Xcode
4.2 on 10.6, and warn users
On Oct 21, 2011, at 8:50 AM, Jack Howarth wrote:
On Fri, Oct 21, 2011 at 08:05:38AM -0700, David R. Morrison wrote:
So at the very least, we should put a news item on the fink webpage warning
users that fink on 10.6 is currently incompatible with Xcode 4.2, and
suggesting a downgrade
On Oct 24, 2011, at 7:49 AM, Jack Howarth wrote:
On Fri, Oct 21, 2011 at 09:01:58AM -0700, David R. Morrison wrote:
On Oct 21, 2011, at 8:50 AM, Jack Howarth wrote:
On Fri, Oct 21, 2011 at 08:05:38AM -0700, David R. Morrison wrote:
So at the very least, we should put a news item
I wonder if we should put a test for Xcode version into the bootstrap, so that
people get an error message which tells them what is wrong and suggests how to
fix it?
-- Dave
On Nov 23, 2011, at 6:50 AM, Alexander Hansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/11
Thanks for noticing that. I did the update.
-- Dave
On Nov 26, 2011, at 3:16 PM, Hanspeter Niederstrasser wrote:
Dave,
Is it possible to update Fink's fribidi to the latest upstream? A package
I'm trying needs fribidi 0.19. According to the fribidi page, 0.19 is
API/ABI compatible
There is a problem with libgeos on 10.7.
The most recent XCode will not compile it, even using llvm-gcc-4.2.
The MacPorts project is also aware of this; they actually have a package called
apple-gcc-4.2 which provides the now-missing gcc-4.2 from apple for people
who have upgraded XCode.
Thanks, I'll try 3.3.1.
-- Dave
On Nov 28, 2011, at 2:16 PM, Merle Reinhart wrote:
Dave,
I just noticed your post about libgeos not working in 10.7 with XCode
compilers.
I do know that libgeos 3.3.1 WILL successfully build in 10.7 with the XCode
4.2 clang compiler. I'm using
The dependent packages not yet in 10.7 are: farsight2, libnice, and
silc-toolkit.
All three of these, and pidgin itself, built for me on 10.7 this evening.
-- Dave
On Jan 4, 2012, at 6:07 PM, David Fang wrote:
Hi, sorry to bother you, I was just wondering when there might be a fink
I'm curious where you are putting the dylibs? (haven't had a chance to look at
the packages)
-- Dave
Sent from my iPhone
On Jan 21, 2012, at 5:24 PM, Sjors Gielen sj...@sjorsgielen.nl wrote:
Hi Alexander,
Op 22-01-12 00:17, Alexander Hansen schreef:
Let's try to stay close to our
My recollection of the original idea was that there might be a package with
binaries, static libs, and headers all together. I dont know if there are any
such left, but if there are, they will need to be splitoffized to separate the
binaries (should this change be made).
-- Dave
Sent from
-only libraries and maybe some executables, and
especially if also executables other packages tend to Depends on them.
That makes it difficult to upgrade them to be shared or for
backward-incompatible new libversions even if still static-only.
dan
On Tue, 24 Jan 2012 15:57:59 -0800, David R
On Apr 29, 2012, at 10:57 AM, Daniel Macks wrote:
On Sun, 29 Apr 2012 09:43:33 -0700, Alexander Hansen
alexanderk.han...@gmail.com wrote:
We've got some maintainers (J. Howarth, H. Todd that I know of) who
have
access to Mountain Lion. Jack, in particular has been doing build
tests. To
On May 4, 2012, at 10:56 PM, Alexander Hansen wrote:
On 5/4/2012 8:54 PM, Jack Howarth wrote:
My biggest concern with the 10.8 support is the situation with the perlmod
packages.
Specifically whether we could adjust fink to automatically handle the newer
perl in each OS
release without
I think Dustin's approach is a good one -- less intrusive to users' systems.
-- Dave
On May 10, 2012, at 4:32 AM, Dustin Cartwright wrote:
On Thu, May 10, 2012 at 12:45 AM, Alexander Hansen
alexanderk.han...@gmail.com wrote:
We're approaching the May 16 planned deadline for a new Fink
build process it will
have the wrong perms, unless things have changed since then.
---
TS
http://www.southofheaven.org/
Life begins and ends with chaos, live between the chaos!
On 2012-05-10, at 6:33 AM, David R. Morrison wrote:
I think Dustin's approach is a good one -- less intrusive
On May 13, 2012, at 3:14 PM, Merle Reinhart wrote:
One possibility would be make the id static or dynamic based upon a
configuration setting in fink.conf. I think you'll wind up with a lot less
push-back from IT admins.
We've done things like this in the past. We can store the desired
On Jun 15, 2012, at 8:53 AM, Alexander Hansen wrote:
On 6/15/12 6:08 AM, Sébastien Maret wrote:
Hi all,
I spent most of this morning trying to install Fink on one of my colleague
computer. This made me realize how complicated it is for the end-user.
Pretty much everything that could get
On Jun 22, 2012, at 10:59 AM, Alexander Hansen wrote:
Any thoughts about moving dists/ over to github?
Even though sourceforge isn't going to close down CVS access, it'd be
nice to move to a more modern system. Plus, for users behind firewalls,
github allows files to be accessed via
On Jun 24, 2012, at 10:17 AM, David Lowe wrote:
On 2012 Jun 22, at 2:35 PM, Hanspeter Niederstrasser wrote:
Buildworlds and dist-wide package roundups (like unstable-stable
or multi-package dep upgrades) need a lot of overlapping local
modifications and VCS-updating steps, and I stopped
/usr/bin/readlink is present on both 10.6 and 10.5.
-- Dave
On Jun 27, 2012, at 7:44 AM, TheSin wrote:
it turns out that Lion have /usr/bin/readlink as well, can anyone confirm
this on 10.6/10.5 if so then it won't matter if I replace debianutils.
---
TS
http://www.southofheaven.org/
Dear Fink developers,
At the time of the upgrade to 10.7, many fink -pm5123 packages were limited to
Distribution: 10.7 only. Since we will make perl 5.1.23 available in 10.8,
that restriction is no longer necessary or appropriate. On behalf of the
fink-core team, I plan to alter such
Is there any possibility that we can just disable the need for Tex by telling
some package with a configure option that it should build it's Tex docs?
-- Dave
On Jun 29, 2012, at 9:50 AM, TheSin the...@southofheaven.org wrote:
I already thought of these options, the problem would be the
On Jun 29, 2012, at 10:56 AM, Jack Howarth wrote:
Dear Fink developers,
At the time of the upgrade to 10.7, many fink -pm5123 packages were limited
to Distribution: 10.7 only.
Since we will make perl 5.1.23 available in 10.8, that restriction is no
longer necessary or appropriate.
On
On Jun 29, 2012, at 12:40 PM, Hanspeter Niederstrasser wrote:
On 6/29/2012 1:13 PM, David R. Morrison wrote:
On Jun 29, 2012, at 10:56 AM, Jack Howarth wrote:
Dear Fink developers,
At the time of the upgrade to 10.7, many fink -pm5123 packages were
limited to Distribution: 10.7 only
My recollection is that we hacked the dpkg code to allow unversioned virtuals
at the time we introduced virtual pkgs.
-- Dave
On Jun 29, 2012, at 2:01 PM, TheSin wrote:
So I'm not sure how but the old dpkg seemed to not check version of
fink-virtuals, the patch I'm using is pretty much
On Jul 2, 2012, at 11:55 AM, Daniel Macks wrote:
On Sun, 01 Jul 2012 21:59:43 +0200, Sjors Gielen sj...@sjorsgielen.nl wrote:
Op 01-07-12 21:54, TheSin schreef:
would we rather it silently do it or with a warning but still pass?
I assume no warning but thought I'd show an example.
Good point. The reason this was done is documented in the perlXXX.info file,
but you are right that it creates potential upgrade problems.
I guess what we need is a package called perlXXX-upgrade which is a bundle that
depends on all these non-core pm's. Would that solve it, or am I
:59 AM, David R. Morrison wrote:
Good point. The reason this was done is documented in the perlXXX.info
file, but you are right that it creates potential upgrade problems.
I guess what we need is a package called perlXXX-upgrade which is a bundle
that depends on all these non-core pm's
Sounds like a good idea to me.
-- Dave
Sent from my iPhone
On Jul 13, 2012, at 1:46 PM, Hanspeter Niederstrasser f...@snaggledworks.com
wrote:
Currently, if a new passwd-package is created, passwd-core gets a new
version and so all the other passwd-* packages need to be rebuilt and
On Sep 1, 2012, at 1:38 PM, Alexander Hansen alexanderk.han...@gmail.com
wrote:
On 9/1/12 1:07 PM, Hanspeter Niederstrasser wrote:
On 9/1/2012 10:32 AM, Alexander Hansen wrote:
On 8/31/12 5:36 PM, Jack Howarth wrote:
Why exactly are we building the entirety of gettext-tools at -O0
in
Yes, please go ahead and commit the new version.
-- Dave
On Feb 25, 2013, at 8:55 AM, Hanspeter Niederstrasser wrote:
Dave,
I'm packaging the latest libtiff that bumps libN (to libtiff5), and taking
the opportunity to update our existing libtiff to the last of that line.
Here's the
Jack,
I get errors building the latest versions of gcc44 and gcc45 on 10.6, i386 . I
have Xcode 3.2.6 but if that's too old, the packages should tell me so. I
reproduce the error msg from gcc44 below; the one from gcc45 was similar.
Based on the error msg, I guessed that maybe I needed to
Yes, I use tcsh, and which makeinfo now gives me
/sw/opt/texinfo-legacy/bin/makeinfo (to which I say opt???), but
unfortunately the build failed just as before.
-- Dave
On May 5, 2013, at 5:46 PM, Alexander Hansen wrote:
On 5/5/13 4:59 PM, David R. Morrison wrote:
Jack,
I get errors
I started a new shell, to be on the safe side…
On May 5, 2013, at 6:11 PM, Alexander Hansen wrote:
Yeah, %p/opt has been around a while. :-)
Did you start a new shell session or re-source /sw/bin/init.tcsh ?
On 5/5/13 5:59 PM, David R. Morrison wrote:
Yes, I use tcsh, and which makeinfo
On May 6, 2013, at 6:33 AM, Jack Howarth wrote:
On Sun, May 05, 2013 at 04:59:42PM -0700, David R. Morrison wrote:
Jack,
I get errors building the latest versions of gcc44 and gcc45 on 10.6, i386 .
I have Xcode 3.2.6 but if that's too old, the packages should tell me so.
I reproduce
On May 6, 2013, at 9:32 AM, Jack Howarth wrote:
On Mon, May 06, 2013 at 09:02:34AM -0700, David R. Morrison wrote:
On May 6, 2013, at 6:33 AM, Jack Howarth wrote:
On Sun, May 05, 2013 at 04:59:42PM -0700, David R. Morrison wrote:
Jack,
I get errors building the latest versions
Yes, well, I'm on Lion…
On Nov 23, 2015, at 9:28 AM, Alexander Hansen wrote:
>
>> On Nov 23, 2015, at 08:06, Max Horn <m...@quendi.de> wrote:
>>
>> Hi Dave,
>> [CC: fink-devel],
>>
>>> On 22 Nov 2015, at 21:39, David R. Morrison <d...@mat
1101 - 1174 of 1174 matches
Mail list logo
