Re: Packaging of github cli?

[Joe Doss]

On 2/14/20 12:36 PM, Joe Doss wrote:
> I will see what it takes to get this submitted for review this weekend.

Here we go https://bugzilla.redhat.com/show_bug.cgi?id=1803302

If anyone has any some time to give these package a review that would be
great.

Joe



-- 
Joe Doss
j...@solidadmin.com
___
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

Re: URGENT: users prompted to upgrade to F32

[Kevin Fenzi]

On Fri, Feb 14, 2020 at 05:14:57PM -0800, Adam Williamson wrote:
> On Fri, 2020-02-14 at 18:37 -0600, Michael Catanzaro wrote:
> > Hi,
> > 
> > Users are being prompted to upgrade to F32. Anyone who knows how to fix 
> > this, please help with 
> > https://pagure.io/fedora-infrastructure/issue/8652 ASAP.
> 
> We fixed it several hours ago, but people are likely hitting copies of
> the bad data cached somewhere along the line :/
> 
> https://pagure.io/fedora-infrastructure/issue/8652#comment-626587

Yeah, it was live for about 45min this morning, but we fixed it as soon
as it was noted. ;( 

Not sure that there is too much more we can do at this point... 

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

[Bug 1802968] EPEL8 Build

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Term-ReadLine-Gnu-1.36-7.el8 has been pushed to the Fedora EPEL 8 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-452e225c88

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

[Bug 1798643] perl-Shell-Config-Generate-0.34 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Shell-Config-Generate- |perl-Shell-Config-Generate-
   |0.34-1.fc32 |0.34-1.fc32
   |perl-Shell-Config-Generate- |perl-Shell-Config-Generate-
   |0.34-1.fc31 |0.34-1.fc31
   ||perl-Shell-Config-Generate-
   ||0.34-1.fc30



--- Comment #7 from Fedora Update System  ---
perl-Shell-Config-Generate-0.34-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

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

[Bug 1795119] Upgrade perl-Time-Local to 1.30

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Time-Local-1.300-1.fc3 |perl-Time-Local-1.300-1.fc3
   |2   |2
   |perl-Time-Local-1.300-1.fc3 |perl-Time-Local-1.300-1.fc3
   |1   |1
   ||perl-Time-Local-1.300-1.fc3
   ||0



--- Comment #5 from Fedora Update System  ---
perl-Time-Local-1.300-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

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

[Test-Announce] 2020-02-17 @ 16:00 UTC - Fedora QA Meeting

[Adam Williamson]

# Fedora Quality Assurance Meeting
# Date: 2020-02-17
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's been a couple of weeks, so let's meet on Monday to check in on
Fedora 32 status and a few other things.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. F32 status
3. Proposals, IoT, CoreOS...
4. Test Day / community event status
5. Open floor
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://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
___
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

[Test-Announce] 2020-02-17 @ 17:00 UTC - Fedora 32 Blocker Review Meeting

[Adam Williamson]

# F32 Blocker Review meeting
# Date: 2020-02-17
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have 2 proposed Beta blockers, 1 proposed Beta freeze
exception, and 1 proposed Final blocker to review, so let's have a
Fedora 32 blocker review meeting on Monday!

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting -  the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

We'll be evaluating these bugs to see if they violate any of the 
Release Criteria and warrant the blocking of a release if they're not 
fixed. Information on the release criteria for F32 can be found on the 
wiki [0].

For more information about the Blocker and Freeze exception process, 
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting 
works - or how it's supposed to go and you want to run one - check out 
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://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
___
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

[Bug 1798643] perl-Shell-Config-Generate-0.34 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Shell-Config-Generate- |perl-Shell-Config-Generate-
   |0.34-1.fc32 |0.34-1.fc32
   ||perl-Shell-Config-Generate-
   ||0.34-1.fc31
 Resolution|--- |ERRATA
Last Closed||2020-02-15 02:16:50



--- Comment #6 from Fedora Update System  ---
perl-Shell-Config-Generate-0.34-1.fc31 has been pushed to the Fedora 31 stable
repository. If problems still persist, please make note of it in this bug
report.

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

[Bug 1802773] perl-Sys-Mmap-0.20 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Sys-Mmap-0.20-1.fc31 has been pushed to the Fedora 31 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-552ee1dcf5

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

Re: URGENT: users prompted to upgrade to F32

[Adam Williamson]

On Fri, 2020-02-14 at 18:37 -0600, Michael Catanzaro wrote:
> Hi,
> 
> Users are being prompted to upgrade to F32. Anyone who knows how to fix 
> this, please help with 
> https://pagure.io/fedora-infrastructure/issue/8652 ASAP.

We fixed it several hours ago, but people are likely hitting copies of
the bad data cached somewhere along the line :/

https://pagure.io/fedora-infrastructure/issue/8652#comment-626587
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: deduplicating noarch subpackages

[Kevin Kofler]

Josh Stone wrote:
> On 2/13/20 7:26 AM, Kevin Kofler wrote:
>> built only on one of them.) As far as I know, this was implemented that
>> way to make QEMU firmwares work (which are built on and for a specific
>> architecture, and then shipped as noarch packages for all of them so that
>> the architecture can be emulated).
> 
> Ah, I suppose you are referring to ipxe?

I was mainly referring to all those BIOS equivalents that are used for
qemu-system-* full system emulation.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

URGENT: users prompted to upgrade to F32

[Michael Catanzaro]

Hi,

Users are being prompted to upgrade to F32. Anyone who knows how to fix 
this, please help with 
https://pagure.io/fedora-infrastructure/issue/8652 ASAP.


Michael

___
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

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

[Kevin Kofler]

David Cantrell wrote:
>> On 1/30/20 8:32 AM, Kevin Kofler wrote:
[…]

I have not actually written the lines you quoted, Huzaifa Sidhpurwala has.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora-32-20200214.n.1 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 98/158 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-32-20200213.n.0):

ID: 521482  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/521482
ID: 521514  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/521514
ID: 521535  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/521535

Old failures (same test failed in Fedora-32-20200213.n.0):

