Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Simon Dawson <spdawson@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/xscreensaver: fix build
Date: Tue, 18 Jul 2023 11:46:08 +0200	[thread overview]
Message-ID: <20230718114608.60593e6d@windsurf> (raw)
In-Reply-To: <20230716170126.438652-1-bernd@kuhls.net>

Hello Bernd,

On Sun, 16 Jul 2023 19:01:25 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:

> diff --git a/.checkpackageignore b/.checkpackageignore
> index 504b96951b..fa557733e8 100644
> --- a/.checkpackageignore
> +++ b/.checkpackageignore
> @@ -1638,6 +1638,8 @@ package/xinetd/0004-configure-rlim_t.patch Upstream
>  package/xinetd/0005-CVE-2013-4342-xinetd-ignores-user-and-group-directiv.patch Upstream
>  package/xl2tp/xl2tpd TrailingSpace
>  package/xml-security-c/0001-fix-build-with-libressl-3.5.0.patch Upstream
> +package/xscreensaver/0001-disable-check-for-pam.patch
> +package/xscreensaver/0002-build-Do-not-build-po-files.patch

Is this valid syntax? You're saying to ignore some warnings, but not
which ones.

Also, for new patches, adding them in the checkpackageignore file is
quite odd. We definitely want those new patches to have an "Upstream:"
tag.

>  package/xxhash/0001-fix-man-page-installation.patch Upstream
>  package/xxhash/0002-Makefile-add-dedicated-install-targets.patch Upstream
>  package/xxhash/0003-do-no-longer-depend-on-assert-h-for-XXH_STATIC_ASSERT.patch Upstream
> diff --git a/package/xscreensaver/0001-disable-check-for-pam.patch b/package/xscreensaver/0001-disable-check-for-pam.patch
> new file mode 100644
> index 0000000000..6d052a53e9
> --- /dev/null
> +++ b/package/xscreensaver/0001-disable-check-for-pam.patch
> @@ -0,0 +1,16 @@
> +Fix cross-build
> +
> +Detecting features of the host does not make sense when cross-compiling.
> +
> +Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Meh, no Git repository of the project to have a nice Git formatted patch? :-/

> diff --git a/package/xscreensaver/0002-build-Do-not-build-po-files.patch b/package/xscreensaver/0002-build-Do-not-build-po-files.patch
> new file mode 100644
> index 0000000000..03674f5d50
> --- /dev/null
> +++ b/package/xscreensaver/0002-build-Do-not-build-po-files.patch
> @@ -0,0 +1,58 @@
> +From 6b5d022f6dd9848a2d5ca08a1968929b8c140981 Mon Sep 17 00:00:00 2001
> +From: Khem Raj <raj.khem@gmail.com>
> +Date: Sat, 16 Jul 2022 09:59:40 -0700
> +Subject: [PATCH 2/2] build: Do not build po files

No patch numbering, this raises a check-package warning.

I see Khem has been able to generate a git formatted patch, I wonder
against which Git repository?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-07-18  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 17:01 [Buildroot] [PATCH 1/2] package/xscreensaver: fix build Bernd Kuhls
2023-07-16 17:01 ` [Buildroot] [PATCH 2/2] package/xscreensaver: bump version to 6.06 Bernd Kuhls
2023-07-18  9:46 ` Thomas Petazzoni via buildroot [this message]
2023-07-31 22:41   ` [Buildroot] [PATCH 1/2] package/xscreensaver: fix build Thomas Petazzoni via buildroot

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=20230718114608.60593e6d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=spdawson@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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