Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] packages broken by cmake build-style change
Date: Thu, 18 Apr 2024 09:33:24 +0200	[thread overview]
Message-ID: <20240418073324.4A2AE2214D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45679@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

Closed issue by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/45679

Description:
cc @sgn

the following packages were broken by using cmake-bootstrap by default in the build-style:

network download:
- [x] grpc
- [x] sysdig
- [x] OpenRCT2
- [x] mixxx

other:
- [x] musikcube

there are definitely more, but these are the ones I saw when doing rebuilds for openssl. this can be fixed by simply adding `cmake` to hostmakedepends, but the build-style doesn't seem to account for this

### example error
```
[8/206] Performing download step (download, verify and extract) for 'jq'
FAILED: jq-prefix/src/jq-stamp/jq-download /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-stamp/jq-download 
cd /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src && /usr/libexec/xbps-src/bin/cmake -P /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-stamp/download-jq.cmake && /usr/libexec/xbps-src/bin/cmake -P /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-stamp/verify-jq.cmake && /usr/libexec/xbps-src/bin/cmake -P /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-stamp/extract-jq.cmake && /usr/libexec/xbps-src/bin/cmake -E touch /builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-stamp/jq-download
-- Downloading...
   dst='/builddir/sysdig-0.31.5/sysdig-0.31.5/build/jq-prefix/src/jq-1.6.tar.gz'
   timeout='none'
   inactivity timeout='none'
-- Using src='https://download.falco.org/dependencies/jq-1.6.tar.gz'
CMake Error at jq-stamp/download-jq.cmake:170 (message):
  Each download failed!

    error: downloading 'https://download.falco.org/dependencies/jq-1.6.tar.gz' failed
          status_code: 1
          status_string: "Unsupported protocol"
          log:
          --- LOG BEGIN ---
          Protocol "https" not supported or disabled in libcurl

  Closing connection -1



          --- LOG END ---
```

  parent reply	other threads:[~2024-04-18  7:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20  0:25 [ISSUE] " classabbyamp
2023-08-20  0:30 ` sgn
2023-08-20  2:51 ` classabbyamp
2023-08-22 21:24 ` motorto
2023-08-29 14:10 ` sgn
2023-12-24 19:35 ` d4r1us-drk
2023-12-24 21:17 ` 0x5c
2023-12-24 22:08 ` d4r1us-drk
2023-12-24 22:11 ` d4r1us-drk
2023-12-24 22:53 ` 0x5c
2023-12-25  1:00 ` d4r1us-drk
2023-12-25  1:07 ` classabbyamp
2023-12-25  1:56 ` sgn
2023-12-25  2:10 ` 0x5c
2023-12-25  2:13 ` d4r1us-drk
2023-12-25  2:15 ` sgn
2023-12-25  2:16 ` sgn
2023-12-25  2:17 ` sgn
2023-12-25  2:17 ` sgn
2023-12-25  2:19 ` d4r1us-drk
2023-12-25  3:03 ` 0x5c
2023-12-25  3:07 ` d4r1us-drk
2024-04-18  7:33 ` classabbyamp [this message]
2024-04-18  7:33 ` classabbyamp
2024-04-19  4:43 ` ibhagwan
2024-04-20 20:24 ` d4r1us-drk
2024-04-20 20:25 ` d4r1us-drk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240418073324.4A2AE2214D@inbox.vuxu.org \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).