Re: port -v checksum

On Feb 6, 2017, at 15:11, John Patrick wrote: > should 'port -v checksum' check all checksum's listed? > > just wondering as about to upgrade a port version and it complained > about the rmd160, I updated rmd160 with the new checksum but not the > sha512 > > if their an option to force it to

Re: KDE4 ports not built on Sierra buildbot?

On Feb 6, 2017, at 17:29, Marko Käning wrote: > > Hi Ryan, > >> On 22 Dec 2016, at 17:07 , Ryan Schmidt <ryandes...@macports.org> wrote: >> >> Ok but maybe wait until I've deployed a change to the master.cfg that might >> help performance. >

Re: port -v checksum

On Feb 7, 2017, at 02:07, Joshua Root wrote: > On 2017-2-7 08:11 , John Patrick wrote: >> should 'port -v checksum' check all checksum's listed? >> >> just wondering as about to upgrade a port version and it complained >> about the rmd160, I updated rmd160 with the new checksum but not the >>

Re: [macports-ports] 12/13: xcbuild: add new tool for xcode

> On Jan 23, 2017, at 18:08, Sean Farley wrote: > > Sean Farley (seanfarley) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/ea02c6a2415087a43634f83653532c4aaf346a21 > > commit

Re: [macports-ports] branch master updated: emacs: Rev-bump due to imagemagick changes

> On Jan 23, 2017, at 21:05, Jeremy Huddleston Sequoia > wrote: > > Jeremy Huddleston Sequoia (jeremyhu) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/b45c6c288b90421df0407b17a5885033bfb4efdd >

Re: [macports-ports] branch master updated: arc: update to 5.21p

On Jan 26, 2017, at 09:03, Kurt Hindenburg wrote: > > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/31df8bb6a24ffa67515c5e07d20e185c73b1f855 > > The following

Re: [macports-ports] branch master updated (f548f90 -> f3225e3)

> On Jan 27, 2017, at 14:04, tobypeterson > wrote: > > tobypeterson pushed a change to branch master > in repository macports-ports. > >from f548f90 zsh-completions: update to 0.22.0 > new 917a557 trac-53177 activator submission > new

Re: [macports-ports] 01/02: libevent: update to version 2.1.8

> On Jan 27, 2017, at 13:24, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/f674c03eb39d77ac7d3a38b96f2cd2acbf2fd041 > > commit

Re: [macports-ports] branch master updated: arc: re-add universal variant

> On Jan 26, 2017, at 21:09, Kurt Hindenburg wrote: > > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/d108da56e7944b3d5145cda9d004f79ec92e992d > > The

Re: [macports-ports] branch master updated: emacs: Rev-bump due to imagemagick changes

> On Jan 24, 2017, at 15:20, Jeremy Huddleston Sequoia <jerem...@macports.org> > wrote: > > >> On Jan 24, 2017, at 01:32, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> >>> On Jan 23, 2017, at 21:05, Jeremy Huddleston Seq

Re: PortFile command

> On Jan 26, 2017, at 05:33, René J.V. Bertin wrote: > > Hello, > > In the past I've simplified the development of complex Portfiles by splitting > them over at least 2 Portfiles, loaded with Tcl's `source` command. The > latest example would be the ffmpeg-VLC subport >

Re: [macports-ports] branch master updated: upx: update to 3.92

> On Jan 25, 2017, at 16:46, Zero King wrote: > > tobypeterson pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/8ece104001dabd2c92e633d74963c72c0fe8cb28 > > The following commit(s) were added to

Re: build progress bar

On Feb 18, 2017, at 19:46, René J.V. Bertin <rjvber...@gmail.com> wrote: > >> On Saturday February 18 2017 17:57:04 Ryan Schmidt wrote: >> >> The muniversal portgroup used to say "building for i386", "building for >> x86_64",

Re: build progress bar

On Feb 18, 2017, at 17:55, René J.V. Bertin wrote: > On Saturday February 18 2017 17:27:45 Ryan Schmidt wrote: > >> The problem is that it only applies to cmake-generated makefiles and certain >> other one-off makefiles. But maybe a progress bar for some builds is better

Re: build progress bar

> On Feb 18, 2017, at 12:45, René J.V. Bertin wrote: > > Hi, > > I've been tinkering a bit with a build progress bar feature that uses the > information certain build systems provide. > CMake for instance generates Makefiles that print regular "[xyz%] " tags in > their

