#59495 closed defect (fixed)
ansible-lint @3.4.19 fails to build
Reported by: | rseichter (Ralph Seichter) | Owned by: | zdw@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | Cc: | judaew (Vadym-Valdis Yudaiev) | |
Port: | ansible-lint |
Description
Building ansible-lint fails on Catalina:
$ sudo port install ansible-lint ---> Computing dependencies for ansible-lint ---> Fetching archive for ansible-lint ---> Attempting to fetch ansible-lint-3.4.19_0.darwin_19.noarch.tbz2 from http://nue.de.packages.macports.org/ansible-lint ---> Attempting to fetch ansible-lint-3.4.19_0.darwin_19.noarch.tbz2 from https://packages.macports.org/ansible-lint ---> Attempting to fetch ansible-lint-3.4.19_0.darwin_19.noarch.tbz2 from http://lil.fr.packages.macports.org/ansible-lint ---> Fetching distfiles for ansible-lint ---> Attempting to fetch ansible-lint-3.4.19.tar.gz from http://nue.de.distfiles.macports.org/ansible-lint ---> Verifying checksums for ansible-lint ---> Extracting ansible-lint ---> Configuring ansible-lint ---> Building ansible-lint Error: Failed to build ansible-lint: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_ansible-lint/ansible-lint/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port ansible-lint failed
Attachments (1)
Change History (9)
Changed 5 years ago by rseichter (Ralph Seichter)
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Owner: | set to zdw@… |
---|---|
Status: | new → assigned |
comment:2 Changed 4 years ago by thorfi (@thorfi)
comment:3 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
Cc: | judaew added |
---|
comment:4 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
This port should now be build correctly.
comment:5 Changed 3 years ago by reneeotten (Renee Otten)
Ralph - can you confirm that this indeed works for you so that we can close this ticket?
comment:6 Changed 3 years ago by rseichter (Ralph Seichter)
Well, sudo port install ansible-lint
was successful, but I did not build the whole dependency chain from source, and ansible-lint @5.0.12_0 appears to have been pre-built. Given that the ansible-lint port does not have any variants, pre-built is fine by me.
comment:7 Changed 3 years ago by reneeotten (Renee Otten)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
the dependency chain will be build from source on the buildbots and it shouldn't matter in this case I think. If you really wanted you could do sudo port -s install ansible-lint
to build that port from source on your computer. But let's close this ticket than as resolved and if you run into other trouble you can comment here or open a new one.
comment:8 Changed 3 years ago by rseichter (Ralph Seichter)
I am aware of the -s
flag. Alas, in combination with --force
this would cause the whole dependency chain to be built from scratch based on the ports' respective source code, so I did not do that. That being said, I am OK with closing this issue.
Hi, this issue is still persistent on Big Sur - although with a slightly different issue (checksum failure):