ID: 521403  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/521403
ID: 521404  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/521404
ID: 521405  Test: x86_64 Server-dvd-iso support_server
URL: https://openqa.fedoraproject.org/tests/521405
ID: 521406  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/521406
ID: 521407  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/521407
ID: 521411  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/521411
ID: 521416  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/521416
ID: 521417  Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/521417
ID: 521418  Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation
URL: https://openqa.fedoraproject.org/tests/521418
ID: 521419  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/521419
ID: 521420  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/521420
ID: 521428  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/521428
ID: 521433  Test: x86_64 Server-dvd-iso install_vncconnect_server
URL: https://openqa.fedoraproject.org/tests/521433
ID: 521436  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/521436
ID: 521443  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/521443
ID: 521444  Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/521444
ID: 521445  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/521445
ID: 521446  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/521446
ID: 521447  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/521447
ID: 521462  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/521462
ID: 521467  Test: x86_64 KDE-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/521467
ID: 521471  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/521471
ID: 521473  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/521473
ID: 521480  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/521480
ID: 521483  Test: x86_64 universal install_multi
URL: https://openqa.fedoraproject.org/tests/521483
ID: 521484  Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/521484
ID: 521485  Test: x86_64 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/521485
ID: 521486  Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/521486
ID: 521487  Test: x86_64 universal install_xfs
URL: https://openqa.fedoraproject.org/tests/521487
ID: 521488  Test: x86_64 universal install_repository_http_variation
URL: https://openqa.fedoraproject.org/tests/521488
ID: 521489  Test: x86_64 universal support_server
URL: https://openqa.fedoraproject.org/tests/521489
ID: 521490  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/521490
ID: 521491  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/521491
ID: 521493  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/521493
ID: 521494  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/521494
ID: 521495  Test: x86_64 universal install_multi@uefi
URL: https://openqa.fedoraproject.org/tests/521495
ID: 521496  Test: x86_64 universal install_no_swap@uefi
URL: https://openqa.fedoraproject.org/tests/521496
ID: 521497  Test: x86_64 universal install_blivet_no_swap
URL: 

[Bug 1792699] perl-CDB_File-1.01 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CDB_File-1.00-1.fc32   |perl-CDB_File-1.00-1.fc32
   |perl-CDB_File-1.01-1.fc32   |perl-CDB_File-1.01-1.fc32
   |perl-CDB_File-1.01-1.fc31   |perl-CDB_File-1.01-1.fc31
   ||perl-CDB_File-1.01-1.el8



--- Comment #14 from Fedora Update System  ---
perl-CDB_File-1.01-1.el8 has been pushed to the Fedora EPEL 8 stable
repository. If problems still persist, please make note of it in this bug
report.

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

[Bug 1795181] Add perl-WWW-Curl to EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-WWW-Curl-4.17-21.el8
 Resolution|--- |ERRATA
Last Closed||2020-02-15 00:15:54



--- Comment #4 from Fedora Update System  ---
perl-WWW-Curl-4.17-21.el8 has been pushed to the Fedora EPEL 8 stable
repository. If problems still persist, please make note of it in this bug
report.

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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Kevin Fenzi]

On Fri, Feb 14, 2020 at 06:21:34PM +0100, Marius Schwarz wrote:
> Am 14.02.20 um 17:57 schrieb Kevin Fenzi:
> > On Fri, Feb 14, 2020 at 08:07:19AM -0500, Stephen John Smoogen wrote:
> >> On Fri, 14 Feb 2020 at 06:21, Leigh Griffin  wrote:
> >>
> >>>
> >>> On Fri, Feb 14, 2020 at 12:59 AM Artem Tim  wrote:
> >>>
>  Same here. I am waiting several minutes for every my action. This is very
>  unproductive.
> 
> >>> Log it as a ticket and I can get the CPE folks to investigate it and see
> >>> if there is an obvious problem that we can help with.
> >>>
> >>
> >> for people having this issue the ticket is
> >> https://pagure.io/fedora-infrastructure/issue/8648
> >>
> >> We need an idea of the geolocation you are coming from, traceroutes of
> >> where you are going from and if possible in the browser any links etc which
> >> are showing very slow (aka in Firefox right click inspect, and switch to
> >> the network page and do a ^R on the koji.fedoraproject.org page)
> > Also, it might help if people noted the exact time of day (UTC) they are
> > accessing things?
> >
> > I suspect it may be backup slowness (which happens after 00:00UTC +-
> > 2hour)
> 
> "NOW" aka. 14.2.2020 18:15 CET  the same pagecall to koji and firefox
> rpm download where as smooth as they could be.

ok. So that means the task link loaded in under 4 seconds?
> 
> But, the koji test page from the ticket, had 4,5 seconds loadtime, which
> was the first page i visited  in koji today.

Had before, but doesn't now? Or still does now?

> I know this behaviour from my serverfarm, if the initial DNS resolver is
> not responding and the timeout until the second is asked, kicks in.
> As the server does no longer need to ask for an ip resolv on the second
> visit (here firefox), it responds faster.

You mean the end user dns? Sure, could cause problems indeed... but
thats out of our control.
> 
> This does not explain the worst case download rate from yesterday, but
> it can explain the results people have writte to the ticket for visiting
> koji .

It would seem odd for a variety of people to all hit dns issues at the
same time with different end user servers. 

Anyhow, I have asked for more info in the ticket, hopefully we can
figure something out. 

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

Re: Invalid body, keys: sls missing

[Kevin Fenzi]

On Thu, Feb 13, 2020 at 10:00:36AM -0700, Jerry James wrote:
> I'm trying to get an f32 branch for a newly created package.  Branch
> creation has failed twice now with the error in $SUBJECT:
> 
> https://pagure.io/releng/fedora-scm-requests/issue/22127
> 
> Can I get a human to look at that ticket instead of whatever
> automation it is that keeps closing it without actually accomplishing
> the requested task?  Thanks,

I think mohan and pingou were trying to debug this on another package
the other day, but I am not sure where they got. 

The thing to do when these tickets don't process right is to open a new
releng ticket. Just re-opening the scm-request usually just results in
it failing to process again. ;( 

So, if you could file a ticket and note the package hopefully we can get
it fixed. 

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

Re: dnf exit code

[Kevin Fenzi]

On Thu, Feb 13, 2020 at 07:42:45AM -0500, Matthew Miller wrote:
> On Wed, Feb 12, 2020 at 10:29:47AM +0100, Daniel Mach wrote:
> > There seem to be 2 related problems:
> > 1) Only the image on docker.io doesn't work. If you use
> > registry.fedoraproject.org/fedora:rawhide, it works as expected.
> 
> Yeah, that's ... concerning. They should be identical.

nope... we can update our registry every rawhide compose. 
In order to update docker.io, someone has to file a PR, sign stuff and
wait for them to merge it. It's not automated and it's sometimes slow. 

