Re: How do base commits get released?

In addition to what Ryan already said, let me add a few more pointers. On 2018-11-02 03:41, George Plymale II wrote: > Furthermore, upon examining the commits between 2.5.3 and 2.5.4 it is > apparent that some commits on the master branch are missing: > https://github.com/macports/macports-base/co

Re: loading checksums table from pre-checksum block?

On 2018-10-27 09:16, René J.V. Bertin wrote: > I have a port with lots of subports for which I keep the checksums in a > table-like structure in a dedicated file, so as to keep the Portfile a bit > more manageable (and to be able to generate said table with a script when > it's upgrade time). >

Re: Keep 32-bit build support on Mojave

On 2018-10-24 23:53, Joshua Root wrote: > On 2018-10-2 08:50 , Joshua Root wrote: >> Second, I'm not sure about changing the SDK only some of the time, or >> not changing the deployment target. We've always recommended changing >> the deployment target for an entire installation globally if it's go

Re: Verify domain for github.com/macports

On 2018-10-23 12:18, Zero King wrote: > GitHub now supports verifying organization's domain[1], and Homebrew > verified their brew.sh[2]. Should we verify ours too? macports.org is now verified for the MacPorts organization. Rainer

Re: Merging pull requests before 72 hours

On 2018-10-17 09:42, Christopher Jones wrote: > On 17 Oct 2018, at 1:17 am, Rainer Müller wrote: >> >> What you describe would be the process without openmaintainer. With >> openmaintainer, "minor updates" can be pushed directly by other project >> member

Re: Merging pull requests before 72 hours

On 2018-10-16 10:06, Chris Jones wrote: > On 16/10/18 07:37, Leonardo Brondani Schenkel wrote: >>> On 15 Oct 2018, at 11:18 pm, Chris Jones >> hep.phy.cam.ac.uk> wrote: >>> On 15 Oct 2018, at 10:34 pm, Leonardo Brondani Schenkel >>> at macports.org> wrote: I'm a committer, and if I'm doin

Re: cloning the macports-ports travis/CI to personal ports tree repositories?

On 2018-10-16 21:23, René J.V. Bertin wrote: > The biggest mystery for me is why the script adds a remote for the > macports-ports repo and then checks it out; isn't that taken care of > automatically by the CI? This is used to update the timestamps of the Portfiles. We use the PortIndex as dist

Re: cloning the macports-ports travis/CI to personal ports tree repositories?

On 2018-10-16 12:55, René J.V. Bertin wrote: > Are there guidelines somewhere how to tweak the travis.yml and > _ci/bootstrap.sh in order to get things set up correctly? You do not need anything special, just create an account on travis-ci.org, enable it for your fork of macports-ports, and selec

Re: Tcl namespaces and private procedures and variables

On 2018-10-09 00:18, Ryan Schmidt wrote: > What's the correct way to make a private procedure or variable in a portgroup > -- something the portgroup will use internally but that portfiles using the > portgroup should not use?> > I think the answer is to use a namespace. The xcode-1.0 portgroup d

Re: qreduce

On 2018-10-06 22:39, Mark Brethen wrote: > One advantage of the subport, it wouldn’t require fetching another copy of > the 270+ mb source file, but I could use svn to fetch just the qreduce source. If you use separate ports, you can use a common dist_subdir in both to share the distfile. Rainer

Re: new xcode build system and build failures

On 2018-10-01 16:53, Ryan Schmidt wrote: > > > On Oct 1, 2018, at 09:00, Ken Cunningham wrote: > >> To force Xcode10 to use the old build system (as it did before) add this >> flag to the xcodebuild args. Some ports need this in both the build and >> destroot args (aquaterm), others pass it in

Re: noise on selfupdate

On 2018-09-25 16:48, Dr M J Carter wrote: > On Tue, Sep 25, 2018 at 02:19:29AM +0100, Chris Jones wrote: > >> That said, does it ever say anything useful, more than the welcome >> below ? I confess I stopped playing detailed attention some time >> ago, but i don’t recall it ever saying anything i

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 as

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 options

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

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 mem

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

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 metho

Re: [macports-ports] branch master updated: grep: add new variant to install as ggrep

On 2018-06-30 20:46, George Plymale II wrote: > Rainer Müller writes: >> If grep is installed as ggrep, just just remove the dependency on >> bin:grep:grep and be done. > > I was inclined to do that initially, but I thought that since Macports > tries to rely on its own

Re: [macports-ports] branch master updated: grep: add new variant to install as ggrep

On 2018-06-30 08:39, George Plymale II wrote: > Ryan Schmidt writes: > >> Do all of the ports that declare the dependency "bin:grep:grep" already know >> that they should alternately look for a binary called "ggrep"? I don't know, >> and figuring that out and making any necessary adjustments to

Re: [macports-ports] branch master updated: grep: add new variant to install as ggrep

Just to add to the previous discussion, /usr/bin/grep used to be GNU grep on older versions of macOS. That is probably the reason why it does not implement the g* prefix like the other ports for GNU tools yet. On 2018-06-27 21:14, George Plymale II wrote: > I noticed that most of them have build d

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} > ${workpath}/build/InstallR

