Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread René J . V . Bertin
Hi, This is a poll about MacPorts's bug reporting engine, Trac. If you don't (plan to) use that thing, just delete this message. Trac never sent notifications when you added or deleted (replaced) an attachment, but a recent introduced that as a new feature. I find this mostly useless and even

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread Mojca Miklavec
On 3 November 2016 at 09:30, René J.V. Bertin wrote: > > 1- Do you agree there is no need for (this many) notifications concerning > changes to attachments (= you never missed it)? No. I have always been annoyed by the fact that some users (me included) uploaded an attachment and then I had to

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread Clemens Lang
Hi, - On 3 Nov, 2016, at 09:30, René J.V. Bertin rjvber...@gmail.com wrote: > I've asked the administrators if something can be done about it. Not to insult > anyone, but to put it bluntly, it does seem they cannot be bothered by > something they consider an upstream problem namely that Trac

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread Davide Liessi
I fully agree with Mojca: 2016-11-03 9:46 GMT+01:00 Mojca Miklavec : > On 3 November 2016 at 09:30, René J.V. Bertin wrote: >> >> 1- Do you agree there is no need for (this many) notifications concerning >> changes to attachments (= you never missed it)? > > No. I have always

Re: 10.6.8 and ffmpeg

2016-11-03 Thread René J . V . Bertin
Mojca Miklavec wrote: > I'm pretty sure one can make it build without 10.7 SDK, it will just > take quite a bit of work to do so. Perhaps you know if there is an > elegant way to actually patch the code in a way that would be > acceptable for upstream in case we manage to find a sufficient set of

Re: GitHub migration complete

2016-11-03 Thread René J . V . Bertin
A question that came up due to another ticket: last time I checked, github's issue tracker wasn't available for the ports repo. I presume that's on purpose, but why? Even if "we already have a bug tracker", why would it make life harder and not easier at least for some things? I must admit

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread Ralph Seichter
On 03.11.2016 09:30, René J.V. Bertin wrote: > For active tickets I spend too much time weeding through and deleting > emails devoid of interest. Have you tried using Sieve or your MUA's filter options to get rid of e-mails you personally don't consider of interest? Notifications are a major

Re: GitHub migration complete

2016-11-03 Thread Clemens Lang
Hi, - On 3 Nov, 2016, at 10:57, René J.V. Bertin rjvber...@gmail.com wrote: > last time I checked, github's issue tracker wasn't available for the ports > repo. > I presume that's on purpose, but why? Even if "we already have a bug tracker", > why would it make life harder and not easier at

Re: GitHub migration complete

2016-11-03 Thread René J . V . Bertin
On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > It's something we all have to deal with. Presumably, we will all learn over > time. Presumably. Question is, who has to learn what, and how reasonable is it to require that of them when the general consensus usually is that "users

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread Rainer Müller
On 2016-11-03 09:30, René J.V. Bertin wrote: > Trac never sent notifications when you added or deleted (replaced) an > attachment, but a recent introduced that as a new feature. I find > this mostly useless and even annoying because when you update > (replace, delete) an attachment there will be 2

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

2016-11-03 Thread René J . V . Bertin
On Thursday November 03 2016 12:46:18 Rainer Müller wrote: > By now I received more mails from you with complaints about this than > actual "duplicate" Trac notifications for attachment replacements... You're welcome to filter out my emails, but you certainly won't receive any notifications

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Murray Eisenberg
After the re-install script (from the migration instructions) got into an infinite loop, I started to reinstall ports manually, starting with the first one on my “myports.txt” list: analitza The failure came when installing that failed during the automatic installation of dependencies, in

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Ken Cunningham
Murray, that is very specific now I have that port installed. $ port -v installed gmp The following ports are currently installed: gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64' I just rebuilt it right now from source without trouble. so it's something on your machine. Jerermy

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Murray Eisenberg
I looked at the tickets #46589, 51971, and 52326 about gmp, and I don’t see mention of availability.h there. I thought the issue with availability.h concerned gcc48 and was resolved somehow (with newer Xcode? with patched port?) some time ago. The logs seem to indicate that the current issue

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Ken Cunningham
Look at this ticket comment 3 pthreads is not picking up the definition from Availability.h for some reason. Ken On 2016-11-03, at 7:26 AM, Murray Eisenberg wrote: > I looked at the tickets #46589, 51971, and 52326 about gmp, and I don’t see > mention

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Murray Eisenberg
OK, and in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/Availability.h I find at lines 341-355: /* for use marking APIs unavailable for swift */ #if defined(__has_feature) #if __has_feature(attribute_availability_swift)

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Ken Cunningham
Hi Murray, Just to tell you I have not touched a thing on this Sierra install, and it works fine for me. (Did you have a beta installed? Can you think of any reason why your SDK might not be stock?) It takes 5 minutes to reinstall Xcode and the command line tools. That would be step 1 for

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Murray Eisenberg
Looking more carefull, I see that the problematic "if defined(__has_feature)” in Availability discussed in ticket #48471 is different from the same phrase in the current Availability.h. Namely, the new one has the whole new section, shown below, headed with “/* for use marking APIs

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Ken Cunningham
>> >> If so, the workaround for that was to make a local copy of Availability.h in >> /opt/local/include and edit it there. >> I'd still reinstall Xcode and the command line tools -- but you don't have a rogue Availability.h sitting /opt/local/include do you? If so, that's your trouble. K

Re: GitHub migration complete

2016-11-03 Thread Michael
On 2016-11-03, at 4:44 AM, René J.V. Bertin wrote: > On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > >> It's something we all have to deal with. Presumably, we will all learn over >> time. > > Presumably. Question is, who has to learn what, and how reasonable

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Murray Eisenberg
Problem with re-installing my ports after migration from El Capitan to Sierra is SOLVED — at least with respect to installing gmp (upon which quite a few other ports depend)! That ‘__SWIFT_UNAVAILABLE_MSG” error, which ultimately points back to Availability.h was the clue indeed: As a

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

2016-11-03 Thread Ryan Schmidt
> On Nov 3, 2016, at 9:10 AM, Ken Cunningham > wrote: > > (Why is this not coming to you as a prebuilt binary from the buldbots, I > wonder?) The gmp portfile explains why this is so: # Prevent precompiled binaries. # See #41614. # might not be needed if we