Fedora-Cloud-33-20210214.0 compose check report

[Fedora compose checker]

No missing expected images.

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

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

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

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

[389-devel] 389 DS nightly 2021-02-14 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2021/02/14/report-389-ds-base-2.0.3-20210214gita355b30b2.fc33.x86_64.html
___
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

[Test-Announce] Proposal to CANCEL: 2021-02-15 Fedora QA Meeting

[Adam Williamson]

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have
anything urgent this week. We did just branch and there are things we
could kick around, but Monday's a public holiday in Canada so I won't
be around to run a meeting.

If someone else wants to run a meeting, please do reply to this mail
with an agenda and go ahead and run the meeting on Monday.

Thanks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


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

Re: Fedora 34 Change: Enable btrfs transparent zstd compression by default (System-Wide Change proposal)

[Jeremy Linton]

Hi,

On 2/11/21 11:05 PM, Chris Murphy wrote:

On Thu, Feb 11, 2021 at 9:58 AM Jeremy Linton  wrote:


Hi,

On 1/1/21 8:59 PM, Chris Murphy wrote:



Anyway, compress=zstd:1 is a good default. Everyone benefits, and I'm
not even sure someone with a very fast NVMe drive will notice a slow
down because the compression/decompression is threaded.


I disagree that everyone benefits. Any read latency sensitive workload
will be slower due to the application latency being both the drive
latency plus the decompression latency. And as the kernel benchmarks
indicate very few systems are going to get anywhere near the performance
of even baseline NVMe drives when its comes to throughput.


It's possible some workloads on NVMe might have faster reads or writes
without compression.

https://github.com/facebook/zstd

btrfs compress=zstd:1 translates into zstd -1 right now; there are
some ideas to remap btrfs zstd:1 to one of the newer zstd --fast
options, but it's just an idea. And in any case the default for btrfs
and zstd will remain as 3 and -3 respectively, which is what
'compress=zstd' maps to, making it identical to 'compress=zstd:3'.

I have a laptop with NVMe and haven't come across such a workload so
far, but this is obviously not a scientific sample. I think you'd need
a process that's producing read/write rates that the storage can meet,
but that the compression algorithm limits. Btrfs is threaded, as is
the compression.

What's typical, is no change in performance and sometimes a small
small increase in performance. It essentially trades some CPU cycles
in exchange for less IO. That includes less time reading and writing,
but also less latency, meaning the gain on rotational media is
greater.


Worse, if the workload is very parallel, and at max CPU already
the compression overhead will only make that situation worse as well. (I
suspect you could test this just by building some packages that have
good parallelism during the build).


This is compiling the kernel on a 4/8-core CPU (circa 2011) using make
-j8, the kernel running is 5.11-rc7.

no compression

real55m32.769s
user369m32.823s
sys 35m59.948s

--

compress=zstd:1

real53m44.543s
user368m17.614s
sys 36m2.505s

That's a one time test, and it's a ~3% improvement. *shrug* We don't
really care too much these days about 1-3% differences when doing
encryption, so I think this is probably in that ballpark, even if it
turns out another compile is 3% slower. This is not a significantly
read or write centric workload, it's mostly CPU. So this 3% difference
may not even be related to the compression.


Did you drop caches/etc between runs? Because I git cloned mainline, 
copied the fedora kernel config from /boot and on a fairly recent laptop 
(12 threads) with a software encrypted NVMe. Dropped caches and did a 
time make against a compressed directory and an uncompressed one with 
both a semi constrained (4G) setup and 32G ram setup (compressed 
swapping disabled, because the machine has an encrypted swap for 
hibernation and crashdumps).


compressed:
real22m40.129s
user221m9.816s
sys 23m37.038s

uncompressed:
real21m53.366s
user221m56.714s
sys 23m39.988s

uncompressed 4G ram:
real28m48.964s
user288m47.569s
sys 30m43.957s

compressed 4G
real29m54.061s
user281m7.120s
sys 29m50.613s

and that is not an IO constrained workload its generally cpu 
constrained, and since the caches are warm due to the software 
encryption the decompress times should be much faster than machines that 
aren't cache stashing.


The machine above, can actually peg all 6 cores until it hits thermal 
limits simply doing cp's with btrfs/zstd compression, all the while 
losing about 800MB/sec of IO bandwidth over the raw disk. Turning an IO 
bound problem into a CPU bound one isn't ideal.


Compressed disks only work in the situation where the CPUs can 
compress/decompress faster than the disk, or the workload is managing to 
significantly reduce IO because the working set is streaming rather than 
random. Any workload which has a random read component to it and is 
tending closer to page sized read/writes is going to get hurt, and god 
help if its a RMW cycle. Similarly for parallelized compression, which 
is only scalable if the IO sizes are large enough that its worth the IPI 
overhead of bringing additional cores online and the resulting chunks 
are still large enough to be dealt with individually.








Plus, the write amplification comment isn't even universal as there
continue to be controllers where the flash translation layer is
compressing the data.


At least consumer SSDs tend to just do concurrent write dedup. File
system compression isn't limited to Btrfs, there's also F2FS
contributed by Samsung which implements compression these days as
well, although they commit to it at mkfs time, where as on Btrfs it's
a mount option. Mix and match compressed extents is routine on Btrfs
anyway, so there's no 

Re: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Tom Seewald]

 > The GPUs also have firmware blobs
Could you provide some links to mailing list posts or bug reports where AMD 
developers confirm that their GPU firmware requires 4k pages? I think having 
some definitive sources will make this situation more clear.

So far the only amdgpu bug report I could find that relates to 64k pages[1] is 
a regression, as the reporter states the driver works with the 5.4 kernel. If 
someone with a power9 machine is willing to bisect the issue I think that would 
greatly increase the odds of this bug being resolved.

[1] https://gitlab.freedesktop.org/drm/amd/-/issues/1446
___
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 1926184] bugzilla-5.0.6-11.fc34 FTBFS: Can't exec "make": No such file or directory at docs/makedocs.pl line 56.

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1926184

Fedora Release Engineering  changed:

   What|Removed |Added

  Flags||needinfo?(itamar@ispbrasil.
   ||com.br)



--- Comment #2 from Fedora Release Engineering  ---
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either
create
an update in bodhi, or close this bug without creating an update, if updating
is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this
Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-04-05).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html


-- 
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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1905190

Fedora Release Engineering  changed:

   What|Removed |Added

  Flags||needinfo?(c...@m.fsf.org)



--- Comment #5 from Fedora Release Engineering  ---
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either
create
an update in bodhi, or close this bug without creating an update, if updating
is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this
Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html


-- 
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: Unable to install using Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso

[Mamoru TASAKA]

Ian Laurie wrote on 2021/02/14 11:44:

Tried KDE.  Part way through the installation got the following error:

"The following error occurred while installing the payload.  This is a fatal
error and installation will be aborted.

DNF error:Error in POSTIN scriptlet in rpm package 
xorg-x11-fonts-ISO8859-1-100dpi"


https://bugzilla.redhat.com/show_bug.cgi?id=1925922
___
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: Unable to install using Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso

[Ian Laurie]

  
  
Tried KDE.  Part way through the installation got the following
error:

"The following error occurred while installing the payload.  This is
a fatal error and installation will be aborted.

DNF error:Error in POSTIN scriptlet in rpm package
xorg-x11-fonts-ISO8859-1-100dpi"

Ian

On 14/02/2021 1:29 pm, Ian Laurie
  wrote:


  
  It looks like the perf-5.11.0-0.rc7 dependency issue was caused by
  selecting the "C Development Tools and Libraries" option on the
  right side, so presumably MATE would have worked without that
  selected.
  
  --
  Ian
  
  On 14/02/2021 12:24 pm, Ian Laurie
wrote:
  
  

I tried testing out
  Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso with an
  Xfce and MATE install, both failed.
  
  I've attached screen shots of the error my software selection
  gave me for each attempt.
  
  --
  Ian
  
  
  
  ___
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



-- 
Ian Laurie
ilau...@bigpond.net.au
  
___
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: Unable to install using Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso

[Ian Laurie]

  
  
It looks like the perf-5.11.0-0.rc7 dependency issue was caused by
selecting the "C Development Tools and Libraries" option on the
right side, so presumably MATE would have worked without that
selected.

--
Ian

On 14/02/2021 12:24 pm, Ian Laurie
  wrote:


  
  I tried testing out
Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso with an
Xfce and MATE install, both failed.