Re: PortGroup vs. Portfile search strategy

On 2018-06-12 21:20, René J.V. Bertin wrote: > Rainer Müller wrote on 20180612::18:22:46 re: "Re: PortGroup vs. Portfile > search strategy" > > Hi, > >> The implementation of PortGroup is here: >> https://github.com/macports/macports-base/blob/master

Re: PortGroup vs. Portfile search strategy

On 2018-06-12 10:43, René J.V. Bertin wrote: > Where would I have to look if I wanted to make a local patch to "base" so > that PortGroup files are looked up with the same tree hierarchy as used for > Portfiles (i.e. search first in the default tree, not only in the current > tree and then the d

dbus does not install startupitem into /Library/LaunchAgents (was: Re: [MacPorts] KDE modified)

On 2018-06-11 17:29, Jonathan Stickel wrote: > OK. Now I see the symlink for org.macports.kdecache.plist, but the > symlink for org.freedesktop.dbus-session.plist is definitely missing on > my machine. As a consequence, dbus was not loaded in launchctl and KDE > apps would not run for me this morni

Re: [MacPorts] KDE modified

On 2018-06-11 17:03, MacPorts Wiki wrote: > Page "KDE" was changed by jjstickel > Diff URL: > Revision 26 > Comment: it seems that the location of Macports-supplied lanuchagents have > changed recently > Changes: > ---8<--8<--

Re: glfw does not have a version option in PortIndex

On 2018-06-07 18:16, Joshua Root wrote: > On 2018-6-8 02:04 , Joshua Root wrote: >> On 2018-6-8 00:23 , Rainer Müller wrote: >>> Can anybody figure out what might be causing this? >>> >>> Note we run 'portindex -p darwin_16_i386' on the buildbot job t

glfw does not have a version option in PortIndex

Hello, a user on IRC reported a strange behavior that currently breaks updating the repology database. The glfw port does not have a version option in PortIndex set. The problem can be seen here: $ rsync --no-motd rsync://rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIn

Re: How are other dev's filtering macports mail?

On 2018-06-05 21:53, Daniel J. Luke wrote: > This may be something that would be useful to put in the wiki, but I thought > I'd ask on list how other committers deal with the large MacPorts email > volume. The way I've been doing it for many years doesn't work anymore (I > missed notification of

Re: CC vs assign

On 2018-06-06 03:14, iEFdev wrote: > When I added #56618, I forgot to CC the maintainer (mojca). When > modifying the ticket that CC option is gone, and all there's left is assign. > > I'm not really sure I feel that's up to me to do the assigning part. How > should I do/proceed? Assign is the co

Re: (Not) deprecating py35 subports

On 2018-06-03 01:37, Joshua Root wrote: > On 2018-6-3 07:28 , Mojca Miklavec wrote: >> The whole idea of the graveyard was to help users migrate to a newer >> version automatically, but in case of python it doesn't really serve >> the purpose if ports get moved to the graveyard at random times (ok,

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

On 2018-05-31 17:39, Rainer Müller wrote: > On 2018-05-31 16:49, Ken Cunningham wrote: >> >> On 2018-05-30, at 11:04 PM, Joshua Root wrote: >> >>> On 2018-5-31 15:39 , Ken Cunningham wrote: >>>> gcc5 is using libstdc++ (this installation is configured

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

On 2018-05-31 16:49, Ken Cunningham wrote: > > On 2018-05-30, at 11:04 PM, Joshua Root wrote: > >> On 2018-5-31 15:39 , Ken Cunningham wrote: >>> gcc5 is using libstdc++ (this installation is configured to use libc++) >>> gcc6 is using libstdc++ (this installation is configured to use libc++) >>>

Re: install-patch-install cycles & install without activate

On 2018-05-29 20:31, macpo...@parvis.nl wrote: > I'm trying to work as much as possible with scripted procedures. > > After an initial install of a new/modified port, I need to apply/change > patches. > > My workflow is: > > port install munin > > #- cycle start > port clean --work munin

Re: 2.5 and cxx_stdlib

On 2018-05-29 11:39, Vincent Habchi wrote: > Josh, > >> Not sure how you ran into that. Installing the new version of base must >> be done as root as well, and it runs scripts that open the registry and >> should trigger that upgrade. > > Transcript from my terminal: > > Air > sudo port selfupda

Online Meeting 2018-05-26

Hello, in our last meeting, we scheduled the next meeting to be tomorrow, 2018-05-26 13:00 UTC. However, this seems to have fallen off the radar, because we have not set any agenda yet... One point would be the website-related topics that we postponed in the last meeting due to time constraints.

Re: [MacPorts] #55764: geoexpress-sdk @9.0.0.3864: upgrade to 9.5.4.4709

On 2018-05-24 20:56, Vincent Habchi wrote: >> I don’t understand the licensing requirements, but I find this to be a >> convenient port for getting Mr. Sid support with the MacPorts gdal. I find >> it useful and hope that it can remain as long as it is appropriate. > > In any case, the support w

Re: [macports-ports] 02/02: py-alabaster: update to 0.7.10

On 2018-05-24 16:06, Renee Otten wrote: > Perry E. Metzger (pmetzger) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/ed0c7271ee05130702cdb1833ae686969e3e780f > > commit ed0c7271ee05130702cdb1833ae686969e3e780f Author: reneeotte

Re: configuredistcc=yes and ~/.distcc/hosts

On 2018-05-18 10:41, René J.V. Bertin wrote: > From what I can see in base, distcc is invoked in the controlled build > environment without any attempt at setting things up for distributed > compiling. > I don't exactly have a standard install (and so have $workpath/.home and .tmp > directories)

Re: [macports-ports] branch master updated: wireshark24: fix the Portfile's "name" field. Resolves #56459.

On 2018-05-10 23:10, Eric Hall wrote: > ghosthound pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/879e68cd177d0e4b03d29e1851aab6bf6ee50afb > > The following commit(s) were added to refs/heads/master by this push: > new 879e68c

Re: “Executable” StartupItems are preferred over “script” StartupItems

On 2018-05-15 20:57, macpo...@parvis.nl wrote: > >> On 2018-05-15, at 03:56, Ryan Schmidt wrote: >> >> >> On May 14, 2018, at 11:13, macpo...@parvis.nl wrote: >> >>> The Guide states “Executable” StartupItems are preferred over “script” >>> StartupItems. >>> >>> I have 2 daemons that are Perl s

Re: Ticket Commit Request

On 2018-05-12 17:56, Allan Que wrote: > I am requesting the commit of tickets #56438 > and #56440 > . I am not their maintainer and > these are not under openmaintainer, but I am taking advantage of > maintainer timeou

New project member: yan12125

To: Subject: Please join us in welcoming the following new MacPorts project member: - Chih-Hsuan Yen (yan12125) 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 considere

Re: [macports-mgr] Question about MacPorts project membership application

On 2018-05-14 08:53, Dave Horsfall wrote: > On Mon, 14 May 2018, Ryan Schmidt wrote: > Email has no such feature. >>> >>> And yet, you know what I meant. >> >> Well no, I don't. "Return receipt" to me means that the sender >> receives automatic notification that their message was received by

Re: [macports-mgr] Question about MacPorts project membership application

On 2018-05-13 23:03, Mojca Miklavec wrote: > On 13 May 2018 at 21:32, Rainer Müller wrote: >> On 2018-05-13 18:30, Mojca Miklavec wrote: >>> The portmgr team might need some time to check the contributions and >>> verify candidate's suitability for commit rights, b

Re: [macports-mgr] Question about MacPorts project membership application

On 2018-05-13 18:30, Mojca Miklavec wrote: > The portmgr team might need some time to check the contributions and > verify candidate's suitability for commit rights, but maybe they > forgot to send you a preliminary confirmation of receiving your > request and were simply waiting for the votes to a

Re: Gsoc 18 Project | Collect build statistics

On 2018-05-12 17:26, Vishnu wrote: > So where can i see that code that checks the modification time? https://github.com/macports/macports-base/blob/bb9db185d54c04efd55a3d634518a971bbb530a7/src/port/portindex.tcl#L120-L141 > "The portindex2postgres.sql script merely converts the PortIndex file > f

Re: Gsoc 18 Project | Collect build statistics

On 2018-05-12 17:27, Mojca Miklavec wrote: > I would in fact really really like to see a functionality like > portindex --mode=diff --format=json > that would create a table like > > { > new = [...], > removed = [...], > updated = [...] > } > > which would only provide the differe

Re: Gsoc 18 Project | Collect build statistics

On 2018-05-12 10:34, Vishnu wrote: > I am not saying that my db and the exiting Db would be interdependent. > Rather i am saying just once in forever I can copy the content to my > database. > Then do the code to keep on updating it whenever something is added or > deleted or modified. > > Like fo

Re: Gsoc 18 Project | Collect build statistics

On 2018-05-11 09:17, Mojca Miklavec wrote: >> I got the rough idea of the db from here: >> https://github.com/macports/macports-infrastructure/blob/2129f0cd0eb80f207d2cc62542b65c197733ac51/jobs/PortIndex2PGSQL.tcl#L249 > > Sure, you can take this as inspiration for database design, but not as > yo

Re: New project member: vishnu

On 2018-05-09 03:49, Zero King wrote: >> Do you want to join the MacPorts team? If you would like to be >> considered for team membership and commit access, please read this >> section of the Guide: >> >> http://guide.macports.org/chunked/project.membership.html > > Was PortMgr aware of > https://

Re: [macports-ports] branch master updated: poedit: new port @2.0.7

Hey Zero, I appreciate that you stepped up as the maintainer of poedit after I had given up on it! [1] However, the poedit port now bundles full builds of other software, including zlib, gettext, boost, icu, and even wxWidgets. That really should be avoided, as this software is already available

New project member: vishnu

Please join us in welcoming the following new MacPorts project member: - Vishnu M (vishnu, @Vishnum98) We look forward to continued excellent contributions during Google Summer of Code 2018 and beyond. - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be c

Re: Compiler blacklist 'shorthand'

On 2018-05-06 12:07, Ryan Schmidt wrote: > > On May 5, 2018, at 19:36, Craig Treleaven wrote: > >> A couple of times recently, I’ve noticed boilerplate in ports that require >> C++14. After including the compiler_blacklist_versions portgroup, they then >> do some gymnastics like: >> >> compile

Re: Releasing 2.4.4

On 2018-04-29 10:17, Mojca Miklavec wrote: > Are there any news or progress about the 2.4.4 release? It has been two weeks. How do we want to proceed? Rainer

Re: Instructions for creating patches

On 2018-05-03 09:14, Zero King wrote: > On Thu, May 03, 2018 at 08:51:49AM +0200, Mojca Miklavec wrote: >> On 1 May 2018 at 16:11, Rainer Müller wrote: >>> >>> The guide uses "Portfile-rrdtool.diff" as an example filename [1]. Some >>> users seem to ta

Re: Help with Pull Request

On 2018-05-03 12:14, Marcus Calhoun-Lopez wrote: > The only git commands I have been running (not in this order) are > git pull --rebase upstream master > git pull --rebase origin cargo-pg > git pull --rebase origin master > git push origin cargo-pg > where > cargo-pg is the nam

Re: missing dejavusansmono in rrdtool pango cairo fontconfig

On 2018-05-02 22:17, macpo...@parvis.nl wrote: > >> On 2018-05-02, at 16:15, Rainer Müller wrote: >> >> On 2018-05-02 12:44, macpo...@parvis.nl wrote: >>> (...) >>> Pango has a simple tool to show font examples: >>> pango-view --backend= --tex

Re: missing dejavusansmono in rrdtool pango cairo fontconfig

On 2018-05-02 12:44, macpo...@parvis.nl wrote: Macports installs fonts in /opt/local/share/fonts. This directory is seen only by fontconfig (defined in /opt/local/etc/fonts/fonts.conf). Most software uses cairo for advanced font handling and pango for the heavy-lifting in cairo. This is calle

Re: [macports-ports] 01/17: cargo PG: modify comments

On 2018-05-01 03:16, Rainer Müller wrote: > However, why do we add a license header to the port groups at all? > We also do not add it to each Portfile. I think we should drop the > license headers from all port groups. https://github.com/macports/macports-ports/pull/1707 Rainer

Re: Why didn't this PR get labeled?

On 2018-05-01 16:28, Perry E. Metzger wrote: > On Tue, 1 May 2018 13:20:45 + Zero King wrote: >> As Rainer replied, GitHub didn't provide the needed information in >> time. Maybe we should wait 30 seconds and retry? > > That seems like a very good idea. I'd probably wait two minutes, > though

Re: trac rrdtool

On 2018-05-01 15:20, macpo...@parvis.nl wrote: > searching for open tickets on rrdtool, I don't understand some things. [...] > What is happening here? Did these people perhaps made a patch on basis > of a rrdtool patch and didn't change the filename? The guide uses "Portfile-rrdtool.diff" as an

Re: Why didn't this PR get labeled?

On 2018-05-01 03:45, Helmut K. C. Tessarek wrote: > > > On 2018-04-30 09:49, Perry E. Metzger wrote: >> Sometimes, I've noticed, PRs in the queue don't get automatically >> labeled as expected. See this one, for example: >> >> https://github.com/macports/macports-ports/pull/1687 >> >> Anyone know

Re: [macports-ports] 01/17: cargo PG: modify comments

On 2018-04-30 05:26, Ryan Schmidt wrote: > > On Apr 28, 2018, at 04:31, Joshua Root wrote: > >> On 2018-4-28 13:04 , Ryan Schmidt wrote: >>> According to WikiPedia, "All rights reserved" has no effect in any legal >>> jurisdiction: >>> >>> https://en.wikipedia.org/wiki/All_rights_reserved >>> >>

Re: Request for discussion: lowering the backlog of old Trac tickets.

On 2018-04-30 21:09, Chris Jones wrote: > I would also argue we are using the same system, for two different things. > Short term bug reports and longer term 'work goals' are not the same, but we > seem to mix them up in the same system. Maybe some way (label ?) to identify > tickets that are go

Re: Request for discussion: lowering the backlog of old Trac tickets.

On 2018-04-30 18:16, Perry E. Metzger wrote: > But, more generally: because if you make your tracking system into a > graveyard of dead requests that will never be acted on, you end up > with it being very difficult for someone to look through it and find > things that actively need fixing. > > Th

Re: build failures and lack of logs

On 2018-04-29 14:31, Joshua Root wrote: > On 2018-4-29 22:04 , Jack Howarth wrote: >> As far as I can see, the links for the main.log file on these mailed >> build failure reports is a dead or empty file. > I see what you mean now. I'm not sure why we have a separate main.log > link when all the sa

Re: Why didn't this PR get labeled?

On 2018-04-30 15:49, Perry E. Metzger wrote: > Sometimes, I've noticed, PRs in the queue don't get automatically > labeled as expected. See this one, for example: > > https://github.com/macports/macports-ports/pull/1687 > > Anyone know why? The log file on braeburn says (times in UTC): Apr 28 1

Re: [MacPorts] Tickets modified

On 2018-04-30 16:14, MacPorts Wiki wrote: > Page "Tickets" was changed by pmetzger > Diff URL: > Revision 43 > Comment: Correct report number. > Changes: > ---8<--8<--8<--8<--8<--8<--8<--8< > Ind

Re: Open Letter of Apology

Hello Marcus, On 2018-04-28 01:33, Marcus Calhoun-Lopez wrote: > Recently, I made some major changes to the cargo PortGroup and the Portfiles > of several people. > My intent was: > *) create a branch > *) solicit feedback on the branch with the changes > > Instead, I pushed the chan

