Re: [?bug?] PortGroup python 1.0

Christopher Jones wrote: > > b.t.w. its also far from obvious (to me at least) why you have altered > the port file in the way you have ? Whats you aim here… ? It's because pypi i broken for 0.37.2 Also, to bring it in line with the newest version of certbot see the threads "[certbot]

Re: [?bug?] PortGroup python 1.0

Christopher Jones wrote: > Hi, > > Your port file is incorrectly set up. Compare to the original > > https://github.com/macports/macports-ports/blob/master/python/py-acme/Portfile > > you are missing the subport bits. This part is not optional, its part of > how the python PG works.

Re: boost upgrade from 1.70.0_0 to 1.71.0_0 does not trigger ledger rebuilt

Is it a bug in ledger port file that ledger does not detect upgrade of boost? Should I better report it in trac? Or is there a different way of going through boost upgrade? I encountered this yesterday myself, with exactly the same results that you describe. I filed a ticket on this at

Re: Can't compile `lilypond-devel`

It's correct base behavior. Base sees a port compiled against libstdc++ on a system configured to use libc++, and knows this is most often bad, and needs to be fixed. So it flags this as an error. If the portfile author investigates and works out that it's OK for this port to do that (as it

Re: Can't compile `lilypond-devel`

On 02/09/2019 2:33 pm, Mojca Miklavec wrote: On Mon, 2 Sep 2019 at 15:18, Ken Cunningham wrote: It's correct base behavior. Base sees a port compiled against libstdc++ on a system configured to use libc++, and knows this is most often bad, and needs to be fixed. So it flags this as an

Re: Can't compile `lilypond-devel`

On Mon, 2 Sep 2019 at 15:18, Ken Cunningham wrote: > > It's correct base behavior. Base sees a port compiled against libstdc++ on a > system configured to use libc++, and knows this is most often bad, and needs > to be fixed. So it flags this as an error. > > If the portfile author investigates

Re: boost upgrade from 1.70.0_0 to 1.71.0_0 does not trigger ledger rebuilt

On Sun, Sep 01, 2019 at 08:38:11PM -0700, Kastus Shchuka wrote: > I ran “port upgrade outdated” today and it installed a new version of boost: > After that ledger fails to start: > If I uninstall and install again ledger, I am getting the same error. > > I had to build ledger from source:

MacPorts Meeting 11th-16th October 2019

Dear MacPorters, We are happy to announce the 3rd international MacPorts meeting in Bohinj, Slovenia, from 11th to the 16th of October. (Meeting starts on Friday 11th with the dinner and ends on Wednesday after lunch.) Some basic information (to be completed):

[?bug?] PortGroup python 1.0

I've got this : file:///Volumes/Bjarne/WebServer/MacPorts/newPorts rsync://rsync.macports.org/release/tarballs/ports.tar [default] in my sources.conf Now, if I put my py-acme Portfile https://macports.mathiesen.info/portfiles/python/py-acme/Portfile into my own port tree, I get this : #=>

Re: [?bug?] PortGroup python 1.0

Hi, Your port file is incorrectly set up. Compare to the original https://github.com/macports/macports-ports/blob/master/python/py-acme/Portfile you are missing the subport bits. This part is not optional, its

Re: [?bug?] PortGroup python 1.0

b.t.w. its also far from obvious (to me at least) why you have altered the port file in the way you have ? Whats you aim here… ? Chris > On 2 Sep 2019, at 9:40 pm, Christopher Jones wrote: > > Hi, > > Your port file is incorrectly set up. Compare to the original > >