From: ajtcode71 <ajtcode71@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: darktable: update to 4.0.0
Date: Sun, 31 Jul 2022 08:49:03 +0200 [thread overview]
Message-ID: <20220731064903.1GiwcuwCr2r9tKembOSahiwrd-UH9fpZiJUFyLON-4w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38336@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
New comment by ajtcode71 on void-packages repository
https://github.com/void-linux/void-packages/pull/38336#issuecomment-1200361542
Comment:
For some reasons all xbps packages i xlint come up with following errors:
grep: zstd-1.5.2_1.x86_64.xbps: binary file matches
grep: zstd-1.5.2_1.x86_64.xbps: binary file matches
grep: zstd-1.5.2_1.x86_64.xbps: binary file matches
grep: zstd-1.5.2_1.x86_64.xbps: binary file matches
grep: zstd-1.5.2_1.x86_64.xbps: binary file matches
zstd-1.5.2_1.x86_64.xbps: 'homepage' missing!
zstd-1.5.2_1.x86_64.xbps: 'license' missing!
zstd-1.5.2_1.x86_64.xbps: 'maintainer' missing!
zstd-1.5.2_1.x86_64.xbps: 'pkgname' missing!
zstd-1.5.2_1.x86_64.xbps: 'revision' missing!
zstd-1.5.2_1.x86_64.xbps: 'short_desc' missing!
zstd-1.5.2_1.x86_64.xbps: 'version' missing!
zstd-1.5.2_1.x86_64.xbps:1: Header should be: # Template file for ''
zstd-1.5.2_1.x86_64.xbps:1758: File does not end with newline character
These are will packages that I havent built... My Darktable 4 template is as peer the 3.8 template will the change to version number and checksum..
All the fields that are coming back as missing are in the template...
Any ideas?
next prev parent reply other threads:[~2022-07-31 6:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 15:22 [PR PATCH] New Version 4.0.0 - Test compiled amd64 and aarch64 ajtcode71
2022-07-28 15:30 ` [PR PATCH] [Updated] " ajtcode71
2022-07-28 15:37 ` darktable: update to 4.0.0 CameronNemo
2022-07-28 15:44 ` tranzystorek-io
2022-07-28 16:25 ` [PR PATCH] [Updated] " ajtcode71
2022-07-28 16:40 ` ajtcode71
2022-07-31 6:49 ` ajtcode71 [this message]
2022-07-31 7:07 ` ajtcode71
2022-07-31 7:12 ` CameronNemo
2022-08-01 4:00 ` ajtcode71
2022-08-05 23:49 ` abenson
2022-08-07 7:47 ` [PR PATCH] [Updated] " ajtcode71
2022-08-08 7:07 ` ajtcode71
2022-08-09 22:57 ` ajtcode71
2022-08-09 23:11 ` ajtcode71
2022-08-09 23:31 ` ajtcode71
2022-08-09 23:48 ` lemmi
2022-08-10 7:27 ` [PR PATCH] [Updated] " ajtcode71
2022-08-10 7:33 ` ajtcode71
2022-08-10 7:59 ` ajtcode71
2022-08-10 8:01 ` ajtcode71
2022-08-10 8:01 ` ajtcode71
2022-08-10 8:43 ` paper42
2022-08-11 0:49 ` lemmi
2022-08-11 0:49 ` [PR PATCH] [Closed]: " lemmi
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=20220731064903.1GiwcuwCr2r9tKembOSahiwrd-UH9fpZiJUFyLON-4w@z \
--to=ajtcode71@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).