Re: [fink-core] Any objections to a new fink release?

[Max Horn]

Go ahead, and thanks for taking care of it 

> Am 07.02.2016 um 23:11 schrieb Alexander Hansen :
> 
> We’re a couple of El Capitan teeny versions behind on “This distribution is 
> supported and tested.” :-)  We’ve also had a few other fixes.
> 
> 
> 
> 
> -- 
> Alexander Hansen, Ph.D.
> Fink User Liaison
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> fink-core mailing list
> fink-core@lists.sourceforge.net
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.core
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-core

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

[fink-core] Status as Fink maintainer?

[Max Horn]

Hi Fang, (CC: fink-core)

I contacted you last October and this January about updates for mpfr and gmp, 
with new info files attached.

No reply by you. Could you please clarify whether you are still active as 
package maintainer?

Thanks,
Max
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] New openssl location

[Max Horn]

Hi,

> On 26 Sep 2016, at 13:44, Daniel Johnson  wrote:
> 
> There is a new OpenSSL libversion out, 1.1.0. I’ve made a new package but 
> want to check with everyone else where I should put it, base or crypto. It 
> does have a new BuildDepends, text-template-pm, so that would have to move to 
> base too. Also note that not everything will be able to use it right away. 
> There have been a lot of changes to the API (removed functions, structs made 
> opaque, new threading model) so other packages usually need changes to work 
> with it. Opinions?

Why would we put this into base? The (naive) logical approach would be to put 
it into crypto, and thus also leave text-template-pm out of base.

I don't say there are no good reasons for putting it into base/, but if there 
are, they should be named explicitly.


Cheers,
Max
--
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] Time to de-emphasize SourceForge

[Max Horn]

Hi,


> Am 01.10.2017 um 07:30 schrieb Alexander Hansen :
> 
> 1)  We no longer have the ability to remove locks from CVS.
> 2)  They’ve reduced our ability to administer our mailing lists—the list 
> owner can’t even remove users any more.
> 
> I’d be OK with having users report bugs via issues on GitHub rather than via 
> the mailing list, especially since we’ll be able to associate them directly 
> with the relevant .info and .patch files once we get the distribution up and 
> running there.
> 
> I’m still OK with using SourceForge to host our tarballs.


Not that it matters much, but I agree with all you say (but am on vacation, 
travelling in Australia
> 
> -- 
> Alexander Hansen, Ph.D.
> Fink User Liaison
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> fink-core mailing list
> fink-core@lists.sourceforge.net
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.core
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-core


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] CVS support at SourceForge and Nov. 30

[Max Horn]

Dear all,


SF.net meant to disable CVS commits yesterday, but it seems they have not yet 
(at least I was just able to commit something).


I have been badly out of the loop, but: is anybody working on a transition 
plan? It seems high time for one, no? It seems we need at least this, in order:

1. A fink release with selfupdate-git or -svn support (done!)

2. A full migration of the CVS repository to SVN or GIT (status?)
   and disable write access to the CVS repository for everybody (except for 
handful of admins, so they can perform the next step)

3. A fink release (with an .info file in the CVS repository) which disables 
selfupdate-cvs, and instead prompts the user to switch to the -git or -svn 
variant.

Ideally, around step 2, all maintainers would be notified how to access the new 
distribution, I guess?

Is anybody working on this? If not, once CVS write access is down for good, I 
fear lots of Fink users will be stranded and will require manual work to 
migrate to git/svn.


Cheers,
Max
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

[fink-core] Fink development work flow: pull requests? reviews?

[Max Horn]

Hi there,

so I recently had some time and motivation to work on a few small patches for 
fink. And since things are now on GitHub, I thought it might be best to submit 
them as pull requests, so that they can be reviewed and then merged (as opposed 
to just pushing them directly, as I would have in the distant past).

However, there was little reaction; only dmacks found some time to review them 
(thank you, BTW). Which leaves me wondering how to proceed?

Don't get me wrong, I am not complaining; everybody here is a volunteer, we all 
have little spare time, etc. etc.. I just wonder: Should I go ahead and merge 
my work resp. push directly, w/o care? Or are there any intentions to use pull 
requests systematically? I.e. should I wait more, and then "somebody" will 
review and merge those PRs? I've been "out of town" for quite some time and 
don't want to step on anybodies toes, as I have no idea how things are done now 
(it seems most development discussions still happen on IRC, like in the bad old 
days, i.e. completely intransparent to outsiders?)