Re: [macports-ports] 09/17: cargo PG: respect build_arch; allow universal build

On 2018-04-28 00:34, Marcus Calhoun-Lopez wrote: > Marcus Calhoun-Lopez (MarcusCalhoun-Lopez) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/68a34f577814e3e5b3f444530262b109093da515 > > commit 68a34f577814e3e5b3f444530262b10909

Re: [macports-ports] 17/17: fd: use new features of cargo PG

On 2018-04-28 00:34, Marcus Calhoun-Lopez wrote: > Marcus Calhoun-Lopez (MarcusCalhoun-Lopez) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/24864aeda99bedbc183f882878df70e8b555aa0b > > commit 24864aeda99bedbc183f882878df70e8b5

Re: guide bug?

On 27 April 2018 23:12:31 GMT+02:00, Ryan Schmidt wrote: > >On Apr 27, 2018, at 16:11, Joshua Root wrote: > >> On 2018-4-28 06:25 , Ryan Schmidt wrote: >> >>> On Apr 27, 2018, at 08:10, Joshua Root wrote: >>> >>> 'move' still handles some case-sensitivity issues, but indeed >'copy' and >>

Re: guide bug?

On 2018-04-27 14:37, Perry E. Metzger wrote: > "For the above operations provided by Tcl's file command, MacPorts > provides the following shorthands. These should be used in preference > to the Tcl commands above, as they may work around certain bugs." Ah, I even linked to this section, but did n

