Github messages for voidlinux
 help / color / mirror / Atom feed
From: tuxliban <tuxliban@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: herbe-1.0.0
Date: Thu, 17 Dec 2020 23:08:12 +0100	[thread overview]
Message-ID: <20201217220812.Nq4YQZPKvTZiF9JWnaA4U1YhrsHenLhd4r7cf7Mj7u8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27195@inbox.vuxu.org>

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

New review comment by tuxliban on void-packages repository

https://github.com/void-linux/void-packages/pull/27195#discussion_r545434875

Comment:
Previously I tried to build the binary directly with the help of the gnu-makefile build script, but despite having specified the makedepends in the middle of the process it gives me an error for missing a header.
The only way I was able to build the binary was as the template currently is.

```
-> $ ./xbps-src -f pkg herbe
=> xbps-src: updating repositories for host (x86_64-musl)...
[*] Updating repository `https://alpha.us.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
x86_64-musl-repodata: 1688KB [avg rate: 86KB/s]
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
x86_64-musl-repodata: 1688KB [avg rate: 187KB/s]
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ..
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> herbe-1.0.0_1: removing autodeps, please wait...
=> herbe-1.0.0_1: building [gnu-makefile] for x86_64-musl...
   [target] libXft-devel-2.3.3_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
   [target] freetype-devel-2.10.4_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
=> herbe-1.0.0_1: installing target dependencies: libXft-devel-2.3.3_1 freetype-devel-2.10.4_1 ...
=> herbe-1.0.0_1: running do-fetch hook: 00-distfiles ...
=> herbe-1.0.0_1: running do-extract hook: 00-distfiles ...
=> herbe-1.0.0_1: extracting distfile(s), please wait...
=> herbe-1.0.0_1: running do-patch hook: 00-patches ...
=> herbe-1.0.0_1: patching: 11.diff.
=> herbe-1.0.0_1: patching: Xresources.diff.
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file config.def.h.rej
Reversed (or previously applied) patch detected!  Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file herbe.c.rej
=> ERROR: herbe-1.0.0_1: do-patch_00-patches: 'patch -sl ${_args} -i ${_patch} 2> /dev/null' exited with 1
=> ERROR:   in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR:   in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR:   in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR:   in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR:   in run_step() at common/xbps-src/shutils/common.sh:71
=> ERROR:   in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33
```

  parent reply	other threads:[~2020-12-17 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 10:14 [PR PATCH] " tuxliban
2020-12-16 10:44 ` [PR PATCH] [Updated] " tuxliban
2020-12-17 14:08 ` [PR REVIEW] " Piraty
2020-12-17 14:08 ` Piraty
2020-12-17 22:07 ` tuxliban
2020-12-17 22:08 ` tuxliban [this message]
2020-12-17 22:35 ` tuxliban
2020-12-17 22:38 ` tuxliban
2020-12-17 22:44 ` tuxliban
2020-12-21 11:46 ` Piraty
2020-12-21 11:47 ` Piraty
2020-12-21 11:48 ` Piraty
2020-12-21 11:50 ` Piraty
2020-12-21 11:50 ` Piraty
2021-02-07 11:33 ` [PR PATCH] [Updated] " tuxliban
2021-04-28 11:51 ` ericonr
2021-04-28 11:51 ` [PR PATCH] [Closed]: " ericonr

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=20201217220812.Nq4YQZPKvTZiF9JWnaA4U1YhrsHenLhd4r7cf7Mj7u8@z \
    --to=tuxliban@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).