Cheers,
Max
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] Merge #166 ?

[Max Horn]

> On 12. Dec 2018, at 11:11, Hanspeter Niederstrasser  
> wrote:
> 
> On 12/11/18 11:14 PM, Alexander Hansen wrote:
>> I was thinking that it might help us if we do the aforementioned merge to 
>> facilitate community testing, etc.
>> -akh
> 
> I'm OK with that. TheSin said he'd added a couple local changes on top of 
> jwhowarth's pull and been running OK with them. I *think* it might be 
> possible to edit the files via the web interface even though the pull comes 
> from jwhowarth's clone. I know I can see the edit pencil icon, but I haven't 
> tried to actually save a change.

You can probably also push to this PR. And then e.g. squash some changes.

> 
> Might be good to have those changes then merge, or just merge as is and then 
> ask TheSin to make a pull for his changes and merge them quickly.

Or, make a new PR with all the changes?

By chance, I have finally updated from OS X 10.11 to 10.14, so I guess I could 
help.

I just made a new https://github.com/fink/fink/pull/170 with the changes 
squashed into a PR, and will now work on addressing the open suggestions, and 
test it on my system.

Cheers,
Max

___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] Merge #166 ?

[Max Horn]

PS:

I have now committed a fix for python2.7, in which I point it at the SDK_PATH. 
So, yeah, it seems useful to expose that to packages. Perhaps we might even 
want to add `-I$SDK_PATH/usr/include` to the default CPPFLAGS?

Note: the headers in /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk are 
not enough, it really needs to "see" the full 10.14 SDK in order to work.

I am told that another way to solve the problem with Python 2.7 (and probably 
many other packages) is to install headers into /usr/include, by running

sudo installer -pkg 
/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
 -target / 

See also 


Alas, I am not sure that we can or want to suggest this to users.


Cheers,
Max

___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] Merge #166 ?

[Max Horn]

Hi all,

thanks for the feedback, I have fixed the ARCHFLAGS now and made the code 
generally more robust, adding a new helper Fink::Services::get_sdkpath() which 
returns an empty string on Darwin < 18 and the SDK path as returned by `xcrun 
--sdk macosx --show-sdk-path`. I believe it would make sense to change that 
Darwin version cutoff to a lower value, but for now wanted to play it safe.

The perlmodule builds fine now, but python is still broken. Hanspeter hinted 
that normally it finds zlib; so I am guessing this might be another case where 
the SDK path needs to be inserted somewhere. I'll take a look.

In general, I noticed that in various .info files, we might have to start using 
the SDK path now. Perhaps time to introduce %{sdkpath} for that? Any concerns 
about doing just that?

E.g. in libcurl4.info, we have this in the PatchScript:

/bin/cp /usr/include/lber*.h .
/bin/cp /usr/include/ldap*.h .
/bin/cp /usr/lib/libldap.dylib .

That is of course easy to adjust (and indeed, I just see that somebody did it). 
But there is also this in ConfigureParams:

ConfigureParams: <<
--with-darwinssl \
--without-ssl \
--without-gnutls \
--with-libssh2=%p \
--with-gssapi=/usr \
...

and that last line could be easily turned into

--with-gssapi=%{sdkpath}/usr \


Any thoughts on that?

Cheers,
Max

___
fink-core mailing list
fink-core@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core

Re: [fink-core] Merge #166 ?

[Max Horn]

