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

On 1 May 2018 at 02:35, Jeremy Lavergne wrote: > 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? > > "wontfix" ? "Won't fix" sounds plain wrong for things that are real bugs or for reasonable fea

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

On 30/04/18 23:52, Rainer Müller wrote: 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 (labe

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] #56389: rrdtool @1.7.0: fix missing dependency for dejavu-fonts

> On 2018-05-01, at 07:14, MacPorts wrote: > (...) > Comment: > > If you wish to maintain the port, feel free to modify the `maintainers` > line appropriately in your patch. done.

Another tagging failure in the PR queue

Tags failed to appear again on something in the PR queue. https://github.com/macports/macports-ports/pull/1697 -- Perry E. Metzgerpmetz...@macports.org

Re: Why didn't this PR get labeled?

On Mon, Apr 30, 2018 at 06:09:09PM +0200, Rainer Müller wrote: 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?

trac rrdtool

searching for open tickets on rrdtool, I don't understand some things. page 2: https://trac.macports.org/search?changeset=on&milestone=on&portsummarysearch=on&ticket=on&wiki=on&q=rrdtool&page=2&noquickjum

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: Request for discussion: lowering the backlog of old Trac tickets.

On Tue, 1 May 2018 00:51:27 +0200 Rainer Müller wrote: > 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

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

On Mon, 30 Apr 2018 18:26:32 -0500 Ryan Schmidt wrote: > 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/6b1fe110a0a558d323ebc8b6

Re: Why didn't this PR get labeled?

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, just to nail it. Perry -- Perry E. Metzger

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: [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 10:50, Rainer Müller wrote: > This should be reported to GitHub support. I would consider it a bug at > their end if they send out WebHooks but do not actually provide the > referenced data via the API yet. I agree, Github should be made aware of this problem. Cheers, K. C. --

Re: [MacPorts] #56389: rrdtool @1.7.0: fix missing dependency for dejavu-fonts

> On 2018-05-01, at 22:56, MacPorts wrote: > (...) > Tidy other deps based on port-depcheck.sh analysis - what is that? - can I do that myself?

Re: [MacPorts] #56389: rrdtool @1.7.0: fix missing dependency for dejavu-fonts

> On May 1, 2018, at 6:50 PM, macpo...@parvis.nl wrote: > > >> On 2018-05-01, at 22:56, MacPorts wrote: >> (...) >> Tidy other deps based on port-depcheck.sh analysis > > - what is that? > - can I do that myself? > Various MacPorts maintainers have developed little tools that ease some task o

Re: [macports-ports] branch master updated: root6: update default compiler variants

On May 1, 2018, at 12:52, Chris Jones wrote: > +# Enable variants that only seem to work when not using macports clang... > +if [expr ![string match macports-clang-* ${configure.compiler}] ] { > +default_variants-append +veccore +davix > +} You don't really need [expr] here, do you?