So, docker.io could be out of date a fair bit...

> > 2) Fedora infra is unreliable. When the image from
> > registry.fedoraproject.org cannot be downloaded, there's a fallback
> > to docker.io which contains a different image. Running the command
> > several times in a row produces "random" results:
> 
> I believe the plan is to migrate to using quay.io now that that's open
> source.

Yeah, ideally, but we need them to support multi-arch and flatpaks. ;) 

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

Re: Fonts packaging policy rewrite proposal

[Nicolas Mailhot via devel]

Le mardi 12 novembre 2019 à 09:00 +0100, Nicolas Mailhot a écrit :
> A fonts packaging policy rewrite proposal has been pushed to FPC
> today:
> https://pagure.io/packaging-committee/pull-request/934
> 
> It should be clearer, more opinionated, and take into account:
>   – updates of The OpenType standard
>   – variable fonts
>   – web fonts
>   – upstream depreciation of non OpenType formats
>   – appstream & fonts
>   – weak dependencies
>   – and probably more I forget here

And the proposal has now been approved by FPC:
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2020-02-13/fpc.2020-02-13-17.00.txt

It shall soon replace the content in
https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/

and make it easier to create good font packages in Fedora.

> It is based on the new fonts-rpm-macros project for automation:

The associated review request is here
https://bugzilla.redhat.com/show_bug.cgi?id=1803281

Depending on how long the review takes, some of the material in
https://copr.fedorainfracloud.org/coprs/nim/fonts-rpm-macros/builds/

may end up in Fedora 32, or slip to the next release.

If it slips pre Fedora 33 font package changes will probably be limited
to conservative updates.

Regards,

-- 
Nicolas Mailhot
___
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

[EPEL-devel] Re: Proposed official change to EPEL guidelines: modules and RHEL

[Chris Adams]

Once upon a time, Kevin Fenzi  said:
> Does this mean if there's a package foo that is a rhel package, but not
> in a module, that it can be overlapped with a foo package thats in a
> epel non default module? ie, does it only mean the modular case or does
> it mean any rpm?

As a consumer of EPEL, I'd rather nothing in the base RHEL (or really
CentOS in my case) ever get replaced, up or downgrade, by something in
EPEL.

Unless... does RHEL have modules that replace base packages?  I admit, I
haven't fully got my head wrapped around all the effects of modularity.

-- 
Chris Adams 
___
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

[EPEL-devel] Re: Proposed official change to EPEL guidelines: modules and RHEL

[Kevin Fenzi]

On Thu, Feb 13, 2020 at 07:54:24AM -0500, Matthew Miller wrote:
> I've been saying this for a while as if it's fact, but of course it's not
> actually fact until approved, so I'm puting this to the EPEL team to
> hopefully do so.
> 
> The current guidelines * say:
> 
>EPEL packages should only enhance and never disturb the Enterprise Linux
>distributions they were built for. Thus packages from EPEL should never
>replace packages from the target base distribution - including those on the
>base distribution as well as layered products; kernel-modules further are
>not allowed, as they can disturb the base kernel easily.
> 
> With modularity in EPEL 8, we have the opportunity to allow more flexibility
> while preserving the primary goal of not disturbing the base distribution.
> Therefore, I propose adding:
> 
>   In EPEL 8 or later, it is permitted to have module streams which contain
>   packages with alternate versions to those provided in RHEL. These packages
>   may be newer, built with different options, or even older to serve
>   compatibility needs. These MUST NOT be the default stream -- in every
>   case, explicit user action must be required to opt in to these versions.
> 
> 
> (Note that the base package _does not_ have to be part of a module for this
> to work.)
> 
> What do you think?

This is what I was trying to get to in the thread recently about
libssh2. However it's still not entirely clear to me. 

Does this mean if there's a package foo that is a rhel package, but not
in a module, that it can be overlapped with a foo package thats in a
epel non default module? ie, does it only mean the modular case or does
it mean any rpm?

kevin


signature.asc
Description: PGP signature
___
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

[EPEL-devel] Re: Can we enable some "-devel" modules from CBR in the EPEL8 buildroot?

[Kevin Fenzi]

On Thu, Feb 13, 2020 at 10:23:52AM +0100, Miro Hrončok wrote:
> Hello EPEL.
> 
> It seems that we have a python38-devel module in the RHEL 8.2 Beta Code
> Ready Builder repository. It has only one stream but it is not a default
> stream due to some technical limitations.
> 
> Can we please enable such stream in the EPEL8 buildroot trough some Ursa
> Major/Prime/... thing?

Nope. We don't ever sync or use betas... once it's released it should be
possible to use it however. 

> Is that technically possible on EPEL side?

Yeah, the way we have things now it should be possible. 

> Is that possible by policy?

I think so... 

kevin


signature.asc
Description: PGP signature
___
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

Fedora-Rawhide-20200214.n.1 compose check report

[Fedora compose checker]

No missing expected images.

Compose FAILS proposed Rawhide gating check!
26 of 43 required tests failed, 9 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 104/169 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-Rawhide-20200211.n.0):

ID: 521236  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/521236
ID: 521238  Test: x86_64 Server-dvd-iso server_cockpit_default **GATING**
URL: https://openqa.fedoraproject.org/tests/521238
ID: 521239  Test: x86_64 Server-dvd-iso base_service_manipulation
URL: https://openqa.fedoraproject.org/tests/521239
ID: 521241  Test: x86_64 Server-dvd-iso release_identification
URL: https://openqa.fedoraproject.org/tests/521241
ID: 521244  Test: x86_64 Server-dvd-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/521244
ID: 521250  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/521250
ID: 521251  Test: x86_64 Server-dvd-iso server_remote_logging_server
URL: https://openqa.fedoraproject.org/tests/521251
ID: 521252  Test: x86_64 Server-dvd-iso server_role_deploy_database_server 
**GATING**
URL: https://openqa.fedoraproject.org/tests/521252
ID: 521253  Test: x86_64 Server-dvd-iso base_system_logging **GATING**
URL: https://openqa.fedoraproject.org/tests/521253
ID: 521254  Test: x86_64 Server-dvd-iso base_reboot_unmount
URL: https://openqa.fedoraproject.org/tests/521254
ID: 521255  Test: x86_64 Server-dvd-iso base_update_cli **GATING**
URL: https://openqa.fedoraproject.org/tests/521255
ID: 521256  Test: x86_64 Server-dvd-iso server_filesystem_default
URL: https://openqa.fedoraproject.org/tests/521256
ID: 521259  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/521259
ID: 521261  Test: x86_64 Server-dvd-iso server_firewall_default **GATING**
URL: https://openqa.fedoraproject.org/tests/521261
ID: 521264  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/521264
ID: 521267  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/521267
ID: 521268  Test: x86_64 Server-dvd-iso server_database_client **GATING**
URL: https://openqa.fedoraproject.org/tests/521268
ID: 521269  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/521269
ID: 521270  Test: x86_64 Server-dvd-iso server_remote_logging_client
URL: https://openqa.fedoraproject.org/tests/521270
ID: 521271  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/521271
ID: 521316  Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal
URL: https://openqa.fedoraproject.org/tests/521316
ID: 521317  Test: x86_64 Silverblue-dvd_ostree-iso desktop_background
URL: https://openqa.fedoraproject.org/tests/521317
ID: 521319  Test: x86_64 Silverblue-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/521319
ID: 521321  Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/521321
ID: 521322  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud **GATING**
URL: https://openqa.fedoraproject.org/tests/521322

