Fedora-Cloud-33-20210416.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-20210415.0):

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

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Re-launch of the OCaml devel list

[Richard W.M. Jones]

On Thu, Apr 15, 2021 at 10:27:58PM +0200, Dan Čermák wrote:
> Dear OCaml devs & packagers,
> 
> thanks to the work of smoodge and the infra team, I am proud to announce
> the resurrection of the ocaml-devel list!
> 
> It should be now available again for subscription in hyperkitty [1]

I'm getting emails saying I need to visit:

https://lists.fedoraproject.org/admin/lists/ocaml-devel.lists.fedoraproject.org/held_messages

to approve messages, but when I go there (after logging in) I only see:

403 Forbidden

Rich.

> 
> Cheers,
> 
> Dan
> 
> Footnotes:
> [1]  
> https://lists.fedoraproject.org/archives/list/ocaml-de...@lists.fedoraproject.org/
> 



> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-32-20210416.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-20210415.0):

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

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Announcing creation of Fedora Source-git SIG

[Vitaly Zaitsev via devel]

On 15.04.2021 23:05, J. Bruce Fields wrote:

Which one exactly is more than 100 GiB?


Chromium.

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Join us at our Fedora Websites and Apps Meet-up - 1330hrs UTC Every Friday

[Akashdeep Dhar]

Hello everyone,

I write this mail to let you know about the very recent developments that took 
place which led to the revamp of the previous Fedora Websites, as the new 
Fedora Websites and Apps team as well as to invite you to our weekly meetings 
that helps shape our objective. You can find more about the discussions that 
led this to happen over at https://pagure.io/mentored-projects/issue/85 and 
https://discussion.fedoraproject.org/c/project/websites/66.

Support from the infrastructure team and from all over the Fedora is valuable 
for us to realize the objectives stated in our 
https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Community_Revamp 
draft so please feel free to join us over at #fedora-websites:matrix.org. We 
have a weekly meet to discuss progress and plans every Friday, 13:30UTC at 
https://meet.jit.si/fedora-websites-apps-meeting and everyone is welcome!

Thanks and regards,
Akashdeep Dhar
t0xic0...@fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: 2021-04-15 dnf broken in rawhide?

[Nicola Sella]

Hello,

I am sorry for the issue, that's my fault.

I tried to release the whole stack yesterday (Thursday), but I bumped 
into some unexpected failures (unrelated to this) during the scratch 
build for dnf-plugins-core and other packages, so I decided to wait 
until today for the plugins as I thought it was an infrastructure problem.


I am used to build plugins as the last pkg and, since I was focused 
fixing the scratch build, I missed the conflict introduced in dnf 
specfile. The same happened for f33, I did the override for dnf without 
noticing. I am sorry, I should have removed the builds from the override 
myself.


Now dnf-plugins-core-4.0.21 is being released which should fix the 
conflict for dnf on f35. I'll do it for 33 as well.


About the side-tag. I think it is definitely a good point. That would 
have avoided the problem.


Thank you for reporting and I am sorry for the issue,

Nicola

On 4/15/21 8:11 PM, Ankur Sinha wrote:

On Thu, Apr 15, 2021 10:57:47 -0700, Kevin Fenzi wrote:

On Thu, Apr 15, 2021 at 06:35:22PM +0100, Ankur Sinha wrote:

Hiya,

I'm trying to build a new package for rawhide but keep running into this
error on koji:

Error:
  Problem: package dnf-plugins-core-4.0.19-1.fc34.noarch requires 
python3-dnf-plugins-core = 4.0.19-1.fc34, but none of the providers can be 
installed
   - package dnf-4.7.0-1.fc35.noarch conflicts with python3-dnf-plugins-core < 
4.0.20 provided by python3-dnf-plugins-core-4.0.19-1.fc34.noarch
   - conflicting requests
(try to add '--allowerasing' to command line to replace conflicting packages or 
'--skip-broken' to skip uninstallable packages)

Anyone else running into this? Known issue?

Yes, already untagged those and mailed the maintainer to use a side-tag
instead.


Ah, awesome! Thanks very much!



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

--

Nicola Sella

He/Him/His

Associate Software Engineer

Red Hat Brno, CZ 

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- liangwen12year contacted since April 6th
- nando contacted since March 26th
- pavlix contacted since March 18th
- zoglesby contacted since April 6th


liangwen12year is maintainer of rpms/nmstate

nando is maintainer of rpms/clthreads
nando is maintainer of rpms/hydrogen
nando is maintainer of rpms/jamin
nando is watching rpms/jconv
nando is maintainer of rpms/jconvolver
nando is maintainer of rpms/ladspa-amb-plugins
nando is maintainer of rpms/ladspa-blop-plugins
nando is maintainer of rpms/ladspa-caps-plugins
nando is maintainer of rpms/ladspa-cmt-plugins
nando is maintainer of rpms/ladspa-fil-plugins
nando is maintainer of rpms/ladspa-mcp-plugins
nando is maintainer of rpms/ladspa-rev-plugins
nando is maintainer of rpms/ladspa-tap-plugins
nando is maintainer of rpms/ladspa-vco-plugins
nando is maintainer of rpms/muse
nando is maintainer of rpms/qjackctl
nando is maintainer of rpms/qsynth
nando is watching rpms/rtaudio
nando is main admin of rpms/sooperlooper
nando has a bugzilla override on rpms/sooperlooper
nando is maintainer of rpms/swami
nando is maintainer of rpms/zita-convolver

