Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: luca.ceresoli@bootlin.com, Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH v2] package/unzip: bump to Debian patch level -29 to fix GCC 15.x issues
Date: Tue, 16 Sep 2025 02:21:25 -0700	[thread overview]
Message-ID: <m2jz1yiwkr.fsf@aperture.us> (raw)
In-Reply-To: <20250907150711.3438750-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Sun, 7 Sep 2025 17:07:10 +0200")

Hi Thomas,

Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

> unzip currently fails to build with GCC 15.x. We're already fetching
> from Debian, using patchlevel -27, and it turns out that Debian
> patchlevel -29 has the GCC 15.x fix, and very few other fixes:
>
> unzip (6.0-29) unstable; urgency=medium
>
>   * Ignore invalid "Total number of disks" field on Microsoft ZIP64 files.
>     Closes: #661956, #1064000.
>   * Drop conflicting declarations of gmtime() and localtime().
>     Should fix build with gcc-15. Closes: #1098043.
>   * Fix zipgrep handling of escapes. Closes: #1054628.
>   * Stop using update-mime. Closes: #1072396.
>   * Add debian/source/lintian-overrides for *.a files.
>   * Do not trim Debian changelog.
>   * Add debian/salsa-ci.yml.
>   * Add Vcs-Git and Vcs-Browser fields.
>   * Update Standards-Version.
>
> unzip (6.0-28) unstable; urgency=medium
>
>   * Drop debian/source/lintian-overrides, obsolete since version 6.0-18.
>   * Update URI for Info-ZIP license in copyright file.
>   * Update standards version to 4.6.2.
>   * Run wrap-and-sort.
>   * Update Homepage.
>
> So let's just bump to this patchlevel version.
>
> Note that the .dsc file link in the .hash file was wrong, it was still
> referring to patchlevel -26.
>
> Fixes:
>
>   https://autobuild.buildroot.net/results/d81cb9d7c9e87dd233dde350d15cb03427ba2036/

This seems to fix build failures on my end as well:

https://github.com/skiffos/SkiffOS/actions/runs/17750130442/job/50443305589#step:8:30204

Tested-by: Christian Stewart <christian@aperture.us>

Thanks!
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-09-16  9:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 15:07 [Buildroot] [PATCH v2] package/unzip: bump to Debian patch level -29 to fix GCC 15.x issues Thomas Petazzoni via buildroot
2025-09-07 15:19 ` Baruch Siach via buildroot
2025-09-16  9:21 ` Christian Stewart via buildroot [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=m2jz1yiwkr.fsf@aperture.us \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=luca.ceresoli@bootlin.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