Old failures (same test failed in Fedora-Rawhide-20200211.n.0):

ID: 521232  Test: x86_64 Server-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/521232
ID: 521233  Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/521233
ID: 521247  Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation
URL: https://openqa.fedoraproject.org/tests/521247
ID: 521248  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/521248
ID: 521257  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/521257
ID: 521272  Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/521272
ID: 521273  Test: x86_64 Everything-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/521273
ID: 521274  Test: x86_64 Workstation-live-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/521274
ID: 521275  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/521275
ID: 521276  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/521276
ID: 521291  Test: x86_64 KDE-live-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/521291
ID: 521296  Test: x86_64 KDE-live-iso install_default@uefi **GATING**
URL: 

Re: Signal 4 (ILL) caught by ps in mock

[Christoph Junghans]

On Fri, Feb 14, 2020 at 10:37 AM Dan Horák  wrote:
>
> On Fri, 14 Feb 2020 10:28:10 -0700
> Christoph Junghans  wrote:
>
> > >>
> > >> In your case procps-ng package seems to be miscompiled (or run on
> > >> an incopatible hardware). I recommend getting a shell in the mock
> > >> enviroment (mock --shell) and investigeting whether the ps program
> > >> works there).
> > >
> > > Ok, I will try that and report back.
> > It is indeed broken in shell as well:
> >  sh-5.0# ps
> >
> > Signal 4 (ILL) caught by ps (3.3.15).
> > /usr/bin/ps:ps/display.c:66: please report this bug
> > Segmentation fault (core dumped)
>
> works (no crash) on my Power9 system, but it could be a P9 instruction
> sneaked into the binary and crashing on Power8 systems. I'll take a
> look, but if you could file a bug (with me in CC), it would be helpful.
just to make sure, I am running this in mock on the following system:
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
stepping : 9
cpu MHz : 3504.000
cache size : 4096 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm
constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq
pni pclmulqdq monitor ssse3 cx16 pcid sse4_1 sse4_2 movbe popcnt aes
xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single
pti fsgsbase avx2 invpcid rdseed clflushopt md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
swapgs itlb_multihit
bogomips : 7008.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

Christoph
>
>
> Dan
> ___
> 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



-- 
Christoph Junghans
Web: http://www.compphys.de
___
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

[Bug 1802968] EPEL8 Build

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2020-452e225c88 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-452e225c88

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

Schedule for Mondays's FESCo Meeting (2020-02-17)

[David Cantrell]

Schedule for Mondays's FESCo Meeting (2020-02-17)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2020-02-17 15:00 UTC'


Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

Python2 exception for mailman
https://pagure.io/fesco/issue/2312
APPROVED (+3,0,-0)

Nonresponsive maintainer: Steve Jenkins stevej
https://pagure.io/fesco/issue/2330
APPROVED (+5, 0, 0)

F32 Self-Contained Change: Update Haskell packages to Stackage LTS 14
https://pagure.io/fesco/issue/2334
APPROVED (+5,0,-0)

F32 Self-Contained Change: Python3-rdiff-backup
https://pagure.io/fesco/issue/2335
APPROVED (+5,0,-0)

Approve new Workstation WG governance document
https://pagure.io/fesco/issue/2336
APPROVED (+6,0,-0)

F32 Self-Contained Change: PostgreSQL 12
https://pagure.io/fesco/issue/2337
APPROVED (+3, 0, -0)

= New business =

#topic mingw CVEs aren't getting fixed
https://pagure.io/fesco/issue/2333

#topic Proposal to change ARM Release Blocking Criteria - Drop XFCE (32bit), 
Add Workstation(64bit) - 
https://fedoraproject.org/wiki/Changes/ARM_Release_Criteria_Changes
https://pagure.io/fesco/issue/2339

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: How to get proper nsswitch.conf?

[Michael Catanzaro]

On Thu, Feb 13, 2020 at 7:13 pm, Michael Catanzaro 
 wrote:

Why don't we have mymachines here?


Next question, I have:

passwd: sss files systemd
shadow: files sss
group: sss files systemd

The difference is that authselect doesn't write the shadow line [1], 
that one is coming from our glibc [2]. (glibc is already patched to 
enable sssd.) That inconsistency seems odd; shouldn't authselect be 
modifying the shadow line as well?


Then it also doesn't make sense that we put files before sss in half 
the lines, and sss before files in the other half.


[1] 
https://github.com/pbrezina/authselect/blob/master/profiles/sssd/nsswitch.conf
[2] 
https://src.fedoraproject.org/rpms/glibc/blob/master/f/glibc-fedora-nsswitch.patch


___
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

Re: Packaging of github cli?

[Joe Doss]

On 2/14/20 10:23 AM, Joe Doss wrote:
> On 2/14/20 9:56 AM, Richard Shaw wrote:
>> Anyone working on packaging github's CLI?
>>
>> https://github.com/cli/cli 
>>
>> I've never packaged a GO application before...
> 
> I have a spec I am working on right now. I will try to get it up on my
> Copr this weekend.

Well that was easier than I thought.

https://copr.fedorainfracloud.org/coprs/jdoss/github

$ dnf copr enable jdoss/github
$ dnf install github-cli

I will see what it takes to get this submitted for review this weekend.

Joe





-- 
Joe Doss
j...@solidadmin.com
___
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

