Re: New project members: jonesc

Welcome, Chris! B-D Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Github user repos?

Dear Ryan, please delete my user repo https://github.com/macports/macports-user-mk I don’t need it and didn’t use is since ages. Thanks in advance. Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

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

Hi Ryan, On 02 Nov 2016, at 23:49 , Ryan Schmidt wrote: > I'm confused about why you're confused or what you're talking about. :) > We've always provided @macports.org email forwarding for committers. You tell > us what handle you want, we set it up to forward to

Re: Pull Requests for Work in Progress (WIP)

On 04 Nov 2016, at 02:19 , Arno Hautala wrote: > But, it occurs to me that one of the goals of moving > to GitHub is greater collaboration and that is facilitated by inline > comments on the pull request. Plus, a completed pull request is one > comment away from a work in

Re: Pull Requests for Work in Progress (WIP)

Hi Rainer, On 03 Nov 2016, at 18:57 , Sterling Smith wrote: > On Nov 3, 2016, at 10:47AM, Rainer Müller wrote: > >> On 2016-11-03 17:49, Sterling Smith wrote: >>> The main question of procedure is: Should the main macports repo be >>> used for

Re: Proposal for a MacPorts'ish commit message template

Hi Larry, On 04 Nov 2016, at 18:34 , Lawrence Velázquez wrote: > It doesn't really do anything differently w.r.t. wrapping, but it > highlights subject-line overflow in an alarming red color. that’s a nice feature. Will have to test whether that works as documented in our

Re: Proposal for a MacPorts'ish commit message template

On 02 Nov 2016, at 23:33 , Ryan Schmidt wrote: > ...my initial reaction to your template (and my initial reaction when I saw > it mentioned previously) was "TL;DR”. I got it now. :) >> vim does that with syntax highlighting automatically nowadays when it >> notices

Re: Proposal for a MacPorts'ish commit message template

On 02 Nov 2016, at 01:03 , Lawrence Velázquez wrote: > To be honest, this template adds so much comment noise that I can't > imagine ever using it. That’s fine ok, your decision. :) >> --- ~/.git-commit-template --- >> # Please enter the commit message for your changes.

Re: Proposal for a MacPorts'ish commit message template

Hi, On 02 Nov 2016, at 00:08 , Clemens Lang wrote: > Developers are free to use your template if they want to. We don't want > to mandate using it though (since we couldn't enforce it anyway). yeah, I am aware of that. > vim does that with syntax highlighting automatically

Re: Proposal for a MacPorts'ish commit message template

On 01 Nov 2016, at 23:56 , Sterling Smith wrote: > Remind me, would using this template still give the commented git status > (which is the default)? Yes, make a change and test it like this: $ git commit -a -t ~/.git-commit-template The status gets appended at the

Proposal for a MacPorts'ish commit message template

Hi MacPorts’ GitHubians, I know that many of you weren't in favour of a commit message template, but I propose one anyway, which I derived from KDE’s neat one, as I find it on the console quite handy to know when 50 or 72 characters are reached in a line: --- ~/.git-commit-template --- #

Re: Github user repos?

The question I already posted in the “GitHub migration complete” thread was whether I can simply remove my git repo altogether? On 01 Nov 2016, at 09:52 , Marko Käning <mk-macpo...@posteo.net> wrote: > On 01 Nov 2016, at 04:00 , Ryan Schmidt <ryandes...@macports.org> wrote

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

Hi Rainer, On 01 Nov 2016, at 21:05 , Rainer Müller wrote: > What do you mean by address rewriting? If you are referring to problems > with SPF, I guess I do. > the new mail server is now doing SRS [1]. OK... > Right now we do not host any mailboxes with IMAP, we only

Re: rev-upgrade question

On 01 Nov 2016, at 19:57 , Rainer Müller <rai...@macports.org> wrote: > On 2016-11-01 19:50, Clemens Lang wrote: >> On Tue, Nov 01, 2016 at 07:09:48PM +0100, Marko Käning wrote: >>> how can I convince rev-upgrade to actually rebuild broken ports if >>> 'r

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