> On 12. Dec 2018, at 12:14, Max Horn  wrote:
> 
> 
> 
>> On 12. Dec 2018, at 11:11, Hanspeter Niederstrasser  
>> wrote:
>> 
>> On 12/11/18 11:14 PM, Alexander Hansen wrote:
>>> I was thinking that it might help us if we do the aforementioned merge to 
>>> facilitate community testing, etc.
>>> -akh
>> 
>> I'm OK with that. TheSin said he'd added a couple local changes on top of 
>> jwhowarth's pull and been running OK with them. I *think* it might be 
>> possible to edit the files via the web interface even though the pull comes 
>> from jwhowarth's clone. I know I can see the edit pencil icon, but I haven't 
>> tried to actually save a change.
> 
> You can probably also push to this PR. And then e.g. squash some changes.
> 
>> 
>> Might be good to have those changes then merge, or just merge as is and then 
>> ask TheSin to make a pull for his changes and merge them quickly.
> 
> Or, make a new PR with all the changes?
> 
> By chance, I have finally updated from OS X 10.11 to 10.14, so I guess I 
> could help.
> 
> I just made a new https://github.com/fink/fink/pull/170 with the changes 
> squashed into a PR, and will now work on addressing the open suggestions, and 
> test it on my system.

So that PR seems to work, basically, but various packages have issues. Would be 
interesting to know what additional changes TheSin has...

I already pushed a fix for texinfo.info which enables it on 10.14. But now 
python27 fails to build (and that blocks a ton of other stuff):

gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -fwrapv -O3 -Wall 
-Wstrict-prototypes -I_ctypes/darwin -I/sw/include -I. -IInclude -I./Include 
-I/sw/include -I/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Include 
-I/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15 -c 
/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/darwin/dlfcn_simple.c
 -o 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/darwin/dlfcn_simple.o
 -DMACOSX
gcc -L/sw/lib -bundle 
/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/libpython2.7.dylib -L/sw/lib 
-L/sw/lib -I. -IInclude -I./Include -I/sw/include 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/_ctypes.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/callbacks.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/callproc.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/stgdict.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/cfield.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/malloc_closure.o
 
build/temp.macosx-10.14-x86_64-2.7/sw/src/fink.build/python27-2.7.15-1/Python-2.7.15/Modules/_ctypes/darwin/dlfcn_simple.o
 -L/sw/lib -L. -lffi -ldl -o build/lib.macosx-10.14-x86_64-2.7/_ctypes.so

Python build finished, but the necessary bits to build these modules were not 
found:
bsddb185   dl imageop
linuxaudiodev  nisossaudiodev
spwd   sunaudiodevzlib
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.
(Fink package build should have 7 missing)

make: *** [sharedmods] Error 1
### execution of make failed, exit code 2
### execution of /tmp/fink.2ROxo failed, exit code 2
Removing runtime build-lock...
Removing build-lock package...
/sw/bin/dpkg-lockwait -r fink-buildlock-python27-2.7.15-1
(Reading database ... 91352 files and directories currently installed.)
Removing fink-buildlock-python27-2.7.15-1 ...
Failed: phase compiling: python27-2.7.15-1 failed



Moreover, it seems that building -pm5182 perlmod packages may fail, e.g.:

Params-Util-1.07/t/13_all.t
Params-Util-1.07/t/03_all.t
sudo -u fink-bld [ENV] sh -c /tmp/fink.fdGjL
/tmp/fink.L76Fh
#!/bin/sh -ev
 export PERL_EXTUTILS_AUTOINSTALL=--skip
 
ARCHFLAGS="-I$sdkpath/System/Library/Perl/$perlversion/darwin-thread-multi-2level/CORE"
 /usr/bin/arch -x86_64 perl5.18 Makefile.PL PERL="/usr/bin/arch -x86_64 
perl5.18" PREFIX=/sw INSTALLPRIVLIB=/sw/lib/perl5/5.18.2 
INSTALLARCHLIB=/sw/lib/perl5/5.18.2/darwin-thread-multi-2level 
INSTALLSITELIB=/sw/lib/perl5/5.18.2 
INSTALLSITEARCH=/sw/lib/perl5/5.18.2/darwin-thread-multi-2level 
INSTALLMAN1DIR=/sw/share/man/man1 INSTALLMAN3DIR=/sw/share/man/man3 
INSTALLSITEMAN1DIR=/sw/share/man/man1 INSTALLSITEMAN3DIR=/sw/share/man/man3 
INSTALLBIN=/sw/bin INSTALLSITEBIN=/sw/bin INSTALLSCRIPT=/sw/bin
sanexs-Fq82m.c:1:10: fatal error: 'EXTERN.h' file not found
#include "EXTERN.h"
 ^~
1 error generated.
Unresolvable broken external