Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

Mojca, I think you're going to need to add some files (in the files directory) for these ports: py-django-htmlmin py-hieroglyph py-ioflo py-local-pipelines py-memprof py-obspy-devel py-pss

gcc6, libgcc, and the ABI issue reprised

There is expressed concern about the improvements to portconfigure.tcl to put forth gcc6 for PPC instead of clang-3.4 (which always fails) when the default compilers were blacklisted. I don't see there being such a concern. I'd hope to put some of this to rest with a few examples. 1. the

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On Apr 11, 2018, at 21:36, Joshua Root wrote: > On 2018-4-12 12:23 , Ryan Schmidt wrote: >> >> On Apr 11, 2018, at 21:22, Joshua Root wrote: >> >>> On 2018-4-12 11:49 , Ryan Schmidt wrote: These performance problems predate the existence of our getNextBuildOnPortBuilder

Re: New guide section on Git and GitHub

Have we thought about moving entirely to github. Using issues and projects? I remember there being a reason we didn't, but I don't remember what it was. —Mark ___ Mark E. Anderson On Wed, Apr 11, 2018 at 10:17 PM, Andrew Moore wrote: > > >

Re: [macports-base] branch master updated: Use old ABI if building ports with MP g++ on 10.4 & 10.5

On Apr 10, 2018, at 17:39, Joshua Root wrote: > Joshua Root (jmroot) pushed a commit to branch master > in repository macports-base. > > > https://github.com/macports/macports-base/commit/fb72047770987adea88599a7a69bd70e6c61d214 > > The following commit(s) were added to refs/heads/master by

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On Apr 11, 2018, at 21:22, Joshua Root wrote: > On 2018-4-12 11:49 , Ryan Schmidt wrote: >> >> These performance problems predate the existence of our >> getNextBuildOnPortBuilder function. >> >> It smells to me like a missing database index problem. I don't know how to >> determine that

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On 2018-4-12 11:49 , Ryan Schmidt wrote: > > These performance problems predate the existence of our > getNextBuildOnPortBuilder function. > > It smells to me like a missing database index problem. I don't know how to > determine that though. I'm guessing we probably run into trouble when the

Re: New guide section on Git and GitHub

> On Apr 11, 2018, at 7:52 PM, Dave Horsfall wrote: > > On Wed, 11 Apr 2018, Andrew Moore wrote: > >> Okay, so when all is said and done, am I actually prepared to make an actual >> contribution? Perhaps it merits a topic of discussion for the online >> meeting how

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On 2018-4-12 11:49 , Ryan Schmidt wrote: > > On Apr 11, 2018, at 20:47, Joshua Root wrote: > >> On 2018-4-12 10:47 , Ryan Schmidt wrote: >>> The developer of buildbot thinks we may be able to improve buildbot's >>> performance when there are so many pending builds, by switching to a >>>

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On Apr 11, 2018, at 20:47, Joshua Root wrote: > On 2018-4-12 10:47 , Ryan Schmidt wrote: >> The developer of buildbot thinks we may be able to improve buildbot's >> performance when there are so many pending builds, by switching to a >> postgresql database [2]. I intend to do that, when I have

Re: [macports-ports] branch master updated: py-*: add missing subports for python 3.5 and 3.6

On Apr 10, 2018, at 15:39, Mojca Miklavec wrote: > Mojca Miklavec (mojca) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/6c05e9852d0b08b2a8f14e7ee622031196a9d699 > > The following commit(s) were added to

Re: port version reports 2.4.2 when built from tag v2.4.3

On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote: > Well, I replicated it: > > * Clean the repo (e.g.: git clean -xfd) > * git checkout v2.4.2 > * build and install 2.4.2: > > $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin > $ MP_PREFIX=/opt/macports-2.4.2 > $

Re: New guide section on Git and GitHub

On Wed, 11 Apr 2018, Andrew Moore wrote: Okay, so when all is said and done, am I actually prepared to make an actual contribution?  Perhaps it merits a topic of discussion for the online meeting how MacPorts wants to present itself.  I’d like to see one of MacPorts’s goals be towards