Hi folks, Mojca was addressing the email and MacPorts handle issue in thread “[macports-ports] branch master updated: berkeleygw: Remove svn $Id$ line.” which brings me to the point, that this in in fact a bit of an long standing annoyance for me. On 01 Nov 2016, at 19:42 , Mojca

rev-upgrade question

Hi folks, how can I convince rev-upgrade to actually rebuild broken ports if 'revupgrade_mode' is set to ‘report' in macports.conf? Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: Trac down again

Trac is down again. It seems like it is periodically dying and reviving itself. :( ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: GitHub desired workflow...

On 01 Nov 2016, at 01:10 , Brandon Allbery wrote: > You can even configure so that becomes the default for "git pull" for that > repo. > > git config --local --bool pull.rebase true > git config --local --bool rebase.autoStash true This should go into the wiki page!

Re: Working with Git

On 01 Nov 2016, at 09:57 , Rainer Müller wrote: > > I do not see valid reasons not to use hub. +1 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

On 01 Nov 2016, at 02:02 , Rainer Müller wrote: > buildbot: ignore +1 I’d also suggest to use this also to specify which buildbots should be used for a commit: buildbot: Mavericks Sierra I think that can be very helpful in some cases. Opened a ticket for this:

Re: GitHub migration complete

On 01 Nov 2016, at 04:00 , Ryan Schmidt wrote: > We suggest that you move your user repository to your own GitHub account > where you can continue to use it as you see fit. Instructions for how to move > it are forthcoming. You should not use the Fork button to do so.

Re: Working with Git

Hi Mojca and Ryan, On 01 Nov 2016, at 05:54 , Mojca Miklavec wrote: > I'm with Ryan in this case. We don't prevent anyone from using this > software if they choose to, I just don't see the point of advertising > software whose maintainer decided to go against MP. I am with

Re: [macports-ports] branch master updated: jasper: needs a revbump

So, now I ran *again* into a problem with my local install after self updating it just now: --- $ port -v rev-upgrade ---> Scanning binaries for linking errors Warning: Error parsing file /opt/local/bin/cdda2wav: Error opening or reading file Warning: Error parsing file /opt/local/bin/cdrecord:

Re: GitHub migration complete

On 31 Oct 2016, at 21:14 , Lawrence Velázquez <lar...@macports.org> wrote: >> On Oct 31, 2016, at 5:23 AM, Marko Käning <mk-macpo...@posteo.net> wrote: >> >> a post-commit-hook checking whether the GitHub pull request ID #123 >> actually exists for the m

Re: [macports-ports] branch master updated: jasper: needs a revbump

On 31 Oct 2016, at 20:25 , Joshua Root wrote: > Depends on the nature of the breakage, which is not shown above. The only > dependency is jpeg, which has not changed in some time. My jasper > installation is certainly not broken. Hmmm… OK, next time I need to get more

Re: [macports-ports] branch master updated: jasper: needs a revbump

Hi Joshua, On 31 Oct 2016, at 18:04 , Joshua Root wrote: > Why? because I ran into this: --- $ port dir jasper /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/graphics/jasper $ sudo port upgrade outdated ---> Computing dependencies for jasper --->

Re: GitHub migration complete

Hi Larry, On 31 Oct 2016, at 05:38 , Lawrence Velázquez wrote: > Old habits die hard, but from now on do NOT refer to Trac tickets as > "#12345" in your commit messages; GitHub's website interprets those as > pull request numbers. Copy and paste the full Trac URL instead. a

Re: nested port upgrading and variants

Hi folks, thanks René, for reporting, but ... On 27 Oct 2016, at 21:59 , René J.V. Bertin wrote: > On Thursday October 27 2016 14:55:59 Ryan Schmidt wrote: > >>> That's what I told Marko too, but we're not talking here about the initial >>> installation. I think that when

Re: Git tools for managing patchsets

On 26 Oct 2016, at 17:54 , Michael wrote: > Interesting that you mention "Quilt". There is another tool -- Stacked Git -- > that is modeled after Quilt. I don’t see the point of these additional tools on top of git? If git provides branches, why do I need extra magic to

Trac down again

Where is our trac again? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Moving to GitHub: Status Update, Action Required

I fully agree with Mojca, that it is better to work on a private fork for the start and let others - like Clemens suggested - take part in reviewing on that forked repository. This way one can train what would have to be done on the main macports-ports repo before causing trouble there... On

Re: Git tools for managing patchsets

Hi folks, when I read only the first two paragraphs of this thread... On 24 Oct 2016, at 18:37 , Michael wrote: > So since MacPorts is moving to git, and from what I saw in the "how to use > git" docs you mentioned, you apparently want people to work with patchsets >

Re: QTKit & macOS Sierra

Hi René, On 24 Oct 2016, at 09:57 , René J.V. Bertin <rjvber...@gmail.com> wrote: > On Monday October 24 2016 09:54:56 Marko Käning wrote: > > Indirectly, yes. I get the impression port:opencv has been unmaintained for a > while, so maybe you can update the official copy from

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Hi, On 07 Oct 2016, at 17:31 , René J.V. Bertin wrote: > Port:qt5-kde doesn't depend on cmake anyway so it's pointless to hold up the > Qt5 discussion for it (but the KF5 ports do). OK, then let’s wait regarding the cmake portgroup until we’ve qt5-kde committed. > I

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Hi, in the light of the upcoming commit of the new 'qt5-kde' port I want to ask (again) whether it would be acceptable, that we - for the sake of housekeeping - store all KF5-related ports in a dedicated folder at dports/kf5 or whether it is really necessary, that all these KDE ports have

Re: Buildbots logon failing...

On 22 Oct 2016, at 18:28 , Ryan Schmidt wrote: > There's been no change to the buildbot. It still uses the separate user and > password database from the old macOS forge buildbot. Turns out that I tried to log in with my full handle email address, instead of only

Buildbots logon failing...

Hi, can it be that the authentication info for the buildbots hasn’t been migrated yet? I wanted to restart a build of kmymoney4-devel and couldn’t since my logon failed. Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: SVN committing not possible ATM?

Hi Rainer, On 22 Oct 2016, at 15:17 , Rainer Müller wrote: > This is probably some configuration issue on the server. We have not yet > figured out what causes this, but you are the second to report this. It > only seems to affect some users with specific commits. > > I

Re: Moving to GitHub: Status Update, Action Required

On 22 Oct 2016, at 14:49 , Joshua Root wrote: > Please see the Migration Timeline section in the first message in this > thread. Developers cannot yet push to the git repos. yes, I figured that now. OK, awaiting you guys’ decisions on the new workflow.

Re: Moving to GitHub: Status Update, Action Required

Hi Clemens, On 22 Oct 2016, at 14:41 , Clemens Lang wrote: > Developers will merge them, either using the command line client, or the > GitHub UI. We haven't decided and documented which merge method to use, > although I'd prefer the rebase. ok, I see. BTW, you’ve mentioned

Re: Moving to GitHub: Status Update, Action Required

Hi Clemens, great to see the GitHub conversion progressing this rapidly! Thumbs up from me!!! When reading the WorkingWithGit wiki page [1] I saw how port contributors can post their suggestions to MacPorts via "Pull Requests”, yet it does not get clear from that text how those PRs will then

Re: 2nd MacPorts Meeting & Online Meeting

Hi Clemens, On 16 Oct 2016, at 23:58 , Clemens Lang wrote: > Thanks, and sorry for not putting a plan together to do it in Munich in > the fall. Seems I need to improve my time management :) now that you say it… Weren’t you aiming at the Wiesn earlier this year? ;-) >> In