Re: Any plans to include kotlin in Fedora

[Code Zombie]

So I suppose if someone takes on Gradle again,  it would be possible to add
Kotlin to Fedora. But overall, it seems rather complicated.

-Mehdi

On Thu, Feb 13, 2020, 19:03 Kevin Kofler  wrote:

> Dridi Boukelmoune wrote:
> > I think it boils down to having people to do the work, which is
> > probably not an easy task. I'm also assuming we'd need a more
> > up-to-date gradle package, which might not be a trivial task, and I
> > suspect that the build system is probably full of "Fedora violations"
> > between the need for an internet access, fetching pre-built
> > dependencies, bundling some dependencies...
>
> The main issue is that the dependency between Gradle and Kotlin is
> circular.
> Gradle is actually blocking, among other things, on Kotlin being packaged,
> and Kotlin is blocking on Gradle (which has been entirely retired because
> its maintainers were unable to keep it up to date). See the recent
> "Package
> uses Gradle (retired) to build: what to do?" thread.
>
> Gradle also has a circular dependency of the same kind on its main
> implementation language, Groovy.
>
> And of course, Gradle also has a trivial circular dependency on itself.
>
> And finally, there is also Scala code in Gradle now. I am not sure whether
> the latest version of Scala can be built without Gradle or whether the
> dependency is circular there too.
>
> Kevin Kofler
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
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

[Bug 1802968] EPEL8 Build

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Emmanuel Seyman  ---
I was convinced that I had done this a long time ago...

https://pagure.io/releng/fedora-scm-requests/issue/22178
https://pagure.io/releng/fedora-scm-requests/issue/22179

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

CPE Weekly: 2020-02-14

[Aoife Moloney]

# CPE Weekly: 2020-02-14

Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
can give.
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done.  Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.

## Fedora Updates

### Data Centre Move
By June 15th 2020, dedicated Fedora servers will have moved to a new
data centre in Northern Virginia.
If you want to read more, check out our post on hackmd:
https://hackmd.io/@Ap8CkTlpSfmjb44UGV-kWA/rJsk7A-QL

Here are some key dates and actions we need you to know:
* On 28th Feb, the old OpenStack instance in Fedora Cloud will be retired.
* Please reach out to Kevin before 25th Feb if you need to take action
for your instance if you are an instance owner. Here is the link to
the current status: https://pagure.io/fedora-infrastructure/issue/8614
* On 13th April, the CPE team will begin to ship servers to our new
data centre - this does not affect F32 distribution or release
* From March 1st, the CPE team will begin to build the Minimum Viable
Fedora infrastructure in the new datacenter
* Between May 20th - July 1st, we will be redirecting Fedora services
to run on the 'MVF' offering to facilitate the final part of the move
and allow for re-racking and testing
* By July 1st we hope to have BAU (business as usual) for Fedora infra

### AAA Replacement
This project is replacing our old existing fas (fedora account system)
with a new freeipa based system.
* Check out our blog on the teams progress to date!
* You can also see our jira board for tickets we are working on
* And we have an IRC channel - #fedora-AAA
* We are currently working on the FreeIPA API integration and the
folks at FreeIPA have been really helpful so far to work with

### CI/CD
* The team have been trying to get a local instance of Koji running this week
* They are investigating different algorithms that could help generate
the next release if a package based on its git history.
* Monitoring-gating is being deployed in OpenShift in staging

### Sustaining Team
* The team meets daily @ 1900 UTC in #fedora-admin on IRC
* The priority work is:
** Fedora 32
** Assisting with technical debt to facilitate the colo move
** mbbox upgrading
** CentOS CI OpenShift upgrading
* The team also have a public thread on knowledge sharing,
https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/thread/PY7H2N57NXU6MKZFNLYMKOL7N3NO6OBB/
so take a look!

## Docs
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/175
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/174
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/173
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/167
* Reviewed https://pagure.io/fedora-docs/install-guide/pull-request/40
* Also work underway on CentOS 8.1 docs


### Misc Updates
* The team are also working on creating Fedora infra application map -
stay tuned for the publication soon!
* keys.fedoraproject.org has been turned off
* boot.fedoraproject.org will be retired this week
* Certs have been changed to letsencrypt for fedorahosted/fedoracommunity
* Moved Koji calls to a backend task worker in Bodhi:
https://github.com/fedora-infra/bodhi/issues/3061
* kdreyer's playbook repo has been integrated:
https://pagure.io/koji-vagrant/pull-request/1
* Testing dist-git repo as a submodule has been added:
https://pagure.io/koji-vagrant/pull-request/2
* Ticket in Monitor-Gating has been reviewed:
https://pagure.io/fedora-ci/monitor-gating/pull-request/8


## CentOS Updates
### CentOS
* Tuning/adding more mirrorlist servers due to EC2/AWS change from last week
* Updates are really faster now for CentOS users in AWS/EC2 (more
than 100TiB of updated packages served internally with a 98.33% ratio
served from cache, so faster than ever)
* Moving data from CentOs Infra and switching to a new solution for
backup for infra:
* https://github.com/CentOS/ansible-role-centos-backup/
* https://github.com/CentOS/ansible-role-restic
* VDO 
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo)
* Investigating how to incorporate CentOS auth into the new AAA solution
* We'll need proper communication plan to ask everybody to get a
FAS account when we'll migrate


### CentOS Stream
* The CPE team are collaborating with the Packit team internally to
develop a workflow for contributor patches
* We are working towards demoing a contributor patch from submission
to end for Red Hat Summit in April!



As 

Re: Signal 4 (ILL) caught by ps in mock

[Dan Horák]

On Fri, 14 Feb 2020 10:28:10 -0700
Christoph Junghans  wrote:

> >>
> >> In your case procps-ng package seems to be miscompiled (or run on
> >> an incopatible hardware). I recommend getting a shell in the mock
> >> enviroment (mock --shell) and investigeting whether the ps program
> >> works there).
> >
> > Ok, I will try that and report back.
> It is indeed broken in shell as well:
>  sh-5.0# ps
> 
> Signal 4 (ILL) caught by ps (3.3.15).
> /usr/bin/ps:ps/display.c:66: please report this bug
> Segmentation fault (core dumped)

works (no crash) on my Power9 system, but it could be a P9 instruction
sneaked into the binary and crashing on Power8 systems. I'll take a
look, but if you could file a bug (with me in CC), it would be helpful.


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