pavlix is watching rpms/NetworkManager-iodine
pavlix is watching rpms/NetworkManager-l2tp
pavlix is watching rpms/NetworkManager-openconnect
pavlix is watching rpms/NetworkManager-openvpn
pavlix is watching rpms/NetworkManager-pptp
pavlix is maintainer of rpms/NetworkManager-ssh
pavlix is maintainer of rpms/NetworkManager-strongswan
pavlix is watching rpms/NetworkManager-vpnc
pavlix is watching rpms/bind10
pavlix is maintainer of rpms/dhcpcd
pavlix is maintainer of rpms/dnsmasq
pavlix is maintainer of rpms/dnssec-trigger
pavlix is maintainer of rpms/getdns
pavlix is maintainer of rpms/hostname
pavlix is maintainer of rpms/iproute
pavlix is maintainer of rpms/libecap
pavlix is maintainer of rpms/python-ptrace
pavlix is maintainer of rpms/python-pyroute2
pavlix is maintainer of rpms/radvd
pavlix is maintainer of rpms/rdist
pavlix is maintainer of rpms/rsync
pavlix is maintainer of rpms/squid
pavlix is maintainer of rpms/strongswan
pavlix is maintainer of rpms/unbound

zoglesby is main admin of rpms/ghc-X11-xft
zoglesby has a bugzilla override on rpms/ghc-X11-xft
zoglesby is watching rpms/ghc-utf8-string
zoglesby is maintainer of rpms/publican-fedora


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Inactive packagers to be removed from their packages

[Pierre-Yves Chibon]

Good Morning Everyone,

When we rolled out the new AAA solution a few weeks ago, some accounts have not
been migrated:
- Accounts that have been set inactive by their owner
- Accounts that are disabled
- Accounts marked as spam

This resulted in some packager accounts not being migrated.
As a consequence, since then, the script that syncs the default-assignee and CC
list for each component from dist-git to bugzilla has been notifying us about a
list of packagers in dist-git that could not be synced to bugzilla due to a lack
of bugzilla account (or rather, in this case, the lack of Fedora account). Since
these accounts do not exist in the new FAS, I will be removing them from their
packages on dist-git.

Here is the list of account impacted:
- amukunda
- brolley
- dp67
- ianweller
- jensm
- jima
- jjmcd
- juanmabc
- kmatsui
- kurtseifried
- marcusk
- rnorwood
- sindrepb
- splinux
- vvitek

I am planning on removing these users on April 20th. If anyone is opposed to
this, please let me know.


At the bottom of this email is the list of component affected for each of these
users.

Thanks,
Pierre


---
amukunda is maintainer of rpms/java-atk-wrapper

brolley is maintainer of rpms/si-units
brolley is watching rpms/systemtap
brolley is maintainer of rpms/uom-lib
brolley is maintainer of rpms/uom-parent
brolley is maintainer of rpms/uom-systems

dp67 is watching rpms/HamFax
dp67 is watching rpms/ax25-apps
dp67 is watching rpms/cwirc
dp67 is maintainer of rpms/demorse
dp67 is watching rpms/dxcc
dp67 is watching rpms/gmfsk
dp67 is watching rpms/gpsk31
dp67 is maintainer of rpms/gpsman
dp67 is maintainer of rpms/gridloc
dp67 is maintainer of rpms/linpsk
dp67 is watching rpms/lpsk31
dp67 is watching rpms/xgridloc
dp67 is maintainer of rpms/xpsk31

ianweller is watching rpms/abattis-cantarell-fonts
ianweller is maintainer of rpms/datagrepper
ianweller is watching rpms/ezstream
ianweller is watching rpms/fedora-business-cards
ianweller is watching rpms/gnome-gmail-notifier
ianweller is watching rpms/irclog2html
ianweller is watching rpms/lordsawar
ianweller is watching rpms/mediawiki-CategoryTree
ianweller is watching rpms/mediawiki-HTTP302Found
ianweller is maintainer of rpms/mediawiki-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki-ParserFunctions
ianweller is main admin of rpms/mediawiki116-Cite
ianweller has a bugzilla override on rpms/mediawiki116-Cite
ianweller is main admin of rpms/mediawiki116-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki116-ParserFunctions
ianweller is watching rpms/odfpy
ianweller is watching rpms/openarena
ianweller is maintainer of rpms/python-backports-lzma
ianweller is maintainer of rpms/python-backports-ssl_match_hostname
ianweller is maintainer of rpms/python-fedmsg-meta-debian
ianweller is maintainer of rpms/python-fedmsg-meta-fedora-infrastructure
ianweller is watching rpms/python-flask
ianweller is watching rpms/python-flickrapi
ianweller is watching rpms/python-simplemediawiki
ianweller is main admin of rpms/python-sqlite3dbm
ianweller has a bugzilla override on rpms/python-sqlite3dbm
ianweller is watching rpms/python-transitfeed
ianweller is watching rpms/python-werkzeug
ianweller is watching rpms/rsstool
ianweller is main admin of rpms/supybot-fedora
ianweller is watching rpms/techtalk-pse
ianweller is watching rpms/wordpress-plugin-add-to-any
ianweller is watching rpms/wordpress-plugin-add-to-any-subscribe