Re: [153663] trunk/dports/kde/kmymoney4-devel/Portfile

Hi Ryan, On 08 Oct 2016, at 10:04 , Ryan Schmidt wrote: >> kmymoney4-devel: increase version suffix, as that seems to be needed for the >> port to pick up the previously added patch file > > No, that's not the case. When I committed that revbump I was already unsure

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Dear Qt folks, regarding René's post from March (see below) I believe it would be good to give a _short_ update on the qt5-kde port status. Currently the situation for port qt5-kde is as follows: - Qt at version 5.6.1 - tested building on Mavericks and El Capitan VMs - René also managed

Re: No Xcode 8 CLT for El Capitan

Hi, there is no CLT for Xcode 8? How come Xcode 8.0 tells me in "Preferences/Locations" that it uses CLT "Xcode 8.0 (8A218a)”! I recently ran into this issue --- :info:configure :info:configureXcode not set up properly. You may need to confirm the license :info:configureagreement by

Re: GitHub tester wanted?

Hi Lawrence, On 20 Aug 2016, at 19:48 , Lawrence Velázquez wrote: > How can you play the n00b if you're so fluent? :P I can tell you: I CAN! :-) Have proven this umpteen times. Many of my coworkers tell me that I am the ideal tester! No joking. 8-D Greets, Marko

