Re: [MacPorts] WorkingWithGit modified

On 2017-02-06 21:28, MacPorts wrote: > Page "WorkingWithGit" was changed by mkae > Diff URL: > > Revision 76 > Comment: Describe how to work on someone's PR > Changes: >

Re: [GSoC] Call for Mentors GSoC 2017

On 2017-02-07 04:52, Jackson Isaac wrote: > Clemens, Lawrence, Michael, Rainer, > > There are some of your ideas in the ideas list, would you like to > mentor GSoC students this year ? As in 2015, I am happy to help with the selection of students and with whatever comes up during the mentoring

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

On 2017-01-21 15:42, Kevin Reid wrote: > On Sat, Jan 21, 2017 at 5:20 AM, Ryan Schmidt > wrote: > > GitHub doesn't have server-side pre-commit hooks. > > > It does have pre-(merge or push) hooks, in the form of “status checks”. As

Re: Your message to macports-changes awaits moderator approval

On 2017-01-26 02:40, Joshua Root wrote: > On 2017-1-26 01:41 , Rainer Müller wrote: >> Your message was held for moderation because SpamAssassin gave the >> message a score of 6.2 for the following reasons: >> >> HEADER_FROM_DIFFERENT_DOMAINS, HEADER_SPAM, HTML_MESSAG

Re: Your message to macports-changes awaits moderator approval

On 2017-01-25 13:50, John Patrick wrote: > I'm getting these emails too for pull requests I created that have > been approved. > > Is someone able to whitelist github sending emails to the > macport-changes list... Sorry for the inconvenience, these mails are certainly not intended to go out to

Re: Postfix, CAfile and Macports

On 2017-01-27 09:07, Johannes Kastl wrote: > I found the reason. Somehow the postfix started via macports 'port > load postfix' and with all paths in main.cf pointing to /opt/ used > some configuration in /etc/postfix/. Or maybe /opt/local/bin/mailx > used it. Are you sure it is actually the

Re: PortFile command

On 2017-01-26 12:33, René J.V. Bertin wrote: > The only real obstacle is the fact that only a single file, > "Portfile" is copied into the registry, but a quick look suggests > that could be solved by loading delegate Portfiles through a `proc > PortFile` (clone of the PortGroup proc) that sets

Re: PortFile command

On 2017-01-26 23:12, René J.V. Bertin wrote: > On Thursday January 26 2017 21:56:59 Rainer Müller wrote: >> Looking at the VLC port it looks like the subport ffmpeg-VLC and >> the main port have nothing in common at all. > > You're not wrong but that's not entirely tru

Re: Handling C++11

On 2017-01-16 21:03, Ken Cunningham wrote: > Rather than force the older systems to install gcc6 and libgcc and > then find a roundabout and complicated way to support cxx11 with c++ > standard library inconsistencies, I would suggest we finally just > change/add/modify/get the buildbots to libc++

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

On 2017-01-16 03:13, Ryan Schmidt wrote: > >> On Jan 15, 2017, at 07:22, Rainer Müller <rai...@macports.org> wrote: >> >> Rainer Müller (raimue) pushed a change to tag release_2_3_4 >> in repository macports-base. >> >> *** WARNING: tag release_2_3_4

Re: [macports-base] 02/03: Add 'rleaves' alias

On 2017-02-17 22:42, Dan Villiom Podlaski Christiansen wrote: > Dan Villiom Podlaski Christiansen (danchr) pushed a commit to branch master > in repository macports-base. > > https://github.com/macports/macports-base/commit/b042c0e754098d7e7d6630e37f9db7ef9657a379 > > commit

Re: [macports-ports] branch master updated: misc: follow up on base changes and mass-unbreak ports in trace mode.

On 2016-11-07 12:13, Mihai Moldovan wrote: > Mihai Moldovan (Ionic) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/ce3e478b4aa910e128b737ff7523242ec6e63536 > > The following commit(s) were added to refs/heads/master by this

