Re: [Proposal] The dual head set-up criterion

[Chris Murphy]

On Thu, Apr 1, 2021 at 1:12 PM Ben Cotton  wrote:
>
> On Tue, Mar 30, 2021 at 7:27 AM Lukas Ruzicka  wrote:
> >
> > I would like to propose a new release covering criterion that was suggested 
> > on the yesterday's Blocker Review Meeting. Please let me know, what you 
> > think about it and perhaps suggest improvements.
> >
>
> I like the idea of dual monitors being a blocker in general, but as
> this thread shows, it gets complicated quickly. I think if we do this,
> it should be very narrowly scoped. The two main use cases we need to
> worry about are:
>
> 1. Laptop with an external monitor (and does it have to be directly
> attached, or would we block if a monitor attached via a docking
> station doesn't work?)
> 2. Desktop with a single video card that drives two monitors
>
> I suspect that this would cover most usage without getting too caught
> up in all of the possible hardware combinations, especially since one
> major video card manufacturer isn't the best at supporting Linux.
>

I agree.


-- 
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: /boot on btrfs

[Chris Murphy]

On Thu, Apr 1, 2021 at 10:18 AM Proprietary Chrome-chan
 wrote:
>
> Hi,
>
> `/boot` can be used on btrfs. However, Anaconda forces me to use ext4 in that 
> specific, when it shouldn't if you use btrfs.
>
> I'd like to request allowing `/boot` to be used on btrfs.

You can do this in Custom partitioning, if you fiddle with it enough.
However... I recommend you create a 1-2G Btrfs boot outside of the
installer. The installer will let you assign it to the /boot mount
point without reformatting it.

The reason is it's better to use the 'mkfs.btrfs --mixed' option for
file systems of this size.

-- 
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Touchpad multi-touch not working in Fedora 34

[super cow]

Here are some terminal outputs:

$ dmesg | grep -i touchpad
[3.757914] psmouse serio1: synaptics: Touchpad model: 1, fw: 6.3, id:
0x180b1, caps: 0xa04711/0xa0/0x0/0x0, board id: 0, fw id: 436772
[3.826925] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio1/input/input6



$ sudo libinput list-devices
Device:   SynPS/2 Synaptics TouchPad
Kernel:   /dev/input/event7
Group:9
Seat: seat0, default
Size: 51x23mm
Capabilities: pointer
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock:disabled
Left-handed:  disabled
Nat.scrolling:disabled
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   *edge
Click methods:none
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation: n/a
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Fedora 34 Silverblue] Bluetooth not working anymore

[Proprietary Chrome-chan]

I have installed Fedora 34 Silverblue a couple of days ago in my laptop, but 
Bluetooth isn't working anymore on GNOME Settings.

It worked fine on Fedora 33 Workstation, but not anymore on 34 Silverblue.

When I use `bluetoothctl`, I get the following:

```
$ bluetoothctl 
[bluetooth]# scan on 
Failed to start discovery: org.bluez.Error.NotReady
```

I check if bluez is installed:

```
$ rpm-ostree install bluez
error: "bluez" is already provided by: bluez-5.56-4.fc34.x86_64. Use 
--allow-inactive to explicitly require it.
```

May I get some assistance?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: /boot on btrfs

[FUNG Chi Chuen Sampson]

Anaconda do not complain about /boot partition using btrfs, as tested with 
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-34-20210401.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-34-20210401.n.0.iso

Testing steps:

1.  Boot the USB
2.  Choose Custom Storager
3.  Remove All existing partitions
4.  By using the default btrfs scheme, choose to create the default layout
5.  Edit /boot, change type to btrfs
6.  Result:
- /dev/sda1 - 1GB, btrfs
- /dev/sda2 - 180GB, btrfs
* subvol /
* subvol /home
(It is on a legacy BIOS system, so no EFI partition created.)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora Linux 34 Final blocker status update #3

[Adam Williamson]

On Thu, 2021-04-01 at 14:56 -0400, Ben Cotton wrote:
> 
> 1.  gdm — https://bugzilla.redhat.com/show_bug.cgi?id=1942443 — NEW
> Login using password failed after upgrade to Fedora 34
> 
> When a device has a fingerprint reader, but no fingerprints are
> enrolled, login fails on the default terminal. Switching to a
> different virtual console allows login. Removing fprintd-pam resolves
> the problem, but is probably not the solution we want. It may be that
> modifications of nsswitch.conf outside of authselect cause fprintd to
> get unexpected failures from authselect.