GitHub tester wanted?

Hi Clemens, if you need an independent tester for your MacPorts workflows on GitHub I am herewith offering my support. I’d happily clone the official MacPorts git repo (also before it is live) and try to create pull-requests and play the newbee there, because I think that’s the best way to

Re: Goodbye Mac OS Forge, hello GitHub

Dear Ryan, On 20 Aug 2016, at 02:18 , Ryan Schmidt wrote: > I'm pleased to announce that MacPorts will be moving its source code to > GitHub. in general I applaud this move! Congratulations to all those involved to make this change happen!!! > great collaboration

Re: New build system

Thanks Ryan, On 10 Aug 2016, at 08:02 , Ryan Schmidt wrote: > There are many options for excluding columns; see: > > https://build.macports.org/waterfall/help that slipped my attention. Exactly what I needed. :) Greets, Marko

Re: New build system

Dear MacPorts team, this is amazing news! Thanks for the great work!! The grid view looks more informative than before. The waterfall view is - horizontally - pretty full these days... It would be neat if at least a logged on user could customise the view a little, like e.g. being able to

Re: New Mac OS Forge administrator

Hi Ryan, On 20 Nov 2015, at 03:49 , Ryan Schmidt wrote: > I'm pleased finally to be able to tell you that I have been hired to be your > new Mac OS Forge administrator. this is just great news! I was already wondering why suddenly trac starts to show commits again.

Nonexistent mpi.default variable lets port upgrade fail

Ooops, what does this error suddenly happen? --- ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.4 installed, MacPorts base version 2.3.4 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To

Buildbots stuck?

Just noticed that the waterfall doesn’t show recently committed changes to ports… … are the buildbots stuck? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: All KDE ports need a major revbump, due to recent changes to qt4-mac

Answering my own question now, at least partially, since a rev-upgrade just gave me this much longer list: --- ---> Found 38 broken port(s), determining rebuild order ---> Rebuilding in order qtscriptgenerator @0.2.0 kdenlive @0.9.10 kdiff3 @0.9.98 litecoin @0.8.7.4

Re: All KDE ports need a major revbump, due to recent changes to qt4-mac

On 27 Oct 2015, at 22:48 , Marko Käning <mk-macpo...@posteo.net> wrote: > Answering my own question now, at least partially, since a rev-upgrade just > gave me this much longer list: Should we forget about revbumping everything and simply rely on that the sanity of our use

All KDE ports need a major revbump, due to recent changes to qt4-mac

Hi Nicolas, while building kdevelop and kdepim4 I came across some rev-upgrades… Thus I have rebumped ports kate, libkgapi and konversation. For instance, the latter tried to find libqca in it’s old location --- Dyld Error Message: Library not loaded: /opt/local/lib/libqca.2.dylib

Re: Buildbots stuck?

Thanks, Ryan, On 28 Oct 2015, at 00:28 , Ryan Schmidt wrote: > https://trac.macports.org/ticket/49305 for reminding me of that ticket. Have subscribed to that and the one referenced in there as well. Greets, Marko ___

Re: trac.macports.org is down again

I guess it might be worthwhile to collect all these issues on a dedicated wiki page: On 12 Oct 2015, at 16:46 , Daniel J. Luke wrote: >> Subversion log importer not running: https://trac.macports.org/ticket/48758 >> >> Snow Leopard builder registry corrupted: >>

Re: trac.macports.org is down again