I've attached screen shots of the error my software selection
gave me for each attempt.

--
Ian

  
___
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] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  58  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4a9fc09599   
openjpeg2-2.3.1-10.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-5ecfbfc6f6   
pngcheck-2.4.0-7.el7
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6eebad70ee   
SDL2-2.0.14-2.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-01679b76db   
chromium-88.0.4324.150-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-692420cee2   
snapd-2.49-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

bitlbee-facebook-1.2.2-1.el7

Details about builds:



 bitlbee-facebook-1.2.2-1.el7 (FEDORA-EPEL-2021-9ebc679fcb)
 Facebook protocol plugin for BitlBee

Update Information:

bitlbee-facebook 1.2.2 ==- Fix id assertion in
`fb_api_cb_publish_mst()`   - Increase `sync_interval` from 5 to 1440 ("The
action attempted has been deemed abusive or is otherwise disallowed")   - Bump
the `FB_ORCA_AGENT` version once again

ChangeLog:

* Sat Feb 13 2021 Robert Scheck  1.2.2-1
- Upgrade to 1.2.2 (#1928417)
* Tue Jan 26 2021 Fedora Release Engineering  - 
1.2.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild

References:

  [ 1 ] Bug #1928417 - bitlbee-facebook-1.2.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1928417


___
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

[EPEL-devel] Fedora EPEL 8 updates-testing report

[updates]

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-eca913b42e   
pngcheck-2.4.0-7.el8
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-5e4b80b9d8   
zeromq-4.3.4-2.el8
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-69b5865b58   
privoxy-3.0.31-1.el8
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1917130359   
czmq-4.2.1-2.el8
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-87e6bb3010   
chromium-88.0.4324.150-1.el8
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-2561abf859   
snapd-2.49-1.el8


The following builds have been pushed to Fedora EPEL 8 updates-testing

bitlbee-facebook-1.2.2-1.el8

Details about builds:



 bitlbee-facebook-1.2.2-1.el8 (FEDORA-EPEL-2021-dd24ee1f4b)
 Facebook protocol plugin for BitlBee

Update Information:

bitlbee-facebook 1.2.2 ==- Fix id assertion in
`fb_api_cb_publish_mst()`   - Increase `sync_interval` from 5 to 1440 ("The
action attempted has been deemed abusive or is otherwise disallowed")   - Bump
the `FB_ORCA_AGENT` version once again

ChangeLog:

* Sat Feb 13 2021 Robert Scheck  1.2.2-1
- Upgrade to 1.2.2 (#1928417)
* Tue Jan 26 2021 Fedora Release Engineering  - 
1.2.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild

References:

  [ 1 ] Bug #1928417 - bitlbee-facebook-1.2.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1928417


___
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 1925321] perl-File-Path-Tiny-1.0 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1925321

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-File-Path-Tiny-1.0-1.f |perl-File-Path-Tiny-1.0-1.f
   |c34 |c34
   |perl-File-Path-Tiny-1.0-1.f |perl-File-Path-Tiny-1.0-1.f
   |c33 |c33
   ||perl-File-Path-Tiny-1.0-1.f
   ||c32



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-a1af4846c4 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

Unable to install using Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso

[Ian Laurie]

  
  
I tried testing out
  Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso with an Xfce
  and MATE install, both failed.
  
  I've attached screen shots of the error my software selection gave
  me for each attempt.
  
  --
  Ian

  

___
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 1925321] perl-File-Path-Tiny-1.0 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1925321

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-File-Path-Tiny-1.0-1.f |perl-File-Path-Tiny-1.0-1.f
   |c34 |c34
   ||perl-File-Path-Tiny-1.0-1.f
   ||c33
 Resolution|--- |ERRATA
Last Closed||2021-02-14 01:23:01



--- Comment #4 from Fedora Update System  ---
FEDORA-2021-6a0e0ff598 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: ELN SIG Launch

[Matthew Miller]

On Sat, Feb 13, 2021 at 10:42:51PM +0100, Kevin Kofler via devel wrote:
> Why would I bother signing up for such a license if I will be able (very 
> likely before the CentOS 8 EOL) to just download Rocky Linux the same way I 
> can download Fedora or Debian?

That's fine too -- it *is* open source / free software, and those things
also couldn't exist without our efforts here in Fedora and Red Hat's efforts
in RHEL.

-- 
Matthew Miller

Fedora Project Leader
___
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: ELN SIG Launch

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:
> And ELN leeching Fedora hardware infrastructure that is actually paid by
> Red Hat to begin with is one thing, but Stephen Gallagher's announcement
> goes as far as attempting to leech unpaid community manpower.

PS: But even if this attempt at poaching community volunteers for free 
fails, ELN is still leeching community manpower by consuming the time of 
people who have NOT volunteered, e.g., by spamming them with failed build 
notifications:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AVFI3WEXYIEK2WXEHERBABDN6ZJU3MPJ/

(In addition, this behavior is also wasting hardware resources for lots of 
failed automated Koji builds.)

Kevin Kofler
___
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: ELN SIG Launch

[Miro Hrončok]

On 13. 02. 21 23:00, Kevin Kofler via devel wrote:

And ELN leeching Fedora hardware infrastructure that is actually paid by Red
Hat to begin with is one thing, but Stephen Gallagher's announcement goes as
far as attempting to leech unpaid community manpower.


That claim is simply not true. Stephen's announcement simply clarifies that it 
possible for interested community members to join. If they are not interested, 
nobody is leeching their manpower.


--
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

Re: Copr in 2020 and outlook for 2021

[Ken Dreyer]

On Mon, Jan 4, 2021 at 9:52 AM Miroslav Suchý  wrote:
>  * Contribute to fedpkg/koji to have machine-readable output.

There is a "--json" argument to "koji call", and that produces
machine-readable output for individual Koji RPCs.

It would be really nice if rpkg had something similar, or even an
easier-to-extend Python API. There was an attempt a while back, with
https://pagure.io/rpkg2 .

- Ken
___
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: ELN SIG Launch

[Kevin Kofler via devel]

Stephen John Smoogen wrote:
> In written English the word 'or' is not exclusive and 'yes' is a synonym
> for 'TRUE'.  Basically the question is Stephen trying a CS pun with that
> of
> 
> Is this a Fedora project || a Red Hat project using Fedora resources.
> 
> It would evaluate as TRUE/yes in either case.

You don't have to explain boolean algebra to me, I understand that well. It 
is still weaseling out of the real question based on technicalities, just as 
Stephen Gallagher's announcement did.

The thing is, while in boolean algebra, "or" is inclusive by default, and in 
some contexts that is also the case in English, an "or" question of the form 
"Is X or Y?" is clearly meant to imply that "X xor Y" is true and to ask 
which of the 2 cases "X is true and Y is false" xor "X is false and Y is 
true" is true. Any other interpretation is deliberately misunderstanding the 
question to avoid answering it.

> I will break it out further
> 
> Is this a Fedora project? 'yes'
> Is this a Red Hat project using resources Fedora would normally use? 'yes'
> 
> I can understand the want for making this an exclusive or, which I believe
> would make the answer 'No/False' because the two parts are 'true'.

The way I read this question:
* "Is this a Fedora project?" = "Is this a project by and for the Fedora
  community?"
* "Is this a Red Hat project using Fedora resources?" = "Is this a project
  by Red Hat, abusing its control of Fedora resources to leech those
  resources for its own purposes, diverting them to a non-Fedora product?"

IMHO, those two options are clearly mutually exclusive. And given that the 
output is useful exclusively for RHEL, I also think it is obvious which 
option is the case for ELN (the latter one).

And ELN leeching Fedora hardware infrastructure that is actually paid by Red 
Hat to begin with is one thing, but Stephen Gallagher's announcement goes as 
far as attempting to leech unpaid community manpower.

>> And why would I want to do Red Hat's / IBM's work for free?
>>
>> Contributing to Fedora provides value to me because I use Fedora myself.
>> In contrast, what would I gain from contributing to ELN?
> 
> I expect the answer is that if you want to help it will help make RHEL a
> better product and that will increase resources available to Fedora. I
> don't think that is an answer you want, but it is what I expect the answer
> is.

To be honest, I did not expect a useful answer to those rhetorical 
questions.

Kevin Kofler
___
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: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Stephen John Smoogen]

On Sat, 13 Feb 2021 at 14:06, Alex Perez  wrote:

> Kevin,
>
> On 2/13/2021 9:51:48 AM, Stephen John Smoogen  wrote:
>
>
> On Sat, 13 Feb 2021 at 05:15, Daniel Pocock  wrote:
>
>>
>>
>> On 13/02/2021 09:11, Tomasz Torcz wrote:
>> > Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
>> >>
>> >>
>> >> On 12/02/2021 21:19, Justin Forbes wrote:
>> >>> On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton 
>> wrote:
>> 
>>  https://fedoraproject.org/wiki/Changes/Power4kPageSize
>> 
>>  == Summary ==
>> 
>>  On ppc64le, the kernel is currently compiled for 64k page size.
>> 
>>  This change proposes using the more common 4k page size.
>> 
>>  Some things, like the AMD Radeon GPU drivers, firmware or related
>>  code, appear to be completely non-functional on the 64k page size.
>>  Insufficient upstream developers are testing such issues on this
>>  architecture.
>> >>>
>> >>> Just as there are many things that expect the 64K page size.  I am not
>> >>> doing this.
>> >>>
>> >>> Justin
>> >>
>> >> Can you please identify some of the things that expect 64k?
>> >>
>> >> If the GPU drivers don't work that makes it a complete non-starter for
>> >> many workstation users, or they have to compile their own kernels or
>> >> obtain custom kernels from another user.
>> >
>> >   Or just fix the GPU drivers. They're open source, after all.
>>
>> The GPUs also have firmware blobs
>>
>>
> OK I think we need to back up a whole bunch here and talk directly about
> what is wanted and going on. I am going to try an outline what I have
> picked up from months of this back and forth:
>
> 1. There is some sort of PowerPC workstation which is going 'to market'
> somewhere soon.
>
> *Alex Perez:*
> We, it's actually been on the market for a few years. There are
> several variants. I've had my Talos II Lite board since January of 2019.
>
>
> 2. It will have high powered video cards of a PC style so will be using
> the same 'firmware' that would be in x86_64.
>
> *Alex Perez:*
> Not will, does. Right now.
>
>
> 3. Those drivers expect x86_64 4k buffer sizes.
>
> *Alex Perez:*
> Some do, some don't.
>
>
> 4. Daniel would like to have Fedora Linux as an option or the operating
> system on it.
> 5. They have been trying to work out through various tickets how to make
> this happen.
>
> Please correct the items above if needed. The questions that I don't see
> having been asked is:
> 1. Is Fedora interested in being offered on this hardware?
>
> *Alex Perez:*
> Err, people are already running Fedora on this exact hardware. You seem to
> think this is not something that's happening. You're mistaken.
>


>From what had been said, I thought this was new systems which were not the
ones already on the market. Thank you both for the corrections.

-- 
Stephen J Smoogen.
___
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 1928420] New: perl-PDL-2.026 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928420