Re: GitHub migration complete

Remember we still have Trac. There is no requirement to use pull requests on GitHub for submission of changes, it is just an additional way. You can just file a ticket with the new file. This won't support any inline comments for reviews, though. > On Wednesday November 09 2016 14:24:36 Raine

Re: GitHub migration complete

On 2016-11-09 13:51, René J.V. Bertin wrote: > 1- Initially I followed github's suggestions as usual and added a > README.md (in a first commit), thinking I'd be able to avoid that > file easily enough. Instead it appears that pull requests can not be > made for a specific commit or

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

On 2016-11-10 01:30, Ryan Schmidt wrote: > I don't think MacPorts wants the burden of running and securing an > smtp server. That's not our mission. You'll have to find an smtp > server that allow you to change the from address. Uhm, in fact, we already do that for the forwards and the mailing

Re: `git describe`

On 2016-11-28 11:44, René J.V. Bertin wrote: > I presume that means they merge the development branch into master > before creating the release. Maybe. I do not want to dive deep into the release workflow of other projects. > Possibly: > > %> port provides /opt/local/bin/git-release >

Re: Macports Ticket System: why does UPPERCASE/lowercase matter when searching?

On 2016-11-13 10:04, Marko Käning wrote: > Do we have a ticket for this trac-setup issue? I was hoping we could resolve this quickly, but it does not seem to be trivial. I created a ticket to track this now: https://trac.macports.org/ticket/52871 Rainer

Re: python's LINKFORSHARED

On 2016-09-18 18:12, Rainer Müller wrote: > Hello pythonXY maintainers, > > in python27, the LINKFORSHARED config variable is broken: > > $ python2.7 -c "import distutils.sysconfig; \ > conf = distutils.sysconfig.get_config_var; \ > print (conf('LINKFORSH

Re: Macports Ticket System: why does UPPERCASE/lowercase matter when searching?

On 2016-11-12 11:25, Johannes Kastl wrote: > Searching for lowercase vlc gives one result, UPPERCASE VLC gives > some more. > > Is this intended behaviour? I just had a look and the port really is > named VLC, but installing it via "port install vlc" works. I would > propose ignoring case during

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