Hi Ryan, On 12 Oct 2015, at 23:10 , Ryan Schmidt wrote: > No need for a separate wiki page. The server/hosting component in the issue > tracker already serves that purpose. > > https://trac.macports.org/query?status=!closed=server/hosting ah, yes, that’s sufficient,

Re: qtN-kde port(s)

Dear qt*-maintainers/interested, On 06 Jul 2015, at 10:00 , René J.V. Bertin rjvber...@gmail.com wrote: I think that can only be done by modifying the Qt PortGroup files so that they detect the install layout and adapt the variable definitions they serve accordingly. The cleanest approach I

Re: qtN-kde port(s)

Hi René, On 07 Jul 2015, at 23:22 , René J.V. Bertin rjvber...@gmail.com wrote: A specific file, either one installed anyway by Qt but in a location specific to qt5-kde, or something like a README or stub file that's specific to the port. ah, ok, so it would be up to you to create this

phonon for Qt5 in ticket #46552

Hi again, On 07 Jul 2015, at 23:22 , René J.V. Bertin rjvber...@gmail.com wrote: Right now I am struggling with phonon [1], since it doesn’t want to install itself with current qt5-mac on my system, but perhaps I better open a separate thread for that topic… That's simply because the

Re: How to deal with ports-filesystem violation?

On 29 Jun 2015, at 00:26 , Clemens Lang c...@macports.org wrote: In your case, since you seem to have a reason to ignore this warning, add this line to your Portfile to silence the warning. I did so, but I still get this warning: --- Warning: kf5-kdoctools installs files outside the common

Re: How to deal with ports-filesystem violation?

Hi Lawrence, On 29 Jun 2015, at 00:54 , Lawrence Velázquez lar...@macports.org wrote: Is this our Qt5? Yes, it is. :) If so, I think it would be best if we modify it so that it looks inside ${prefix}/Library also. It won't be good if all KF5 ports need to install junk into /Library. Ha,

How to deal with ports-filesystem violation?

Hi maintainers, I am having a little trouble with some new ports which I am trying to introduce anew. They need to install stuff into OSX’ system locations, specifically into - /Library/Application Support - /Library/Preferences But, of course, this is what I get when trying that: --- $

Re: How to deal with ports-filesystem violation?

Hi Clemens, On 29 Jun 2015, at 00:26 , Clemens Lang c...@macports.org wrote: - /Library/Application Support - /Library/Preferences Why do they need to do that? they do it, because Qt5’s QStandardPaths logic searches in system locations for its files, which is why it wouldn’t be able to find

Re: Shouldn't qt5 also include cmake?

Hi René, On 27 Jun 2015, at 09:36 , René J.V. Bertin rjvber...@gmail.com wrote: The {c,q}make portgroups redefine the default build system, so including either of them with the qt5 portgroup isn't appropriate ok, good to know! That’s why I am asking here. :) Thanks, Marko

Re: [137900] trunk/dports/kde

Ryan, turns out that it was a completely unintended commit to qtcurve. No idea how that could happen… Reverted in r137900. Thanks for poking me! Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

How to avoid file system violation during destrooting

Hi, I am having trouble with file system violation in https://trac.macports.org/ticket/48184 … Seems to be caused by creating file modules/qt_Attica.pri in ${prefix}/mkspecs Any ideas what can be done to avoid it? Greets, Marko

Re: How to avoid file system violation during destrooting

On 27 Jun 2015, at 03:52 , Lawrence Velázquez lar...@macports.org wrote: Patch the build system? To do what (not) exactly? Does MacPorts not allow ports to install directly into ${prefix}/mkspecs, or what is the problem here?? ___ macports-dev

Re: How to avoid file system violation during destrooting

Or does the build system install right away into the MP file system instead of into destroot? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to avoid file system violation during destrooting

On 27 Jun 2015, at 04:05 , Brandon Allbery allber...@gmail.com wrote: That is what it's complaining about, yes. Oh, ok. That means I need to find the CMake file which is responsible for this… Thanks for the pointer guys! :)___ macports-dev mailing

Shouldn't qt5 also include cmake?

Hi Marcus, I wondered whether port group “qt5” should also include port group “cmake” since it is internally making use of it anyways?! Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: [MacPorts] #47947: qt5-creator-mac @3.2.2 fails to build