Bug ID: 1928420
   Summary: perl-PDL-2.026 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-PDL
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: caillon+fedoraproj...@gmail.com,
jakub.jedel...@gmail.com, jples...@redhat.com,
ka...@ucw.cz, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com, tjczep...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.026
Current version/release in rawhide: 2.25.0-2.fc34
URL: http://search.cpan.org/dist/PDL/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/3205/


-- 
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: ELN SIG Launch

[Kevin Kofler via devel]

Gary Buhrmaster wrote:
> Perhaps you missed the announcement that "small"
> production environments (up to 16? servers) are now
> "free" under the RH developer licensees.  That may
> not be a lot of servers for the hyperscallers, but
> for smaller deployments it may cover you.  Should
> I have chosen to use EL8 rather than Fedora for
> my (smallish) environments 16 servers would
> more than cover my needs.

This is a usage restriction (and indirectly also a field-of-use restriction, 
not to mention that the term "developer licensee" implies a field-of-use 
restriction by itself), which inherently contradicts the Free Software 
licenses of the packages in the distribution. I am not interested in running 
a commercial distribution imposing such non-Free restrictions, even if Red 
Hat is now jumping on the "free (as in beer) developer licenses to get 
developers hooked and hopefully more software developed for the platform" 
bandwagon pioneered by proprietary software companies.

Why would I bother signing up for such a license if I will be able (very 
likely before the CentOS 8 EOL) to just download Rocky Linux the same way I 
can download Fedora or Debian?

Kevin Kofler
___
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: Orphaned my Ruby packages (Jekyll + dependencies)

[FreedomBen via devel]

Sad day indeed, but the situation is indeed a tough one.  I also switched to 
bundler for similar reasons and pain for my jekyll sites.

Thanks so much for your service Fabio!

I don't have time/bandwidth to take over completely, but I could offer some 
assistance/backup if somebody else takes primary on them.

Ben



Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, February 13, 2021 12:29 PM, Fabio Valentini  
wrote:

> Hi everybody,
>
> With a heavy heart, I have orphaned all my Ruby packages today.
>
> -   rubygem-jekyll
> -   rubygem-jekyll-asciidoc (official, optional AsciiDoc support)
> -   rubygem-jekyll-feed (dep of the default theme)
> -   rubygem-jekyll-sass-converter (jekyll dep)
> -   rubygem-jekyll-seo-tag (dep of the default theme)
> -   rubygem-jekyll-toc (unofficial table of contents plugin)
> -   rubygem-jekyll-watch (jekyll dep)
> -   rubygem-kramdown-parser-gfm (kramdown support for GitHub-flavored 
> markdown)
> -   rubygem-kramdown-syntax-coderay (coderay syntax highlighting support)
> -   rubygem-liquid (jekyll dep, templating engine)
> -   rubygem-minima (jekyll default theme)
> -   rubygem-minitest-profile (test dependency for some of the other gems)
> -   rubygem-rouge (jekyll dep, default syntax highlighter, "compatible"
> with pygments)
>
> -   rubygem-ruby-progressbar
> -   rubygem-sassc (wrapper for C libsass, "official" successor of the
> pure-ruby sass gem)
>
> -   rubygem-stringex
> -   rubygem-tomlrb (optional jekyll dep, for TOML config file support in
> addition to YAML)
>
> I originally took them or packaged them because I used Jekyll, but for
> some time now, I have used bundler to manage the gems for my Jekyll
> pages (because not all gems I needed were available on Fedora anyway,
> and mixing and matching doesn't work well).
>
> There are some known issues with the packages:
>
> -   Some of them are failing to build on Fedora 34 due to changes in
> Ruby 3.0 (jekyll, jekyll-feed, liquid, stringex, tomlrb).
>
> -   Jekyll test suite is failing due to changes in kramdown 2.2.0.
> -   Two of them are outdated (jekyll, tomlrb). jekyll 4.2.0 requires
> tomlrb 2.0, but jekyll cannot be updated to 4.2.0 unless
> terminal-table is updated to 2.0).
>
> Jekyll and liquid have some non-upstreamable downstream patches which
> I used to maintain here: https://pagure.io/group/jekyll-fedora
>
> I have pushed the working patches I have for jekyll 4.2.0 there, and
> submitted two final PRs for tomlrb and jekyll with the changes I had
> prepared locally:
>
> -   https://src.fedoraproject.org/rpms/rubygem-tomlrb/pull-request/2
> -   https://src.fedoraproject.org/rpms/rubygem-jekyll/pull-request/6
>
> The PRs are blocked by other missing updates for now.
>
> Big thanks to everybody who helped me with maintaining my Ruby
> packages over the years.
> Fabio
>
>
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

___
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

Orphaned my Ruby packages (Jekyll + dependencies)

[Fabio Valentini]

Hi everybody,

With a heavy heart, I have orphaned all my Ruby packages today.

- rubygem-jekyll
- rubygem-jekyll-asciidoc (official, optional AsciiDoc support)
- rubygem-jekyll-feed (dep of the default theme)
- rubygem-jekyll-sass-converter (jekyll dep)
- rubygem-jekyll-seo-tag (dep of the default theme)
- rubygem-jekyll-toc (unofficial table of contents plugin)
- rubygem-jekyll-watch (jekyll dep)
- rubygem-kramdown-parser-gfm (kramdown support for GitHub-flavored markdown)
- rubygem-kramdown-syntax-coderay (coderay syntax highlighting support)
- rubygem-liquid (jekyll dep, templating engine)
- rubygem-minima (jekyll default theme)
- rubygem-minitest-profile (test dependency for some of the other gems)
- rubygem-rouge (jekyll dep, default syntax highlighter, "compatible"
with pygments)
- rubygem-ruby-progressbar
- rubygem-sassc (wrapper for C libsass, "official" successor of the
pure-ruby sass gem)
- rubygem-stringex
- rubygem-tomlrb (optional jekyll dep, for TOML config file support in
addition to YAML)