On 2016-12-13 20:33, Luc Bourhis wrote: > >> On 13 Dec 2016, at 20:14, Mojca Miklavec wrote: >> >> On 13 December 2016 at 20:08, Luc Bourhis wrote: >>> (Ruby is completely outdated and only the interpreter works, packaging is completely unmaintained. >>> >>>

Re: Branching for 2.4

On 2016-12-15 16:39, Joshua Root wrote: > If nobody can think of anything else, I'll go ahead and create the > branch and tag beta1 this weekend. Some more thoughts on the current state of master: # port diagnose 'port diagnose' seems completely broken. The ports tree resources do not contain

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

On 2016-12-06 17:03, René J.V. Bertin wrote: > Has there ever been discussion about if and how to let `port edit` > invoke a different editor when you're working locally vs. over SSH? 'port edit' just invokes the common VISUAL or EDITOR from your environment, so you will experience the same thing

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

On 2016-12-07 13:22, René J.V. Bertin wrote: > My question about the weird port_${action}_editor variable still stands > though. What's that about? There used to be 'port ed' as an alias for 'port edit'. This was before the unambiguous shortening of actions was introduced. This code in proc

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

On 2016-12-07 14:30, René J.V. Bertin wrote: > On Wednesday December 07 2016 14:15:26 Rainer Müller wrote: > >> There used to be 'port ed' as an alias for 'port edit'. This was before >> the unambiguous shortening of actions was introduced. This code in proc >> action_por

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

On 2016-12-07 12:20, René J.V. Bertin wrote: >> What does that achieve that setting $EDITOR doesn't? > > For one thing it would also provide a convenient way to use a simple, > lightweight editor when you want or have to avoid the usual editor > for a few quick changes. The standard vi fallback

Re: Your message to macports-changes awaits moderator approval

On 2016-12-02 12:28, Mojca Miklavec wrote: > 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

Re: `git describe`

On 2016-11-29 15:01, Davide Liessi wrote: > 2016-11-29 14:49 GMT+01:00 René J.V. Bertin : >> On Tuesday November 29 2016 13:28:27 Clemens Lang wrote: >>> You can just use >>> [vercmp $macports_version 2.3.4] > 0 >>> to check whether a bugfix you need is available. >> >> Which

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

On 2016-12-06 02:34, Joshua Root wrote: > From what I understand, what we'd really like for that case is a > "squash, rebase and merge" option. Unless we've misunderstood what > "squash and merge" does and it doesn't actually create a merge commit? No, "squash and merge" will not create a merge

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

On 2016-12-02 21:47, René J.V. Bertin wrote: > On Friday December 02 2016 20:54:41 Rainer Müller wrote: > >> Which notification mail? There are no notification mails going to the >> maintainer for pull requests unless the person opening the pull requests > > We must be

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

On 2016-12-02 20:39, René J.V. Bertin wrote: > What does "@mentioning maintainers on pull requests" do, concretely? > (If it's akin to those #sillytweetythingies, aka "hey @RJVB, could you ..." - > that looks just as silly to me, if you read the notification emails before > opening the webpage

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

On 2016-12-06 12:42, René J.V. Bertin wrote: > On Tuesday December 06 2016 11:39:22 Rainer Müller wrote: > >> You do not even need any other repository: >> >> git fetch origin refs/pull/89/head >> git checkout -b pull-89 FETCH_HEAD >> git rebase

Re: Command line switch to say yes to dependencies?

On 2017-01-03 17:47, Sterling Smith wrote: > I did search `man port`, but I had not added my custom install's > MANPATH. MANPATH is supposed to be empty, as man(1) will then deduce the paths from the PATH environment variable. > Note that the use of the phrase "non-interactive mode" for this >

Re: Build Failure: cctools, libmacho, libmacho-headers

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 can install to > /opt/curl) instead of the host's version? More and more source mirrors are > dropping

Re: PATH deals with binaries, not libraries

On 2017-03-22 08:54, Jan Stary wrote: > Even if this gets rejected (as it seems to be the consensus > to edit the user's shell configuration during the install), > there is one bit of wording in installig.xml that I think > should be changed (see diff below). > > The PATH is where shell commands

Re: Prevent MacPorts editing .bash_profile

On 2017-03-22 07:48, Jan Stary wrote: > As discussed currently on -users, here is a diff > that stops postflight messing with the user's config > and edits the correspondng parts of installing.xml As I said on macports-users, the output from the postflight script will not be shown to the user.

Re: citing git commits on Trac?

On 2017-03-28 15:34, Joshua Root wrote: > Documentation is available at . > > I find the easiest way to link to a commit is [committish/repo], e.g. > [42a4d67a/macports-ports]. Apparently you need at least 8 characters of > the hash, which is slightly

Re: port search --maintainer[s]

[sending again with correct list address] On 03/30/2017 06:18 PM, Jan Stary wrote: > This is 2.4.99 from git running on 10.6.8. > The 'port search' recognizes '--maintainer' and '--maintainers', > but the guide says '--maintainer' and '--maintainer' > while port-search.1 only says '--maintainer'.

Re: GSOC Application

Hello, On 03/30/2017 04:04 PM, Chinmaya Bhat wrote: > I am Chinmaya, a third-year Computer Science student at BMSIT, Bangalore. I am > new to MacPorts. I can code in C and Python and am going through the Tcl > tutorial on the GSOC wiki. > I have installed MacPorts and am reading the

Re: manpages is mdoc(7)

On 03/30/2017 09:26 PM, Jan Stary wrote: > Just forget it. My intentions when proposing the mdoc(7) rewrite > were the opposite of having asciidoc and docbook and xml/xsl ... While the dependencies seem quite heavy, languages like man(7)/mdoc(7) just fell out of fashion and rarely anyone still

Re: GSOC Application

On 03/31/2017 12:08 AM, Bradley Giesbrecht wrote: > Would the buildbots upload the tarballs to the MacPorts mirrors? Yes, that is the idea. It will not even require anything special on the buildbots, as just running the usual 'sudo port fetch' will generate this tarball after fetching from VCS.

Re: port search --maintainer[s]

On 2017-03-30 23:44, Jan Stary wrote: > On Mar 30 21:06:59, rai...@macports.org wrote: >> On 03/30/2017 06:18 PM, Jan Stary wrote: >>> This is 2.4.99 from git running on 10.6.8. >>> The 'port search' recognizes '--maintainer' and '--maintainers', >>> but the guide says '--maintainer' and

Re: GSoC Proposal

Hello, On 2017-03-31 17:43, Zero King wrote: > I'd like to implement a bot in Go dealing with pull requests for > macports-ports on GitHub and utilize Travis CI to test PRs and commits > in GSoC 2017. > > More details in my draft: > https://gist.github.com/l2dy/420533b821570e26dc7374898c3264fb >

Re: manpages is mdoc(7)

On 2017-04-01 10:28, Jan Stary wrote: > But the age of the asciidoc rewrite has nothing to do with it, right? > > I'm not hoping to change the course here, > but what were the manpages written in before this? > porthier.7 is in mdoc(7), with .Dd June 1, 2007 > - were all the base manpages im

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

On 2017-04-10 02:41, Andrew Fernandes wrote: > Andrew Fernandes (adfernandes) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/717197f4a88e94d5c667c4797712d1b0daecfaf6 > > The following commit(s) were added to refs/heads/master

Re: To force-push or not to force-push

On 2017-04-15 21:30, Mojca Miklavec wrote: > Hi, > > A confused maintainer just pointed out "a problem" with our guidelines: > https://trac.macports.org/wiki/CommitMessages#corrections > > ~~~ > You cannot correct commits that you have already pushed. Comment on > the commit's GitHub page

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

On 2017-04-21 21:55, Ryan Schmidt wrote: >> +depends_lib-append port:perl5 \ >> >> +port:p5-text-csv_xs > > It is not proper to depend on a stub port such as one whose name begins with > "p5-". Depend instead on the specific perl version of that module that you > want, e.g.

New project member: l2dy

Please join us in welcoming the following new MacPorts project member: - Zero King (l2dy) 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 membership

Re: Build base archives for CI in a separate repository

On 2017-07-28 04:06, Zero King wrote: > On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote: >> I would argue that the repository should in fact contain the MacPorts >> source code. Ideally, without change in the repository, the build >> results should be exactly the same, so there should

Re: GCC-ARM 6

On 2017-08-02 21:26, CeDeROM wrote: > Hello :-) Would that be possible to create a port of ARM-GCC version 6 > please? :-) I had filed a ticket for that quite a while now. As the maintainer has since abandoned the port, I just committed this older patch [1] without giving it much more testing. I

