Re: index warning and bash-completion

On Mar 10, 2018, at 12:18, db wrote: > > bash-completion for port outputs stderr on pressing tab, right before it > completes a word, on certain actions like contents. > > $ port contents bash-complWarning: port definitions are more than two weeks > old, consider updating them by running 'port

index warning and bash-completion

bash-completion for port outputs stderr on pressing tab, right before it completes a word, on certain actions like contents. $ port contents bash-complWarning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. etion Can anyone reproduce it?

Re: index warning and bash-completion

On 10 Mar 2018, at 20:05, Ryan Schmidt wrote: > Are your port definitions in fact more than two weeks old? Yes, but I'd expect the warning after I actually ran the command.

Re: Back level boost libraries available?

On Mar 10, 2018, at 14:53, S. L. Garwood wrote: > I need boost 1.65 … is it available on MacPorts? All I see is 1.66 No, MacPorts provides only the current version of a port. Instructions for installing an older version of a port are here:

Re: index warning and bash-completion

On Mar 10, 2018, at 14:24, db wrote: > On 10 Mar 2018, at 20:05, Ryan Schmidt wrote: >> Are your port definitions in fact more than two weeks old? > > Yes, but I'd expect the warning after I actually ran the command. When you press tab, the bash completion code runs. Looking at the contents of

Re: index warning and bash-completion

On Sat, Mar 10, 2018 at 09:24:27PM +0100, db wrote: > On 10 Mar 2018, at 20:05, Ryan Schmidt wrote: > > Are your port definitions in fact more than two weeks old? > > Yes, but I'd expect the warning after I actually ran the command. Unfortunately that happens because

Back level boost libraries available?

I need boost 1.65 … is it available on MacPorts? All I see is 1.66

Re: index warning and bash-completion

On 10 Mar 2018, at 23:15, Clemens Lang wrote: > > https://github.com/macports/macports-ports/blob/master/sysutils/bash-completion/files/port > so if you have time you could try modifying it to drop stderr into nirvana > and submit a pull request for that. Ok, I'll have to

qscintilla-qt4 won't compile

I just upgraded outdated ports (it had been a month or two probably). And qscintilla-qt4 failed. I think the relevant chunk from the log is below. Has anyone else had problems with this. I didn’t quickly find a bug report of this but may have missed it. :info:build In file included from

Re: qscintilla-qt4 won't compile

I ran into the same issue. The problem seems to be that during last week's SourceForge outage something other than the source package was downloaded (likely an html error message). I fixed this by running sudo port clean —dist qscintilla-qt4 and then sudo port upgrade qscintilla-qt4 > On

dependency doesn't upgrade so existing version of port broken

I just tried to run port upgrade outdated and a dependency of openscad (qscintilla-qt4) failed to upgrade. I still have the previous version of that dependency listed as active and only one version of port is listed as installed and it is listed as active. I thought the port would get

Re: dependency doesn't upgrade so existing version of port broken

On Mar 10, 2018, at 18:51, Lenore Horner wrote: > I just tried to run port upgrade outdated and a dependency of openscad > (qscintilla-qt4) failed to upgrade. I still have the previous version of > that dependency listed as active and only one version of port is listed as > installed and it

Re: Back level boost libraries available?

> On Mar 10, 2018, at 4:53 PM, Ryan Schmidt wrote: > > > On Mar 10, 2018, at 14:53, S. L. Garwood wrote: > >> I need boost 1.65 … is it available on MacPorts? All I see is 1.66 > > No, MacPorts provides only the current version of a port. > > Instructions for

Re: qscintilla-qt4 won't compile

< https://trac.macports.org/ticket/55944[1] > We're working on it. - MLD On Sat, Mar 10, 2018, at 7:15 PM, Lenore Horner wrote: > I just upgraded outdated ports (it had been a month or two probably). > And qscintilla-qt4 failed. I think the relevant chunk from the log > is below. Has anyone

Re: qscintilla-qt4 won't compile

On Mar 10, 2018, at 18:15, Lenore Horner wrote: > I don’t know whether the fetch errors are related at all. Nope. > qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 doesn't seem to exist in > /opt/local/var/macports/incoming/verified > Attempting to fetch