Re: Trac & Subversion available again

On 2016-10-23 14:48 , Jeremy Huddleston Sequoia wrote: On Oct 21, 2016, at 18:16, Clemens Lang wrote: Hello MacPorts users and developers, On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: Due to the current SVN and Trac downtime, we are also discussing to

Re: Trac & Subversion available again

> On Oct 22, 2016, at 22:48, Jeremy Huddleston Sequoia > wrote: > > >> On Oct 21, 2016, at 18:16, Clemens Lang wrote: >> >> Hello MacPorts users and developers, >> >>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: >>> Due to the

Re: Trac & Subversion available again

> On Oct 21, 2016, at 18:16, Clemens Lang wrote: > > Hello MacPorts users and developers, > > On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: >> Due to the current SVN and Trac downtime, we are also discussing to >> make the move of Trac sooner if that helps us

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

> On Oct 22, 2016, at 8:08 PM, Marko Käning wrote: > > 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 >

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

Re: Moving to GitHub: Status Update, Action Required

> On Oct 22, 2016, at 9:40 AM, Marko Käning wrote: > >> On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote: >> >> as well as the "hub" command line program in the "hub" port. > > Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on

Re: Autotools help

On Oct 22, 2016, at 10:35, Craig Treleaven wrote: > > I’m working on an update to Lirc and the build system has changed to > Autotools--which I know very little about. > > It seems that Lirc will now opportunistically link with Alsa and there is no > configure flag to

Re: New Trac Uses Session Cookies

On 2016-10-22 18:16, Zero King wrote: > Please provide an option to keep the cookies after browser exits. Thanks for noticing. I raised the expiry date of cookies to 30 days. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org

New Trac Uses Session Cookies

Please provide an option to keep the cookies after browser exits. -- Best regards, Zero King ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

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: Autotools help

> On Oct 22, 2016, at 11:35 AM, Craig Treleaven wrote: > > Hi: > > I’m working on an update to Lirc and the build system has changed to > Autotools--which I know very little about. > > It seems that Lirc will now opportunistically link with Alsa Argh, nevermind. I

Autotools help

Hi: I’m working on an update to Lirc and the build system has changed to Autotools--which I know very little about. It seems that Lirc will now opportunistically link with Alsa and there is no configure flag to disable such behaviour. I want to make Alsa support a non-default variant. Is my

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 Oct 22, 2016, at 7:49 AM, Marko Käning wrote: > > 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

Re: SVN committing not possible ATM?

On 2016-10-22 14:44, Marko Käning wrote: > I just now couldn’t commit to the SVN server: > > --- > $ svn ci -m "gwenhywfar4-devel: update to 4.16.0beta" > SendingPortfile > Transmitting file data .svn: E175002: Commit failed (details follow): > svn: E175002: Unexpected server error 500

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

On 2016-10-22 23:31 , Marko Käning wrote: 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

Re: Moving to GitHub: Status Update, Action Required

Hi, On Sat, Oct 22, 2016 at 02:31:32PM +0200, Marko Käning wrote: > 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 actually be included

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