Re: New guide section on Git and GitHub

As someone who only reads the manual as last resort, I think Section 7 of the MacPorts Guide could be retitled from “MacPorts Project” to “Contributing to MacPorts”. And then steps for creating pull requests via GitHub spelled out tutorial-wise. Perhaps steal an existing tutorial

Re: New guide section on Git and GitHub

On Wed, 11 Apr 2018 18:19:50 -0400 Andrew Moore wrote: > My impression from the mailing list is that going forward Trac > would be used exclusively for bug reports. Any code submissions > would ideally be submitted as pull requests to GitHub. That's both true and not quite

Re: New guide section on Git and GitHub

On Wed, 11 Apr 2018 17:54:23 -0400 Andrew Moore wrote: > > On Apr 11, 2018, at 5:31 PM, Perry E. Metzger > > wrote: > > > > I just committed a new section of the guide called "Using Git > > and GitHub". Please read, comment, and improve. > > Um, submit

Re: New guide section on Git and GitHub

My impression from the mailing list is that going forward Trac would be used exclusively for bug reports. Any code submissions would ideally be submitted as pull requests to GitHub. If so, this change needs to put front and center, in large display type. Section 7 “MacPorts Projects” should

Re: New guide section on Git and GitHub

Um, submit pull requests, no? > On Apr 11, 2018, at 5:31 PM, Perry E. Metzger wrote: > > I just committed a new section of the guide called "Using Git > and GitHub". Please read, comment, and improve. > > Perry > -- > Perry E. Metzger pmetz...@macports.org

New guide section on Git and GitHub

I just committed a new section of the guide called "Using Git and GitHub". Please read, comment, and improve. Perry -- Perry E. Metzgerpmetz...@macports.org

Re: Dealing with False Positive during Livecheck

On 2018-04-11 21:18, Jackson Isaac wrote: > One possible way as suggested on IRC is to add a comment in the Portfile > as to why it cannot and/or won't be updated further (in case of > inactive upstream) > and removing the livecheck regex. Be careful that removing the options does not mean

Re: Dealing with False Positive during Livecheck

On Wed, Apr 11, 2018 at 9:23 PM, Perry E. Metzger wrote: > On Wed, 11 Apr 2018 11:25:16 +0530 Jackson Isaac > wrote: >> Hi, >> >> Recently I took upon a journey to try to update ports >> which are tagged as 'nomaintainer' and noticed that >> some of the

Re: Gsoc

Dear Abhishek, On 11 April 2018 at 19:06, Abhishek Kashyap wrote: > On Tue, 10 Apr 2018 at 3:56 PM, Abhishek Kashyap wrote: >> >> Is there any notification about my proposals.Whats going on. >> I am enclosing my proposals with this mail. > > What happened there is no reply from anyone.Please

How to submit changes with a GitHub Pull Request (was Re: CI system for PR builds)

On Wed, 11 Apr 2018 16:50:02 +0200 db wrote: > On 11 Apr 2018, at 15:44, Mojca Miklavec wrote: > > Are you willing to open pull requests for your submissions? > > Sure. I just need to learn how and if I'm allowed to. Anyone can submit a GitHub pull

Re: CI system for PR builds

On Wed, 11 Apr 2018 15:01:24 +0200 Rainer Müller wrote: > On 2018-04-11 14:11, db wrote: > > It means that ports I submitted like stem and ipfs are not > > further reviewed, so new portfiles I write I just keep in my > > local repo and don't bother submitting. > > There

Re: Gsoc

On Tue, 10 Apr 2018 at 3:56 PM, Abhishek Kashyap < abhishek.kasya...@gmail.com> wrote: > Is there any notification about my proposals.Whats going on. > I am enclosing my proposals with this mail. > What happened there is no reply from anyone.Please reply I am very curious to know about my

Re: CI system for PR builds

