Re: 10.6.8 and ffmpeg

On 2 November 2016 at 09:46, Davide Liessi wrote: > 2016-10-30 15:38 GMT+01:00 Ryan Schmidt: >> copying the 10.7 SDK into /Developer/SDKs is the simplest solution. > > How can I get a copy of the 10.7 SDK? > I have only the 10.5 and 10.6 SDKs on my machine. I didn't test this, but I guess that you

Re: 10.6.8 and ffmpeg

Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 use the 10.6 SDK effectively? > On Oct 31, 2016, at 20:44, Ken Cunningham > wrote: > >> >> I’d be happy to test the minimum requirements to build it, if Richard >> doesn’t beat me to it :> >> >> Get back to you in a

Re: 10.6.8 and ffmpeg

2016-10-30 15:38 GMT+01:00 Ryan Schmidt : > copying the 10.7 SDK into /Developer/SDKs is the simplest solution. How can I get a copy of the 10.7 SDK? I have only the 10.5 and 10.6 SDKs on my machine. ___ macports-users mailing list macports-users@lists.m

Fwd: Re: Error in updating macports

-- Forwarded message -- From: "Sumanth" Date: 01-Nov-2016 12:36 PM Subject: Re: Error in updating macports To: "Ryan Schmidt" Cc: I've tried using different networks. With another network I'm got the following error message. $ port -v selfupdate

Re: 10.6.8 and ffmpeg