Re: guide bug?

On 2018-04-27 03:23, Perry E. Metzger wrote: > In one part of the guide, we say not to use "file copy" but to use > "copy" instead, Are you sure you read that in the guide? > but in 4.3.2. we show an example using "file copy" > rather than "copy". Is this a bug? "file copy|move|delete" are native

Re: How do I check what is autobuilding successfully?

On 2018-04-26 22:48, Rainer Müller wrote: > On 2018-04-26 22:31, Clemens Lang wrote: >> | Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz >> | Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 >> 22cf20180c06c92f5fdc223180ba94bb96b6ff7b >> | Distf

Re: How do I check what is autobuilding successfully?

On 2018-04-26 22:31, Clemens Lang wrote: > | Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz > | Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 > 22cf20180c06c92f5fdc223180ba94bb96b6ff7b > | Distfile checksum: coffee-script-1.3.3.tar.gz rmd160 > e069ff420bc2584015f4a412d559

Re: Binary packages not rebuilding against updated libraries

On 2018-04-26 18:55, Perry E. Metzger wrote: > On Fri, 27 Apr 2018 02:46:43 +1000 Joshua Root > wrote: >>> So what might work would be trying out installing the archives in >>> a sandbox and using the same mechanism that's used locally before >>> triggering a rebuild? >> >> Sounds like a plan? >