jensm is watching rpms/callgit
jensm is watching rpms/perl-Ham-Reference-QRZ
jensm is maintainer of rpms/pisg

jima is maintainer of rpms/alpine
jima is watching rpms/alsa-oss
jima is watching rpms/aoetools
jima is watching rpms/banner
jima is watching rpms/bwm-ng
jima is maintainer of rpms/clusterssh
jima is watching rpms/conserver
jima is watching rpms/dnsmasq
jima is watching rpms/graphviz
jima is watching rpms/libdnet
jima is watching rpms/libstatgrab
jima is watching rpms/miau
jima is watching rpms/ngrep
jima is maintainer of rpms/perl-Device-SerialPort
jima is maintainer of rpms/perl-X11-Protocol
jima is watching rpms/prtconf
jima is watching rpms/putty
jima is watching rpms/rblcheck
jima is watching rpms/scanssh
jima is watching rpms/silo
jima is watching rpms/vblade
jima is watching rpms/videodog
jima is watching rpms/xorg-x11-drv-sunbw2
jima is watching rpms/xorg-x11-drv-suncg14
jima is watching rpms/xorg-x11-drv-suncg3
jima is watching rpms/xorg-x11-drv-suncg6
jima is watching rpms/xorg-x11-drv-sunffb
jima is watching rpms/xorg-x11-drv-sunleo
jima is watching rpms/xorg-x11-drv-suntcx

jjmcd is main admin of rpms/R-qcc
jjmcd has a bugzilla override on rpms/R-qcc
jjmcd is main admin of rpms/rcrpanel
jjmcd has a bugzilla override on rpms/rcrpanel

juanmabc is main admin of rpms/mkproject
juanmabc has a bugzilla override on rpms/mkproject
juanmabc is main admin of rpms/rf
juanmabc has a bugzilla override on rpms/rf
juanmabc is main admin of rpms/tw
juanmabc has a bugzilla override on rpms/tw

kmatsui is main admin

Re: What do we think about always autoreconfing? (was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))

[David Cantrell]

On Tue, Apr 13, 2021 at 11:26:24AM +0100, Richard W.M. Jones wrote:

Hijacking this thread originally about
https://fedoraproject.org/wiki/Changes/Autoconf_271

What is the current thinking in Fedora about always running
"autoreconf -i" during builds that use autotools?


I think we are likely to see the least problems for projects that
created their configure.ac files using autoscan.  For projects that
constructed them manually or in other ways, we'll likely see some
fallout.  I would encourage maintainers to work towards fixing these
things and contributing them back upstream.  Still, we would need to
provide a way to disable the autoreconf step for particular
problematic packages.

Some projects provide their own autotools macros and wrappers around
autoreconf.  For example, Xfce either provides or provided xdt-autogen
as a wrapper to run autoreconf with the Xfce-specific macros and other
defines available.  If it's best to rerun xdt-autogen in these cases,
how could we handle that in the spec file so it runs the correct
'autoreconf' command?


The cons of always autoreconfing are that it slows down builds,
sometimes considerably.  It also could fail - I noticed that autoconf
2.71 has several incompatibilities with the most widely used autoconf
(2.69).


I think the failures will be the most frustrating part of this rather
than the build time.  An FAQ or something of how to fix common
failures for 2.71 would be useful for contributors.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Ben Cotton]

On Fri, Apr 16, 2021 at 9:19 AM Pierre-Yves Chibon  wrote:
>
> zoglesby is maintainer of rpms/publican-fedora
>
Huh. That still exists? What a throwback!

>
> Does anyone know how to contact them?
>
I sent a tweet in zoglesby's direction. He posted about a week ago, so
hopefully he'll see it.


-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 compose report: 20210416.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-34-20210415.n.0
NEW: Fedora-34-20210416.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   1
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   886.77 KiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -2.46 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-34-20210416.n.0.iso
Image: Minimal raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Minimal-34-20210416.n.0.armhfp.raw.xz

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  python-blivet-1:3.3.3-2.fc34
Old package:  python-blivet-1:3.3.3-1.fc34
Summary:  A python module for system storage configuration
RPMs: blivet-data python3-blivet
Size: 886.77 KiB
Size change:  -2.46 KiB
Changelog:
  * Mon Apr 12 2021 Vojtech Trefny  - 3.3.3-2
  - Avoid AttributeError for DiskLabel formats without disklabel type (#1945914)



= DOWNGRADED PACKAGES =
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Zach Oglesby]