OK! Just submitted my first git pull — please be gentle — I think I did it correctly, but …. Ken > On Oct 31, 2016, at 8:56 PM, Ryan Schmidt wrote: > > On Oct 31, 2016, at 22:44, Ken Cunningham > wrote: >> >> I have no clue how to submit a portfile *.diff any longer (is that a sigh of >

Re: 10.6.8 and ffmpeg

On Oct 31, 2016, at 22:44, Ken Cunningham wrote: > > I have no clue how to submit a portfile *.diff any longer (is that a sigh of > relief I hear?? :> ) , but hopefully this helps. Thanks! The new way is to submit a pull request on GitHub, but I think we can also still accept patch files atta

Re: 10.6.8 and ffmpeg

> > I’d be happy to test the minimum requirements to build it, if Richard doesn’t > beat me to it :> > > Get back to you in a day or two with the info. > Hello friends, ran some tests with a spanking new installation of 10.6.8 and macports 2.3.4 with nothing installed to build libsdl2 on 1

Re: GitHub migration complete

> On Oct 31, 2016, at 1:16 PM, Thibaut Paumard wrote: > > Le 31/10/2016 à 17:23, Lawrence Velázquez a écrit : >>> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote: >>> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit : > On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: > >

Re: Marking a port as broken

On Mon, Oct 31, 2016 at 1:34 PM, Bradley Giesbrecht wrote: > Test in pre-fetch and give ui_error. > > port cat pinentry-mac | grep -A6 pre-fetch Perfect! Thanks! Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org https://l

Re: Marking a port as broken

Test in pre-fetch and give ui_error. port cat pinentry-mac | grep -A6 pre-fetch Regards, Bradley Giesbrecht (pixilla) > On Oct 31, 2016, at 11:26 AM, Adam Mercer wrote: > > Hi > > I have some ports that are out of date due to the newer versions no > longer building on macOS and the latest

Re: GitHub migration complete

> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote: > >> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit : >>> On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: >>> >>> This issue only affects the very small percentage of the MacPorts user >>> population (including developers and mainta

Re: GitHub migration complete

On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: > This issue only affects the very small percentage of the MacPorts user > population (including developers and maintainers) that clones the git > repository. Most users will use the rsync server, on which we do generate > portindexes for e

Re: 10.6.8 and ffmpeg

On 10/31/16 8:05 AM, Gustaf Neumann wrote: > Am 30.10.16 um 21:31 schrieb David Evans: >> Agreed, the problem here is with libsdl2. We need to understand what the >> problem is on >> 10.6 at least and either help upstream to fix it or fix it ourselves. If >> all that fails >> then maybe upstrea

Re: 10.6.8 and ffmpeg

Am 30.10.16 um 21:31 schrieb David Evans: Agreed, the problem here is with libsdl2. We need to understand what the problem is on 10.6 at least and either help upstream to fix it or fix it ourselves. If all that fails then maybe upstream needs to revise they're thinking on macOS compatibility.

Re: GitHub migration complete

> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin wrote: > > Clemens Lang wrote: > >> If your question is not yet answered, ask on the mailing lists so it can >> be added. > > I may have overlooked this, but does github have any provisions that would > allow > the PortIndex files to be genera

Re: 10.6.8 and ffmpeg

On 2016-10-31, at 2:28 AM, René J. V. Bertin wrote: > > Probably an open door, possibly a forbidden one: it may be relevant here to > block concerned ports at the latest supported version for legacy platforms? Although I think not needed for libsdl2 (which builds and works without issue on 10

Re: GitHub migration complete

time operation. hardly worth worrying about. Additionally, git does not preserve timestamps from the repository on checkout, so you might actually end up re-generating the index locally anyway. I think that wouldn't (or shouldn't) happen as the timestamp would be newer. And of

Re: GitHub migration complete

the repository on >checkout, so you might actually end up re-generating the index locally >anyway. I think that wouldn't (or shouldn't) happen as the timestamp would be newer. And of course the auto-regeneration could be deactivated if the server always

Re: GitHub migration complete

into different files. Additionally, git does not preserve timestamps from the repository on checkout, so you might actually end up re-generating the index locally anyway. After the initial checkout, when the first time generation of the index does take a short while, subsequent updates are from my

Re: GitHub migration complete

. Additionally, git does not preserve timestamps from the repository on checkout, so you might actually end up re-generating the index locally anyway. -- Clemens ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosfo

Re: 10.6.8 and ffmpeg

David Evans wrote: > However, sdl/sdl2 provides the only audio/video outdev that we support in > MacPorts which means that if you have to have one or the other. Without an > outdev, ffplay will not be configured/built and you'll have no direct way to > play audio/video with ffmpeg. It's been too

Re: GitHub migration complete

Clemens Lang wrote: > If your question is not yet answered, ask on the mailing lists so it can > be added. I may have overlooked this, but does github have any provisions that would allow the PortIndex files to be generated on the server and served with the actual repo contents? That would pr

Re: GitHub migration complete

> On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > Our Subversion repository has been split into several repositories on > GitHub. Please note that Ryan ran the svn2git conversion several times this weekend, so any clones made previously will have nothing in common with the final repositorie

Re: GitHub migration complete

> On Oct 30, 2016, at 10:28 PM, Carlo Tambuatco wrote: > > Is that mailto link macports-users@lists.macosforge.org in the signature > still valid…? Yes, our previous mailing lists have not moved yet. And even when they do, the old addresses will remain valid.

Re: GitHub migration complete

Is that mailto link macports-users@lists.macosforge.org in the signature still valid…? Just curious… > On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > Good day MacPorts developers and users, > > We are pleased to announce that MacPorts has

Re: 10.6.8 and ffmpeg

Oh — I see that there’s a lot of build info in docs/ README-macosx.md in there it says you need minimum Xcode 4.6 and the 10.7 SDK (maybe that’s why macports-clang-3.7 worked for me?) and a lot more info that I didn’t read fully through. Ken > On Oct 30, 2016, at 2:28 PM, Ken Cunningha

Re: 10.6.8 and ffmpeg

> > Agreed, the problem here is with libsdl2. We need to understand what the > problem is on > 10.6 at least and either help upstream to fix it or fix it ourselves. Dave, I may not be seeing the entire picture (often happens!), but I don’t think there is actually a problem on 10.6. It uses

Re: 10.6.8 and ffmpeg

On 10/30/16 1:13 AM, Davide Liessi wrote: > 2016-10-30 1:23 GMT+02:00 Ryan Schmidt : >> If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained >> from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be >> happy if we could come up with an official way to s

Re: 10.6.8 and ffmpeg

> On Oct 30, 2016, at 10:06 AM, Ken Cunningham > wrote: > >> I can do that on the buildbot machines, and we can write the libsdl2 >> portfile so that it uses that SDK if available and instructs the user how to >> download and install it if it's not yet there. > > > The portfile is already w

Re: 10.6.8 and ffmpeg

> I can do that on the buildbot machines, and we can write the libsdl2 > portfile so that it uses that SDK if available and instructs the user how to > download and install it if it's not yet there. The portfile is already written like that. Also, see:

Re: 10.6.8 and ffmpeg

> On Oct 30, 2016, at 3:13 AM, Davide Liessi wrote: > > 2016-10-30 1:23 GMT+02:00 Ryan Schmidt : >> If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained >> from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be >> happy if we could come up with an of

Re: 10.6.8 and ffmpeg

2016-10-30 1:23 GMT+02:00 Ryan Schmidt : > If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained > from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be > happy if we could come up with an official way to support that, and then we > could do that on th

Re: 10.6.8 and ffmpeg

On 10/29/16 4:23 PM, Ryan Schmidt wrote: > >> On Oct 29, 2016, at 5:32 PM, David Evans wrote: >> >> On 10/28/16 9:58 PM, Richard L. Hamilton wrote: >>> Am I right in thinking that ffmpeg now requires libsdl2 while it >>> previously required libsdl? That causes ffmpeg to fail on 10.6.x, because

Re: 10.6.8 and ffmpeg

> On Oct 29, 2016, at 16:23, Ryan Schmidt wrote: > > >> On Oct 29, 2016, at 5:32 PM, David Evans wrote: >> >> On 10/28/16 9:58 PM, Richard L. Hamilton wrote: >>> Am I right in thinking that ffmpeg now requires libsdl2 while it >>> previously required libsdl? That causes ffmpeg to fail on 1

Re: 10.6.8 and ffmpeg

> > If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained > from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be > happy if we could come up with an official way to support that, and then we > could do that on the buildbot, which would cover a lot of

Re: 10.6.8 and ffmpeg

> On Oct 29, 2016, at 5:32 PM, David Evans wrote: > > On 10/28/16 9:58 PM, Richard L. Hamilton wrote: >> Am I right in thinking that ffmpeg now requires libsdl2 while it previously >> required libsdl? That causes ffmpeg to fail on 10.6.x, because libsdl2 >> fails: >> >> Error: org.macports.

Re: 10.6.8 and ffmpeg

On 10/28/16 9:58 PM, Richard L. Hamilton wrote: > Am I right in thinking that ffmpeg now requires libsdl2 while it previously > required libsdl? That causes ffmpeg to fail on 10.6.x, because libsdl2 fails: > > Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 > requires OS

Re: Moving to GitHub: Status Update, Action Required

On 10/29/16 7:19 AM, Clemens Lang wrote: > On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote: >> Considering that this is a significant event, I'd appreciate it (and >> others might as well) if a specific date & time, expressed in UTC, >> could be published today for the disabling of subv

Re: 10.6.8 and ffmpeg

Hi Richard You have a lot of Xcode versions installed! Keeping them all straight must be a bit of a mind-bender. perhaps select the most modern one (Xcode 4.2) and put the macOSX10.7.sdk in there? > ld: library not found for -lcrt1.10.6.o that's a bit weird. that's a basic library. In the 'f

Re: 10.6.8 and ffmpeg

I know -- I'm sorry for stepping out there and just blurting it like that. I'm just trying to help Richard 'get it done'. Also - I upgraded libsdl to the new 2.0.5 version here -- perhaps i should put up a diff for JMR to use? Best, Ken $ port -v installed | grep ffmpeg ffmpeg @3.1.4_0+gpl

Re: Moving to GitHub: Status Update, Action Required

On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote: > Considering that this is a significant event, I'd appreciate it (and > others might as well) if a specific date & time, expressed in UTC, > could be published today for the disabling of subversion write access. We'll try to keep write

Re: 10.6.8 and ffmpeg

> On Oct 29, 2016, at 12:05 AM, Ken Cunningham > wrote: > > libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 > SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk That is not a procedure we have ever recommended users do before. I know that using the 10.12 SDK

Re: 10.6.8 and ffmpeg

Thanks - closer, but must be more to it than that: h-3.2# ls -ld /Dev* lrwxr-xr-x 1 root admin 16 Aug 23 20:42 /Developer -> /Developer-3.2.6 drwxrwxr-x@ 20 root admin 680 Nov 16 2010 /Developer-3.2.2 drwxrwxr-x@ 16 root admin 544 Aug 23 19:50 /Developer-3.2.6 drwxrwxr-x 14 root admin

Re: 10.6.8 and ffmpeg

libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk Ken On 2016-10-28, at 9:58 PM, Richard L. Hamilton wrote: > Am I right in thinking that ffmpeg now requires libsdl2 while it previously > required libsdl? Tha

Re: Error installing gnuplot/aquaterm

> On 29 Oct. 2016, at 3:00 am, macports-users-requ...@lists.macosforge.org > wrote: > >> I am sorry if this is a silly question, but I am trying to install gnuplot >> (I am running Mac OS Sierra, recently updated and performed the MacPorts >> migration) and am getting the error shown below. Aqu

Re: command line tools for Xcode 8.1?

> On Oct 28, 2016, at 3:34 PM, Murray Eisenberg > wrote: > > Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. > > Release notes for Xcode 8.1 say: > > Known Issues > • There are no Command Line Tools (OS X 10.11) for Xcode 8.1. > Xcode 8.1 contains SDKs

Re: command line tools for Xcode 8.1?

On Fri, Oct 28, 2016 at 3:34 PM, Murray Eisenberg wrote: > Known Issues > >- There are no Command Line Tools (OS X 10.11) for Xcode 8.1. Xcode >8.1 contains SDKs that are incompatible with earlier toolchains. Developers >who want to make use of the Xcode 8 SDKs from the command line m

Re: Moving to GitHub: Status Update, Action Required

On 10/28/16 7:18 AM, Rainer Müller wrote: > On 2016-10-28 16:02, Craig Treleaven wrote: >>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >>> ... >>> Migration Timeline >>> == >>> The switch to Git will happen on the weekend of October 29th/30th. ... >> >> Is this still on track

Re: zenmap issues

On Oct 28, 2016, at 9:43 AM, William Woods wrote: > >> On Oct 28, 2016, at 9:23 AM, Ryan Schmidt wrote: >> >> >>> On Oct 28, 2016, at 6:18 AM, William Woods wrote: >>> >>> So, I installed nap +zenmap, it installed fine, but: >>> >>> >>> >>> bash-4.4$ which zenmap >>> /opt/local/bin/zenma

Re: zenmap issues

OK sure, but any idea of when will be fixed to work normally ? > On Oct 28, 2016, at 9:23 AM, Ryan Schmidt wrote: > > >> On Oct 28, 2016, at 6:18 AM, William Woods wrote: >> >> So, I installed nap +zenmap, it installed fine, but: >> >> >> >> bash-4.4$ which zenmap >> /opt/local/bin/zenmap

Re: Error installing gnuplot/aquaterm

On Oct 28, 2016, at 4:36 AM, Mojca Miklavec wrote: > In that case I would suggest you to run "sudo port deactivate active", > then "rm -rf /Applications/MacPorts" and potentially clean up a few > more places (I have no clue which ones). Fortunately, it's documented in the Guide: https://guide.ma

Re: zenmap issues

> On Oct 28, 2016, at 6:18 AM, William Woods wrote: > > So, I installed nap +zenmap, it installed fine, but: > > > > bash-4.4$ which zenmap > /opt/local/bin/zenmap > bash-4.4$ sudo zenmap > Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. > I checked in these direct

Re: Moving to GitHub: Status Update, Action Required

On 2016-10-28 16:02, Craig Treleaven wrote: >> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >> ... >> Migration Timeline >> == >> The switch to Git will happen on the weekend of October 29th/30th. ... > > Is this still on track? Yes, expect Subversion to go read-only this wee

Re: Moving to GitHub: Status Update, Action Required

> On Oct 28, 2016, at 9:02 AM, Craig Treleaven wrote: > >> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >> ... >> Migration Timeline >> == >> The switch to Git will happen on the weekend of October 29th/30th. ... > > Is this still on track? Yes. _

Re: trouble building mtr 0.87 on snow leopard. portfile patched?

> On Oct 28, 2016, at 5:03 AM, Peter Hancock wrote: > > On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. > The trouble, according to the log, is that IPPROTO_SCTP isn't defined. The > failing compile is: > > :info:build /usr/bin/gcc-4.2 -DHAVE_CONFIG_H -I. -I/opt/local/incl

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: > ... > Migration Timeline > == > The switch to Git will happen on the weekend of October 29th/30th. ... Is this still on track? Craig ___ macports-users mailing list macports-users@lis

Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...

On 28/10/16 14:08, Peter Hancock wrote: On 28/10/2016 13:10, Chris Jones wrote: On 28/10/2016 11:03, Peter Hancock wrote: On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/inclu

Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...

On 28/10/16 12:45, Peter Hancock wrote: On 28/10/2016 11:03, Peter Hancock wrote: On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/include/netinet/in.h and give IPPROTO_SCTP the

Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...

On 28/10/2016 11:03, Peter Hancock wrote: > On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. > The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/include/netinet/in.h and give IPPROTO_SCTP the same value (132) as it has on the Yosem

Re: Error installing gnuplot/aquaterm

On 28 October 2016 at 06:23, Tom Gederberg wrote: > I am sorry if this is a silly question, but I am trying to install gnuplot > (I am running Mac OS Sierra, recently updated and performed the MacPorts > migration) and am getting the error shown below. Aquaterm is needing to be > installed and th

Re: Libc++ on Snow Leopard

Jasper, I've been using this for months now, and I think I've worked through most of the hiccups, often with Jeremy's help. If you get stuck or have any questions or issues, please don't hesitate to ask, either on the list here if you want, or offline to me directly if you prefer to conceal you

Re: Flummoxed again by Octave

Jerry, To list the installed versions of octave-devel: post select octave to select a particular version, e.g. octave-devel-rc: sudo port select octave octave-devel-rc On Oct 27, 2016, at 5:59 PM, list_em...@icloud.com wrote: >> >> On Oct 27, 2016, at 1:29 PM, Marius Schamschula >> wrote:

Re: Flummoxed again by Octave

> On Oct 27, 2016, at 1:29 PM, Marius Schamschula wrote: > > Jerry, > > If you want to use octave packages with octave-devel*, you need to use octave > select. Otherwise mkoctfile (which is needed to build octave packages) cannot > be found, and MacPorts will proceed to install octave. I can

Re: Flummoxed again by Octave

On Thu, Oct 27, 2016 at 4:11 PM, wrote: > I recently did a fresh installation of MacPorts. I then installed > octave-devel because the version given for it is 4.1.0+, more recent than > that for octave the version of which is given as 4.0.3_1. > -devel ports are for testing; there is no guarante

Re: Libc++ on Snow Leopard

On Thu, Oct 27, 2016 at 3:18 PM, Jasper van der Schors < jasper.vandersch...@gmail.com> wrote: > I can't find the following names: > > cxx_stdlib libc++ > > delete_la_files yes > > default_compilers macports-clang-3.4 macports-clang-3.3 gcc-4.2 > apple-gcc-4.2 gcc-4.0 > > > Is there someone who ca

Re: anyone working on the KiCad port?

> Am 27.10.2016 um 11:41 schrieb Aljaž Srebrnič : > >> On 26 ott 2016, at 17:15, Lars Sonchocky-Helldorf >> wrote: >> >> Hi, >> >> there is currently no port for KiCad ( http://kicad-pcb.org ) available for >> MacPorts. Although googling for a port brought up the following two tickets: >> >

Re: anyone working on the KiCad port?

> On 26 ott 2016, at 17:15, Lars Sonchocky-Helldorf > wrote: > > Hi, > > there is currently no port for KiCad ( http://kicad-pcb.org ) available for > MacPorts. Although googling for a port brought up the following two tickets: > > https://trac.macports.org/ticket/47268 > https://trac.macport

Re: Sierra 10.12.1 and NTP

> On Oct 26, 2016, at 23:36, Dave Horsfall wrote: > > Just upgraded to 10.12.1, and system.log began spewing out this: > > Oct 27 14:54:36 ozzie com.apple.xpc.launchd[1] (org.macports.ntp): Service > only ran for 0 seconds. Pushing respawn out by 10 seconds. > > along with annoying pop-ups.

Re: Sierra 10.12.1 and NTP

> On Oct 27, 2016, at 01:36, Dave Horsfall wrote: > > Just upgraded to 10.12.1, and system.log began spewing out this: > > Oct 27 14:54:36 ozzie com.apple.xpc.launchd[1] (org.macports.ntp): Service > only ran for 0 seconds. Pushing respawn out by 10 seconds. > > along with annoying pop-ups.

Re: webkit-gtk2: Will it ever be fixed?

Am 24.10.16 um 01:27 schrieb David Evans: I did a test build this morning and, with the information you have provided, was able to reproduce the problem. Opened ticket https://trac.macports.org/ticket/52688 to track the issue and copied you there so you can see what's going on. Thanks for he

Re: webkit-gtk2: Will it ever be fixed?

On 10/22/16 1:20 PM, Bachsau wrote: > Am 21.10.16 um 22:37 schrieb David Evans: >> I understand your opinion but, in fact, X11 is generally the default. We >> port much more than just macOS native >> software, much of it from Linux, so X11 is the de facto default for >> historical reasons and be

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 make the move of Trac

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 current SVN and Trac downtime, we are also di

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 restore service ear

Re: Servers down?

On Sun, Oct 23, 2016 at 1:44 AM, Ryan Schmidt wrote: > a change Apple made to their network configuration which had unexpected > consequences ​Maybe it is not related but ​I have suffered serious synchronization issues in iCloud services. -- Eneko Gotzon Ares enekogot...@gmail.com ___

Re: Servers down?

> On Oct 22, 2016, at 16:11, Fielding, Eric J (329A) > wrote: > > I am guessing that the lack of access to MacPorts yesterday (Friday) may have > been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn > uses their content delivery network to provide DNS, different areas we

Re: Servers down?

> On Oct 22, 2016, at 5:11 PM, Fielding, Eric J (329A) > wrote: > > I am guessing that the lack of access to MacPorts yesterday (Friday) > may have been related to the massive DDoS attack on the Dyn DNS > servers. This seems unlikely to me, as our unplanned downtime began (I think) on Thursday

Re: Servers down?

I am guessing that the lack of access to MacPorts yesterday (Friday) may have been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn uses their content delivery network to provide DNS, different areas were affected to differing degrees from what I saw reported. The regular M

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 the > wiki page. I've added several tools to the l

Re: Moving to GitHub: Status Update, Action Required

On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote: > There's the "git" command line program in the "git" port, :-) Hahaha. Yes, of course! ;-) > 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 the wiki page. Haven’t

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 merge method to use, >> although I'd prefer th

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 in some thread latel

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 cl

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 into

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: Moving to GitHub: Status Update, Action Required

Hi, On Sat, Oct 22, 2016 at 07:54:20AM -0400, Richard Cobbe wrote: > Is there/will there be a story for people who cannot use rsync to pull > down updates because they're behind a restrictive proxy? > > This affects one of the three computers on which I maintain a MacPorts > installation. I curr

Re: Moving to GitHub: Status Update, Action Required

> On Oct 22, 2016, at 6:54 AM, Richard Cobbe wrote: > > On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: >> Hello MacPorts users and developers, >> >> MacPorts will be moving to GitHub soon. We're sending this email to >> inform you about changes in how you access the MacPorts repo

Re: Moving to GitHub: Status Update, Action Required

> On 22 Oct 2016, at 12:54 pm, Richard Cobbe wrote: > >> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: >> Hello MacPorts users and developers, >> >> MacPorts will be moving to GitHub soon. We're sending this email to >> inform you about changes in how you access the MacPorts re

Re: Moving to GitHub: Status Update, Action Required

On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: > Hello MacPorts users and developers, > > MacPorts will be moving to GitHub soon. We're sending this email to > inform you about changes in how you access the MacPorts repositories and > bug tracker. Additionally, this email contains in

Re: Moving to GitHub: Status Update, Action Required

On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote: >> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote: >> >>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote: >>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote: Also, is the consensus that a graphical user

Re: Moving to GitHub: Status Update, Action Required

On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote: >> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote: >> >>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote: >>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote: Also, is the consensus that a graphical user

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote: > >> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote: >> >>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven >>> wrote: >>> >>> Also, is the consensus that a graphical user interface over git >>> more likely to be harmful than helpful?

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote: > >> On Oct 21, 2016, at 10:20 PM, Craig Treleaven >> wrote: >> >> However, would it be possible to add a tangible example of updating >> a port to that page? >> >> I know a little bit about Subversion and less about Git. I would li

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote: > > However, would it be possible to add a tangible example of updating > a port to that page? > > I know a little bit about Subversion and less about Git. I would like > to see a soup-to-nuts example of cloning the ports tree, updating >

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: > > Hello MacPorts users and developers, > > ... Please read through > https://trac.macports.org/wiki/WorkingWithGit > which contains a number of guidelines for working with the MacPorts Git > repositories. > The Working with Git page is pretty

Re: Trac & Subversion available again

On Sat, Oct 22, 2016 at 3:16 AM, Clemens Lang wrote: > we brought the migration of our > ​ ​ > Trac installation… > Wonderful professionals: Thank you very much for all your work. -- Eneko Gotzon Ares enekogot...@gmail.com ___ macports-users mailing

Re: Servers down?

> On Oct 21, 2016, at 5:45 PM, Manfred Antar wrote: > > >> On Oct 21, 2016, at 3:32 PM, Ryan Schmidt wrote: >> >> >>> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez wrote: >>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco wrote: I can't even get to the migration page on ma

Re: Servers down?

> On Oct 21, 2016, at 3:32 PM, Ryan Schmidt wrote: > > >> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez wrote: >> >>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco wrote: >>> >>> I can't even get to the migration page on macports.org... >> >> Yes, {svn,trac}.macports.org is still down, an

Re: Servers down?

> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez wrote: > >> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco wrote: >> >> I can't even get to the migration page on macports.org... > > Yes, {svn,trac}.macports.org is still down, and probably others. The only other server that appears to have be

<    1   2   3   4   5   6   7   8   9   10   >