Re: [macports-ports] 01/03: qt5*: add openssl variant

> On Feb 17, 2017, at 07:23, Marcus Calhoun-Lopez wrote: > > MarcusCalhoun-Lopez pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/c7a773046fd088bdfff557277384b28099f94406 > > commit

Re: [macports-ports] branch master updated: darktable: update to 2.2.3

> On Feb 23, 2017, at 10:48, Craig Treleaven wrote: > > Craig Treleaven (ctreleaven) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/4606c62b254f469098fe72805b99c13e81ec1839 > > The following

Re: [macports-ports] branch master updated: hackrf: move current to devel & add release.

> On Feb 23, 2017, at 07:25, Michael Dickens wrote: > > Michael Dickens (michaelld) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/b566db2c16035d568261b863c73b0fb795aa7eab > > The following

Resolving pull request conflicts

Browsing pull requests, I found this one: https://github.com/macports/macports-ports/pull/305 Another commit had happened to that port in the mean time, so the PR now had conflicts and could not be applied as-is. GitHub invited me to edit the file on the web to resolve the conflict, so I did.

Re: [macports-ports] branch master updated: aqua/x2goclient: update to 4.1.0.0.

> On Feb 23, 2017, at 02:56, Mihai Moldovan wrote: > > Mihai Moldovan (Ionic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5ef7d72e34586081b904c15830ec70741f758566 > > The following commit(s) were

Re: Resolving pull request conflicts

On Feb 23, 2017, at 04:46, Mojca Miklavec <mo...@macports.org> wrote: > > Dear Ryan, > > On 23 February 2017 at 11:19, Ryan Schmidt wrote: >> Browsing pull requests, I found this one: >> >> https://github.com/macports/macports-ports/pull/305 >> &

Re: GitHub usernames in maintainers field

On Feb 11, 2017, at 13:14, Mojca Miklavec wrote: > On 11 February 2017 at 20:05, Jeremy Huddleston Sequoia wrote: >> Do we have a mapping list somewhere, so we can just script this for known >> mappings? > > The list should be available on our Trac (at least for those who > logged in with

Re: GitHub usernames in maintainers field

I appreciate that we are making these changes slowly. This gives the buildbot time to catch up on other commits. I don't want to commit all maintainer-to-GitHub changes in one revision and then cancel the buildbot build, as we did with the $Id$ removal commit, because valuable builds are being

Re: GitHub usernames in maintainers field

On Feb 11, 2017, at 23:12, Joshua Root wrote: > On 2017-2-12 12:07 , Ryan Schmidt wrote: >> The mega $Id$ removal commit also exposed a limitation of the GitHub >> git-to-svn gateway, which we are using on our server in the mprsyncup >> script. I reported the limitation to

Re: [macports-ports] branch master updated: sqlite3: Fix build failure by using a newer compiler

> On Feb 14, 2017, at 14:48, Jeremy Huddleston Sequoia > wrote: > > Jeremy Huddleston Sequoia (jeremyhu) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/bcc939f4f8b71aef04559128504538e1417b6a6f >

Re: [macports-ports] branch master updated: science/ligo-gracedb: update to 1.23

> On Feb 11, 2017, at 14:52, Adam Mercer wrote: > > Adam Mercer (skymoo) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/e6a419681b3f4a38912ae939784c6bca4fb9c6f7 > > The following commit(s) were added

Re: [macports-ports] branch master updated: fontconfig: support mpkg/mdmg packaging, add postinstall script to initialize/update font cache. Fixes #53350

> On Jan 21, 2017, at 06:46, Marko Käning <mk-macpo...@posteo.net> wrote: > > Hi Ryan, > >> On 20 Jan 2017, at 05:13 , Ryan Schmidt <ryandes...@macports.org> wrote: >> >> Remember that now that we've switched to GitHub, "#53350" refers to

Re: destroot'ing into ${destroot}${prefix}/foo ?

> On Jan 18, 2017, at 04:23, René J.V. Bertin wrote: > > Hi, > > Is there an existing way to create a kind of nested destroot, where the > installed port ends up *unmodified* under say ${prefix}/test? > > Looking at the Portfile guide I think that the only way to

Re: [macports-ports] branch master updated: fontconfig: support mpkg/mdmg packaging, add postinstall script to initialize/update font cache. Fixes #53350

> On Jan 19, 2017, at 12:21, Craig Treleaven wrote: > > Craig Treleaven (ctreleaven) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/39211f92fda4458526220604cef41079bd7b3899 > > The following

Re: [macports-ports] 01/06: pgcli: updates.

> On Jan 19, 2017, at 20:28, Ivan Larionov <xeron.os...@gmail.com> wrote: > >> On Thu, Jan 19, 2017 at 5:58 PM, Ryan Schmidt <ryandes...@macports.org> >> wrote: >> >> > On Jan 19, 2017, at 17:29, Ivan Larionov <xeron.os...@gmail.com> wr

Warning: reinplace ... didn't change anything in ...

MacPorts 2.4.1 shows a new warning when a reinplace command doesn't change anything. The purpose of reinplace is to change something in a file, so when that doesn't happen, it may be a developer error that we want to alert the developer about. Portfile developers should remove these warnings in

Re: [macports-ports] branch master updated: smlr: new port

> On Feb 28, 2017, at 07:56, Kurt Hindenburg wrote: > > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/6262d02ad4539a02372e9959b8a653ba2d03b043 > > The

Re: [146082] trunk/dports/audio

> On Feb 26, 2016, at 08:42, mo...@macports.org wrote: > > Revision > 146082 > Author > mo...@macports.org > Date > 2016-02-26 06:42:27 -0800 (Fri, 26 Feb 2016) > Log Message > > audacity: new port (maintainer, closes #47189) > Added Paths > > • trunk/dports/audio/audacity/ > •

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

> On Nov 9, 2016, at 6:28 PM, Marko Käning <mk-macpo...@posteo.net> wrote: > > Hi Ryan, > > On 05 Nov 2016, at 19:05 , Ryan Schmidt <ryandes...@macports.org> wrote: > >>> I’d like to be able to send emails as well, not just receive them. What >&g

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

> On Nov 9, 2016, at 7:17 PM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-11-10 01:30, Ryan Schmidt wrote: >> I don't think MacPorts wants the burden of running and securing an >> smtp server. That's not our mission. You'll have to find an smtp >>

Re: [macports-ports] 03/03: lbdb: Update to 0.42

> On Nov 10, 2016, at 8:55 AM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-11-10 15:19, Ryan Schmidt wrote: >> Ryan Schmidt (ryandesign) pushed a commit to branch master >> in repository macports-ports. >> >> >> http

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

> On Nov 5, 2016, at 11:43 AM, Marko Käning <mk-macpo...@posteo.net> wrote: > > Hi Ryan, > > On 02 Nov 2016, at 23:49 , Ryan Schmidt <ryandes...@macports.org> wrote: >> I'm confused about why you're confused or what you're talking about. > > :) >

Re: Backport or not: [macports-base] Support multi-valued maintainers

> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Nov 12, 2016, at 12:44 PM, Rainer Müller <rai...@macports.org> wrote: >> >>> On 2016-11-12 17:39, Ryan Schmidt wrote: >>> >>> Perhaps it

Re: [macports-ports] branch master updated: grib_api: delete unused CMake flags

> On Nov 14, 2016, at 6:42 PM, tenomoto > wrote: > > tenomoto pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/8dd1f26e3c8218708a97ac7bd1d4b0aae1984046 > > The following commit(s) were

Re: Another workflow (pull requests) question.

> On Nov 14, 2016, at 11:11 AM, Eric A. Borisch wrote: > > If squash-and-merge is what we're going to want for pull requests, can we > re-enable the button? (Also known as, if we're using GitHub, can we use > GitHub?) Ideally contributions from others (like this pull

Re: `git describe`

> On Nov 28, 2016, at 3:28 PM, René J.V. Bertin wrote: > >> As you discovered yourself now, 'port version' of master identifies >> itself as 2.3.99 at the moment. > > Yes, and if you look at the history of the script in config that sets that > version, it apparently has

Re: [macports-ports] 03/03: shared-mime-info: Declare lack of libraries

> On Nov 19, 2016, at 4:32 PM, René Bertin wrote: > > Lawrence Velázquez (larryv) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/d0a125505343b650472fdf74ca7cab18b7ce94eb > > commit

Re: Triggering a rebuild on the buildbot

On Nov 15, 2016, at 21:27, Adam Mercer wrote: > > Thanks, I've logged in. Now for a hopefully not too stupid question, > but how do I actually trigger a new build? Is there some documentation > somewhere? I'm not sure what we have documented. But I'm sending this reply back

Re: Thanks

On Nov 26, 2016, at 2:15 PM, Marko Käning wrote: > I hope Apple will employ for longer than just the past year to keep > this community effort alive and ticking! My contract position with Apple was for the purpose of maintaining macOS forge and decommissioning it. Now that that has happened

Re: Some Homebrew commands send data to Google Analytics vs. port mpstats

I also read that article yesterday. Because our statistics are opt in, and the user is not invited to enable them during the installation, and they are not described in the guide or anywhere that I'm aware of, the number of users who have found and enabled it are minuscule and probably not

Re: `git describe`

> On Nov 29, 2016, at 2:57 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Monday November 28 2016 17:25:39 Ryan Schmidt wrote: > >> That's correct and intentional. > > I also said that that version complied with practices I see elsewhere :) > >

Re: declaring variants/subports in loops and loop variables

> On Dec 7, 2016, at 11:04 AM, Joshua Root <j...@macports.org> wrote: > > On 2016-12-8 03:07 , Ryan Schmidt wrote: >> >>> On Dec 7, 2016, at 4:20 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: >>> >>> Hi, >>> >>>

Re: Criteria for picking compilers from fallback list ?

> On Dec 7, 2016, at 12:05 PM, Christopher Jones > wrote: > > >> On 7 Dec 2016, at 5:32 pm, Joshua Root wrote: >> >> On 2016-12-8 04:24 , Chris Jones wrote: >>> Hi, >>> >>> I'm working on an update to the root6 port, where the minimum compiler

Re: Commits that implicitly close PRs do not remember doing so

On Dec 12, 2016, at 05:43, Mojca Miklavec wrote: > > This actually reminded me of another potential "problem". In the past > we always used the >(closes #1234567) > syntax which we changed during migration to GIT to absolute links. Do > we want to use absolute links

Re: [MacPorts] #53049: gqrx dependency missing

On Dec 11, 2016, at 8:49 AM, Michael Dickens wrote: > It -is- true that, if you are installing 'port' from scratch, then > doxygen almost always fails to build the first time (I don't recall why; > nor if I've looked into this issue; nor if anybody has tried to fix this > issue). The solution is

Re: `port edit`, local/console vs. remote use

On Dec 6, 2016, at 10:03, René J.V. Bertin wrote: > > Has there ever been discussion about if and how to let `port edit` invoke a > different editor when you're working locally vs. over SSH? > > I realise this could theoretically be handled by setting a different > MP_EDITOR value in your

Re: Build Failure: gstreamer1-gst-plugins-bad, mesa, x265

oia > <jerem...@macports.org> wrote: > > Can you please grab a sysdiagnose before rebooting? That'll be a good first > step. Once I see that, I might have some questions for next time. > > >> On Nov 28, 2016, at 15:31, Ryan Schmidt <ryandes...@macports.org> wro

Re: [macports-ports] branch master updated: py-certbot 0.10.0: new port

> On Jan 13, 2017, at 18:22, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/34767d74a27ef02f00bde27cb79a762f46bd6b00 > > The following

Re: [macports-ports] branch master updated (e58232e -> af96137)

> On Jan 12, 2017, at 18:28, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a change to branch master > in repository macports-ports. > >from e58232e dependents of x265: rebuild with x265 version 2.2 > new d26e175 bro: Update to 2.5 > new

Re: [macports-ports] branch master updated: arp-scan: use GitHub

On Jan 12, 2017, at 19:28, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/666b4d8918ed73de55a42a69598509b4a512439e > > The following

Re: [macports-ports] branch master updated (e58232e -> af96137)

I know. And we want the history of our main repository to be reasonable, so it's necessary to fix PRs before merging. > On Jan 12, 2017, at 20:15, Marius Schamschula <li...@schamschula.com> wrote: > > This was a merge from a GitHub PR. > >> On Jan 12, 2017, at 8:07 P

Re: [macports-ports] branch master updated: gnutls: add compiler blacklist for Snow Leopard build issue

> On Jan 12, 2017, at 18:21, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/46f834998a6e47ff74fdbd65e47b9cb10cc716c6 > > The following

Re: Conflicting binary in dependency

On Jan 12, 2017, at 22:10, Aaron Madlon-Kay wrote: > > Is there a particular reason why it should be a variant, as opposed to just > > always building and installing the tools in the sqlite3 port? > > That's the most convenient solution to be sure. I wasn't sure if, perhaps, > sqlite3 is such

Re: Conflicting binary in dependency

On Jan 12, 2017, at 01:58, Aaron Madlon-Kay wrote: > > Hi all. I was hoping to get some advice: > > I want to make the sqlite3-tools package available via MacPorts (binaries > available at https://sqlite.org/download.html); this package contains three > binaries: sqlite3 CLI shell, sqldiff,

Re: [macports-ports] 07/18: py-graph-tool: add Python 3.6 version

> On Jan 11, 2017, at 08:56, Mark Moll wrote: > > Mark Moll (mamoll) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/ac9a9ab102bc2026808f6a869d6fdbed41434523 > > commit

Re: [macports-contrib] branch master updated: portfile-gen: update python versions

> On Dec 2, 2016, at 4:09 AM, Joshua Root wrote: > > Joshua Root (jmroot) pushed a commit to branch master > in repository macports-contrib. > > > https://github.com/macports/macports-contrib/commit/03f312cb5470db0f189df70cdc2070875279efad > > The following commit(s) were

Re: How should ports refer to the 2-clause BSD license?

On Dec 4, 2016, at 10:49, Lawrence Velázquez wrote: > > The checking script only mentions BSD (3-clause) and BSD-old (4-clause). As far as I was aware, we were referring to all three versions of the BSD licensee as "BSD". Is there a reason to do otherwise?

Re: How should ports refer to the 2-clause BSD license?

> On Dec 4, 2016, at 6:25 PM, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Dec 4, 2016, at 12:11 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >>> On Dec 4, 2016, at 10:49, Lawrence Velázquez <lar...@macports.org> wrote: >>>

Re: [MacPorts] Migration modified

> On Dec 28, 2016, at 17:54, MacPorts wrote: > > Page "Migration" was changed by adfernandes > Diff URL: > Revision 98 > Comment: Add a 'troubleshooting' note for when the restore uses too many open > files. >

Re: rsync server out of date?

On Dec 31, 2016, at 14:08, Ryan Schmidt wrote: > I think we can work around the problem by checking out a fresh working copy > of macports-ports on the server for mprsyncup to use. Done.

Re: [macports-ports] branch master updated: fluidsynth: new variants, maintainers

> On Dec 25, 2016, at 03:09, Mojca Miklavec wrote: > > Mojca Miklavec (mojca) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/004674273d1ef6f7bbb6afdcc9fc4bec0a1083e0 > > The following commit(s) were

Re: [macports-ports] branch master updated: synergy: update to v1.8.5; fixes build on Sierra

> On Dec 6, 2016, at 21:21, Dan Ports wrote: > > Dan Ports (drkp) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/06a980089ff2cecaefbd42b19e44dd67b0b0a54c > > The following commit(s) were added to

Re: rsync server out of date?

On Dec 31, 2016, at 13:31, Ryan Schmidt wrote: > Starting on 12/28, mprsyncup is unable to update the Subversion working copy > of the macports-ports git repository: > > > 2016-12-28T11:28:40-0600 + PORTS_OLD_REV=131029 > 2016-12-28T11:28:40-0600 + /opt/local/bin/svn --

Re: rsync server out of date?

> On Dec 31, 2016, at 06:45, Clemens Lang wrote: > > Hi, > > On Fri, Dec 30, 2016 at 11:13:21PM -0700, Marcus Calhoun-Lopez wrote: >> I just ran `port sync`, but the ports are several days behind the >> GitHub repository. I have never encountered this before and am at a >>

Re: adding a supported compiler

> On Jan 7, 2017, at 05:23, René J.V. Bertin wrote: > > Morning! > > I've created a port for clazy (https://github.com/KDE/clazy) which provides > an additional layer of code analysis on top of what clang already can do. > > This is a compiler wrapper, so it can be used

Re: Tickets affecting multiple ports and committers & "annoying" commits

> On Dec 11, 2016, at 12:13 PM, Mojca Miklavec wrote: > > Hi, > > After some cool features have been enabled on Trac, in particular the > "See:" and "Closes:" syntax that automatically adds a comment, I > wonder what to do with tickets that affect many ports and

Re: [macports-ports] branch master updated: grass: jump to 7.2RC2 (dubbed 7.1.99.2)

> On Dec 21, 2016, at 06:22, Vincent wrote: > > Vincent (Veence) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/6879a39dde564230f06179065fe1afeeed8a8175 > > The following commit(s) were added to

Re: [macports-ports] branch master updated: ocaml-zarith: update to 1.4.1

> On Dec 20, 2016, at 20:00, Kurt Hindenburg wrote: > > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/ae81c668093b56cc220726e69154fa6f73e23f2d > > The

Re: [macports-ports] branch master updated: gdal-grass: bump to 2.1.0

> On Dec 27, 2016, at 10:21, Vincent wrote: > > Vincent (Veence) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/d0a0af40d314aebd3bbfe68ebc8d43a52ce7ff35 > > The following commit(s) were added to

Re: KDE4 ports not built on Sierra buildbot?

On Dec 22, 2016, at 09:51, Marko Käning wrote: > > Hi Mojca, > >> On 22 Dec 2016, at 16:45 , Mojca Miklavec wrote: >> After the new buildbot has been set up we never started any major >> build jobs for all packages. (There are plans to fix this, but

Re: [macports-ports] 05/08: gstreamer1-gst-plugins-bad: add missing dependency gdk-pixbuf2 and rebuild

> On Jan 5, 2017, at 17:37, David B. Evans wrote: > > David B. Evans (dbevans) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/a6105d58f8c4fe4533918886f6abd7efb85a04fa > > commit

Re: [macports-ports] branch master updated (e58232e -> af96137)

> On Jan 12, 2017, at 18:28, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a change to branch master > in repository macports-ports. > >from e58232e dependents of x265: rebuild with x265 version 2.2 > new d26e175 bro: Update to 2.5 > new

Re: [macports-base] tag release_2_3_4 deleted (was d92ac26)

> On Jan 15, 2017, at 07:22, Rainer Müller wrote: > > Rainer Müller (raimue) pushed a change to tag release_2_3_4 > in repository macports-base. > > *** WARNING: tag release_2_3_4 was deleted! *** > > was d92ac26 merge https://trac.macports.org/changeset/140724 from

Re: [macports-ports] branch master updated: certbot: rename py-certbot to certbot

> On Jan 15, 2017, at 10:30, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/cb88f3944b1c4949168ca876d4ca4a55a93f6772 > > The following

Re: [macports-ports] branch master updated: finance/bitcoin: update to bitcoin-core-0.14.0

> On Mar 20, 2017, at 05:54, Mark Evenson > wrote: > > Mark Evenson (easye) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/c9e772d7cb0f771ad2903357565071777e3450ba > > The following

Re: [macports-ports] branch master updated: youtube-dl: update master_sites

> On Mar 27, 2017, at 00:59, Zero King wrote: > > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/028449c4cfaecdf2788a33919d5bfd3a4f786acd > > The following commit(s) were added to

Re: [macports-ports] 01/02: pkcs11-helper: update to 1.22, depend on pkg-config to fix trace-mode build

> On Feb 18, 2017, at 14:49, Dan Villiom Podlaski Christiansen > wrote: > > Dan Villiom Podlaski Christiansen (danchr) pushed a commit to branch master > in repository macports-ports. > > >

Re: citing git commits on Trac?

> On Mar 28, 2017, at 09:23, Rainer Müller wrote: > > On 2017-03-28 15:34, Joshua Root wrote: >> Documentation is available at . >> >> I find the easiest way to link to a commit is [committish/repo], e.g. >>

Re: Reinplace warnings

On Mar 21, 2017, at 07:07, Craig Treleaven wrote: > > 1) What happens if my port uses ‘reinplace -q …’ but the user hasn’t updated > to MacPorts 2.4.1? Does the port fail or is the -q flag ignored? With 2.4.0 it will be ignored. With earlier, an error will occur, so users should upgrade. >

Re: buildbot: +quartz ?

> On Mar 4, 2017, at 08:10, Craig Treleaven wrote: > >> On Mar 3, 2017, at 10:26 PM, Mojca Miklavec wrote: >> >> On 4 March 2017 at 03:51, Craig Treleaven wrote: >>> I know that we would like to find a clean solution to building ports with >>>

Re: [macports-ports] 02/04: cracklib: update to version 2.9.6

> On Mar 14, 2017, at 05:08, David B. Evans wrote: > > David B. Evans (dbevans) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/050703aea8d7f54a901f5824228d7eaa3f8dd3d8 > > commit

Re: expired certificate

> On Apr 1, 2017, at 13:33, John Patrick wrote: > > think you have posted to the wrong mailing list. macosforge.org != > macports.org The old MacPorts email addresses and web page URLs on macosforge.org do forward to macports.org. But I agree, the certificate on the

Re: [macports-ports] branch master updated: sysutils/ansible: update to 2.2.2.0-1, close #53797

On Apr 9, 2017, at 19:41, Andrew Fernandes wrote: > Andrew Fernandes (adfernandes) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/717197f4a88e94d5c667c4797712d1b0daecfaf6 > > The following commit(s) were added to

Re: [macports-ports] branch master updated: asymptote: replace python34 with python36 variant

> On Mar 9, 2017, at 13:17, Mojca Miklavec wrote: > > Mojca Miklavec (mojca) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/defbebe639cfdf1e4ce3504568835f4e00ac5f29 > > The following commit(s) were

Re: [macports-ports] branch master updated: nginx: Add headers_more module support

On Apr 10, 2017, at 05:57, Clemens Lang wrote: > >> In this situation, it would be better to use GitHub's older tarball URLs >> which >> can accept any filename, such as one that includes the name of the module. >> See >> for example my patch to add the fancyindex module here: >> >>

Re: [macports-ports] branch master updated: nginx: Add headers_more module support

> On Apr 8, 2017, at 11:49, Clemens Lang wrote: > > Clemens Lang (neverpanic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5fb6ff652be2ee1655d41ed7891c7ead70c593cd > > The following commit(s) were

Re: [macports-ports] branch master updated: New port: pgbadger

> On Apr 21, 2017, at 12:25, Eric Hall wrote: > > ghosthound pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/71033af1f4162235c6971ee899fd507f81bf9f48 > > The following commit(s) were added to

Git autostash doesn't

I don't understand why I get the error: Please commit your changes or stash them before you merge. when the command I'm running (via "sudo port sync") is "/opt/local/bin/git pull --rebase --autostash". Why won't it automatically stash? Usually it does, but apparently not when there are

Re: Git autostash doesn't

> On Mar 9, 2017, at 14:18, Brandon Allbery <allber...@gmail.com> wrote: > > > On Thu, Mar 9, 2017 at 2:51 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > Why won't it automatically stash? Usually it does, but apparently not when > there are conflicts. >

Re: [macports-ports] branch master updated: minio[-mc]: New ports. s3-compat client and server

> On Mar 3, 2017, at 16:38, Eric A. Borisch wrote: > > Eric A. Borisch (eborisch) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/dd54dbf955eb6502444a66a6ee5fe782fcaa2d8a > > The following

Re: buildbot: +quartz ?

On Mar 3, 2017, at 20:51, Craig Treleaven wrote: > (Second attempt to send; copying lists.macosforge.org address) You don't need to do that. Just write to lists.macports.org. If you forget and write to the old lists.macosforge.org address instead, it will forward to lists.macports.org,

Re: [macports-ports] 03/04: textproc/terminal_markdown_viewer: new port

> On Mar 4, 2017, at 07:09, Aljaž Srebrnič wrote: > > Aljaž Srebrnič (g5pw) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/f807864e8533c48c999bd8fcaa5451aa64dc5a07 > > commit

Re: [macports-ports] 03/04: textproc/terminal_markdown_viewer: new port

> On Mar 4, 2017, at 07:41, Joshua Root <j...@macports.org> wrote: > > On 2017-3-5 00:24 , Ryan Schmidt wrote: >> >>> On Mar 4, 2017, at 07:22, Aljaž Srebrnič <g...@macports.org> wrote: >>> >>> Well, yeah, they should be both distribut

Re: [macports-ports] 03/04: textproc/terminal_markdown_viewer: new port

> On Mar 4, 2017, at 07:22, Aljaž Srebrnič <g...@macports.org> wrote: > >> On 04 mar 2017, at 14:17, Ryan Schmidt <ryandes...@macports.org> wrote: >> >>> >>> On Mar 4, 2017, at 07:09, Aljaž Srebrnič <g...@macports.org> wrote: >>&

Re: Security Ticket Keyword

On Mar 6, 2017, at 08:41, Zero King wrote: > Do we have a way to mark tickets fixing security vulnerabilities? I have no objection to adding a "security" keyword to such Trac tickets. Someone looking through the issue tracker for updates that could be committed might be more likely to pick a

  1   2   3   4   5   6   7   8   9   10   >