Just to clarify this one a bit: AIUI, this is the same bug we fixed
earlier in the cycle, but it's still a problem after update to the
'fixed' package for some people. It seems to affect two scenarios:

1. Very old installs, from a release where we had authconfig not
authselect, that have been upgraded all the way to F34
2. Installs where /etc/nsswitch.conf has been modified in any way
except via authselect, so authselect won't apply changes to it any more

I believe benzea is planning to try and solve this by having the
package make the specific change to the configuration that's necessary,
in affected cases. We think that just making this specific change in a
package scriptlet should be pretty safe, it shouldn't be able to break
any odd configuration we can think of.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Important notice !!! To All Outreachy Fedora QA Dashboard Candidates

[Alisina Bolourchi]

Dear All Candidates,

I am Alisina Bolourchi and outreachy candidates too working on dashboard
yesterday I spoke with @lbra...@redhat.com   He told me
All candidates can work on the tickets as they like then they will compare
pulls and pick the best so no one owns a ticket it is a professional duty
to let you know as you know communication is the key in programming.

Kind Regards,

Alisina Bolourchi
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: dnf install Errors during downloading metadata for repository 'updates-testing-modular'

[Samuel Sieb]

On 4/1/21 8:25 AM, wang_chen wrote:

dnf -y groupinstall "C Development Tools and Libraries" "Development Tools"

Fedora Modular 34 - x86_64 - Test Updates   

  80 kB/s | 105 kB 00:01
Errors during downloading metadata for repository 'updates-testing-modular':
   - Zchunk error: Unable to find multipart download range

错误：Failed to download metadata for repo 'updates-testing-modular': Yum repo 
downloading error: Downloading error: Unable to initialize zchunk file 
repodata/b9f6f1d6b10734076777b6619ed2e198a21f480f46617393074748a43db739f3-primary.xml.zck:
 Unable to set zchunk file descriptor for 
repodata/b9f6f1d6b10734076777b6619ed2e198a21f480f46617393074748a43db739f3-primary.xml.zck:
 Unable to find multipart download range


I don't know the cause of this error, maybe the repo wasn't completely 
synced.  But this is just a warning.  Everything will still work, it 
just might have to download more.

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Upgrade on F34 -> F34 on x11 utils split

[Neal Gompa]

Hey all,

I attempted to do a distro-sync to upgrade my system to latest F34
pre-release packages, but I got the following error:

Error: Transaction test error:
  file /usr/bin/iceauth conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
iceauth-1.0.8-1.fc34.x86_64
  file /usr/bin/sessreg conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
sessreg-1.1.2-1.fc34.x86_64
  file /usr/bin/xgamma conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xgamma-1.0.6-1.fc34.x86_64
  file /usr/bin/xhost conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and xhost-1.0.7-1.fc34.x86_64
  file /usr/bin/xinput conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xinput-1.6.3-1.fc34.x86_64
  file /usr/bin/xkill conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and xkill-1.0.5-1.fc34.x86_64
  file /usr/bin/xmodmap conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xmodmap-1.0.9-1.fc34.x86_64
  file /usr/bin/xrandr conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xrandr-1.5.1-1.fc34.x86_64
  file /usr/bin/xrdb conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and xrdb-1.1.1-1.fc34.x86_64
  file /usr/bin/xrefresh conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xrefresh-1.0.6-1.fc34.x86_64
  file /usr/bin/xset conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and xset-1.2.4-1.fc34.x86_64
  file /usr/bin/xsetroot conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xsetroot-1.1.2-1.fc34.x86_64
  file /usr/bin/xstdcmap conflicts between attempted installs of
xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xstdcmap-1.0.4-1.fc34.x86_64
  file /usr/share/man/man1/sessreg.1.gz conflicts between attempted
installs of xorg-x11-server-utils-7.7-39.fc34.x86_64 and
sessreg-1.1.2-1.fc34.x86_64
  file /usr/share/man/man1/xrandr.1.gz conflicts between attempted
installs of xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xrandr-1.5.1-1.fc34.x86_64
  file /usr/share/man/man1/xstdcmap.1.gz conflicts between attempted
