Re: Mailing list for infrastructure request?

Hi, On Sun, Nov 06, 2016 at 01:58:26PM +0100, Mark Evenson wrote: > From [reading the GitHub migration page][1], I understood that in > order to get permissions for the GitHub group, I was to mail > with my request, where I took the ellipsis to be > the domain "macports.org", but that mail has ju

Re: cmake 1.1 PortGroup: one more thing

Hi, On Sun, Nov 06, 2016 at 10:26:25PM +0100, René J.V. Bertin wrote: > There's apparently no such thing resembling a pull request that says > "please consider incorporating this new version of you-know-what > file", right? Would be nice if you don't have to fork the whole beast > of a ports tree

Re: [macports-base] branch master updated: Fix version check for Git autostashing

Hi, On Mon, Nov 07, 2016 at 09:25:40PM +0100, Lawrence Velázquez wrote: > src/macports1.0/macports.tcl | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/src/macports1.0/macports.tcl b/src/macports1.0/macports.tcl > index 14d628f..6aafa73 100644 > --- a/src/macports1

Re: Issues with upgrading with private repositories

Hi, On Wed, Nov 09, 2016 at 10:17:36AM +, Artur Szostak wrote: > During my testing when developing Portfiles I have a few different > private repositories configured under > /opt/local/etc/macports/sources.conf. I have gotten into a situation > where after a "sudo port sync" I am seeing a vers

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

Hi *, On Sat, Nov 12, 2016 at 04:19:44PM +0100, Clemens Lang wrote: > > https://github.com/macports/macports-base/commit/30c27d5d3ad169ffa5f55465cf9663dbd1ff7537 > commit 30c27d5d3ad169ffa5f55465cf9663dbd1ff7537 > Author: Clemens Lang > AuthorDate: Sun Nov 6 18:1

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

Hi, to summarize: - The consensus seems to be that the feature should be in the next release. - We're not sure whether that next release should be 2.3.5 or 2.4, but it should definitely come from the release branch for 2.3.x. - There are risks associated with releasing a 2.4 that does not have

Re: "catch" wrapper (commit 0ecff30a328993179b757a13830a1a5249839dd8)

hould not try to be intelligent about how to handle this. > PS: native_catch would have been a bit less ambiguous than builtin_catch IMHO, > if it's a command that is not off-limits to us poor mere mortals of course. It's off-limits, so the name doesn't matter. -- Clemens Lang

Re: "catch" wrapper (commit 0ecff30a328993179b757a13830a1a5249839dd8)

ed to the number of call levels anyway. It's just about the number of stack frames added by a catch instruction. Btw: Can you adjust your bookmarks to send to the @lists.macports.org address? I cannot reply to @lists.macosforge.org due to SPF. -- Clemens Lang

Re: [macports-ports] branch master updated: x265: update to 2.1

lib: Error opening or reading file (referenced from /opt/local/bin/ffmpeg) You should bump the revision of ffmpeg. -- Clemens Lang

Re: `git describe`

vercmp $macports_version 2.3.4] > 0 to check whether a bugfix you need is available. -- Clemens Lang

Re: `git describe`

orts.org wrote: > In the past, we often just checked for new features by testing whether > the corresponding option or proc exists. That didn't work in this particular case: https://github.com/macports/macports-ports/blob/master/archivers/deco-archive/Portfile#L23 -- Clemens Lang

Re: `git describe`

Hi, On Tue, Nov 29, 2016 at 05:17:18PM +0100, René J.V. Bertin wrote: > With the risk of trolling: how do you determine whether someone is > running an older version? ;) By asking. Somebody who wastes developers time by hiding the fact that they are running and older version on purpose will end u

Re: [RJVB/macstrop] use github ID for maintainer (2fb8aab)

Hi, On Sat, Dec 03, 2016 at 11:35:21AM +0100, René J.V. Bertin wrote: > If I may add a few more cents to this topic (I understand things are > still in flux): This has been implemented in released in 2.3.5 already, so there's no flux and we get to keep what we currently have. I haven't gotten ar

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

On Tue, Dec 06, 2016 at 09:31:47PM +, Brandon Allbery wrote: > On Tue, Dec 6, 2016 at 9:30 PM, René J.V. Bertin wrote: > > > Just out of curiosity, I suppose this is still the full hostname, > > domain included? > > On very old systems, no. On newer ones, as much as will fit --- often > trun

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