Hi Andrea, On 19 Jun 2015, at 10:53 , Andrea D'Amore and.dam...@macports.org wrote: Just to put things in context you're referring to [1] but that ticket is about failing build and doesn't mention parallel building at all. Also you are not the reporter there, like you seem to imply. I didn’t

Re: [137900] trunk/dports/kde

Hi Ryan, On 27 Jun 2015, at 02:22 , Ryan Schmidt ryandes...@macports.org wrote: Any particular reason for the nonstandard 'exec sh -c cd ... ; ...', instead of the usual 'system -W ... ...”’? No. Will fix that. Note that the compilers macports-clang-2.9, macports-clang-3.0,

Re: How to avoid file system violation during destrooting

On 27 Jun 2015, at 04:21 , Joshua Root j...@macports.org wrote: I don't think that's right, the port would not successfully finish destroot if that was installing straight to ${prefix} and being stopped by sandboxing. The message in the ticket is complaining about an mtree violation.

opencv version 3 vs. 2

Hi stromnov, recently opencv was updated from version 2 to 3, which left at least 2 dependent ports in limbo [1,2] and there might be even more out there... I think this may ask for a new port opencv2, until its dependent ports can also handle version 3. Do you agree? If so, I'd suggest to take

Re: opencv version 3 vs. 2

Hi Ryan, If fixing those two ports is more complicated than just updating them to a newer version, or copying an existing patch from upstream, then yes, it would be fine to create an opencv2 port. ok, I'll wait a bit until I have feedback from the digikam developer, but I have no idea about

Re: [137817] trunk/dports/textproc

Isn't cppunit a unit-testing framework, which would only used at build or test time? Oh, yes, that slipped my attention. Shall I commit with a revbump? ___ macports-dev mailing list macports-dev@lists.macosforge.org

Create a new category named 'kf5' for KDE's KF5?

Hi devs, as the KDE Frameworks 5 (KF5) are still under heavy development, we can expect that KF5-based software will have to coexist with KDE4 for quite some time to come. I wonder now, whether these KF5 frameworks could get their own category 'kf5', or whether they should also go into

Re: [MacPorts] #47947: qt5-creator-mac @3.2.2 fails to build

Hi, I am saying the opposite! It always built fine for me in parallel, which is why I raised this issue. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Contributing to MacPorts (specifically to introduce am improved concurrent qt5-mac)

Hi René, On 14 Jun 2015, at 23:02 , René J.V. Bertin rjvber...@gmail.com wrote: Anyway, I suppose you saw I updated ticket in which we discussed my PortGroup definition. I hope you'll be able to take a look soon (= before the Portfile diff no longer applies). sorry, I can’t react fast ATM on

gpsbabel suddenly based on qt5-mac thus leaving qt4-mac-based port qlandkartegt in limbo

I just realised that updated gpsbabel [1] leaves qlandkartegt in limbo because of switching to qt5-mac: --- $ port deps gpsbabel Full Name: gpsbabel @1.5.2_0 Build Dependencies: pkgconfig Library Dependencies: qt5-mac, expat, libusb-compat, zlib $ port rdependents gpsbabel The following ports

Re: qt5-mac w/o parallel build

Hi Marcus, On 08 Jun 2015, at 02:25 , Marcus Calhoun-Lopez marcuscalhounlo...@gmail.com wrote: It should be fixed in r137268. thanks for fixing that. ... BTW, have you intentionally set - by any chance - the X-No-Archive option in your mail client? If not I can’t understand, why your reply

qt5-mac w/o parallel build

Commit r137229 [1] actually mentions in line 78: --- 78# TODO: Uncomment out for testing only. Be sure to comment out next line before commit. 79use_parallel_build no --- but still doesn’t allow for parallel build... So, seemingly, the commenting out of line 79 was not made sure at

Re: gnutar broken

Hi René, On 20 May 2015, at 10:01 , René JV Bertin rjvber...@gmail.com wrote: I simply installed bsdtar and got rid of the gnutar if I want to go this route myself, where do I find bsdtar on MacPorts? Greets, Marko ___ macports-dev mailing list

