devel March 2022

devel@lists.stg.fedoraproject.org

191 participants
388 discussions

CVE 9.8 rated httpd update stuck in updates-testing for a week
by Marius Schwarz 01 Apr '22

01 Apr '22

hi all, the critpath update for httpd-2.4.53.fc34 is stuck in updates-testing. bodhi reports a pending test for this package. https://bodhi.fedoraproject.org/updates/FEDORA-2022-21264ec6db I can confirm, that i rolled out this update on my web->cluster<- and pages do still work. httpd test suite passed (php, ssl, static ). Pls push it to stable. best regards, Marius Schwarz

5 7

[IPP-over-USB printers/scanners] Expected breakage when ipp-usb+a driver are installed
by Zdenek Dohnal 31 Mar '22

31 Mar '22

Hi all, driverless+printer applications world of printing and scanning is coming in the future: - printer driver, raw queues and other removals are planned with CUPS 3.0, roughly in the next year, - printer applications RPMs are waiting for cups-filters 2.0, but the apps are in SNAP already for people to try them, - driverless scanning is already possible with sane-airscan, which supports WSD and eSCL protocols. and since ipp-usb is in Fedora for a while (since Fedora 32), CUPS and sane-airscan packages started to recommend ipp-usb package, which unfortunately leads to expected breakage (see known issues[1] - either under HPLIP or golang-github-openprinting-ipp-usb) due a conflict on USB port. _This breakage happens if both conditions below are met:_ - the device supports IPP-over-USB - how to find out here[2] - the device is currently installed with a classic driver, (f.e. HPLIP - has its device uri starting with 'hp:/usb/'), _The __behavior__of breakage_ is: - for printing - the old queue is available, but when a job is sent it prints nothing, with errors in the logs as: hp[3559]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy - for scanning - the scanner is not recognized by the classic driver, but sane-airscan should kick in and provide functional device, so a new device should appear in scanning dialog _The breakage is __expected__for IPP-over-USB devices_, because ipp-usb is running on the USB port, prepared for incoming IPP requests. This behavior blocks the port for other binaries, which can try to access it, such as printing and scanning backends (pixma, hp, hpaio...). Unfortunately there is no clean upgrade path to solve the migration automatically because of unrealistic requirements such as: - the USB device would have needed to be plugged in and turned on during the update - %post scriptlets don't work the same way on immutable Fedoras as on Fedora Linux, and other upgrade possibilities such as Leapp don't support Fedora upgrades AFAIK, the fix has to be done manually. _How to fix the breakage:_ - printing - remove the old print queue and start using CUPS temporary queue[3], which is supported by modern print dialogs, or install the new queue permanently by: $ lpadmin -p <queue_name> -v ipp://localhost:60000/ipp/print -m everywhere -E ipp-usb advertises the printer only to localhost at port 60000 by default, any other USB printer capable of IPP-over-USB will be available at port 60001 etc... - scanning - sane-airscan should automatically pick the device up, if the device supports eSCL or WSD protocols - here [4] is the growing list of devices, which were identified by users as they are working with sane-airscan. In case you have only one device supported by the driver package and the driver is a list package, you can safely remove the driver package _If the driverless setup with ipp-usb doesn't work for you:_ It would be great if you filed a bug at https://bugzilla.redhat.com for golang-github-openprinting-ipp-usb component after you've gone through the useful tricks for printing[8], 'How to fix the breakage' from this email and known issues of CUPS[9]. If the device is unusable for ipp-usb due a serious firmware bug, we can add a quirk upstream rejecting this device in ipp-usb, so the daemon will ignore the device and the quirk will be shared with all users - so the device can be again used with classic driver or with, in the future, with a printer application. If user wants to go with classic drivers again, golang-github-openprinting-ipp-usb-0.9.20 (currently in rawhide and for other releases in testing repo - F36[5], F35[6], F34[7]) supports device quirks in /etc/ipp-usb/quirks directory. See 'man ipp-usb' for more info. __ _Affected OS versions:_ Fedora 36+ and users who installed cups-2.3.3op2-15.fc35/fc34 updates - the change was reverted in cups-2.3.3op2-16.fc35/fc34, but ipp-usb is not removed with the new CUPS update, so it has to be removed manually or the setup has to be migrated ('How to fix the breakage') to ipp-usb. _SUMMARY:_ I'm deeply sorry for the inconvenience during the breakage and for not announcing the change in advance via proper channels - hopefully driverless setup with ipp-usb can help you with using the device without additional drivers, proprietary binary blobs and its 'installation' (in case of CUPS temporary queues you don't need to install the printer at all, that's why installation with quotes) will be more smoother. Thank you for your time and effort! Zdenek [1] https://docs.fedoraproject.org/en-US/quick-docs/cups-known-issues/#_golang_… [2] https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to… [3] https://docs.fedoraproject.org/en-US/quick-docs/cups-terminology/#_temporar… [4] https://github.com/alexpevzner/sane-airscan#compatibility [5] https://bodhi.fedoraproject.org/updates/FEDORA-2022-037458e247 [6] https://bodhi.fedoraproject.org/updates/FEDORA-2022-140993eb13 [7] https://bodhi.fedoraproject.org/updates/FEDORA-2022-f151accd9b [8] https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks [9] https://docs.fedoraproject.org/en-US/quick-docs/cups-known-issues/#_cups -- Zdenek Dohnal Software Engineer Red Hat, BRQ-TPBC