I originally took them or packaged them because I used Jekyll, but for
some time now, I have used bundler to manage the gems for my Jekyll
pages (because not all gems I needed were available on Fedora anyway,
and mixing and matching doesn't work well).

There are some known issues with the packages:

- Some of them are failing to build on Fedora 34 due to changes in
Ruby 3.0 (jekyll, jekyll-feed, liquid, stringex, tomlrb).
- Jekyll test suite is failing due to changes in kramdown 2.2.0.
- Two of them are outdated (jekyll, tomlrb). jekyll 4.2.0 requires
tomlrb 2.0, but jekyll cannot be updated to 4.2.0 unless
terminal-table is updated to 2.0).

Jekyll and liquid have some non-upstreamable downstream patches which
I used to maintain here: https://pagure.io/group/jekyll-fedora

I have pushed the working patches I have for jekyll 4.2.0 there, and
submitted two final PRs for tomlrb and jekyll with the changes I had
prepared locally:

- https://src.fedoraproject.org/rpms/rubygem-tomlrb/pull-request/2
- https://src.fedoraproject.org/rpms/rubygem-jekyll/pull-request/6

The PRs are blocked by other missing updates for now.

Big thanks to everybody who helped me with maintaining my Ruby
packages over the years.
Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1928408] perl-Log-Agent-1.004 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928408



--- Comment #1 from Upstream Release Monitoring 
 ---
Unable to resolve the hostname for one of the package's Source URLs


-- 
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 1928408] New: perl-Log-Agent-1.004 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928408

Bug ID: 1928408
   Summary: perl-Log-Agent-1.004 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Log-Agent
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.004
Current version/release in rawhide: 1.003-11.fc34
URL: http://search.cpan.org/dist/Log-Agent/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/8292/


-- 
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: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Alex Perez]

Kevin,

On 2/13/2021 9:51:48 AM, Stephen John Smoogen  wrote:


On Sat, 13 Feb 2021 at 05:15, Daniel Pocock mailto:dan...@pocock.pro]> wrote:



On 13/02/2021 09:11, Tomasz Torcz wrote:
> Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
>>
>>
>> On 12/02/2021 21:19, Justin Forbes wrote:
>>> On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton >> [mailto:bcot...@redhat.com]> wrote:

 https://fedoraproject.org/wiki/Changes/Power4kPageSize 
 [https://fedoraproject.org/wiki/Changes/Power4kPageSize]

 == Summary ==

 On ppc64le, the kernel is currently compiled for 64k page size.

 This change proposes using the more common 4k page size.

 Some things, like the AMD Radeon GPU drivers, firmware or related
 code, appear to be completely non-functional on the 64k page size.
 Insufficient upstream developers are testing such issues on this
 architecture.
>>>
>>> Just as there are many things that expect the 64K page size.  I am not
>>> doing this.
>>>
>>> Justin
>>
>> Can you please identify some of the things that expect 64k?
>>
>> If the GPU drivers don't work that makes it a complete non-starter for
>> many workstation users, or they have to compile their own kernels or
>> obtain custom kernels from another user.
>
>   Or just fix the GPU drivers. They're open source, after all.

The GPUs also have firmware blobs



OK I think we need to back up a whole bunch here and talk directly about what 
is wanted and going on. I am going to try an outline what I have picked up from 
months of this back and forth:

1. There is some sort of PowerPC workstation which is going 'to market' 
somewhere soon.
Alex Perez:
We, it's actually been on the market for a few years. There are several 
variants. I've had my Talos II Lite board since January of 2019.

2. It will have high powered video cards of a PC style so will be using the 
same 'firmware' that would be in x86_64.
Alex Perez: 
Not will, does. Right now.



3. Those drivers expect x86_64 4k buffer sizes.
Alex Perez: 
Some do, some don't.



4. Daniel would like to have Fedora Linux as an option or the operating system 
on it.
5. They have been trying to work out through various tickets how to make this 
happen.

Please correct the items above if needed. The questions that I don't see having 
been asked is:
1. Is Fedora interested in being offered on this hardware?
Alex Perez: 
Err, people are already running Fedora on this exact hardware. You seem to 
think this is not something that's happening. You're mistaken.

___
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 1928404] perl-Clipboard-0.27 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928404



--- Comment #1 from Upstream Release Monitoring 
 ---
Unable to resolve the hostname for one of the package's Source URLs


-- 
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 1928404] New: perl-Clipboard-0.27 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928404

Bug ID: 1928404
   Summary: perl-Clipboard-0.27 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Clipboard
  Keywords: FutureFeature, Triaged
  Assignee: mkre...@gmail.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: c...@alum.wpi.edu, iarn...@gmail.com,
mkre...@gmail.com, perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.27
Current version/release in rawhide: 0.26-4.fc34
URL: http://search.cpan.org/dist/Clipboard/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/14091/


-- 
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: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Daniel Pocock]

On 13/02/2021 18:51, Stephen John Smoogen wrote:
> 
> 
> On Sat, 13 Feb 2021 at 05:15, Daniel Pocock  > wrote:
> 
> 
> 
> On 13/02/2021 09:11, Tomasz Torcz wrote:
> > Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
> >>
> >>
> >> On 12/02/2021 21:19, Justin Forbes wrote:
> >>> On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton  > wrote:
> 
>  https://fedoraproject.org/wiki/Changes/Power4kPageSize
> 
>  == Summary ==
> 
>  On ppc64le, the kernel is currently compiled for 64k page size.
> 
>  This change proposes using the more common 4k page size.
> 
>  Some things, like the AMD Radeon GPU drivers, firmware or related
>  code, appear to be completely non-functional on the 64k page size.
>  Insufficient upstream developers are testing such issues on this
>  architecture.
> >>>
> >>> Just as there are many things that expect the 64K page size.  I
> am not
> >>> doing this.
> >>>
> >>> Justin
> >>
> >> Can you please identify some of the things that expect 64k?
> >>
> >> If the GPU drivers don't work that makes it a complete
> non-starter for
> >> many workstation users, or they have to compile their own kernels or
> >> obtain custom kernels from another user.
> >
> >   Or just fix the GPU drivers. They're open source, after all.
> 
> The GPUs also have firmware blobs
> 
> 
> OK I think we need to back up a whole bunch here and talk directly about
> what is wanted and going on. I am going to try an outline what I have
> picked up from months of this back and forth:
> 
> 1. There is some sort of PowerPC workstation which is going 'to market'
> somewhere soon.

The workstations and motherboards are already available from Raptor:
https://www.raptorcs.com/

Vikings is about to start shipping a European version:
https://store.vikings.net/openpower

Many people already bought the Blackbird kits in the first production run.

> 2. It will have high powered video cards of a PC style so will be using
> the same 'firmware' that would be in x86_64.
> 3. Those drivers expect x86_64 4k buffer sizes.

This is a moving target, new GPUs arrive each year.  It is like
whack-a-mole, by the time people have it fixed with one model, the next
model is available.

> 4. Daniel would like to have Fedora Linux as an option or the operating
> system on it.

I've been compiling kernels since the early days so I can work around
this in my personal situation.  I would like other Fedora users to have
the best possible experience and as easily as possible.

I'll let other people answer your questions below...

> 5. They have been trying to work out through various tickets how to make
> this happen.
> 
> Please correct the items above if needed. The questions that I don't see
> having been asked is:
> 1. Is Fedora interested in being offered on this hardware?
> 2. If it is, what changes is it willing to make it happen. 
> 3. Are there other people interested in helping make this happen outside
> of Daniel
> 
> If those have been asked and answered, I apologize for not finding
> things. However this seems to be having someone throw 'softballs' at an
> iceberg in motion with the hopes that it will change course. It would be
> better if we answered somewhere on those 3 questions:  
> 'Yes, and here is someone who can help you' or 'No we aren't interested
> in this'
> 'Yes but we need to work out ways to deal with our expected delvirables
> and here are the people who can help out' or 'No we can not make these
> changes because it affects our expected deliverables'
> 'Yes we are all buying these XYZ systems' or 'No most of us want this to
> work on our IBM Power 9 boxes with some other workload'.
> 
> 
> 
>  
> 
> 
> -- 
> Stephen J Smoogen.
> 
> 
> ___
> 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