> On Fri, Apr 16, 2021 at 9:19 AM Pierre-Yves Chibon  wrote:
> Huh. That still exists? What a throwback!
> 
> I sent a tweet in zoglesby's direction. He posted about a week ago, so
> hopefully he'll see it.
Fixed
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Inactive packagers to be removed from their packages

[Alessio]

On Fri, 2021-04-16 at 15:25 +0200, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> When we rolled out the new AAA solution a few weeks ago, some
> accounts have not
> been migrated:

OT
Out of curiosity: what happens if I register a new account on the new
AAA with one of these usernames?


Ciao,
A.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Re-launch of the OCaml devel list

[Jerry James]

On Fri, Apr 16, 2021 at 1:39 AM Richard W.M. Jones  wrote:
> I'm getting emails saying I need to visit:
>
> https://lists.fedoraproject.org/admin/lists/ocaml-devel.lists.fedoraproject.org/held_messages
>
> to approve messages, but when I go there (after logging in) I only see:
>
> 403 Forbidden

That happened to me, too, until I subscribed to the list.  Now I can
click on the admin links and it works as expected.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: What do we think about always autoreconfing?

[Pavel Raiskup]

On Tuesday, April 13, 2021 3:50:18 PM CEST Florian Weimer wrote:
> * Neal Gompa:
> 
> > As I said previously[1], I think doing autoconf upgrades would be less
> > painful if we always did that.
> >
> > [1]: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZZG3SNLFS7BSXQ3JFJDOWUS3WWGTGLR2/
> 
> I think that's not actually true: If we do not build from source, it
> doesn't matter if the compiler produces a working executable program
> from the old sources.

This is interesting perspective, but I doubt that changing the status quo
would bring much practical difference.  As long as there are no problems,
people don't review the generated files like configure, config.status, ...
no matter if autoreconfed in Fedora, or upstream.

Doing so may also bring an additional level of non-determinism.

For packages that don't patch auto* inputs nowadays it can bring
significant build-time problems.

The problem is that autoconf macros are hard, often misunderstood, some
things change, older auto* versions are more tolerant, ... and fixing
FTBFSs is non-trivial for many package maintainers.

Btw., the fact that there are even now so many packages BuildRequiring
autotools brings the significant fear from actually updating autotools in
distributions (contrary to what I would wish, e.g. in EL).

> Apart from the build-from-source principle, there are other advantages.
> It may be easier to adopt new architectures and toolchain versions.

At least config.sub and config.guess are automatically replaced by
%configure even now.

Pavel

> Thanks,
> Florian
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
> 



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: 2021-04-15 dnf broken in rawhide?

[Justin Forbes]

On Fri, Apr 16, 2021 at 8:11 AM Nicola Sella  wrote:
>
> Hello,
>
> I am sorry for the issue, that's my fault.
>
> I tried to release the whole stack yesterday (Thursday), but I bumped into 
> some unexpected failures (unrelated to this) during the scratch build for 
> dnf-plugins-core and other packages, so I decided to wait until today for the 
> plugins as I thought it was an infrastructure problem.
>
> I am used to build plugins as the last pkg and, since I was focused fixing 
> the scratch build, I missed the conflict introduced in dnf specfile. The same 
> happened for f33, I did the override for dnf without noticing. I am sorry, I 
> should have removed the builds from the override myself.
>
> Now dnf-plugins-core-4.0.21 is being released which should fix the conflict 
> for dnf on f35. I'll do it for 33 as well.
>
> About the side-tag. I think it is definitely a good point. That would have 
> avoided the problem.
>
> Thank you for reporting and I am sorry for the issue,
>
> Nicola
>
> On 4/15/21 8:11 PM, Ankur Sinha wrote:
>
> On Thu, Apr 15, 2021 10:57:47 -0700, Kevin Fenzi wrote:
>
> On Thu, Apr 15, 2021 at 06:35:22PM +0100, Ankur Sinha wrote:
>
> Hiya,
>
> I'm trying to build a new package for rawhide but keep running into this
> error on koji:
>
> Error:
>  Problem: package dnf-plugins-core-4.0.19-1.fc34.noarch requires 
> python3-dnf-plugins-core = 4.0.19-1.fc34, but none of the providers can be 
> installed
>   - package dnf-4.7.0-1.fc35.noarch conflicts with python3-dnf-plugins-core < 
> 4.0.20 provided by python3-dnf-plugins-core-4.0.19-1.fc34.noarch
>   - conflicting requests
> (try to add '--allowerasing' to command line to replace conflicting packages 
> or '--skip-broken' to skip uninstallable packages)
>
> Anyone else running into this? Known issue?
>
> Yes, already untagged those and mailed the maintainer to use a side-tag
> instead.
>
> Ah, awesome! Thanks very much!

It has also spilled over to eln:


 Problem: package dnf-plugins-core-4.0.19-1.eln109.noarch requires
