Re: Can the BTRFS transparent compression mess with RPM's free space checks?
On Mon, Apr 19, 2021 at 4:42 PM Lyes Saadi wrote: > > I think I realized what went wrong: I compressed my filesystem _after_ > already having done some snapshots. I think it then duplicated all my > files and basically filled my filesystem... And I did Yeah defragmentation unshares shared extents. So all the deduplication of reflinks and snapshots is undone. It's best to narrow the defragmentation to be limited to a particular subvolume, or directories in that subvolume, rather than all snapshots. Or just enable compression in fstab and don't compress already written things, just let it compress new writes. The autodefrag mount option is a bit different because it's only triggered on small writes less than 64KiB, either inserts or appends into an existing file. The target extent size is 128KiB which is also the max compression block size. So as a file is modified with this write pattern, it's already unsharing any shared extents from snapshots or reflinks. Since the whole file isn't (re)defragmented every time autodefrag is triggered by the write pattern, it's not going to add much (if at all) to unsharing extents. -- Chris Murphy ___ 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: Can the BTRFS transparent compression mess with RPM's free space checks?
I think I realized what went wrong: I compressed my filesystem _after_
already having done some snapshots. I think it then duplicated all my
files and basically filled my filesystem... And I did
Sorry for that! I'm happy to be wrong at least. And thank you for this
great answer!
Le 19/04/2021 à 23:29, Dominique Martinet a écrit :
Lyes Saadi wrote on Mon, Apr 19, 2021 at 10:56:51PM +0100:
It's a bit late to ask this question, but it emerged when I noticed that
after upgrading my PC to Silverblue 34 and after compressing manually my
files, and doing some snapshots, rpm-ostree began complaining about the
absence of free space... While compsize reported that I used only 84G(o/io?)
of my 249Go filesystem... I then realized that because of the compression
and the snapshots, ostree thought that my disk was full. The same problem
happened with gnome-disk. I reported both issues[1][2].
Err, no.
btrfs has been reporting proper things in statfs that programs can rely
on, compsize is only there for you if you're curious and for debugging.
In this case your filesystem is really almost full (around 8GB free
according to your output)
That was a problem very early on and basically everyone complained df
being unuseable would break too many programs.
You probably compressed your / but have snapshots laying around that
still take up space and weren't considered in your compsize command?
If you don't trust df (statfs), you have two btrfs commands to look at
for more details; here's what it gives on my system:
# btrfs fi df /
Data, single: total=278.36GiB, used=274.63GiB
System, DUP: total=32.00MiB, used=48.00KiB
Metadata, DUP: total=9.29GiB, used=6.88GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
# btrfs fi usage /
Overall:
Device size:330.00GiB
Device allocated: 297.00GiB
Device unallocated: 33.00GiB
Device missing: 0.00B
Used: 288.39GiB
Free (estimated):36.73GiB (min: 20.23GiB)
Free (statfs, df): 36.73GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:278.36GiB, Used:274.63GiB (98.66%)
/dev/mapper/slash278.36GiB
Metadata,DUP: Size:9.29GiB, Used:6.88GiB (74.09%)
/dev/mapper/slash 18.57GiB
System,DUP: Size:32.00MiB, Used:48.00KiB (0.15%)
/dev/mapper/slash 64.00MiB
Unallocated:
/dev/mapper/slash 33.00GiB
And for comparison:
# df -h /
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/slash 330G 289G 37G 89% /
In all cases, the Used column actually corresponds to compressed size --
real blocks on disk and not uncompressed data size.
I have way too many subvolumes but here's an output that lists more than
289G "used"; I'm lazy so without snapshots:
# compsize -x / /home /var /var/lib/machines/ /nix
Processed 2722869 files, 1820146 regular extents (2063805 refs), 1625123 inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 76% 232G 302G 317G
none 100% 196G 196G 194G
zstd33% 34G 104G 122G
prealloc 100% 1.0G 1.0G 553M
Hm, not very convincing, adding a few (there's more, I guess adding all
of them should bring the Disk Usage column up to 289G but this just
takes too long for this mail -- the "proper" way to track snapshot usage
would be quota but I don't have these enabled here):
# compsize -x / /home /var /var/lib/machines/ /nix /.snapshots/{19,20}*/snapshot
Processed 10803451 files, 2110568 regular extents (7656942 refs), 5960388
inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 75% 249G 331G 732G
none 100% 206G 206G 281G
zstd33% 41G 123G 451G
prealloc 100% 1.0G 1.0G 551M
I would suggest finding what subvolumes you may have (btrfs subvolume
list /) and cleanup old ones, I'm not sure what is used by default
nowadays (snapper?) there might be higher level commands
They might not be visible from your mountpoint if your setup mounts a
subvolume by default, in which case you can mount your btrfs volume
somewhere else with -o subvol=/ for example to show everything and play
with compsize if you want.
___
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:
Re: Can the BTRFS transparent compression mess with RPM's free space checks?
Lyes Saadi wrote on Mon, Apr 19, 2021 at 10:56:51PM +0100:
> It's a bit late to ask this question, but it emerged when I noticed that
> after upgrading my PC to Silverblue 34 and after compressing manually my
> files, and doing some snapshots, rpm-ostree began complaining about the
> absence of free space... While compsize reported that I used only 84G(o/io?)
> of my 249Go filesystem... I then realized that because of the compression
> and the snapshots, ostree thought that my disk was full. The same problem
> happened with gnome-disk. I reported both issues[1][2].
Err, no.
btrfs has been reporting proper things in statfs that programs can rely
on, compsize is only there for you if you're curious and for debugging.
In this case your filesystem is really almost full (around 8GB free
according to your output)
That was a problem very early on and basically everyone complained df
being unuseable would break too many programs.
You probably compressed your / but have snapshots laying around that
still take up space and weren't considered in your compsize command?
If you don't trust df (statfs), you have two btrfs commands to look at
for more details; here's what it gives on my system:
# btrfs fi df /
Data, single: total=278.36GiB, used=274.63GiB
System, DUP: total=32.00MiB, used=48.00KiB
Metadata, DUP: total=9.29GiB, used=6.88GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
# btrfs fi usage /
Overall:
Device size: 330.00GiB
Device allocated:297.00GiB
Device unallocated: 33.00GiB
Device missing: 0.00B
Used:288.39GiB
Free (estimated): 36.73GiB (min: 20.23GiB)
Free (statfs, df):36.73GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:278.36GiB, Used:274.63GiB (98.66%)
/dev/mapper/slash 278.36GiB
Metadata,DUP: Size:9.29GiB, Used:6.88GiB (74.09%)
/dev/mapper/slash 18.57GiB
System,DUP: Size:32.00MiB, Used:48.00KiB (0.15%)
/dev/mapper/slash 64.00MiB
Unallocated:
/dev/mapper/slash 33.00GiB
And for comparison:
# df -h /
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/slash 330G 289G 37G 89% /
In all cases, the Used column actually corresponds to compressed size --
real blocks on disk and not uncompressed data size.
I have way too many subvolumes but here's an output that lists more than
289G "used"; I'm lazy so without snapshots:
# compsize -x / /home /var /var/lib/machines/ /nix
Processed 2722869 files, 1820146 regular extents (2063805 refs), 1625123 inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 76% 232G 302G 317G
none 100% 196G 196G 194G
zstd33% 34G 104G 122G
prealloc 100% 1.0G 1.0G 553M
Hm, not very convincing, adding a few (there's more, I guess adding all
of them should bring the Disk Usage column up to 289G but this just
takes too long for this mail -- the "proper" way to track snapshot usage
would be quota but I don't have these enabled here):
# compsize -x / /home /var /var/lib/machines/ /nix /.snapshots/{19,20}*/snapshot
Processed 10803451 files, 2110568 regular extents (7656942 refs), 5960388
inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 75% 249G 331G 732G
none 100% 206G 206G 281G
zstd33% 41G 123G 451G
prealloc 100% 1.0G 1.0G 551M
I would suggest finding what subvolumes you may have (btrfs subvolume
list /) and cleanup old ones, I'm not sure what is used by default
nowadays (snapper?) there might be higher level commands
They might not be visible from your mountpoint if your setup mounts a
subvolume by default, in which case you can mount your btrfs volume
somewhere else with -o subvol=/ for example to show everything and play
with compsize if you want.
--
Dominique
___
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
Can the BTRFS transparent compression mess with RPM's free space checks?
Hello! It's a bit late to ask this question, but it emerged when I noticed that after upgrading my PC to Silverblue 34 and after compressing manually my files, and doing some snapshots, rpm-ostree began complaining about the absence of free space... While compsize reported that I used only 84G(o/io?) of my 249Go filesystem... I then realized that because of the compression and the snapshots, ostree thought that my disk was full. The same problem happened with gnome-disk. I reported both issues[1][2]. But, in the rpm-ostree issue, jlebon raised an important question: does this also happen with RPM? Because if it does, this may mess up quite a bit the next Fedora Release... Note: I am not an expert in BTRFS or RPM, so, I'm sorry if this question is irrelevant. [1]: https://github.com/coreos/rpm-ostree/issues/2761 [2]: https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/211 ___ 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
[Bug 1950739] perl-Lingua-StopWords-0.12 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950739 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Lingua-StopWords-0.12- ||1.fc35 Resolution|--- |RAWHIDE Last Closed||2021-04-19 21:49:26 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Lingua-StopWords] PR #1: Tests
jplesnik merged a pull-request against the project: `perl-Lingua-StopWords` that you are following. Merged pull-request: `` Tests `` https://src.fedoraproject.org/rpms/perl-Lingua-StopWords/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Lingua-StopWords] PR #1: Tests
jplesnik opened a new pull-request against the project: `perl-Lingua-StopWords` that you are following: `` Tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Lingua-StopWords/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kdump with full-disk LUKS encryption
On Mon, 2021-04-19 at 18:24 +0100, Daniel P. Berrangé wrote: > On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote: > > On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote: > > > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote: > > > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to > > > > use a lot of memory. kdump is expected to use a minimal amount of > > > > memory. Users will have to reserve a huge amount of memory for kdump > > > > to work (eg. 1G reserve for kdump with 4G total memory which is not > > > > reasonable). > > > > > > I'm just going to sympathise with you rather than provide a good > > > answer here ... We had the same problem in libguestfs where Argon2 > > > used too much memory for our small appliance when opening LUKS2 disks. > > > We had to simply increase the amount of memory reserved, which is far > > > from ideal. > > > > Or you could switch to use PBKDF2, it is still a supported and > > reasonable option. > > libguestfs has to open whatever disk image the user gives it, and whoever > built the image originally decided whether it uses Argon2 or PBKDF2. My bad, I thought you were creating new partitions. Yeah argon2 has that "problem". In theory there is a tradeoff between memory vs CPU power, but it seem our implementation decided to go for memory and not give the option to use the more time consuming but less memory hungry algorithm. Simo. > 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 > > :| > ___ > 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://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
[EPEL-devel] Re: Getting conman into EPEL8
For what it's worth, there's a conman build for x86_64 and aarch64 in the loveshack/livhpc copr (untested). ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950578] perl-version-0.9929 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950578 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2021-d684a57861 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d684a57861` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d684a57861 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 --- Comment #6 from Fedora Update System --- FEDORA-2021-39b27b88ec has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-39b27b88ec` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-39b27b88ec See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 --- Comment #6 from Fedora Update System --- FEDORA-2021-7a8ebb70b5 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7a8ebb70b5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a8ebb70b5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1949332] perl-Crypt-OpenSSL-ECDSA-0.09 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1949332 --- Comment #9 from Fedora Update System --- FEDORA-2021-7a8ebb70b5 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7a8ebb70b5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a8ebb70b5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- FEDORA-2021-538e46d7a8 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-538e46d7a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-538e46d7a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- FEDORA-2021-97d373c145 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-97d373c145` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-97d373c145 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1949332] perl-Crypt-OpenSSL-ECDSA-0.09 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1949332 --- Comment #8 from Fedora Update System --- FEDORA-2021-97d373c145 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-97d373c145` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-97d373c145 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-34-20210419.n.0 compose check report
No missing expected images. Failed openQA tests: 4/127 (aarch64), 2/189 (x86_64) New failures (same test not failed in Fedora-34-20210418.n.0): ID: 861097 Test: aarch64 Server-dvd-iso install_default_upload@uefi URL: https://openqa.fedoraproject.org/tests/861097 ID: 861148 Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi URL: https://openqa.fedoraproject.org/tests/861148 ID: 861217 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/861217 ID: 861270 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/861270 Old failures (same test failed in Fedora-34-20210418.n.0): ID: 861166 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/861166 ID: 861241 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/861241 Soft failed openQA tests: 4/189 (x86_64), 5/127 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-34-20210418.n.0): ID: 860977 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/860977 ID: 861018 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/861018 ID: 861075 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/861075 ID: 861081 Test: aarch64 Minimal-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/861081 ID: 861094 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi URL: https://openqa.fedoraproject.org/tests/861094 ID: 861119 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/861119 ID: 861134 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/861134 ID: 861156 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/861156 ID: 861215 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/861215 Passed openQA tests: 95/127 (aarch64), 182/189 (x86_64) New passes (same test not passed in Fedora-34-20210418.n.0): ID: 861109 Test: aarch64 Server-dvd-iso support_server@uefi URL: https://openqa.fedoraproject.org/tests/861109 ID: 861118 Test: aarch64 Server-dvd-iso install_updates_nfs@uefi URL: https://openqa.fedoraproject.org/tests/861118 ID: 861154 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/861154 ID: 861239 Test: aarch64 universal install_blivet_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/861239 ID: 861260 Test: aarch64 universal install_blivet_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/861260 Skipped non-gating openQA tests: 23 of 316 Installed system changes in test x86_64 Server-boot-iso install_default: System load changed from 0.04 to 0.39 Previous test data: https://openqa.fedoraproject.org/tests/859941#downloads Current test data: https://openqa.fedoraproject.org/tests/860969#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: System load changed from 0.09 to 0.20 Previous test data: https://openqa.fedoraproject.org/tests/859942#downloads Current test data: https://openqa.fedoraproject.org/tests/860970#downloads Installed system changes in test x86_64 Workstation-live-iso install_default_upload: Used mem changed from 574 MiB to 763 MiB 1 services(s) removed since previous compose: fwupd.service System load changed from 0.76 to 0.63 Average CPU usage changed from 3.52857143 to 27.34285714 Previous test data: https://openqa.fedoraproject.org/tests/85#downloads Current test data: https://openqa.fedoraproject.org/tests/861027#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: System load changed from 1.06 to 0.91 Previous test data: https://openqa.fedoraproject.org/tests/860016#downloads Current test data: https://openqa.fedoraproject.org/tests/861044#downloads Installed system changes in test x86_64 Silverblue-dvd_ostree-iso install_default_upload: Mount /run contents changed to 70.99656357% of previous size System load changed from 1.32 to 0.54 Previous test data: https://openqa.fedoraproject.org/tests/860036#downloads Current test data: https://openqa.fedoraproject.org/tests/861064#downloads Installed system changes in test aarch64 Server-boot-iso install_default@uefi: System load changed from 0.21 to 0.42 Previous test data: https://openqa.fedoraproject.org/tests/860061#downloads Current test data: https://openqa.fedoraproject.org/tests/861089#downloads Installed system changes in test x86_64 universal
Re: wlroots 0.13.0 update for rawhide and f34
wlroots-0.13 is now available in rawhide. The compatibility issues are resolved via `wlroots0.12` package which will be installed on update if there is anything that depends on `libwlroots.so.7`. No rebuilds are necessary. If your package depends on the old wlroots API or hardware support, you may need to adjust build requirements to one of following: BuildRequires: pkgconfig(wlroots) = 0.12.0 BuildRequires: (pkgconfig(wlroots) >= 0.12 with pkgconfig(wlroots) < 0.13) for future builds. --- @atim, @fnux, @lyessaadi, if you want to have new versions of cage/hikari/labwc to be available in f34 as a day 0 update, you are welcome to use the side-tag `f34-build-side-40158` (`fedpkg build --target=f34-build-side-40158`). Merge ETA is in 1 day. Although in the case of hikari that might not work, as the side-tag does not contain libucl from `f34-updates-testing` :( On 4/7/21 1:54 PM, Aleksei Bavshin wrote: Greetings, wlroots 0.13.0 and sway 1.6 have been released today. As usual, the update is API and ABI breaking and all dependent packages must be rebuilt. For all the dependents I identified either upstream patches or ETA for the new release and have successful copr builds. I'm planning to create rawhide side-tag later today, rebuild all @sway-sig packages and send PRs with instructions to the packages I don't have access to. The side-tag will be merged in a week or when all the rebuilds are done. I also plan to prepare a day 0 update for f34 once rawhide rebuilds are completed. Let me know if you have any concerns about that. BCC: maintainer aliases for cage, labwc, phoc and wayfire -- With best regards, Aleksei Bavshin ___ 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
[Bug 1948241] perl-perlfaq-5.20210411 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948241 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-perlfaq-5.20210411-1.f |perl-perlfaq-5.20210411-1.f |c35 |c35 |perl-perlfaq-5.20210411-1.f |perl-perlfaq-5.20210411-1.f |c33 |c33 ||perl-perlfaq-5.20210411-1.f ||c32 --- Comment #6 from Fedora Update System --- FEDORA-2021-cc8bb1557c has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1948241] perl-perlfaq-5.20210411 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948241 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-perlfaq-5.20210411-1.f |perl-perlfaq-5.20210411-1.f |c35 |c35 ||perl-perlfaq-5.20210411-1.f ||c33 Resolution|--- |ERRATA Last Closed||2021-04-19 17:45:18 --- Comment #5 from Fedora Update System --- FEDORA-2021-4583f61395 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kdump with full-disk LUKS encryption
On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote: > On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote: > > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote: > > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to > > > use a lot of memory. kdump is expected to use a minimal amount of > > > memory. Users will have to reserve a huge amount of memory for kdump > > > to work (eg. 1G reserve for kdump with 4G total memory which is not > > > reasonable). > > > > I'm just going to sympathise with you rather than provide a good > > answer here ... We had the same problem in libguestfs where Argon2 > > used too much memory for our small appliance when opening LUKS2 disks. > > We had to simply increase the amount of memory reserved, which is far > > from ideal. > > Or you could switch to use PBKDF2, it is still a supported and > reasonable option. libguestfs has to open whatever disk image the user gives it, and whoever built the image originally decided whether it uses Argon2 or PBKDF2. 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 :| ___ 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
[Bug 1950637] perl-XML-LibXML-2.0207 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950637 --- Comment #1 from Fedora Update System --- FEDORA-2021-fe7f5688bc has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fe7f5688bc -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kdump with full-disk LUKS encryption
On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote: > On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote: > > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote: > > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to > > > use a lot of memory. kdump is expected to use a minimal amount of > > > memory. Users will have to reserve a huge amount of memory for kdump > > > to work (eg. 1G reserve for kdump with 4G total memory which is not > > > reasonable). > > > > I'm just going to sympathise with you rather than provide a good > > answer here ... We had the same problem in libguestfs where Argon2 > > used too much memory for our small appliance when opening LUKS2 disks. > > We had to simply increase the amount of memory reserved, which is far > > from ideal. > > Or you could switch to use PBKDF2, it is still a supported and > reasonable option. This is v2v of random, existing guests, so switching the encryption isn't an option. Rich. > Simo. > > -- > 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://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 virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ 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
[Bug 1950637] perl-XML-LibXML-2.0207 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950637 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-XML-LibXML-2.0207-1.fc ||35 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-93d78fa1a6 perl-Net-CIDR-Lite-0.22-1.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f08dc6b4c1 gnuchess-6.2.7-5.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3f9b6786f4 clamav-0.103.2-1.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-13ed778e19 singularity-3.7.3-1.el7 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9daa9fc0b1 seamonkey-2.53.7-3.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-fe3075d537 wordpress-5.1.9-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing libjwt-1.12.1-7.el7 rust-1.51.0-3.el7 Details about builds: libjwt-1.12.1-7.el7 (FEDORA-EPEL-2021-b8c4714317) A Javascript Web Token library in C Update Information: Same version, 1.12.1, but removed example programs Add libjwt to EPEL7 ChangeLog: References: [ 1 ] Bug #1940198 - Request to add libjwt to epel7 https://bugzilla.redhat.com/show_bug.cgi?id=1940198 rust-1.51.0-3.el7 (FEDORA-EPEL-2021-044df87bd4) The Rust Programming Language Update Information: Security fixes for CVE-2020-36323, CVE-2021-28876, CVE-2021-28878, CVE-2021-28879, and CVE-2021-31162. These are memory safety bugs in the Rust standard library. Because it is statically linked, affected applications will need to be rebuilt to benefit from the fixes. The actual security implications will depend on how these APIs are used in each particular case. ChangeLog: * Fri Apr 16 2021 Josh Stone - 1.51.0-3 - Security fixes for CVE-2020-36323, CVE-2021-31162 * Wed Apr 14 2021 Josh Stone - 1.51.0-2 - Security fixes for CVE-2021-28876, CVE-2021-28878, CVE-2021-28879 - Fix bootstrap for stage0 rust 1.51 References: [ 1 ] Bug #1949198 - CVE-2021-28876 rust: panic safety issue in Zip implementation https://bugzilla.redhat.com/show_bug.cgi?id=1949198 [ 2 ] Bug #1949207 - CVE-2021-28878 rust: memory safety violation in Zip implementation when next_back() and next() are used together https://bugzilla.redhat.com/show_bug.cgi?id=1949207 [ 3 ] Bug #1949211 - CVE-2021-28879 rust: integer overflow in the Zip implementation can lead to a buffer overflow https://bugzilla.redhat.com/show_bug.cgi?id=1949211 [ 4 ] Bug #1950396 - CVE-2020-36323 rust: optimization for joining strings can cause uninitialized bytes to be exposed https://bugzilla.redhat.com/show_bug.cgi?id=1950396 [ 5 ] Bug #1950398 - CVE-2021-31162 rust: double free in Vec::from_iter function if freeing the element panics https://bugzilla.redhat.com/show_bug.cgi?id=1950398 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-XML-LibXML] PR #1: Tests
jplesnik merged a pull-request against the project: `perl-XML-LibXML` that you are following. Merged pull-request: `` Tests `` https://src.fedoraproject.org/rpms/perl-XML-LibXML/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kdump with full-disk LUKS encryption
On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote: > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote: > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to > > use a lot of memory. kdump is expected to use a minimal amount of > > memory. Users will have to reserve a huge amount of memory for kdump > > to work (eg. 1G reserve for kdump with 4G total memory which is not > > reasonable). > > I'm just going to sympathise with you rather than provide a good > answer here ... We had the same problem in libguestfs where Argon2 > used too much memory for our small appliance when opening LUKS2 disks. > We had to simply increase the amount of memory reserved, which is far > from ideal. Or you could switch to use PBKDF2, it is still a supported and reasonable option. Simo. -- 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://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-Rawhide-20210419.n.0 compose check report
No missing expected images. Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 9/189 (x86_64), 18/127 (aarch64) New failures (same test not failed in Fedora-Rawhide-20210418.n.0): ID: 860505 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/860505 ID: 860528 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/860528 ID: 860555 Test: aarch64 Server-dvd-iso install_blivet_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/860555 ID: 860562 Test: aarch64 Server-dvd-iso install_vnc_server@uefi URL: https://openqa.fedoraproject.org/tests/860562 ID: 860563 Test: aarch64 Server-dvd-iso server_freeipa_replication_master@uefi URL: https://openqa.fedoraproject.org/tests/860563 ID: 860564 Test: aarch64 Server-dvd-iso server_freeipa_replication_replica@uefi URL: https://openqa.fedoraproject.org/tests/860564 ID: 860578 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/860578 ID: 860579 Test: aarch64 Server-dvd-iso server_freeipa_replication_client@uefi URL: https://openqa.fedoraproject.org/tests/860579 ID: 860585 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/860585 ID: 860601 Test: aarch64 Workstation-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/860601 Old failures (same test failed in Fedora-Rawhide-20210418.n.0): ID: 860465 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/860465 ID: 860468 Test: x86_64 Server-dvd-iso server_cockpit_updates URL: https://openqa.fedoraproject.org/tests/860468 ID: 860583 Test: aarch64 Server-dvd-iso modularity_tests@uefi URL: https://openqa.fedoraproject.org/tests/860583 ID: 860625 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/860625 ID: 860674 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/860674 ID: 860681 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/860681 ID: 860696 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/860696 ID: 860697 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/860697 ID: 860700 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/860700 ID: 860703 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/860703 ID: 860711 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/860711 ID: 860712 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/860712 ID: 860729 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/860729 ID: 860730 Test: aarch64 universal upgrade_minimal_64bit@uefi URL: https://openqa.fedoraproject.org/tests/860730 ID: 860732 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/860732 ID: 860742 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/860742 ID: 860743 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/860743 Soft failed openQA tests: 3/189 (x86_64), 4/127 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Rawhide-20210418.n.0): ID: 860436 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/860436 ID: 860477 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/860477 ID: 860534 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/860534 ID: 860540 Test: aarch64 Minimal-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/860540 ID: 860553 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi URL: https://openqa.fedoraproject.org/tests/860553 ID: 860593 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/860593 ID: 860615 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/860615 Passed openQA tests: 176/189 (x86_64), 93/127 (aarch64) New passes (same test not passed in Fedora-Rawhide-20210418.n.0): ID: 860484 Test: x86_64 Everything-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/860484 ID: 860523 Test: x86_64
[Bug 1950739] perl-Lingua-StopWords-0.12 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950739 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|iarn...@gmail.com, | |lkund...@v3.sk | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950637] perl-XML-LibXML-2.0207 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950637 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|caillon+fedoraproject@gmail | |.com, ka...@ucw.cz, | |mspa...@redhat.com, | |rhug...@redhat.com, | |rstr...@redhat.com, | |sandm...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-XML-LibXML] PR #1: Tests
jplesnik opened a new pull-request against the project: `perl-XML-LibXML` that you are following: `` Tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-XML-LibXML/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-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
On Mon, Apr 19, 2021 at 03:35:40PM +0200, Pierre-Yves Chibon wrote: > On Mon, Apr 19, 2021 at 09:11:19AM -0400, Ben Cotton wrote: > > On Sun, Apr 18, 2021 at 4:13 PM Zbigniew Jędrzejewski-Szmek > > wrote: > > > > > > What about the unused "qa contact field"? Kevin suggested dropping > > > qa-extras [1], but it never went anywhere, afaics? > > > > > Good idea. I have a few other BZ cleanup things I want to look at > > post-release. I'll add this to the list. > > This one may have been done already actually, worth double checking though. I think we are creating new components without it, but have not yet removed it from existing ones. If you can take on removing it from all existing components that would be great. And then I guess on existing open bugs? (hopefully without generating email). Or perhaps we just leave existing bugs alone... 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
[Bug 1950578] perl-version-0.9929 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950578 --- Comment #2 from Fedora Update System --- FEDORA-2021-d684a57861 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d684a57861 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950578] perl-version-0.9929 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950578 --- Comment #1 from Fedora Update System --- FEDORA-2021-958f634819 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-958f634819 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950578] perl-version-0.9929 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950578 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-version-0.99.29-1.fc35 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-version] PR #2: Tests
jplesnik merged a pull-request against the project: `perl-version` that you are following. Merged pull-request: `` Tests `` https://src.fedoraproject.org/rpms/perl-version/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[389-devel] Reminder: please review: PR 4720 - remove problematic language from source code and config
On 4/8/21 3:15 PM, Mark Reynolds wrote: https://github.com/389ds/389-ds-base/pull/4720 -- 389 Directory Server Development Team ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: matio: Not announced soname change in stable branch
I'll fix those as well. -- Gwyn Ciesla she/her/hers in your fear, seek only peace in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Monday, April 19, 2021 9:13 AM, Remi Collet wrote: > Le 05/04/2021 à 23:19, Gwyn Ciesla via devel a écrit : > > > Updates are now in flight for kst, libASL, openmeeg, and vips, for f34 and > > f33. gtatool is retired and FTBFS, so I left it alone. > > Looks like the same happens today in Fedora 32 > > Remi > > > -- > > Gwyn Ciesla > > she/her/hers > > > > > > > > in your fear, seek only peace > > in your fear, seek only love > > -d. bowie > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On Monday, April 5, 2021 8:29 AM, Gwyn Ciesla via devel > > devel@lists.fedoraproject.org wrote: > > > > > My apologies; 1.5.18 fixes a few CVEs, and the subsequent releases fixed > > > regressions. I'm usually much more scrupulous about soname changes. I've > > > added versioning to the solib's %files line in the spec, and will take > > > care of the broken packages. > > > > > -- > > > Gwyn Ciesla > > > she/her/hers > > > > > > > > > > > > in your fear, seek only peace > > > in your fear, seek only love > > > -d. bowie > > > > > Sent with ProtonMail Secure Email. > > > > > ‐‐‐ Original Message ‐‐‐ > > > On Friday, April 2, 2021 11:45 PM, Remi Collet fed...@famillecollet.com > > > wrote: > > > > > > It looks like matio have been updated in Fedora 33 > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2021-0933889858 > > > > > > From matio 1.5.17 with soname 9 > > > > To matio 1.5.21 with soname 11 > > > > > > This doesn't seems acceptable, or, at least, should be managed > > > > > > Used by: > > > > > > gtatool-matlab-0:2.2.3-6.fc33.x86_64 > > > > kst-0:2.0.8-29.fc33.x86_64 > > > > libASL-0:0.1.7-24.fc33.x86_64 > > > > openmeeg-0:2.4.2-0.8.fc33.x86_64 > > > > vips-0:8.9.2-1.fc33.x86_64 > > > > > > Remi > > > > > > P.S. and an "empty" bodhi description seems also bad > > > > > > 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 > > > > 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 signature.asc Description: OpenPGP digital 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: matio: Not announced soname change in stable branch
Le 05/04/2021 à 23:19, Gwyn Ciesla via devel a écrit : Updates are now in flight for kst, libASL, openmeeg, and vips, for f34 and f33. gtatool is retired and FTBFS, so I left it alone. Looks like the same happens today in Fedora 32 Remi -- Gwyn Ciesla she/her/hers in your fear, seek only peace in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Monday, April 5, 2021 8:29 AM, Gwyn Ciesla via devel wrote: My apologies; 1.5.18 fixes a few CVEs, and the subsequent releases fixed regressions. I'm usually much more scrupulous about soname changes. I've added versioning to the solib's %files line in the spec, and will take care of the broken packages. -- Gwyn Ciesla she/her/hers in your fear, seek only peace in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, April 2, 2021 11:45 PM, Remi Collet fed...@famillecollet.com wrote: It looks like matio have been updated in Fedora 33 https://bodhi.fedoraproject.org/updates/FEDORA-2021-0933889858 From matio 1.5.17 with soname 9 To matio 1.5.21 with soname 11 This doesn't seems acceptable, or, at least, should be managed Used by: gtatool-matlab-0:2.2.3-6.fc33.x86_64 kst-0:2.0.8-29.fc33.x86_64 libASL-0:0.1.7-24.fc33.x86_64 openmeeg-0:2.4.2-0.8.fc33.x86_64 vips-0:8.9.2-1.fc33.x86_64 Remi P.S. and an "empty" bodhi description seems also bad 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 ___ 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
[rpms/perl-version] PR #2: Tests
jplesnik opened a new pull-request against the project: `perl-version` that you are following: `` Tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-version/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-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
On Mon, Apr 19, 2021 at 09:11:19AM -0400, Ben Cotton wrote: > On Sun, Apr 18, 2021 at 4:13 PM Zbigniew Jędrzejewski-Szmek > wrote: > > > > What about the unused "qa contact field"? Kevin suggested dropping > > qa-extras [1], but it never went anywhere, afaics? > > > Good idea. I have a few other BZ cleanup things I want to look at > post-release. I'll add this to the list. This one may have been done already actually, worth double checking though. 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
Re: F35 Change: Switching Cyrus Sasl from BerkeleyDB to GDBM (System-Wide Change proposal)
On Fri, Apr 16, 2021 at 03:48:04PM -0400, Simo Sorce wrote: 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. I think this should be acceptable. Leaving the previous DB should a revert of the software be necessary leaves users with the ability to run what they had set up. I'd like to see that noted in the proposal. Thanks, 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 -- 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
Re: Disabling BZ `fedora_requires_release_note` flag
On Sun, Apr 18, 2021 at 4:13 PM Zbigniew Jędrzejewski-Szmek wrote: > > What about the unused "qa contact field"? Kevin suggested dropping > qa-extras [1], but it never went anywhere, afaics? > Good idea. I have a few other BZ cleanup things I want to look at post-release. I'll add this to the list. -- 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: 20210419.n.0 changes
OLD: Fedora-34-20210418.n.0 NEW: Fedora-34-20210419.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Python_Classroom raw-xz armhfp Path: Labs/armhfp/images/Fedora-Python-Classroom-34-20210419.n.0.armhfp.raw.xz = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = 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
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 --- Comment #4 from Fedora Update System --- FEDORA-2021-538e46d7a8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-538e46d7a8 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 --- Comment #2 from Fedora Update System --- FEDORA-2021-e9797584a7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e9797584a7 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 --- Comment #3 from Fedora Update System --- FEDORA-2021-39b27b88ec has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-39b27b88ec -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Pod-Weaver-4.017-1.fc3 ||5 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Pod-Weaver] PR #1: Tests
ppisar merged a pull-request against the project: `perl-Pod-Weaver` that you are following. Merged pull-request: `` Tests `` https://src.fedoraproject.org/rpms/perl-Pod-Weaver/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads up, upcoming mass spec update to explicitly BuildRequire python3-setuptools
Hello everyone, we successfully pushed explicit python3-setuptools BuildRequire to all affected packages. As mentioned in the Change proposal, there is no need to rebuild them, it will be done together with Python 3.10. mass rebuild. Regards, Tomáš Hrnčiar On Fri, Mar 26, 2021 at 2:50 PM Tomas Hrnciar wrote: > Hello everyone, > > some of you might have already seen the F35 Change [0] we submitted last > week. > > We are trying to reduce the number of Python packages unnecessarily > Requiring python3-setuptools. If you are interested in technical details > see the change proposal [1], there is a broad explanation of why we are > doing this. > > If the change is approved by FESCo we plan to do the mass spec update > that will add explicit BuildRequire on python3-setuptools for all affected > packages. We'll try to make this addition consistent with the actual style > used in the spec files, but nobody's perfect and there might be some > discrepancies; so please, if your package is listed below, check this > diff [2] to see how the change will look like. If you disagree with the > way how the BuildRequires will be added, feel free to add it yourself in > any other way you prefer before 2021-04-15. A push to the rawhide/main > branch in dist-git is sufficient, no need to bump the release or rebuild > the package. > > We plan to update the list of affected packages again before we actually > do the change. If you wish to opt-out of this change entirely, please let > us know by editing the change wiki page and moving your package into the > "Packages to be ignored" section [3] before 2021-04-15. However, bear in > mind that this will likely cause future failures to build from source if > your package actually needs setuptools to build. > > Thank you for your cooperation. > Tomáš Hrnčiar > > [0] > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/LGAUGOYHFKQXTS55IRWSIUVVAO3YHD5R/ > [1] > https://fedoraproject.org/wiki/Changes/Reduce_dependencies_on_python3-setuptools > [2] > https://github.com/hrnciar/add-setuptools-buildrequire/compare/c082a1a...a60a447 > [3] > https://fedoraproject.org/wiki/Changes/Reduce_dependencies_on_python3-setuptools#Packages_to_be_ignored > > List of all affected packages: > > Maintainers by package: > 0ad ignatenkobrain pcpa pwalter > OpenMolcas jussilehtola > PyGreSQL hhorak jmlich odubaj panovotn pkubat praiskup > R2spec pingou > ViTables tnorth zbyszek > ansible-review dcallagh ttrinks > barman slaanesh tsao > blender design-sw hobbes1069 ignatenkobrain kwizart luya roma > s4504kr slaanesh > btrfs-progs ignatenkobrain josef ngompa sandeen > bumpversion duriantang jdornak > calypso rathann > cinchgreghellings > commissaire-client mbarnes smilner > cppcheck c72578 jussilehtola sgrubb > cranclenkaseg > crudini apevec jruzicka pbrady > cxxtest mgieseki > datanommer ralph > dlib bizdelnick luya > ec2-hibinit-agentdavdunc > electrum tredaell > fbthrift dcavalca filbranden salimma > fedora-messaging abompard > firefox alexl caolanm erack gecko-maint jgrulich kalev > kengert mbarnes rhughes rstrode sharkcz stransky tpopela ueno xhorak > follydcavalca filbranden salimma > fontforgefrixxon kevin pnemade > gajimmichich suraia > gau2grid jussilehtola > gfal2-python adev andreamanzi > gingalupinix > git-filter-repo asn > gns3-gui kwizart > gns3-net-converter kwizart > gns3-server kwizart nucleo > gpsd fab mlichvar ttorling > h5py stevetraylen terjeros > khardmathstuf sdyroff > kismon fab > koji ausil kevin mikem puiterwijk > lammps ellio167 junghans > legofy lkf williamjmorenor > libcaca hubbitus slaanesh thias > libiptcdata dcm hobbes1069 jchaloup > libnuml sagitter > libreoffice caolanm dtardon erack sbergmann > lldb airlied daveisfera jankratochvil sergesanspaille > siddharths tstellar > llvm dmalcolm ignatenkobrain jakub jistone kyle scottt > sergesanspaille siddharths tstellar > llvm10 sergesanspaille tstellar > llvm11 sergesanspaille tstellar > llvm7.0 jistone petersen sergesanspaille tstellar > llvm9.0 jistone sergesanspaille tstellar > mercurialkiilerix nbecker pstodulk > mod_wsgi jdornak jkaluza jorton lmacken mrunge > moosezbyszek > mypaint avsej > mysql-connector-python hhorak hubbitus hvad mschorm > nototoolsmfabian pwu > officeparser rebus > offlineimap cicku
Re: Heads up, upcoming mass spec update to explicitly BuildRequire python3-setuptools
Hello everyone, we successfully pushed explicit python3-setuptools BuildRequire to all affected packages. As mentioned in the Change proposal, there is no need to rebuild them, it will be done together with Python 3.10. mass rebuild. Regards, Tomáš Hrnčiar On Fri, Mar 26, 2021 at 2:50 PM Tomas Hrnciar wrote: > Hello everyone, > > some of you might have already seen the F35 Change [0] we submitted last > week. > > We are trying to reduce the number of Python packages unnecessarily > Requiring python3-setuptools. If you are interested in technical details > see the change proposal [1], there is a broad explanation of why we are > doing this. > > If the change is approved by FESCo we plan to do the mass spec update > that will add explicit BuildRequire on python3-setuptools for all affected > packages. We'll try to make this addition consistent with the actual style > used in the spec files, but nobody's perfect and there might be some > discrepancies; so please, if your package is listed below, check this > diff [2] to see how the change will look like. If you disagree with the > way how the BuildRequires will be added, feel free to add it yourself in > any other way you prefer before 2021-04-15. A push to the rawhide/main > branch in dist-git is sufficient, no need to bump the release or rebuild > the package. > > We plan to update the list of affected packages again before we actually > do the change. If you wish to opt-out of this change entirely, please let > us know by editing the change wiki page and moving your package into the > "Packages to be ignored" section [3] before 2021-04-15. However, bear in > mind that this will likely cause future failures to build from source if > your package actually needs setuptools to build. > > Thank you for your cooperation. > Tomáš Hrnčiar > > [0] > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/LGAUGOYHFKQXTS55IRWSIUVVAO3YHD5R/ > [1] > https://fedoraproject.org/wiki/Changes/Reduce_dependencies_on_python3-setuptools > [2] > https://github.com/hrnciar/add-setuptools-buildrequire/compare/c082a1a...a60a447 > [3] > https://fedoraproject.org/wiki/Changes/Reduce_dependencies_on_python3-setuptools#Packages_to_be_ignored > > List of all affected packages: > > Maintainers by package: > 0ad ignatenkobrain pcpa pwalter > OpenMolcas jussilehtola > PyGreSQL hhorak jmlich odubaj panovotn pkubat praiskup > R2spec pingou > ViTables tnorth zbyszek > ansible-review dcallagh ttrinks > barman slaanesh tsao > blender design-sw hobbes1069 ignatenkobrain kwizart luya roma > s4504kr slaanesh > btrfs-progs ignatenkobrain josef ngompa sandeen > bumpversion duriantang jdornak > calypso rathann > cinchgreghellings > commissaire-client mbarnes smilner > cppcheck c72578 jussilehtola sgrubb > cranclenkaseg > crudini apevec jruzicka pbrady > cxxtest mgieseki > datanommer ralph > dlib bizdelnick luya > ec2-hibinit-agentdavdunc > electrum tredaell > fbthrift dcavalca filbranden salimma > fedora-messaging abompard > firefox alexl caolanm erack gecko-maint jgrulich kalev > kengert mbarnes rhughes rstrode sharkcz stransky tpopela ueno xhorak > follydcavalca filbranden salimma > fontforgefrixxon kevin pnemade > gajimmichich suraia > gau2grid jussilehtola > gfal2-python adev andreamanzi > gingalupinix > git-filter-repo asn > gns3-gui kwizart > gns3-net-converter kwizart > gns3-server kwizart nucleo > gpsd fab mlichvar ttorling > h5py stevetraylen terjeros > khardmathstuf sdyroff > kismon fab > koji ausil kevin mikem puiterwijk > lammps ellio167 junghans > legofy lkf williamjmorenor > libcaca hubbitus slaanesh thias > libiptcdata dcm hobbes1069 jchaloup > libnuml sagitter > libreoffice caolanm dtardon erack sbergmann > lldb airlied daveisfera jankratochvil sergesanspaille > siddharths tstellar > llvm dmalcolm ignatenkobrain jakub jistone kyle scottt > sergesanspaille siddharths tstellar > llvm10 sergesanspaille tstellar > llvm11 sergesanspaille tstellar > llvm7.0 jistone petersen sergesanspaille tstellar > llvm9.0 jistone sergesanspaille tstellar > mercurialkiilerix nbecker pstodulk > mod_wsgi jdornak jkaluza jorton lmacken mrunge > moosezbyszek > mypaint avsej > mysql-connector-python hhorak hubbitus hvad mschorm > nototoolsmfabian pwu > officeparser rebus > offlineimap cicku
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 --- Comment #1 from Petr Pisar --- An enhancement release suitable for all Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Pod-Weaver] PR #1: Tests
ppisar opened a new pull-request against the project: `perl-Pod-Weaver` that you are following: `` Tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Pod-Weaver/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950700] perl-Pod-Weaver-4.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950700 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED CC|ppi...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kdump with full-disk LUKS encryption
On 19.04.2021 13:02, Richard W.M. Jones wrote: I'm just going to sympathise with you rather than provide a good answer here ... We had the same problem in libguestfs where Argon2 used too much memory for our small appliance when opening LUKS2 disks. We had to simply increase the amount of memory reserved, which is far from ideal. Argon2 is designed to allocate large amounts of memory to withstand brute-force on GPUs. -- 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
Fedora rawhide compose report: 20210419.n.0 changes
OLD: Fedora-Rawhide-20210418.n.0 NEW: Fedora-Rawhide-20210419.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 1 Dropped packages:1 Upgraded packages: 63 Downgraded packages: 0 Size of added packages: 1.41 MiB Size of dropped packages:257.51 MiB Size of upgraded packages: 636.19 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -3.79 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Astronomy_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-Rawhide-20210418.n.0.iso = ADDED PACKAGES = Package: python-neurom-1.8.0-1.fc35 Summary: Neuronal Morphology Analysis Tool RPMs:python-neurom-doc python3-neurom Size:1.41 MiB = DROPPED PACKAGES = Package: virtualplanet-2.5-11.164svn.fc34 Summary: An atlas for planets surface formations RPMs:virtualplanet virtualplanet-data-base virtualplanet-data-historical virtualplanet-doc Size:257.51 MiB = UPGRADED PACKAGES = Package: autofs-1:5.1.7-12.fc35 Old package: autofs-1:5.1.7-10.fc35 Summary: A tool for automatically mounting and unmounting filesystems RPMs: autofs Size: 1.86 MiB Size change: 6.59 KiB Changelog: * Mon Apr 19 2021 Ian Kent - 1:5.1.7-12 - Coverity fixes. - add missing free in handle_mounts(). - remove redundant if check. - fix possible memory leak in master_parse(). - fix possible memory leak in mnts_add_amdmount(). - fix double unlock in parse_mount(). - add length check in umount_subtree_mounts(). - fix flags check in umount_multi(). - dont try umount after stat() ENOENT fail. - remove redundant assignment in master_add_amd_mount_section_mounts(). - fix dead code in mnts_add_mount(). - fix arg not used in error print. - fix missing lock release in mount_subtree(). - fix double free in parse_mapent(). - refactor lookup_prune_one_cache() a bit. - cater for empty mounts list in mnts_get_expire_list(). - add ext_mount_hash_mutex lock helpers. - fix amd section mounts map reload. - fix dandling symlink creation if nis support is not available. Package: blinken-21.04.0-1.fc35 Old package: blinken-20.12.3-1.fc35 Summary: Memory Enhancement Game RPMs: blinken Size: 11.47 MiB Size change: 851.84 KiB Changelog: * Sat Apr 17 2021 Rex Dieter - 21.04.0-1 - 21.04.0 Package: cantor-21.04.0-1.fc35 Old package: cantor-20.12.2-3.fc35 Summary: KDE Frontend to Mathematical Software RPMs: cantor cantor-R cantor-devel cantor-julia cantor-libs Size: 13.11 MiB Size change: 20.67 KiB Changelog: * Wed Mar 03 2021 Rex Dieter - 20.12.3-1 - 20.12.3 * Sat Apr 17 2021 Rex Dieter - 21.04.0-1 - 21.04.0 Package: cozy-0.9.1-1.fc35 Old package: cozy-0.8.1-1.fc34 Summary: Modern audiobook player RPMs: cozy Size: 280.51 KiB Size change: 6.36 KiB Changelog: * Mon Apr 19 2021 Artur Frenszek-Iwicki - 0.9.1-1 - Update to latest release Package: dolphin-plugins-21.04.0-1.fc35 Old package: dolphin-plugins-20.12.3-1.fc35 Summary: Dolphin plugins for revision control systems RPMs: dolphin-plugins Size: 2.55 MiB Size change: 15.13 KiB Changelog: * Sat Apr 17 2021 Rex Dieter - 21.04.0-1 - 21.04.0 Package: dummy-test-package-gloster-0-3455.fc35 Old package: dummy-test-package-gloster-0-3444.fc35 Summary: Dummy Test Package called Gloster RPMs: dummy-test-package-gloster Size: 214.74 KiB Size change: 678 B Changelog: * Sun Apr 18 2021 packagerbot - 0-3445 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3446 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3447 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3448 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3449 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3450 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3451 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3452 - rebuilt * Sun Apr 18 2021 packagerbot - 0-3453 - rebuilt * Mon Apr 19 2021 packagerbot - 0-3454 - rebuilt * Mon Apr 19 2021 packagerbot - 0-3455 - rebuilt Package: emacs-transient-0.3.0-1.20210221git9ca983bab.fc35 Old package: emacs-transient-0.2.0-3.20210117git8ad5fb83c.fc34 Summary: Emacs transient key maps RPMs: emacs-transient Size: 96.93 KiB Size change: 113 B Changelog: * Sun Apr 18 2021 Tulio Magno Quites Machado Filho - 0.2.0-2.20210117git8ad5fb83c - Update to version 0.3.0. Package: foot-1.7.2-1.fc35 Old package: foot-1.7.1-1.fc35 Summary: Fast, lightweight and minimalistic Wayland terminal emulator RPMs: foot foot-terminfo Size: 1.15 MiB Size change: 11.62 KiB Changelog: * Sun Apr 18 2021 Aleksei Bavshin - 1.7.2-1 - Update to 1.7.2 Package: gap-pkg-browse
[Bug 1950578] perl-version-0.9929 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950578 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|mmasl...@redhat.com,| |mspa...@redhat.com, | |spo...@gmail.com| Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950067] perl-PDL-2.038 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950067 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-PDL-2.38.0-1.fc35 Resolution|--- |RAWHIDE Last Closed||2021-04-19 11:19:12 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Help needed] Possible change from gcc failed both openxr and luxcorerender
On 18/04/21 23:38 -0700, Luya Tshimbalanga wrote: On 2021-04-15 6:33 a.m., Jonathan Wakely wrote: The error for this build is completely different to the errors you showed above: /builddir/build/BUILD/LuxCore-luxcorerender_v2.5/include/luxrays/utils/utils.h:40:18: error: 'std::std' has not been declared 40 | #define isinf(f) std::isinf(f) | ^~~ That's a bug in the source package. What will be the suggestion to address that issue before contacting upstream luxcorerender? Replace the silly macro above with something like: using std::isinf; ___ 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: Kdump with full-disk LUKS encryption
On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote: > 2. LUKS2 prefers Argon2 as the key derivation function, designed to > use a lot of memory. kdump is expected to use a minimal amount of > memory. Users will have to reserve a huge amount of memory for kdump > to work (eg. 1G reserve for kdump with 4G total memory which is not > reasonable). I'm just going to sympathise with you rather than provide a good answer here ... We had the same problem in libguestfs where Argon2 used too much memory for our small appliance when opening LUKS2 disks. We had to simply increase the amount of memory reserved, which is far from ideal. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ ___ 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
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 --- Comment #4 from Fedora Update System --- FEDORA-2021-97d373c145 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-97d373c145 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 --- Comment #3 from Fedora Update System --- FEDORA-2021-7a8ebb70b5 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a8ebb70b5 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 --- Comment #2 from Fedora Update System --- FEDORA-2021-00c5e3447d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-00c5e3447d -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Crypt-OpenSSL-ECDSA-0. ||10-1.fc35 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for all Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1950616] perl-Crypt-OpenSSL-ECDSA-0.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950616 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED CC|jples...@redhat.com,| |ppi...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Spaces in tarball directory name
On 19.04.2021 04:28, Qiyu Yan wrote:
What if %autosetup -n Foo\ Bar-%{version} ?
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.fqLJUo
+ umask 022
+ cd /home/vitaly/rpmbuild/BUILD
+ cd /home/vitaly/rpmbuild/BUILD
+ rm -rf Foo
+ /usr/bin/gzip -dc /home/vitaly/rpmbuild/SOURCES/Foo.Bar-1.0.0.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Foo
/var/tmp/rpm-tmp.fqLJUo: line 39: cd: Foo: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.fqLJUo (%prep)
--
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
Re: Spaces in tarball directory name
On 18.04.2021 22:46, Nico Kadel-Garcia wrote:
What tarball is this? Because that sort of cutesy tarball name is
well, not going to work well for any standard release software.
JetBrains Rider for example. Tarball name:
"JetBrains.Rider-%{version}.tar.gz", directory name - "JetBrains
Rider-%{version}".
--
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
Fedora-Cloud-32-20210419.0 compose check report
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-20210418.0): ID: 860415 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/860415 ID: 860422 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/860422 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: PETSc 3.15
PETSc-3.15 is built in side-tag f35-build-side-40112 Please, rebuild your own related package. On 4/10/21 7:26 PM, Antonio T. sagitter wrote: Hi all. PETSc 3.15 is coming in Rawhide branch. Release notes: https://www.mcs.anl.gov/petsc/documentation/changes/315.html Dependencies in Fedora: $ repoquery --disablerepo=* --enablerepo=fedora*-source --whatrequires petsc-openmpi-devel bout++-0:4.3.1-7.fc33.src freefem++-0:4.6-6.fc33.src petsc4py-0:3.13.0-5.fc33.src python-steps-0:3.5.0-5.fc33.src -- --- Antonio Trande Fedora Project mailto: sagit...@fedoraproject.org GPG key: 0x29FBC85D7A51CC2F GPG key server: https://keys.gnupg.net/ OpenPGP_0x29FBC85D7A51CC2F.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital 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
Kdump with full-disk LUKS encryption
Hi all, I'm currently trying to add kdump support for systemd with full-disk LUKS encryption. vmcores contain sensitive data so they should also be protected, and network dumps sometimes are not available. So kdump has to open the LUKS encrypted device in the kdump environment. I'm using systemd/dracut, my work machine is running Fedora 34, and there are several problems I'm trying to solve: 1. Users have to input the password in the kdump kernel environment. But users often don't have shell access to the kdump environment. (headless server, graphic card not working after kexec, both are very common) 2. LUKS2 prefers Argon2 as the key derivation function, designed to use a lot of memory. kdump is expected to use a minimal amount of memory. Users will have to reserve a huge amount of memory for kdump to work (eg. 1G reserve for kdump with 4G total memory which is not reasonable). To fix these problems, I tried to pass the master key to the second kernel directly via initramfs. Kdump will modify the initramfs in ramfs to include the key, kexec_load it, and never write to any actual back storage. This worked with old LUKS configurations. But LUKS2/cryptsetup now stores the key in the kernel keyring by default. The key is accessible from userspace. Users can enter the password to start kdump manually and then it will work, but usually people expect kdump service to start automatically. (WIP patch series: https://lists.fedoraproject.org/archives/list/ke...@lists.fedoraproject.org/thread/RTYJEQ4BV25JYVYJHTTPOK476FUEJOWW/) I've several ideas about how to improve it but not sure which one is better, and if this is a good idea after all: 1. Simply introduce a config to let systemd-cryptsetup disable kernel keyring on setup, there is currently no such option. 2. If we can let the key stay in userspace for a little longer, eg. for systems booted with dracut/systemd, when systemd-cryptsetup@%s.service opens the crypt device, keep the key in dm-crypt. And later when services like kdump have finished loading, cryptsetup can refresh the device and store the key in the kernel keyring again. 3. Let kdump use some custom helper/service to load all needed resources in the early initrd boot stage, prior to systemd-cryptsetup@%s.service. It will ask the password / parse the keyfile and load kdump, then provide info for systemd-cryptsetup or just do the setup. Or maybe let systemd-cryptsetup support some kind of "plugins" so other tools can use it. 4. A better and safer solution seems to keep a consistent key ring between kexec boots but also more complex and difficult as different arch implements kexec differently. Any suggestions are welcomed! -- Best Regards, Kairui Song ___ 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: nando pavlix
On 19. 04. 21 10:52, Pierre-Yves Chibon wrote: On Fri, Apr 16, 2021 at 03:12:34PM +0200, Pierre-Yves Chibon wrote: 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 - nando contacted since March 26th - pavlix contacted since March 18th Thanks to zoglesby and liangwen12year for fixing their accounts. Does anyone know how to contact nando and pavlix? I know how to contact pavlix. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
Next for ARC - researching how to replace PDC
Hi everyone, ARC team - that is me, Vipul and Mark, are looking to figure out possible ways how we could replace our current PDC [0] whose project has gone unmaintained for years [1]. We plan to share what we find out in our https://fedora-arc.readthedocs.io/en/latest/pdc/index.html It would be really helpful if any other users of PDC would reach out, so that we don't leave anybody behind. First, is there anybody using the PDC UI? So far we have identified, only api/cli usage. Second, based on a cursory search through our infrastructure configuration far we identified usage in: - Release Engineering scripts - https://pagure.io/releng/ - fedpkg - https://pagure.io/fedpkg - pungi - https://pagure.io/pungi/ - fedfind - https://pagure.io/fedora-qa/fedfind - bodhi - https://github.com/fedora-infra/bodhi/ - pagure - https://pagure.io/pagure/ - MBS - https://pagure.io/fm-orchestrator/ - mirrormanager scripts - https://pagure.io/Fedora-Infra/ansible - ODCS - https://pagure.io/odcs - the new hotness - https://github.com/fedora-infra/the-new-hotness - fedora messaging - https://github.com/fedora-infra/fedora-messaging - osbs client - https://github.com/containerbuildsystem/osbs-client Is there anything we are forgetting about? Thanks! Adam and the rest of the ARC team [0] https://pdc.fedoraproject.org/ [1] https://github.com/product-definition-center/product-definition-center [2] https://fedora-arc.readthedocs.io/en/latest/pdc/index.html ___ 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: nando pavlix
On Fri, Apr 16, 2021 at 03:12:34PM +0200, Pierre-Yves Chibon wrote: > 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 > > - nando contacted since March 26th > - pavlix contacted since March 18th Thanks to zoglesby and liangwen12year for fixing their accounts. Does anyone know how to contact nando and pavlix? Pierre > 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 ___ 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-33-20210419.0 compose check report
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-20210418.0): ID: 860295 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/860295 ID: 860302 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/860302 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: What do we think about always autoreconfing? (was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))
On Fri, Apr 16, 2021 at 3:30 PM David Cantrell wrote: > 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. > Document with common failures and fixes already exists [1]. Also multiple ways of testing are documented in the change proposal [2], where the link to the document [1] is present. Updating autoconf to version 2.71 is a hard process, we are doing our best to make it as fluent as possible. There is a copr created for testing, bugs in bugzilla created (with link to change proposal) for failing components and we are actively moving things forward. Hopefully it will be enough to make this possible. [1] https://docs.google.com/document/d/1SAGTJZEF9z_nkHMbXTF-YTTvKRja7ygfOOMzl-DYBSk/edit [2] https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test > 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: [Help needed] Possible change from gcc failed both openxr and luxcorerender
On 2021-04-15 6:33 a.m., Jonathan Wakely wrote: The error for this build is completely different to the errors you showed above: /builddir/build/BUILD/LuxCore-luxcorerender_v2.5/include/luxrays/utils/utils.h:40:18: error: 'std::std' has not been declared 40 | #define isinf(f) std::isinf(f) | ^~~ That's a bug in the source package. What will be the suggestion to address that issue before contacting upstream luxcorerender? Result from openxr https://copr.fedorainfracloud.org/coprs/luya/blender-egl/build/2131057/ This one has the errors above, and there is no sign of -lstdc++fs in the linker command. It's a package bug. You are right. I managed to solve the issue for openxr. -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ 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
