Re: Fedora-Rawhide-20210430.n.0 compose check report

[Luna Jernberg]

This one works, and cya all at the last day of the Release Party for 34 in
some hours

On Fri, Apr 30, 2021 at 4:42 PM Fedora compose checker <
rawh...@fedoraproject.org> wrote:

> No missing expected images.
>
> Compose FAILS proposed Rawhide gating check!
> 3 of 43 required tests failed
> openQA tests matching unsatisfied gating requirements shown with
> **GATING** below
>
> Failed openQA tests: 18/189 (x86_64), 11/127 (aarch64)
>
> New failures (same test not failed in Fedora-Rawhide-20210428.n.1):
>
> ID: 873976  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
> URL: https://openqa.fedoraproject.org/tests/873976
> ID: 874029  Test: x86_64 KDE-live-iso desktop_notifications_live
> URL: https://openqa.fedoraproject.org/tests/874029
> ID: 874265  Test: aarch64 universal install_european_language@uefi
> URL: https://openqa.fedoraproject.org/tests/874265
>
> Old failures (same test failed in Fedora-Rawhide-20210428.n.1):
>
> ID: 873966  Test: x86_64 Server-dvd-iso install_vnc_server
> URL: https://openqa.fedoraproject.org/tests/873966
> ID: 873982  Test: x86_64 Server-dvd-iso
> server_role_deploy_domain_controller **GATING**
> URL: https://openqa.fedoraproject.org/tests/873982
> ID: 873985  Test: x86_64 Server-dvd-iso install_vnc_client
> URL: https://openqa.fedoraproject.org/tests/873985
> ID: 873986  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
> **GATING**
> URL: https://openqa.fedoraproject.org/tests/873986
> ID: 873989  Test: x86_64 Server-dvd-iso modularity_tests
> URL: https://openqa.fedoraproject.org/tests/873989
> ID: 873990  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
> URL: https://openqa.fedoraproject.org/tests/873990
> ID: 874006  Test: x86_64 Server-dvd-iso realmd_join_cockpit
> URL: https://openqa.fedoraproject.org/tests/874006
> ID: 874022  Test: x86_64 Workstation-live-iso desktop_login
> URL: https://openqa.fedoraproject.org/tests/874022
> ID: 874023  Test: x86_64 Workstation-live-iso apps_startstop
> URL: https://openqa.fedoraproject.org/tests/874023
> ID: 874036  Test: x86_64 KDE-live-iso apps_startstop
> URL: https://openqa.fedoraproject.org/tests/874036
> ID: 874076  Test: aarch64 Server-dvd-iso install_vnc_server@uefi
> URL: https://openqa.fedoraproject.org/tests/874076
> ID: 874081  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
> URL: https://openqa.fedoraproject.org/tests/874081
> ID: 874110  Test: aarch64 Server-dvd-iso modularity_tests@uefi
> URL: https://openqa.fedoraproject.org/tests/874110
> ID: 874133  Test: aarch64 Workstation-raw_xz-raw.xz
> desktop_browser@uefi
> URL: https://openqa.fedoraproject.org/tests/874133
> ID: 874165  Test: x86_64 universal upgrade_2_server_domain_controller
> URL: https://openqa.fedoraproject.org/tests/874165
> ID: 874173  Test: x86_64 universal upgrade_server_domain_controller
> URL: https://openqa.fedoraproject.org/tests/874173
> ID: 874191  Test: x86_64 universal upgrade_2_realmd_client
> URL: https://openqa.fedoraproject.org/tests/874191
> ID: 874198  Test: x86_64 universal install_asian_language
> URL: https://openqa.fedoraproject.org/tests/874198
> ID: 874210  Test: x86_64 universal install_blivet_resize_lvm
> URL: https://openqa.fedoraproject.org/tests/874210
> ID: 874221  Test: x86_64 universal upgrade_realmd_client
> URL: https://openqa.fedoraproject.org/tests/874221
> ID: 874224  Test: aarch64 universal install_asian_language@uefi
> URL: https://openqa.fedoraproject.org/tests/874224
> ID: 874238  Test: aarch64 universal
> upgrade_2_server_domain_controller@uefi
> URL: https://openqa.fedoraproject.org/tests/874238
> ID: 874243  Test: aarch64 universal install_blivet_resize_lvm@uefi
> URL: https://openqa.fedoraproject.org/tests/874243
> ID: 874249  Test: aarch64 universal
> upgrade_server_domain_controller@uefi
> URL: https://openqa.fedoraproject.org/tests/874249
> ID: 874251  Test: aarch64 universal upgrade_2_realmd_client@uefi
> URL: https://openqa.fedoraproject.org/tests/874251
> ID: 874264  Test: aarch64 universal upgrade_realmd_client@uefi
> URL: https://openqa.fedoraproject.org/tests/874264
>
> Soft failed openQA tests: 1/189 (x86_64), 3/127 (aarch64)
> (Tests completed, but using a workaround for a known bug)
>
> Old soft failures (same test soft failed in Fedora-Rawhide-20210428.n.1):
>
> ID: 874061  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
> URL: https://openqa.fedoraproject.org/tests/874061
> ID: 874066  Test: aarch64 Minimal-raw_xz-raw.xz
> install_arm_image_deployment_upload@uefi
> URL: https://openqa.fedoraproject.org/tests/874066
> ID: 874119  Test: aarch64 Server-raw_xz-raw.xz
> install_arm_image_deployment_upload@uefi
> URL: https://openqa.fedoraproject.org/tests/874119
> ID: 874142  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
> URL: https://openqa.fedoraproject.org/tests/874142
>
> Passed openQA tests: 170/189 (x86_64), 113/127 

[Bug 1953981] perl-Graphics-TIFF-11 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
FEDORA-2021-2629b83bac has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-2629b83bac`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2629b83bac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-2629b83bac has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-2629b83bac`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2629b83bac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
FEDORA-2021-3ee965d9de has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-3ee965d9de`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-3ee965d9de

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
FEDORA-2021-f7210bb6b5 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-f7210bb6b5`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7210bb6b5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1953981] perl-Graphics-TIFF-11 is available

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
FEDORA-2021-f7210bb6b5 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-f7210bb6b5`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7210bb6b5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1953981] perl-Graphics-TIFF-11 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
FEDORA-2021-3ee965d9de has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-3ee965d9de`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-3ee965d9de

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1955843] New: perl-DateTime-Locale-1.32 is available

[bugzilla]

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

Bug ID: 1955843
   Summary: perl-DateTime-Locale-1.32 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-DateTime-Locale
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.32
Current version/release in rawhide: 1.31-2.fc34
URL: http://search.cpan.org/dist/DateTime-Locale/

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


-- 
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: New RPM submission

[Bryce Carson]

For what it's worth, I'm trying to join and have a package included and
there are definitely some areas I would like to improve. Should we make a
thread on their mailing list?

On Fri., Apr. 30, 2021, 5:50 p.m. Bryce Carson, 
wrote:

> Perhaps we could improve the wiki page on Joining** to make it more clear
> what the process is like?
>
> I read through the guidelines and the Joining page a couple times, and
> only near the end does it state that Joining is more about, well, joining
> as a person than publishing a package. I believe it then recommendeds Copr
> around that point for simple publishing.
>
> Maybe we could ask Docs and some newer joiners to do a little review of
> the wiki for Joining and see if we can rewrite and modernize?
>
> On Fri., Apr. 30, 2021, 10:43 a.m. Stephen John Smoogen, 
> wrote:
>
>>
>>
>> On Fri, 30 Apr 2021 at 12:26, Mattia Verga via devel <
>> devel@lists.fedoraproject.org> wrote:
>>
>>> Il 30/04/21 15:16, Joan Moreau via devel ha scritto:
>>>
>>> Thanks but I am really scratching my head to try to understand all this:
>>>
>>> 1 - How to get to the "packager" group ou forum or else ?
>>>
>>> 2 - What does it mean to "block the FE-NEEDSPONSOR
>>>  tracking
>>> bug" ?
>>>
>>> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340
>>>
>>> Any help very welcome
>>>
>>> Thanks
>>>
>>> JM
>>>
>>> Short answer: wait for someone to review your package submission,
>>> meanwhile you can do some informal reviews as described here [1] to show
>>> some sponsor you actually comprehend Fedora Packaging Guidelines [2].
>>>
>>> Becoming a Fedora packager and being allowed to push software in Fedora
>>> official repositories require following specific rules and standards. Just
>>> like getting a driver license, you're required to study the rules and to
>>> show you know how to do things. You cannot just jump in a car and start
>>> driving (at least, not in Italy).
>>>
>>> BTW from a quick look at your specfile, the changelog doesn't seem to be
>>> in the prescribed format.
>>>
>>
>> So going from this long list of posts, I think the core problem is that
>> new people do not have a good idea of what it means to have a package in
>> Fedora Linux.
>>
>> Fedora Linux is built around the idea that it is a total operating
>> system, which means that the packages should be integrated with each other.
>> This means that the packages in it have some knowledge of how the rest of
>> the operating system works so that they a) do not interfere with each other
>> and b) are able to ask for and use resources properly from other systems.
>> Over the ~30 years of Linux operating systems a lot of corner cases and
>> other complexities have been discovered which are boiled down in each
>> operating system's "packaging rules". Because Fedora Linux releases every 6
>> months, there are additional complexities which are needed to allow for
>> someone else to 'take over a package' that require 'prescribed formats and
>> rules of the road'. Finally because each application in a 'total operating
>> system' can affect the security of many different computers, there needs to
>> be a certain amount of trust between people on who the packager is, why
>> they are doing something, and what they know.
>>
>> This means that becoming a Fedora Packager requires some training
>> (usually done by oneself) and it requires commitment for working through
>> the process of becoming a packager. Similar processes are needed to add
>> packages in Debian and some other Linux distributions also.
>>
>> It is a lot of work, and it is probably something we should be more
>> upfront with (we mainly forget because most of us 'joined the club' years
>> ago).
>>
>>
>>
>>
>>> Mattia
>>>
>>> [1]
>>> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests
>>> [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/
>>> ___
>>> 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
>>>
>>
>>
>> --
>> Stephen J Smoogen.
>> I've seen things you people wouldn't believe. Flame wars in
>> sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
>> All those moments will be lost in time... like posts on  BBS...
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> 

Re: New RPM submission

[Bryce Carson]

Perhaps we could improve the wiki page on Joining** to make it more clear
what the process is like?

I read through the guidelines and the Joining page a couple times, and only
near the end does it state that Joining is more about, well, joining as a
person than publishing a package. I believe it then recommendeds Copr
around that point for simple publishing.

Maybe we could ask Docs and some newer joiners to do a little review of the
wiki for Joining and see if we can rewrite and modernize?

On Fri., Apr. 30, 2021, 10:43 a.m. Stephen John Smoogen, 
wrote:

>
>
> On Fri, 30 Apr 2021 at 12:26, Mattia Verga via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Il 30/04/21 15:16, Joan Moreau via devel ha scritto:
>>
>> Thanks but I am really scratching my head to try to understand all this:
>>
>> 1 - How to get to the "packager" group ou forum or else ?
>>
>> 2 - What does it mean to "block the FE-NEEDSPONSOR
>>  tracking
>> bug" ?
>>
>> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340
>>
>> Any help very welcome
>>
>> Thanks
>>
>> JM
>>
>> Short answer: wait for someone to review your package submission,
>> meanwhile you can do some informal reviews as described here [1] to show
>> some sponsor you actually comprehend Fedora Packaging Guidelines [2].
>>
>> Becoming a Fedora packager and being allowed to push software in Fedora
>> official repositories require following specific rules and standards. Just
>> like getting a driver license, you're required to study the rules and to
>> show you know how to do things. You cannot just jump in a car and start
>> driving (at least, not in Italy).
>>
>> BTW from a quick look at your specfile, the changelog doesn't seem to be
>> in the prescribed format.
>>
>
> So going from this long list of posts, I think the core problem is that
> new people do not have a good idea of what it means to have a package in
> Fedora Linux.
>
> Fedora Linux is built around the idea that it is a total operating system,
> which means that the packages should be integrated with each other. This
> means that the packages in it have some knowledge of how the rest of the
> operating system works so that they a) do not interfere with each other and
> b) are able to ask for and use resources properly from other systems. Over
> the ~30 years of Linux operating systems a lot of corner cases and other
> complexities have been discovered which are boiled down in each operating
> system's "packaging rules". Because Fedora Linux releases every 6 months,
> there are additional complexities which are needed to allow for someone
> else to 'take over a package' that require 'prescribed formats and rules of
> the road'. Finally because each application in a 'total operating system'
> can affect the security of many different computers, there needs to be a
> certain amount of trust between people on who the packager is, why they are
> doing something, and what they know.
>
> This means that becoming a Fedora Packager requires some training (usually
> done by oneself) and it requires commitment for working through the process
> of becoming a packager. Similar processes are needed to add packages in
> Debian and some other Linux distributions also.
>
> It is a lot of work, and it is probably something we should be more
> upfront with (we mainly forget because most of us 'joined the club' years
> ago).
>
>
>
>
>> Mattia
>>
>> [1]
>> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests
>> [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/
>> ___
>> 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
>>
>
>
> --
> Stephen J Smoogen.
> I've seen things you people wouldn't believe. Flame wars in
> sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
> All those moments will be lost in time... like posts on  BBS...
> ___
> 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] Proposal to CANCEL: 2021-05-03 Fedora QA Meeting

[Adam Williamson]

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything urgent on the agenda, so let's take a well-earned break
after the F34 release!

If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.

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

[EPEL-devel] Re: Is it possible to have openldap in EPEL8?

[Troy Dawson]

You would need to make an "openldap-servers" package.
It could be the exact same everything as openldap from RHEL, just a
different name, and without the openldap and openldap-clients binary
packages.
Or, if you want, you could use the Fedora version.  As far as I know, the
server and client don't have to be the same versions.
Troy


On Fri, Apr 30, 2021 at 2:27 PM Trey Dockendorf  wrote:

> I sent an email to what I hope is email address for Fedora openldap
> maintainers for epel8 branch but then I realized that might not be
> possible. It appears like RHEL8 ships the openldap and openldap-clients
> packages buts purposely leaves out openldap-servers.  So given that some
> RPMs exist and some are missing, how would that be handled to do an EPEL8
> build or would that simply not be possible?  I took the Fedora 35 SRPM and
> rebuilt for EPEL8 using mock with no issues but the overlap of openldap and
> openldap-clients packages I imagine is a problem.
>
> Thanks,
> - Trey
> ___
> 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 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] Re: Is it possible to have openldap in EPEL8?

[Lance Albertson]

On Fri, Apr 30, 2021 at 2:22 PM Trey Dockendorf  wrote:

> I sent an email to what I hope is email address for Fedora openldap
> maintainers for epel8 branch but then I realized that might not be
> possible. It appears like RHEL8 ships the openldap and openldap-clients
> packages buts purposely leaves out openldap-servers.  So given that some
> RPMs exist and some are missing, how would that be handled to do an EPEL8
> build or would that simply not be possible?  I took the Fedora 35 SRPM and
> rebuilt for EPEL8 using mock with no issues but the overlap of openldap and
> openldap-clients packages I imagine is a problem.
>

FWIW we've been doing the same and publishing them here [1] for our own
purposes. For now we only use this on the LDAP servers to work around any
potential issues on clients.

[1] https://ftp.osuosl.org/pub/osl/repos/yum/8/openldap/

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
___
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] Is it possible to have openldap in EPEL8?

[Trey Dockendorf]

I sent an email to what I hope is email address for Fedora openldap
maintainers for epel8 branch but then I realized that might not be
possible. It appears like RHEL8 ships the openldap and openldap-clients
packages buts purposely leaves out openldap-servers.  So given that some
RPMs exist and some are missing, how would that be handled to do an EPEL8
build or would that simply not be possible?  I took the Fedora 35 SRPM and
rebuilt for EPEL8 using mock with no issues but the overlap of openldap and
openldap-clients packages I imagine is a problem.

Thanks,
- Trey
___
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

RE: Unresponsive maintainer for genders package

[treydock]

Apologies, my indication of unresponsive was that I got no response when I 
emailed genders-maintain...@fedoraproject.org and 
genders-ow...@fedoraproject.org last week.  Maybe that was not the best way to 
make contact.

Thanks for adding me to the package, I'll see about getting EPEL8 builds going.

Thanks,
- Trey
___
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: Unresponsive maintainer for genders package

[Brown, David M JR via devel]

Trey,

Not quite unresponsive, just not as interested 

If you want to help maintaining genders that would be helpful. I’m the only one 
I think managing the package right now, so getting another person would be 
good. I’m going to add you as admin to 
https://src.fedoraproject.org/rpms/genders so hopefully you’ll be able to start 
the process of making an EPEL8 build.

Thanks,
- David Brown

