From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: meta@public-inbox.org
Cc: Ricardo Ribalda <ribalda@chromium.org>
Subject: Debian's Perl CI tests fail for public-inbox
Date: Mon, 14 Nov 2022 19:26:19 +0100 [thread overview]
Message-ID: <20221114182619.r7hbl37giytraqj4@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
Hello,
based on a MR by Ricardo Ribalda Delgado[1] I looked into the automatic
CI possibilities for Debian packages. I enabled it for the Debian
packaging repository and there are a few failures. Given my little Perl
foo I don't know how to properly handle all of them.
The pipeline just runs perl -wc $file for each installed file.
For /usr/share/perl5/PublicInbox/WwwHighlight.pm this might be fixed by
build-depending on libhighlight-perl?
/usr/share/perl5/PublicInbox/DSKQXS.pm fails because it's BSD stuff not
available/needed on Linux. How should this be resolved? Not installing
that module? Or is running perl -wc on everything just a bad idea?
The full log is available on https://salsa.debian.org/ukleinek/public-inbox/-/jobs/3485533
Best regards
Uwe
[1] https://salsa.debian.org/ukleinek/public-inbox/-/merge_requests/1,
thanks, even if I didn't pick up everything in there for 1.9.0-1
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-14 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 18:26 Uwe Kleine-König [this message]
2022-11-14 20:32 ` Debian's Perl CI tests fail for public-inbox Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221114182619.r7hbl37giytraqj4@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=meta@public-inbox.org \
--cc=ribalda@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).