python3-dnf-plugins-core = 4.0.19-1.eln109, but none of the providers
can be installed
  - package dnf-4.7.0-1.eln110.noarch conflicts with
python3-dnf-plugins-core < 4.0.20 provided by
python3-dnf-plugins-core-4.0.19-1.eln109.noarch
  - conflicting requests

Justin

>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
>
> --
>
> Nicola Sella
>
> He/Him/His
>
> Associate Software Engineer
>
> Red Hat Brno, CZ
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Disabling BZ `fedora_requires_release_note` flag

[Ben Cotton]

On Wed, Apr 7, 2021 at 3:40 PM Ben Cotton  wrote:
>
> I will disable the flag on Friday 16 April unless there's a good
> reason to keep it.
>
This is done. Farewell `fedora_requires_release_note` and long live
https://pagure.io/fedora-docs/release-notes/issues !

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

SIMD-related package amd minimum supported instructions

[Robert-André Mauchin]

Hello,

I have a dependency that is a C++ library for SIMD (called highway). 
This library requires SSE4 as its minimum required instruction set 
("Supported targets: SSE4, AVX2, AVX-512, NEON (ARMv7 and v8), WASM 
SIMD."). However the minimum for Fedora is SSE2. Am I still allowed to 
package this despite the requirement being above what's minimum for 
Fedora? It won't compile on old systems but building works fine in Koji.


Best regards,

Robert-André
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Switching Cyrus Sasl from BerkeleyDB to GDBM (System-Wide Change proposal)

[David Cantrell]

> https://fedoraproject.org/wiki/Change/CyrusSaslBerkeleyDBtoGdbm
> 
> == Summary ==
> cyrus-sasl package was built with libdb requirement, now it is replaced by 
> gdbm.
> 
> == Owner ==
> * Name: [[User:Dbelyavs| Dmitry Belyavskiy]]
> * Email: dbelyavs(a)redhat.com
> 
> 
> 
> == Detailed Description ==
> This change switches the default backend Key-Value DB used by sasldb
> plugin from BerkeleyDB to GDBM and provides a migration tool for
> automatic conversion from old to new format.
> 
> 
> == Benefit to Fedora ==
> According to more restrictive libdb licence policy exists effort to
> remove libdb's dependencies.
> cyrus-sasl package can now be built without libdb requirement.
> 
> 
> == Scope ==
> * Proposal owners:
> * Other developers: The owners of the packages depending on cyrus-sasl
> sasldb plugin should provide the documentation about the migration
> procedure.
> 
> * Release engineering: [https://pagure.io/releng/issue/10084]
> * Policies and guidelines: not needed for this Change
> * Trademark approval: N/A (not needed for this Change)
> * Alignment with Objectives:
> 
> 
> == Upgrade/compatibility impact ==
> The migration script should be used to upgrade the particular
> databases used by specific applications via sasldb plugin
> 
> 
> == How To Test ==
> * Install the new version of the cyrus-sasl.
> * Use the migration tool bdb2current provided by the package to
> migrate your sasldb file
> * update the configuration file to point on the new sasldb file
> * restart the application if necessary
> * Check that auth is still working
> 
> 
> == User Experience ==
> not provided
> 
> == Dependencies ==
> A lot of application use cyrus-sasl sasldb plugins. Their maintainers
> were notified via email and some of them have responded.
> 
> 
> == Contingency Plan ==
> * Contingency mechanism: Revert the shipped configuration
> * Contingency deadline: Beta freeze
> * Blocks release? Yes
> 
> 
> == Documentation ==
> Here is the notification sent to known developers of the depending packages:
> 
> New version of the cyrus-sasl is planned to use the gdbm database for
> the sasldb plugins.
> 
> I've implemented the patch
> (https://src.fedoraproject.org/rpms/cyrus-sasl/pull-request/3#request_diff)
> changing the default DB and implementing the migration tool to make
> the switching from BerkeleyDB to GDBM seamless.
> 
> I kindly ask you to check the information in the following spreadsheet:
> https://docs.google.com/spreadsheets/d/1z5eTSm3rtlKtEKPCxhI_wE861Xzg8kbvI...:
> 
> whether your package is affected by the proposed change
> whether the migration tool is suitable for your purposes
> 
> and let me know or mark the results in the table
> 
> 
> == Release Notes ==
> a new version of the cyrus-sasl package is landing in rawhide.
> 
> This version changes the database used to store saslauthdb data. This
> is part of the move to deprecate use of Berkley DB. The new package
> will use GDBM instead.
> 
> We provided a tool to perform migrations for database should that be
> needed by a package:
> 
> The syntax of the migration tool is
> bdb2current  
> 
> Please check whether your packages use the sasldb plugin and provide a
> relevant migration guideline.

A couple of questions:

1) The contingency plan does not make it clear how users revert if the BDB 
version of Cyrus SASL has to return.  Does the migration tool leave a copy of 
the previous db file or files in place that can be used by the BDB version of 
Cyrus SASL?  Should the new file be migrated back in case of changes 
post-migration?

2) I'm curious why GDBM was chosen instead of something like sqlite.

Thanks,
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Inactive packagers to be removed from their packages

[Kevin Fenzi]

On Fri, Apr 16, 2021 at 02:04:53PM +, Alessio wrote:
> On Fri, 2021-04-16 at 15:25 +0200, Pierre-Yves Chibon wrote:
> > Good Morning Everyone,
> > 
> > When we rolled out the new AAA solution a few weeks ago, some
> > accounts have not
> > been migrated:
> 
> OT
> Out of curiosity: what happens if I register a new account on the new
> AAA with one of these usernames?

It would be in a weird state. It would appear to be a maintainer, and if
bugzilla account was setup would get assigned bugs for the packages, but
since it would not be in the packager group, it could not push any
changes at all to the packages. 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Switching Cyrus Sasl from BerkeleyDB to GDBM (System-Wide Change proposal)

[Gary Buhrmaster]

On Fri, Apr 16, 2021 at 4:31 PM David Cantrell  wrote:

> 2) I'm curious why GDBM was chosen instead of something like sqlite.