FedoraRespin-33-updates-20210212.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 7/37 (x86_64)

ID: 776919  Test: x86_64 Workstation-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/776919
ID: 776921  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/776921
ID: 776922  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/776922
ID: 776936  Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/776936
ID: 776940  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/776940
ID: 776942  Test: x86_64 KDE-live-iso release_identification
URL: https://openqa.fedoraproject.org/tests/776942
ID: 776943  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/776943

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

ID: 776915  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/776915

Passed openQA tests: 29/37 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Stephen John Smoogen]

On Sat, 13 Feb 2021 at 05:15, Daniel Pocock  wrote:

>
>
> On 13/02/2021 09:11, Tomasz Torcz wrote:
> > Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
> >>
> >>
> >> On 12/02/2021 21:19, Justin Forbes wrote:
> >>> On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton 
> wrote:
> 
>  https://fedoraproject.org/wiki/Changes/Power4kPageSize
> 
>  == Summary ==
> 
>  On ppc64le, the kernel is currently compiled for 64k page size.
> 
>  This change proposes using the more common 4k page size.
> 
>  Some things, like the AMD Radeon GPU drivers, firmware or related
>  code, appear to be completely non-functional on the 64k page size.
>  Insufficient upstream developers are testing such issues on this
>  architecture.
> >>>
> >>> Just as there are many things that expect the 64K page size.  I am not
> >>> doing this.
> >>>
> >>> Justin
> >>
> >> Can you please identify some of the things that expect 64k?
> >>
> >> If the GPU drivers don't work that makes it a complete non-starter for
> >> many workstation users, or they have to compile their own kernels or
> >> obtain custom kernels from another user.
> >
> >   Or just fix the GPU drivers. They're open source, after all.
>
> The GPUs also have firmware blobs
>
>
OK I think we need to back up a whole bunch here and talk directly about
what is wanted and going on. I am going to try an outline what I have
picked up from months of this back and forth:

1. There is some sort of PowerPC workstation which is going 'to market'
somewhere soon.
2. It will have high powered video cards of a PC style so will be using the
same 'firmware' that would be in x86_64.
3. Those drivers expect x86_64 4k buffer sizes.
4. Daniel would like to have Fedora Linux as an option or the operating
system on it.
5. They have been trying to work out through various tickets how to make
this happen.

Please correct the items above if needed. The questions that I don't see
having been asked is:
1. Is Fedora interested in being offered on this hardware?
2. If it is, what changes is it willing to make it happen.
3. Are there other people interested in helping make this happen outside of
Daniel

If those have been asked and answered, I apologize for not finding things.
However this seems to be having someone throw 'softballs' at an iceberg in
motion with the hopes that it will change course. It would be better if we
answered somewhere on those 3 questions:
'Yes, and here is someone who can help you' or 'No we aren't interested in
this'
'Yes but we need to work out ways to deal with our expected delvirables and
here are the people who can help out' or 'No we can not make these changes
because it affects our expected deliverables'
'Yes we are all buying these XYZ systems' or 'No most of us want this to
work on our IBM Power 9 boxes with some other workload'.






-- 
Stephen J Smoogen.
___
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: ELN SIG Launch

[Stephen John Smoogen]

On Fri, 12 Feb 2021 at 19:59, Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:

> Stephen Gallagher wrote:
> > Is this a Fedora project or a Red Hat project using Fedora resources?
> >
> > Yes.
>
> "Yes" is not a valid answer to that "or" question.
>
>

In written English the word 'or' is not exclusive and 'yes' is a synonym
for 'TRUE'.  Basically the question is Stephen trying a CS pun with that of

Is this a Fedora project || a Red Hat project using Fedora resources.

It would evaluate as TRUE/yes in either case. I will break it out further

Is this a Fedora project? 'yes'
Is this a Red Hat project using resources Fedora would normally use? 'yes'

I can understand the want for making this an exclusive or, which I believe
would make the answer 'No/False' because the two parts are 'true'.


> Do I need to be employed by Red Hat to be a member of the ELN SIG?
> >
> > No, anyone with an interest in helping will be welcomed enthusiastically!
>
> And why would I want to do Red Hat's / IBM's work for free?
>
> Contributing to Fedora provides value to me because I use Fedora myself.
> In
> contrast, what would I gain from contributing to ELN?
>
>

I expect the answer is that if you want to help it will help make RHEL a
better product and that will increase resources available to Fedora. I
don't think that is an answer you want, but it is what I expect the answer
is. In the end, Red Hat provides the majority of the resources that are
used by Fedora to build its packages. It pays for the employment of a lot
of people who are also working on Fedora and it owns the trademarks for
Fedora. It has to ask the same question you have above of why should it put
these into Fedora versus something else. The answer is that it gets a place
to put in SIGs and deliverables which help it continue to function. (Again
maybe not an answer we like, but an answer).



-- 
Stephen J Smoogen.
___
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: Fedora's GPG key in DNS(SEC)

[Matthew Miller]

On Sat, Feb 13, 2021 at 05:57:07PM +0100, Miroslav Suchý wrote:
> Does somebody knows where is the source for:
>   https://getfedora.org/security/
> ? I want to submit PR with information that these keys are in DNS as well, 
> but I have no idea where to go.

https://pagure.io/fedora-web/websites/blob/master/f/sites/getfedora.org/site/security

Docs for the framework: https://docs.fedoraproject.org/en-US/websites/

-- 
Matthew Miller

Fedora Project Leader
___
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: Fedora's GPG key in DNS(SEC)

[Miroslav Suchý]

Dne 12. 02. 21 v 20:22 Miroslav Suchý napsal(a):
All Fedora's GPG key - starting with Fedora 27 - are now stored in fedoraproject.org DNS record and can be verified 
using DNSSEC.


Why? How it can be used? That is long story and you can read about it in my 
blog entry:
    
http://miroslav.suchy.cz/blog/archives/2021/02/11/verify_package_gpg_signature_using_dnssec/index.html

Few last minutes notes here:
  - there are still some gotchas which should be fixed. But enough code is already in production - you can play with it 
now. Relevant issues are linked in the blog post.
  - the DNF team is migrating their code to libdnf, I do not have any guarantee when this piece of code will be 
migrating - so we are far from enabling this by default.


Comments are welcomed.


Does somebody knows where is the source for:
  https://getfedora.org/security/
? I want to submit PR with information that these keys are in DNS as well, but 
I have no idea where to go.

--
Miroslav Suchy, RHCA
Red Hat, Associate Manager, Community Packaging Tools, #brno, #fedora-buildsys
___
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 1928387] perl-ExtUtils-CBuilder-0.280236 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928387



--- Comment #1 from Upstream Release Monitoring 
 ---
Unable to resolve the hostname for one of the package's Source URLs


-- 
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 1928387] New: perl-ExtUtils-CBuilder-0.280236 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928387

Bug ID: 1928387
   Summary: perl-ExtUtils-CBuilder-0.280236 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-ExtUtils-CBuilder
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, spo...@gmail.com,
st...@silug.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.280236
Current version/release in rawhide: 0.280235-2.fc34
URL: http://search.cpan.org/dist/ExtUtils-CBuilder/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/6563/


-- 
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 1928344] perl-Business-ISBN-Data-20210112.005 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928344

Paul Howarth  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Business-ISBN-Data-202
   ||10112.005-1.fc34
   ||perl-Business-ISBN-Data-202
   ||10112.005-1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-02-13 13:45:23



--- Comment #1 from Paul Howarth  ---
F34:
https://koji.fedoraproject.org/koji/taskinfo?taskID=61870085

Rawhide:
https://koji.fedoraproject.org/koji/taskinfo?taskID=61869923


-- 
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 1928344] perl-Business-ISBN-Data-20210112.005 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1928344

Paul Howarth  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|jples...@redhat.com |p...@city-fan.org
   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

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

[Fedora compose checker]

Missing expected images:

Minimal raw-xz armhfp
Xfce raw-xz armhfp

Failed openQA tests: 36/183 (x86_64), 27/124 (aarch64)

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