ion of VISUAL_EDITOR if that's a traditional variable also used outside > of MacPorts. What does that achieve that setting $EDITOR doesn't? -- Clemens Lang

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 02:28:14PM +0100, René J.V. Bertin wrote: > > A Portfile should not should not print anything in response to it > > simply being opened. (Think about it, does a user really want to see > > this message whenever they run 'port info' > > Yes they are supposed to! Cf. #52981

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 03:38:14PM +0100, René J.V. Bertin wrote: > > Because it runs 'port -q info --line --subports' and parses the > > result. The flags to info guarantee that only the list of subports > > is printed. > > Portindex? I'm pretty sure I've had a ui_msg for a while in one of my > P

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 04:53:13PM +0100, René J.V. Bertin wrote: > > 'port info' output is already parsed by scripts today. It's output is > > already machine-readable when using -q info --line --$fieldname. Your > > change breaks this. > > Just as machine readable as this line. Wrong, since 'p

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 08:14:13PM +0100, René J.V. Bertin wrote: > > > Just as machine readable as this line. > > > > Wrong, since 'port -q info --line --$fieldname' by definition only > > contains information on $fieldname, whereas your message contains > > natural language. > > Clutching at st

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

On Fri, Dec 16, 2016 at 04:00:37AM +1100, Joshua Root wrote: > The installer isn't really conducive to this. We could definitely > advertise it better though, both in the documentation and with a > message inviting users to install the port if they haven't. I'm > thinking the latter should use the

Re: tuning the behaviour of the -u option?

Hi, On Fri, Dec 23, 2016 at 11:11:57AM +0100, René J.V. Bertin wrote: > It's probably overkill to support a universal filter that could > theoretically catch all possible selections of inactive versions to > prune and not to prune. There is however one useful case that might > not be so hard: keep

Report from the Reproducible Builds World Summit 2016

| objStab.string = assureFullPath(atomFile->path()); | objStab.value = atomFile->modificationTime(); This could be considered a bug, and we should report it to Apple so they can fix it. Acknowledgments === My time, travel and accommodation costs have been sponsored by my employer BMW Car IT G

Re: Command line switch to say yes to dependencies?

Hi, On Fri, Dec 30, 2016 at 06:49:24AM -0800, Sterling Smith wrote: > So it seems there is a new feature that asks if I want to install all > of the dependencies of a requested port. Is there a command line > switch to answer yes? If not, is there some other programmatic way to > answer yes? (T

Re: rsync server out of date?

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 > bit of a loss as to how to proceed. Is anyone else having this > problem? Can confi

Re: dblatex @0.3.7 update to 0.3.9

Hi, On Tue, Jan 03, 2017 at 09:48:34AM +0100, Joël Brogniart via macports-dev wrote: > An happy new year for all. > > Could someone take a loot at ticket #53081? Done, will push in a couple of minutes. -- Clemens

Re: question for the "base gurus"

On Tue, Jan 24, 2017 at 04:22:39PM +0100, René J.V. Bertin wrote: > I have mentioned before that I sometimes get permissions errors during > the destroot phase because directories created with xinstall don't > have the intended umask. This happens episodically, and this morning I > had one of those

Re: question for the "base gurus"

Hi, On Wed, Jan 25, 2017 at 12:53:25AM +0100, René J.V. Bertin wrote: > > The only difference in MacPorts behavior I would expect here is the > > check whether output is to a terminal. > > Between the 2 commands above? Indeed, but there must be subtle > differences in the overall context. Strace

Re: 2.4.0 upgrade issue

Hi, On Fri, Jan 27, 2017 at 03:53:05PM -0500, Daniel J. Luke wrote: > On Jan 27, 2017, at 3:50 PM, John Patrick wrote: > > just tried to upgraded and got an error, so retried and got this; > > > > $ sudo port -v selfupdate > > I reported this here earlier today: > > https://lists.macports.org/

Re: 2.4.0 upgrade issue

Hi, On Sat, Jan 28, 2017 at 11:01:06AM +1100, Joshua Root wrote: > I guess we could modify this as part of the upgrade process? Or > transparently map the old setting to the new like we do with > portdbformat? Yeah, I guess we should. The old URLs should really go away and we should eventually di

Re: Removal of llvm-3.5 and llvm-3.6

On Fri, Jan 27, 2017 at 04:14:27PM -0800, Jeremy Huddleston Sequoia wrote: > With the release of 2.4.0, base no longer uses clang 3.5 and 3.6 in > their fallbacks, and these two compilers don't really serve a purpose > any more. 3.5 has i386 codegen issues, and 3.7 works everywhere that > 3.6 does

Re: GitHub usernames in maintainers field

Hi, On Thu, Feb 02, 2017 at 03:12:27PM -0800, Eitan Adler wrote: > > maintainers {jmr @jmroot} openmaintainer > > Why did we choose to do it this way instead of a central list of email > -> github mapping? This method requires some level of replication. Ports can exists outside of a port rep

Re: [GSoC] Call for Mentors GSoC 2017

Hi Jackson, On Tue, Feb 07, 2017 at 09:22:03AM +0530, Jackson Isaac wrote: > I have already started the application process by coordinating with > Rainer. If we have sufficient mentors and a admin and backup admin(s), > we can move ahead with the application process. Thanks for making the effort!

Re: build progress bar

Hi, On Sun, Feb 19, 2017 at 11:10:50AM +0100, René J.V. Bertin wrote: > > The idea was that the buildbot would update the database > > automatically after each build. Not only, because using only the buildbot would not give us any information about variants, which could significantly change the n

Re: build progress bar

On Mon, Feb 20, 2017 at 10:17:05PM +0100, René J.V. Bertin wrote: > I don't think I was the one who wrote that :) Hence the double quotation markers as opposed to single ones where I was quoting you. > Speaking of "quite a few people" who provide line number info: how do > you consider handling i

Re: build progress bar

aven't > managed to access macports::ui_options from there. Which file? Why do you need to call start and finish from different files? That sounds like a problem waiting to happen if you do the progress setting from macports.tcl but the start and finish from somewhere else. -- Clemens Lang

Re: Resolving pull request conflicts

though, you added a merge commit, which might possibly have been preserved by the rebase merge method and would have ended up in the master history. HTH, -- Clemens Lang

Re: build progress bar

Hi, On Wed, Feb 22, 2017 at 03:47:32PM +0100, René J.V. Bertin wrote: > > Yes. Probably still not a good idea to put progress guessing into > > the implementation of ui_info, though. > > proc ui_message is where I've put it because that's the function that > gets called from Pextlib. That functi

Re: build progress bar

On Thu, Mar 09, 2017 at 09:45:44AM +0100, René J.V. Bertin wrote: > I don't disagree, but how would we determine from there that a build > is going to be done (or destroot, I'd add that step too)? Or would we > simply support progress logging for everything invoked through > Pextlib's system call (

Re: GSoC'17: Add migrate action to port command Project

Hey everybody, On Tue, Mar 28, 2017 at 01:37:55PM -0700, Bradley Giesbrecht wrote: > > On Mar 28, 2017, at 11:55 AM, Umesh Singla wrote: > > Does the migrate and snapshot actions help you divide the work? The > snapshot action is basically an inventory of what is installed along > with meta data

Re: manpages is mdoc(7)

Hey, On Thu, Mar 30, 2017 at 07:08:44PM +0200, Jan Stary wrote: > Currently, the port-* manpages are written using the legacy man(7) > language which uses low-level roff constructs to described > presentational details. > > I propose to rewrite them into the _semantic_ markup of mdoc(7) > languag

Re: [macports-ports] branch master updated: mosh: 1.3.0, switch to CommonCrypto

Hi, On Sat, Apr 01, 2017 at 12:48:08PM -0500, Ryan Schmidt wrote: > Mountain Lion works with CommonCrypto, but Lion and earlier now fails > with: > > configure: error: Apple Common Crypto header not found > > The previous version of the port was still building successfully on > Leopard and later

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

n some of the modules (to the point where I sometimes have to disable them for nginx updates because they are incompatible), so we may be stuck with the variants for a while. -- Clemens Lang

Re: python port - use pypi or github

tes most of the boilerplate and is better tested, since most python ports use PyPI. HTH, -- Clemens Lang

Re: GSoC Proposal

Hi, On Thu, Apr 13, 2017 at 12:37:55AM +0200, Mojca Miklavec wrote: > I was talking to someone from the HB community. Apparently they tried > very hard to make Travis CI work. One of the major problems they had > other than the time limit (the builder is relatively slow and jobs get > killed after

Re: building from source with libc++

Hi, On Wed, Apr 19, 2017 at 03:13:37PM +0200, Mojca Miklavec wrote: > I just had some back-and-forth conversation about problems related to > config.guess [1] (link is not too relevant). They sent me this link > which might be more relevant: [2], arguing that one should probably > use: > CC="c

Re: "dev" ports (=/= "devel" ports!)

ports.org/ticket/52713 I really really don't think a PortGroup is the right way to do this. This should be done in base, with proper support of creating multiple packages from a single build and then optionally installing some of them, more like FreeBSD's ports does things. -- Clemens Lang

Re: BuildBot Broken

rac.macports.org/ticket/54086. -- Clemens Lang

Re: Congratulations to all the selected GSOC students and projects

Hi Umesh and Zero, and welcome to MacPorts! You have been accepted into Google Summer of Code 2017 and will work for MacPorts over the summer. Congratulations, we are happy to have you! First of all let me welcome you to our organization. I am looking forward to a good summer with an interesting

Re: Congratulations to all the selected GSOC students and projects

Hi, On Mon, May 08, 2017 at 04:02:55PM +, Zero King wrote: > > Please read our guidelines we put together here: > > http://trac.macports.org/wiki/SummerOfCodeGuidelines > > Subversion -> Git ;) Thanks, fixed. > My work will be done in github.com/macports-staging first and then > deployed t

Re: Congratulations to all the selected GSOC students and projects

Hey, On Tue, May 09, 2017 at 12:47:15PM +1000, Joshua Root wrote: > On 2017-5-9 12:11 , Zero King wrote: > > Does anyone have a list of packages to install on Ubuntu Trusty to > > run MacPorts? This would save some test builds for Travis. > > The "Other Platforms" section of

Re: Registering MacPorts as Not for Profit Organization

Hi, On Fri, May 19, 2017 at 06:01:30PM +0530, Jackson Isaac wrote: > The following two ways were discussed: > 1. Register our own organization in a country where cost is minimal > (for e.g., France as discussed by Mojca in the attached mail). Or in > US or Germany (with strict rules, higher yearly

Re: [GSoC 2017] Community Bonding

Hi, On Tue, May 23, 2017 at 12:52:55AM +0530, Umesh Singla wrote: > I have written two introductory posts on my blog [0] on Blogger. I > thought I shared the link to it in the proposal but no, I didn't. The > one is just when the results got announced and other about my take on > the macports-base

Re: finding dependents of a shared library

Hi, On Wed, May 24, 2017 at 04:23:15PM +0200, René J.V. Bertin wrote: > AFAIK the way rev-upgrade works is > - rev-upgrade scans a list of all supposed-to-be-present binary files Correct. > - for each file on that list it determines the list of dependencies > (or list of deps provided by activ

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Hi, On Wed, May 24, 2017 at 09:50:31PM +0200, Leonardo Brondani Schenkel wrote: > I have been working on an update to the Free42 port, which I just > opened a PR for: > https://github.com/macports/macports-ports/pull/486 > > However I am experiencing something I never encountered before, which >

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Hi, On Thu, May 25, 2017 at 09:29:49AM +0200, Leonardo Brondani Schenkel wrote: > On 2017-05-24 23:47, Clemens Lang wrote: > > I've previously seen builds using xcodebuild in particular hanging > > after they were apparently done. In the cases I've seen so far > > x

Re: [GSoC 2017] Community Bonding

Hi, On Fri, May 26, 2017 at 12:57:11AM +0530, Umesh Singla wrote: > Since we are planning on 3 different actions which can also be used > independently like snapshot and migrate, having 2 scripts in the > macports1.0 directory directly or keeping these 2 commands in a single > script doesn't seem

Re: GitHub getopt repository

Hi Ryan, On Mon, Jun 19, 2017 at 08:35:46PM -0500, Ryan Schmidt wrote: > On Jun 19, 2017, at 20:34, Zero King wrote: > > > On Mon, Jun 19, 2017 at 08:31:16PM -0500, Ryan Schmidt wrote: > >> > >> I understand why I got the email. I don't understand why we have a > >> repository for getopt when we

Re: man.macports.org

Hi, On Tue, Jun 27, 2017 at 01:37:12AM +0200, Rainer Müller wrote: > Hello, > > I created a preliminary version of a linkable web version of our man pages: > > https://man.macports.org/port.1.html Love it! > If anyone would be willing to contribute a better CSS, that would be > highly appre

Re: man.macports.org

Hi, On Wed, Jun 28, 2017 at 10:27:31AM +0200, Rainer Müller wrote: > On 2017-06-28 00:28, Clemens Lang wrote: > > How are those updated? Are we using the master manpages? > > I created a buildbot deploy job for that [1]. However, as we still > lack a builder to run job

Re: Travis: failed build reported as successful

Hi, On Sat, Jul 01, 2017 at 10:37:04AM +, Zero King wrote: > I thought of `grep`ing the output for "Failed to parse file" and > ignore broken Portfiles not touched by the PR like this one > > Failed to parse file python/py-pydot/Portfile: can't read "_name": no such > > variable > in https://

Re: Buildbot now fails to build wine dependencies

Hi, On Tue, Jul 04, 2017 at 04:23:13PM +0200, Rainer Müller wrote: > I still don't understand why we pass *default* variants to > dependencies at all. As I see it, the problem would go away if we > would not request default variants explicitly... > > @Clemens, > as you originally added this to mp

Re: Buildbot now fails to build wine dependencies

Hey, On Tue, Jul 04, 2017 at 10:00:16PM +0200, Clemens Lang wrote: > > I am attaching a patch to only print active variants that are not > > enabled by default (or disabled default variants). To me the result > > looks like what we want to have: > > > > $ tools/d

Re: Buildbot now fails to build wine dependencies

Hey, On Wed, Jul 05, 2017 at 07:18:59AM +1000, Joshua Root wrote: > So really we need two pieces of information: the > canonical_active_variants to use with the fail cache, and the variants > that should be actually be requested. Yes. > How about this? Close, but not fully there, since neither

Re: Buildbot now fails to build wine dependencies

e. Are you going to commit this change? -- Clemens Lang

Re: Petulant buildbots

Hi, On Sun, Jul 16, 2017 at 10:30:13AM -0400, Craig Treleaven wrote: > I’ve updated mkvtoolnix to 13.0.0. On my main system (OS X 10.10, > Xcode 7.2.1) it builds and runs without issue. Building in trace mode > did not work Why did the build in trace mode not work? > checking whether xsltproc w

Announcing paste.macports.org

Hello MacPorts developers! For l2dy's Google Summer of Code project of providing us with a continuous integration system, we noticed a limitation of 4 MiB of logs per build running on Travis CI (which we could easily happen with dependencies and multiple subports) and decided to work around this b

Re: rsync server out of date?

Hi, On Sat, Jul 22, 2017 at 07:48:59AM -0700, Marcus Calhoun-Lopez wrote: > I just ran `port sync`, but the ports are several days behind the > GitHub repository. Is anyone else having this problem? We're aware of the problem and are in contact with GitHub support to resolve the issue. If you wa

Re: Build base archives for CI in a separate repository

ue at hand, you could try to inject a > system "/bin/ls -laeO@ ${target_dir}" > right before the 'file delete' to find out if there is anything like an > immutable flag on this file or directory. This might also happen if our builds are run under a sandbox, which could denies deleting files in this location. -- Clemens Lang

Re: Build base archives for CI in a separate repository

Hi, On Thu, Jul 27, 2017 at 01:51:31AM +, Zero King wrote: > I prefer using a separate repository (only containing .travis.yml and > maybe patches, not MacPorts source) because I can update the binaries > by creating a new release (tag) on the same commit (MacPorts version > can be read from t

Re: [GSoC 2017] Second Evaluation

Hi Jackson, On Mon, Jul 24, 2017 at 09:40:24PM +0530, Jackson Isaac wrote: > Phase 2 evaluations has begun. Deadline for filling the evaluations is > July 28, 2017 16:00 UTC. The procedure remains the same as previous. > Also please summarize the work done until now, challenges faced and > how did

Re: Build base archives for CI in a separate repository

Hi, - On 28 Jul, 2017, at 04:06, Zero King l...@macports.org wrote: > On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote: > > What's your use case for re-tagging on the same commit? I.e. what change > > do you expect from rebuilding without changing something i

Re: Why does macports require a migration across major version bumps?

Hi, On Tue, Aug 29, 2017 at 06:01:36PM -0700, Eitan Adler wrote: > What is the underlying reason to require a reinstall across major > versions? I did something silly/stupid/smart and removed the check > from libexec/macports/lib/macports1.0/macports.tcl and just did 'sudo > port upgrade outdated

Re: Appropriateness for inclusion in MacPorts

Hi, On Tue, Sep 12, 2017 at 12:28:07PM +, Rainer Müller wrote: > As Java applications are mostly self-contained without external > dependencies (no dynamically linked libraries), I guess the approach > to just extract the .zip will work. > > However, I do not know what kind of compatibility w

Re: New project member: kencu

On Mon, Sep 11, 2017 at 01:26:32PM +, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts project member: > > - Ken Cunningham (kencu) Ken, welcome aboard! Glad to have you, looking forward to your continued contributions. -- Clemens

Re: ignore "portfile changed" ?

stroot line from it, otherwise macports will assume destroot was already successfully completed. Hi, -- Clemens Lang

Re: [GSoC] Progress Report

Hi, On Fri, Aug 18, 2017 at 04:16:25AM +, Zero King wrote: > In the next week, I'll automate deployment of base binaries used by > the CI bot and work on graceful shutdown of the PR bot. I'll also > write a blog post in Markdown that describes the work I've done and > upload it to https://gith

Re: New project member: lbschenkel

I'm late to the party, but anyway: On Sun, Oct 22, 2017 at 04:23:33PM +, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts project member: > > - Leonardo Brondani Schenkel (lbschenkel) Welcome aboard! Glad to have you! -- Clemens

Report from Google Summer of Code Mentor Summit

Hi everybody, (The following is a condensed version of a post on my blog with anecdotal content and information not relevant for MacPorts removed. If you have too much time on your hands, you can find the full version at https://neverpanic.de/blog/2017/10/29/attending-the-google-summer-of-code-men

Re: [macports-guide] branch master updated: Convert from docbook 4.5 -> 5.0

Hi, On Sat, Dec 16, 2017 at 05:30:26PM -0800, Eitan Adler wrote: > P.S. Any thoughts on adding travisCI testing to www/ to avoid 'make > validate' errors? I don't mind setting this up, though it would > require an admin to click a button in the web UI. Sure, that would be nice, especially since i

Re: trace mode fails with sh: /usr/bin/tar: No such file or directory

Hi, On Mon, Dec 18, 2017 at 08:05:17AM +1100, Joshua Root wrote: > On 2017-12-18 07:54 , Ken Cunningham wrote: > >> On Dec 17, 2017, at 12:52 PM, Joshua Root wrote: > >> On 2017-12-18 07:18 , Ken Cunningham wrote: > >>> I haven’t been able to use trace mode to test port installs > >>> because of

Re: Bugfixes to backport to MacPorts 2.4.x

se to also cherry-pick: sandbox: Allow file-write-data for /var/db/mds https://github.com/macports/macports-base/commit/1f7658abba0d8383071b059daff726a8c9f6 Close the portfiles after reading https://github.com/macports/macports-base/commit/c2df3cc958635f7ac6d0983288723c6ea097b221 -- Clemens Lang

Re: Python 2.7 – allow another db version beside 4.8

Hi, On Sat, Dec 23, 2017 at 12:39:34PM +0100, Vincent Habchi wrote: > I’ve a made a private change to my python27 Portfile to allow it to > use DB60 instead of the default DB48, which was installed only for its > needs. I think allowing people (through a variant) to build a Python > 2.7 version wh

Re: why does standard configure uses -Os?

Hi, On Mon, Dec 25, 2017 at 08:32:00AM +, Chris Jones wrote: > > Ports are free to override configure.optflags if desired. > > That’s not the same as simply letting the underlying package decide, > via its configure script or similar. That’s the point at which > upstream gets to say what they

Re: poppler, security updates in general...

bsite for that). Maybe that could be used here? -- Clemens Lang

Re: GSOC 2018 org application period has begun

Hi, On Wed, Jan 10, 2018 at 08:36:39AM +0530, Jackson Isaac wrote: > That's great :) I'll help you out. Probably its time for me to become > a Mentor now ;) > > > Let me know what you think and also, if any other criteria MacPorts > > has. I'd be happy to volunteer. Could use someone as backup ad

Re: poppler, security updates in general...

Hi, On Wed, Jan 10, 2018 at 04:39:05PM +0100, Rainer Müller wrote: > > I think you’re referring to Repology: > > > > https://repology.org > > > > No CVE linkages that I can see there. That would be a valuable > > resource though. That's the one, thanks. > I do not think Repology would offer t

Re: Allowing PortGroups to bump port revision

Hi, On Fri, Jan 12, 2018 at 03:30:50PM -0800, Jeremy Huddleston Sequoia wrote: > In https://trac.macports.org/ticket/54744, we've been pondering adding > a PortGroup to allow concurrent installation of multiple providers of > the OpenSSL API (eg: openssl, libressl, libressl-devel) and allow > port

Re: Allowing PortGroups to bump port revision

Hi, On Sun, Jan 14, 2018 at 12:01:34AM +1100, Joshua Root wrote: > portindex isn't slow, mportopen is. You have to evaluate the changed > Portfiles before you can extract their info. I haven't measures this, but I assume the majority of time in mportopen is spent by the sub-interpreter loading th

Re: system -notty what is it for?

Hi, On Thu, Feb 08, 2018 at 11:18:33AM -0800, Ken Cunningham wrote: > I noted here > > https://github.com/macports/macports-base/blob/master/src/pextlib1.0/system.c > > > an option for system called “-notty” > > Se

Re: Any spare mac hardware (for MacPorts meeting) lying around?

Hi, On Mon, Feb 19, 2018 at 11:32:50PM +0100, Mojca Miklavec wrote: > From 10th to 14th March we'll be meeting at the 2nd MacPorts Meeting > in Slovenia. > > https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018 > > During the last meeting we borrowed two older Mac Pros (box format, > pret

Re: Suggestions for hacking sessions & discussions for the MacPorts meeting in March

Hi, On Wed, Feb 21, 2018 at 05:33:53PM +0100, Mojca Miklavec wrote: > I have a few ideas, but I would like to gather more input about what > you consider the most burning issues that might need some discussions > or hacking sessions during the MacPorts meeting. We'll try to fit > those on the sche

Re: Suggestions for hacking sessions & discussions for the MacPorts meeting in March

Hi, On Wed, Feb 21, 2018 at 05:33:53PM +0100, Mojca Miklavec wrote: > I have a few ideas, but I would like to gather more input about what > you consider the most burning issues that might need some discussions > or hacking sessions during the MacPorts meeting. We'll try to fit > those on the sche

Re: GSoC 2018: Interested in Improving startup item code

bly be done together with rule adaptions for trace mode to hide Xcode if a dependency was not declared, so port maintainers had a simple way to test whether their port uses Xcode. -- Clemens Lang

Re: Java port maintainers: What should be installed on the buildbot workers?

On Fri, Feb 23, 2018 at 06:43:27PM -0600, Ryan Schmidt wrote: > I think I should probably install Oracle's latest Java 8 on the Lion > and later buildbot workers. Does that seem reasonable? I don't know if > our java portgroup is compatible with that. The java portgroup uses /usr/libexec/java_home

Re: Upgrading Pandoc

Hi, On Sun, Mar 04, 2018 at 02:18:24PM -0500, Mark Anderson wrote: > So I started trying to move pandoc from some older version to 2.1.1 > but then I realized I needed to upgrade the Haskell compiler and > libraries to do that. I got started, but wow, this is something else. > Does anyone have tip

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

Hi, On Sat, Mar 03, 2018 at 06:50:35AM +, Zero King wrote: > Let's discuss this during the meeting, I also have to check why it > failed to upload logs to the pastebin. From > https://travis-ci.org/macports/macports-ports/jobs/348478666#L316, it > seems to be a permission problem. Do we keep H

Re: Changing default cxx_stdlib to libc++

Hi, On Mon, Mar 12, 2018 at 04:45:39PM -0500, Ryan Schmidt wrote: > You'll see each PR title has a red "X" or a green "√" next to it. > That's the indicator of whether Travis built the PR successfully or > not. You can click them for more information. > > A failed Travis CI build does not necessa

Action Required: Clone Your MacPorts User Repository on GitHub

Hello, If you find yourself in the To list of this email, you still have a user repository in the MacPorts GitHub organization at https://github.com/macports/macports-user- We have created this repository from the users/ subfolder of the MacPorts Subversion repository when we moved to GitHub.

Re: [macports-base] 12/18: fetch: Always use port:git for fetch.type git

sion 1.8.3.4 (Apple Git-47). Unfortunately that version of git has a bug in its 'git archive' that was later fixed. However, this bug causes the output to change, which breaks the entire approach of having checksums for the archives generated by this branch. Remember that checksums for files downloaded from GitHub would suddenly change? If we don't want to end up in the same situation, we'll need this dependency. -- Clemens Lang

Re: GSoC-Announcements distributed over the ports tree

3.html I would read his answer as a "no" and agree with it. -- Clemens Lang

  1   2   3   >