I believe sasldb only supports gdbm and
ndbm as alternatives to bdb.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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

[Fedora compose checker]

No missing expected images.

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

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

ID: 858248  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/858248
ID: 858470  Test: aarch64 universal install_blivet_resize_lvm@uefi
URL: https://openqa.fedoraproject.org/tests/858470
ID: 858474  Test: aarch64 universal support_server@uefi
URL: https://openqa.fedoraproject.org/tests/858474
ID: 858476  Test: aarch64 universal install_iscsi@uefi
URL: https://openqa.fedoraproject.org/tests/858476

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

ID: 858220  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/858220
ID: 858239  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/858239
ID: 858351  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/858351
ID: 858426  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/858426

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

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

ID: 858162  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/858162
ID: 858203  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/858203
ID: 858260  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/858260
ID: 858266  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/858266
ID: 858279  Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/858279
ID: 858304  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/858304
ID: 858319  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/858319
ID: 858341  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/858341
ID: 858400  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/858400
ID: 858455  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/858455

Passed openQA tests: 180/189 (x86_64), 117/127 (aarch64)

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

ID: 858169  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/858169
ID: 858294  Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/858294
ID: 858298  Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi
URL: https://openqa.fedoraproject.org/tests/858298
ID: 858313  Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi
URL: https://openqa.fedoraproject.org/tests/858313
ID: 858315  Test: aarch64 Server-dvd-iso 
install_repository_nfs_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/858315
ID: 858321  Test: aarch64 Server-raw_xz-raw.xz base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/858321
ID: 858460  Test: aarch64 universal install_multi@uefi
URL: https://openqa.fedoraproject.org/tests/858460

Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 
System load changed from 0.24 to 0.13
Previous test data: https://openqa.fedoraproject.org/tests/857587#downloads
Current test data: https://openqa.fedoraproject.org/tests/858155#downloads

Installed system changes in test x86_64 Server-dvd-iso install_default_upload: 
System load changed from 0.25 to 0.10
Previous test data: https://openqa.fedoraproject.org/tests/857598#downloads
Current test data: https://openqa.fedoraproject.org/tests/858166#downloads

Installed system changes in test x86_64 Workstation-live-iso 
install_default@uefi: 
Used mem changed from 585 MiB to 726 MiB
System load changed from 0.26 to 0.82
Average CPU usage changed from 2.96190476 to 17.30476190
Previous test data: https://openqa.fedoraproject.org/tests/857643#downloads
Current test data: https://openqa.fedoraproject.org/tests/858211#downloads

Installed system changes in test x86_64 Workstation-live-iso 
install_default_upload: 
Used mem changed from 728 MiB to 573 MiB
1 services(s) added since previous compose: fwupd.service
Average CPU usage changed from 27.52857143 to 3.48571429
Previous test data: https://openqa.fedoraproject.org/tests/857644#downloads
Current test data: https://openqa.fedoraproject.org/tests/858212#downloads

Installed system changes in test x86_64 KDE-live-iso install_default@uefi: 
System load cha

Re: SIMD-related package amd minimum supported instructions

[Fabio Valentini]

On Fri, Apr 16, 2021 at 6:29 PM Robert-André Mauchin  wrote:
>
> Hello,
>
> I have a dependency that is a C++ library for SIMD (called highway).
> This library requires SSE4 as its minimum required instruction set
> ("Supported targets: SSE4, AVX2, AVX-512, NEON (ARMv7 and v8), WASM
> SIMD."). However the minimum for Fedora is SSE2. Am I still allowed to
> package this despite the requirement being above what's minimum for
> Fedora? It won't compile on old systems but building works fine in Koji.
>
> Best regards,
>
> Robert-André

Relevant FESCo discussion and decision:
https://pagure.io/fesco/issue/2569#comment-713002

The text that was voted on:

Libraries packaged in Fedora may require ISA extensions, however
any packaged application must not crash on any officially supported
architecture, either by providing a generic fallback implementation OR
by cleanly exiting when the requisite hardware support is unavailable.

It is still stuck in the pipeline to get the packaging guidelines
changed, though:
https://pagure.io/packaging-committee/issue/1044

Hope that helps.
Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Pierre-Yves Chibon]

