qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Ed Maste" <emaste@freebsd.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Gerd Hoffmann" <gerd@kraxel.org>,
	"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: FreeBSD build regressions
Date: Fri, 19 Feb 2021 11:28:42 -0700	[thread overview]
Message-ID: <CANCZdfpcDhWt0fh3kvM_+RfEaggkeWFTKJLy0CSofstFjOQkbg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9hW-hvjrS+tFt9KAkvVH+cCS_4JkMx+TUNEy5uFU-qaw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]

On Fri, Feb 19, 2021 at 9:14 AM Peter Maydell <peter.maydell@linaro.org>
wrote:

> On Fri, 19 Feb 2021 at 16:08, Warner Losh <imp@bsdimp.com> wrote:
> > FreeBSD builds packages on the oldest supported version in the stable
> branch. Due to forward compatibility, that means all supported versions of
> FreeBSD 12.x will work. Recently, FreeBSD 12.1 became unsupported, so the
> build machines clicked forward to 12.2. Since there's no 'forward
> compatibility' guarantees, this problem was hit. While you can run binaries
> compiled on old versions of the software on new versions of the system, you
> can't necessarily do the inverse because new symbols are introduced (in
> this case close_range).
>
> It makes perfect sense that you don't want to support older
> versions forever and that at some point newer packages aren't
> valid on old systems, but I don't understand why an
> older 12.1 system then says "but I'm going to go ahead and
> install these won't-work packages anyway" rather than
> "oh dear, I'm out of support, there are no newer packages
> available, I will install whatever the last archived version
> of the package for my OS version is" (or "I will install nothing").
> I'm surprised this doesn't break a lot of real-world users...
>

That's a reasonable expectation. I'd kinda expected that to be the default,
but it looks like it might not be. I'll see if I can get the freebsd vm
updated to use something safer and/or work with the pkg folks to get it to
do the safe thing here if there's no easy way to do this with command line
/ config settings. I think the issue is that we set IGNORE_OSVERSION which
is needed for the case when we were running 12.0 packages on 12.1, but it's
harmful for this case. This highlights, I think, a rough edge in pkg.

Short term, I'll bump things up to 12.2 which will take care of the
immediate issue. I should have a patch by later in the day.... I may also
have a patch to detect the mismatch directly and report it until this issue
can be resolved in FreeBSD's pkg.

Warner

[-- Attachment #2: Type: text/html, Size: 2608 bytes --]

  reply	other threads:[~2021-02-19 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 10:29 FreeBSD build regressions Alex Bennée
2021-02-19 10:41 ` Peter Maydell
2021-02-19 10:58   ` Alex Bennée
2021-02-19 15:05     ` Warner Losh
2021-02-19 15:24   ` Gerd Hoffmann
2021-02-19 16:08     ` Warner Losh
2021-02-19 16:13       ` Peter Maydell
2021-02-19 18:28         ` Warner Losh [this message]
2021-02-19 10:42 ` Daniel P. Berrangé

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=CANCZdfpcDhWt0fh3kvM_+RfEaggkeWFTKJLy0CSofstFjOQkbg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=alex.bennee@linaro.org \
    --cc=emaste@freebsd.org \
    --cc=gerd@kraxel.org \
    --cc=lwhsu@freebsd.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).