On Sun, 8 Apr 2018 12:20:34 +0200 db wrote: > On 7 Apr 2018, at 19:44, Clemens Lang wrote: > > Remember that Portfiles can execute arbitrary code and root > > access is available from Portfiles. We do not want to run > > arbitrary code in a PR on the same

Builds with "fakeroot" (was Re: CI system for PR builds)

On Sat, 7 Apr 2018 19:44:40 +0200 Clemens Lang > Remember that Portfiles can execute arbitrary code and root access > is available from Portfiles. We do not want to run arbitrary code > in a PR on the same build machines we use to build packages that we > will distribute to our

Re: Dealing with False Positive during Livecheck

On Wed, 11 Apr 2018 11:25:16 +0530 Jackson Isaac wrote: > Hi, > > Recently I took upon a journey to try to update ports > which are tagged as 'nomaintainer' and noticed that > some of the ports give out false positives during livecheck. > > This is due to the reason that

Re: CI system for PR builds

> On Apr 11, 2018, at 10:37 AM, Mojca Miklavec wrote: > > On 11 April 2018 at 16:18, Joshua Root wrote: >> >> Certainly let's encourage contributors who have something to submit to >> use PRs. But I don't know that simply moving existing tickets over to >> PRs without the

Re: CI system for PR builds

