On Tue, 18 Apr 2017, Ryan Schmidt wrote:
> rsync://aarnet.au.rsync.macports.org/pub/macports/ports/ [default]
Fixed! I guess I regarded "[default]" as, well, an optional default...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
> On 19 Apr 2017, at 10:29 am, Ken Cunningham
> wrote:
> Jeremy has previously indicated privately to me that he wasn’t too keen on
> the idea due to possible unexpected consequences of changing default
> behaviour, and this is a respectable point coming from the honcho himself.
Jeremy: inte
On 2017-04-18, at 8:54 AM, Mojca Miklavec wrote:
>>
>> After coming across this issue one too many times for my own liking, and
>> changing several dozen ports as you have done, I finally just patched clang
>> to make it default to add -stdlib=lilbc++ by default on all systems, which
>> solves
This is sort of on topic because I installed tmux via macports…
I can do this to set environment variable as as non-root user:
launchctl setenv BLAH blah
But, within tmux I get:
Not privileged to set domain environment.
I find posts on the internets suggesting running tmux with sudo, but then
If you want aarnet to be your default ports source, use this line:
rsync://aarnet.au.rsync.macports.org/pub/macports/ports/ [default]
> On Apr 18, 2017, at 17:15, Ken Cunningham
> wrote:
>
> you appear to have commented out the default ports source.
>
> Ken
>
>
> On 2017-04-18, at 3:00 P
you appear to have commented out the default ports source.
Ken
On 2017-04-18, at 3:00 PM, Dave Horsfall wrote:
> I keep getting this message since around 2.4.1:
>
>Warning: No default port source specified in
> /opt/local/etc/macports/sources.conf, using last source as default
>
> Yet I
I keep getting this message since around 2.4.1:
Warning: No default port source specified in
/opt/local/etc/macports/sources.conf, using last source as default
Yet I have this in sources.conf:
# DH rsync://rsync.macports.org/release/ports/ [default]
rsync://aarnet.au.rsync.macports.
py-pyqt5 was just updated to 5.8.2 today while qt5 was updated to 5.7.1 (which
doesn't include qtenginio anymore) before that. So I would say this shouldn't
have happened... unless you forced py27-pyqt5 to upgrade before qt5 was
upgraded by using the -n flag?
> On Apr 18, 2017, at 11:31, Field
Now that all the ports are upgraded on my second machine, I am getting a broken
file warning, but it does not offer to fix it, even when I tried the “port
rev-upgrade”:
% sudo port rev-upgrade
---> Scanning binaries for linking errors
---> Found 1 broken file, matching files to ports
---> Foun
> On Apr 18, 2017, at 11:23, Fielding, Eric J (329A)
> wrote:
>
> I just did a similar “port selfupdate” and “port upgrade outdated” on my
> other Mac, and I got the same error message when I tried to uninstall
> qt5-qtenginio. This time, I did “port uninstall qt5 @5.6.2_0” first and then
>
I just did a similar “port selfupdate” and “port upgrade outdated” on my other
Mac, and I got the same error message when I tried to uninstall qt5-qtenginio.
This time, I did “port uninstall qt5 @5.6.2_0” first and then uninstalled
qt5-qtenginio without any error. It seems that the warning about
>
> Newer systems will stumble on these ports as by default clang will add
> -stdlib=libstdc++ and that doesn't work with cxx11; you get link errors.
>
>
One typo, sorry -- this should say "Older systems will stumble on these ports
...", not "Newer systems will stumble on these ports ."
my a
On 18 April 2017 at 17:45, Ken Cunningham wrote:
>
> After coming across this issue one too many times for my own liking, and
> changing several dozen ports as you have done, I finally just patched clang
> to make it default to add -stdlib=lilbc++ by default on all systems, which
> solves this i
There are two issues:
1. cxx11 features required. These crop up in more and more software as these
features are increasingly used. Newer systems breeze right past them as their
default compiler is new enough to handle this. Older systems (10.8 or less)
hang up on them as their default compiler
On 18 Apr 2017, at 09:50, db wrote:
> I filed #53994, #53995, #53996 for highlight, nmap and ostinato respectively,
> failing to build with libc++. I'd appreciate if anyone could peek at the logs
> and recognize a pattern or tell these are unrelated.
highlight (#53994) and nmap (#53995) build w
Yes, I ran “port selfupdate” and “port upgrade” again and the last ports after
qt5 (including py27-pyqt5 @5.8.2_0 ) are now upgraded successfully, so the port
system fixed whatever was wrong before. The scan for broken ports helps a lot
for those of us who are not so careful with our maintenance
Well it looks good now. 5.7.1 is the latest, and it's what you have active, so
hopefully things are fine now?
> On Apr 18, 2017, at 09:19, Fielding, Eric J (329A)
> wrote:
>
> Thanks for the help.
>
> I did run “port selfupdate” before doing the “port upgrade”, but I think the
> last time I
Thanks for the help.
I did run “port selfupdate” before doing the “port upgrade”, but I think the
last time I did the “port upgrade” it did not complete due to some error that I
forgot. I didn’t have time to figure out what was wrong at that time, which was
likely my mistake. Probably the ports
On 18 Apr 2017, at 14:43, Ryan Schmidt wrote:
> Ok fine. So texinfo got installed as a dependency of coreutils. You didn't
> ask for it directly, so it was not marked requested.
> Then, after that, you asked MacPorts to directly install texinfo. Since it
> was already installed, MacPorts did not
> On Apr 18, 2017, at 07:37, db wrote:
>
> On 18 Apr 2017, at 13:07, Ryan Schmidt wrote:
>> Yes, installing a port should mark it requested. I'm unclear what happened
>> in your situation.
>
> This is what I do:
>
> Last login: Tue Apr 18 14:14:12 on ttys001
> tests-mac:~ test$
> tests-mac:
On 18 Apr 2017, at 13:07, Ryan Schmidt wrote:
> Yes, installing a port should mark it requested. I'm unclear what happened in
> your situation.
This is what I do:
Last login: Tue Apr 18 14:14:12 on ttys001
tests-mac:~ test$
tests-mac:~ test$ port version
Version: 2.4.1
tests-mac:~ test$
tests
> On Apr 17, 2017, at 20:27, Fielding, Eric J (329A)
> wrote:
>
> I might have missed something in the last few months, but I didn’t find a
> mention of this.
>
> I did a “port upgrade outdated” after a month or two, and I got this error
> message:
>
> Error: qt5-qtenginio is obsolete; pl
On Apr 18, 2017, at 02:52, db wrote:
> I wanted to install texinfo which is actually a leaf of coreutils, but `sudo
> port install texinfo` doesn't make it a requested port, as I would expect. Is
> it intended behaviour? I suppose, I could either uninstall leaves and
> reinstall it, or use set
I wanted to install texinfo which is actually a leaf of coreutils, but `sudo
port install texinfo` doesn't make it a requested port, as I would expect. Is
it intended behaviour? I suppose, I could either uninstall leaves and reinstall
it, or use setrequested.
I filed #53994, #53995, #53996 for highlight, nmap and ostinato respectively,
failing to build with libc++. I'd appreciate if anyone could peek at the logs
and recognize a pattern or tell these are unrelated.
25 matches
Mail list logo