installs of xorg-x11-server-utils-7.7-39.fc34.x86_64 and
xstdcmap-1.0.4-1.fc34.x86_64

Seems we're not properly handling the package split in F34?

-- 
真実はいつも一つ！/ Always, there's only one truth!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] The dual head set-up criterion

[Ben Cotton]

On Tue, Mar 30, 2021 at 7:27 AM Lukas Ruzicka  wrote:
>
> I would like to propose a new release covering criterion that was suggested 
> on the yesterday's Blocker Review Meeting. Please let me know, what you think 
> about it and perhaps suggest improvements.
>

I like the idea of dual monitors being a blocker in general, but as
this thread shows, it gets complicated quickly. I think if we do this,
it should be very narrowly scoped. The two main use cases we need to
worry about are:

1. Laptop with an external monitor (and does it have to be directly
attached, or would we block if a monitor attached via a docking
station doesn't work?)
2. Desktop with a single video card that drives two monitors

I suspect that this would cover most usage without getting too caught
up in all of the possible hardware combinations, especially since one
major video card manufacturer isn't the best at supporting Linux.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Linux 34 Final blocker status update #3

[Ben Cotton]

The F34 Final freeze begins on Tuesday 6 April.

Action summary


Accepted blockers
-
1. sddm — logout after switch returns the user to console instead of sddm — NEW
ACTION: sddm maintainers to diagnose and fix issue

2. shim — include new bootloaders on Fedora 34 install media so UEFI
Secure Boot enabled systems can boot from them — ASSIGNED
ACTION: shim maintainers to provide shim signed with new key

3. plasma-discover — Hitting "Update All" in Plasma Discover sometimes
does nothing, just cycles back — NEW
ACTION: plasma-discover maintainers to diagnose and fix issue


Proposed blockers
-

1. gdm — Login using password failed after upgrade to Fedora 34 — NEW
ACTION: gdm maintainers to diagnose and fix issue


Bug-by-bug detail
=

Accepted blockers
-
1. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1929643 — NEW
logout after switch returns the user to console instead of sddm

Using the "Switch User" functionality in sddm results in dropping to a
console: either to tty2 with a working text login prompt, or to tty1
where only a blinking cursor appears (no login prompt). This may be
limited to Wayland sessions.

2. shim — https://bugzilla.redhat.com/show_bug.cgi?id=1938630 — ASSIGNED
include new bootloaders on Fedora 34 install media so UEFI Secure Boot
enabled systems can boot from them

The current shim was signed in 2018 and its signing key was revoked
last year due to the Boothole vulnerability. We need a new shim to
make sure F34 images will boot on machines with Secure Boot enabled.

3. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=1943943 — NEW
Hitting "Update All" in Plasma Discover sometimes does nothing, just cycles back

It takes several clicks of the "Update All" button before Discover
updates packages. This may actually be a PackageKit issue, as AdamW
observed issues with the GNOME tests, too.

Proposed blockers
-

1.  gdm — https://bugzilla.redhat.com/show_bug.cgi?id=1942443 — NEW
Login using password failed after upgrade to Fedora 34

When a device has a fingerprint reader, but no fingerprints are
enrolled, login fails on the default terminal. Switching to a
different virtual console allows login. Removing fprintd-pam resolves
the problem, but is probably not the solution we want. It may be that
modifications of nsswitch.conf outside of authselect cause fprintd to
get unexpected failures from authselect.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

/boot on btrfs

[Proprietary Chrome-chan]

Hi,

`/boot` can be used on btrfs. However, Anaconda forces me to use ext4 in that 
specific, when it shouldn't if you use btrfs.

I'd like to request allowing `/boot` to be used on btrfs.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-34-20210401.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 4/178 (x86_64), 6/127 (aarch64)

New failures (same test not failed in Fedora-34-20210330.n.0):

ID: 839705  Test: x86_64 universal install_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/839705
ID: 839766  Test: aarch64 universal install_simple_free_space@uefi
URL: https://openqa.fedoraproject.org/tests/839766
ID: 839767  Test: aarch64 universal install_anaconda_text@uefi
URL: https://openqa.fedoraproject.org/tests/839767
ID: 839774  Test: aarch64 universal install_blivet_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/839774
ID: 839789  Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/839789
ID: 839800  Test: aarch64 universal upgrade_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/839800

Old failures (same test failed in Fedora-34-20210330.n.0):

ID: 839577  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/839577
ID: 839581  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/839581
ID: 839682  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/839682
ID: 839757  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/839757

Soft failed openQA tests: 6/127 (aarch64), 4/178 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-34-20210330.n.0):