Re: install doc with python group

On 2017-07-11 15:23, db wrote: > On 11 Jul 2017, at 14:44, Joshua Root wrote: >> Only the subports like py27-setuptools_hg and py35-setuptools_hg are >> supposed to install any files. py-setuptools_hg is a stub port, and as such >> has no distfiles and thus no extracted

Re: registry with multiple portfiles

On 2017-07-11 18:40, db wrote: > On 11 Jul 2017, at 16:16, Joshua Root wrote: >> How do the files differ? Is one not referenced in the registry database? > > port cat shows the right file. I think I might explain this case — but not > others. While writing the portfile for

Re: hedgewars PR request to commit

On 2017-07-11 03:12, Ken Cunningham wrote: > https://github.com/macports/macports-ports/pull/522 > > This one I believe needs no more attention - it's been looked over well > enough I think to go ahead and commit. Done! Thanks for your contribution. > It's getting close to scrolling off page 1

Re: combining directories / moving files within Portfile

On 2017-07-19 23:09, Michael Dickens wrote: > I have an issue with SIP that needs to be addressed, that I'm not sure > how do execute in port via Portfiles. I have a solution, but it's kinda > a hack. This confused me a lot as I first assumed you are talking about System Integrity Protection...

Re: Build base archives for CI in a separate repository

