devel May 2020

devel@lists.fedoraproject.org

246 participants
396 discussions

Schedule for Monday's FESCo Meeting (2020-05-04)
by Fabio Valentini 02 May '20

02 May '20

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-05-04 15:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = F33 Self-Contained Change: Erlang 23 https://pagure.io/fesco/issue/2380 APPROVED (+4, 0, -0) = Followups = #topic #2382 2382 systemd default service exception for rpmdb-rebuild service https://pagure.io/fesco/issue/2382 No FESCo-approved exception is needed in this case. = New business = #topic #2372 F33 Self-contained Change: Network Time Security https://pagure.io/fesco/issue/2372 = 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.

1 0

Fedora-Cloud-31-20200502.0 compose check report
by Fedora compose checker 02 May '20

02 May '20

No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

Fedora-Cloud-30-20200502.0 compose check report
by Fedora compose checker 02 May '20

02 May '20

No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

[Test-Announce] 2020-05-04 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 01 May '20

01 May '20

# Fedora Quality Assurance Meeting # Date: 2020-05-04 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We didn't get through the whole agenda last week, so let's continue this week! 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. Proposals: backgrounds criterion, last-minute blocker process, service manipulation test case, user switching... 3. Test Day / community event status 4. Fedora 33 Change proposals 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-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.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-announce@lists.fedorapro…

1 0

ocaml-bisect-ppx and related updates
by Jerry James 01 May '20

01 May '20

I would like to update the ocaml-bisect-ppx package to its latest version, 2.3.1. It is currently on a post-1.4.1 git snapshot. The new version requires ocaml-ppx-tools-versioned >= 5.3.0. That requirement sets off a cascade of updates and rebuilds. I am BCCing all of the affected package maintainers. Here is what I would like to do, in the approximate order each would need to be done: ocaml-migrate-parsetree: update to version 1.7.0. I'm going to want this version for a later ocaml-tyxml update anyway, so we may as well do it now while we are rebuilding most of the affected packages for other reasons. ocaml-ppxfind: rebuild due to the ocaml-migrate-parsetree update; drop a patch needed to work with ocaml-migrate-parsetree <= 1.5.0. ocaml-ppx-tools-versioned: update to 5.3.0 ocaml-bisect-ppx: update to version 2.3.1 ocaml-ppx-deriving: rebuild due to the ocaml-migrate-parsetree update ocaml-sedlex: rebuild due to the ocaml-ppx-tools-versioned update ocaml-lwt: update to version 5.2.0 ocaml-curl: update to version 0.9.1 (it needs rebuilding anyway due to the ocaml-lwt update) ocaml-lwt-log: rebuild due to the ocaml-lwt update ocaml-ounit: rebuild due to the ocaml-lwt update ocaml-zmq: rebuild due to the ocaml-lwt update ocaml-lambda-term: update to version 2.0.3 (it needs rebuilding anyway due to the ocaml-bisect-ppx and ocaml-lwt updates) ocaml-markup: rebuild due to the ocaml-bisect-ppx update ocaml-tyxml: rebuild due to the ocaml-ppx-tools-versioned update utop: update to version 2.4.3 and BR ocaml-bisect-ppx-devel for the tests. I see that this package is orphaned. I'll take it if nobody else wants it. If any package maintainers object to this plan, please let me know. I can submit git pull requests if you prefer to do it that way, but in that case please do not start a build after merging as all of these builds will need to be done together. I have done all of the builds noted above in mock on an x86_64 machine with no problems. Regards, -- Jerry James http://www.jamezone.org/

3 13

Co-Maintainers wanted for python-lockfile EPEL branches
by Fabio Valentini 01 May '20

01 May '20

Hi everybody, I took over python-lockfile some time ago because it was FTBFS in fedora / orphaned at the time, but it's a dependency of some of my packages. However, I have zero interest in maintaining the EPEL branches of that package, because I have no packages in EPEL myself, and it seems I can't even figure out how to determine which EPEL packages require python*-lockfile. I have received two PRs for the epel7 branch already, and I don't even know if they're fine or not, so any help would be appreciated. If nobody steps up within the next two weeks, I will probably retire the epel7 and epel8 branches of python-lockfile. Fabio

5 7

Non-responsive maintainer check for hubbitus
by David Schwörer 01 May '20

01 May '20

Hi, Does anybody know how to contact Pavel Alexeev (fas: hubbitus) ? https://bugzilla.redhat.com/show_bug.cgi?id=1829117 Last comment on the most recent ticket on bugzilla: #1737349 2019-09-08 pahan #1215344 2016-01-01 pahan #1200038 2015-10-04 pahan #1130101 2014-09-09 pahan List of open bugs: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&… Kind Regards, David

2 1

simple-koji-ci fails with new patch
by Iñaki Ucar 01 May '20

01 May '20

Hi, I forked a package, changed the spec, added a patch and submitted a PR. Then simple-koji-ci fails because the patch wasn't included in the SRPM apparently [1]. Any idea why? Did I miss something? [1] https://src.fedoraproject.org/rpms/R/pull-request/3 Regards, -- Iñaki Úcar

2 2

WARNING: The pip package is not available, falling back to EasyInstall
by Luke Hinds 01 May '20

01 May '20

Hey All, Trying to update a package and getting failures over: ~~~ WARNING: The pip package is not available, falling back to EasyInstall for handling setup_requires/test_requires; this is deprecated and will be removed in a future version. Download error on https://pypi.org/simple/pbr/: [Errno -2] Name or service not known -- Some packages may not be found! Couldn't find index page for 'pbr' (maybe misspelled?) ~~~ Full stack trace in the build log here: https://kojipkgs.fedoraproject.org//work/tasks/292/43940292/build.log Has anyone seen this before, why would it not be able to find pip. I have python3-setuptools & python3-devel as BuildRequires, perhaps its path issue? Cheers, Luke

4 4

Fedora-Cloud-31-20200501.0 compose check report
by Fedora compose checker 01 May '20

01 May '20

No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel May 2020