public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: libpng-1.5 smooth upgrade
Date: Fri, 11 Feb 2011 18:26:05 +0100	[thread overview]
Message-ID: <1297445165.2150.12.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <4D556603.8040400@gentoo.org>

Il giorno ven, 11/02/2011 alle 17.38 +0100, "Paweł Hajdan, Jr." ha
scritto:
> 1) Are we going to have a tinderbox run *before* libpng-1.5 gets keyworded?

Absolutely.

> 2) If the upgrade is non-trivial, i.e. just emerge -uDNa world and
> revdep-rebuild isn't going to fix it, will we have an upgrade guide,
> possibly as a news item?

As Samuli said we're planning on making it as "standard" as possible,
similarly to what's done with Berkeley DB. This is going to take a bit
more work than a standard bump but will avoid further breakage.

Slotted installation is the thing that makes most sense, especially
since upstream helps us there already by versioning the symbols.

> 3) Can we do something to make catching libpng problems easier? As
> Samuli pointed out in https://bugs.gentoo.org/show_bug.cgi?id=354479
> there is a predictable compilation warning. How about making portage
> print it as a QA warning, so more people can report the issues without
> even emerging libpng-1.5 on their systems? That may be a good backup
> option for the tinderbox too.

Tinderbox is also going to report all those warnings to me, which means
I'll open them to the bugzilla. While it might not cover 100% use cases,
I doubt adding the warning to Portage's "reported" ones is going to
help, based on the experience of not even being able to get
fortify-sources "will overflow" warnings to be acted upon.

> Finally, it seems that hard work on --as-needed and automatic fixing of
> .la files is going to make the upgrade experience better now, right?

Most definitely, yes. It could have been better, to be honest, but it's
definitely not going to be the many-tiers failure we have seen before.

-- 
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/




      parent reply	other threads:[~2011-02-11 17:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 16:38 [gentoo-dev] libpng-1.5 smooth upgrade "Paweł Hajdan, Jr."
2011-02-11 16:49 ` Samuli Suominen
2011-02-11 19:51   ` Alexis Ballier
2011-02-11 20:07     ` [gentoo-dev] " Diego Elio Pettenò
2011-02-11 20:39       ` Matt Turner
2011-02-11 23:24         ` Duncan
2011-02-11 23:33       ` Alexis Ballier
2011-02-11 23:44         ` Mike Frysinger
2011-02-11 23:56           ` Alexis Ballier
2011-02-24 15:26             ` Enrico Weigelt
2011-02-24 15:47               ` Samuli Suominen
2011-02-26 16:08               ` Enrico Weigelt
2011-02-27 21:51                 ` Rémi Cardona
2011-02-12 23:21   ` [gentoo-dev] " Mike Frysinger
2011-02-12 23:31     ` [gentoo-dev] " Nikos Chantziaras
2011-02-13  2:26       ` Mike Frysinger
2011-02-13  2:37     ` Diego Elio Pettenò
2011-02-13 19:22       ` Mike Frysinger
2011-02-13 20:16         ` [gentoo-dev] " Diego Elio Pettenò
2011-02-13 21:42           ` [gentoo-dev] " Mike Frysinger
2011-02-14 15:37       ` [gentoo-dev] " Alexis Ballier
2011-02-14 18:49         ` Mike Frysinger
2011-02-15  6:37         ` Ryan Hill
2011-02-26 16:11       ` Enrico Weigelt
2011-02-11 17:13 ` [gentoo-dev] " Michael Haubenwallner
2011-02-11 17:26 ` Diego Elio Pettenò [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=1297445165.2150.12.camel@raven.home.flameeyes.eu \
    --to=flameeyes@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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