On 2017-07-22 13:26, Zero King wrote: > In [1], I patched MacPorts in an attempt to fix a bug (port(1) failed > randomly on Travis). As it seems to be a Travis-specific bug, I plan to > use a separate repository to generate MacPorts archives used in CI and > keep the patch there. This way we can

Re: Buildbot now fails to build wine dependencies

On 2017-07-03 22:26, Mojca Miklavec wrote: > The problem is that we loop through all dependencies and install and > *uninstall* each individual one of them. This is both inefficient and > leads to problems like this one. > > The problem should be solved if we skip deactivation of dependencies.

Re: Is it time for a libc_fixes library yet?

On 2017-07-03 19:07, Ken Cunningham wrote: > So the last 10 or so tickets in trac seem like they are all for > basically the same issue - a few missing symbols from libc prior to 10.7. Well, I would take this as a reason to just drop support for such an old OS release... I know, I cannot convince

Re: [macports-ports] branch master updated: unar: new port at 1.10.1

On 2017-07-02 17:59, Zero King wrote: > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/2e286f5317b231e098549abfcfe30ccf15e07b89 > > The following commit(s) were added to refs/heads/master by this push: > new

Re: Buildbot now fails to build wine dependencies

On 2017-06-27 11:31, Ryan Schmidt wrote: >> > Installing dependency (55 of 120) 'cairo' with variants >> '+quartz+universal+x11' >> ... >> Error: glib2: Variant quartz conflicts with x11 > > The cairo port has for years had both x11 and quartz variants that are both > enabled by default.

Re: Buildbot now fails to build wine dependencies

On 2017-07-04 23:18, Joshua Root wrote: > On 2017-7-5 06:00 , Clemens Lang wrote: >> You were right on it when you mentioned the failcache. However, you only >> considered the reading part of the failcache, not the writing part of >> it. Makes sense, of course we need the full set of selected

Re: Why does autoconf.cmd remove autotools?

On 2017-06-29 09:17, Mojca Miklavec wrote: > It turned out that autoconf.cmd removes dependencies on autoconf, > automake, libtool ... > > Is there a good reason for that? Wouldn't it be safer to simply leave > the dependencies there, in particular if they have been listed by the > portfile? The

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

On 2017-04-26 14:15, René J.V. Bertin wrote: >> I really really don't think a PortGroup is the right way to do >> this. This should be done in base, with proper support of creating >> multiple packages from a single build and then optionally >> installing some of them, more like FreeBSD's ports

Re: Carthage Build Failure on BuildBot

On 2017-04-26 16:36, Zero King wrote: > Cloning into 'Carthage/Checkouts/Argo'... > fatal: unable to access 'https://github.com/thoughtbot/Argo.git/': SSL > certificate problem: Couldn't understand the server certificate format > fatal: clone of 'https://github.com/thoughtbot/Argo.git' into

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

On 2017-04-26 19:11, René J.V. Bertin wrote: > On Wednesday April 26 2017 17:32:58 Rainer Müller wrote: > >> source, but skip the compilation with pre-compiled archives. These >> are not real packages, as they cannot be installed standalone >> without a source ports

Re: [macports-ports] branch master updated: lang/ruby24: install libruby-static.a same as ruby23 or earlier

On 06/24/2017 01:49 AM, kimura wataru wrote: > kimura wataru (kimuraw) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/6959a9f89c69aba1849450ee5059c85ebafbc208 > > The following commit(s) were added to refs/heads/master by this