From: Trey Dockendorf 
Sent: Friday, April 30, 2021 12:59 PM
To: devel@lists.fedoraproject.org
Cc: genders-maintain...@fedoraproject.org; genders-ow...@fedoraproject.org
Subject: Unresponsive maintainer for genders package

Check twice before you click! This email originated from outside PNNL.

I'd like to report what I think is an unresponsive maintainer for the genders 
package.  Per 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
 I filed this bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1955798

There do not appear to be any other bugs open for this package.

I am starting this process in hopes of getting EPEL8 builds done for genders. I 
would be happy to take on the package as a maintainer if needed.  I am also 
hoping to get this into EPEL8 so that I can also get powerman into EPEL8 which 
I believe depends on genders.

Thanks,
- Trey
___
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

Unresponsive maintainer for genders package

[Trey Dockendorf]

I'd like to report what I think is an unresponsive maintainer for the
genders package.  Per
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
I filed this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1955798

There do not appear to be any other bugs open for this package.

I am starting this process in hopes of getting EPEL8 builds done for
genders. I would be happy to take on the package as a maintainer if
needed.  I am also hoping to get this into EPEL8 so that I can also get
powerman into EPEL8 which I believe depends on genders.

Thanks,
- Trey
___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[DJ Delorie]

I normally would complain about taking options away from users, but as I
typically use ssh for root *anyway*, I felt this wasn't appropriate
(although I have a friend who never uses ssh keys, always
password-over-ssh).

I would, however, ask that the config file have a commented out option
that re-enables it, with a suitable text comment clearly saying
"uncomment this to allow root passwords over ssh".

Perhaps that comment might be a good place to mention ssh-copy-id ?

Such comments make the "best practices" much more discoverable without
frustrating users who just want to make things work.
___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Simo Sorce]

On Fri, 2021-04-30 at 20:42 +0200, Martin Kolman wrote:
> On Fri, 2021-04-30 at 15:23 +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 30, 2021 at 03:37:54PM +0200, Vitaly Zaitsev via devel
> > wrote:
> > > On 30.04.2021 15:21, Richard W.M. Jones wrote:
> > > > Not everything is exposed to the internet.  Please leave the
> > > > option,
> > > > disabled by default and with a suitable warning if you like.
> > > 
> > > Why are you still using passwords in 2021? SSH keys are much more
> > > secure and easier to use.
> > 
> > Because distributing SSH keys to temporary VMs is hard?  Not
> > everything is a long-lived machine connected to the internet.
> What about creating an admin user instead ? It's effectively the same
> ammount of clicks - instead of setting a root password and checking the
> "Allow SSH root login with password" checkbox, create a regular user
> and check the "make this user an admin" checkbox.
> 
> Regular users, including users with admin (sudo/wheel) privileges, can
> of course still login with password via SSH just fine.

This is not useful to use things like rsync or scp/sftp to transfer
files maintaining permissions/attributes/etc.. for doing quick local
testing, development, or other ephemeral things this option is
reasonable and there is no need to remove it.

And also to run commands it is not great, if you end up using su/sudo
without password, then you just made a process more complicated without
adding much if any security.

> > Rich.
> > 
> > -- 
> > Richard Jones, Virtualization Group, Red Hat 
> > http://people.redhat.com/~rjones
> > Read my programming and virtualization blog: 
> > http://rwmj.wordpress.com
> > virt-top is 'top' for virtual machines.  Tiny program with many
> > powerful monitoring features, net stats, disk stats, logging, etc.
> > http://people.redhat.com/~rjones/virt-top
> > ___
> > 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

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc



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

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Martin Kolman]

On Fri, 2021-04-30 at 15:23 +0100, Richard W.M. Jones wrote:
> On Fri, Apr 30, 2021 at 03:37:54PM +0200, Vitaly Zaitsev via devel
> wrote:
> > On 30.04.2021 15:21, Richard W.M. Jones wrote:
> > > Not everything is exposed to the internet.  Please leave the
> > > option,
> > > disabled by default and with a suitable warning if you like.
> > 
> > Why are you still using passwords in 2021? SSH keys are much more
> > secure and easier to use.
> 
> Because distributing SSH keys to temporary VMs is hard?  Not
> everything is a long-lived machine connected to the internet.
What about creating an admin user instead ? It's effectively the same
ammount of clicks - instead of setting a root password and checking the
"Allow SSH root login with password" checkbox, create a regular user
and check the "make this user an admin" checkbox.

Regular users, including users with admin (sudo/wheel) privileges, can
of course still login with password via SSH just fine.
> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat 
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: 
> http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
> ___
> 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-34-updates-20210430.0 compose check report

[Fedora compose checker]

Missing expected images:

Workstation live x86_64

Failed openQA tests: 2/19 (x86_64)

ID: 874446  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/874446
ID: 874453  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/874453

Passed openQA tests: 17/19 (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

[Bug 1955741] perl-experimental-0.023 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-experimental-0.023-1.fc32.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=66982383


-- 
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 1955741] New: perl-experimental-0.023 is available

[bugzilla]

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

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



Latest upstream release: 0.023
Current version/release in rawhide: 0.022-4.fc34
URL: http://search.cpan.org/dist/experimental/

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


-- 
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: Storing package metadata in ELF objects

[Mark Wielaard]

Hi,

On Sat, 2021-04-10 at 18:44 +, Zbigniew Jędrzejewski-Szmek wrote:
> [I'm forwarding the mail from Luca who is not subscribed to fedora-
> devel]
> On Sat, Apr 10, 2021 at 01:38:31PM +0100, Luca Boccassi wrote:
> Cross-posting to the mailing lists of a few relevant projects.

Note that in this version of the email the [N] references in your email
don't seem to point anywhere. I found an older variant of the same
email which contained:

[0] https://github.com/systemd/systemd/issues/18433
[1] https://systemd.io/COREDUMP_PACKAGE_METADATA/
[2] https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
[3] https://github.com/systemd/package-notes

> After an initial discussion [0], recently we have been working on a new
> specification [0] to encode rich package-level metadata inside ELF
> objects, so that it can be included automatically in generated coredump
> files. The prototype to parse this in systemd-coredump and store the
> information in systemd-journal is ready for testing and merged
> upstream. We are now seeking further comments/opinions/suggestions, as
> we have a few months before the next release and thus there's plenty of
> time to make incompatible changes to the format and implementation, if
> required.
> 
> A proposal to use this by default for all packages built in Fedora 35
> has been submitted [1].
> 
> The Fedora Wiki and the systemd.io document have more details, but to
> make a long story short, a new .notes.package section with a JSON
> payload will be included in ELF objects, encoding various package-
> build-time information like distro name, package
> name,
> etc.

Is there a list of default keys (and their canonical spelling, upper-
lower-Camel_Case, etc.)? If there is, could we have a "debuginfod" key
with as value an URL pointing to the debuginfod server URL where the
embedded build-id executable, debuginfo and sources can be found?
https://sourceware.org/elfutils/Debuginfod.html

> To summarize from the discussion, the main reasons why we believe this
> is useful are as following:
> 
> 1) minimal containers: the rpm database is not installed in the
> containers. The information about build-ids needs to be stored
> externally, so package name information is not available immediately,
> but only after offline processing. The new note doesn't depend on the
> rpm db in any way.
> 
> 2) handling of a core from a container, where the container and host
> have different distros
> 
> 3) self-built and external packages: unless a lot of care is taken to
> keep access to the debuginfo packages, this information may be lost.
> The new note is available even if the repository metadata gets lost.
> Users can easily provide equivalent information in a format that makes
> sense in their own environment. It should work even when rpms and debs
> and other formats are mixed, e.g. during container image creation.
> 
> Other than in Fedora, we are already making the required code changes
> at Microsoft to use the same format for internally-built
> binaries, and for tools that parse core files and logs.
> 
> Tools for RPM and DEB (debhelper) integration are also available [3].
> 
> > -- 
> > Kind regards,
> > Luca Boccassi
> 
> 
___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Gary Buhrmaster]

On Fri, Apr 30, 2021 at 5:18 PM Vitaly Zaitsev via devel
 wrote:
>
> On 30.04.2021 16:23, Richard W.M. Jones wrote:
> > Because distributing SSH keys to temporary VMs is hard?
>
> Kickstart + Ansible will fix all these issues.

Or, perhaps, cloud-init, for those using that approach.
___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Vitaly Zaitsev via devel]

On 30.04.2021 16:23, Richard W.M. Jones wrote:

Because distributing SSH keys to temporary VMs is hard?


