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 qscintilla-qt4-2.10.3_0.darwin_17.x86_64.
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 i
On Mar 10, 2018, at 17:47, db wrote:
> Btw, how can I change the two-week period for the warning. I couldn't find an
> option in macports.conf, either to change the period or to suppress it
> altogether.
I don't think we offer any options to configure that. We want users to stay up
to date; w
< 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 el
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 upgraded
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 Mar
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 q
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 take a closer look, a
> 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 installing an older version of
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 the bash completion executes
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:
https://trac.macports.org/wiki/howto/InstallingOlderPo
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
I need boost 1.65 … is it available on MacPorts? All I see is 1.66
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.
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
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?
16 matches
Mail list logo