ID: 776560  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/776560
ID: 776564  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/776564
ID: 776571  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/776571
ID: 776578  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/776578
ID: 776580  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/776580
ID: 776583  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/776583
ID: 776585  Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/776585
ID: 776597  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/776597
ID: 776598  Test: x86_64 Server-dvd-iso server_cockpit_basic
URL: https://openqa.fedoraproject.org/tests/776598
ID: 776621  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/776621
ID: 776630  Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/776630
ID: 776631  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/776631
ID: 776632  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/776632
ID: 776647  Test: x86_64 Silverblue-dvd_ostree-iso desktop_background
URL: https://openqa.fedoraproject.org/tests/776647
ID: 776675  Test: aarch64 Server-dvd-iso 
server_role_deploy_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/776675
ID: 776677  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/776677
ID: 776691  Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi
URL: https://openqa.fedoraproject.org/tests/776691
ID: 776693  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/776693
ID: 776694  Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi
URL: https://openqa.fedoraproject.org/tests/776694
ID: 776705  Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi
URL: https://openqa.fedoraproject.org/tests/776705
ID: 776707  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/776707
ID: 776717  Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing@uefi
URL: https://openqa.fedoraproject.org/tests/776717
ID: 776752  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/776752
ID: 776753  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/776753
ID: 776760  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/776760
ID: 776761  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/776761
ID: 776764  Test: x86_64 universal upgrade_2_minimal_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/776764
ID: 776769  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/776769
ID: 776770  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/776770
ID: 776788  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/776788
ID: 776813  Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/776813
ID: 776814  Test: aarch64 universal install_mirrorlist_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/776814
ID: 776835  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/776835
ID: 776845  Test: aarch64 universal install_european_language@uefi
URL: https://openqa.fedoraproject.org/tests/776845
ID: 776847  Test: aarch64 universal install_with_swap@uefi
URL: https://openqa.fedoraproject.org/tests/776847
ID: 776861  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/776861
ID: 776877  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/776877
ID: 776878  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/776878
ID: 776886  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/776886

Old failures 

Fedora 34 compose report: 20210213.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-34-20210212.n.0
NEW: Fedora-34-20210213.n.0

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

Size of added packages:  11.61 MiB
Size of dropped packages:0 B
Size of upgraded packages:   7.09 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   1.40 GiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: dosbox-staging-0.76.0-2.fc34
Summary: DOS/x86 emulator focusing on ease of use
RPMs:dosbox-staging
Size:6.78 MiB

Package: python-pynn-0.9.6-1.fc34
Summary: A package for simulator-independent specification of neuronal network 
models
RPMs:python-pynn-devel python-pynn-doc python3-pynn
Size:4.83 MiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  389-ds-base-2.0.3-1.fc34
Old package:  389-ds-base-2.0.2-1.fc34.1
Summary:  389 Directory Server (base)
RPMs: 389-ds-base 389-ds-base-devel 389-ds-base-libs 389-ds-base-snmp 
cockpit-389-ds python3-lib389
Size: 26.91 MiB
Size change:  2.36 MiB
Changelog:
  * Fri Feb 12 2021 Mark Reynolds  - 2.0.3-1
  - Bump version to 2.0.3
  - Issue 4619 - remove pytest requirement from lib389
  - Issue 4615 - log message when psearch first exceeds max threads per conn
  - Issue 4469 - Backend redesing phase 3a - implement dbimpl API and use it in 