Re: gnutar broken

Hi René, On 21 May 2015, at 09:36 , René J.V. Bertin rjvber...@gmail.com wrote: I was about to say port:bsdtar but indeed, no, it's under the more evocative name of port:libarchive. Maybe an idea to rewrite the description to mention that this port doesn't only install libraries … Jesus,

gnutar broken

Hi devs, gnutar is broken since a quarter of a year by now [1]... Anyone out there who has a clue what might be going on there? Greets, Marko [1] https://trac.macports.org/ticket/47001 ___ macports-dev mailing list

Re: gnutar broken

Hi folks, On 20 May 2015, at 10:19 , Andrea D'Amore and.dam...@macports.org wrote: It works for me as well using 2.3.99 on OS X 10.10.3. only now I realise that I misinterpreted something. I thought gnutar wasn’t building at all at the moment, instead it is only that one open issue... All

Re: Bad files on buildports-lion-x86_64

David, I had this in the past with RKWard already twice!! Check what we’ve done in rkward's pre-activate phase, where we did delete the left-over files previously, but have disabled the “delete” commands ATM as we want to understand when those files got created. Mac OS Forge folks never reacted

IP traffic monitoring tools on MacPorts with different results

Hi folks, I have tested a few of MacPorts’ IP traffic monitoring tools for the console and found that bmon is my favourite - while bwm-ng and ifstat worked fine too. But I noticed that these two tools - nload - iftop gave unreasonably high transfer rates!!! Could it

Re: MacPorts' trac in Europe slower than usual

Performance has improved again. Did someone change something somewhere? Thanks in any case. Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

MacPorts' trac in Europe slower than usual

MacPorts’ trac is quite slow here in Europe since yesterday! (But it was even slower 12h ago.) Any ideas what was/is wrong? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: MacPorts' trac in Europe slower than usual

On 22 Apr 2015, at 15:57 , Henry Groen gr...@apple.com wrote: I have kicked the server, let me know if you see an improvement. no, still very slow. Perhaps it only happens for me... Marko ___ macports-dev mailing list

Re: Port variant libcaca -x11 still pulls in xorg deps...

Hi Jeremy, thanks for your helpful response. On 22 Apr 2015, at 00:20 , Jeremy Huddleston Sequoia jerem...@macports.org wrote: imlib2's configure script looks like it has a way to disable X11 support, but the resulting dylib is still linked against X11 libs. Here's a patch to get you

Re: Ports not listed as outdated

Hi Mojca, On 22 Apr 2015, at 09:00 , Mojca Miklavec mo...@macports.org wrote: MacPorts is behaving a bit weird. It doesn't report some outdated ports and as a consequence doesn't upgrade them. I need some clues about where I could look to diagnose the source of the problem. thanks so much

Failing to come up with a working -x11 variant for port gstreamer1-gst-plugins-good

Hi, I want to be able to build gstreamer without X11. Thanks to [1] I am almost there, but gstreamer1-gst-plugins-good is still failing now that I try to build ‘-x11’: --- :info:build gstid3v2mux.cc:55:10: fatal error: 'textidentificationframe.h' file not found :info:build #include

Re: Port variant libcaca -x11 still pulls in xorg deps...

Turns out that libcaca was easy, although I am not sure that https://trac.macports.org/ticket/47526 does this correctly. Well, the project builds fine at least... ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: Port variant libcaca -x11 still pulls in xorg deps...

Hi Josh, On 21 Apr 2015, at 21:43 , Joshua Root j...@macports.org wrote: The ticket summary is a bit confusing given that the patch neither adds an x11 variant nor makes it default. But the patch looks reasonable, assuming that --disable-x11 causes the removed dependencies not to be used.

Port variant libcaca -x11 still pulls in xorg deps...

Hi Jeremy, this pulls in xorg: --- $ sudo port install libcaca -x11 --- Computing dependencies for libcaca --- Dependencies to be installed: freeglut libGLU mesa xorg-dri2proto xorg-glproto xorg-libXdamage xorg-damageproto xorg-libXxf86vm xorg-xf86vidmodeproto imlib2 libid3tag --- because of

  1   2   3   4   5   6   >