On Fri, Apr 16, 2021 at 01:41:41PM -, Zach Oglesby wrote:
> > On Fri, Apr 16, 2021 at 9:19 AM Pierre-Yves Chibon 
> >  > Huh. That still exists? What a throwback!
> > 
> > I sent a tweet in zoglesby's direction. He posted about a week ago, so
> > hopefully he'll see it.
> Fixed

Thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Switching Cyrus Sasl from BerkeleyDB to GDBM (System-Wide Change proposal)

[David Cantrell]

On Fri, Apr 16, 2021 at 04:49:46PM +, Gary Buhrmaster wrote:

On Fri, Apr 16, 2021 at 4:31 PM David Cantrell  wrote:


2) I'm curious why GDBM was chosen instead of something like sqlite.


I believe sasldb only supports gdbm and
ndbm as alternatives to bdb.


Ooops, my mistake.  I see:

--with-dblib={berkeley|gdbm|lmdb|ndbm|none|auto_detect}

So yeah.  I was mistaking cyrus-sasl for another
project-with-db-backend-of-your-choice and sqlite was an option.

Nevermind.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Linux 34 Final blocker status email #5

[Ben Cotton]

Let's keep our streak alive and hit target date #1 by being go on Thursday!

Action summary


Accepted blockers
-
1. sddm — logout after switch returns the user to console instead of
sddm — ON_QA
ACTION: collective to decide if FEDORA-2021-87d6b51834 is a sufficient fix

2. shim — include new bootloaders on Fedora 34 install media so UEFI
Secure Boot enabled systems can boot from them — POST
ACTION: shim maintainers to get shim-unsigned-x64-15.4-4.fc33 signed

3. uboot-tools — latest uboot fails to load the dtb — ASSIGNED
ACTION: uboot-tools maintainers to diagnose and fix issue


Proposed blockers
-

1. plasma-discover — Do final F34 fedora-release and fedora-repos builds — ON_QA
ACTION: QA to verify FEDORA-2021-4cb56488da

2. virt-manager — USB flash disk cannot be mounted into a virtual machine. — NEW
ACTION: virt-manager 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 islimited
to Wayland sessions. FEDORA-2021-87d6b51834 partially fixes this, but
we may still need to consider deferring the Wayland-by-default for KDE
Plasma change.

2. shim — https://bugzilla.redhat.com/show_bug.cgi?id=1938630 — POST
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.
shim-unsigned-x64-15.4-4.fc33 fixes bugs discovered during testing of
the latest update, but it needs to be signed before we can release.

3. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=1946278 — ASSIGNED
latest uboot fails to load the dtb

Recent uboot releases fail to load the dtb. Some supported systems
boot using dtb provided by firmware, but others will not boot.


Proposed blockers
-

1. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=1903294 — ON_QA
plasma-discover doesnt refresh metadata

Clicking the "refresh" button on plasma-discover does not update the
metadata. The root cause is an apparent PackageKit bug. As a
short-term fix, FEDORA-2021-4cb56488da changes plasma-discover to tell
PackageKit to force a refresh, which gets us the desired behavior.

2. virt-manager — https://bugzilla.redhat.com/show_bug.cgi?id=1950258 — NEW
USB flash disk cannot be mounted into a virtual machine.

With F34 hosts, guests can see the existence USB flash disks but
cannot read them. This is independent of guest OS version and the
SELinux settings on both host and guest. F33 hosts do not display this
behavior.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Switching Cyrus Sasl from BerkeleyDB to GDBM (System-Wide Change proposal)

[Simo Sorce]

