On Fri, 2021-03-26 at 17:39 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Mar 26, 2021 at 08:42:51AM -0700, Adam Williamson wrote:
> > Can you do a Koji scratch build? This is easier for me to test in
> > openQA (I already have the tooling set up to schedule tests on scr
st "yes"/"no" is already useful.
Can you do a Koji scratch build? This is easier for me to test in
openQA (I already have the tooling set up to schedule tests on scratch
builds, it cannot do it for COPR builds). Thanks!
--
Adam Williamson
and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 Beta prep and status
3. Test Day / community event status
4. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
r how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adam
!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code
and community events.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status
3. Test Day / community event status
4. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter
orrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an ema
On Fri, 2021-03-05 at 01:51 +0100, David Kaufmann wrote:
> On Thu, Mar 04, 2021 at 02:45:29PM -0800, Adam Williamson wrote:
> > Well, you could still argue it's prettier than a wall-o-text boot. And
> > it *does* hide the wall-o-text.
>
> On the first boot after inst
should fix the
> bug of the text splash showing by installing plymouth-system-theme, or the
> server spin does not want a pretty boot and then there should be no
> plymouth at all.
What if we want something arguably-prettier than wall-o-text, but don't
want an extra 32 package
e do?
1) Remove plymouth from @core
2) Add plymouth-system-theme to @core
3) Make Hans/Ray/someone fix the plymouth bug
Opinions? :) Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
_
the same thing as the abidiff failure: the
update changes the ABI. Note that many other files in the package will
have changed, but they're not *all* shown in the test results, just
these specific ones.
The question here is more "should ABI change-type issues be counted as
failures on Rawhide
e_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
F
On Sat, 2021-02-27 at 23:01 -0800, Adam Williamson wrote:
> Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have
> anything urgent this week, and we'll be doing a blocker meeting for F34.
>
> If you're aware of anything important we have to discuss this week,
>
!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code
ker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
tomorrow.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status and Changes
3. Test Day / community event status
4. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw
to this mail
with an agenda and go ahead and run the meeting on Monday.
Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
is a problem.
This cycle it's actually going better, I'd say - we're not at freeze
yet, remember. We've only just branched. Freeze isn't for over a week.
And the kde-settings build happened today. If that does the job, then
I'm fine with the timing.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitte
illion other 'states' that it
would be useful to have info on which aren't relevant to any *one*
existing system, and that's why to me it makes sense to have a separate
thing for that.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
_
edit, which winds up getting reprocessed into that...:D
https://fedorapeople.org/groups/qa/metadata/release.json
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.or
n particular it means that
> the following users/groups are covered:
For the record it's also required by fedora-messaging, which is why
just about everything else in the world needed it :)
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https
Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything urgent this week.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter
it shaky right now, but I think openQA was seeing repeated
Shell crashes up until today's compose - with debug kernels - but with
today's compose (with a non-debug kernel) that doesn't seem to be
happening.
We *do* get a crash during g-i-s right after first boot of the
installed system, though. I'
tomorrow.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status and Changes
3. Criteria proposals, etc.
4. Test Day / community event status
5. Open floor
--
Adam Williamson
stand. This is
> well before the zram module is loaded, by the way.
I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1921923 for
this. zdzichu suggests https://lkml.org/lkml/2021/1/25/701 may be
related.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.ne
On Thu, 2021-01-28 at 10:18 -0800, Adam Williamson wrote:
> On Thu, 2021-01-28 at 14:16 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Jan 28, 2021 at 03:20:38PM +0200, Alexander Bokovoy wrote:
> > > With today's OpenQA tests I can point out that using zram on 2048MB RAM
test that runs a default Fedora Server install:
https://openqa.fedoraproject.org/tests/763650
which, AIUI, should not be creating a swap partition. The logs from the test -
https://openqa.fedoraproject.org/tests/763657/file/role_deploy_domain_contr
On Thu, 2021-01-07 at 09:25 -0800, Adam Williamson wrote:
> Hey folks!
>
> So here's an idea I was thinking about over the RH shutdown: I propose
> we gate stable release critical path updates on the openQA tests.
A further update on this: FESCo has voted on it and approved it:
https
Hi folks! Sorry for the late notice - I'm proposing we cancel the QA
meeting tomorrow. I don't have anything urgent this week.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
--
Adam Williamson
On Fri, 2021-01-22 at 09:57 +0200, Panu Matilainen wrote:
> On 1/21/21 8:37 PM, Adam Williamson wrote:
> > On Thu, 2021-01-21 at 10:53 +0100, Kevin Kofler via devel wrote:
> > > Florian Weimer wrote:
> > > > With rpm-4.15.1-3.fc32.1.x86_64, I get this erro
er.
>
> Considering that direct upgrades from F32 to F34 (n to n+2) are supposed to
> be supported, this sounds like a blocker to me.
openQA N+2 upgrade tests have indeed been running into this for a few
days:
https://openqa.fedoraproject.org/tests/759545#step/upgrade_run/20
I had been meaning to dig
on Monday.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status (inc. GNOME 40)
3. Gating proposals/ideas
4. Test Day / community event status
5. Open floor
--
Adam Williamson
On Thu, 2021-01-14 at 13:21 +0100, Miro Hrončok wrote:
> On 14. 01. 21 13:15, Kevin Kofler via devel wrote:
> > Adam Williamson wrote:
> > > As feedback on this was mostly positive, I went ahead and did the work.
> > > The PR for the Greenwave policy has been m
On Thu, 2021-01-07 at 09:25 -0800, Adam Williamson wrote:
> Hey folks!
>
> So here's an idea I was thinking about over the RH shutdown: I propose
> we gate stable release critical path updates on the openQA tests.
As feedback on this was mostly positive, I went ahead and did the
On Wed, 2021-01-13 at 13:42 -0800, Kevin Fenzi wrote:
> I'm definitely in favor of this effort. ;)
>
> A few questions inline...
>
> On Wed, Jan 13, 2021 at 09:53:36AM -0800, Adam Williamson wrote:
> ...snip...
> >
> > that is all it does. The "releases"
f a state change to change radically - it can
go from being done by a human to being done by system X to being done
by system Y, and all that needs to happen is to ensure the same dead
simple POST request is sent to the same server.
So, what do folks think? Does this seem like a good idea? Shou
tainers
might not bother to do any of those three things, *but* if we disabled
autopush, they *would* check that the updates their update depends on
have gone stable before pushing it stable manually. I'm sceptical that
that is the case.
--
Adam Williamson
Fedora QA
IRC: adamw |
changed Bodhi to precisely your preferred
configuration, I'm gonna posit that maintainers would still manage to
get stuff wrong sometimes. :)
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing li
On Mon, 2021-01-11 at 00:46 +0100, Miro Hrončok wrote:
> On 10. 01. 21 23:25, Matthew Miller wrote:
> > On Sun, Jan 10, 2021 at 02:20:04PM -0800, Adam Williamson wrote:
> > > > All this does is making it again harder to issue bug fixes for the very
> > > > p
to be waiving results for every update, here. It would
be a pretty rare occurrence.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an em
On Sun, 2021-01-10 at 12:44 -0500, Neal Gompa wrote:
> On Sun, Jan 10, 2021 at 12:32 PM Adam Williamson
> wrote:
> >
> > On Sat, 2021-01-09 at 12:27 +0100, Vitaly Zaitsev via devel wrote:
> > > On 08.01.2021 23:24, Matthew Miller wrote:
> > > > I think we
Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't
have anything urgent this week.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter
re permanently broken. For example rpminspect-pipeline -
> filesize.
>
> It's okay when the size of the files in the package changes, but it
> always fails.
That's not an openQA test, so not in the scope of this proposal.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw
an update that isn't tested (this is unusual
but does sometimes happen). Neither of these things happens terribly
often. When one does happen, I treat it as a high priority to get it
fixed or worked around and re-run all non-related tests that were
affected by it.
And, of course, we *can* waive failure
o
waive the failed test first, then push it. See
https://docs.fedoraproject.org/en-US/ci/gating/#_waive .
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscrib
On Fri, 2021-01-08 at 03:08 +0100, Kevin Kofler via devel wrote:
> Adam Williamson wrote:
> > So here's an idea I was thinking about over the RH shutdown: I propose
> > we gate stable release critical path updates on the openQA tests.
>
> -1
>
> We already enfo
On Thu, 2021-01-07 at 22:35 +0100, Miro Hrončok wrote:
> On 07. 01. 21 18:25, Adam Williamson wrote:
> > What do people think of this idea? Any questions? Thanks!
>
> I'd like to see the critpath definition up to date before we do this.
>
> https://pagure.io/releng/issue/89
On Thu, 2021-01-07 at 20:58 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jan 07, 2021 at 09:25:44AM -0800, Adam Williamson wrote:
> > Hey folks!
> >
> > So here's an idea I was thinking about over the RH shutdown: I propose
> > we gate stable release critical
On Thu, 2021-01-07 at 11:23 -0800, Adam Williamson wrote:
> On Thu, 2021-01-07 at 18:48 +, Mattia Verga via devel wrote:
> > Il 07/01/21 18:25, Adam Williamson ha scritto:
> > > ...snip...
> > >
> > > Implementing this would be relatively simple, and wo
On Thu, 2021-01-07 at 18:48 +, Mattia Verga via devel wrote:
> Il 07/01/21 18:25, Adam Williamson ha scritto:
> > ...snip...
> >
> > Implementing this would be relatively simple, and would involve two
> > things: adding some new bits to Fedora's greenwave policy d
On Thu, 2021-01-07 at 09:48 -0800, Kevin Fenzi wrote:
> On Thu, Jan 07, 2021 at 09:25:44AM -0800, Adam Williamson wrote:
> > Hey folks!
> >
> > So here's an idea I was thinking about over the RH shutdown: I propose
> > we gate stable release critical path updates on
email I'll be updating that test and re-running it. That should give
you a flavor of how things go in general.
What do people think of this idea? Any questions? Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
where we're at.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status and Changes
3. Matrix, redux
4. Test Day / community event status
5. Open floor
--
Adam Williamson
as long as both cases exist. If
anything this makes them more fragile: the more divergent paths a tool
has to support, the more likely it is something will break.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
__
On Tue, 2020-12-29 at 18:54 +, Gary Buhrmaster wrote:
> On Tue, Dec 15, 2020 at 11:45 PM Adam Williamson
> wrote:
>
> > I wrote in the update that in my opinion the solution for this bug
> > can't involve expecting add-ons to suddenly get re-signed en masse, o
now:
>
> sudo update-crypto-policies --set FEDORA:32
>
> PS: no need to cc me on posts to the list. :)
It's not that something "didn't reach" Rawhide, either. The NSS
maintainer intends nss in Rawhide to respect the system-wide policy by
default. We need mstransky to patc
opefully
packagers all have a passphrase, so you need the cert and the
passphrase.
The weakest point in the current system is really the FAS password. If
you have a packager's FAS password you can change the ssh key
associated with the account to another that you control, and the FAS
password is also all
ntil new-FAS (based on AAA) is deployed. At that
point I think it would make sense to require packager accounts to have
a second factor, and require that second factor when getting a Kerberos
ticket and when changing the ssh keys on the account.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter:
On Tue, 2020-12-22 at 15:22 -0800, Adam Williamson wrote:
> On Mon, 2020-12-21 at 17:34 -0500, Jonathan Lebon wrote:
> > We've recently started a rawhide "mechanical" stream of Fedora CoreOS
> > (mechanical streams are streams that are meant for developers and that
&g
set openQA up to test this stream too.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproje
lose provenpackager
privileges, which could quite easily be restored if it turned out
they'd just gone on a yak farming retreat for a bit or something.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel maili
of them decided they had a
grudge against Fedora now and were going to have some fun), the results
could be...unfortunate.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.
development going on in OBS (afaik e.g. Igor exported all
> Fedora Rust rpms to OBS for automated rebuilds) and enabling this
> preprocessing will make these packages FTBFS in OBS.
I mean, only if you're sourcing from dist-git?
The .src.rpm will have the post-processed spec file
r
version in git but not built; I bumped it back down to the last version
that was actually built then did the rebuild on top of that, as I don't
know if the newer version (it was an RC) was actually meant to go out
yet, and pemensik's mail is auto-responding as OOO.
--
Adam Williamson
Fedora QA
I
=57780927
Please remember to announce soname bumps ahead of time and arrange
rebuilds of dependencies so this kind of problem can be avoided.
Thanks. I will try and rebuild things, at least compose-critical
things, now, but if straight rebuilds don't work might need people to
help out.
--
Adam
86_64 3.59.0-3.fc33 in today’s updates. Is this fixed or
> are there going to be a lot of unhappy Firefox users?
It's fixed.
> The bug is still open.
Because we still need to do something (or, rather, get Mozilla to do
something) about the underlying situation.
--
Adam
On Wed, 2020-12-16 at 11:18 -0800, Kevin Fenzi wrote:
> On Wed, Dec 16, 2020 at 11:06:45AM -0800, Adam Williamson wrote:
> >
> > See I thought that too at first, and was going to cite it, but then I
> > thought, wait. The problem isn't that the update *actually brok
On Wed, 2020-12-16 at 10:48 -0800, Kevin Fenzi wrote:
> On Wed, Dec 16, 2020 at 10:01:19AM -0800, Adam Williamson wrote:
> > On Wed, 2020-12-16 at 12:37 +0100, Vitaly Zaitsev via devel wrote:
> > > On 15.12.2020 23:29, Miroslav Suchý wrote:
> > > > What you - as Fe
edoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/2629/testReport/(root)/tests/_abidiff/
are OK. I don't know of a known failure case to check it's failing when
it should, though.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
ed of course.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Con
the update
text directly, separate from package commit messages and changelogs.
For me, the description of "this update containing five new package
builds" is completely different from the package-level description of
any one of those new builds.
--
Adam Williamson
Fedora QA
IR
On Tue, 2020-12-15 at 17:59 -0500, Steven A. Falco wrote:
> On 12/15/20 5:09 PM, Adam Williamson wrote:
> > On Tue, 2020-12-15 at 22:38 +0100, Alexander Ploumistos wrote:
> > > On Tue, Dec 15, 2020 at 9:04 PM Alexander Ploumistos
> > > wrote:
> > > >
> &
igned with SHA-1 certs, but nss is now not accepting SHA-1 per the
current system-wide policy.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To un
you sign up for devel@ for *whatever* reason, you find out about
these report emails because they start showing up in your mailbox. If
we move them to a separate list which *won't* be linked all over the
intarwebs, how will people know the reports exist?
--
Adam Williamson
Fedora QA
IRC: adamw | Tw
that
compose you should be OK to install/update. If you want to be sure,
wait another few hours first. The fixed versions are glibc-2.32.9000-
20.fc34 and fprintd-1.90.7-1.fc34 or higher (I think the compose got 8-
1.fc34).
Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https
95 for VFAT, but for ext[234] filesystems it is only limited by
the available space."
I have no idea when is the last time anyone tested this.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing
he 'troubleshooting' menu or
whatever it's labelled there and have it not be the default, rather
than remove it entirely?
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- deve
der construction, of course.)
>
> It was started by the original founder of CentOS with the aim of going back
> to the roots of CentOS, the way it worked before Red Hat started their
> Embrace, Extend, Extinguish scheme.
Off the record...there really wasn't one. It was an Embrace,
Equivocate,
On Wed, 2020-12-09 at 12:02 -0800, Adam Williamson wrote:
> On Wed, 2020-12-09 at 10:34 -0800, Adam Williamson wrote:
> > Hey folks!
> >
> > Just a heads up that the most recent Rawhide compose (20201208.n.0)
> > seems badly broken; console login doesn't work and
On Wed, 2020-12-09 at 10:34 -0800, Adam Williamson wrote:
> Hey folks!
>
> Just a heads up that the most recent Rawhide compose (20201208.n.0)
> seems badly broken; console login doesn't work and 'su' segfaults. I
> think the most likely cause of these issues is the new glibc 2.32.
on updating, and
especially on updating glibc, if you didn't do it already. If you've
updated glibc you may want to downgrade it (if you still have a root
shell somewhere :>)
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.
periodic lumps).
For some folks / maintenance styles this might still be an issue, but
it should work OK in quite a lot of cases. It's not like you're running
Rawhide.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
__
rts for
different things to different places, but they keep breaking because we
keep changing what things we build, what we call them, and how we build
them :/
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel
and I find it usefull to point out
> things.
>
> Perhaps we could keep the traditional rawhide report, but send the
> qa/compose test reports to another list?
BTW, people do actually follow those reports even if they don't reply
to them, because I get pings when they stop working :)
--
Ad
On Sat, 2020-12-05 at 18:49 +0100, Marius Schwarz wrote:
>
> BTW: whats the actual gnome bugzilla?
gitlab.gnome.org .
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list --
n keyboard is actually built
> into gnome-shell nowadays.
The subject says "Fedora 34". So if it's different because of that,
it's not that 33 fixed it compared to what Marius is seeing, but
current Rawhide GNOME has it broken compared to what you're seeing...
--
Adam Wi
oo.
If anyone winds up trying to find out where we decide where to mail
"compose check reports", this is it:
https://pagure.io/fedora-infra/ansible/blob/master/f/inventory/group_vars/checkcompose
checkcompose_emailto would be the thing to change.
--
Adam Williamson
Fedora
those as a local repo and its content
will be available for downgrading. Of course, that server doesn't
expect heavy traffic, so if lots of pinephone people start trying to do
it at once, it might start choking.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassi
On Thu, 2020-12-03 at 15:22 -0500, Colin Walters wrote:
>
> On Thu, Dec 3, 2020, at 2:48 PM, Adam Williamson wrote:
>
> > I dunno when's the last time anyone tried without it, tbh.
>
> For CoreOS we spent a *lot* of time ensuring that Ignition has first class
> SELin
On Thu, 2020-12-03 at 14:43 -0500, Matthew Miller wrote:
> On Thu, Dec 03, 2020 at 11:36:32AM -0800, Adam Williamson wrote:
> > > > (Personally I'm really proud that for example our Live ISO ships with
> > > > SELinux enforcing)
> > > This is true of Fedora Wor
ively restricted what "deployment" means, in terms
of what gets deployed where and how. That gives it quite a big payoff
in various ways in terms of how development and testing and release can
be done. But we really don't have those options for the whole of the
thing called "Fedora", no
esktop spin live ISOs as well.
Yes, but the live installer runs 'setenforce 0' at the start then sets
it back on exit. As long as the live installer is running, you're in
permissive.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://
More or less, yes - but with a key addition: "...and if so, how?"
> >
>
> I feel that we already have the how, Fedora CoreOS has been releasing
> fortnightly for more than a year now.
> So it is a matter of making more widely known how this is done ?
It's a matter of
ing FCOS must at all costs align with
existing processes and schedules, when I was not saying that at all. I
was just trying to outline the situation and the factors that need to
be considered.
I'll reply to the stuff from lower down, where you actually engaged
with what I was actually saying, in
for a few reasons:
I'm pretty sure I covered this in my original mail.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
g
what to do about them.
> How do you consider Rawhide for example ?
Rawhide isn't an edition, which I think should be clear from the
definitions above. Rawhide is sort of the primordial soup from which
Editions and all else eventually emerges, I guess. :P
> >
> > All
on and two
months after Fedora 34 is "released", our "stable" CoreOS is still
Fedora 33-based, that seems like the sort of thing that would look bad.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
t of quiet and undramatic necessarily merits that, especially
if we don't have clear replacements for its capabilities yet.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- deve
nal-go_no_go-meeting.2020-10-22-17.00.log.html
[2]: https://github.com/release-engineering/productmd
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
T
On Tue, 2020-12-01 at 21:30 +, rawh...@fedoraproject.org wrote:
> Announcing the creation of a new nightly release validation test event
> for Fedora 34 Rawhide 20201201.n.0.
A note: this compose still has the systemd crasher bug. The next
compose should have it fixed.
--
Adam Will
901 - 1000 of 6877 matches
Mail list logo