man.macports.org

Hello, I created a preliminary version of a linkable web version of our man pages: https://man.macports.org/port.1.html If anyone would be willing to contribute a better CSS, that would be highly appreciated. For example, linkable anchors for headlines on hover (as on Trac) would be nice to

Re: Travis and "rebase before commit"

On 2017-06-22 08:14, Sterling P. Smith wrote: > The simple solution is to allow the "Rebase" option in GitHub. It is enabled and the default. The thing is that in the Mojca's workflow for editing the PR commits, you would still need to push to the PR branch, wait for Travis to finish and approve

Re: [macports-ports] branch master updated: cdo: update to 1.8.2

On 2017-05-24 19:07, m...@macports.org wrote: > >> On May 24, 2017, at 1:12 AM, Takeshi Enomoto > > wrote: >> >> Takeshi Enomoto (tenomoto) pushed a commit to branch master >> in repository macports-ports. >> >>

Re: [macports-ports] branch master updated: qt4-mac: Fix pointer comparison with 0.

On 05/28/2017 05:34 PM, Mihai Moldovan wrote: > On 05/27/2017 11:08 AM, Ryan Schmidt wrote: >>> diff --git a/aqua/qt4-mac/files/patch-fix_pointer_comparison_to_0.diff >>> b/aqua/qt4-mac/files/patch-fix_pointer_comparison_to_0.diff >>> >>> new file mode 100644 >>> >>> index 000..4ed86aa >>>

Re: [GSoC 2017] Community Bonding

On 05/25/2017 09:27 PM, Umesh Singla wrote: > > About the project, so the `restore`, `snapshot` and `migrate` actions > > are going to the action_array list [1]. While the flow was made clear > > in the proposal, I think the first step should be to decide on an > > exhaustive list

Re: streamline github dev process

On 2017-05-31 10:40, Mojca Miklavec wrote: > On 30 May 2017 at 20:23, Helmut K. C. Tessarek wrote: >> Maybe you could allow maintainers to review and approve other pull requests. > > This would be ideal, but I don't know if there is any way to allow > that. This is again a question for the GitHub

Re: streamline github dev process

On 2017-05-31 16:38, Craig Treleaven wrote: > 0) The wiki currently includes the following: > > https://trac.macports.org/wiki/WorkingWithGit > > I presume we would adapt your Gist to become something like > “WorkingWithGitHubPullRequests”? I think the current page would be > unweildy if the

Re: [GSoC] Progress Report

On 2017-06-04 14:49, Zero King wrote: > GSoC coding phrase has begun and I'm implementing a CI bot that runs on > Travis CI and tests pull requests. > > My project includes two bots, the CI bot testing pull requests and the > PR bot assigning labels to PRs and notify maintainers. As far as I

Re: [macports-ports] branch master updated: net/wireshark2: update to 2.2.7 resolves #54272

On 06/03/2017 01:15 AM, Ryan Schmidt wrote: > (I don't think we're recognizing the word "resolves" as a synonym of > "closes".) We are using the defaults of Trac's CommitTicketUpdater: Close ticket: close closed closes fix fixed fixes Reference ticket: addresses re references refs see

Re: [GSoC] Progress Report

On 2017-06-05 03:17, Zero King wrote: > All information CI bot have access to is public, so I'm worried that > someone would send PR bot data without submitting a PR at all. Make the PR bot pull data from Travis. The CI bot then only triggers the PR bot, which then checks for new unprocessed

Re: [macports-contrib] 02/02: port-whatsnew: remove -t option for macportsTclPath - it doesn't appear to do anything

On 2017-06-16 04:14, Kurt Hindenburg wrote: > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > in repository macports-contrib. > > https://github.com/macports/macports-contrib/commit/d4985c85db95aa3423d614985df6da996533d636 > > commit d4985c85db95aa3423d614985df6da996533d636

Re: [GSoC] migration