On 2018-04-11 16:43, Joshua Root wrote: > On 2018-4-12 00:37 , Mojca Miklavec wrote: >> We could move them to something like "changesneeded" (not sure where >> exactly; they could get a special status, even if closed, but it >> should be easy enough to find them should anyone have motivation to >>

Re: Docs on submitting new ports and updates (was Re: jmol haspatch maintainer - please commit #56106)

On Mon, 9 Apr 2018 16:29:56 + Zero King wrote: > On Mon, Apr 09, 2018 at 12:10:47PM -0400, Perry E. Metzger wrote: > >> I'm following the (obviously out-of-date) guide at > >> https://trac.macports.org/wiki/howto/Upgrade > >> but I'll try and use the pull requests for

Re: CI system for PR builds

On 11 Apr 2018, at 15:44, Mojca Miklavec wrote: > On 11 April 2018 at 14:11, db wrote: >> On 10 Apr 2018, at 20:07, Mojca Miklavec wrote: >>> That streamlined process is what keeps new and updated portfiles in my local repo… >>> I have no clue what you wanted to

Re: CI system for PR builds

On 2018-4-12 00:37 , Mojca Miklavec wrote: > We could move them to something like "changesneeded" (not sure where > exactly; they could get a special status, even if closed, but it > should be easy enough to find them should anyone have motivation to > fix the remaining issues). Just because none

Re: CI system for PR builds

On 11 April 2018 at 16:18, Joshua Root wrote: > > Certainly let's encourage contributors who have something to submit to > use PRs. But I don't know that simply moving existing tickets over to > PRs without the involvement of the original contributor will be useful. In any case I don't think that

Re: port version reports 2.4.2 when built from tag v2.4.3

On 2018-4-11 23:48 , Enrico Maria Crisostomo wrote: > * At this point > /opt/macports-2.4.3/libexec/macports/lib/macports1.0/macports_autoconf.tcl > correctly contains `variable macports_version "2.4.3"`. > * But port reports 2.4.2: > > % echo path > >

Re: CI system for PR builds

On 2018-4-11 23:55 , Mojca Miklavec wrote: > On 11 April 2018 at 15:47, G A wrote: >> Can these 400 new or pending ports on Trac be rolled over into the repo as >> PRs? > > Yes, that would be ideal, and any help doing that would be greatly > appreciated. > > It would probably make sense to make

Re: CI system for PR builds

I've taken some of them on, including the oldest one (From Ryan, of all people) for a game called enigma from a submission 10 years ago. I advise you to be very careful with them, based on the ones I've seen. Lots of them are not of high quality, build wrongly or against the wrong libraries,

Re: CI system for PR builds

On 11 April 2018 at 15:47, G A wrote: > Can these 400 new or pending ports on Trac be rolled over into the repo as > PRs? Yes, that would be ideal, and any help doing that would be greatly appreciated. It would probably make sense to make a mass-edit on Trac to invite authors to submit PRs, but

Re: port version reports 2.4.2 when built from tag v2.4.3

Not if I'm installing a MacPorts instance from source _side-by-side_ with another one installed in /opt/local (e.g.: from the packages). At least that's my understanding of the documentation. > On 11 Apr 2018, at 15:52, G A wrote: > > Your path should have

Re: port version reports 2.4.2 when built from tag v2.4.3

Your path should have /opt/local/bin first. On Wed, Apr 11, 2018 at 06:48 Enrico Maria Crisostomo < enrico.m.crisost...@gmail.com> wrote: > Well, I replicated it: > > * Clean the repo (e.g.: git clean -xfd) > * git checkout v2.4.2 > * build and install 2.4.2: > > $ export

Re: port version reports 2.4.2 when built from tag v2.4.3

Well, I replicated it: * Clean the repo (e.g.: git clean -xfd) * git checkout v2.4.2 * build and install 2.4.2: $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin $ MP_PREFIX=/opt/macports-2.4.2 $ ./configure --prefix=$MP_PREFIX --with-applications-dir=$MP_PREFIX/Applications

Re: CI system for PR builds

Can these 400 new or pending ports on Trac be rolled over into the repo as PRs? On Wed, Apr 11, 2018 at 06:01 Rainer Müller wrote: > On 2018-04-11 14:11, db wrote: > > I won't address every single point and just say that it might be > interpreted as finger-pointing, but I'm

Re: port version reports 2.4.2 when built from tag v2.4.3

Ok, now I'm sufficiently curious as to dig deeper and replicate what I think the sequence of events were. > On 11 Apr 2018, at 15:32, Joshua Root wrote: > > On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote: >> Thanks Rainer, >> >> I can't check it but as I said in my

Re: port version reports 2.4.2 when built from tag v2.4.3

On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote: > Thanks Rainer, > > I can't check it but as I said in my previous mail I think I had forgotten to > run `make distclean` when I previously built `v2.4.2`. And now I see that > the `macports_autoconf.tcl` file you cite is an Autoconf config

Re: port version reports 2.4.2 when built from tag v2.4.3

Thanks Rainer, I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`. And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file. Why this happen now makes sense. Cheers, -- Enrico >

Re: port version reports 2.4.2 when built from tag v2.4.3

Hi Joshua, Thanks. The port script was the correct one. I think I re-configured and built v2.4.3 over a previous v2.4.2 build but I can't confirm. I cleaned the HEAD and rebuilt and the result is as expected. I noticed in the documentation that "2.2.3 git install" instructs to make

Re: port version reports 2.4.2 when built from tag v2.4.3

On 2018-04-11 10:52, Enrico Maria Crisostomo wrote: > I've just created a new installation of macports-base from tag v2.4.3 > following the instructions in the documentation (basically git checkout > v2.4.3, ./configure ..., make and make install) and I've just noticed that > `port` reports

Re: port version reports 2.4.2 when built from tag v2.4.3

On 2018-4-11 18:52 , Enrico Maria Crisostomo wrote: > Hi, > > I've just created a new installation of macports-base from tag v2.4.3 > following the instructions in the documentation (basically git checkout > v2.4.3, ./configure ..., make and make install) and I've just noticed that > `port`

Re: CI system for PR builds

On 10 Apr 2018, at 20:07, Mojca Miklavec wrote: > On 7 April 2018 at 15:45, db wrote: >> On 7 Apr 2018, at 14:37, Ryan Schmidt wrote: >> Is buildbot running on your basement??? > Yes (not mine). > […] >> Testing and reproducibility, doesn't seem to me as user to be a prime >>

port version reports 2.4.2 when built from tag v2.4.3

Hi, I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2: % which port /opt/macports-2.4.3/bin/port