Re: Gsoc 18 Project | Collect build statistics

On 30 April 2018 at 02:22, Vishnu wrote: > Hi > > After hours of fixing error in heroku and my ubuntu . > Finally got to run the so far app. Yay! That's great since it will be much easier for the whole community to test the app much more quickly. Now, it would be great to pick some name for the r

Re: Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

Dear Clemens, On 29 April 2018 at 18:00, Clemens Lang wrote: > On Sun, Apr 29, 2018 at 09:34:10AM +0200, Mojca Miklavec wrote: >> Hi, >> >> This looks pretty strange to me: >> >> ---> Fetching distfiles for pymol >> Executing: cd "/path/to/pymol/work" && /usr/bin/svn --non-interactive >> --trust

Why didn't this PR get labeled?

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? Perry -- Perry E. Metzgerpmetz...@macports.org

Seeing closed tickets on Trac tickets page...

On: https://trac.macports.org/wiki/Tickets I see a list of tickets assigned to me, but it includes closed tickets. When I edit the Wiki page, it shows me the query is: TicketQuery(status=!closed,reporter=$USER,or,owner=$USER,col=id|summary|component|port|reporter|owner|time|changetime,order=chang

Re: Seeing closed tickets on Trac tickets page...

On Mon, Apr 30, 2018 at 10:18:51AM -0400, Perry E. Metzger wrote: On: https://trac.macports.org/wiki/Tickets I see a list of tickets assigned to me, but it includes closed tickets. When I edit the Wiki page, it shows me the query is: TicketQuery(status=!closed,reporter=$USER,or,owner=$USER,col=

Re: Seeing closed tickets on Trac tickets page...

On Mon, 30 Apr 2018 14:30:51 + Zero King wrote: > On Mon, Apr 30, 2018 at 10:18:51AM -0400, Perry E. Metzger wrote: > >On: > >https://trac.macports.org/wiki/Tickets > > > >I see a list of tickets assigned to me, but it includes closed > >tickets. When I edit the Wiki page, it shows me the quer

Re: Seeing closed tickets on Trac tickets page...