5 7

Review requests: mingw-qt6-qtwebchannel, mingw-qt6-qttranslations
by Sandro Mani 31 Mar '22

31 Mar '22

Hi I've got two more mingw-qt6-* packages which are up for review, both are straight forward mingw/c++ packages. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2009269 - mingw-qt6-qtwebchannel https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2070708 - mingw-qt6-qttranslations Happy to review in exchange Thanks Sandro

1 0

Retiring python-typer-cli due to lack of upstream support
by Ben Beasley 31 Mar '22

31 Mar '22

This is just a heads-up that I am retiring python-typer-cli in F37/Rawhide due to an ongoing lack of upstream support. It is a leaf package. Important functionality has been patched out downstream[1] for about six months due to incompatibility with click version 8.x and typer version 0.4.0 (the latter by the same author as typer-cli). The required fix is nontrivial, and there is no sign of progress[2]. This has been the case through the entire F35 lifecycle, and I wouldn’t expect the package to be adequately maintained even if upstream does comes through with a patch at some point. Still, I will maintain the packages in F34–F36 until those releases’ end-of-life dates, and I’ll also keep maintaining the related python-typer package, which has seen a much more adequate amount of upstream attention in the past year. – Ben [1] https://bugzilla.redhat.com/show_bug.cgi?id=1999921 [2] https://github.com/tiangolo/typer-cli/issues/50

1 0

Poco FTBFS fix and soname bump
by Robin Lee 31 Mar '22

31 Mar '22

Poco upstream finally committed OpenSSL 3 in the next release branch. And Carl George helped to finish rawhide/f36 builds with a snapshot source. There is also a soname bump. Poco bumps soname at every release. After all, nothing else in Fedora depends on Poco. -robin

1 0

Fedora-Cloud-34-20220331.0 compose check report
by Fedora compose checker 31 Mar '22

31 Mar '22

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-20220330.0): ID: 1204329 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1204329 ID: 1204338 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1204338 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

Fedora-Cloud-35-20220331.0 compose check report
by Fedora compose checker 31 Mar '22

31 Mar '22

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-20220330.0): ID: 1204312 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1204312 ID: 1204321 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1204321 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

[Test-Announce] [Test Day] Fedora Wallpaper Test Day is TODAY!
by Sumantro Mukherjee 31 Mar '22

31 Mar '22

Hey All, The Fedora Design team is hosting a test day today. We will be testing the Light/Dark theme and Wallpaper for Fedora Linux 36. If you have some cycles, these resources[0] will give you some context of how to test and submit results[1] For a little bit of history about the test day can be found here [2] [0] http://fedoraproject.org/wiki/Test_Day:2022_03_31_F36_Wallpapers [1] https://testdays.fedoraproject.org/events/130 [2] https://discussion.fedoraproject.org/t/help-us-test-fedora-linux-36-beta-wa… -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)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-announce@lists.fedorapro… Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 0

