Re: something is wrong with www.macports.org webpage

On 2018-01-13 18:51, Joshua Root wrote: > On 2018-1-14 04:43 , Joshua Root wrote: >> The page is being served as application/xhtml+xml but it was converted >> to HTML5. > > > should fix it. Please push to

Re: a no-homepage homepage for ports with dead homepages

On 2018-01-11 22:22, Jan Stary wrote: > On Jan 11 11:49:40, ken.cunningham.web...@gmail.com wrote: >> I've been prospecting MacPorts errors reported by repology >> . A >> common error is that the homepage 404s out. >> >> Many

New project member: grimreaper

Please join us in welcoming the following new MacPorts project member: - Eitan Adler (grimreaper) We look forward to continued excellent contributions from these new team members. - Joshua, Rainer, and Ryan Do you want to join the MacPorts team? If you would like to be considered for team

Re: registry.db-journal file location

On 2018-02-05 11:08, René J.V. Bertin wrote: > I have a test system on which certain operations, esp. uninstalling, block > for up to over a minute after they appear to be done (= after the last debug > info was printed). This doesn't just block the port command in question, it > also blocks

Re: registry.db-journal file location

On 2018-02-05 16:47, René J.V. Bertin wrote: > On Monday February 05 2018 15:34:52 Rainer Müller wrote: >> in your setup. To try this, you should be able to convert your registry >> database to this mode without making any changes to base itself. > > I presume that I can alwa

Re: GSoC 2018 Project: Improve startupitem code

On 2018-02-15 20:22, Joshua Root wrote: > On 2018-2-16 06:02 , Bradley Giesbrecht wrote: >>> On Feb 15, 2018, at 10:47 AM, Joshua Root wrote: >>> >>> On 2018-2-16 05:04 , Bradley Giesbrecht wrote: How to handle two launchd plists with “port load” command? Separate ports?

Re: Fix Sierra Trac query

On 2017-12-25 11:34, Jan Stary wrote: > On Dec 24 13:56:08, ryandes...@macports.org wrote: > Perhaps Chris is suggesting to just change the tag going forward. I would find that more confusing. >>> >>> How is "10.13" confusing? >>> How is it more confusing than "High Sierra"? >> >> I meant

Re: port "gohome" --> "A keychain cannot be found."

On 01/02/2018 08:52 PM, Ken Cunningham wrote: > Often, but oddly not always, when I try to use > > port gohome PORTNAME > > it opens Safari but then brings up a modal dialog box with the above message, > requiring Safari to be force-quit. > > If you click the option button “Reset To Defaults”

Re: travis builds time out -- then keep restarting ???

On 01/02/2018 11:13 AM, Jan Stary wrote: > On Sep 15 15:37:01, ken.cunningham.web...@gmail.com wrote: >> Something funny is going on with travis today. >> The builds keep restarting after timing out at 48 mins, I think >> > > On Sep

Re: Cmake build problem workaround

On 2018-06-18 21:20, Randolph M. Fritz wrote: > This is what I ended up with. I don't like it at all. > > pre-destroot { >     # This fixes what may be a cmake error >     catch { > # look for DESTDIR in the fixup_bundle arguments > exec grep -q {fixup_bundle.*DESTDIR} >

Re: "size" documentation

