Re: sourceforge.net - gsmartcontrol 1.1.1 now available

2017-09-26 Thread Clemens Lang
Hi,

On Tue, Sep 26, 2017 at 08:04:36AM +, FritzS - gmx wrote:
> Hi,
> please make an update from gsmartcontrol 1.0.2 to gsmartcontrol 1.1.1
> 
> gsmartcontrol 1.0.2
> https://www.macports.org/ports.php?by=name&substr=gsmartcontrol
> 
> gsmartcontrol  1.1.1
> https://sourceforge.net/projects/gsmartcontrol/ 
> https://sourceforge.net/projects/gsmartcontrol/files/latest/download

https://github.com/macports/macports-ports/pull/835

1.1.0 because sourceforge is in 'disaster recovery mode' at the moment
and does not have the 1.1.1 release in this mode.

Feel free to remind me to update to 1.1.1 once it's back, or, even
better, submit a pull request that updates it to 1.1.1. Presumably only
the version and checksum lines need to be changed.

-- 
Clemens


Re: repairing broken port

2017-09-26 Thread Fielding, Eric J (329A)
Marius,

Thanks for the fast reply! I didn’t see anything in Trac about this, so I had 
guessed that I had done something wrong in my installation. From what you say, 
this is not a pilot error.

++Eric

From: Marius Schamschula 
Date: Tuesday, September 26, 2017 at 6:47 AM
To: "Eric J. Fielding" 
Cc: "macports-users@lists.macports.org" 
Subject: Re: repairing broken port

Eric,

I looks like py-matplotlib-basemap needs a revision bump. If no one beats me to 
it, I should get around to this in the afternoon.

Marius
--
Marius Schamschula



On Sep 26, 2017, at 8:42 AM, Fielding, Eric J (329A) 
mailto:eric.j.field...@jpl.nasa.gov>> wrote:

I have a file that shows up as broken in the automatic scan of the port command:

--->  Scanning binaries for linking errors
--->  Found 1 broken file, matching files to ports
--->  Found 1 broken port:
 py27-matplotlib-basemap @1.0.7
 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so

I tried uninstalling and installing again “py27-matplotlib-basemap”, but that 
does not fix this file. I checked the file “_geoslib.so” with “otool –L” and I 
see that it is linked to an obsolete version of the “libgeos” library (the 
installed version is libgeos-3.6.2.dylib):

% otool -L 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so:
/opt/local/lib/libgeos_c.1.dylib (compatibility version 11.0.0, 
current version 11.0.0)
/opt/local/lib/libgeos-3.5.0.dylib (compatibility version 
0.0.0, current version 0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 1238.0.0)

How do I get the “_geoslib.so” to update correctly? Should I manually remove it 
to force MacPorts to rebuild it?

Thanks,
  ++Eric



Re: repairing broken port

2017-09-26 Thread Marius Schamschula
Eric,

I looks like py-matplotlib-basemap needs a revision bump. If no one beats me to 
it, I should get around to this in the afternoon.

Marius
--
Marius Schamschula



> On Sep 26, 2017, at 8:42 AM, Fielding, Eric J (329A) 
>  wrote:
> 
> I have a file that shows up as broken in the automatic scan of the port 
> command:
>  
> --->  Scanning binaries for linking errors
> --->  Found 1 broken file, matching files to ports
> --->  Found 1 broken port:
>  py27-matplotlib-basemap @1.0.7
>  
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so
>  
> I tried uninstalling and installing again “py27-matplotlib-basemap”, but that 
> does not fix this file. I checked the file “_geoslib.so” with “otool –L” and 
> I see that it is linked to an obsolete version of the “libgeos” library (the 
> installed version is libgeos-3.6.2.dylib):
>  
> % otool -L 
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so:
> /opt/local/lib/libgeos_c.1.dylib (compatibility version 
> 11.0.0, current version 11.0.0)
> /opt/local/lib/libgeos-3.5.0.dylib (compatibility version 
> 0.0.0, current version 0.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
> current version 1238.0.0)
>  
> How do I get the “_geoslib.so” to update correctly? Should I manually remove 
> it to force MacPorts to rebuild it?
>  
> Thanks,
>   ++Eric



repairing broken port

2017-09-26 Thread Fielding, Eric J (329A)
I have a file that shows up as broken in the automatic scan of the port command:

--->  Scanning binaries for linking errors
--->  Found 1 broken file, matching files to ports
--->  Found 1 broken port:
 py27-matplotlib-basemap @1.0.7
 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so

I tried uninstalling and installing again “py27-matplotlib-basemap”, but that 
does not fix this file. I checked the file “_geoslib.so” with “otool –L” and I 
see that it is linked to an obsolete version of the “libgeos” library (the 
installed version is libgeos-3.6.2.dylib):

% otool -L 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so:
/opt/local/lib/libgeos_c.1.dylib (compatibility version 11.0.0, 
current version 11.0.0)
/opt/local/lib/libgeos-3.5.0.dylib (compatibility version 
0.0.0, current version 0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 1238.0.0)

How do I get the “_geoslib.so” to update correctly? Should I manually remove it 
to force MacPorts to rebuild it?

Thanks,
  ++Eric


Re: sourceforge.net - gsmartcontrol 1.1.1 now available

2017-09-26 Thread Ryan Schmidt

On Sep 26, 2017, at 03:04, FritzS wrote:

> please make an update from gsmartcontrol 1.0.2 to gsmartcontrol 1.1.1
> 
> gsmartcontrol 1.0.2
> https://www.macports.org/ports.php?by=name&substr=gsmartcontrol
> 
> gsmartcontrol  1.1.1
> https://sourceforge.net/projects/gsmartcontrol/ 
> https://sourceforge.net/projects/gsmartcontrol/files/latest/download

Updates should be requested by filing tickets in our issue tracker.




Re: Mulberry v4.1d1 for MacPorts?

2017-09-26 Thread Rainer Müller
On 2017-09-26 09:58, FritzS - gmx wrote:
> why did’t Mulberry v4.1d1 available in MacPorts?
> http://trac.mulberrymail.com/mulberry/browser#Mulberry/branches/v4.1d1
> 
> Mulberry is an old IMAP Client and now OpenSource.

MacPorts is a completely volunteer-driven project. Nobody else has
invested time and effort yet to write and submit a Portfile for Mulberry.

You are welcome to contribute to MacPorts and help with making new
software ports available in the MacPorts ports tree. The guide can get
you started with Portfile development, but help with writing Portfiles
is usually provided on the macports-dev mailing list.

https://guide.macports.org/#development

In this case, however, my personal opinion would be that it is not worth
the effort for Mulberry. Although the source code was published under an
open source license in 2007, it did not see any significant development
over the last 10 years and at this point it looks like a dead project.

Rainer


sourceforge.net - gsmartcontrol 1.1.1 now available

2017-09-26 Thread FritzS - gmx
Hi,
please make an update from gsmartcontrol 1.0.2 to gsmartcontrol 1.1.1

gsmartcontrol 1.0.2
https://www.macports.org/ports.php?by=name&substr=gsmartcontrol

gsmartcontrol  1.1.1
https://sourceforge.net/projects/gsmartcontrol/ 
https://sourceforge.net/projects/gsmartcontrol/files/latest/download

Greetings
Fritz


Mulberry v4.1d1 for MacPorts?

2017-09-26 Thread FritzS - gmx
Hi,
why did’t Mulberry v4.1d1 available in MacPorts?
http://trac.mulberrymail.com/mulberry/browser#Mulberry/branches/v4.1d1

Mulberry is an old IMAP Client and now OpenSource.

Greetings
Fritz