pagure.io / pagure.org dead ?
by Daniel P. Berrangé 30 Mar '22

30 Mar '22

Any attempt to connect to pagure.io / pagure.org right now appears to be getting immediately terminated before TLS handshake even runs. It was reported to me by a 3rd party user trying to access some release files hosted there, and confirmed it myself too. I would report it to Fedora infra, except IIUC the infra ticket system is on pagure. So I mention it here in the hope that someone will see it. I do see status.fedoraproject.org claims there was a pagure outage yesterday which was resolved, due to a network problem. It seems to have recurred... With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

3 2

Fedora CoreOS Meeting Minutes 2022-03-30
by Dusty Mabe 30 Mar '22

30 Mar '22

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:31:30 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos… . Meeting summary --------------- * roll call (dustymabe, 16:31:35) * Action items from last meeting (dustymabe, 16:35:56) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/601 (davdunc, 16:39:11) * LINK: https://github.com/amazonlinux/amazon-ec2-utils (davdunc, 16:44:10) * for #601 after davadunc talked with Amazon engineers the code in ec2-utils and ec2-net-utils might be a good reference for other distributions, but is not promised to work. They encourage us to write our own with those as a reference. (dustymabe, 16:50:52) * ACTION: jlebon bgilbert travier to discuss potential solutions for #392 and update the ticket and present the outcome at a future meeting. (jlebon, 16:53:44) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1147 (miabbott, 16:54:38) * dustymabe aaradhak ravanelli mnguyen and i met today to lay out the todo items for f36 test day - https://github.com/coreos/fedora-coreos-tracker/issues/1147 (miabbott, 16:55:00) * miabbott sent an email to coreos-status for ovf changes and posted to the fedora discussion site (miabbott, 16:55:28) * LINK: https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedorapro… (miabbott, 16:55:36) * LINK: https://discussion.fedoraproject.org/t/changes-to-vmware-ovf-metadata/37792 (miabbott, 16:55:42) * supportability of non-EOL VMware platforms (dustymabe, 16:55:53) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1146 (dustymabe, 16:55:57) * AGREED: FCOS will not make any changes to the hardware version in the OVF metadata of the VMware OVA that would exclude non-EOL platforms from being supported. (jlebon, 17:03:27) * F36 FCOS Test Day TODO List (dustymabe, 17:04:00) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1147 (dustymabe, 17:04:06) * we have most work items that we identified assigned to volunteers! (dustymabe, 17:14:58) * the organizers of the test day are going to get together in an informal session next Tuesday (April 5) to strategize about what test cases are left to execute and divide them up. All are welcome to join. (dustymabe, 17:17:08) * tracker: Fedora 36 changes considerations (dustymabe, 17:18:48) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918 (dustymabe, 17:18:52) * FCOS `next` stream is now based on Fedora 36 beta content (dustymabe, 17:19:29) * an issue found so far with Fedora 36 is RPi4 networking seems to not work: https://github.com/coreos/fedora-coreos-tracker/issues/1145 (dustymabe, 17:20:14) * another issue found (not filed), but NM dispatchers are blocked by SELinux: https://bugzilla.redhat.com/show_bug.cgi?id=2065940 (dustymabe, 17:21:16) * open floor (dustymabe, 17:24:30) Meeting ended at 17:31:40 UTC. Action Items ------------ * jlebon bgilbert travier to discuss potential solutions for #392 and update the ticket and present the outcome at a future meeting. Action Items, by person ----------------------- * bgilbert * jlebon bgilbert travier to discuss potential solutions for #392 and update the ticket and present the outcome at a future meeting. * jlebon * jlebon bgilbert travier to discuss potential solutions for #392 and update the ticket and present the outcome at a future meeting. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (110) * davdunc (37) * zodbot (18) * jlebon (16) * miabbott (12) * bgilbert (9) * fifofonix (5) * aaradhak[m] (4) * ravanelli (3) * skunkerk (3) * jdoss (2) * saqali (1) * aaradhak (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

← Newer
1
2
3
4
5
6
7
...
39
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel March 2022