Kickstart + Ansible will fix all these issues.

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

Re: GNOME only: KeepassXC quirks

[Vitaly Zaitsev via devel]

On 30.04.2021 16:23, Hans de Goede wrote:

Maybe instead the QT_QPA_PLATFORM environment option can be set in the
KDE wayland session, so that Wayland is used there while leaving GNOME3
alone ?


KDE Wayland already uses native qt-wayland backend. No changes needed.


I tend to agree, it seems this downstream patch breaks at least 3 apps:


4. goldendict (patched in upstream).
5. ksnip (patched in downstream).
6. flameshot (patched in upstream).


I can understand that it is desirable to make this change, but it seems that
QT5 just is not completely ready for this yet. For me the patch[2] breaks
2/2 Qt apps which I regularly used, so it seems that it would be best to drop
this downstream modification for now.


That's why this downstream patch should be dropped, IMO.

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

Re: GNOME only: KeepassXC quirks

[Vitaly Zaitsev via devel]

On 30.04.2021 16:09, Germano Massullo wrote:

Could you please suggest me how I could implement a patch?


https://src.fedoraproject.org/rpms/ksnip/blob/rawhide/f/ksnip-wayland-workaround.patch


Would you do it in the .desktop file?


Patching desktop file is not a good idea. It can break lots of things 
and custom themes.


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

Re: Status of CMake on EPEL-8?

[Stephen John Smoogen]

On Fri, 30 Apr 2021 at 12:35, Michael Catanzaro 
wrote:

> On Fri, Apr 30 2021 at 10:59:22 AM -0500, Ron Olson
>  wrote:
> > Hm, so does that mean it was packaged specifically for CentOS so it
> > presumably shows up in the CentOS repos?
>
> No, content flow is the reverse in el8:
>
> RHEL 8 (upstream) -> CentOS Stream 8 (downstream)
>
> Whereas for el9 the flow is:
>
> CentOS Stream 9 (upstream) -> RHEL 9 (downstream)
>
> Anyway you can see the shiny new cmake is in CentOS Stream 8, so can
> guess it's probably going to be included in RHEL 8.4, which we've just
> publicly announced will be released imminently. What I do not know is
> how long it will take to reach the EPEL buildroot, because I don't know
> how the buildroot is composed.
>
>
The buildroot for RHEL-8 is whatever was synced down from Red Hat at ~0330
UTC that day* (and then grobisplit at 10:00 UTC later).  That usually means
that within 24 hours of a minor release, koji has all those packages and is
building from it.

* sometimes we need to hand run it because of some sort of failure.




-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
All those moments will be lost in time... like posts on  BBS...
___
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 1953837] perl-PDL-2.043 is available

[bugzilla]

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

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-PDL-2.042 is available |perl-PDL-2.043 is available



--- Comment #3 from Upstream Release Monitoring 
 ---
Latest upstream release: 2.043
Current version/release in rawhide: 2.39.0-1.fc35
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: New RPM submission

[Stephen John Smoogen]

On Fri, 30 Apr 2021 at 12:26, Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:

> Il 30/04/21 15:16, Joan Moreau via devel ha scritto:
>
> Thanks but I am really scratching my head to try to understand all this:
>
> 1 - How to get to the "packager" group ou forum or else ?
>
> 2 - What does it mean to "block the FE-NEEDSPONSOR
>  tracking
> bug" ?
>
> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340
>
> Any help very welcome
>
> Thanks
>
> JM
>
> Short answer: wait for someone to review your package submission,
> meanwhile you can do some informal reviews as described here [1] to show
> some sponsor you actually comprehend Fedora Packaging Guidelines [2].
>
> Becoming a Fedora packager and being allowed to push software in Fedora
> official repositories require following specific rules and standards. Just
> like getting a driver license, you're required to study the rules and to
> show you know how to do things. You cannot just jump in a car and start
> driving (at least, not in Italy).
>
> BTW from a quick look at your specfile, the changelog doesn't seem to be
> in the prescribed format.
>

So going from this long list of posts, I think the core problem is that new
people do not have a good idea of what it means to have a package in Fedora
Linux.

Fedora Linux is built around the idea that it is a total operating system,
which means that the packages should be integrated with each other. This
means that the packages in it have some knowledge of how the rest of the
operating system works so that they a) do not interfere with each other and
b) are able to ask for and use resources properly from other systems. Over
the ~30 years of Linux operating systems a lot of corner cases and other
complexities have been discovered which are boiled down in each operating
system's "packaging rules". Because Fedora Linux releases every 6 months,
there are additional complexities which are needed to allow for someone
else to 'take over a package' that require 'prescribed formats and rules of
the road'. Finally because each application in a 'total operating system'
can affect the security of many different computers, there needs to be a
certain amount of trust between people on who the packager is, why they are
doing something, and what they know.

This means that becoming a Fedora Packager requires some training (usually
done by oneself) and it requires commitment for working through the process
of becoming a packager. Similar processes are needed to add packages in
Debian and some other Linux distributions also.

It is a lot of work, and it is probably something we should be more upfront
with (we mainly forget because most of us 'joined the club' years ago).




