Re: qscintilla-qt4 won't compile

[Ryan Schmidt]

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.tbz2 from 
> https://packages.macports.org/qscintilla-qt4
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found
> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
> http://ywg.ca.packages.macports.org/mirror/macports/packages/qscintilla-qt4
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found
> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
> http://sea.us.packages.macports.org/macports/packages/qscintilla-qt4
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found

The archive can't be fetched both because 1) it doesn't exist because the 
software doesn't build, as you've discovered, and 2) we are not allowed to 
distribute binaries for this port because of the license.

> Fetching distfiles for qscintilla-qt4
> :debug:fetch Executing org.macports.fetch (qscintilla-qt4)
> :info:fetch --->  QScintilla_gpl-2.10.3.tar.gz does not exist in 
> /opt/local/var/macports/distfiles/qscintilla
> :notice:fetch --->  Attempting to fetch QScintilla_gpl-2.10.3.tar.gz from 
> http://iweb.dl.sourceforge.net/pyqt

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

[Ryan Schmidt]

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 is listed as active.  I thought the port would get upgraded 
> after all its dependencies got upgraded so the old port which referred to the 
> old version of the dependency should still work but it won’t even start.  I 
> guess that means my ports are now in some mixed state where some dependencies 
> of openscad have been upgraded but the port itself hasn’t been so the port is 
> trying to link against something that’s now inactive.

That sounds right.

> Is there any way to go back to previous versions of everything I just 
> upgraded other than scrolling through the terminal buffer and going through 
> deactivate of new and activate of previous on everything in the list?

No automated way, no, unless you recorded a list of what was active before you 
started the upgrade.

My usual procedure when I update ports on the MacPorts build server is to 
selfupdate (sudo port selfupdate), uninstall inactive ports (sudo port 
uninstall inactive), then upgrade outdated ports (sudo port upgrade outdated). 
I haven't had a need to test this yet, but my hope is that if anything failed 
to build, or if everything seemed to succeed but then some service on the 
server doesn't work right, I would be able to go back to the previous working 
versions of everything with "sudo port activate inactive".

Re: qscintilla-qt4 won't compile

[Michael Dickens]

< 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 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 qsciscintillabase.cpp:41:
> :info:build ./SciAccessibility.h:80:26: error: no type named
> 'InterfaceType' in 'QAccessible'; did you mean
> 'QAccessible2::InterfaceType'?> :info:build void 
> *interface_cast(QAccessible::InterfaceType t);
> :info:build  ^~
> :info:build  QAccessible2::InterfaceType
> :info:build /opt/local/libexec/qt4/include/QtGui/qaccessible.h:349:10:
> note: 'QAccessible2::InterfaceType' declared here> :info:build enum 
> InterfaceType
> 
> I don’t know whether the fetch errors are related at all.
> 
> 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.tbz2 from
> https://packages.macports.org/qscintilla-qt4> :debug:archivefetch Fetching 
> archive failed: The requested URL
> returned error: 404 Not Found> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-
> 2.10.3_0.darwin_17.x86_64.tbz2 from
> http://ywg.ca.packages.macports.org/mirror/macports/packages/qscintilla-qt4> 
> :debug:archivefetch Fetching archive failed: The requested URL
> returned error: 404 Not Found> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-
> 2.10.3_0.darwin_17.x86_64.tbz2 from
> http://sea.us.packages.macports.org/macports/packages/qscintilla-qt4> 
> :debug:archivefetch Fetching archive failed: The requested URL
> returned error: 404 Not Found> Fetching distfiles for qscintilla-qt4
> :debug:fetch Executing org.macports.fetch (qscintilla-qt4)
> :info:fetch --->  QScintilla_gpl-2.10.3.tar.gz does not exist in
> /opt/local/var/macports/distfiles/qscintilla> :notice:fetch --->  Attempting 
> to fetch QScintilla_gpl-2.10.3.tar.gz
> from http://iweb.dl.sourceforge.net/pyqt

Links:

  1. https://trac.macports.org/ticket/55944#comment:23

dependency doesn't upgrade so existing version of port broken

[Lenore Horner]

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 after all 
its dependencies got upgraded so the old port which referred to the old version 
of the dependency should still work but it won’t even start.  I guess that 
means my ports are now in some mixed state where some dependencies of openscad 
have been upgraded but the port itself hasn’t been so the port is trying to 
link against something that’s now inactive.  Is there any way to go back to 
previous versions of everything I just upgraded other than scrolling through 
the terminal buffer and going through deactivate of new and activate of 
previous on everything in the list?

TIA,
Lenore

Re: qscintilla-qt4 won't compile