Re: Signal 4 (ILL) caught by ps in mock

[Christoph Junghans]

On Fri, Feb 14, 2020 at 6:38 AM Christoph Junghans 
wrote:
>
>
>
> On Fri, Feb 14, 2020, 00:16 Petr Pisar  wrote:
>>
>> On Thu, Feb 13, 2020 at 07:48:22PM -0700, Christoph Junghans wrote:
>> > when running "mock -r fedora-rawhide-ppc64le --no-clean
>> > gromacs-2019.5-2.fc32.1.src.rpm"
>> > I am getting the following error:
>> > Signal 4 (ILL) caught by ps (3.3.15).
>> > /usr/bin/ps:ps/display.c:66: please report this bug
>> >
>> > I tried a couple of different src.rpm with the same result.
>> > This is mock 1.4.21 on f31.
>> >
>> > Has anybody else seen this?
>> >
>> Not exactly, but if you check Koji build history for gromacs package
>> . You
will
>> find out that the build failed during F32 mass rebuild
>>  on
ppc64le and
>> aarch64. The ppc64le failure is:
>
> That was exactly the reason why I was looking into building this ppc64le
;-) But unfortunately the Signal 4 shows up before it even gets to the
CMake part.
>
>>
>> -- Performing Test CXX_mvsx_COMPILE_WORKS - Failed
>> -- Flag was accepted, but it did not build test source (this could be
due to either the compiler or binutils)
>> -- Performing Test CXX_maltivec_mabi_altivec_FLAG_ACCEPTED
>> -- Performing Test CXX_maltivec_mabi_altivec_FLAG_ACCEPTED - Success
>> -- Performing Test CXX_maltivec_mabi_altivec_COMPILE_WORKS
>> -- Performing Test CXX_maltivec_mabi_altivec_COMPILE_WORKS - Failed
>> -- Flag was accepted, but it did not build test source (this could be
due to either the compiler or binutils)
>> -- Performing Test CXX_qarch_auto_qaltivec_FLAG_ACCEPTED
>> -- Performing Test CXX_qarch_auto_qaltivec_FLAG_ACCEPTED - Failed
>> -- Performing Test CXX_COMPILE_WORKS_WITHOUT_SPECIAL_FLAGS
>> -- Performing Test CXX_COMPILE_WORKS_WITHOUT_SPECIAL_FLAGS - Failed
>> -- Could not find any flag to build test source (this could be due to
either the compiler or binutils)
>> CMake Error at cmake/gmxManageSimd.cmake:51 (message):
>>   Cannot find IBM VSX compiler flag.  Use a newer compiler, or disable
SIMD
>>   support (slower).
>> Call Stack (most recent call first):
>>   cmake/gmxManageSimd.cmake:265
(gmx_give_fatal_error_when_simd_support_not_found)
>>   CMakeLists.txt:719 (gmx_manage_simd)
>> -- Configuring incomplete, errors occurred!
>> See also
"/builddir/build/BUILD/gromacs-2019.5/serial/CMakeFiles/CMakeOutput.log".
>> See also
"/builddir/build/BUILD/gromacs-2019.5/serial/CMakeFiles/CMakeError.log".
>>
>> Koschei history 
claims the
>> build started to fail with these changes
>> . It's probably a
triggered by
>> an upgrade of GCC to 10 version.
>>
>> SIGILL means the processor met an instruction it does not understand.
>>
>> In your case procps-ng package seems to be miscompiled (or run on an
>> incopatible hardware). I recommend getting a shell in the mock enviroment
>> (mock --shell) and investigeting whether the ps program works there).
>
> Ok, I will try that and report back.
It is indeed broken in shell as well:
 sh-5.0# ps

Signal 4 (ILL) caught by ps (3.3.15).
/usr/bin/ps:ps/display.c:66: please report this bug
Segmentation fault (core dumped)


>
>>
>> My gut feeling is that GCC 10 started to omit new instructions and your
>> hardware is not compatible with them. Can you reproduce it on one of
these
>> machines
>> <
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
>?
>
> Using these machines might be the easiest way the track down the gromacs
issue, thanks for the reminder that we have these resources.
>
> Christoph
>
>>
>> -- Petr
>> ___
>> 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



-- 
Christoph Junghans
Web: http://www.compphys.de
-- 
Christoph Junghans
Web: http://www.compphys.de
___
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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Marius Schwarz]

Am 14.02.20 um 17:57 schrieb Kevin Fenzi:
> On Fri, Feb 14, 2020 at 08:07:19AM -0500, Stephen John Smoogen wrote:
>> On Fri, 14 Feb 2020 at 06:21, Leigh Griffin  wrote:
>>
>>>
>>> On Fri, Feb 14, 2020 at 12:59 AM Artem Tim  wrote:
>>>
 Same here. I am waiting several minutes for every my action. This is very
 unproductive.

>>> Log it as a ticket and I can get the CPE folks to investigate it and see
>>> if there is an obvious problem that we can help with.
>>>
>>
>> for people having this issue the ticket is
>> https://pagure.io/fedora-infrastructure/issue/8648
>>
>> We need an idea of the geolocation you are coming from, traceroutes of
>> where you are going from and if possible in the browser any links etc which
>> are showing very slow (aka in Firefox right click inspect, and switch to
>> the network page and do a ^R on the koji.fedoraproject.org page)
> Also, it might help if people noted the exact time of day (UTC) they are
> accessing things?
>
> I suspect it may be backup slowness (which happens after 00:00UTC +-
> 2hour)

"NOW" aka. 14.2.2020 18:15 CET  the same pagecall to koji and firefox
rpm download where as smooth as they could be.

But, the koji test page from the ticket, had 4,5 seconds loadtime, which
was the first page i visited  in koji today.

I know this behaviour from my serverfarm, if the initial DNS resolver is
not responding and the timeout until the second is asked, kicks in.
As the server does no longer need to ask for an ip resolv on the second
visit (here firefox), it responds faster.

This does not explain the worst case download rate from yesterday, but
it can explain the results people have writte to the ticket for visiting
koji .

Best regards,
Marius


___
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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Marius Schwarz]

Am 14.02.20 um 17:57 schrieb Kevin Fenzi:
>
> Also, it might help if people noted the exact time of day (UTC) they are
> accessing things?
>
> I suspect it may be backup slowness (which happens after 00:00UTC +-
> 2hours)
>
it was around 12AM CET (+100), so the backup is off the hook.

