On 10/28/20 11:21 AM, pmkel...@frontier.com wrote:
I'm guessing that those extra lines are data needed by a process that
sha256sum calls (perhaps gpg), but sha256sum doesn't use them directly.
Otherwise I have no idea what their purpose is.
Those lines have nothing to do with sha256sum. They
On Wed, 2020-10-28 at 17:21 -0400, Ben Cotton wrote:
> I don't blame you one bit here. Part of the issue with this policy is
> enforcement. We have to trust maintainers to submit updates that will
> meet it (and we should trust our maintainers!), but it can be hard to
> tell until it's already in
On Wed, Oct 28, 2020 at 3:48 PM Adam Williamson
wrote:
>
> On Wed, 2020-10-28 at 12:29 -0400, Ben Cotton wrote:
> > In yesterday's F33 emergency brake meeting[1], one of the issues that
> > came up is the short window for testing all of the different IoT
> > hardware. One way to reduce that effort
On Wed, Oct 28, 2020 at 12:22 PM pmkel...@frontier.com
wrote:
>
>
>
> On 10/28/20 11:44, Ankur Sinha wrote:
> > On Wed, Oct 28, 2020 11:21:07 -0400, pmkel...@frontier.com wrote:
> >> Are you saying that the warning message about the 19 lines is a don't care
> >> or is their a problem with the way
On Wed, Oct 28, 2020 at 12:46:55PM -0700, Adam Williamson wrote:
> (mainly I)
While I appreciate all of this taking-of-responsiblity and stuff, let's
focus on the process. There are plenty of places where anyone can make
decisions (or fail to consider something) and then in retrospect it was
obvio
On Wed, 2020-10-28 at 12:29 -0400, Ben Cotton wrote:
> In yesterday's F33 emergency brake meeting[1], one of the issues that
> came up is the short window for testing all of the different IoT
> hardware. One way to reduce that effort (by extending the window) is
> reducing the change set in the day
On 10/28/20 11:44, Ankur Sinha wrote:
On Wed, Oct 28, 2020 11:21:07 -0400, pmkel...@frontier.com wrote:
Are you saying that the warning message about the 19 lines is a don't care
or is their a problem with the way the checksum file is made? Does this mean
that the OK message that comes first i
On Wed, Oct 28, 2020 at 10:31 AM Ben Cotton wrote:
>
> In yesterday's F33 emergency brake meeting[1], one of the issues that
> came up is the short window for testing all of the different IoT
> hardware. One way to reduce that effort (by extending the window) is
> reducing the change set in the da
On Wed, 28 Oct 2020 11:21:07 -0400, pmkel...@frontier.com wrote:
> Are you saying that the warning message about the 19 lines is a don't
> care or is their a problem with the way the checksum file is made? Does
> this mean that the OK message that comes first is in error?
Just display the check
No missing expected images.
Failed openQA tests: 1/16 (x86_64)
New failures (same test not failed in Fedora-IoT-33-20201020.0):
ID: 708917 Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/708917
Soft failed openQA tests: 1/16 (x86_64)
(Test
In yesterday's F33 emergency brake meeting[1], one of the issues that
came up is the short window for testing all of the different IoT
hardware. One way to reduce that effort (by extending the window) is
reducing the change set in the days before an RC. I don't know if it
would have helped in this
no idea regarding CINNAMON.
under Genome:
- Settings => "Region & Languages" => "Input Source" => "+"
- delete the US keyboard
- logoff/-on ?
?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedor
On Wed, Oct 28, 2020 11:21:07 -0400, pmkel...@frontier.com wrote:
> Are you saying that the warning message about the 19 lines is a don't care
> or is their a problem with the way the checksum file is made? Does this mean
> that the OK message that comes first is in error?
I guess you could call i
On 10/28/20 11:07, Ankur Sinha wrote:
On Wed, Oct 28, 2020 10:55:28 -0400, pmkel...@frontier.com wrote:
On 10/28/20 10:16, Ankur Sinha wrote:
I think sha256sum is pointing out the 19 lines related to the PGP
Signature in the CHECKSUM file, which it can't understand.
https://getfedora.org/s
On Wed, Oct 28, 2020 10:55:28 -0400, pmkel...@frontier.com wrote:
> On 10/28/20 10:16, Ankur Sinha wrote:
>
> >
> > I think sha256sum is pointing out the 19 lines related to the PGP
> > Signature in the CHECKSUM file, which it can't understand.
> >
> > https://getfedora.org/static/checksums/Fedo
On 10/28/20 10:16, Ankur Sinha wrote:
On Wed, Oct 28, 2020 09:32:51 -0400, pmkel...@frontier.com wrote:
I wanted a fresh copy of the F33 ISO to use for the PCs I maintain. I went
to the getfedora.org site. and downloaded the ISO and CHECKSUM files for F33
Workstation.
When I run:
sha256sum -
On Wed, Oct 28, 2020 09:32:51 -0400, pmkel...@frontier.com wrote:
> I wanted a fresh copy of the F33 ISO to use for the PCs I maintain. I went
> to the getfedora.org site. and downloaded the ISO and CHECKSUM files for F33
> Workstation.
>
> When I run:
>
> sha256sum -c Fedora-Workstation-live-33-
I wanted a fresh copy of the F33 ISO to use for the PCs I maintain. I
went to the getfedora.org site. and downloaded the ISO and CHECKSUM
files for F33 Workstation.
When I run:
sha256sum -c Fedora-Workstation-live-33-1;2-x86_64-CHECKSUM
I get:
Fedora-Workstation-live-x86_64-33-1.2.iso: OK
B
Missing expected images:
Xfce raw-xz armhfp
Compose FAILS proposed Rawhide gating check!
7 of 43 required tests failed, 1 result missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 35/181 (x86_64)
New failures (same test not failed in
OLD: Fedora-Rawhide-20201027.n.0
NEW: Fedora-Rawhide-20201028.n.0
= SUMMARY =
Added images:67
Dropped images: 0
Added packages: 6
Dropped packages:0
Upgraded packages: 150
Downgraded packages: 0
Size of added packages: 3.92 MiB
Size of dropped packages:0
No missing expected images.
Passed openQA tests: 7/7 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproj
Hi guys,
I upgraded almost successfully from F32 to F33, using dnf.
Before the upgrade action, my Keyboard was German, with no deadkeys as
option, in all Fedora versions.
But now, each time I logout and relogin, my keyboard is reset to an STD
US keyboard.
Is this a known issue?
I am running
No missing expected images.
Soft failed openQA tests: 1/7 (x86_64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-33-20201027.0):
ID: 708386 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproj
23 matches
Mail list logo