Re: Binary packages not rebuilding against updated libraries

On 2018-04-26 15:36, Perry E. Metzger wrote: > Not sure. I did come up with a better solution for the ABI bump > problem, though, and wanted to run it by you. > > So rather than just guessing based on things like major version of a > library whether dependents need to be bumped, I would suggest we

Re: Binary packages not rebuilding against updated libraries

On 2018-04-26 07:48, Jan Stary wrote: > On Apr 26 03:16:37, rai...@macports.org wrote: >> On 2018-04-26 00:11, Jan Stary wrote: >>> On Apr 24 09:31:04, ken.cunningham.web...@gmail.com wrote: Portfile authors need to manually "revbump" the library's dependent ports when supporting lib

Re: Binary packages not rebuilding against updated libraries

On 2018-04-26 08:03, Jan Stary wrote: >> >> For comparison, the OpenBSD port system has resigned on upstreams' >> library versioning, and versions the libraries itself. For example, >> in audio/libsndfile (1.0.28): >> >> SHARED_LIBS += sndfile 6.0 # .1.28 >> >> and it installs /usr/local/

Re: Binary packages not rebuilding against updated libraries

On 2018-04-26 00:11, Jan Stary wrote: > On Apr 24 09:31:04, ken.cunningham.web...@gmail.com wrote: >> Portfile authors need to manually "revbump" >> the library's dependent ports when >> supporting libraries change significantly. >> It's not automatically figured out by MacPorts. > > Wait, what? I

Re: Agility

On 2018-04-25 21:02, Perry E. Metzger wrote: > On Thu, 26 Apr 2018 01:19:59 +1000 Joshua Root > wrote: >> On 2018-4-26 00:44 , Perry E. Metzger wrote: >>> I tend to think it's a better way of working but it's up to the >>> community as a whole to say if it's really the right way to do >>> things.

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 resulted in months of

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 giv

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

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 > 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 Portfile is fully generated by tha

Installing nokogiri with --use-system-libraries (was: Re: Migrating the guide to AsciiDoc)

On 2018-04-23 20:35, Andrew Moore wrote: > You might try: > > $ sudo gem update —system > > which should install the latest version of bundler (you really want that), > and go from there. > In the particular case of nokogiri, you might also try running `gem install > nokogiri` as user root. I

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 t

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 Alja

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-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, x

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 c

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 de

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

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 th

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 detai

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: 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 bui

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. Ask your sys

<    1   2   3   4   5   6   >