unfortune for us firefox just said "yesterday" when i asked him for the
time :D

best regards,
Marius

___
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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Kevin Fenzi]

On Fri, Feb 14, 2020 at 08:07:19AM -0500, Stephen John Smoogen wrote:
> On Fri, 14 Feb 2020 at 06:21, Leigh Griffin  wrote:
> 
> >
> >
> > On Fri, Feb 14, 2020 at 12:59 AM Artem Tim  wrote:
> >
> >> Same here. I am waiting several minutes for every my action. This is very
> >> unproductive.
> >>
> >
> > Log it as a ticket and I can get the CPE folks to investigate it and see
> > if there is an obvious problem that we can help with.
> >
> 
> 
> for people having this issue the ticket is
> https://pagure.io/fedora-infrastructure/issue/8648
> 
> We need an idea of the geolocation you are coming from, traceroutes of
> where you are going from and if possible in the browser any links etc which
> are showing very slow (aka in Firefox right click inspect, and switch to
> the network page and do a ^R on the koji.fedoraproject.org page)

Also, it might help if people noted the exact time of day (UTC) they are
accessing things?

I suspect it may be backup slowness (which happens after 00:00UTC +-
2hours)

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

Re: koji build fails on arch armv7hl

[Kevin Fenzi]

On Fri, Feb 14, 2020 at 07:42:40AM -, Martin Gansser wrote:
> always same behaviour
> 
> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=41489282
> [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=41489285

This looks a lot like: 
https://pagure.io/releng/issue/9226

I'm hoping to backport the fix/patch there soon, we can see if it solves
your issue as well. 

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

Re: Packaging of github cli?

[Joe Doss]

On 2/14/20 9:56 AM, Richard Shaw wrote:
> Anyone working on packaging github's CLI?
> 
> https://github.com/cli/cli 
> 
> I've never packaged a GO application before...

I have a spec I am working on right now. I will try to get it up on my
Copr this weekend.

Joe




-- 
Joe Doss
j...@solidadmin.com
___
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

Packaging of github cli?

[Richard Shaw]

Anyone working on packaging github's CLI?

https://github.com/cli/cli

I've never packaged a GO application before...

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

[Bug 1803121] Impossible to install perl-Monitoring-Plugin

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||ppi...@redhat.com
 Resolution|--- |WORKSFORME
   Doc Type|--- |If docs needed, set a value
Last Closed||2020-02-14 14:51:02



--- Comment #1 from Petr Pisar  ---
I forgot to enable CodeReady Builder or PowerTools repository that is a
prerequisite for the EPEL repository
.

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

[Bug 1803121] New: Impossible to install perl-Monitoring-Plugin

[bugzilla]

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

Bug ID: 1803121
   Summary: Impossible to install perl-Monitoring-Plugin
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-Monitoring-Plugin
  Assignee: piotr1...@gmail.com
  Reporter: aurel...@bompard.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com,
perl-devel@lists.fedoraproject.org,
piotr1...@gmail.com
  Target Milestone: ---
Classification: Fedora



Description of problem:
On EPEL8, perl-Monitoring-Plugin can't be installed:

# dnf install perl-Monitoring-Plugin
Last metadata expiration check: 10:17:23 ago on Fri 14 Feb 2020 04:02:18 AM
GMT.
Error: 
 Problem: conflicting requests
  - nothing provides perl(Params::Validate) needed by
perl-Monitoring-Plugin-0.40-1.el8.noarch
  - nothing provides perl(Class::Accessor::Fast) needed by
perl-Monitoring-Plugin-0.40-1.el8.noarch
  - nothing provides perl(Class::Accessor) needed by
perl-Monitoring-Plugin-0.40-1.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use
not only best candidate packages)


Version-Release number of selected component (if applicable):
0.40-1.el8

How reproducible:
always

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

Re: Signal 4 (ILL) caught by ps in mock

[Christoph Junghans]

On Fri, Feb 14, 2020, 00:16 Petr Pisar  wrote:

> On Thu, Feb 13, 2020 at 07:48:22PM -0700, Christoph Junghans wrote:
> > when running "mock -r fedora-rawhide-ppc64le --no-clean
> > gromacs-2019.5-2.fc32.1.src.rpm"
> > I am getting the following error:
> > Signal 4 (ILL) caught by ps (3.3.15).
> > /usr/bin/ps:ps/display.c:66: please report this bug
> >
> > I tried a couple of different src.rpm with the same result.
> > This is mock 1.4.21 on f31.
> >
> > Has anybody else seen this?
> >
> Not exactly, but if you check Koji build history for gromacs package
> . You will
> find out that the build failed during F32 mass rebuild
>  on ppc64le
> and
> aarch64. The ppc64le failure is:
>
That was exactly the reason why I was looking into building this ppc64le
;-) But unfortunately the Signal 4 shows up before it even gets to the
CMake part.


> -- Performing Test CXX_mvsx_COMPILE_WORKS - Failed
> -- Flag was accepted, but it did not build test source (this could be due
> to either the compiler or binutils)
> -- Performing Test CXX_maltivec_mabi_altivec_FLAG_ACCEPTED
> -- Performing Test CXX_maltivec_mabi_altivec_FLAG_ACCEPTED - Success
> -- Performing Test CXX_maltivec_mabi_altivec_COMPILE_WORKS
> -- Performing Test CXX_maltivec_mabi_altivec_COMPILE_WORKS - Failed
> -- Flag was accepted, but it did not build test source (this could be due
> to either the compiler or binutils)
> -- Performing Test CXX_qarch_auto_qaltivec_FLAG_ACCEPTED
> -- Performing Test CXX_qarch_auto_qaltivec_FLAG_ACCEPTED - Failed
> -- Performing Test CXX_COMPILE_WORKS_WITHOUT_SPECIAL_FLAGS
> -- Performing Test CXX_COMPILE_WORKS_WITHOUT_SPECIAL_FLAGS - Failed
> -- Could not find any flag to build test source (this could be due to
> either the compiler or binutils)
> CMake Error at cmake/gmxManageSimd.cmake:51 (message):
>   Cannot find IBM VSX compiler flag.  Use a newer compiler, or disable SIMD
>   support (slower).
> Call Stack (most recent call first):
>   cmake/gmxManageSimd.cmake:265
> (gmx_give_fatal_error_when_simd_support_not_found)
>   CMakeLists.txt:719 (gmx_manage_simd)
> -- Configuring incomplete, errors occurred!
> See also
> "/builddir/build/BUILD/gromacs-2019.5/serial/CMakeFiles/CMakeOutput.log".
> See also
> "/builddir/build/BUILD/gromacs-2019.5/serial/CMakeFiles/CMakeError.log".
>
> Koschei history 
> claims the
> build started to fail with these changes
> . It's probably a
> triggered by
> an upgrade of GCC to 10 version.
>
> SIGILL means the processor met an instruction it does not understand.
>
> In your case procps-ng package seems to be miscompiled (or run on an
> incopatible hardware). I recommend getting a shell in the mock enviroment
> (mock --shell) and investigeting whether the ps program works there).
>
Ok, I will try that and report back.


