Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread Chris Murphy
On Fri, Jan 21, 2022 at 3:54 PM Adam Williamson wrote: > > The release criteria aren't design documents. We're not defining the > intended behavior, exactly; we're defining a certain subset of known > expected behavior which we require to *work*. > > The situations you describe are, essentially, "

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread Adam Williamson
On Fri, 2022-01-21 at 18:20 -0500, John Mellor wrote: > > Ok, so would that allowance not violate 2 of the proposed criteria: > > 1. * The displayed state of software or software sources must not > differ from their actual state. (E.g. an RPM package must not be > shown as installed when

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread Adam Williamson
On Thu, 2022-01-20 at 14:17 -0500, John Mellor wrote: > The suggested criteria list is pretty generic, and offhand I can't think > of a current GUI or CLI installer that does not conform to these > requirements. Just before Fedora 35 was released, the KDE package manager did not conform to sever

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread John Mellor
On 2022-01-21 5:54 p.m., Adam Williamson wrote: On Fri, 2022-01-21 at 14:20 -0500, John Mellor wrote: I am unclear from this proposal on what is supposed to happen if a package is not completely installed.  E.g: a powerdown or other outage causes the post-install script in an installed rpm to n

Fedora-Rawhide-20220120.n.1 compose check report

2022-01-21 Thread Fedora compose checker
No missing expected images. Compose FAILS proposed Rawhide gating check! 4 of 43 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 15/225 (x86_64), 17/157 (aarch64) New failures (same test not failed i

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread Adam Williamson
On Thu, 2022-01-20 at 17:54 +0100, Kamil Paral wrote: > This is another attempt at creating a new release criterion specific for > graphical package managers. We already discussed it in November, but we > couldn't agree easily on some particular details, and then I was gone for a > long time: > htt

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread Adam Williamson
On Fri, 2022-01-21 at 14:20 -0500, John Mellor wrote: > > > I am unclear from this proposal on what is supposed to happen if a > package is not completely installed.  E.g: a powerdown or other outage > causes the post-install script in an installed rpm to not be run.  A few > packages like the

Re: new criterion proposal: Graphical package managers (take #2)

2022-01-21 Thread John Mellor
On 2022-01-20 11:54 a.m., Kamil Paral wrote: This is another attempt at creating a new release criterion specific for graphical package managers. We already discussed it in November, but we couldn't agree easily on some particular details, and then I was gone for a long time: https://lists.fed

Fedora rawhide compose report: 20220120.n.1 changes

2022-01-21 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20220119.n.0 NEW: Fedora-Rawhide-20220120.n.1 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 8 Dropped packages:0 Upgraded packages: 129 Downgraded packages: 0 Size of added packages: 345.21 MiB Size of dropped packages:0

Re: Proposal: revise "Default application functionality" final criterion to be clearer

2022-01-21 Thread Ben Cotton
On Thu, Jan 20, 2022 at 7:10 PM Adam Williamson wrote: > > Thoughts? Is this an improvement? Anyone have a better idea? Thanks! This is a definite improvement. I agree with Kamil's comment about including the "graphically" wording. It might be unnecessarily pedantic, but our future selves may app

Re: Proposal: revise "Default application functionality" final criterion to be clearer

2022-01-21 Thread pmkel...@frontier.com
On 1/20/22 19:08, Adam Williamson wrote: Hi folks! So I've had this action item at meetings forever now: "adamw to try and clarify intent of "default application functionality" criterion regarding arches" For all release-blocking desktop / arch combinations, the following applications mu

Re: Proposal: revise "Default application functionality" final criterion to be clearer

2022-01-21 Thread Kamil Paral
On Fri, Jan 21, 2022 at 1:11 AM Adam Williamson wrote: > Hi folks! So I've had this action item at meetings forever now: > > "adamw to try and clarify intent of "default application functionality" > criterion regarding arches" > > That's referring to > > https://fedoraproject.org/wiki/Fedora_35_F

Fedora-Cloud-34-20220121.0 compose check report

2022-01-21 Thread Fedora compose checker
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20220120.0): ID: 1109861 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Fedora-Cloud-35-20220121.0 compose check report

2022-01-21 Thread Fedora compose checker
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20220120.0): ID: 1109845 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op