Opened 9 years ago

Closed 9 years ago

#49715 closed defect (fixed)

qt5 port: can fetch and checksum but extract fails

Reported by: hardwhack Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: qt5

Description

I am getting an unusual error. I can fetch and even checksum qt5 but when I try to extract qt5, I get an error:

Error: org.macports.extract for port qt5 returned: command execution failed

When I try a port install qt5, I get the same error. Looking a the log file, I see the following lines:

:debug:extract Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_aqua_qt5/qt5/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/qt5/qt5-5.5.1.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - 
:info:extract gzip: can't stat: /opt/local/var/macports/distfiles/qt5/qt5-5.5.1.tar.gz (/opt/local/var/macports/distfiles/qt5/qt5-5.5.1.tar.gz.gz): No such file or directory
:info:extract /usr/bin/gnutar: This does not look like a tar archive
:info:extract /usr/bin/gnutar: Exiting with failure status due to previous errors

The file /opt/local/var/macports/distfiles/qt5/qt5-5.5.1.tar.gz does not exist although there are a log of other .tar.xz files in that directory. Why is this failing for me? I thought perhaps my prior install of qt5-mac was interfering so I uninstalled qt5-mac first and then tried cleaning and installing qt5 but same error.

For some reason, both fetch and checksum failing silently without throwing error messages. It is only when extract goes to gnutar a non-existant file that an error is generated. Logfile attached.

Attachments (2)

main.log (100.7 KB) - added by hardwhack 9 years ago.
main.2.log (100.9 KB) - added by hardwhack 9 years ago.
logfile right after port clean --all qt5

Download all attachments as: .zip

Change History (11)

Changed 9 years ago by hardwhack

Attachment: main.log added

comment:1 Changed 9 years ago by hardwhack

I tried sudo port clean qt5 and even sudo port clean --all qt5 but same error.

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: extract failure removed

I am curious about the reference in the log to /opt/local/var/macports/distfiles/qt5/qt5-5.5.1.tar.gz.gz, which should not be.

The log you attached was not from the run immediately following running "sudo port clean --all qt5", so please run "sudo port clean --all qt5" one more time, then try one more time to install, and when it fails, attach that main.log to the ticket. I want to know which server you're getting the distfile from.

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: mcalhoun@… removed
Owner: changed from macports-tickets@… to mcalhoun@…

Wait: I see the same problem. Also, qt5 appears to be a stub port that is not intended to install anything, so it should not have a distfile at all. There is a bug here somewhere.

The stub port overrides the fetch and checksum phases. It should not do so. It should instead clear the distfiles variable.

comment:4 Changed 9 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Status: newassigned

I do not know why I can not reproduce this.
Attempting to follow comment:3, I copied the code from another meta port in r142609.
Does this fix the problem?

Changed 9 years ago by hardwhack

Attachment: main.2.log added

logfile right after port clean --all qt5

comment:5 in reply to:  2 Changed 9 years ago by hardwhack

Replying to ryandesign@…:

... please run "sudo port clean --all qt5" one more time, then try one more time to install, and when it fails, attach that main.log to the ticket. I want to know which server you're getting the distfile from.

I have attached a logfile immediately after a port clean -all command. I did a diff and other than a few timestamps being different, the ONLY difference I could see was the warning re: :warn:archivefetch Your DNS servers incorrectly claim to know the address of nonexistent

Could it be because I am using svn instead of rsync? I had to switch to svn last month when rsync started behaving flaky and throwing errors half the time.

comment:6 in reply to:  4 ; Changed 9 years ago by hardwhack

Replying to mcalhoun@…:

I do not know why I can not reproduce this.
Attempting to follow comment:3, I copied the code from another meta port in r142609.
Does this fix the problem?

Is the " r142609" supposed to be a link? I tried searching the trac.macports database and this thread is the only hit. I don't know what I am supposed to do to find out if this fixes my problem.

comment:7 in reply to:  6 ; Changed 9 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Replying to pjkim00@…:

Replying to mcalhoun@…:

I do not know why I can not reproduce this.
Attempting to follow comment:3, I copied the code from another meta port in r142609.
Does this fix the problem?

Is the " r142609" supposed to be a link? I tried searching the trac.macports database and this thread is the only hit. I don't know what I am supposed to do to find out if this fixes my problem.

r142609 links to a change in the subversion repository, but that feature is currently down (see #49389).
In case you are interested, you can also see the change by

cd /opt/local/var/macports/sources/svn.macports.org/trunk
svn diff -r142608:142609

This assumes that /opt/local/var/macports/sources/svn.macports.org/trunk is your subversion repository (based on the log file).

To test to see if the change worked, please try

sudo port clean --all qt5
sudo port selfupdate
sudo port install qt5

I believe selfupdate updates the subversion repository, but you could also try

sudo port clean --all qt5
cd /opt/local/var/macports/sources/svn.macports.org/trunk
svn up
sudo port install qt5

comment:8 in reply to:  7 ; Changed 9 years ago by hardwhack

Replying to mcalhoun@…:

To test to see if the change worked, please try

sudo port clean --all qt5
sudo port selfupdate
sudo port install qt5

I tried this and it worked. Consistent with it being a stub/placeholder port, it installs nearly instantaneously. Thanks.

comment:9 in reply to:  8 Changed 9 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: fixed
Status: assignedclosed

Replying to pjkim00@…:

I tried this and it worked. Consistent with it being a stub/placeholder port, it installs nearly instantaneously. Thanks.

I'm glad it worked.
Thanks for the report.

Note: See TracTickets for help on using tickets.