> My gut feeling is that GCC 10 started to omit new instructions and your
> hardware is not compatible with them. Can you reproduce it on one of these
> machines
> <
> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
> >?

Using these machines might be the easiest way the track down the gromacs
issue, thanks for the reminder that we have these resources.

Christoph


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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Stephen John Smoogen]

On Fri, 14 Feb 2020 at 06:21, Leigh Griffin  wrote:

>
>
> On Fri, Feb 14, 2020 at 12:59 AM Artem Tim  wrote:
>
>> Same here. I am waiting several minutes for every my action. This is very
>> unproductive.
>>
>
> Log it as a ticket and I can get the CPE folks to investigate it and see
> if there is an obvious problem that we can help with.
>


for people having this issue the ticket is
https://pagure.io/fedora-infrastructure/issue/8648

We need an idea of the geolocation you are coming from, traceroutes of
where you are going from and if possible in the browser any links etc which
are showing very slow (aka in Firefox right click inspect, and switch to
the network page and do a ^R on the koji.fedoraproject.org page)




> ___
>> 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
>>
>
>
> --
>
> Leigh Griffin
>
> Engineering Manager
>
> Red Hat Waterford 
>
> Communications House
>
> Cork Road, Waterford City
>
> lgrif...@redhat.com
> M: +353877545162 IM: lgriffin
> @redhatjobs    redhatjobs
>  @redhatjobs
> 
> 
> ___
> 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
>


-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora-Cloud-31-20200214.0 compose check report

[Fedora compose checker]

No missing expected images.

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

Re: Package uses Gradle (retired) to build: what to do?

[Miro Hrončok]

On 14. 02. 20 12:45, Ankur Sinha wrote:

So, I'll focus on converting Gradle projects to Maven as the short-term
solution. I'll start a new thread for that to see how other maintainers
currently go about it.


Thanks for doing this! You rock.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Converting Gradle project files to Maven for packaging

[Ankur Sinha]

Hello,

Could the maintainers that have converted the Gradle project files to
Maven for packaging in Fedora please share how they've gone about it?

- is it a process of manually reading the Gradle files and writing Maven
  poms?

- is there an automated way of doing it (like this:
  https://github.com/tvaughan77/gradle2maven)?

Any other ways of simplifying this conversion and making it reliable so
we can use it in Fedora packages?

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

Re: Package uses Gradle (retired) to build: what to do?

[Ankur Sinha]

Hi Mario,

On Thu, Feb 13, 2020 11:39:31 +0100, Mario Torre wrote:
> The problem with Gradle as far as I'm aware is that it's a moving
> target. It insist on updating itself when you have an incompatible
> version and versions tend to break compatibility a lot, with new
> features added often, all of which makes impossible for a Linux
> distribution to keep up realiably.

Thanks for that.

So, basically, packaging and maintaining Gradle are both not easily
doable, certainly not in the man-power we have.

So, I'll focus on converting Gradle projects to Maven as the short-term
solution. I'll start a new thread for that to see how other maintainers
currently go about it.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

Re: infrastructure problem: koji and bodhi responding very slow / dl with 80kb/s

[Leigh Griffin]

On Fri, Feb 14, 2020 at 12:59 AM Artem Tim  wrote:

> Same here. I am waiting several minutes for every my action. This is very
> unproductive.
>

Log it as a ticket and I can get the CPE folks to investigate it and see if
there is an obvious problem that we can help with.

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


-- 

Leigh Griffin

Engineering Manager

Red Hat Waterford 

Communications House

Cork Road, Waterford City

lgrif...@redhat.com
M: +353877545162 IM: lgriffin
@redhatjobs    redhatjobs
 @redhatjobs


___
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

Failed to open file “build/gresource.xml”: No such file or directory

[Martin Gansser]

Hi,

tried to compile helia [1] on fc31, but this fails with this error messages:

rogram data/desktop.sh found: YES (/bin/sh 
/home/martin/rpmbuild/BUILD/Helia-14.0/data/desktop.sh)
Program data/gen-gres.sh found: YES (/bin/sh 
/home/martin/rpmbuild/BUILD/Helia-14.0/data/gen-gres.sh)
Found pkg-config: /usr/bin/pkg-config (1.6.3)
WARNING: glib-compile-resources failed to get dependencies for 
build/gresource.xml:
Failed to open file “build/gresource.xml”: No such file or directory

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/mesonbuild/mesonmain.py", line 129, in 
run
return options.run_func(options)
  File "/usr/lib/python3.7/site-packages/mesonbuild/msetup.py", line 245, in run
app.generate()


[1] https://martinkg.fedorapeople.org/Packages/test/helia.spec

How can i fix this ?

Regards
Martin
___
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

[Bug 1802999] New: Upgrade perl-Pegex to 0.75

[bugzilla]

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

Bug ID: 1802999
   Summary: Upgrade perl-Pegex to 0.75
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Pegex
  Assignee: g...@zimt.uni-siegen.de
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: g...@zimt.uni-siegen.de,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.74 version. Upstream released 0.75. 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

[Bug 1802968] EPEL8 Build

[bugzilla]

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

Timothée Floure  changed:

   What|Removed |Added

 Blocks||1756117




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1756117
[Bug 1756117] [RFE] shelldap build for epel8
-- 
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

[Bug 1802968] New: EPEL8 Build

[bugzilla]

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

Bug ID: 1802968
   Summary: EPEL8 Build
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Term-ReadLine-Gnu
  Assignee: emman...@seyman.fr
  Reporter: timothee.flo...@posteo.net
QA Contact: extras...@fedoraproject.org
CC: c...@wpi.edu, emman...@seyman.fr, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Hello,

Would it be possible to have an EPEL8 build of this package? Feel free to add
me as co-maintainer.

Thanks!

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