On 2018-08-18 09:53, Jan Stary wrote: > On Aug 17 22:06:13, c...@macports.org wrote: >> I think the idea of the size keyword is to start to use it to display >> download progress bars for servers that do not send a Content-Length >> HTTP header (or do not have an equivalent of such a header due to

Re: Golang dependencies and glide

On 2018-09-04 11:54, Mojca Miklavec wrote: > Our current support for go-based software and libraries is pretty much > non-existant. The fact that everything needs to be done manually is > super suboptimal. Ideally we would have a PortGroup which could take > care of dependencies in a similar way

Re: Identifying possible situations for interactivity

On 2018-09-01 18:12, Eric Gallager wrote: > - modifications to configuration files: > {{{ > Configuration file `/sw64/etc/shells' > ==> File on system created by you or by a script. > ==> File also in package provided by package maintainer. >What would you like to do about it ? Your

Re: feature request: a method to try a Port build against the buildbot farm BEFORE it is committed to the main macports repository

On 2018-07-07 21:00, Ken Cunningham wrote: > It would be very helpful to be able to try a Portfile build against the > buildbot farm before committing it. > > We would get lots of info regarding breakage before the damage is done that > way. > > I can see that at present there is no easy

Re: feature request: a method to try a Port build against the buildbot farm BEFORE it is committed to the main macports repository

On 2018-07-08 18:02, Ken Cunningham wrote: > > On 2018-07-08, at 7:59 AM, Rainer Müller wrote: > >> >> There was a lengthy thread on this in April: >> https://lists.macports.org/pipermail/macports-dev/2018-April/038023.html >> >> Rainer > > I had t

New project member: amake

Please join us in welcoming the following new MacPorts project member: - Aaron Madlon-Kay (amake) We look forward to continued excellent contributions from these new team members. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be considered for team

Re: request for port create command, to build a portfile from a URL

On 2018-03-06 23:00, db wrote: > [...] an *overview* of how to write a portfile is much needed. Isn't this what this chapter in the guide is supposed to provide? https://guide.macports.org/#development Rainer

Re: Buildbot proposal: combine portwatcher and portbuilder

On 2018-03-11 10:25, Ryan Schmidt wrote: > The current buildbot setup has a number of problems that I believe could be > solved by combining the currently separate portwatcher and portbuilder > schedulers into a single ports scheduler. > > I am not suggesting that we return to the behavior of

Re: Changing default cxx_stdlib to libc++

On 2018-03-09 15:21, Joshua Root wrote: > On 2018-3-9 20:38 , db wrote: >> On 9 Mar 2018, at 01:27, Ryan Schmidt wrote: >>> When would we run this script to delete libstdc++ archives? Presumably, >>> after all legacy users have MacPorts 2.5 and have switched to libc++.

Re: request for port create command, to build a portfile from a URL

On 2018-03-09 20:22, Enrico Maria Crisostomo wrote: > I pushed to GitHub a skeleton of the idea: > > https://github.com/emcrisostomo/macports-utils > > I've moved what I'm using to a new script to see what the end result looked > like. If you want to try it, just grab the release tarball

Re: request for port create command, to build a portfile from a URL

On 2018-03-11 23:54, Enrico Maria Crisostomo wrote: >> However, when we are going to add more templates, lots of options will >> be repeated in each of them. If we are later going to change any of >> these, we have to do this in all templates. I am not sure how much of a >> problem that will be.

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

On 2018-03-13 11:06, Rainer Müller wrote: > I am working on a filter by builder name. This should be covered with this commit: https://github.com/macports/macports-infrastructure/commit/830b9ff5b4f0af5d7d2598e01f48ff69074e7742 Rainer

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

On 2018-03-13 13:27, Ryan Schmidt wrote: > > On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: > >> On 13 March 2018 at 05:07, Ryan Schmidt wrote: >>> On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: >>> > Shall we backport these PRs to our buildbot 0.8.12 port? > > Add context field

Re: CI system for PR builds

On 2018-03-14 04:08, Ryan Schmidt wrote: > I was not aware of the existence of GitLab CI, but I haven't done a survey of > CI systems, mainly because we already selected one many years ago: Buildbot. > The problem, to my mind, was not that of selecting which CI system to use, > but the fact

Re: [macports-infrastructure] branch master updated: Use mpbb to mirror distfiles

On 2018-03-07 16:03, Ryan Schmidt wrote: > Ryan Schmidt (ryandesign) pushed a commit to branch master > in repository macports-infrastructure. > > https://github.com/macports/macports-infrastructure/commit/7a2fc5596970826f362413b362a5a3dc23db5e7a > > The following commit(s) were added to

Re: [macports-infrastructure] branch master updated: Use mpbb to mirror distfiles

On 2018-03-07 18:21, Rainer Müller wrote: > This should probably use path_jobs here. These are identical paths at > the moment, but I think it is better to keep the abstraction. Nevermind, I was interrupted while typing the mail and you already fixed it by now. Sorry for the noise. Rainer

Re: request for port create command, to build a portfile from a URL

On 2018-03-07 11:32, Enrico Maria Crisostomo wrote: > This is a little bit offtopic IMHO, anyway: I found surprising too that > the github portgroup was not documented, given the high percentage of > software that I build out of github repositories, and that's why I > recently contributed the

Re: Changing default cxx_stdlib to libc++

On 2018-03-14 00:42, db wrote: > On 14 Mar 2018, at 00:22, Mojca Miklavec wrote: >> Because someone would need to write the code for an alternative CI > > Wouldn't self-hosted GitLab CI be good enough? Are you going to sponsor a dedicated Mac server for GitLab CI? Travis CI

Re: Trac upgraded to 1.2

On 2018-04-01 09:35, Ryan Schmidt wrote: > So far, I dislike the "cosmetic improvements for ticket changelog". > > https://trac.edgewall.org/ticket/11835 > > I'm pretty sure I don't like the property changes floated to the right, and I > don't like that the box they're in is yellow. I agree

Re: CI system for PR builds

On 2018-04-03 12:31, db wrote: > On 3 Apr 2018, at 02:20, Rainer Müller <rai...@macports.org> wrote: >> Then please explain what this would offer us at all? > > I'll try. GitLab let's you have external runners > (https://docs.gitlab.com/ee/ci/runners/README.html

Re: py36 sub-ports fail to build

On 2018-04-05 19:05, Bjarne D Mathiesen wrote: > port -q search py36- \ > | xargs -n1 sudo port -Nup -f install Just a small hint here. The port command supports wildcards for port names. Just remember to escape for your shell: $ sudo port -Nup -f install 'py36-*' > diff <( port -q search py36-

Re: [macports-ports] branch master updated: librsvg: also use pre-cargo version for 10.8

On 2018-04-05 22:32, David B. Evans wrote: > +# cargo build also fails on 10.8 due to known SSL/TLS issues with > github.com +# Updating registry > `https://github.com/rust-lang/crates.io-index` +# Downloading > shell-escape v0.1.4 +# error: unable to get packages from source +# > Caused by:[35]

Re: [MacPorts] ProblemHotlist modified

On 2018-04-06 07:54, Ryan Schmidt wrote: > > On Apr 5, 2018, at 20:54, MacPorts Wiki wrote: > >> Page "ProblemHotlist" was changed by raimue >> Diff URL: >> >> Revision 138 >> Comment: No longer hot, have not even heard of this

Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase

On 2018-04-08 12:56, Jackson Isaac wrote: > On Sun, Apr 8, 2018 at 3:33 PM, Jackson Isaac wrote: >> I did find one at "https://github.com/mecke/aacgain; but I was not so >> sure if they both are by same author since 'alvarez' was mentioned at >>

Re: CI system for PR builds

On 2018-04-08 12:06, Ryan Schmidt wrote: >> As the buildbot has no local packages installed, operations like >> checking for the existence of a package over HTTP and then fetching the >> file will be slow. I expect this to be one major bottleneck. Our usual >> portbuilders have all previously

Re: Online MacPorts Meeting on 21st April at 13:00 UTC - suggestion

On 2018-04-07 14:18, William H. Magill wrote: > IRC is still quite popular in Europe, but is little used in the US. IRC on our #macports channel is fine to ask questions for which you do not want to write a lengthy email or to debug problems with quick back-and-forth on what to check or try.

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-08 03:26, Joshua Root wrote: > Joshua Root (jmroot) pushed a commit to branch master > in repository macports-base. > > https://github.com/macports/macports-base/commit/3dde77d7d6c66dbb8fcc1d4b1b4972a2ac8b1947 > > The following commit(s) were added to refs/heads/master by this push: >

Re: Releasing 2.4.3

On 2018-04-10 19:07, Ryan Schmidt wrote: > > On Apr 9, 2018, at 17:15, Rainer Müller wrote: > >> If nobody objects, I am going to tag a new release on Tuesday and >> prepare tarballs. > > Please merge my other two commits from this ticket: > > https://trac.

Re: Releasing 2.4.3

On 2018-04-10 19:39, Ryan Schmidt wrote: > > On Apr 10, 2018, at 12:07, Ryan Schmidt wrote: > >> On Apr 9, 2018, at 17:15, Rainer Müller wrote: >> >>> If nobody objects, I am going to tag a new release on Tuesday and >>> prepare tarballs. >> >>

Re: Releasing 2.4.3

On 2018-04-10 21:06, Ryan Schmidt wrote: > I'm not going to merge them, because I don't know how, and don't have the > energy to attempt to learn how to do so, given the zillion other things I'm > trying to do right now. This is even documented:

Re: Releasing 2.4.3

On 2018-04-10 19:39, Ryan Schmidt wrote: > Do you want to merge this performance enhancement too: [...] > And these bugfixes: I assigned this to the MacPorts 2.4.4 milestone, so we do not forget about them: https://trac.macports.org/ticket/56267 Rainer

Re: Releasing 2.4.3

On 2018-04-10 20:26, Ryan Schmidt wrote: > > On Apr 10, 2018, at 12:54, Rainer Müller wrote: >> >> At some point we should make a cut and not add many changes in the last >> minute... > > Well I can't force you to merge them. I cannot stop you either... I am just

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

On 2018-04-04 16:36, Andrew Moore wrote: > If I’m reading correctly the attached report from build...@macports.org > , port net/mosquitto fails for OS X <= > 10.6 due to indirect dependency: libpsl.  If so, this is presumably a > known issue, since many ports depend

Re: port & root

On 2018-04-05 19:14, Joshua Root wrote: > My guess is that this is a bug in Tcl's file command. Deleting a > nonexistent file is not supposed to be considered an error. But by > starting two instances of port(1) at the same time, a race condition > arises. The 'file delete' command probably checks

Re: port & root

On 2018-04-05 18:26, Bjarne D Mathiesen wrote: > When running './diffPorts php72-' as root I get this : Just to be specific, did you open a root shell first or did you run it with sudo? > Error: /macports/bin/port: Failed to initialize MacPorts, error deleting >

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

On 2018-04-04 17:19, Rainer Müller wrote: > Now that we execute the mirror step before attempting a build, we should > make the buildbot use a master_site_local pointing to a local mirror, as > we cannot expect the upload to be completed at the time the build runs. > Right now we are

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

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

Re: CI system for PR builds

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

Re: Dealing with False Positive during Livecheck

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

Re: CI system for PR builds

On 2018-04-12 20:14, db wrote: > On 12 Apr 2018, at 18:52, Ryan Schmidt wrote: >> 1. MacPorts does not have a method of declaring that a port does not build >> on a version of macOS. Such a feature is being discussed: >> https://trac.macports.org/ticket/15712 >> In the

Re: New guide section on Git and GitHub

On 2018-04-13 15:31, Jonathan Stickel wrote: > As a long time contributor of patches using the ticket interface (Trac), > I think it would be a mistake to discourage submission of patches there. > While it is fine to encourage use of git pull requests, the barrier of > entry is much higher. In

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-09 01:20, Joshua Root wrote: > On 2018-4-9 08:43 , Rainer Müller wrote: >> This handles ports that create .plist files via startupitem.* or the new >> startupitems. However, there are also ports that install custom .plist >> file to ${destroot}/Library/Launch

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-09 00:06, Joshua Root wrote: > On 2018-4-9 07:55 , Rainer Müller wrote: >> On 2018-04-08 03:26, Joshua Root wrote: >>> Joshua Root (jmroot) pushed a commit to branch master >>> in repository macports-base. >>> >>> htt

Releasing 2.4.3

Hello, according to our milestone on Trac, there is nothing left to be fixed or backported to the release-2.4 branch for MacPorts 2.4.3. The ChangeLog was already updated and reflects the changes this release will contain: https://github.com/macports/macports-base/blob/release-2.4/ChangeLog See

CI system for PR builds

On 2018-04-07 07:40, Mojca Miklavec wrote: >>> - with a bit of legal questionability >> >> From my understanding, it is legal to virtualize macOS, as long as the >> hypervisor is running on a Mac as well, which is possible. > > I'm aware that it's legal to virtualize macOS on mac hardware, it's >

Re: CI system for PR builds

On 2018-04-07 19:44, Clemens Lang wrote: > For these resons, we want to reset the machines to a clean state before > every build, which we could do with buildbot, but requires some python > magic that hasn't been written yet. I think this is mostly written. What is needed is only a little bit of

Re: port & root

On 2018-04-05 19:39, Joshua Root wrote: > On 2018-4-6 03:25 , Rainer Müller wrote: >> On 2018-04-05 19:14, Joshua Root wrote: >>> My guess is that this is a bug in Tcl's file command. Deleting a >>> nonexistent file is not supposed to be considered an error. But by

Re: [macports-ports] 01/04: aften: An A/52 audio encoder

On 2018-04-06 14:34, Michael Dickens wrote: > The issue being that if a port's configure checks for the build type (e.g., > {{{ > if(${CMAKE_BUILD_TYPE} STREQUAL "Release") then > ... > elseif > }}} > and so forth, and if "MacPorts" is not in BUILD_TYPEs list -- no matter > whether it has

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

On 2018-04-13 23:55, Joshua Root wrote: > On 2018-4-14 07:30 , Enrico Maria Crisostomo wrote: >> Hence, the macports installation that was built from the dirty tree is >> referring to the installation directory of the previous build. That also >> explains why removing that directory makes port

Re: [macports-base] 01/06: fetch: Always use ${prefix}/bin/git for gitfetch

On 2018-04-16 22:29, Ryan Schmidt wrote: > > On Apr 14, 2018, at 22:09, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >> >> https://github.com/macports/macports-base/commit/d

Re: Buiid/install stages documentation?

On 2018-04-18 15:20, Perry E. Metzger wrote: > On Tue, 17 Apr 2018 22:33:10 -0500 Ryan Schmidt > wrote: >> On Apr 17, 2018, at 12:39, Perry E. Metzger wrote: >> >>> Just to be clear: I know what is in: >>> https://guide.macports.org/#reference.phases >>> >>> but I'm

Re: [macports-base] 01/06: fetch: Always use ${prefix}/bin/git for gitfetch

On 2018-04-18 05:37, Ryan Schmidt wrote: > > On Apr 17, 2018, at 07:33, Rainer Müller wrote: > >> On 2018-04-16 22:29, Ryan Schmidt wrote: >>> >>> On Apr 14, 2018, at 22:09, Rainer Müller wrote: >>> >>>> Rainer Müller (raimue) pushed a commi

Re: Online MacPorts Meeting on 21st April at 13:00 UTC - suggestion

On 2018-04-18 01:11, Rainer Müller wrote: > On 2018-04-13 13:34, Mojca Miklavec wrote: >> If we find three volunteers (I volunteer, so only two more needed), we >> could perhaps do a technology test run tomorrow at 13:00 UTC (that's >> precisely 7 days earlier) >> ... (

Releasing 2.4.4

Hello, as discussed in today's online meeting [1], there is nothing left to be fixed or backported to the release-2.4 branch for MacPorts 2.4.4. The ChangeLog shows the changes this release will contain: https://github.com/macports/macports-base/blob/release-2.4/ChangeLog See also the full

Re: Online MacPorts Meeting on 21st April at 13:00 UTC

On 2018-04-07 10:31, Mojca Miklavec wrote: > I would like to announce the first online MacPorts meeting happening > two weeks from now, on April 21st at 13:00 - 14:00 UTC (if it takes > much longer than one hour, we are probably doing something wrong). The minutes of the meeting can be found on

Failure in port diagnose (was: Re: Releasing 2.4.4)

On 2018-04-21 23:23, Michael wrote: > I took a look at the change log, and saw there is a command, port diagnose This was first released with 2.4.0 last year, but no changes were made for 2.4.4. > bash-3.2# port -v diagnose > Error: process_cmd failed: dsAttrTypeNative:shell: /bin/bash >

Re: Migrating the guide to AsciiDoc

On 2018-04-22 09:44, Andrew Moore wrote: > Just to be clear, asciidoc is the format, but asciidoctor is the text > processor (a superset of python asciidoc). Is that correct? Yes. AsciiDoc is both the name of the format and also the name of the original reference implementation in Python, but

Re: [macports-base] 03/03: fetch: Do not redirect stderr

On 2018-04-16 01:31, Ryan Schmidt wrote: > > On Apr 15, 2018, at 11:34, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >> >> https://github.com/macports/macports-base/commit/6

Re: Allow access to a file in trace mode

On 2018-04-19 12:44, Ryan Schmidt wrote: > If I try to build minivmac in trace mode (sudo port -t install minivmac) it > fails because: > > Warning: The following existing files were hidden from the build system by > trace mode: > /Applications/MacPorts/Mini vMac/vMac.ROM > > The minivmac

Re: Can't use Expect in a portfile

On 2018-04-19 13:31, Ryan Schmidt wrote: > I can't seem to use Expect in a portfile. Using the following minimal > portfile: > > > PortSystem 1.0 > name foo > version 1 > fetch { > system "expect -c 'spawn echo hello; interact;'" > } > > > And running: > > > sudo port fetch > > > I

Re: Can't use Expect in a portfile

On 2018-04-19 13:58, Ryan Schmidt wrote: > > On Apr 19, 2018, at 06:49, Rainer Müller wrote: > >> On 2018-04-19 13:31, Ryan Schmidt wrote: >>> I can't seem to use Expect in a portfile. [...] >>> >>> The system has no more ptys. As

Re: Online MacPorts Meeting on 21st April at 13:00 UTC - suggestion

On 2018-04-19 11:24, Rainer Müller wrote: > On 2018-04-18 01:11, Rainer Müller wrote: >> On 2018-04-13 13:34, Mojca Miklavec wrote: >>> If we find three volunteers (I volunteer, so only two more needed), we >>> could perhaps do a technology test run tomorrow at 13:00

Re: Migrating the guide to AsciiDoc

On 2018-04-22 09:29, Mojca Miklavec wrote: > As requested during yesterday's meeting, here's the result of > automatic conversion of our guide from xml (docbook) to asciidoc: > > https://github.com/macports/macports-guide/tree/master/guide/adoc > > This was initially explored by Aljaž and

Re: Migrating the guide to AsciiDoc

On 2018-04-23 10:42, Jan Stary wrote: > Also, having manpages written in asciidoc means we need > the abominable docbook to actually produce the man(7) pages, right? > At least that's what it says at the end of install: > > * Warning: Using pre-generated man pages only. > * asciidoc,

Re: Migrating the guide to AsciiDoc

On 2018-04-23 10:12, Jan Stary wrote: >>> We are already using the AsciiDoc format for our man pages, >> >> Manpages are supposed to be written in mdoc(7), the language of >> manpages, just like e.g. /usr/share/man/man1/ls.1 is. >> >> The current port-* manpages are horrible >> (not talking about

Re: Migrating the guide to AsciiDoc

On 2018-04-23 14:27, Jan Stary wrote: >> These quirks are added by DocBook XSLT and are apparently required to >> make the output compatible. If you disagree with that, talk to DocBook >> why they added them. > > You don't care that a 2008 workaround to a Debian bug > is included in every manpage

Re: Migrating the guide to AsciiDoc

On 2018-04-22 09:29, Mojca Miklavec wrote: > Hi, > > As requested during yesterday's meeting, here's the result of > automatic conversion of our guide from xml (docbook) to asciidoc: > > https://github.com/macports/macports-guide/tree/master/guide/adoc > > This was initially explored by

Re: [macports-ports] branch master updated: collectd: update to 5.8.0

On 2018-04-23 19:47, Perry E. Metzger wrote: > Perry E. Metzger (pmetzger) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/5b70112c367fdc957b751f1ca6b8f1d1314f3b46 > > The following commit(s) were added to refs/heads/master by

Re: Installing nokogiri with --use-system-libraries

On 2018-04-24 07:50, Mojca Miklavec wrote: > On 23 April 2018 at 17:42, Rainer Müller wrote: >> >> Ruby and gems are really strange... >> >> Apparently, installing nokogiri with bundle fails > > Wasn't it you who said that we don't need a port for it as

Re: [macports-ports] branch master updated: collectd: update to 5.8.0

On 2018-04-24 00:48, Perry E. Metzger wrote: > On Mon, 23 Apr 2018 23:58:23 +0200 Rainer Müller > <rai...@macports.org> wrote: >> It is a bit suspicious that you made no changes to files/dep-gen.sh >> in the port directory. >> >> The second half of the Portf

Re: What "openmaintainer" means

On 2018-04-25 17:10, Joshua Root wrote: > On 2018-4-26 00:25 , Perry E. Metzger wrote: >> On Wed, 25 Apr 2018 04:43:12 +1000 Joshua Root >> wrote: >>> On 2018-4-25 03:56 , Ken Cunningham wrote: Waiting for the maintainer to review the ticket submission someday often

Mirror size & completeness of binaries

On 2018-03-27 13:56, Mojca Miklavec wrote: > I don't know about the best way to do it, but I would like to suggest to > provide macports mirorring in two different sizes: a small one and a > complete one. > > While I'm a heavy supporter of providing support for legacy systems, I > see no reason

Re: Mirror size & completeness of binaries

On 2018-03-30 21:20, Ryan Schmidt wrote: > I have not yet heard any reason why we need to change the file structure of > the packages server. The start of the discussion was to have mirrors that only provide a subset of the packages, for example the latest release. It would be a lot easier to

Re: Python ports: should we use wheel files?

On 2018-03-31 12:11, Enrico Maria Crisostomo wrote: > The definition of a wheel file is the following: > >> Wheel (in this context) is a project that adds the bdist_wheel command to >> distutils/setuptools. This produces a cross platform binary packaging format >> (called “wheels” or “wheel

Re: Mirror size & completeness of binaries

On 2018-03-29 16:19, Ryan Schmidt wrote: > At the same time, we need to consider how MacPorts base will respond to the > situation. Currently, it assumes all packages are available on all mirrors. > Therefore, it tries to find a package on three mirrors before giving up. If > many mirror

Re: how to handle this element in Makefile.config ?

On 2018-03-26 14:31, macpo...@parvis.nl wrote: > I'm working on a port for munin 2.0.x > > the munin-node component builds and installs java plugins if the Makefile can > find the javac compiler. > > on my system I need to have java but I want to ignore this feature. > > code is: > - > #

Re: Questions on port development

On 2018-03-25 16:19, macpo...@parvis.nl wrote: > I'm working on a port for munin 2 as the current macports version 1.4.7 is of > 14 mar 2012. > The munin-node seems to work fine, the server part requires more testing. Great! That port is really in the need of an update. > (1) > > I need a port

Re: Semi-automating updates

On 2018-03-26 00:34, Mojca Miklavec wrote: > On 26 March 2018 at 00:14, Rainer Müller wrote: >> On 2018-03-25 06:11, Ryan Schmidt wrote: >>> >>> Currently PRs are tested by a separate build infrastructure on Travis. It >>> runs on three systems: Xcode 7.3 on

xcodebuild wants to write to $HOME/Library/Developer (was: Re: Editing Git history with GitUp)

On 2018-03-23 11:17, Mojca Miklavec wrote: > I just stumbled upon this app (I haven't tested it yet) which might be > able to avoid some pain when editing git history before pushing your > changes upstream: > http://gitup.co Thank you for the this tip. I especially like the visualization of

Re: [macports-base] branch master updated: portbuild: Pass -j for parallel builds to cargo

On 2018-04-02 22:13, Jeremy Huddleston Sequoia wrote: > This causes cargo to fail to build with -j being unrecognized. > > --->  Building cargo > Executing:  cd > "/opt/local/var/macports/build/_Users_jeremy_src_macports_macports-ports_devel_cargo/cargo/work/cargo-0.25.0" > &&  >

Re: CI system for PR builds

On 2018-04-03 01:18, db wrote: > On 2 Apr 2018, at 23:09, Clemens Lang wrote: >> On Mon, Apr 02, 2018 at 08:43:52PM +0200, db wrote: >>> GitLab 10.6 released with CI/CD for GitHub >> Interesting, but I couldn't find any indication that this would support >> builds on macOS. Do

Re: port policy questions for munin

On 2018-04-04 01:38, macpo...@parvis.nl wrote: > Questions about policy: > - how to submit Portfile (unified diff against the previous version?) If your new Portfile is significantly different from the previous version, a unified diff would not be helpful. Just attach the full Portfile in this

Re: GSOC

Hello Abhishek, On 2018-03-25 16:43, Abhishek Kashyap wrote: > I have drafted my proposals through GSOC portal.Please review it,give > feedback and suggest changes.As time is very less (only 2 days left) So > i hope you plase take steps soon as possible. Your proposal is well-structured and

Re: Semi-automating updates

On 2018-03-25 06:11, Ryan Schmidt wrote: > > On Mar 24, 2018, at 18:41, Michael Dickens wrote: > >> The only other "gotcha" I wonder about is including buildbots for various >> target OSs [do PRs already go through building on (say) 10.6 and newer?] > > The Buildbot is not currently involved

Re: port sync performance

On 2018-03-25 16:24, Perry E. Metzger wrote: > Now that I'm a project member, I've noticed that the performance of > "port sync" is vastly lower than the performance of "git pull", > probably because rsync is much slower than git. > > 1) Does anyone know why this is? Is git doing something

Re: MacPorts from behind proxy servers & fetching the file directly

On 2018-03-16 12:31, Mojca Miklavec wrote: > While discussing GSOC with Umesh, he repeated what we already > discussed during the meeting. Students in campuses (including the one > where he is studying and from which roughly 40 students participate in > GSOC each year) might be behind proxies and

Re: How to fetch and extract patches in archives?

On 2018-03-18 13:22, Zero King wrote: > On Sun, Mar 18, 2018 at 12:48:59PM +0100, Rainer Müller wrote: >> On 2018-03-18 12:28, Zero King wrote: >>> On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: >>>> On 18 March 2018 at 08:33, Zero King wrote

Re: How to fetch and extract patches in archives?

On 2018-03-18 12:28, Zero King wrote: > On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: >> On 18 March 2018 at 08:33, Zero King wrote: >> I would add the patches to distfiles and include debian site in >> master_sites. You then need to keep your fingers crossed that the main >>

Re: Fwd: understanding macports

On 2018-03-17 17:28, Abhishek Kashyap wrote: > News items as mentioned in GSOC and plists You need to elaborate more what you mean, as this is quite confusing. I assume you are talking about this idea [1], but it does not mention plists at all? The format of the news items for the ports tree has

Re: [macports-base] 14/18: fetch: Remove svn.method option

On 2018-03-20 02:32, Ryan Schmidt wrote: > Note: this commit is to the vcs-fetch branch, not to master. > > On Mar 18, 2018, at 19:20, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >

<    1   2   3   4   5   >