[Marius Schamschula]

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 10, 2018, at 6: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 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 qsciscintillabase.cpp:41:
> :info:build ./SciAccessibility.h:80:26: error: no type named 'InterfaceType' 
> in 'QAccessible'; did you mean 'QAccessible2::InterfaceType'?
> :info:build void *interface_cast(QAccessible::InterfaceType t);
> :info:build  ^~
> :info:build  QAccessible2::InterfaceType
> :info:build /opt/local/libexec/qt4/include/QtGui/qaccessible.h:349:10: note: 
> 'QAccessible2::InterfaceType' declared here
> :info:build enum InterfaceType
> 
> I don’t know whether the fetch errors are related at all.
> 
> 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.tbz2 from 
> https://packages.macports.org/qscintilla-qt4 
> 
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found
> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
> http://ywg.ca.packages.macports.org/mirror/macports/packages/qscintilla-qt4 
> 
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found
> :msg:archivefetch --->  Attempting to fetch 
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
> http://sea.us.packages.macports.org/macports/packages/qscintilla-qt4 
> 
> :debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404 Not Found
> Fetching distfiles for qscintilla-qt4
> :debug:fetch Executing org.macports.fetch (qscintilla-qt4)
> :info:fetch --->  QScintilla_gpl-2.10.3.tar.gz does not exist in 
> /opt/local/var/macports/distfiles/qscintilla
> :notice:fetch --->  Attempting to fetch QScintilla_gpl-2.10.3.tar.gz from 
> http://iweb.dl.sourceforge.net/pyqt 
> 
> TIA,
> Lenore

Marius
--
Marius Schamschula

qscintilla-qt4 won't compile

[Lenore Horner]

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 qsciscintillabase.cpp:41:
:info:build ./SciAccessibility.h:80:26: error: no type named 'InterfaceType' in 
'QAccessible'; did you mean 'QAccessible2::InterfaceType'?
:info:build void *interface_cast(QAccessible::InterfaceType t);
:info:build  ^~
:info:build  QAccessible2::InterfaceType
:info:build /opt/local/libexec/qt4/include/QtGui/qaccessible.h:349:10: note: 
'QAccessible2::InterfaceType' declared here
:info:build enum InterfaceType

I don’t know whether the fetch errors are related at all.

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.tbz2 from 
https://packages.macports.org/qscintilla-qt4
:debug:archivefetch Fetching archive failed: The requested URL returned error: 
404 Not Found
:msg:archivefetch --->  Attempting to fetch 
qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
http://ywg.ca.packages.macports.org/mirror/macports/packages/qscintilla-qt4
:debug:archivefetch Fetching archive failed: The requested URL returned error: 
404 Not Found
:msg:archivefetch --->  Attempting to fetch 
qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 from 
http://sea.us.packages.macports.org/macports/packages/qscintilla-qt4
:debug:archivefetch Fetching archive failed: The requested URL returned error: 
404 Not Found
Fetching distfiles for qscintilla-qt4
:debug:fetch Executing org.macports.fetch (qscintilla-qt4)
:info:fetch --->  QScintilla_gpl-2.10.3.tar.gz does not exist in 
/opt/local/var/macports/distfiles/qscintilla
:notice:fetch --->  Attempting to fetch QScintilla_gpl-2.10.3.tar.gz from 
http://iweb.dl.sourceforge.net/pyqt

TIA,
Lenore

Re: index warning and bash-completion

[db]

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, as it doesn't show for certain actions 
like info.

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.

Re: Back level boost libraries available?

[S. L. Garwood]

> 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 a port are here:
> 
> https://trac.macports.org/wiki/howto/InstallingOlderPort
> 
> However, if you downgrade boost to 1.65, that will probably break any ports 
> you've installed that depend on boost. So I don't recommend you do that.
> 
> Why do you need 1.65?

error: use of class template 'boost::asio::strand' requires template arguments 
boost::asio::strand* _strand;
Common problem with 1.66 due to rework of asio:: 
1.65 worked fine

Re: index warning and bash-completion

[Clemens Lang]

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 'port
-q', which only hides info messages, but still displays warnings. The
source code for this is at
  
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.

-- 
Clemens

Re: Back level boost libraries available?

[Ryan Schmidt]

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/InstallingOlderPort

However, if you downgrade boost to 1.65, that will probably break any ports 
you've installed that depend on boost. So I don't recommend you do that.

Why do you need 1.65?

Re: index warning and bash-completion

[Ryan Schmidt]

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 
/opt/local/share/bash-completion/completions/port, I see that in order to 
provide the completions to you, it will be running various port commands. For 
example, if you are typing "port contents bash-compl" and then pressing tab, 
expecting it to autocomplete the name of an installed port, it has to run "port 
installed" or something to find the list of installed ports.

I don't know if MacPorts has a flag to suppress the warning. If so, 
/opt/local/share/bash-completion/completions/port should use it. If not, we 
should add one.

Back level boost libraries available?

[S. L. Garwood]

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

Re: index warning and bash-completion

[db]

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: index warning and bash-completion

[Ryan Schmidt]

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 selfupdate'.
> etion
> 
> Can anyone reproduce it?

Are your port definitions in fact more than two weeks old?

index warning and bash-completion

[db]

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?