From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Future of gentoo's stable and unstable trees: what are your thoughts?
Date: Tue, 25 Jul 2017 15:36:56 +0200 [thread overview]
Message-ID: <1500989816.4544.88.camel@gentoo.org> (raw)
In-Reply-To: <10267d25-547b-cbe1-7fdd-40200e7bae4b@gentoo.org>
El mar, 25-07-2017 a las 23:10 +1000, Michael Palimaka escribió:
> On 07/25/2017 05:22 PM, Dirkjan Ochtman wrote:
> > First, the assumption in our processes seems to be that many or
> > important bugs will be due to architecture-specific differences, and I
> > wonder if that assumption really holds up. Do arch testers for a smaller
> > arch often find problems that were not noticed on one of the larger
> > arches? With the languages and tools that we have today, it seems like
> > for many of our packages, bugs due to architectural differences
> > represent a minority of the problems we found. In this case, the whole
> > idea of per-arch stabilization does not really make sense, and doing
> > away with that idea could drastically shortcut our process.
>
> This would be really interesting to know.
Anyway, I think it depends on the arch you are running. I remember to have seen
specific issues for ia64, hppa, ppc64 or arm. But, for example, I agree that,
*at present time*, I don't remember to have seen a package failing on x86 and
not on amd64 for example (well, I now remember a past systemd upstream runtime
bug that was catched in testing period ;)).
Then, I guess it depends on each arch. For example, for x86 it could be probably
done if things work on amd64 :/. Between ppc and ppc64 I don't know. For the
others, I don't think that we can extrapolate between amd64 and ia64 for example
(I remember important runtime issues to be catched only affecting ia64 for
example).
next prev parent reply other threads:[~2017-07-25 13:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 21:22 [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? Sergei Trofimovich
2017-07-24 21:52 ` [gentoo-dev] " Pacho Ramos
2017-07-24 23:22 ` [gentoo-dev] " Peter Stuge
2017-07-24 23:52 ` Rich Freeman
2017-07-25 4:34 ` [gentoo-dev] " Duncan
2017-07-25 6:26 ` Hans de Graaff
2017-07-25 6:18 ` [gentoo-dev] " Hans de Graaff
2017-07-25 9:18 ` Pacho Ramos
2017-07-25 11:54 ` Michał Górny
2017-07-25 12:15 ` Pacho Ramos
2017-07-25 13:19 ` Michał Górny
2017-07-25 13:23 ` Pacho Ramos
2017-07-25 11:26 ` Rich Freeman
2017-07-25 7:44 ` Sergei Trofimovich
2017-07-28 10:44 ` Andreas K. Huettel
2017-07-28 12:45 ` Marek Szuba
2017-07-28 13:10 ` Sam Jorna (wraeth)
2017-07-28 19:59 ` William L. Thomson Jr.
2017-07-28 21:21 ` David Seifert
2017-07-31 0:28 ` Sam Jorna
2017-07-31 0:40 ` Benda Xu
2017-07-31 2:44 ` William L. Thomson Jr.
2017-07-31 2:56 ` Sam Jorna
2017-07-31 15:00 ` William L. Thomson Jr.
2017-07-31 12:59 ` Andreas K. Huettel
2017-07-31 14:43 ` William L. Thomson Jr.
2017-07-31 14:47 ` David Seifert
2017-07-28 19:44 ` Alec Warner
2017-07-29 1:05 ` Rich Freeman
2017-07-31 14:52 ` Alec Warner
2017-07-31 15:11 ` Rich Freeman
2017-07-31 16:51 ` Peter Volkov
2017-08-01 0:24 ` [gentoo-dev] " Duncan
2017-08-01 0:55 ` Rich Freeman
2017-08-01 1:45 ` Duncan
2017-07-31 16:44 ` [gentoo-dev] " Michał Górny
2017-07-29 4:18 ` Daniel Campbell
2017-07-29 16:41 ` Mart Raudsepp
2017-07-29 19:10 ` David Seifert
2017-07-29 18:03 ` Andrew Savchenko
2017-07-25 7:22 ` Dirkjan Ochtman
2017-07-25 13:10 ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:22 ` Rich Freeman
2017-07-25 20:16 ` Daniel Campbell
2017-07-25 13:36 ` Pacho Ramos [this message]
2017-07-25 14:15 ` Peter Stuge
2017-07-29 18:08 ` [gentoo-dev] " Christopher Head
2017-07-31 6:49 ` R0b0t1
2017-07-25 9:03 ` [gentoo-dev] " Agostino Sarubbo
2017-07-25 19:45 ` Markus Meier
2017-07-25 20:12 ` Rich Freeman
2017-07-26 5:49 ` Hans de Graaff
2017-07-25 12:59 ` Michael Palimaka
2017-07-25 13:30 ` Pacho Ramos
2017-07-25 13:51 ` Michał Górny
2017-07-25 14:13 ` [gentoo-dev] " Michał Górny
2017-07-25 14:28 ` Rich Freeman
2017-07-27 23:12 ` Denis Dupeyron
2017-07-27 23:41 ` Rich Freeman
2017-07-28 0:03 ` Denis Dupeyron
2017-07-28 21:24 ` William Hubbs
2017-07-29 10:24 ` Andrew Savchenko
2017-07-28 20:10 ` William L. Thomson Jr.
2017-07-28 21:12 ` A. Wilcox
2017-07-28 21:41 ` William L. Thomson Jr.
2017-07-29 13:41 ` Andreas K. Huettel
2017-07-28 21:45 ` [gentoo-dev] " Duncan
2017-07-28 21:56 ` William L. Thomson Jr.
2017-07-29 19:44 ` Walter Dnes
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=1500989816.4544.88.camel@gentoo.org \
--to=pacho@gentoo.org \
--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