> Mattia
>
> [1]
> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests
> [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/
> ___
> 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
>


-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
All those moments will be lost in time... like posts on  BBS...
___
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: mingw-gcc to 11.1 ?

[Sandro Mani]

On 29.04.21 17:30, Richard W.M. Jones wrote:


It seems like it would be worth having them.  Unfortunately the patch
numbers of the base patches clash with the ones for mingw-gcc, so to
be neat we'd need to renumber the mingw-gcc ones.

I don't see any problem with that.


When you finish your build and it's in Rawhide then I'll see how hard
it will be to add the gcc patches.


Current status is mingw-winpthreads failing to build with [1]

undefined reference to `__udivmoddi4'

Looks like it isn't linking against libgcc, so looks like again related to [2]. 
If you have time to help investigating, I'm happy to grant you access to the 
COPR repo [3].

Thanks
Sandro

[1] 
https://download.copr.fedorainfracloud.org/results/smani/mingw-gcc-11/fedora-rawhide-x86_64/02153746-mingw-winpthreads/builder-live.log.gz

[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97618
[3] https://copr.fedorainfracloud.org/coprs/smani/mingw-gcc-11/

___
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: Status of CMake on EPEL-8?

[Michael Catanzaro]

On Fri, Apr 30 2021 at 10:59:22 AM -0500, Ron Olson 
 wrote:

Hm, so does that mean it was packaged specifically for CentOS so it
presumably shows up in the CentOS repos?


No, content flow is the reverse in el8:

RHEL 8 (upstream) -> CentOS Stream 8 (downstream)

Whereas for el9 the flow is:

CentOS Stream 9 (upstream) -> RHEL 9 (downstream)

Anyway you can see the shiny new cmake is in CentOS Stream 8, so can 
guess it's probably going to be included in RHEL 8.4, which we've just 
publicly announced will be released imminently. What I do not know is 
how long it will take to reach the EPEL buildroot, because I don't know 
how the buildroot is composed.


___
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: nokey warning during F33->F34 upgrade (fstrm package)

[Kevin Fenzi]

On Fri, Apr 30, 2021 at 02:19:31PM +0200, Germano Massullo wrote:
> After running
> dnf system-upgrade download --releasever=34
> and downloading all files, I got the following warning
> warning:
> /var/lib/dnf/system-upgrade/fedora-e21c25ac3662d294/packages/fstrm-0.6.0-4.fc34.x86_64.rpm:
> Header V4 RSA/SHA256 Signature, ID key 45719a39: NOKEY
> 
> Why this package does not have a key?

That is in fact the f34 key and the package is signed with it. 

You don't have that key in your rpmdb (which is why it says NOKEY). 

There was a fedora-release for f33/f32 that had this key in it, if you
updated to that it should have been able to correctly import it. 

Hard to say whats going on without more info. 
What version is there? what version of fedora-release do you have
installed?

kevin


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

Re: New RPM submission

[Mattia Verga via devel]

Il 30/04/21 15:16, Joan Moreau via devel ha scritto:

> Thanks but I am really scratching my head to try to understand all this:
>
> 1 - How to get to the "packager" group ou forum or else ?
>
> 2 - What does it mean to "block the 
> [FE-NEEDSPONSOR](https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR) 
> tracking bug" ?
>
> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340
>
> Any help very welcome
>
> Thanks
>
> JM

Short answer: wait for someone to review your package submission, meanwhile you 
can do some informal reviews as described here [1] to show some sponsor you 
actually comprehend Fedora Packaging Guidelines [2].

Becoming a Fedora packager and being allowed to push software in Fedora 
official repositories require following specific rules and standards. Just like 
getting a driver license, you're required to study the rules and to show you 
know how to do things. You cannot just jump in a car and start driving (at 
least, not in Italy).

BTW from a quick look at your specfile, the changelog doesn't seem to be in the 
prescribed format.

Mattia

[1] 
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests
[2] https://docs.fedoraproject.org/en-US/packaging-guidelines/___
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: Status of CMake on EPEL-8?

[Stephen John Smoogen]

On Fri, 30 Apr 2021 at 12:00, Ron Olson  wrote:

> Hm, so does that mean it was packaged specifically for CentOS so it
> presumably shows up in the CentOS repos?
>
>
Cmake is not in EPEL but in RHEL. The current version for 8.3 is
./rhel-8-for-x86_64-appstream-rpms/Packages/c/cmake-3.11.4-3.el8.x86_64.rpm.
Updated versions look to either appear in 8.4 which I am guessing will be
out after beta is done.
https://www.redhat.com/en/blog/red-hat-enterprise-linux-84-beta-now-available



> On 30 Apr 2021, at 10:33, Michael Catanzaro wrote:
>
> > On Fri, Apr 30 2021 at 10:26:49 AM -0500, Ron Olson
> >  wrote:
> >> Is there any plans on bringing CMake up to the current version of
> >> Fedora
> >> (3.19.7) or at the very least to something >= 3.15.1?
> >
> > Good news: looks like CentOS Stream 8 currently has CMake 3.18.2:
> >
> > https://git.centos.org/rpms/cmake/commits/c8s
> >
> > I don't know when that will reach the EPEL buildroot though.
> >
> > ___
> > 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
>


-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
All those moments will be lost in time... like posts on  BBS...
___
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: Status of CMake on EPEL-8?

[Ron Olson]

Hm, so does that mean it was packaged specifically for CentOS so it 
presumably shows up in the CentOS repos?


On 30 Apr 2021, at 10:33, Michael Catanzaro wrote:

On Fri, Apr 30 2021 at 10:26:49 AM -0500, Ron Olson 
 wrote:
Is there any plans on bringing CMake up to the current version of 
Fedora

(3.19.7) or at the very least to something >= 3.15.1?


Good news: looks like CentOS Stream 8 currently has CMake 3.18.2:

https://git.centos.org/rpms/cmake/commits/c8s

I don't know when that will reach the EPEL buildroot though.

___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Sérgio Basto]

On Thu, 2021-04-29 at 22:09 +0200, Martin Kolman wrote:
> Hi!
> At the moment the Anaconda installer used by Fedora contains an option
> called "Allow SSH root login with password" on the root password
> configuration screen.
> 
> This is how it looks like at the moment, on latest Fedora Rawhide
> installer image:
> 
> https://m4rtink.fedorapeople.org/screenshots/fedora/rawhide_f35/root_password_screen.png
> 
> For some backstory - in 2015 the OpenSSH upstream decided to disable
> password based root logins by default. This was done for security
> reasons as an attacker needs to only guess password to gain access to
> the root account. For a user account the attacker needs to guess both
> the username and password and the user account not even have admin
> privileges, making the remote password guessing attack both harder and
> less useful.
> 
> The Fedora OpenSSH package carried downstream patches to revert this
> upstream change up until summer 2019 when it was decided to restore the
> upstream behavior and drop the downstream patches as enough tools that
> required password based SSH login have been migrated to use either key
> authentication or user based login methods.
> 
> Now back to the "Allow SSH root login with password" checkbox in
> the installer GUI. :)
> 
> The option was added in 2019 when Fedora disabled password based root
> SSH login by default, as a temporary migration aid for users of the
> graphical installer. 
> 
> Note that the checkbox is not ticked by default, the user needs to make
> a conscious choice to allow this security problematic SSH login
> behavior.
> 
> Now fast forward to today, it's 2021, any use cases that needed
> password based root login via SSH had 2 more years to migrate while the
> amount of password guessing attacks certainly didn't get any lower.
> 
> For that reason we in the Anaconda development team feel like it's a
> good time to finally drop the "Allow SSH root login with password" from
> the Anaconda GUI.
> 
> If you are aware of some critical Fedora/Fedora spin usecase that
> depends on users regularly ticking this option, please let us know! 
> 
> If no such critical usecase is found, we will proceed with removing the
> option from the Anaconda GUI in a ~week from now in Rawhide.

Hi,
BTW while I want or like this feature when we are in a devel lab
without internet .
I think the approach was not the best (1) , because after enable root
login with password , it is not easy disable it again. 
IMHO this feature should not create a new config file  (CONFIG_PATH =
"etc/sysconfig/sshd-permitrootlogin"  ) but use the default one 
/etc/sysconfig/sshd 

(1)
https://github.com/rhinstaller/anaconda/pull/2042/files

> Best Wishes
> Martin Kolman & the Anaconda team
> ___
> 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

-- 
Sérgio M. B.
___
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: Status of CMake on EPEL-8?

[Michael Catanzaro]

On Fri, Apr 30 2021 at 10:26:49 AM -0500, Ron Olson 
 wrote:
Is there any plans on bringing CMake up to the current version of 
Fedora

(3.19.7) or at the very least to something >= 3.15.1?


Good news: looks like CentOS Stream 8 currently has CMake 3.18.2:

https://git.centos.org/rpms/cmake/commits/c8s

I don't know when that will reach the EPEL buildroot though.

___
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

Status of CMake on EPEL-8?

[Ron Olson]

Hi all-

I’m trying to build a package under EPEL-8[1] but it fails due to 
CMake being too old:

CMake 3.15.1 or higher is required.  You are running version 3.11.4.

Is there any plans on bringing CMake up to the current version of Fedora 
(3.19.7) or at the very least to something >= 3.15.1?


Thanks!

Ron



[1] 
https://kojipkgs.fedoraproject.org//work/tasks/3421/66973421/build.log

___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[PGNet Dev]

On 4/30/21 10:23 AM, Richard W.M. Jones wrote:

Because distributing SSH keys to temporary VMs is hard?  Not
everything is a long-lived machine connected to the internet.


+1

in addition to, e.g., an _initial_ setup on a remote/headless box at a VPS.
___
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: GNOME only: KeepassXC quirks

[Germano Massullo]

Il 30/04/21 16:23, Hans de Goede ha scritto:
> I tend to agree, it seems this downstream patch breaks at least 3 apps:
>
> 1. KeepassXC
> 2. calibre
> 3. audacious

I think also nextcloud-client. I have been receiving bugreports about
quirks on GNOME
___
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-20210430.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Compose FAILS proposed Rawhide gating check!
3 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

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

New failures (same test not failed in Fedora-Rawhide-20210428.n.1):

ID: 873976  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/873976
ID: 874029  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/874029
ID: 874265  Test: aarch64 universal install_european_language@uefi
URL: https://openqa.fedoraproject.org/tests/874265

Old failures (same test failed in Fedora-Rawhide-20210428.n.1):

ID: 873966  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/873966
ID: 873982  Test: x86_64 Server-dvd-iso 
server_role_deploy_domain_controller **GATING**
URL: https://openqa.fedoraproject.org/tests/873982
ID: 873985  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/873985
ID: 873986  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/873986
ID: 873989  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/873989
ID: 873990  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/873990
ID: 874006  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/874006
ID: 874022  Test: x86_64 Workstation-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/874022
ID: 874023  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/874023
ID: 874036  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/874036
ID: 874076  Test: aarch64 Server-dvd-iso install_vnc_server@uefi
URL: https://openqa.fedoraproject.org/tests/874076
ID: 874081  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/874081
ID: 874110  Test: aarch64 Server-dvd-iso modularity_tests@uefi
URL: https://openqa.fedoraproject.org/tests/874110
ID: 874133  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/874133
ID: 874165  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/874165
ID: 874173  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/874173
ID: 874191  Test: x86_64 universal upgrade_2_realmd_client
URL: https://openqa.fedoraproject.org/tests/874191
ID: 874198  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/874198
ID: 874210  Test: x86_64 universal install_blivet_resize_lvm
URL: https://openqa.fedoraproject.org/tests/874210
ID: 874221  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/874221
ID: 874224  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/874224
ID: 874238  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/874238
ID: 874243  Test: aarch64 universal install_blivet_resize_lvm@uefi
URL: https://openqa.fedoraproject.org/tests/874243
ID: 874249  Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/874249
ID: 874251  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/874251
ID: 874264  Test: aarch64 universal upgrade_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/874264

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

Old soft failures (same test soft failed in Fedora-Rawhide-20210428.n.1):

ID: 874061  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/874061
ID: 874066  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/874066
ID: 874119  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/874119
ID: 874142  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/874142

Passed openQA tests: 170/189 (x86_64), 113/127 (aarch64)

New passes (same test not passed in Fedora-Rawhide-20210428.n.1):

ID: 873978  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/873978
ID: 873996  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/873996
ID: 874002  Test: 

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Richard W.M. Jones]

On Fri, Apr 30, 2021 at 03:37:54PM +0200, Vitaly Zaitsev via devel wrote:
> On 30.04.2021 15:21, Richard W.M. Jones wrote:
> >Not everything is exposed to the internet.  Please leave the option,
> >disabled by default and with a suitable warning if you like.
> 
> Why are you still using passwords in 2021? SSH keys are much more
> secure and easier to use.

Because distributing SSH keys to temporary VMs is hard?  Not
everything is a long-lived machine connected to the internet.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: GNOME only: KeepassXC quirks

[Hans de Goede]

Hi,

On 4/30/21 3:33 PM, Vitaly Zaitsev via devel wrote:
> On 30.04.2021 12:23, Germano Massullo wrote:
>> There are many Fedora GNOME Wayland users experiencing quirks in using 
>> KeepassXC. Textboxes not showing text that is being written, other quirks 
>> with GNOME, etc.
> 
> There are a lot of issues with Mutter and Qt5[1]. That's why the Qt upstream 
> forces XCB backend for the Gnome 3, but Fedora removes it in downstream[2], 
> as approved by the system-wide proposal[3].
> 
> Please try the following:
> QT_QPA_PLATFORM=xcb /usr/bin/keepassxc

Ah interesting, I use calibre regularly under a GNOME3 wayland sessions and
I have noticed some weird issues there too, like the "completion" pop-ups
for things like the Author and Series fields which allow you to select an
Author / Series already used for other books showing up in completely
the wrong places, as well as right-click context(sub)menus also showing up
in completely the wrong places too.

I also use the audacious media-player for music in its x11amp compatible
skinned mode and that is has serious issues when used without
QT_QPA_PLATFORM=xcb under GNOME3. I thought this was just a special case
because of the skinned UI, but I now see that it is part of a wider pattern.

I was going to write the following here:

"""
I can understand if the KDE SIG wants to use Wayland by default when running
a KDE Wayland session, but under GNOME3 this indeed seems like a bad idea for 
now.

Maybe instead the QT_QPA_PLATFORM environment option can be set in the
KDE wayland session, so that Wayland is used there while leaving GNOME3
alone ?
"""

Which seems like a reasonable compromise to me, but then I looked at the
patch from [2] and it seems that that is the upstream default and the
Fedora packages are actually overriding this sensible upstream default.

> I think this downstream patch should be dropped from Fedora.

I tend to agree, it seems this downstream patch breaks at least 3 apps:

1. KeepassXC
2. calibre
3. audacious

And I have a feeling it breaks all Qt apps to at least some extend, now the
changes process page [3] does list a couple of reasons why this is necessary,
but I just checked and calibre looks fine with the mutter provided window
decorations for X11 windows instead of using CSD, so this does not seem like
a strong argument.

I can understand that it is desirable to make this change, but it seems that
QT5 just is not completely ready for this yet. For me the patch[2] breaks
2/2 Qt apps which I regularly used, so it seems that it would be best to drop
this downstream modification for now.

Regards,

Hans



> See also:
> 
> [1]: https://bugreports.qt.io/browse/QTBUG-88293
> [2]: 
> https://src.fedoraproject.org/rpms/qt5-qtbase/blob/rawhide/f/qtbase-use-wayland-on-gnome.patch
> [3]: https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
> 
___
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] please review: PR 4749 - Improve SASL logging

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4749

--

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

Re: GNOME only: KeepassXC quirks

[Germano Massullo]

Il 30/04/21 15:33, Vitaly Zaitsev via devel ha scritto:
> On 30.04.2021 12:23, Germano Massullo wrote:
>> There are many Fedora GNOME Wayland users experiencing quirks in
>> using KeepassXC. Textboxes not showing text that is being written,
>> other quirks with GNOME, etc.
>
> There are a lot of issues with Mutter and Qt5[1]. That's why the Qt
> upstream forces XCB backend for the Gnome 3, but Fedora removes it in
> downstream[2], as approved by the system-wide proposal[3].
>
> Please try the following:
> QT_QPA_PLATFORM=xcb /usr/bin/keepassxc
>
> I think this downstream patch should be dropped from Fedora.
>
> See also:
>
> [1]: https://bugreports.qt.io/browse/QTBUG-88293
> [2]:
> https://src.fedoraproject.org/rpms/qt5-qtbase/blob/rawhide/f/qtbase-use-wayland-on-gnome.patch
> [3]:
> https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
>

Thank you so much Vitaly, your infos are very precious. Many users
reported to have fixed their problems by using xcb platform.
Could you please suggest me how I could implement a patch? Would you do
it in the .desktop file?
___
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: New RPM submission

[Emmanuel Seyman]

* Joan Moreau via devel [30/04/2021 14:16] :
>
> 1 - How to get to the "packager" group ou forum or else ?

We use FAS (https://accounts.fedoraproject.org/user/eseyman/) to manage
Fedora developer accounts. FAS has the notion of groups, one of which is
the packager group (https://accounts.fedoraproject.org/group/packager/).

People can added in this group once they are sponsored in by somebody
with "sponsor" status.

> 2 - What does it mean to "block the FE-NEEDSPONSOR [1] tracking bug" ?

Bugzilla bugs can block and depend on other bugs. To block on the
FE-NEEDSPONSOR bug means to block on bug #177841 (which has the alias
FE-NEEDSPONSOR)

> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340

This bug blocks FE-NEEDSPONSOR so there is noting more to do on this
front.

Emmanuel
___
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: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Frédéric Pierret]

Hi!

Le 4/29/21 à 10:09 PM, Martin Kolman a écrit :

For that reason we in the Anaconda development team feel like it's a
good time to finally drop the "Allow SSH root login with password" from
the Anaconda GUI.


Yes!

I've thought to it in the past when I've submitted originally the "Lock root 
account" modification. Dropping this very insecure feature exposed from the 
installer is a very good idea.

Best regards,
Frédéric



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

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Vitaly Zaitsev via devel]

On 30.04.2021 15:21, Richard W.M. Jones wrote:

Not everything is exposed to the internet.  Please leave the option,
disabled by default and with a suitable warning if you like.


Why are you still using passwords in 2021? SSH keys are much more secure 
and easier to use.


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

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Vitaly Zaitsev via devel]

On 29.04.2021 22:09, Martin Kolman wrote:

At the moment the Anaconda installer used by Fedora contains an option
called "Allow SSH root login with password" on the root password
configuration screen.


+1 for this change. Remote login as root with password is very insecure 
and should be dropped.


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

Re: GNOME only: KeepassXC quirks

[Vitaly Zaitsev via devel]

On 30.04.2021 12:23, Germano Massullo wrote:
There are many Fedora GNOME Wayland users experiencing quirks in using 
KeepassXC. Textboxes not showing text that is being written, other 
quirks with GNOME, etc.


There are a lot of issues with Mutter and Qt5[1]. That's why the Qt 
upstream forces XCB backend for the Gnome 3, but Fedora removes it in 
downstream[2], as approved by the system-wide proposal[3].


Please try the following:
QT_QPA_PLATFORM=xcb /usr/bin/keepassxc

I think this downstream patch should be dropped from Fedora.

See also:

[1]: https://bugreports.qt.io/browse/QTBUG-88293
[2]: 
https://src.fedoraproject.org/rpms/qt5-qtbase/blob/rawhide/f/qtbase-use-wayland-on-gnome.patch

[3]: https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome

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

Re: New RPM submission

[Vitaly Zaitsev via devel]

On 30.04.2021 15:16, Joan Moreau via devel wrote:

1 - How to get to the "packager" group ou forum or else ?


https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group


2 - What does it mean to "block the FE-NEEDSPONSOR tracking bug" ?


Open your Bugzilla package review ticket, set "Blocks: FE-NEEDSPONSOR" 
and press "Save changes" button.


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

Re: New RPM submission

[Vitaly Zaitsev via devel]

On 29.04.2021 21:27, Joan Moreau via devel wrote:
Isn´t there a muh more systemic (and simpler) process to push a RPM in 
the distribution ?


No. With great power comes great responsibility.

Each candidate must, at least, prove that they are familiar with the 
Fedora packaging guidelines.


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

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Richard W.M. Jones]

On Thu, Apr 29, 2021 at 10:09:12PM +0200, Martin Kolman wrote:
> Now fast forward to today, it's 2021, any use cases that needed
> password based root login via SSH had 2 more years to migrate while the
> amount of password guessing attacks certainly didn't get any lower.

Not everything is exposed to the internet.  Please leave the option,
disabled by default and with a suitable warning if you like.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: New RPM submission

[Joan Moreau via devel]

Thanks but I am really scratching my head to try to understand all this:

1 - How to get to the "packager" group ou forum or else ?

2 - What does it mean to "block the FE-NEEDSPONSOR [1] tracking bug" ?

So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340

Any help very welcome

Thanks

JM

Extract:

Until you are sponsored into the packager group you are not able to own 
packages or to check in changes to packages which you own. However, you 
can still create an initial package and submit it for review as talked 
about on the joining the package collection maintainers page [2]. When 
you open your review request in bugzilla, you should block the 
FE-NEEDSPONSOR [1] tracking bug, that way all of the sponsors will be 
able to see your sponsorship request. Although FE-NEEDSPONSOR is set on 
the package's review request, it is the person that needs to be 
sponsored into the packager group, not the package. The package 
undergoes a review and approval [3] that is separate from someone 
sponsoring you. Note that it is possible to have accepted packages which 
you cannot import because you have not been sponsored. See below.


On 2021-04-29 14:51, Qiyu Yan wrote:


在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道：


Thank you
Concretely, how to "find a sponsor" ?

FYI:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

___
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



Links:
--
[1] https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR
[2] 
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Ensure_your_package_is_suitable

[3] https://fedoraproject.org/wiki/Package_Review_Process___
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: 20210430.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20210428.n.1
NEW: Fedora-Rawhide-20210430.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  4
Dropped packages:6
Upgraded packages:   81
Downgraded packages: 0

Size of added packages:  164.41 KiB
Size of dropped packages:13.09 MiB
Size of upgraded packages:   2.88 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -48.54 MiB
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-20210430.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: R-microbats-0.1.1-1.fc35
Summary: An implementation of Bat Algorithm in R
RPMs:R-microbats
Size:24.96 KiB

Package: R-pbapply-1.4.3-1.fc35
Summary: Adding Progress Bar to '*apply' Functions
RPMs:R-pbapply
Size:90.47 KiB

Package: google-compute-engine-guest-configs-20201207.00-7.fc35
Summary: Google Compute Engine guest environment tools
RPMs:google-compute-engine-guest-configs
Size:20.23 KiB

Package: poezio-omemo-0.3.0-2.fc35
Summary: OMEMO plugin for the Poezio XMPP client
RPMs:poezio-omemo
Size:28.75 KiB


= DROPPED PACKAGES =
Package: connman-1.34-14.fc35
Summary: An alternative daemon for managing internet connections on Linux
RPMs:connman connman-devel
Size:2.70 MiB

Package: google-compute-engine-tools-2.8.12-10.fc35
Summary: Google Compute Engine guest environment tools
RPMs:google-compute-engine-tools python3-google-compute-engine
Size:127.69 KiB

Package: python-pytest-catchlog-1.2.2-19.fc34
Summary: py.test plugin to catch log messages (fork of pytest-capturelog)
RPMs:python3-pytest-catchlog
Size:20.97 KiB

Package: r2cutter-0.1.1-4.fc35
Summary: GUI for radare2 reverse engineering framework
RPMs:r2cutter r2cutter-devel
Size:7.67 MiB

Package: racoon2-20100526a-46.fc35
Summary: An implementation of key management system for IPsec
RPMs:racoon2
Size:1.87 MiB

Package: rnv-1.7.11-22.fc34
Summary: Implementation of Relax NG Compact Syntax validator in ANSI C
RPMs:rnv vim-rnv
Size:719.66 KiB


= UPGRADED PACKAGES =
Package:  avahi-0.8-11.fc35
Old package:  avahi-0.8-10.fc35
Summary:  Local network service discovery
RPMs: avahi avahi-autoipd avahi-compat-howl avahi-compat-howl-devel 
avahi-compat-libdns_sd avahi-compat-libdns_sd-devel avahi-devel avahi-dnsconfd 
avahi-glib avahi-glib-devel avahi-gobject avahi-gobject-devel avahi-libs 
avahi-qt3 avahi-qt3-devel avahi-qt4 avahi-qt4-devel avahi-qt5 avahi-qt5-devel 
avahi-sharp avahi-tools avahi-ui avahi-ui-devel avahi-ui-gtk3 avahi-ui-sharp 
avahi-ui-sharp-devel avahi-ui-tools
Size: 5.04 MiB
Size change:  130.31 KiB
Changelog:
  * Thu Apr 29 2021 Rex Dieter  - 0.8-11
  - avahi libraries missing -fstack-protector-stong (#1817737)


Package:  awscli-1.19.61-1.fc35
Old package:  awscli-1.19.60-1.fc35
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 2.03 MiB
Size change:  -14 B
Changelog:
  * Thu Apr 29 2021 Gwyn Ciesla  - 1.19.61-1
  - 1.19.61


Package:  bind-32:9.16.15-1.fc35
Old package:  bind-32:9.16.13-1.fc35
Summary:  The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) 
server
RPMs: bind bind-chroot bind-devel bind-dlz-filesystem bind-dlz-ldap 
bind-dlz-mysql bind-dlz-sqlite3 bind-dnssec-doc bind-dnssec-utils bind-doc 
bind-libs bind-license bind-pkcs11 bind-pkcs11-devel bind-pkcs11-libs 
bind-pkcs11-utils bind-utils python3-bind
Size: 23.76 MiB
Size change:  28.12 KiB
Changelog:
  * Thu Apr 29 2021 Petr Menk  - 32:9.16.15-1
  - Update to 9.16.15


Package:  bind-dyndb-ldap-11.7-3.fc35
Old package:  bind-dyndb-ldap-11.7-2.fc35
Summary:  LDAP back-end plug-in for BIND
RPMs: bind-dyndb-ldap
Size: 541.94 KiB
Size change:  127 B
Changelog:
  * Thu Apr 29 2021 Petr Menk  - 11.7-3
  - Rebuilt for BIND 9.16.15


Package:  bionetgen-2.6.0-1.fc35
Old package:  bionetgen-2.5.2-2.fc34
Summary:  Software for rule-based modeling of biochemical systems
RPMs: bionetgen bionetgen-perl
Size: 1.58 MiB
Size change:  364 B
Changelog:
  * Thu Apr 29 2021 Antonio Trande  - 2.6.0-1
  - Release 2.6.0


Package:  breeze-icon-theme-5.81.0-3.fc35
Old package:  breeze-icon-theme-5.81.0-2.fc35
Summary:  Breeze icon theme
RPMs: breeze-icon-theme breeze-icon-theme-rcc
Size: 8.66 MiB
Size change:  608 B
Changelog:
  * Thu Apr 29 2021 Tom Callaway  - 5.81.0-3
  - use fedora logo image from fedora-logos (not upstream copy)


Package:  
copy-jdk-configs-3.9-4.0.pre.0.bf480d4217342a54d3f1103365d21f6e399c4932.fc35
Old package:  copy-jdk-configs-3.7-8.fc34
Summary:  JDKs configuration files copier
RPMs: copy-jdk-configs
Size: 24.90 KiB
Size change:  1.08 KiB
Changelog:
  * Thu Apr 29 2021 Fedora Release Engineering  - 
3.9-4.0.pre.0

Re: Intention to dropping the the "Allow SSH root login with password" option from the installer GUI

[Ben Cotton]

On Thu, Apr 29, 2021 at 4:17 PM Martin Kolman  wrote:
>
> For that reason we in the Anaconda development team feel like it's a
> good time to finally drop the "Allow SSH root login with password" from
> the Anaconda GUI.
>
> If you are aware of some critical Fedora/Fedora spin usecase that
> depends on users regularly ticking this option, please let us know!
>
> If no such critical usecase is found, we will proceed with removing the
> option from the Anaconda GUI in a ~week from now in Rawhide.
>
I agree with this change, however it's the sort of thing that should
go through Fedora's Changes process:
https://docs.fedoraproject.org/en-US/program_management/changes_policy/

This gives it increased visibility within the Fedora contributor
community and with users.


Thanks,
BC

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

Re: GNOME only: KeepassXC quirks

[Robert Marcano via devel]

On 4/30/21 8:17 AM, Germano Massullo wrote:

Il 30/04/21 14:11, Robert Marcano via devel ha scritto:

The bug about input fields not able to take text input happen
occasionally on passwords fields on XCA.


What is XCA?


Another Fedora package that uses QT

https://hohnstaedt.de/xca/



___
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

nokey warning during F33->F34 upgrade (fstrm package)

[Germano Massullo]

After running
dnf system-upgrade download --releasever=34
and downloading all files, I got the following warning
warning:
/var/lib/dnf/system-upgrade/fedora-e21c25ac3662d294/packages/fstrm-0.6.0-4.fc34.x86_64.rpm:
Header V4 RSA/SHA256 Signature, ID key 45719a39: NOKEY

Why this package does not have a key?

Cheers
___
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: GNOME only: KeepassXC quirks

[Germano Massullo]

Il 30/04/21 14:11, Robert Marcano via devel ha scritto:
> The bug about input fields not able to take text input happen
> occasionally on passwords fields on XCA.

What is XCA?
___
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: GNOME only: KeepassXC quirks

[Robert Marcano via devel]

On 4/30/21 6:23 AM, Germano Massullo wrote:

KeepassXC comaintainer here.

There are many Fedora GNOME Wayland users experiencing quirks in using 
KeepassXC. Textboxes not showing text that is being written, other 
quirks with GNOME, etc.


Upstream developers said many times that this only happen with Fedora users.

Myself I do use KDE Spin and I do not experience these issues (tested on 
Wayland too)


I don't paste bugs titles since they are misleading

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

https://bugzilla.redhat.com/show_bug.cgi?id=1941731 (CentOS 8)

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

https://github.com/keepassxreboot/keepassxc/issues/5608

plus others that I cannot find again at the moment

I would like to ask if you have any idea about why this happens on GNOME 
only (and not on other distros too)


Thank you


The bug about input fields not able to take text input happen 
occasionally on passwords fields on XCA. Switching focus to another 
application and coming back usually workarounds the problem.

___
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: GNOME only: KeepassXC quirks

[Otto Urpelainen]

Germano Massullo kirjoitti 30.4.2021 klo 13.23:

KeepassXC comaintainer here.

There are many Fedora GNOME Wayland users experiencing quirks in using
KeepassXC. Textboxes not showing text that is being written, other
quirks with GNOME, etc.

Upstream developers said many times that this only happen with Fedora users.

Myself I do use KDE Spin and I do not experience these issues (tested on
Wayland too)

I don't paste bugs titles since they are misleading

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

https://bugzilla.redhat.com/show_bug.cgi?id=1941731 (CentOS 8)

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

https://github.com/keepassxreboot/keepassxc/issues/5608

plus others that I cannot find again at the moment

I would like to ask if you have any idea about why this happens on GNOME
only (and not on other distros too)



Octave is suffering from similar problems. I have reported this:

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

and also saw another issue where menus opened in strange places on the 
screen, or even partially off-screen. I did not report that yet, because 
I do know how to reproduce reliably.


The best assumption I could produce was simply that Qt5 and Wayland do 
not play well together. Maybe Gnome also needs to be involved. Is there 
a distribution that has that combination, but does not have these problems?


As far as I know, Qt 5 reached end of life when Qt 6 came out. To me it 
seems unlikely that remaining Qt 5 Wayland problems will ever get fixed. 
Is there some downside to forcing XWayland through QT_QPA_PLATFORM=xcb 
for Qt 5 applications with problems on Wayland?


Otto
___
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 1835353] rubygem-mail: Out of memory issue through nested MIME parts

[bugzilla]

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

Vít Ondruch  changed:

   What|Removed |Added

 Blocks||1835361





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1835361
[Bug 1835361] rubygem-mail: Out of memory issue through nested MIME parts
[fedora-all]
-- 
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

GNOME only: KeepassXC quirks

[Germano Massullo]

KeepassXC comaintainer here.

There are many Fedora GNOME Wayland users experiencing quirks in using
KeepassXC. Textboxes not showing text that is being written, other
quirks with GNOME, etc.

Upstream developers said many times that this only happen with Fedora users.

Myself I do use KDE Spin and I do not experience these issues (tested on
Wayland too)

I don't paste bugs titles since they are misleading

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

https://bugzilla.redhat.com/show_bug.cgi?id=1941731 (CentOS 8)

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

https://github.com/keepassxreboot/keepassxc/issues/5608

plus others that I cannot find again at the moment

I would like to ask if you have any idea about why this happens on GNOME
only (and not on other distros too)

Thank you

___
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] PR test are failing because lmdb pacakages are not installed.

[Pierre Rogier]

Hi all,

When pushing commits on backend redesign phase 4 I got compile error on all
builds
 because lmdb package are not installed (==> lmdb.h is missing)

COPR build is successful (because I updated the rpm/389-ds-base.spec.in
spec file
 and COPR use it to install the prerequisites but obviously PR test builds
are different.
( I suspect that it is using some pre-built image )

Does anyone know how to fix that ?
  Regards
  Pierre

-- 
--

389 Directory Server Development Team
--- Begin Message ---
[389ds/389-ds-base] Compile workflow run

Repository: 389ds/389-ds-base
Workflow: Compile
Duration: 4 minutes and 22.0 seconds
Finished: 2021-04-30 09:19:17 UTC

View results: https://github.com/389ds/389-ds-base/actions/runs/798944212

Jobs:
  * compile (Fedora 33 GCC) failed (3 annotations)
  * compile (Fedora 33 GCC Strict) failed (12 annotations)
  * compile (Fedora 33 GCC Static Analyzer) failed (11 annotations)
  * compile (Fedora 33 Clang) failed (6 annotations)
  * compile (Fedora 33 Clang -Weverything) failed (12 annotations)

-- 
You are receiving this because this workflow ran on your branch.
Manage your GitHub Actions notifications: 
https://github.com/settings/notifications
--- End Message ---
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: New RPM submission

[Felix Schwarz]

Am 29.04.21 um 21:27 schrieb Joan Moreau via devel:
Isn´t there a muh more systemic (and simpler) process to push a RPM in the 
distribution ?


Fedora tries to ship working software. This means there has to be at least one 
person who really cares about each Fedora package. All these processes to try 
ensure that someone is sufficiently motivated and knowledgeable so users can 
trust on Fedora packages.


That being said I can see that some of these docs can feel "overwhelming" and 
from my observation not all packages follow the guidelines all the time. So I'd 
like to encourage you to join even if you feel that you are lacking some skills.
However you should be willing to spend some time for at least 1-2 years when 
trying to get a new package into Fedora.


If you just want to package something for Fedora users without long-term 
commitments you can also try COPR: https://copr.fedorainfracloud.org/

This is similar to Ubuntu's PPAs or the OpenSuse build service.

Your contribution will have a much lower impact (as the software is not 
available by default for all Fedora users) but you can push your package without 
any review and it is easily available in a somewhat well-known location.
Also it can provide a starting point for others to submit the package for 
inclusion in Fedora.


Felix
___
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 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Graphics-TIFF-12-1.fc3
   ||5




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

[Bug 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2021-3ee965d9de has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-3ee965d9de


-- 
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 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2021-f7210bb6b5 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7210bb6b5


-- 
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 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2021-2629b83bac has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2629b83bac


-- 
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 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Petr Pisar  ---
A enhancement release suitable for all Fedoras.


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

[Bug 1954342] perl-Devel-NYTProf-6.08 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|iarn...@gmail.com,  |
   |jples...@redhat.com |
   Doc Type|--- |If docs needed, set a value




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

Fedora-Cloud-33-20210430.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-20210429.0):

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

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

[Bug 1955258] perl-Graphics-TIFF-12 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




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

[Bug 1953837] perl-PDL-2.042 is available

[bugzilla]

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

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-PDL-2.041 is available |perl-PDL-2.042 is available



--- Comment #2 from Upstream Release Monitoring 
 ---
Latest upstream release: 2.042
Current version/release in rawhide: 2.39.0-1.fc35
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

[Bug 1955451] New: Upgrade perl-Crypt-X509 to 0.54

[bugzilla]

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

Bug ID: 1955451
   Summary: Upgrade perl-Crypt-X509 to 0.54
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Crypt-X509
  Assignee: rc040...@freenet.de
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
rc040...@freenet.de
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.53 version. Upstream released 0.54. When you have free
time, please upgrade it.


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