ID: 839786  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/839786

Old soft failures (same test soft failed in Fedora-34-20210330.n.0):

ID: 839504  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/839504
ID: 839545  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/839545
ID: 839591  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/839591
ID: 839597  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/839597
ID: 839610  Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/839610
ID: 839635  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/839635
ID: 839650  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/839650
ID: 839672  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/839672
ID: 839731  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/839731

Passed openQA tests: 170/178 (x86_64), 115/127 (aarch64)

New passes (same test not passed in Fedora-34-20210330.n.0):

ID: 839550  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/839550
ID: 839576  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/839576
ID: 839598  Test: aarch64 Minimal-raw_xz-raw.xz release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/839598
ID: 839599  Test: aarch64 Minimal-raw_xz-raw.xz base_system_logging@uefi
URL: https://openqa.fedoraproject.org/tests/839599
ID: 839600  Test: aarch64 Minimal-raw_xz-raw.xz base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/839600
ID: 839601  Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/839601
ID: 839602  Test: aarch64 Minimal-raw_xz-raw.xz base_selinux@uefi
URL: https://openqa.fedoraproject.org/tests/839602
ID: 839603  Test: aarch64 Minimal-raw_xz-raw.xz 
base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/839603
ID: 839604  Test: aarch64 Minimal-raw_xz-raw.xz base_reboot_unmount@uefi
URL: https://openqa.fedoraproject.org/tests/839604
ID: 839617  Test: aarch64 Server-dvd-iso 
install_repository_hd_variation@uefi
URL: https://openqa.fedoraproject.org/tests/839617
ID: 839620  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/839620
ID: 839621  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/839621
ID: 839626  Test: aarch64 Server-dvd-iso base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/839626
ID: 839633  Test: aarch64 Server-dvd-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/839633
ID: 839636  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/839636
ID: 839638  Test: aarch64 

Re: Fedora 32: Python 3.8.8

[Miro Hrončok]

> Hello,
> we have updated the main Python from 3.8.7 to 3.8.8 in Fedora 32, but since 
> this 
> never went trough rawhide or Fedora 33 (already at 3.9), I wanted it to 
> receive 
> some karma before pushing the update.
> 
> However, after 14 days, it only gained +2.
> 
> If you run Fedora 32, please update Python from updates-testing and after a 
> few 
> days, report back via karma if your system is fully functional. Thanks.
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-88d9d29680

This is still a valid request for help. Thanks.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Outreachy'21 participant Introduction

[059_Rimpi Rani Baruah]

Hello everyone, I am Rimpi Rani Baruah... I am a Btech sophomore in Civil
Engineering in NIT Silchar, India.. My interests include web development
and Blockchain technology. I am a newbie in FOSS and I am quite excited to
be a part of the Developing QA dashboard project and make my learning curve
grow and be involved in the community whatever way I can.. Thank you :)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

dnf install Errors during downloading metadata for repository 'updates-testing-modular'

[wang_chen]

dnf -y groupinstall "C Development Tools and Libraries" "Development Tools"

Fedora Modular 34 - x86_64 - Test Updates   

  80 kB/s | 105 kB 00:01
Errors during downloading metadata for repository 'updates-testing-modular':
  - Zchunk error: Unable to find multipart download range

错误：Failed to download metadata for repo 'updates-testing-modular': Yum repo 
downloading error: Downloading error: Unable to initialize zchunk file 
repodata/b9f6f1d6b10734076777b6619ed2e198a21f480f46617393074748a43db739f3-primary.xml.zck:
 Unable to set zchunk file descriptor for 
repodata/b9f6f1d6b10734076777b6619ed2e198a21f480f46617393074748a43db739f3-primary.xml.zck:
 Unable to find multipart download range
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 compose report: 20210401.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-34-20210330.n.0
NEW: Fedora-34-20210401.n.0

= SUMMARY =
Added images:20
Dropped images:  1
Added packages:  8
Dropped packages:9
Upgraded packages:   134
Downgraded packages: 0