On Mon, 30 Apr 2018 10:40:41 -0400 "Perry E. Metzger" wrote: > On Mon, 30 Apr 2018 14:30:51 + Zero King > > The `or` has lower precedence. So use > > TicketQuery(status=!closed,reporter=$USER,or,status=!closed,owner=$USER,col=id|summary|component|port|reporter|owner|time|changetime,order=chan

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

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

So I started looking over the Trac tickets a few days ago. There was a really scary number open, over 2400. A couple of days of looking got it down without much trouble to 2393. I suspect lowering the number by about 100-200 a month should be doable with a very small but very steady effort from a

Re: Why didn't this PR get labeled?

Hi Zero, On Mon, Apr 30, 2018 at 09:49:10AM -0400, 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? Can you take a look? >F

Re: [macports-ports] branch master updated: quassel: Update to 0.12.5, security

Hi, On Fri, Apr 27, 2018 at 01:50:34PM -0500, Ryan Schmidt wrote: > On Apr 27, 2018, at 08:18, Clemens Lang wrote: > > +github.setupquassel quassel f29f8527d44648d6c2c05054add559c977f80153 > > +version 0.12.5 > > Why not: > > github.setupquassel quassel 0.12.5 > > ? That tag loo

Re: Gsoc 18 Project | Collect build statistics

Hey Repository names: MacPorts-features? Macportsinfo? Or just simple gsoc18? I will look into the feedback. Also i am currently using create. And also in the long term. Parser would be run only once in forever or say a year. And before running the original db must be cleared. And then obviou

Re: [MacPorts] Tickets modified

On Mon, 30 Apr 2018 17:50:51 +0200 Rainer Müller wrote: > The report uses "order=time" (Created), but the name suggests it > would be supposed to use "order=changetime" (Modified). I just > corrected that. Thank you! -- Perry E. Metzgerpmetz...@macports.org

Re: Gsoc 18 Project | Collect build statistics

On Mon, Apr 30, 2018 at 10:06 PM, Vishnu wrote: > Hey > > Repository names: > MacPorts-features? > Macportsinfo? > Or just simple > gsoc18? > > I was thinking about macports-portstatistics or macports-portstats. > > I will look into the feedback. > Also i am currently using create. > > And also

Re: [macports-ports] branch master updated: irrlicht: fix build on case-sensitive file systems

Hi, On Sat, Dec 09, 2017 at 09:12:10AM -0800, Ken Cunningham wrote: will put in a reminder to do so thanks, K Here goes a reminder, the base bug was fixed in MacPorts 2.4.3. On Dec 9, 2017, at 8:50 AM, Ryan Schmidt wrote: On Dec 9, 2017, at 10:07, Ryan Schmidt wrote: I tried it myself a

Re: Gsoc 18 Project | Collect build statistics

On 2018-5-1 02:47 , Jackson Isaac wrote: > On Mon, Apr 30, 2018 at 10:06 PM, Vishnu wrote: >> Hey >> >> Repository names: >> MacPorts-features? >> Macportsinfo? >> Or just simple >> gsoc18? >> >> > > I was thinking about macports-portstatistics or macports-portstats. This is going to cover more

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: Gsoc 18 Project | Collect build statistics

On 30 April 2018 at 18:47, Jackson Isaac wrote: > On Mon, Apr 30, 2018 at 10:06 PM, Vishnu wrote: >> Hey >> >> Repository names: >> MacPorts-features? >> Macportsinfo? >> Or just simple >> gsoc18? No, gsoc18 is a bad name since the idea is to use the project afterwards as well and I don't like to

Force Mirror on Buildbot

Hi, I'd like to mirror unar's distfile for backup, but "it has already been built and uploaded" so mirror was skipped if I force build the port on a portwatcher and I can't force a mirror job directly. -- Zero smime.p7s Description: S/MIME cryptographic signature

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

> Anyway, that was what I wrote. I'd be interested in hearing other > people's thoughts. In short, I would agree with you. MPs current trac is bogged down with too many open tickets such that it is arguably not 100% fit for purpose. I certainly have preferred to largely ignore it as much as I c

Re: Force Mirror on Buildbot

On Apr 30, 2018, at 13:09, Zero King wrote: > I'd like to mirror unar's distfile for backup, but "it has already been > built and uploaded" so mirror was skipped if I force build the port on a > portwatcher and I can't force a mirror job directly. Yes, we need to allow forcing the mirroring job

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

At one point about two years ago I also suggested closing all tickets more than about six months old, for the exact same reasons. So I'm on board. There _is_ a vast storehouse of practical information in MacPorts trac. Whenever I get a build error I go there first, often before Google. But anc

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

Dear Perry, On 30 April 2018 at 18:16, Perry E. Metzger wrote: > So I started looking over the Trac tickets a few days ago. Thanks a lot for taking the initiative for this. Below are some of my thoughts. One thing I really dislike about many projects is that one sometimes spends quite a while t

Re: [macports-ports] branch master updated: duck: New port, version 6.4.6.27773

On Apr 30, 2018, at 15:12, Jackson Isaac wrote: > Jackson Isaac (JacksonIsaac) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5624f07530e7dc202fd9d57b378232dd3fa4b1bf > > The following commit(s) were added to refs/heads/m

Re: [macports-ports] branch master updated: qtcurve: update to 1.9.0

On Apr 30, 2018, at 10:06, 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/6b1fe110a0a558d323ebc8b62ca8fb9938d824c1 > > The following commit(s) were added to refs/head

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

"wontfix" ? On 04/30/2018 07:01 PM, Mojca Miklavec wrote: > tickets that we cannot address, but don't explicitly close either. > Something like a "stale" state?

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: Why didn't this PR get labeled?

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 why? Same here: https://github.com/macports/macports-ports

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

On Apr 30, 2018, at 20: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. Files in base have the copyright header. Portgroups used to be in base

Re: [macports-ports] branch master updated: esmf: fix build with gcc5 or earlier

On Apr 28, 2018, at 01:10, Takeshi Enomoto wrote: > Takeshi Enomoto (tenomoto) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/218d3fd276c65f9e22e19f7ec3ef686322e6a156 > > The following commit(s) were added to refs/heads/

Re: [macports-ports] branch master updated: py-pyslides: Update to 0.9.23. Fix dependencies and master_sites.

On Apr 30, 2018, at 23:37, David Strubbe wrote: > David Strubbe (dstrubbe) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/78bce97dd6c1368229e320435a4dbf20c4fd4aed > > The following commit(s) were added to refs/heads/mast

Re: [macports-ports] branch master updated: py-pybtex: Update to 0.21, fix master_sites.

On Apr 30, 2018, at 23:17, David Strubbe wrote: > David Strubbe (dstrubbe) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/16798c052e98961df280c859023ed49a9ab0cab5 > > The following commit(s) were added to refs/heads/mast

Re: [macports-ports] branch master updated: py-pybtex: Update to 0.21, fix master_sites.

pypi:p/pybtex did not work for me. "port fetch" failed. Does it really work for you? On Mon, Apr 30, 2018 at 10:00 PM, Ryan Schmidt wrote: > > On Apr 30, 2018, at 23:17, David Strubbe wrote: > > > David Strubbe (dstrubbe) pushed a commit to branch master > > in repository macports-ports. > > > >

Re: [macports-ports] branch master updated: py-pybtex: Update to 0.21, fix master_sites.

On 2018-5-1 15:22 , David Strubbe wrote: > pypi:p/pybtex did not work for me. "port fetch" failed. Does it really > work for you? Works here: % sudo port -v checksum py27-pybtex Password: ---> Fetching distfiles for py27-pybtex ---> pybtex-0.21.tar.gz does not exist in /opt/local/var/macports/d

Re: [macports-ports] branch master updated: py-pybtex: Update to 0.21, fix master_sites.

It timed out, on several tries. Maybe this was some temporary outage or local problem here. Anyway, I'll put it back. On Mon, Apr 30, 2018 at 10:44 PM, Joshua Root wrote: > On 2018-5-1 15:22 , David Strubbe wrote: > > pypi:p/pybtex did not work for me. "port fetch" failed. Does it really > > wor