On 2017-06-11 19:07, Bradley Giesbrecht wrote: >> 4. Another thing that ran my mind while pondering that there are 2 options >> for sqlite database as well: make the tables in the very beginning (while >> initial installation) or while running the snapshot for the first time. I >> suggest to go

Re: [GSoC] migration

On 2017-06-14 05:48, Umesh Singla wrote: > Thanks Rainer for this. This is really useful. I had doubts on how often > cregistry/sql.c file gets updated or whether this is the one. The name > sql.c seems to be so OS core file. So, I can just add the new tables here? > > Also, new tables means

Re: [GSoC] migration

On 2017-06-14 05:47, Umesh Singla wrote: > > 4. Another thing that ran my mind while pondering that there are 2 > options for sqlite database as well: make the tables in the very > beginning (while initial installation) or while running the snapshot > for the first time. I suggest

Re: streamline github dev process

On 2017-05-31 18:25, Zero King wrote: > On Wed, May 31, 2017 at 06:09:44PM +0200, Rainer Müller wrote: >> On 2017-05-31 16:38, Craig Treleaven wrote: >>> 0) The wiki currently includes the following: >>> >>> https://trac.macports.org/wiki/WorkingWithGit >&g

Re: [GSoC] Progress Report

On 2017-06-06 04:15, Zero King wrote: > On Mon, Jun 05, 2017 at 02:08:20PM +0200, Rainer Müller wrote: >> On 2017-06-05 03:17, Zero King wrote: >>> All information CI bot have access to is public, so I'm worried that >>> someone would send PR bot data without submitt

Re: Reversing use_bzip2

On 2017-09-14 11:30, Mojca Miklavec wrote: >> Therefore you also need to override these options: >> >> use_xz yes >> distfiles gcc-${version}.tar.xz:gcc >> extract.onlygcc-${version}.tar.xz >> >> To make this easier for the gcc ports, we could pass the suffix to >> crossgcc.setup as

Re: Restoring from Time Machine backup relocates home directories

On 2017-09-16 11:57, db wrote: > Shouldn't MP delete it if no files are owned by that user? In any case, it > could notify during installation that a user was created and upon > uninstallation that a user still owns files (and which) or not, and if not, > it could give the option to delete it.

Re: ignore "portfile changed" ?

On 2017-09-17 16:35, Ken Cunningham wrote: > when working on the destrooting of complex ports it is tedious to have the > ports rebuild with each portfile edit, esp the big ports that need the > complex destrooting > > It must be possible to override this -- I feel I'm missing something

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

On 2017-09-17 15:40, Umesh Singla wrote: > It's not a recent issue. I faced it 9 days ago as well. It keeps > restarting, aborting and then finally, got cancelled [0]. There are > absolutely no logs present. > > I hardly think it's a Travis issue. It would have been fixed by them or > informed if

Re: Restoring from Time Machine backup relocates home directories

On 2017-09-15 20:56, db wrote: > On 15 Sep 2017, at 18:06, Ryan Schmidt wrote: >> Not always, because many ports use local variables when setting the home >> directory, so you then have to find the place in the Portfile where that >> local variable is set. And also,

Re: ignore "portfile changed" ?

On 2017-09-17 16:41, Rainer Müller wrote: > On 2017-09-17 16:35, Ken Cunningham wrote: >> when working on the destrooting of complex ports it is tedious to have the >> ports rebuild with each portfile edit, esp the big ports that need the >> complex destrooting >

Re: Releasing 2.4.2

On 2017-10-06 18:30, Ryan Schmidt wrote: > > On Oct 6, 2017, at 09:32, Rainer Müller wrote: > >> mprsyncup [1] is supposed to handle that automatically. It seems >> like the job failed or is stuck, as ports.tar was also not updated. > > It seems to be having this pro

Re: Releasing 2.4.2