On Fri, 2021-04-16 at 16:31 +, David Cantrell wrote:
> > https://fedoraproject.org/wiki/Change/CyrusSaslBerkeleyDBtoGdbm
> > 
> > == Summary ==
> > cyrus-sasl package was built with libdb requirement, now it is replaced by 
> > gdbm.
> > 
> > == Owner ==
> > * Name: [[User:Dbelyavs| Dmitry Belyavskiy]]
> > * Email: dbelyavs(a)redhat.com
> > 
> > 
> > 
> > == Detailed Description ==
> > This change switches the default backend Key-Value DB used by sasldb
> > plugin from BerkeleyDB to GDBM and provides a migration tool for
> > automatic conversion from old to new format.
> > 
> > 
> > == Benefit to Fedora ==
> > According to more restrictive libdb licence policy exists effort to
> > remove libdb's dependencies.
> > cyrus-sasl package can now be built without libdb requirement.
> > 
> > 
> > == Scope ==
> > * Proposal owners:
> > * Other developers: The owners of the packages depending on cyrus-sasl
> > sasldb plugin should provide the documentation about the migration
> > procedure.
> > 
> > * Release engineering: [https://pagure.io/releng/issue/10084]
> > * Policies and guidelines: not needed for this Change
> > * Trademark approval: N/A (not needed for this Change)
> > * Alignment with Objectives:
> > 
> > 
> > == Upgrade/compatibility impact ==
> > The migration script should be used to upgrade the particular
> > databases used by specific applications via sasldb plugin
> > 
> > 
> > == How To Test ==
> > * Install the new version of the cyrus-sasl.
> > * Use the migration tool bdb2current provided by the package to
> > migrate your sasldb file
> > * update the configuration file to point on the new sasldb file
> > * restart the application if necessary
> > * Check that auth is still working
> > 
> > 
> > == User Experience ==
> > not provided
> > 
> > == Dependencies ==
> > A lot of application use cyrus-sasl sasldb plugins. Their maintainers
> > were notified via email and some of them have responded.
> > 
> > 
> > == Contingency Plan ==
> > * Contingency mechanism: Revert the shipped configuration
> > * Contingency deadline: Beta freeze
> > * Blocks release? Yes
> > 
> > 
> > == Documentation ==
> > Here is the notification sent to known developers of the depending packages:
> > 
> > New version of the cyrus-sasl is planned to use the gdbm database for
> > the sasldb plugins.
> > 
> > I've implemented the patch
> > (https://src.fedoraproject.org/rpms/cyrus-sasl/pull-request/3#request_diff)
> > changing the default DB and implementing the migration tool to make
> > the switching from BerkeleyDB to GDBM seamless.
> > 
> > I kindly ask you to check the information in the following spreadsheet:
> > https://docs.google.com/spreadsheets/d/1z5eTSm3rtlKtEKPCxhI_wE861Xzg8kbvI...:
> > 
> > whether your package is affected by the proposed change
> > whether the migration tool is suitable for your purposes
> > 
> > and let me know or mark the results in the table
> > 
> > 
> > == Release Notes ==
> > a new version of the cyrus-sasl package is landing in rawhide.
> > 
> > This version changes the database used to store saslauthdb data. This
> > is part of the move to deprecate use of Berkley DB. The new package
> > will use GDBM instead.
> > 
> > We provided a tool to perform migrations for database should that be
> > needed by a package:
> > 
> > The syntax of the migration tool is
> > bdb2current  
> > 
> > Please check whether your packages use the sasldb plugin and provide a
> > relevant migration guideline.
> 
> A couple of questions:
> 
> 1) The contingency plan does not make it clear how users revert if
> the BDB version of Cyrus SASL has to return.  Does the migration tool
> leave a copy of the previous db file or files in place that can be
> used by the BDB version of Cyrus SASL?  Should the new file be
> migrated back in case of changes post-migration?

The migration tool creates a new file, so the previous DB should remain
available. We do not really have a way to convert back though,
modifying the migrations script to go ther way around should be
possible, but unclear if that is really required as you have a backup
of th user's db at time of migration.

> 2) I'm curious why GDBM was chosen instead of something like sqlite.
> 
> Thanks,
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://doc

Review swaps

[Jerry James]

Hi all,

I have mentioned previously on this list that I want to update
ocaml-ocamlgraph to version 2.0.0.  It has two consumers in Fedora:
frama-c (which is ready to move to the new version) and ocaml-dose3
(which is not).

There is a new upstream location for ocaml-dose3:
https://gitlab.com/irill/dose3.  That has a version which is ready for
ocaml-ocamlgraph 2.0.0, but it needs two packages not currently
available in Fedora:

ocaml-camlbz2: https://bugzilla.redhat.com/show_bug.cgi?id=1950554
ocaml-parmap: https://bugzilla.redhat.com/show_bug.cgi?id=1950555

Who would like to swap reviews?
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

FedoraRespin-33-updates-20210416.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 7/37 (x86_64)

ID: 858649  Test: x86_64 Workstation-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/858649
ID: 858653  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/858653
ID: 858654  Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/858654
ID: 858655  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/858655
ID: 858658  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/858658
ID: 858674  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/858674
ID: 858678  Test: x86_64 KDE-live-iso release_identification
URL: https://openqa.fedoraproject.org/tests/858678

Passed openQA tests: 30/37 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Review swaps

[Michel Alexandre Salim]

On Fri, 2021-04-16 at 15:49 -0600, Jerry James wrote:
> Hi all,
> 
> I have mentioned previously on this list that I want to update
> ocaml-ocamlgraph to version 2.0.0.  It has two consumers in Fedora:
> frama-c (which is ready to move to the new version) and ocaml-dose3
> (which is not).
> 
> There is a new upstream location for ocaml-dose3:
> https://gitlab.com/irill/dose3.  That has a version which is ready
> for
> ocaml-ocamlgraph 2.0.0, but it needs two packages not currently
> available in Fedora:
> 
> ocaml-camlbz2: https://bugzilla.redhat.com/show_bug.cgi?id=1950554
> ocaml-parmap: https://bugzilla.redhat.com/show_bug.cgi?id=1950555
> 
I'll take them. Apart from ocaml-atd I will have more ocaml
dependencies for infer soon.

Best regards,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure