Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfr-dev <pfr-dev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ncspot-0.9.6
Date: Tue, 05 Apr 2022 11:53:43 +0200	[thread overview]
Message-ID: <20220405095343.Tid51_AafyTK8e0qNTaCG0ciz8G2uDss3_i8s5yEtbI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33600@inbox.vuxu.org>

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

New comment by pfr-dev on void-packages repository

https://github.com/void-linux/void-packages/pull/33600#issuecomment-1088499266

Comment:
trying to update to `0.9.7` from `0.9.0`

I took the template and swapped it out for the old one and ran `./xbps-src update-sys` but it fails to build `zlib-1.2.11_4`

```
=> zlib-1.2.11_4: building [configure] (dependency of pcre) for x86_64...
   [runtime] zlib-1.2.11_4: not found (self, ignored)
=> zlib-1.2.11_4: running do-fetch hook: 00-distfiles ...
=> zlib-1.2.11_4: fetching distfile 'zlib-1.2.11.tar.gz'...
http://www.zlib.net/zlib-1.2.11.tar.gz: Not Found
=> ERROR: zlib-1.2.11_4: failed to fetch zlib-1.2.11.tar.gz.
=> ERROR: xbps-src: failed to build ncspot-0.9.7_1 pkg!
```

I have `zlib-1.2.12_1` currently installed

  parent reply	other threads:[~2022-04-05  9:53 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17  9:42 [PR PATCH] New package: ncspot-0.9.0 ram02z
2021-10-17 12:36 ` [PR PATCH] [Updated] " ram02z
2021-10-29  2:04 ` [PR REVIEW] " abenson
2021-10-29 10:13 ` [PR PATCH] [Updated] " ram02z
2021-10-30  9:49 ` ram02z
2021-11-30  0:43 ` ram02z
2021-12-12  1:39 ` pfr-dev
2021-12-15  7:13 ` 0323pin
2022-01-04 18:40 ` [PR PATCH] [Updated] " ram02z
2022-01-05  0:46 ` New package: ncspot-0.9.4 ram02z
2022-01-20 12:12 ` ram02z
2022-01-20 13:23 ` 0323pin
2022-01-20 13:41 ` 0323pin
2022-01-20 13:42 ` ram02z
2022-01-20 13:50 ` 0323pin
2022-02-19 12:40 ` [PR PATCH] [Updated] " ram02z
2022-03-10 10:36 ` [PR PATCH] [Updated] New package: ncspot-0.9.5 ram02z
2022-03-10 12:30 ` New package: ncspot-0.9.6 ram02z
2022-03-28 14:22 ` [PR PATCH] [Updated] " ram02z
2022-03-28 14:23 ` ram02z
2022-04-05  9:51 ` pfr-dev
2022-04-05  9:53 ` pfr-dev
2022-04-05  9:53 ` pfr-dev
2022-04-05  9:53 ` pfr-dev [this message]
2022-04-05 20:18 ` New package: ncspot-0.9.7 abenson
2022-05-26 10:02 ` [PR PATCH] [Updated] " ram02z
2022-05-26 10:03 ` [PR PATCH] [Updated] New package: ncspot-0.9.8 ram02z
2022-06-11 15:13 ` ram02z
2022-07-01  3:55 ` New package: ncspot-0.10.0 wael444
2022-09-19 21:44 ` [PR PATCH] [Updated] " ram02z
2022-09-19 21:46 ` [PR PATCH] [Updated] New package: ncspot-0.11.1 ram02z
2022-12-19  1:54 ` github-actions
2022-12-19  1:56 ` ram02z
2022-12-19  1:56 ` ram02z
2022-12-28  9:56 ` [PR REVIEW] " classabbyamp
2022-12-28 10:23 ` 0323pin
2022-12-28 10:38 ` classabbyamp
2022-12-28 12:13 ` 0323pin
2023-01-16 13:42 ` [PR PATCH] [Updated] " ram02z
2023-01-16 13:44 ` [PR REVIEW] " ram02z
2023-01-16 13:44 ` ram02z
2023-01-16 13:44 ` [PR PATCH] [Updated] " ram02z
2023-01-16 15:03 ` [PR REVIEW] New package: ncspot-0.11.2 wael444
2023-01-16 16:42 ` classabbyamp
2023-01-16 16:43 ` [PR PATCH] [Updated] " ram02z
2023-01-16 16:43 ` [PR REVIEW] " classabbyamp
2023-01-16 16:43 ` ram02z
2023-01-16 16:45 ` classabbyamp
2023-01-16 16:46 ` ram02z
2023-01-16 16:47 ` classabbyamp
2023-01-16 16:47 ` 0323pin
2023-01-16 16:56 ` paper42
2023-01-16 17:03 ` 0323pin
2023-01-16 17:22 ` 0323pin
2023-01-16 17:57 ` paper42
2023-01-16 18:15 ` 0323pin
2023-01-16 18:15 ` 0323pin
2023-01-17 17:05 ` [PR PATCH] [Updated] " ram02z
2023-01-17 17:10 ` ram02z
2023-01-17 17:38 ` [PR REVIEW] " ram02z
2023-01-17 17:50 ` [PR PATCH] [Merged]: " classabbyamp
2023-01-17 20:19 ` atweiden
2023-01-17 20:28 ` classabbyamp
2023-01-17 20:41 ` classabbyamp
2023-01-17 21:11 ` 0323pin
2023-01-17 21:13 ` classabbyamp

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=20220405095343.Tid51_AafyTK8e0qNTaCG0ciz8G2uDss3_i8s5yEtbI@z \
    --to=pfr-dev@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).