Re: [macports-ports] 01/02: New port for wallet @1.3

> On Nov 2, 2016, at 8:06 PM, Clemens Lang > wrote: > > Clemens Lang (neverpanic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/a2792f4120bbf7fc5b7f771930da83895fd504f1 > > commit

Re: How to keep uncommitted work in a git clone

> On Nov 5, 2016, at 3:07 AM, Mojca Miklavec <mo...@macports.org> wrote: > > On 5 November 2016 at 08:39, Ryan Schmidt wrote: >> On Nov 4, 2016, at 12:39 AM, David Bariod wrote: >> >>> Personnally, I would just commit such change. It is cheap, can be

Re: How to keep uncommitted work in a git clone

On Nov 4, 2016, at 12:39 AM, David Bariod wrote: > Personnally, I would just commit such change. It is cheap, can be reworked > later and be ketp safe in a private remote repository in case of disaster. > With git there are no reason to not commit event not ready yet change set. Coming from a

Re: PR usage by people with commit access

> On Nov 4, 2016, at 1:09 PM, Sterling Smith wrote: > > > On Nov 4, 2016, at 10:50AM, Rainer Müller wrote: > >> On 2016-11-04 18:10, Ivan Larionov wrote: >> >>> * Ability to get a feedback / review from other project members. >>> >>> We use

Re: [macports-ports] branch master updated: octave-image: add cxx11 portgroup, remove gcc-4.2 from compiler blacklist

> On Nov 4, 2016, at 15:18, Marius Schamschula > wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/1119466ab172e47ff602563e691649f1cbcae0cc >

Re: rsync not being kept up to date?

> On Nov 3, 2016, at 11:03 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > >> >> On Nov 3, 2016, at 11:02 PM, Joshua Root <j...@macports.org> wrote: >> >> On 2016-11-4 14:53 , Blair Zajac wrote: >>> >>>> On Nov 3, 2016, at 8:5

Re: Working with Git

On Nov 3, 2016, at 21:41, Lawrence Velázquez <lar...@macports.org> wrote: >> On Nov 3, 2016, at 9:48 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> I did already run "git branch -D l2dy-curl-ca-bundle-update" when "git >> branch -d l2d

Re: Working with Git

> On Nov 3, 2016, at 10:36 AM, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Nov 2, 2016, at 11:24 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> Yes, there are "command line instructions" on the web site, but they >> a

Re: Working with Git

> On Oct 31, 2016, at 12:04 PM, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Oct 31, 2016, at 11:29 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >>> On Oct 5, 2016, at 9:53 PM, Ryan Schmidt <ryandes...@macports.org>

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

> On Nov 1, 2016, at 3:17 PM, Marko Käning wrote: > > Hi Rainer, > > On 01 Nov 2016, at 21:05 , Rainer Müller wrote: >> What do you mean by address rewriting? If you are referring to problems >> with SPF, > > I guess I do. > > >> the new mail

Re: Proposal for a MacPorts'ish commit message template

> On Nov 2, 2016, at 5:43 PM, Clemens Lang <c...@macports.org> wrote: > > On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: >>> vim does that with syntax highlighting automatically nowadays when >>> it notices you are writing a commit message. If y

Re: Github user repos?

> On Nov 1, 2016, at 3:49 PM, David Evans wrote: > > On 11/1/16 1:21 PM, Rainer Müller wrote: >> On 2016-11-01 21:10, David Evans wrote: >>> I see that some github user repos have been created while others (like mine >>> ;-) ) have not. Is this an ongoing process >>>

Re: New build failure emails are difficult to act on

> On Nov 2, 2016, at 12:17 AM, Jeremy Huddleston Sequoia > wrote: > > I've been having a bit of difficulty dealing with the new buildbot emails. I > would really like links to the individual failing jobs. Instead, we're given > links to each job and a list of failed

Re: Proposal for a MacPorts'ish commit message template