Size of added packages:  32.06 MiB
Size of dropped packages:173.43 MiB
Size of upgraded packages:   3.27 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -14.11 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-34-20210401.n.0.s390x.tar.xz
Image: Container_Base docker armhfp
Path: 
Container/armhfp/images/Fedora-Container-Base-34-20210401.n.0.armhfp.tar.xz
Image: Design_suite live x86_64
Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-34-20210401.n.0.iso
Image: Container_Base docker s390x
Path: Container/s390x/images/Fedora-Container-Base-34-20210401.n.0.s390x.tar.xz
Image: Container_Minimal_Base docker armhfp
Path: 
Container/armhfp/images/Fedora-Container-Minimal-Base-34-20210401.n.0.armhfp.tar.xz
Image: Container_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Base-34-20210401.n.0.ppc64le.tar.xz
Image: Container_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Base-34-20210401.n.0.aarch64.tar.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-34-20210401.n.0.ppc64le.tar.xz
Image: Container_Minimal_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Minimal-Base-34-20210401.n.0.aarch64.tar.xz
Image: Mate live x86_64
Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-34-20210401.n.0.iso
Image: Container_Base docker x86_64
Path: 
Container/x86_64/images/Fedora-Container-Base-34-20210401.n.0.x86_64.tar.xz
Image: Container_Minimal_Base docker x86_64
Path: 
Container/x86_64/images/Fedora-Container-Minimal-Base-34-20210401.n.0.x86_64.tar.xz
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Server-netinst-s390x-34-20210401.n.0.iso
Image: Cinnamon live x86_64
Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-34-20210401.n.0.iso
Image: Xfce raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Xfce-34-20210401.n.0.armhfp.raw.xz
Image: SoaS raw-xz armhfp
Path: Spins/armhfp/images/Fedora-SoaS-34-20210401.n.0.armhfp.raw.xz
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-34-20210401.n.0.aarch64.raw.xz
Image: SoaS raw-xz aarch64
Path: Spins/aarch64/images/Fedora-SoaS-34-20210401.n.0.aarch64.raw.xz
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Server-dvd-s390x-34-20210401.n.0.iso
Image: Cloud_Base tar-gz x86_64
Path: Cloud/x86_64/images/Fedora-Cloud-Base-GCP-34-20210401.n.0.x86_64.tar.gz

= DROPPED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-34-20210330.n.0.iso

= ADDED PACKAGES =
Package: centpkg-0.5.1-2.fc34
Summary: CentOS utility for working with dist-git
RPMs:centpkg centpkg-sig
Size:36.72 KiB

Package: gr-funcube-1.0.0-1.fc34
Summary: GNURadio support for FUNcube Dongle Pro and FUNcube Dongle Pro+
RPMs:gr-funcube gr-funcube-devel gr-funcube-doc
Size:3.02 MiB

Package: guestfs-tools-1.45.2-6.fc34
Summary: Tools to access and modify virtual machine disk images
RPMs:guestfs-tools guestfs-tools-bash-completion guestfs-tools-man-pages-ja 
guestfs-tools-man-pages-uk virt-dib virt-win-reg
Size:22.18 MiB

Package: kirigami-gallery-20.12.3-1.fc34
Summary: Gallery application built using Kirigami
RPMs:kirigami-gallery
Size:1.35 MiB

Package: mcrouter-0.41.0-2.20210326git254a127.fc34
Summary: Memcached protocol router for scaling memcached deployments
RPMs:mcrouter
Size:5.13 MiB

Package: ocaml-caml-mode-4.06-1.fc34
Summary: Opam file for caml-mode
RPMs:emacs-caml-mode ocaml-caml-mode
Size:128.04 KiB

Package: rust-tokio-stream-0.1.5-1.fc34
Summary: Utilities to work with Stream and tokio
RPMs:rust-tokio-stream+default-devel rust-tokio-stream+fs-devel 
rust-tokio-stream+io-util-devel rust-tokio-stream+net-devel 
rust-tokio-stream+signal-devel rust-tokio-stream+sync-devel 
rust-tokio-stream+time-devel rust-tokio-stream+tokio-util-devel 
rust-tokio-stream-devel
Size:99.12 KiB

Package: rust-warp0.2-0.2.5-1.fc34
Summary: Serve the web at warp speeds
RPMs:rust-warp0.2+async-compression-devel rust-warp0.2+compression-devel 
rust-warp0.2+default-devel rust-warp0.2+multipart-devel rust-warp0.2-devel
Size:130.81 KiB


