From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Jdupes 1200
Date: Tue, 20 Jul 2021 00:45:34 +0200 [thread overview]
Message-ID: <20210719224534.scnpzTKE5vdhupz376s0ZpyhP0d95wVhT7tfadM6PM8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32048@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
There's a merged pull request on the void-packages repository
Jdupes 1200
https://github.com/void-linux/void-packages/pull/32048
Description:
<!-- Mark items with [x] where applicable -->
Despite the flag ENABLE_BTRFS is enabled for make, this seems to be mishandled by the way the Makefile builds the CFLAGS, so the functionality does not get included.
(It does not depend on any BTRFS headers, libraries, or ioctls, only if the appropriate flag is given on run)
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-glibc
- [x] armv7l
- [ ] armv6l-musl
prev parent reply other threads:[~2021-07-19 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 21:45 [PR PATCH] " chexum
2021-07-19 21:49 ` [PR PATCH] [Updated] " chexum
2021-07-19 22:45 ` leahneukirchen [this message]
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=20210719224534.scnpzTKE5vdhupz376s0ZpyhP0d95wVhT7tfadM6PM8@z \
--to=leahneukirchen@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).