MacPorts used CVS commit templates 10 years ago. This was before my involvement with MacPorts, so I don't know how it was decided to do that in the first place or what developer opinions about it were. But you don't have to look at too much of the history of the repositories from 2006 and prior

Re: GitHub usernames as maintainers

On Nov 2, 2016, at 1:49 AM, Mojca Miklavec wrote: > It would be nice if "port info" would also print the github usernames > of maintainers. When we were originally planning the transition to GitHub, I suggested that we allow an "@" syntax in the maintainers line for GitHub usernames (i.e.

Re: Removing "$Id$" lines

Off list, Larry likened removing $Id$ lines to adding modelines, which we also haven't globally done to all Portfiles yet. But it's not really the same thing. Adding modelines needs to be done on a case by case basis. For example, if a Portfile currently uses tabs, then just adding the modeline

Re: Removing "$Id$" lines

On Nov 1, 2016, at 12:38, Bradley Giesbrecht wrote: > > Would it work as well to have the buildbots ignore commits with unchanged > epoch_version_revision. No: imagine that a port fails to build because pkgconfig wasn't there. To fix that, you'll add a build dependency on pkgconfig; you won't

Re: GitHub migration complete

If you had a personal directory in the users directory of the Subversion repository, that has now been converted to a separate git repository in https://github.com/macports with a name starting with "macports-user-". We suggest that you move your user repository to your own GitHub account where

Re: Removing "$Id$" lines

On Oct 31, 2016, at 17:17, Dan Ports wrote: > > Any reason not to just bulk-remove them all at once? That would probably tie up the buildbot for weeks or months. We could cancel those builds, but even the act of scheduling 20,000 builds per builder is much more than we've

Re: Working with Git

> On Oct 5, 2016, at 9:53 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > How will this work on GitHub? > > The user will submit a pull request. How do I test it locally? What if the > pull request is incomplete? I know I can tell the user what's wrong, and

Re: GitHub migration complete

> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin wrote: > > Clemens Lang wrote: > >> If your question is not yet answered, ask on the mailing lists so it can >> be added. > > I may have overlooked this, but does github have any provisions that would > allow > the

Re: GitHub migration complete

> On Oct 30, 2016, at 10:28 PM, Carlo Tambuatco wrote: > > Is that mailto link macports-us...@lists.macosforge.org in the signature > still valid…? Yes, our previous mailing lists have not moved yet. And even when they do, the old addresses will remain valid.

Re: [154337] users/devans/GNOME-3/stable/dports/www/libhttpseverywhere

> On Oct 28, 2016, at 3:28 AM, dev...@macports.org wrote: > > Revision > 154337 > Author > dev...@macports.org > Date > 2016-10-28 10:28:30 +0200 (Fri, 28 Oct 2016) > Log Message > > GNOME-3/stable: libhttpseverywhere, new port, leverage the power of > HTTPSEverywhere to any

Re: Moving to GitHub: Status Update, Action Required

> On Oct 28, 2016, at 9:02 AM, Craig Treleaven wrote: > >> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >> ... >> Migration Timeline >> == >> The switch to Git will happen on the weekend of October 29th/30th. ... > > Is this

Re: nested port upgrading and variants

> On Oct 27, 2016, at 1:28 PM, René J.V. Bertin wrote: > > On Thursday October 27 2016 11:12:10 David Strubbe wrote: > > Hi David, > > >> used for a dependency. That's all it does. The only way I know of that you >> could make opencv get installed with +qt5 in this

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

> On Oct 25, 2016, at 5:04 PM, Clemens Lang <c...@macports.org> wrote: > > Hi, > > On Tue, Oct 25, 2016 at 08:34:31AM -0500, Ryan Schmidt wrote: >> I don't know the answers to your questions, but I wanted to mention >> that I also have noticed the "

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

> On Oct 25, 2016, at 12:17 PM, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Tuesday October 25 2016 08:34:31 Ryan Schmidt wrote: > >> I don't know the answers to your questions, but I wanted to mention that I >> also have noticed the "Failed to ope

Re: Moving to GitHub: Status Update, Action Required

> On Oct 25, 2016, at 6:54 AM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-10-25 10:36, Ryan Schmidt wrote: >> >> >> On Oct 24, 2016, at 17:57, Clemens Lang <c...@macports.org> wrote: >> >>>> On Tue, Oct 25, 2016 at 12:17:

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

> On Oct 25, 2016, at 7:30 AM, René J.V. Bertin wrote: > > I've been noticing "Failed to open portfile from registry" errors during > certain operations like reinstalling (port -n upgrade --force). I don't know the answers to your questions, but I wanted to mention that I

Re: Moving to GitHub: Status Update, Action Required

On Oct 24, 2016, at 17:57, Clemens Lang wrote: >> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote: >> A description of how exactly one would rebase (potentially squash and >> history-rewrite) a submitted PR onto current master should be on our >> WorkingWithGit

Re: Git tools for managing patchsets

On Oct 24, 2016, at 12:29, Michael wrote: > > >> On 2016-10-24, at 10:25 AM, Clemens Lang wrote: >> >> Hi, >> >>> On Mon, Oct 24, 2016 at 09:37:37AM -0700, Michael wrote: >>> So since MacPorts is moving to git, and from what I saw in the "how to >>>

Re: Moving to GitHub: Status Update, Action Required

> On Oct 24, 2016, at 12:15, Lawrence Velázquez wrote: > > The "macports-ports" repository > (https://github.com/macports/macports-ports.git) already contains > a stale version of the ports tree; you can fork it and play around with > it as you wish. If you clone or fork

Re: [154081] trunk/dports/textproc/extractopinion/Portfile

> On Oct 24, 2016, at 6:56 AM, Mojca Miklavec <mo...@macports.org> wrote: > > On 20 October 2016 at 10:41, Mojca Miklavec wrote: >> On 20 October 2016 at 04:42, Joshua Root wrote: >>> On 2016-10-20 13:23 , Ryan Schmidt wrote: >>>> >>>>

Re: [154177] trunk/dports/python/py-spatialite

> On Oct 23, 2016, at 10:21 AM, vi...@macports.org wrote: > > Revision > 154177 > Author > vi...@macports.org > Date > 2016-10-23 17:21:28 +0200 (Sun, 23 Oct 2016) > Log Message > > py-spatialite: get rid of obsolete API “amalgamation” > Modified:

Re: Trac & Subversion available again

> On Oct 22, 2016, at 22:48, Jeremy Huddleston Sequoia > wrote: > > >> On Oct 21, 2016, at 18:16, Clemens Lang wrote: >> >> Hello MacPorts users and developers, >> >>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: >>> Due to the

Re: Autotools help

On Oct 22, 2016, at 10:35, Craig Treleaven wrote: > > I’m working on an update to Lirc and the build system has changed to > Autotools--which I know very little about. > > It seems that Lirc will now opportunistically link with Alsa and there is no > configure flag to

Re: Moving to GitHub: Status Update, Action Required

> On Oct 22, 2016, at 7:49 AM, Marko Käning wrote: > > Hi Clemens, > > On 22 Oct 2016, at 14:41 , Clemens Lang wrote: >> Developers will merge them, either using the command line client, or the >> GitHub UI. We haven't decided and documented which

Re: [154110] trunk/base/portmgr/dmg/postflight.in

> On Oct 21, 2016, at 8:01 PM, c...@macports.org wrote: > > Revision > 154110 > Author > c...@macports.org > Date > 2016-10-22 03:01:24 +0200 (Sat, 22 Oct 2016) > Log Message > > Installer postflight: Fix useless test $OUR_STRING used to contain a > timestamp down to second precision, which

Re: Trac down?

> On Oct 20, 2016, at 6:48 AM, Peter Danecek wrote: > > Hi all, > I am current not able to reach the trac server. Is this a real issue, or just > a local problem here? Trac, svn, www-origin and guide-origin are inaccessible outside of the Apple network. I'm trying to

Re: [154073] trunk/base/portmgr/dmg/postflight.in

> On Oct 19, 2016, at 5:20 PM, c...@macports.org wrote: > > Revision > 154073 > Author > c...@macports.org > Date > 2016-10-19 15:20:29 -0700 (Wed, 19 Oct 2016) > Log Message > > Installer postflight: Fix all shellcheck warnings > > This may have been the cause for double entries in

Re: foo-snapshot / foo-diff convenience functions

> On Oct 19, 2016, at 4:50 AM, René J.V. Bertin wrote: > > It's not that uncommon that one includes a PortGroup that adds build settings > (e.g. to depends_lib) in a port where those settings are irrelevant and even > unwanted. No, that situation should not be common,

Re: [154020] trunk/dports/science/Gyoto/Portfile

> On Oct 19, 2016, at 9:36 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > >> On Oct 18, 2016, at 7:04 AM, thib...@macports.org wrote: >> >> Revision >> 154020 >> Author >> thib...@macports.org >> Date >> 2016-10-18 05:04:

Re: [154020] trunk/dports/science/Gyoto/Portfile

> On Oct 18, 2016, at 7:04 AM, thib...@macports.org wrote: > > Revision > 154020 > Author > thib...@macports.org > Date > 2016-10-18 05:04:07 -0700 (Tue, 18 Oct 2016) > Log Message > > Gyoto: fix py??-gyoto post-destroot when gmake is not available > Modified Paths > > •

Re: [154019] trunk/dports/science/LORENE

> On Oct 18, 2016, at 7:01 AM, thib...@macports.org wrote: > > Revision > 154019 > Author > thib...@macports.org > Date > 2016-10-18 05:01:47 -0700 (Tue, 18 Oct 2016) > Log Message > > LORENE: fix archflags in debug builds, remove -lX11 from LIB_PGPLOT, add > usagenotes. > Modified Paths > >

Re: [154081] trunk/dports/textproc/extractopinion/Portfile

> On Oct 19, 2016, at 9:04 PM, mo...@macports.org wrote: > > Revision > 154081 > Author > mo...@macports.org > Date > 2016-10-19 19:04:20 -0700 (Wed, 19 Oct 2016) > Log Message > > extractopinion: switch to perl5.24 (#52081) > Modified Paths > > •

Re: [154080] trunk/dports/devel/cutter/Portfile

> On Oct 19, 2016, at 8:35 PM, mo...@macports.org wrote: > > Revision > 154080 > Author > mo...@macports.org > Date > 2016-10-19 18:35:42 -0700 (Wed, 19 Oct 2016) > Log Message > > cutter: switch to perl5.24 (#52081) > Modified Paths > > • trunk/dports/devel/cutter/Portfile > @@ -24,7

Re: Objection to restoring deprecated Python subports

> On Oct 18, 2016, at 3:04 AM, Andrea D'Amore wrote: > > Should less-maintained ports be removed as it's being suggested > for old python versions? I don't have an opinion about the python ports right now. But in general, no, just because a port is unmaintained, or is

Re: Review request for tickets #52545, #52590, #52615

> On Oct 17, 2016, at 7:55 PM, David Evans <dev...@macports.org> wrote: > > On 10/17/16 2:38 PM, Ryan Schmidt wrote: >> >>> On Oct 17, 2016, at 2:43 PM, David Evans <dev...@macports.org> wrote: >>> >>> Ryan, >>> >>&

Re: Review request for tickets #52545, #52590, #52615

> On Oct 17, 2016, at 2:43 PM, David Evans wrote: > > Ryan, > > I'm trying to commit as many pending svn commits as soon as possible in > anticipation of the migration to git. I'd > appreciate it if you could look at these 3 tickets[1][2][3] and let me know > if you

Re: [153943] trunk/dports/science

> On Oct 16, 2016, at 11:57 PM, David Strubbe wrote: > > Additionally, the dependency port:xorg-libX11 does not seem necessary: I > don't see any evidence in the build log that it is used, and the build > succeeds without it being active. Are you sure? libX11 is

Re: [153943] trunk/dports/science

yes. > Kind regards, Thibaut. > > Le Dimanche 16 Octobre 2016 22:27 CEST, Ryan Schmidt > <ryandes...@macports.org> a écrit: > >> >>> On Oct 16, 2016, at 12:41 PM, thib...@macports.org wrote: >>> >>> Revision >>> 153943 >>> Aut

Re: [153935] trunk/dports/gis/routino

> On Oct 16, 2016, at 10:58 AM, khindenb...@macports.org wrote: > > Revision > 153935 > Author > khindenb...@macports.org > Date > 2016-10-16 08:58:14 -0700 (Sun, 16 Oct 2016) > Log Message > > routino: add +universal - attempt to use correct compiler flags > Modified Paths > > •

Re: [153947] trunk/dports/graphics/oce

> On Oct 16, 2016, at 3:30 PM, m...@macports.org wrote: > > Revision > 153947 > Author > m...@macports.org > Date > 2016-10-16 13:30:15 -0700 (Sun, 16 Oct 2016) > Log Message > > oce: fix Sierra build issue. > Modified Paths > > • trunk/dports/graphics/oce/Portfile > Added Paths > >

Re: [153943] trunk/dports/science

> On Oct 16, 2016, at 12:41 PM, thib...@macports.org wrote: > > Revision > 153943 > Author > thib...@macports.org > Date > 2016-10-16 10:41:08 -0700 (Sun, 16 Oct 2016) > Log Message > > New port: LORENE > Added Paths > > • trunk/dports/science/LORENE/ > •

Re: [153886] trunk/dports/gis

> On Oct 14, 2016, at 7:44 PM, khindenb...@macports.org wrote: > > Revision > 153886 > Author > khindenb...@macports.org > Date > 2016-10-14 17:44:22 -0700 (Fri, 14 Oct 2016) > Log Message > > routino: new port #49459 > Added Paths > > • trunk/dports/gis/routino/ > •

Re: trac down?

On Oct 14, 2016, at 09:12, Lawrence Velázquez wrote: >> On Oct 14, 2016, at 8:55 AM, René J.V. Bertin wrote: >> >> I cannot connect to trac but the main site works fine. Is there a problem >> with the server? > > I have not been able to reach it

Re: [153826] trunk/dports/net

> On Oct 12, 2016, at 4:23 PM, m...@macports.org wrote: > > Revision > 153826 > Author > m...@macports.org > Date > 2016-10-12 14:23:02 -0700 (Wed, 12 Oct 2016) > Log Message > > ldns ldns-tools drill: Merge into single Portfile. > Modified Paths > > • trunk/dports/net/ldns/Portfile >

Re: Building for 10.5 i386+ppc on 10.6 x86_64

> On Oct 12, 2016, at 9:35 AM, Ken Cunningham > wrote: > > > On 2016-10-12, at 2:36 AM, Mojca Miklavec wrote: > >> Hi, >> >> A while ago we got a bug report about problems building Perl on 10.6 >> x86_64 for 10.5 i386+ppc >> >>

Re: Documentation overhaul

> On Oct 10, 2016, at 2:44 PM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-10-10 01:23, Ryan Schmidt wrote: >> Thanks for your interest, Marcel, but do you feel you would be able >> to lead such an effort, since you seem to be new to MacPorts? I've >>

Re: gcr requires gtk to be installed with +x11

On Oct 10, 2016, at 15:23, Johannes Kastl wrote: > >> On 10.10.16 22:20 David Evans wrote: >> >> Yesterday. r153733 removed the run time dependency on epiphany from gimp2. >> Perhaps you need to update your ports? >> >> sudo port selfupdate > > I did, but maybe I got a stale

Re: Documentation overhaul

> On Oct 9, 2016, at 15:23, Rainer Müller wrote: > > Hello Marcel, > >> On 2016-10-09 15:53, Marcel Bischoff wrote: >> As Ryan has identified that the online documentation needs work, I'm >> hereby volunteering to give it a go. Since there appear to be quite >> specific

Re: llvm / clang and thread_local storage problems

> On Oct 8, 2016, at 10:59 PM, Ken Cunningham > wrote: > > I've run into this again tonight. > > I'm using, at this moment, clang-3.7 / llvm-3.7 with macports-created libc++ > and libc++abi. > > > Every once in a while, a port I'm trying to create or build

Re: Issues with oudated ports / GitHub

Please, everyone, stop. We are keeping our Trac issue tracker; this has been decided. We will not use GitHub issues at this time because it does not have the features we need. We will move our code to GitHub because it has been requested by many users over the years and will help attract new

Re: [153697] trunk/dports/sysutils/bacula

> On Oct 8, 2016, at 8:43 AM, Aljaž Srebrnič <g...@macports.org> wrote: > >> On 08 ott 2016, at 11:40, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> /opt/local should not be hardcoded. > > Of course. Should I revbump it just to be sure? It

Re: Issues with oudated ports / GitHub

On Oct 8, 2016, at 7:57 AM, Davide Liessi <davide.lie...@gmail.com> wrote: > > Il sabato 8 ottobre 2016, Ryan Schmidt <ryandes...@macports.org> ha scritto: >> in future, they will instead open a GitHub pull request and paste a link to >> the pull request in

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 7:07 PM, Bradley Giesbrecht wrote: > >> On Oct 7, 2016, at 4:02 PM, Rainer Müller wrote: >> >> On 2016-10-07 20:58, Christopher Jones wrote: >>> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 3:25 PM, Marcel Bischoff wrote: > > On 16/10/07, Brandon Allbery wrote: >> On Fri, Oct 7, 2016 at 2:38 PM, Daniel J. Luke wrote: >> >>> the cool kids also aren't writing 'tcl' these days ... >> >> >> ...but the way they write

Re: [153697] trunk/dports/sysutils/bacula

> On Oct 8, 2016, at 3:34 AM, g...@macports.org wrote: > > Revision > 153697 > Author > g...@macports.org > Date > 2016-10-08 01:34:05 -0700 (Sat, 08 Oct 2016) > Log Message > > Fix QT4 detection, remove maintainer > > Remove maintainer as per his request > ( >

Re: [153663] trunk/dports/kde/kmymoney4-devel/Portfile

> On Oct 6, 2016, at 8:52 PM, m...@macports.org wrote: > > Revision > 153663 > Author > m...@macports.org > Date > 2016-10-06 18:52:09 -0700 (Thu, 06 Oct 2016) > Log Message > > kmymoney4-devel: increase version suffix, as that seems to be needed for the > port to pick up the previously added

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 1:40 PM, Lawrence Velázquez wrote: > >> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >> >> Currently, once they find out about svn, and trac > > We will still use Trac for issue tracking, although I believe someone is >

Re: Working with Git

> On Oct 7, 2016, at 12:34 PM, Brandon Allbery wrote: > > On Fri, Oct 7, 2016 at 1:31 PM, Marcel Bischoff > wrote: > 'push --force' should *never* be used when working in a team except for > dire emergencies like having cleaned the history of

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 12:07 PM, Marcel Bischoff <mar...@herrbischoff.com> wrote: > > On 16/10/07, Ryan Schmidt wrote: >>> While the latter examples are just minor differences, especially >>> things >>> like ghc, fontforge an pandoc are either completel

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 12:05 PM, Rainer Müller wrote: > > We are currently using the type field with "defect", "enhancement", > "update", "submission", "request". A ticket should be filed with the > appropriate type. > > To indicate a patch is attached to the ticket, we add

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 10:59 AM, Marcel Bischoff wrote: > >>> It pains me to say that Homebrew is running circles around MacPorts in >>> the department of current available packages. >> >> [citation needed] ;-) > > Gladly. I have written a small script to check that.

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 10:23 AM, Marcel Bischoff wrote: > >>> Just today I commented on a ticket that is six weeks old, about an >>> update to nodejs4. Version 4.5.0 was released on 16-Aug-2016, version >>> 4.6.0 on 27-Sep-2016. Version 4 is considered the stable LTS

Re: review requested - widelands 1.9 update

> On Oct 7, 2016, at 10:08 AM, Ken Cunningham Webuse > wrote: > > I think this one looks ready for prime time. > > https://trac.macports.org/ticket/52188 I had been working on that, and have further changes locally not mentioned in the ticket.

Re: reinplace permission denied mariadb-server

> On Oct 7, 2016, at 9:48 AM, Bradley Giesbrecht wrote: > > Hi, > > > mariadb-server is a support of mariadb. > > > In post-extract I copy a file from filespath and in post-patch I patch the > file with reinplace: > port cat mariadb-server: > ... >post-extract { >

Re: Working with Git

> On Oct 7, 2016, at 9:04 AM, Chris Jones wrote: > > Hi, > >>> There will always be problems with the transition to GitHub that can be >>> discussed on the mailing list to find a common solution. Then it can be >>> documented to point people to that if they have the

Re: Issues with oudated ports / GitHub

It looks like others have already responded to most of your points, but I would just add: On Oct 6, 2016, at 12:12 PM, Marcel Bischoff wrote: > But if I still > cannot install (for example) pandoc because ghc still requires llwm-3.5 > which does not compile on Sierra: what choice do I have? I

Re: Working with Git

> On Oct 6, 2016, at 12:36 PM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-10-06 10:22, Ryan Schmidt wrote: >> On Oct 6, 2016, at 02:33, Sterling Smith <smit...@fusion.gat.com> >> wrote: >>> When is the macports repo on GitHub supposed t

Re: [153647] trunk/dports/devel/dbusmenu-qt/Portfile

> On Oct 6, 2016, at 1:11 PM, m...@macports.org wrote: > > Revision > 153647 > Author > m...@macports.org > Date > 2016-10-06 11:11:52 -0700 (Thu, 06 Oct 2016) > Log Message > > dbusmenu-qt5: upgrade to more recent version and add comments > Modified Paths > > •

Re: [153656] trunk/dports/devel/nodejs4

> On Oct 6, 2016, at 4:52 PM, ciserl...@macports.org wrote: > > Revision > 153656 > Author > ciserl...@macports.org > Date > 2016-10-06 14:52:24 -0700 (Thu, 06 Oct 2016) > Log Message > > nodejs4: update to version 4.5.0; add patch to fix compilation on darwin > version 13 or higher > Modified

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:55 AM, Mojca Miklavec <mo...@macports.org> wrote: > > On 6 October 2016 at 14:43, Ryan Schmidt wrote: >>> On Oct 6, 2016, at 7:35 AM, Mojca Miklavec wrote: >>> >>> It works without https://trac.macports.org/wiki/LibcxxOnOlderSy

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:35 AM, Mojca Miklavec wrote: > > It works without https://trac.macports.org/wiki/LibcxxOnOlderSystems > (= setting libc++ to become your default stdlib globally). But the > port in question most likely still needs libc++. > > Read as: if you use the

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:40 AM, René J.V. Bertin wrote: > >> We want to move the matter of determining that an error condition exists >> from the portfiles and portgroups to MacPorts base. Then it will be easier >> for the buildbot to query MacPorts base and ask if the port

Re: Working with Git

> On Oct 6, 2016, at 7:15 AM, Davide Liessi <davide.lie...@gmail.com> wrote: > > 2016-10-06 13:15 GMT+02:00 Ryan Schmidt <ryandes...@macports.org>: >> I assumed that in such a case, where the contributor is (or we are) making >> several commits to fix mista

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:06 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Thursday October 06 2016 06:25:06 Ryan Schmidt wrote: > >> By including the portgroup, you are declaring that the port requires C++11. >> Users using "vanilla" OS X v

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 6:26 AM, Mojca Miklavec <mo...@macports.org> wrote: > > On 6 October 2016 at 12:06, René J.V. Bertin <rjvber...@gmail.com> wrote: >> On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: >> >>> If a port requires C++11 / libc++,

Re: [153554] trunk/dports/math/octave-database/Portfile

> On Oct 4, 2016, at 7:48 AM, m...@macports.org wrote: > > Revision > 153554 > Author > m...@macports.org > Date > 2016-10-04 05:48:43 -0700 (Tue, 04 Oct 2016) > Log Message > > octave-database: provide mysql variants, fix depends_lib. > Modified Paths > > •

Re: [153575] trunk/dports/devel/gpgme/Portfile

> On Oct 4, 2016, at 3:40 PM, dev...@macports.org wrote: > > Revision > 153575 > Author > dev...@macports.org > Date > 2016-10-04 13:40:24 -0700 (Tue, 04 Oct 2016) > Log Message > > gpgme: deactivate kdepimlibs4 earlier than 4.14.3_4 in pre_activate to avoid > a conflict (#52496). > Modified

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Oct 6, 2016, at 05:06, René J.V. Bertin <rjvber...@gmail.com> wrote: > >> On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: >> >> If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. > > I wonder if that shouldn't simply be done by

Re: Working with Git

On Oct 6, 2016, at 06:09, Chris Jones wrote: > > > >> On 06/10/16 11:43, Mojca Miklavec wrote: >> On 6 October 2016 at 09:39, Chris Jones wrote: How do I take the user's pull request, make additional changes, and commit them to our master? >>> >>> Anyone

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 3:56 AM, René J.V. Bertin wrote: > > Hi, > > I got the attached build failure notifications, which in both cases I think > can be traced to the use of `-stdlib=libstdc++` : > > {{{ > [ 84%] Building CXX object

Re: Working with Git

> On Oct 6, 2016, at 4:02 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > > > On 06/10/16 10:00, Ryan Schmidt wrote: >> >>> On Oct 6, 2016, at 3:59 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: >>> >>> Hi, >>

Re: Working with Git

> On Oct 6, 2016, at 3:59 AM, Chris Jones wrote: > > Hi, > > The instructions at > > https://trac.macports.org/wiki/WorkingWithGit > > seem a little out of date w.r.t. forking. It says > > "To do that, go to ​https://github.com/macports/ports/ and click the fork >

Re: Working with Git

> On Oct 6, 2016, at 03:32, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > > >> On 06/10/16 09:22, Ryan Schmidt wrote: >>> On Oct 6, 2016, at 02:33, Sterling Smith <smit...@fusion.gat.com> wrote: >>> >>> Ryan, >>> >

Re: Working with Git

On Oct 6, 2016, at 02:33, Sterling Smith <smit...@fusion.gat.com> wrote: > > Ryan, > >> On Oct 5, 2016, at 7:53PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> Suppose a user submits an update to a port. >> >> With Subversion, the

Working with Git

Suppose a user submits an update to a port. With Subversion, the user would submit a patch in a Trac ticket. To test it, I would download the patch and apply it to my local Subversion working copy. If I like it, I commit it. If I don't like it, I give feedback to the user in the ticket, or I

Re: [153574] trunk/dports/sysutils/skey

> On Oct 4, 2016, at 3:58 PM, Rainer Müller wrote: > > On 2016-10-04 22:03, lar...@macports.org wrote: >> Revision: 153574 >> https://trac.macports.org/changeset/153574 >> Author: lar...@macports.org >> Date: 2016-10-04 13:03:08 -0700 (Tue, 04 Oct 2016) >>

Re: [153488] trunk/dports/python/py-dnspython/Portfile

> On Oct 4, 2016, at 8:37 AM, Adam Mercer <r...@macports.org> wrote: > > On Tue, Oct 4, 2016 at 3:08 AM, Ryan Schmidt <ryandes...@macports.org> wrote: > >> Since this changes the complement of files installed by the port, its >> revision must be increased.

  1   2   3   4   5   6   7   8   9   10   >