back-ldbm (#4618)
  - Issue 4324 - Some architectures the cache line size file does not exist
  - Issue 4593 - RFE - Print help when nsSSLPersonalitySSL is not found (#4614)
  - Issue 4469 - Backend redesign phase 3a - bdb dependency removal from 
back-ldbm
  - PR 4564 - Update dscontainer
  - Issue 4149 - UI - port TreeView and opther components to PF4
  - Issue 4577 - Add GitHub actions
  - Issue 4591 - RFE - improve openldap_to_ds help and features (#4607)
  - issue 4612 - Fix pytest fourwaymmr_test for non root user (#4613)
  - Issue 4609 - CVE - info disclosure when authenticating
  - Issue 4348 - Add tests for dsidm
  - Issue 4571 - Stale libdb-utils dependency
  - Issue 4600 - performance modify rate: reduce lock contention on the object 
extension factory (#4601)
  - Issue 4577 - Add GitHub actions
  - Issue 4588 - BUG - unable to compile without xcrypt (#4589)
  - Issue 4579 - libasan detects heap-use-after-free in URP test (#4584)
  - Issue 4581 - A failed re-indexing leaves the database in broken state 
(#4582)
  - Issue 4348 - Add tests for dsidm
  - Issue 4577 - Add GitHub actions
  - Issue 4563 - Failure on s390x: 'Fails to split RDN "o=pki-tomcat-CA" into 
components' (#4573)
  - Issue 4093 - fix compiler warnings and update doxygen
  - Issue 4575 - Update test docstrings metadata
  - Issue 4526 - sync_repl: when completing an operation in the pending list, 
it can select the wrong operation (#4553)
  - Issue 4324 - Performance search rate: change entry cache monitor to 
recursive pthread mutex (#4569)
  - Issue 4513 - Add DS version check to SSL version test (#4570)
  - Issue 5442 - Search results are different between RHDS10 and RHDS11
  - Issue 4396 - Minor memory leak in backend (#4558)
  - Issue 4513 - Fix replication CI test failures (#4557)
  - Issue 4513 - Fix replication CI test failures (#4557)
  - Issue 4153 - Added a CI test (#4556)
  - Issue 4506 - BUG - fix oob alloc for fds (#4555)
  - Issue 4548 - CLI - dsconf needs better root DN access control plugin 
validation
  - Issue 4506 - Temporary fix for io issues (#4516)
  - Issue 4535 - lib389 - Fix log function in backends.py
  - Issue 4534 - libasan read buffer overflow in filtercmp (#4541)
  - Issue 4544 - Compiler warnings on krb5 functions (#4545)
  - Update rpm.mk for RUST tarballs


Package:  GitPython-3.1.13-1.fc34
Old package:  GitPython-3.1.11-2.fc34
Summary:  Python Git Library
RPMs: python3-GitPython
Size: 237.05 KiB
Size change:  373 B
Changelog:
  * Fri Feb 12 2021 Kevin Fenzi  - 3.1.13-1
  - Update to 3.1.13. Fixes rhbz#1913159


Package:  almanah-0.12.0-7.fc34
Old package:  almanah-0.12.0-6.fc34
Summary:  Application for keeping an encrypted diary
RPMs: almanah
Size: 1.30 MiB
Size change:  1.52 KiB
Changelog:
  * Fri Feb 12 2021 Milan Crha  - 0.12.0-7
  - Rebuilt for evolution-data-server soname bump


Package:  anaconda-34.24.2-1.fc34
Old package:  anaconda-34.24-1.fc34
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 22.43 MiB
Size change:  -54.45 KiB
Changelog:
  * Thu Feb 11 2021 Martin Kolman  - 34.24.1-1
  - Adjust configuration options for Fedora 34 (mkolman)
  - Add dependabot support for GitHub actions (jkonecny)
  - Set volume id for iso built for kickstart test (rvykydal)
  - Guess the defau

Re: dropping php-imap (was Re: Orphaned packages looking for new maintainers)

[Benson Muite]

On 2/13/21 1:48 PM, Miro Hrončok wrote:

On 09. 02. 21 12:17, Joe Orton wrote:

On Mon, Feb 08, 2021 at 06:43:29PM +, Gwyn Ciesla via devel wrote:
Can uw-imap be replaced with something else, or should someone pick 
it up?


There has not been an upstream release since 2007 - the maintainer Mark
Crispin sadly died in 2012, and nobody else has formed an upstream
around it.

In my view it makes sense to drop it from Fedora 35+ and take the pain
of disabling functionality until the various upstreams switch to
alternatives.  Hopefully Remi can comment on alternatives.


Since uw-imap does not install in Fedora 34 even, and nobody takes care 
of it, it has been scheduled for early retirement, see 
https://pagure.io/releng/issue/10013 -- I guess if we are to preserve it 
in Fedora 34, somebody needs to take action.


I believe the best course of action is to take over the package and keep 
libc-client, but remove uw-imap.



PHP maintainers seemed to have been relying on Fedora maintenance:
https://github.com/uw-imap/imap
and have a related discussion:
https://bugs.php.net/bug.php?id=78572
How crucial is the libc-client? Probably other distributions have the 
same problem so some collaboration may be possible.

___
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

[Test-Announce] Fedora 34 Branched 20210213.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 34 Branched 20210213.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20210210.n.1: anaconda-34.24-1.fc34.src, 20210213.n.0: 
anaconda-34.24.2-1.fc34.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/34

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_34_Branched_20210213.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora's GPG key in DNS(SEC)

[Zbigniew Jędrzejewski-Szmek]

On Fri, Feb 12, 2021 at 02:47:47PM -0500, Matthew Miller wrote:
> On Fri, Feb 12, 2021 at 08:22:45PM +0100, Miroslav Suchý wrote:
> > Comments are welcomed.
> 
> You can use "host -t TYPE61" instead of "dig" to get less verbose output.
> "host -v -t TYPE61" will show a little more (like the flags) while still
> being less noisy than dig.

Or just use resolvectl:

$ COLUMNS=80 resolvectl openpgp fedora...@fedoraproject.org
2d81eb3c5ebd20d163ff111a2dbcdc7e3336825d7d2331a3ef543aa8._openpgpkey.fedoraproject.org
 IN OPENPGPKEY
mQINBFiskqMBEADTbsoAXpDPk+FtcwBEPZQVe0YQYdOqavfQQVD/RYAcHnJW/K1bZhQusBj
UIec9SfGi3uBNNmbziAvpd/ycMKyWHuWQLmBgbImrqnPbBPMXmxeNGnZjA1hjVDp0pzj2+g
ZQhqYWSf6kQy9u9A1mSU63Kl/tfw7+hX7Tc3I8feGAFCHcFQgESxUib8Mw/OOGR3Am9fKdA
+K1kJeQIiZvXMcNFx+3CfoavhFdicuoT2KbcSuzRm76duKNHlLaP6/IbZxNiDWh8SDVpFaF
PlqR/R/+wibA6e9wMf6CZ4vfUY7NKYf4tYBs0EYdkn3j/KhJJxdb+M46Q/xwq9ovZo7XIhL
rIUPuMw91X9cbvkU/a9kE1ffdpNmF1fDnUcEkuuEqOl+aMVsUBEbAQ86yrwpDfL4XT9vwnD
IkggKZyvDTZ6q00XKg3GerKuZtQBl/YcHDXuBlB1fzpGl8a8hq/+GeT2sVxjlYwPXjrsKd1
NeP6ctQsR6gHuP3W5ohP4rArtM6ONN8rlTiodDLVGHBpUzIRdgr7RCL1AqB9vrdQ2MVZMas
TcUnUvKo0H4mps+x05jGao0b0Z0TJc6wr6ybHH38NVG06VX5rJZlfZchGwkWzmYxai55/7l
n1vJmk+kbdS7pK0jfmeVJ8A77XLCL36oJFCiCrYjV+ZGgvB+z08Jzwc7sgwARAQABtCxGZW
RvcmEgMjcgKDI3KSA8ZmVkb3JhLTI3QGZlZG9yYXByb2plY3Qub3JnPokCOAQTAQIAIgUCW
KySowIbDwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ9V50MPUoLuTcww/+LFPVEyVg
uMeU/QABEsE5FEN7kcDReZtdwq7p/aKC29mzCxeHggitYOGlrINkJ26Aq6p+oW6w7JxBWJn
KoTBYJDFzNIbp/6GbG4oKcEnWQZfTnRLTr5aukVdWBFevzC0huraobKz3joYRIX826VUzS/
A418zpnDVPtpo3x86V9f292rqi2tn9Q5cQC5Ck3/cjQDEwkN9gHz4j/c1oa6zBOcHbKkaZd
WA2dIs6XOxCIHg78i6VQwMMs+vfm2vbV3ACCcOVnd3d6NxIQuDLEQwdtdB2zI8R74bjacos
rcafK+F2DnkM7WrLSCiTKLJBMRDx+X2nOjT5pLuts4FC/XYRO23SMtPAMzQ852Z1lkjsaVD
sjzNqCasUB0vDPHLQE8aj0zchNBSzuHoKpXNYTyJztekWL/QXkUsXu0x7N5WhBlZ+lni6Lt
ZU51l7BJd1n+ZKnQ4gmjQ1ffVLbgzb9Z1MNje0s61FdKmUJQGULYqh32W4GV+RLvtI6AJV/
EmFCUEfRJ3eA8tJiyKe512wiim/WDhvzFuuPBup2Z3TufiaJQOysLlN5+HUQitTtcd7j8Zg
psIAIZtSWOMxbIAJWbzn8gjfIj4ZDeo0ZZXH0VgDkXtpv1g8R2aRAz6ob5YYW5VnI2UEr53
x1Z7lmUhv/TUZn26IeU16jCJ80k7pJvQSF8Y= -- link: host0

-- Information acquired via protocol DNS in 851us.
-- Data is authenticated: yes

Zbyszek
___
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: dropping php-imap (was Re: Orphaned packages looking for new maintainers)

[Miro Hrončok]

On 09. 02. 21 12:17, Joe Orton wrote:

On Mon, Feb 08, 2021 at 06:43:29PM +, Gwyn Ciesla via devel wrote:

Can uw-imap be replaced with something else, or should someone pick it up?


There has not been an upstream release since 2007 - the maintainer Mark
Crispin sadly died in 2012, and nobody else has formed an upstream
around it.

In my view it makes sense to drop it from Fedora 35+ and take the pain
of disabling functionality until the various upstreams switch to
alternatives.  Hopefully Remi can comment on alternatives.


Since uw-imap does not install in Fedora 34 even, and nobody takes care of it, 
it has been scheduled for early retirement, see 
https://pagure.io/releng/issue/10013 -- I guess if we are to preserve it in 
Fedora 34, somebody needs to take action.


I believe the best course of action is to take over the package and keep 
libc-client, but remove uw-imap.


--
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

Re: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Daniel Pocock]

On 13/02/2021 09:11, Tomasz Torcz wrote:
> Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
>>
>>
>> On 12/02/2021 21:19, Justin Forbes wrote:
>>> On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton  wrote:

 https://fedoraproject.org/wiki/Changes/Power4kPageSize

 == Summary ==

 On ppc64le, the kernel is currently compiled for 64k page size.

 This change proposes using the more common 4k page size.

 Some things, like the AMD Radeon GPU drivers, firmware or related
 code, appear to be completely non-functional on the 64k page size.
 Insufficient upstream developers are testing such issues on this
 architecture.
>>>
>>> Just as there are many things that expect the 64K page size.  I am not
>>> doing this.
>>>
>>> Justin
>>
>> Can you please identify some of the things that expect 64k?
>>
>> If the GPU drivers don't work that makes it a complete non-starter for
>> many workstation users, or they have to compile their own kernels or
>> obtain custom kernels from another user.
> 
>   Or just fix the GPU drivers. They're open source, after all.

The GPUs also have firmware blobs
___
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: ELN SIG Launch

[Andreas Tunek]

Den lör 13 feb. 2021 kl 02:10 skrev Kevin Kofler via devel <
devel@lists.fedoraproject.org>:

> Kevin Kofler via devel wrote:
> > And why would I want to do Red Hat's / IBM's work for free?
> >
> > Contributing to Fedora provides value to me because I use Fedora myself.
> > In contrast, what would I gain from contributing to ELN?
>
> PS: Especially considering that the stable product Red Hat / IBM expects
> the
> community to help developing will NOT be provided to the community anymore
> by Red Hat / IBM after the end of this year.
>

Inviting somebody is not the same as expecting somebody. Also, you can use
CentOS Stream (and different RHEL rebuilds) as much as you like.

/Andreas


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

Re: ELN SIG Launch

[Miro Hrončok]

On 13. 02. 21 1:57, Kevin Kofler via devel wrote:

Do I need to be employed by Red Hat to be a member of the ELN SIG?

No, anyone with an interest in helping will be welcomed enthusiastically!

And why would I want to do Red Hat's / IBM's work for free?

Contributing to Fedora provides value to me because I use Fedora myself. In
contrast, what would I gain from contributing to ELN?


You contribute to Fedora because you use Fedora.

Others might want to contribute to ELN because they use EL or because they are 
passionate EPEL contributors already and want to participate in the layer below.


I can imagine even Fedora contributors who don't participate in EPEL much and 
don't use EL, but would be interested in being part of ELN SIG, work together to 
discover unneeded dependencies in Fedora itself, or to help shape the content 
set of next RHEL to better match Fedora's infra needs, or to make sure important 
features are enabled in RHEL proper so others don't use their absence as a 
reason (excuse?) not to allow something in Fedora for the next X years etc. etc. 
etc. (One could even join to make sure the impact for packagers who are not 
interested in ELN/EL is kept at a reasonable level.)


Long story short: There are many valid reasons to participate and I absolutely 
love the fact that *it is possible* (it wasn't in previous RHEL versions). But 
if none of the reasons apply to you, nobody's forcing you to join the SIG.


--
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

Fedora rawhide compose report: 20210212.n.1 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20210211.n.0
NEW: Fedora-Rawhide-20210212.n.1

= SUMMARY =
Added images:3
Dropped images:  15
Added packages:  126
Dropped packages:3
Upgraded packages:   179
Downgraded packages: 0

Size of added packages:  159.48 MiB
Size of dropped packages:677.48 KiB
Size of upgraded packages:   5.84 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   1.40 GiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Games live x86_64
Path: Labs/x86_64/iso/Fedora-Games-Live-x86_64-Rawhide-20210212.n.1.iso
Image: Xfce_Appliance raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Xfce-armhfp-Rawhide-20210212.n.1-sda.raw.xz
Image: Xfce live x86_64
Path: Spins/x86_64/iso/Fedora-Xfce-Live-x86_64-Rawhide-20210212.n.1.iso

= DROPPED IMAGES =
Image: Server dvd ppc64le
Path: Server/ppc64le/iso/Fedora-Server-dvd-ppc64le-Rawhide-20210211.n.0.iso
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Server-dvd-s390x-Rawhide-20210211.n.0.iso
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20210211.n.0.s390x.tar.xz
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20210211.n.0.iso
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20210211.n.0.ppc64le.raw.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20210211.n.0.ppc64le.tar.xz
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20210211.n.0.s390x.raw.xz
Image: Container_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Base-Rawhide-20210211.n.0.s390x.tar.xz
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20210211.n.0.s390x.qcow2
Image: Everything boot ppc64le
Path: 
Everything/ppc64le/iso/Fedora-Everything-netinst-ppc64le-Rawhide-20210211.n.0.iso
Image: Everything boot s390x
Path: 
Everything/s390x/iso/Fedora-Everything-netinst-s390x-Rawhide-20210211.n.0.iso
Image: Container_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Base-Rawhide-20210211.n.0.ppc64le.tar.xz
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Server-netinst-s390x-Rawhide-20210211.n.0.iso
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20210211.n.0.ppc64le.qcow2
Image: Server boot ppc64le
Path: Server/ppc64le/iso/Fedora-Server-netinst-ppc64le-Rawhide-20210211.n.0.iso

= ADDED PACKAGES =
Package: dosbox-staging-0.76.0-2.fc35
Summary: DOS/x86 emulator focusing on ease of use
RPMs:dosbox-staging
Size:6.78 MiB

Package: perl-4:5.32.1-467.module_f35+11299+2c136bae
Summary: Practical Extraction and Report Language
RPMs:perl perl-Attribute-Handlers perl-AutoLoader perl-AutoSplit perl-B 
perl-Benchmark perl-Class-Struct perl-Config-Extensions perl-DBM_Filter 
perl-Devel-Peek perl-Devel-SelfStubber perl-DirHandle perl-Dumpvalue 
perl-DynaLoader perl-English perl-Errno perl-ExtUtils-Constant 
perl-ExtUtils-Embed perl-ExtUtils-Miniperl perl-Fcntl perl-File-Basename 
perl-File-Compare perl-File-Copy perl-File-DosGlob perl-File-Find 
perl-File-stat perl-FileCache perl-FileHandle perl-FindBin perl-GDBM_File 
perl-Getopt-Std perl-Hash-Util perl-Hash-Util-FieldHash perl-I18N-Collate 
perl-I18N-LangTags perl-I18N-Langinfo perl-IO perl-IO-Zlib perl-IPC-Open3 
perl-Locale-Maketext-Simple perl-Math-Complex perl-Memoize perl-Module-Loaded 
perl-NDBM_File perl-NEXT perl-Net perl-Net-Ping perl-ODBM_File perl-Opcode 
perl-POSIX perl-Pod-Functions perl-Pod-Html perl-Safe perl-Search-Dict 
perl-SelectSaver perl-SelfLoader perl-Symbol perl-Sys-Hostname 
perl-Term-Complete perl-Term-ReadLine perl-Test perl-Text-Abbrev perl-Thread 
perl-Thread-Semaphore perl-Tie perl-Tie-File perl-Tie-Memoize perl-Tie-RefHash 
perl-Time perl-Time-Piece perl-Unicode-UCD perl-User-pwent perl-autouse 
perl-base perl-blib perl-debugger perl-deprecate perl-devel perl-diagnostics 
perl-doc perl-encoding-warnings perl-fields perl-filetest perl-if 
perl-interpreter perl-less perl-lib perl-libnetcfg perl-libs perl-locale 
perl-macros perl-meta-notation perl-mro perl-open perl-overload 
perl-overloading perl-ph perl-sigtrap perl-sort perl-subs perl-tests perl-utils 
perl-vars perl-vmsish
Size:82.12 MiB

Package: perl-Algorithm-Diff-1.1903-14.module_f35+11289+1f4b364e
Summary: Compute `intelligent' differences between two files/lists
RPMs:perl-Algorithm-Diff
Size:95.23 KiB

Package: perl-Archive-Tar-2.38-1.module_f35+11289+1f4b364e
Summary: A module for Perl manipulation of .tar files
RPMs:perl-Archive-Tar
Size:145.61 KiB

Package: perl-Archive-Zip-1.67-1.module_f35+11289+1f4b364e
Summary: Perl library for accessing Zip archives
RPMs:perl-Archive-Zip
Size:214.91 KiB

Package: perl-CPAN-2.28-2.module_f35+11289+1f4b364e
Summary: Query, download and build perl modules 

Fedora-Cloud-32-20210213.0 compose check report

[Fedora compose checker]

No missing expected images.

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

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

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

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: Fedora 33 Beta blocker status email #1

[Adam Williamson]

On Fri, 2021-02-12 at 20:50 -0500, Matthew Miller wrote:
> On Sat, Feb 13, 2021 at 02:02:16AM +0100, Kevin Kofler via devel wrote:
> > Ben Cotton wrote:
> > > 2. kde-settings — KDE needs to pick up F34 backgrounds — NEW
> > > ACTION: kde-settings maintainers to adopt F34 backgrounds
> > 
> > Oh, it's Groundhog Day, again?
> > 
> > Can we PLEASE find a process for the backgrounds which does NOT include 
> > having this beta blocker open at each and every beta freeze?
> 
> The Fedora 34 background just went in, but the Fedora 35 background should
> land soon. The goal is to shift forward so the new backgrounds to actually
> land in Rawhide at around the time that Rawhide "becomes" the next release
> — so around August 10th this year for Fedora 36.
> 
> However, there still needs to be an update in KDE, right? And it'd still be
> a blocker, although ideally never get to the point where it _matters_ that
> it's a blocker. Or, maybe there is something that can be done in KDE to
> automatically pick up the latest?

It being a blocker isn't necessarily a problem. This happening *late*
is a problem.

This cycle it's actually going better, I'd say - we're not at freeze
yet, remember. We've only just branched. Freeze isn't for over a week.
And the kde-settings build happened today. If that does the job, then
I'm fine with the timing.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


___
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: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Tomasz Torcz]

Dnia Fri, Feb 12, 2021 at 10:16:26PM +0100, Daniel Pocock napisał(a):
> 
> 
> On 12/02/2021 21:19, Justin Forbes wrote:
> > On Fri, Feb 12, 2021 at 10:21 AM Ben Cotton  wrote:
> >>
> >> https://fedoraproject.org/wiki/Changes/Power4kPageSize
> >>
> >> == Summary ==
> >>
> >> On ppc64le, the kernel is currently compiled for 64k page size.
> >>
> >> This change proposes using the more common 4k page size.
> >>
> >> Some things, like the AMD Radeon GPU drivers, firmware or related
> >> code, appear to be completely non-functional on the 64k page size.
> >> Insufficient upstream developers are testing such issues on this
> >> architecture.
> > 
> > Just as there are many things that expect the 64K page size.  I am not
> > doing this.
> > 
> > Justin
> 
> Can you please identify some of the things that expect 64k?
> 
> If the GPU drivers don't work that makes it a complete non-starter for
> many workstation users, or they have to compile their own kernels or
> obtain custom kernels from another user.

  Or just fix the GPU drivers. They're open source, after all.

-- 
Tomasz Torcz   “(…) today's high-end is tomorrow's embedded processor.”
to...@pipebreaker.pl  — Mitchell Blank on LKML
___
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