On 2017-10-06 18:58, db wrote: > On 6 Oct 2017, at 18:54, Ryan Schmidt wrote: >> Thanks, that was exactly the fix I was just going to suggest. I'll deploy >> that, then 2.4.2 should be available within the hour. > > Sorry to hijack the thread. I just installed 2.4.2

Re: Releasing 2.4.2

On 2017-10-06 14:53, Chris Jones wrote: > How long until this macports update is expected to be available via > selfupdate, as I am not getting this yet, it is still returning 2.4.1 as > the latest ? See below. > > Is the rsync server for some reason not yet updated ? No, it is not yet updated:

Re: [macports-ports] branch master updated: libhidapi: create 0.8.0-rc1, #47615

On 10/03/2017 01:23 AM, Jeremy Lavergne wrote: > Jeremy Lavergne (nerdling) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/5ad64a4d1d8f3537dfe1a39b230d1416e340e25b > > The following commit(s) were added to refs/heads/master by

Re: 10.13 ntp build failure (undefined symbols)

On 2017-10-03 22:26, Joshua Root wrote: > Apparently Apple's linker doesn't recognise common symbols in static > libraries as being defined. Workaround would be to initialise the > variables somewhere or use -fno-common. Ideally don't use common linkage > at all, have one file that each global

Re: [macports-ports] 01/04: livecheck/sourceforge.tcl: update default livecheck.regex

On 2017-10-14 21:50, Ryan Schmidt wrote: > Just to check: Did you know Rainer had just modified this regex before your > commit? > > https://github.com/macports/macports-ports/commits/master/_resources/port1.0/livecheck/sourceforge.tcl > > I'm wondering if your change undid what Rainer was

Re: [GSoC] migration

On 2017-09-08 23:33, Umesh Singla wrote: > When I run the `migrate` action with only one port (expat) installed, I > get the following: > > $ sudo ./bin/port migrate > > Taking a snapshot of the current state... > > Done: Snapshot '8':'snapshot created for migration' created at > 2017-09-08

Re: Change and request

On 2017-09-07 22:25, Wahlstedt Jyrki wrote: > Dear all, > as many of you have already seen, I’ve dropped nearly all of my > maintainerships. I’ve been involved in this community over ten years, > and now I feel I want to do some things preventing me from the > commitment to do this anymore on a

New project member: kencu

Please join us in welcoming the following new MacPorts project member: - Ken Cunningham (kencu) 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: Pull request types in template on GitHub

On 2017-09-11 11:49, Zero King wrote: > On Sun, Sep 10, 2017 at 02:28:46PM +0000, Rainer Müller wrote: >> Hello, >> >> our GitHub pull request template [1] contains the following snippet >> which is used by the macportsbot to assign the corresponding label

Re: Deactivate hack and increasing revision

On 2017-09-06 09:52, Ryan Schmidt wrote: > When the ssh-copy-id files were removed from the openssh port [1] and the > port was thus made to no longer conflict with the ssh-copy-id port, the > ssh-copy-id port would install, but could not be activated if the prior > version of openssh was

Re: Reversing use_bzip2

On 2017-09-13 11:48, Mojca Miklavec wrote: > When trying to update x86_64-w64-mingw32-gcc I noticed that GCC 7.2 no > longer provides bzip2 sources, but I'm not sure how to tell the > Portfile that it should use xz instead of bzip2 given that the > crossgcc group already contains "use_bzip2 yes".

Pull request types in template on GitHub

Hello, our GitHub pull request template [1] contains the following snippet which is used by the macportsbot to assign the corresponding label to it. ## Type(s) - [ ] bugfix - [ ] enhancement - [ ] security fix However, GitHub interpretes this as a list of tasks. This means that with that

Re: Appropriateness for inclusion in MacPorts

On 2017-09-04 14:46, Aaron Madlon-Kay wrote: > 1. Some OSS Java applications > > There are some Java applications I use that have both GUI and CLI components. > One of them is bundled by default with a JRE. A trivial port would basically > just download a .zip and dump the contents in

  1   2   3   4   5   >