= DROPPED PACKAGES =
Package: dionaea-0.7.0-9.fc33
Summary: Low interaction honeypot
RPMs:dionaea dionaea-doc python3-dionaea
Size:3.37 MiB

Package: fillets-ng-data-1.0.1-14.fc34
Summary: Game data files for Fish Fillets Next Generation
RPMs:fillets-ng-data
Size:136.23 MiB

Package: flexdock-1.2.4-14.fc33
Summary: Docking framework for Java Swing GUI apps
RPMs:flexdock
Size:411.18 KiB

Package: quvi-0.9.5-15.fc33
Summary

Fedora-Cloud-32-20210401.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210331.0):

ID: 839377  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/839377
ID: 839384  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/839384

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-33-20210401.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210331.0):

ID: 839363  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/839363
ID: 839370  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/839370

Passed openQA tests: 6/7 (aarch64), 6/7 (x86_64)

New passes (same test not passed in Fedora-Cloud-33-20210331.0):

ID: 839372  Test: aarch64 Cloud_Base-qcow2-qcow2 base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/839372
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Self-Introduction: Okwuidegbe Emmanuel

[Sumantro Mukherjee]

you need to join "Fedora Quality Assurance Group (qa)".
That is all you need!

On Wed, Mar 31, 2021 at 10:20 PM Alisina Bolourchi <
alisina.bolour...@gmail.com> wrote:

> Dear Sumanto,
>
> I faced the same problem as Emmanuel. I cannot join git*fedora-qa* group
> as well.
>
> Kind Regards,
>
> Alisina Bolourchi
>
> On Wed, 31 Mar 2021 at 17:38, Emmanuel Okwuidegbe <
> okwuidegbeemman...@gmail.com> wrote:
>
>> Dear Sumantro,
>>
>> Thank you for your reply. But I would like to know if the group I should
>> join is the git*fedora-qa* group?
>>
>> I look forward to hearing from you soon.
>>
>> ---
>>
>> Best Regards,
>>
>> *Okwuidegbe Emmanuel *
>>
>> On Wed, Mar 31, 2021 at 5:20 PM Sumantro Mukherjee 
>> wrote:
>>
>>>
>>>
>>> On Wed, Mar 31, 2021 at 9:43 PM Emmanuel Okwuidegbe <
>>> okwuidegbeemman...@gmail.com> wrote:
>>>
 Dear Sumantro,

 Thank you for your email. I'm an Outreachy applicant looking to start
 contributing to the Fedora QA Dashboard Project.

 The following are what i've already done in no order:
 - Subscribed to the test mailing list.
 - Joined  #fedora-qa IRC channel on Freenode.
 - Introduced myself to the team.
 - Created a Bugzilla Account.
 - Created a FAS account

 I would love to know what fedora-qa group I should join after creating
 a FAS account.

 Less I forget my Nick/Username is emma50.

 I look forward to hearing from you soon.

 ---

 Best Regards,

 *Okwuidegbe Emmanuel *
 ___
 test mailing list -- test@lists.fedoraproject.org
 To unsubscribe send an email to test-le...@lists.fedoraproject.org
 Fedora Code of Conduct:
 https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives:
 https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
 Do not reply to spam on the list, report it:
 https://pagure.io/fedora-infrastructure

>>>
>>>
>>> The group can be joined by
>>> https://admin.fedoraproject.org/accounts/group/view/qa
>>> --
>>> //sumantro
>>> Fedora QE
>>> TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
>>> ___
>>> test mailing list -- test@lists.fedoraproject.org
>>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>> Do not reply to spam on the list, report it:
>>> https://pagure.io/fedora-infrastructure
>>>
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>> Do not reply to spam on the list, report it:
>> https://pagure.io/fedora-infrastructure
>>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: f33 packages in F34?

[David]

I have about 6 man-hours of usage of Fedora 34 WS Beta, and there are
no f33 packages on my install.

I did a query, and dnf said that 1721 lines are counted.I do not think
I have installed much yet. I assume there are packages that can be
removed that I have no use for.That is on my long list of things to
learn
how to do. I think I will run a sudo dnf rm grub2* and reboot.

That is my April Fools Joke.

Cheers.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure