Re: perl 5.34 branch

On Sat, 13 Nov 2021 at 17:38, Renee Otten wrote: > > There is an open PR for that: > https://github.com/macports/macports-ports/pull/11534. I am not sure if there > are unresolved issues (it needs to be rebased for sure) or if we’re just > waiting for the backlog of the buildbots after to change

Any Django volunteers to co-mentor for Google Summer of Code?

Hi, I wanted to ask if we happen to have any volunteers to co-mentor a Django project for GSOC for further improvements of https://ports.macports.org/ We have some mentoring force right now, but not enough to apply for GSOC unless we can recruit at least one more devoted person. The potential co-

Using on macOS 10.13 with clang++-mp-13

Hi, I'm trying to build some sources that require on 10.13 using clang 13 (I can try with clang 14, but I doubt that it helps). What's the correct way to compile the following minimal example? Do I need to link against a newer libc++ somehow? If it's not feasible to do that, I'll target a newer

Re: perl5 default version

ave the subports for 5.36 available, we can of course repeat the exercise of switching to 5.36 ;) There's no hurry for the latter, but it would at least be nice to get to the point where we get rid of < 5.34 and introduce support for 5.36. Thanks, Mojca On Mon, 27 Jun 2022 at 21:54, Mo

What to do with Mono (and msbuild) on ARM64?

Hi, One of the projects that I'm working on requires mono as a build dependency. At the moment mono is broken on ARM64 in MacPorts (I suspect that it works under HomeBrew). I fixed it: https://github.com/macports/macports-ports/pull/14952/ but there's a comment in the port saying > please

Re: perl5 default version

#x27;t exactly helping. #3 A number of ports still need some love, any help would be appreciated. Not because it's hard to do, but because there are a number of ports to check. https://github.com/macports/macports-ports/pull/15265 Before we devote them some love, we would need to clarify #2

Re: ports.macports.org gives strange port dependencies

On Sun, 25 Sept 2022 at 23:27, Joshua Root wrote: > > Compiler selection doesn't depend only on the platform, it looks at the > actual versions (and existence) of the compilers available on the > system. It's just another way in which a static PortIndex can't reflect > the dynamic values of Portfil

Re: ports.macports.org gives strange port dependencies

On Mon, 26 Sept 2022 at 20:54, Chris Jones wrote: > > FWIW I personally would also favour more correct over a bit faster any day of > the week… > so if switching back to rsync would allow the stats to reflect say the most > recent OS precisely, > for me thats a price worth paying. To me by far t

Re: Removed ports still listed on ports.macports.org

Hi, V ned., 30. okt. 2022 01:02 je oseba Nils Breunese napisala: > Hi, > > The openjdk port was removed on August 25th after it had been obsoleted a > while ago (https://github.com/macports/macports-ports/pull/15910), but I > just noticed that https://ports.macports.org/port/openjdk/details/ stil

Weird outdated state of ports (in webapp)

Hi, I was looking at https://ports.macports.org/port/kicad/details/ which says that we are shipping kicad 6.0.7 (while we have 6.0.8), builds point to logs for 6.0.7, livecheck reports that 6.0.8 is the latest version (but it is 6.0.9). None of these updates are super fresh, so I'm wondering

Re: Weird outdated state of ports (in webapp)

g the initial browser hard enough it eventually gave up as well. Mojca On Thu, 3 Nov 2022 at 22:49, Mojca Miklavec wrote: > > Hi, > > I was looking at > https://ports.macports.org/port/kicad/details/ > which says that we are shipping kicad 6.0.7 (while we have 6.0.8), > buil

Getting MacPorts logo into font-linux

Hi, While trying to get MacPorts listed as a source for some software, it turned out that I would likely need to display its logo in a consistent way compared to other distributions. Do you think it would be feasible to get our logo (potentially the "MP" one) added to https://github.com/lukas

Re: GitHub migration complete

On 10 November 2016 at 10:43, René J.V. Bertin wrote: > > How complicated would it be to set up the fork such that you can put custom > ports in the default branch, and set up another branch to track the official > ports tree? I have a hunch that it shouldn't be too hard to do in .git/config > o

Re: Another workflow (pull requests) question.

On 16 November 2016 at 11:30, Rainer Müller wrote: > On 2016-11-16 04:09, Ryan Schmidt wrote: >> >>> On Nov 15, 2016, at 6:06 AM, rod wrote: >>> >>> (Apologies if this has been brought up before but I couldn't find a >>> way to search the mailing list archives...) >>> >>> Travis CI has tight integ

Re: port:libressl vs port:openssl, path-style variants and prebuilt binaries

On 21 November 2016 at 14:23, René J.V. Bertin wrote: > Hi, > > I've been thinking about the implications of alternative/drop-in replacement > ports and ABI differences. > > IIUC, libressl and openssl are API-compatible alternatives that do not build > to ABI-compatible libraries. Yet I have noti

Re: Porting software that wants to build/install its own language bindings

On 29 November 2016 at 02:21, Lawrence Velázquez wrote: >> On Nov 28, 2016, at 7:31 PM, A. Karl Kornel wrote: >> >> I am looking for advice on how best to handle a port for a program >> that wants to build its own language bindings. >> >> I am writing a port for a program called "hivex", which is a

Re: `git describe`

On 29 November 2016 at 19:42, René J.V. Bertin wrote: > On Tuesday November 29 2016 19:03:04 Clemens Lang wrote: > >> By asking. Somebody who wastes developers time by hiding the fact that >> they are running and older version on purpose will end up no longer >> getting support at some point. > > W

Re: Your message to macports-changes awaits moderator approval

On 2 December 2016 at 12:02, Zero King wrote: > > I don't want to receive such mail but would prefer not to subscribe to the > macports-changes list either. What should I do? >From the technical point of view you can easily subscribe and mark that you don't want to receive any emails. Then your p

Re: Your message to macports-changes awaits moderator approval

On 2 December 2016 at 12:13, Zero King wrote: > I didn't write to that list, my commit was merged into master and so I've > got this mail. In that case it's a problem with our scripts or mailman configuration and Rainer should be able to answer you. I guess that the idea was to use the committer

Re: Your message to macports-changes awaits moderator approval

On 2 December 2016 at 14:55, Rainer Müller wrote: > On 2016-12-02 12:28, Mojca Miklavec wrote: > >> But there might be some issues. Looking at a random commit email: >> >> https://lists.macports.org/pipermail/macports-changes/2016-December/144725.html >> sayin

Re: PR final steps (to squash or not to squash)

Hi, On 5 December 2016 at 09:46, René J.V. Bertin wrote: > Hi, > > This has come up on the QtCurve PR and I cannot seem to find an explicit > answer in the wiki (https://trac.macports.org/wiki/WorkingWithGit#pr) > > If a pull request has seen some evolution and thus commits due to the review > p

Re: PR final steps (to squash or not to squash)

On 6 December 2016 at 10:34, René J.V. Bertin wrote: > On Monday December 5 2016 22:52:51 Lawrence Velázquez wrote: > >> Fetching from a fork does not download the full history. Only the >> objects that are not in your repository are fetched. > > That implies adding the fork as another remote with

Question about bootstrapping MinGW

Hi, I have finally managed to come up with ports for MinGW-w64. It seems to work as expected except for a tiny problem: gcc has to be compiled in two stages. The first stage installs the bootstrapped version of the compiler and the second stage installs everything (else). I created two subports (

Re: Question about bootstrapping MinGW

Hi, Here's the forgotten link: https://github.com/mojca/macports-user-mojca/tree/master/ports/cross On 7 December 2016 at 22:02, Mojca Miklavec wrote: > > I have finally managed to come up with ports for MinGW-w64. It seems > to work as expected except for a tiny problem:

Re: Question about bootstrapping MinGW

On 8 December 2016 at 17:16, Brandon Allbery wrote: > On Thu, Dec 8, 2016 at 4:10 PM, Mojca Miklavec wrote: >> >> Also, in an ideal world the package manager would check whether >> "*-all" is already installed or available in a binary form and only if >> i

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

On 11 December 2016 at 13:59, Joshua Root wrote: > On 2016-12-11 23:30 , René J.V. Bertin wrote: >> On Sunday December 11 2016 12:45:44 Marko Käning wrote: >> >>> My goodness, what happened here??? >> >> That seems to come from this line >> >> ui_msg "This port only builds with >> configure

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

On 11 December 2016 at 16:53, René J.V. Bertin wrote: > > Let me ask once more: is there anything currently available that makes it > easier/less work to add variants that select a gcc compiler? I've been > looking at the compilers PG, but cannot assess from the preamble comments > whether it's

Tickets affecting multiple ports and committers & "annoying" commits

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 maintainers. Examples include tickets like "replace no_x11 with x11", "switch to perl5.26", ...

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

On 12 December 2016 at 10:35, Joshua Root wrote: > On 2016-12-12 20:21 , Rainer Müller wrote: >> On 2016-12-12 02:29, Lawrence Velázquez wrote: On Dec 6, 2016, at 10:33 AM, Rainer Müller wrote: (e) add "Closes: #XYZ" to the commit message >>> >>> When commits close PRs implicitly (by

Re: Feature Request: Buildbot triggering dependent port rebuilds in a cascade

On 13 December 2016 at 06:02, Marko Käning wrote: > Hi MacPorts core devs, > > I was wondering whether it is possible to configure the buildbots in such a > way > that they can observe if a just rebuilt port is a dependency of other ports > which > haven’t been built successfully yet. If such a c

Re: qtcurve update failure

On 13 December 2016 at 10:05, René J.V. Bertin wrote: > Marko Käning wrote on 20161213::06:29:51 > >>Was easy to fix by uninstalling qtcurve. >>Yet it would have been nicer to recommend the uninstallation of a too old >>qtcurve in qtcurve-extra. > > This is the kind of situation where you'd want t

Re: qtcurve update failure

On 13 December 2016 at 10:54, René J.V. Bertin wrote: > On Tuesday December 13 2016 10:30:24 Mojca Miklavec wrote: > >>See: >>https://trac.macports.org/wiki/PortfileRecipes#deactivatehack > > Ah, yes, I forgot about that link, though I did consider deactivating in t

Re: qtcurve update failure

On 13 December 2016 at 11:45, René J.V. Bertin wrote: > On Tuesday December 13 2016 11:22:09 Mojca Miklavec wrote: > >>So: >>- you have an old qtcurve installed >>- the new qtcurve will have a new runtime dependency qtcurve-extra >>- qtcurve-extra doesn't depen

Re: Update mono, F#: support "select"

Hi, On 13 December 2016 at 16:32, Luc Bourhis wrote: > Hi, > > I am writing an update for the fsharp port (F# language), which is very > outdated. This requires an update to the mono port, from version 3 to 4. One > could make the case to support every x.y version of Mono and F# as MacPorts > d

Re: Update mono, F#: support "select"

On 13 December 2016 at 20:08, Luc Bourhis wrote: > >> (Ruby is completely outdated and only the interpreter works, packaging >> is completely unmaintained. > > MacPorts provide ruby 2.3, which is not outdated, is it? Ruby is fine, the rest is questionable. For example rb-rails @2.3.5_1 rb

Re: Update mono, F#: support "select"

On 14 December 2016 at 11:13, Russell Jones wrote: > For completeness, Python also has pypi2port > https://trac.macports.org/wiki/pypi2port, created as a GSOC project. I don't > know how widely it's used, though we are starting to use it here. I'm using it most of the time when I need a new Python

Re: Requiring a specific variant in depends_lib

On 18 December 2016 at 02:28, Ryan Schmidt wrote: > On Dec 17, 2016, at 09:06, Akim Demaille wrote: >> >> So my question is: how can I specify that requirement in the Portfile? >> Currently it reads: >> >> depends_lib port:boost \ >> path:bin/ccache:ccache \ >>

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

On 20 December 2016 at 07:38, Ryan Schmidt wrote: >> On Dec 11, 2016, at 12:13 PM, Mojca Miklavec wrote: >> >> After some cool features have been enabled on Trac, in particular the >> "See:" and "Closes:" syntax that automatically adds a comment, I &

Re: Unintentional double commits

On 21 December 2016 at 12:38, Rainer Müller wrote: > On 2016-12-21 11:41, Andrea D'Amore wrote: >> While trying to push a small change (shell/xonsh) I managed to rebase >> AND merge the about 300 commits since my previous update, >> as a results those 300 commits in master now are "duplicated". >>

Re: A new category of ports: purgatory

blems integrating with HB's packaging requirements. Broken formulae are migrated here as an alternative to allowing hard work and valuable knowledge to fade into git history. Mojca On 18 October 2016 at 11:32, Mojca Miklavec wrote: > On 18 October 2016 at 10:42, Ryan Schmidt wrote: >> On Oct 1

Re: Unintentional double commits

On 21 December 2016 at 17:33, Rainer Müller wrote: > On 2016-12-21 16:39, Mojca Miklavec wrote: >> On 21 December 2016 at 12:38, Rainer Müller wrote: >>> On 2016-12-21 11:41, Andrea D'Amore wrote: >>>> While trying to push a small change (shell/xonsh) I managed

Re: Unintentional double commits

On 21 December 2016 at 18:44, Ryan Schmidt wrote: > On Dec 21, 2016, at 04:41, Andrea D'Amore wrote: > >> While trying to push a small change (shell/xonsh) I managed to rebase >> AND merge the about 300 commits since my previous update, >> as a results those 300 commits in master now are "duplicate

Re: Unintentional double commits

On 21 December 2016 at 22:38, Ivan Larionov wrote: > One of the ways to avoid it is to review things you're going to merge. And > one of the easiest ways to do it is to open a PR on github where you can > clearly see which commits you're going to merge. That doesn't necessarily help. The author ca

Re: KDE4 ports not built on Sierra buildbot?

Hi, On 22 December 2016 at 16:32, Marko Käning wrote: > Hi Mojca, > > I just realised that the Sierra buildbot obviously never prepared binary > packages for KDE4. > > Has the Sierra buildbot ever run for ports of the kde4 category at all? After the new buildbot has been set up we never started

Re: KDE4 ports not built on Sierra buildbot?

Hi, On 22 December 2016 at 16:51, Marko Käning wrote: > On 22 Dec 2016, at 16:45 , Mojca Miklavec wrote: > >> So basically 10.5, 10.6-i386, (10.7) and 10.12 only contain binaries >> for ports (and their dependencies) that have seen some commits since >> August. Plus those

Template for pull requests

Hi, I have an impression that we are now getting pull requests from upstream developers (or some close-to-upstream users/developers) who never contributed to MacPorts earlier and sometimes don't even have MacPorts installed and never test the changes. Some of them submit both to MacPorts and HomeB

Mirorring distfiles or enabling libcurl/openssl from MP

(was: Build Failure: cctools, libmacho, libmacho-headers) On 21 December 2016 at 12:42, Rainer Müller wrote: > On 2016-12-21 04:20, Jeremy Huddleston Sequoia wrote: >> Can we please configure base on these older builders to use MacPorts' >> libcurl+libressl/newer OpenSSL (or just a special one we

How to properly add -stdlib=... (and other flags)?

Hi, I would like to know the best way to add arch flags and stdlib to ports with exotic build systems (like scons) where this is not handled automatically by the base. I'm currently using: build.args \ CCFLAGS="[get_canonical_archflags cc] -stdlib=${configure.cxx_stdlib}" \ LINKFLAGS="[get_canon

Re: Mirorring distfiles or enabling libcurl/openssl from MP

On 23 December 2016 at 11:54, Rainer Müller wrote: > On 2016-12-23 08:42, Mojca Miklavec wrote: >> (was: Build Failure: cctools, libmacho, libmacho-headers) >> >> On 21 December 2016 at 12:42, Rainer Müller wrote: >>> On 2016-12-21 04:20, Jeremy Huddleston Seq

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

On 25 December 2016 at 10:45, Vincent Habchi wrote: > Ryan, > > sorry I didn’t see this before: > >>>grass: jump to 7.2RC2 (dubbed 7.1.99.2) >> >> Does upstream also refer to 7.2.0RC2 as 7.1.99.2, or is that something you >> made up? If the latter, why? > > No, upstream’s name is RC2. But 7.1.

Re: Central portindex'ing functional at the moment?

Dear Marko, On 28 December 2016 at 22:31, Marko Käning wrote: > Hi, > > just now I ran a selfupdate and didn’t get notified of any outdated ports: > --- > $ sudo port selfupdate && port outdated > Password: > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.3.5 installed,

Re: Central portindex'ing functional at the moment?

On 28 December 2016 at 23:59, Marko Käning wrote: > On 28 Dec 2016, at 23:18 , Marko Käning wrote: > >> This way I shouldn’t get any shadowing… > > Ha, and I wouldn’t see any updates of my local source either. Exactly. But one of the questions arises: why do you need the global index at all? > S

Guidelines about trac tickets and pull requests

Hi, I believe that we need some written guidelines about opening trac tickets and pull request. Many people now open both at the same time. That's not as bad when they are at least referenced properly (and annoying when they are not), but it probably doesn't serve anyone to have both. (I believe

Best way to fetch/extract sources of a dependency

Hi, I was playing with a port for comparing NetCDF https://trac.macports.org/ticket/53118 The software depends on netcdf, but also wants to have access to two headers that are only available in original netcdf sources and not installed anywhere. What's the best way to handle this? I could:

Re: Guidelines about trac tickets and pull requests

On 29 December 2016 at 19:30, John Patrick wrote: > From a users point of view, it's not clear what I should be doing and > how Ticket's link with Pull Requests and vs versa? Neither is this entirely clear to us :) :) But I feel that it doesn't make so much sense to have both opened at the same t

Re: Guidelines about trac tickets and pull requests

On 30 December 2016 at 16:57, Arno Hautala wrote: > On Fri, Dec 30, 2016 at 10:43 AM, Mojca Miklavec wrote: >> (a) Press the button to merge the changes, but the disadvantage is >> that committer's email is then "quasi-random" (it cannot be configured >> on

Re: port:libressl vs port:openssl, path-style variants and prebuilt binaries

On 30 December 2016 at 11:32, René J.V. Bertin wrote: > Hi, > > I'm coming back to this discussion because of something that came up > elsewhere. > > I think we had a consensus a while back that the implementation of the > support for using libressl at user discretion left a bit to desire. I agr

Request for a tiny test on 10.8-10.11

Hi, I would like to ask any owner of Mac with OS X 10.8-10.11 to test whether sudo port -v test libatomic_ops-devel +universal works on his or her machine. I would like to know which OS version is the first one to support certain features. The relevant ticket is here (I admit that I don't q

Re: Request for a tiny test on 10.8-10.11

Thanks a lot for the extensive testing! This means that 10.9 is needed, 10.8 fails in the same way as 10.7. Mojca On 12 January 2017 at 12:28, Joshua Root wrote: > On 2017-1-12 18:25 , Mojca Miklavec wrote: >> >> Hi, >> >> I would like to ask any owner of Mac w

Re: Request for a tiny test on 10.8-10.11

On 12 January 2017 at 21:33, Mojca Miklavec wrote: > Thanks a lot for the extensive testing! This means that 10.9 is > needed, 10.8 fails in the same way as 10.7. Problem hopefully solved. Thanks again. Mojca

Re: Template for pull requests

Hi, I've recently seen some "templates" in our pull requests, for example on https://github.com/macports/macports-ports/pull/158 Were those added manually? What do others think of adding some templates to our repos? Mojca On 22 December 2016 at 20:56, Mojca Miklavec wro

Re: Template for pull requests

On 15 January 2017 at 23:57, Ryan Schmidt wrote: >> On Jan 15, 2017, at 02:44, Mojca Miklavec wrote: >> >> What do others think of adding some templates to our repos? > > I often find them annoying in other projects because they ask the wrong > questions. Can we find

Re: Handling C++11

On 16 January 2017 at 21:03, Ken Cunningham wrote: > Octave builds and runs great on older systems right now when they are > upgraded to libc++ per the current instructions. Except on 10.5, I guess? Mojca

Re: Handling C++11

On 17 January 2017 at 21:08, Ken Cunningham wrote: > Re: 10.5 Intel - for me, that platform is just a vehicle to 10.5 PPC. > I use it for cross compiling for 10.5 PPC. All these intel machines > can be upgraded to at least 10.7 (10.6 if you want Rosetta). I'm sorry, I meant 10.5 PPC of course. Th

Re: Handling C++11

On 18 January 2017 at 04:43, Marcus Calhoun-Lopez wrote: > I think perhaps I am not being clear in what I am proposing. > > Currently, if cxx_stdlib is equal to libstdc++ then the cxx11PortGroup > returns an error and the port does not build. > I am simply proposing that instead of returning an er

Re: py26-numpy at 1.12.0_0+gfortran build fails on 10.11

On 23 January 2017 at 03:21, Joshua Root wrote: > Looks like support for 3.3 was also dropped. > > Why not dropping subports for 2.6 and 3.3 rather than falling back to old versions of numpy? Do we really still need pyth

Re: [macports-ports] 07/07: npm: use an older nodejs on < 10.7

On 30 January 2017 at 11:27, Ryan Schmidt wrote: >> On Jan 26, 2017, at 17:17, Mojca Miklavec wrote: >> >> https://github.com/macports/macports-ports/commit/19b2d7444aee50a1a155c2f571b4123301ba16c4 >> >> --- a/devel/npm4/Portfile >> +++ b/devel/npm4/Portfile

Interactive port command asking me for installation of an existing port

Hi, The interactive "port upgrade outdated" curiously asked me for confirming installation of an existing (active) port: ---> Computing dependencies for gtk3 ---> Fetching archive for gtk3 /.../ ---> Installing gtk3 @3.22.7_0+x11 ---> Cleaning gtk3 ---> Computing dependencies for gtk3 --->

Proper syntax for recursive copying during destroot

Hi, What's the proper syntax to copy from a bunch of files recursively during installation? I like "xinstall" because it's safe to call "port destroot" twice. If I use "move", this is probably not the case. I have something like the following structure (three folders, two of them contain plain fi

Re: Re: [MacPorts] #53438: Audacity can't find ffmpeg

On 31 January 2017 at 09:58, René J.V. Bertin wrote: > Hi, > > Can someone please tell me how to check if audacity has failed to build on > the 10.11 (and 10.12) build bots, and/or trigger a rebuild? Here it is: https://build.macports.org/builders/ports-10.11_x86_64-watcher/builds/4511 https://b

Fixing binary distributability & revbump

Hi, Is it necessary to use a revbump when fixing a port for binary distributability? For example: https://build.macports.org/builders/ports-10.7_x86_64_legacy-watcher/builds/4522 doesn't upload any archives because the binary already existed (that's partially on my request, so if anything, I'm

Re: Feedback on clang change (#53194)

On 31 January 2017 at 19:48, Marcus Calhoun-Lopez wrote: > > There are three ways to allow clang to refer to MacPorts libstdc++. > > 1) Create a *default* variant to have -stdlib=libstdc++ refer to MacPorts > libstdc++. > This was quite rightly rejected because clang should be “as compatible

Re: Feedback on clang change (#53194)

On 1 February 2017 at 16:20, Marcus Calhoun-Lopez wrote: > Yes, we are talking about the libstdc++ that is shipped with gcc6. OK. Something that's not entirely clear to me yet is what's the benefit of having clang compile software against gcc's libstdc++ vs. gcc6 compiling it. And what's the rel

Re: Feedback on clang change (#53194)

On 1 February 2017 at 20:33, Marcus Calhoun-Lopez wrote: > >> And we should finally address binary builds for libc++. That would >> likely solve 99.9% of our C++11-related problems. > > Unfortunately, I do not even know where to begin to solve this problem. It's mostly about deciding what to do wi

Re: Feedback on clang change (#53194)

On 1 February 2017 at 20:33, Marcus Calhoun-Lopez wrote: > >> Something that's not entirely clear to me yet is what's the benefit of >> having clang compile software against gcc's libstdc++ vs. gcc6 >> compiling it. > > I have attempted to build both Qt and Octave with gcc6, and I have run across

rpcgen: should one rename a packaged binary?

Hi, I need to use "rpcgen -M" for one particular package that I'm trying to create. But that flag is apparently missing on the binary that's bundled on macOS, so apparently I need to create a package for rcpgen as well. See: https://trac.macports.org/ticket/47801 https://lists.apple.com/

Re: GitHub usernames in maintainers field

Hi, On 4 February 2017 at 17:07, Clemens Lang wrote: > 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 o

Re: [GSoC] Call for Mentors GSoC 2017

On 7 February 2017 at 16:25, Michael Dickens wrote: > I'm up for being a mentor again, for the correct student. > > Do we have a MP GSoC website up yet? The best I can find is < > https://trac.macports.org/wiki/SummerOfCode >, which is for 2015. I guess the idea is to simply fix the contents of th

Re: KDE4 ports not built on Sierra buildbot?

On 8 February 2017 at 23:51, Marko Käning wrote: > > @Mojca, can we determine somehow easily which KDE4 ports aren’t yet built on > the Sierra buildbot? (a) Implement the functionality collecting statistics from the buildbots, see https://trac.macports.org/ticket/51995#Statistics (b) Just su

Re: A separate PortIndex for libc++ on older systems

Hi, I'm sorry for top-posting, but I wanted to keep some relevant context (after 6 months of "silence"). The ticket (with a lot of useful discussion from this old thread missing): https://trac.macports.org/ticket/50448 Can we PLEASE PLEASE move forward with this? Let's not spend another thr

Re: GitHub usernames in maintainers field

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 their github account). Mojca

Re: GitHub usernames in maintainers field

On 11 February 2017 at 23:25, Ryan Schmidt wrote: > 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? >> &

Re: GitHub usernames in maintainers field

On 12 February 2017 at 06: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 GitHub and they sai

No email from the buildbot

Hi, Does anyone understand why there was no email sent from the buildbot for this failure? https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/3808 https://lists.macports.org/pipermail/macports-builds/2017-February/thread.html Mojca

Request to review rpcgen

Hi, I would like to ask for help with this: https://github.com/macports/macports-ports/pull/270 Apple already ships rpcgen, but it lacks an important flag to make the generated code thread-safe and I need that flag to package other software. The software seems "abandoned", but FreeBSD keeps

Re: No email from the buildbot

Dear Joshua & Ryan, On 22 February 2017 at 13:00, Joshua Root wrote: > On 2017-2-22 20:41 , Mojca Miklavec wrote: >> >> Does anyone understand why there was no email sent from the buildbot >> for this failure? >> >> https://build.macports.org/builders/ports-10

cxx11-1.1 & gcc

Dear Marcus, After you did the changes in cmake 1.1 I discovered the following in your port: # see https://lists.gnu.org/archive/html/octave-maintainers/2016-05/msg00286.html #PortGroup cxx11 1.0 # Octave requires c++-11 but can not use cxx11 PortGroup because Octave also #require

Re: Resolving pull request conflicts

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 > > 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 inv

Re: Resolving pull request conflicts

On 23 February 2017 at 12:04, Ryan Schmidt wrote: > > GitHub said the pull request had a conflict. (The PR is a version update, but > a revbump was committed to the port in the meantime.) GitHub said I could > resolve the conflict on the command line or in a web-based editor. There was > a green

Re: Resolving pull request conflicts

On 23 February 2017 at 11:19, Ryan Schmidt wrote: > GitHub invited me to edit the file on the web to resolve the conflict, so I > did. I was then asked by the PR author not to do that. To avoid confusion about my earlier replies: the only part that's in my opinion non-desirable is ending up with

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

On 28 February 2017 at 01:02, Jeremy Lavergne wrote: > On 02/27/2017 01:10 PM, Ryan Schmidt wrote: >> >> 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 d

Re: buildbot: +quartz ?

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 > non-default variants. As an interim step, however, I wonder if we might > consider a buildbot that is configured to default to “+quartz”? We don't even need a separate

Re: binary packages missing

On 4 March 2017 at 20:12, Mark Moll wrote: > Hi, > > For one of the packages I maintain, ompl, there are no recent binary > packages, despite the port being redistributable. I suspect it’s due to a > build time-out. The Python binding generation for the C++ library can take an > hour or two duri

Re: binary packages missing

On 4 March 2017 at 20:20, Mojca Miklavec wrote: > On 4 March 2017 at 20:12, Mark Moll wrote: >> Hi, >> >> For one of the packages I maintain, ompl, there are no recent binary >> packages, despite the port being redistributable. I suspect it’s due to a >> b

Timeout on the buildbot (wa: binary packages missing

On 4 March 2017 at 21:52, Mojca Miklavec wrote: > On 4 March 2017 at 20:20, Mojca Miklavec wrote: >> On 4 March 2017 at 20:12, Mark Moll wrote: >>> Hi, >>> >>> For one of the packages I maintain, ompl, there are no recent binary >>> packages, despite t

Re: Security Ticket Keyword

On 6 March 2017 at 15:41, Zero King wrote: > Do we have a way to mark tickets fixing security vulnerabilities? On GitHub or Trac? On GitHub I made a label "security fix" (which you already applied to one of your PRs, https://github.com/macports/macports-ports/pull/359). On Trac we could add a k

Avoiding repeating code for python variants

Hi, Is there some clean way to avoid repeating the following chunk of code four times (or more)? variant python27 conflicts python34 python35 python36 description {Enable GUI using Python 2.7} { set python.version 27 set python.branch "[string range ${python.version} 0 end-1].[string

Re: gitlab tags

On 9 March 2017 at 16:42, Jonathan Stickel wrote: > I am trying to make a port for git-latexdiff. It is hosted on gitlab: > > https://gitlab.com/git-latexdiff/git-latexdiff > > The project has "tags" which look similar to github's tags (and releases). I > am having trouble specifying the "master_s

Re: gitlab tags

On 9 March 2017 at 20:34, Jonathan Stickel wrote: > On 3/9/17 11:26 , Mojca Miklavec wrote: >> >> I would say that we should create a PortGroup for GitLab. > > Sure, that would be helpful, but it looks like only 3 ports are currently > associated with gitlab: > > So

Fwd: GSoC Announcement: GSoC 2017 Student applications are now open!

Hi, Student applications for GSOC are now open, you are warmly invited to participate for the MacPorts project. Feel free to ask questions on our mailing lists or on IRC. https://trac.macports.org/wiki/SummerOfCode Mojca -- Forwarded message -- From: Google Summer of Code Announ

<    1   2   3   4   5   6   7   8   >