devel June 2020

devel@lists.fedoraproject.org

303 participants
313 discussions

How to create a bodhi update from f32-kde tag?
by Robin Lee 15 Jun '20

15 Jun '20

Hi, I rebuilt some packages to the f32-kde tag for Qt 5.14.2. And after the new qt package being pushed to stable, I want to create an update for my packages. But bodhi request failed: $ bodhi updates new --type bugfix --notes 'Deepin rebuilds for Qt 5.14.2' --request testing --autotime --autokarma --suggest logout --user cheeselee deepin-kwin-0.1.0-7.fc32,deepin-qt-dbus-factory-5.0.1-5.fc32,dtkwidget-2.1.1-5.fc32,deepin-qt5integration-5.0.0-5.fc32,deepin-launcher-5.0.0-5.fc32,deepin-file-manager-5.0.0-7.fc32,deepin-editor-1.2.9.1-5.fc32 Cannot find release associated with build: deepin-kwin-0.1.0-7.fc32, tags: ['f32-kde'] So, which is the proper way to create to the update? -robin

3 2

Mailman3
by Lars Bjørndal 15 Jun '20

15 Jun '20

Hello list It seems that <https://lists.fedoraproject.org/> is managed by Mailman 3. In the repo, however, only the core package are available, and not the other components. What's the rationale behind that? Thanks in advance Lars

2 2

CPE Weekly: 2020-06-14
by Aoife Moloney 15 Jun '20

15 Jun '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-06-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. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ ## General Project Updates Please check out our updated initiative timetable for briefing in new projects to our team here:https://docs.fedoraproject.org/en-US/cpe/time_tables/ *Note: Initiatives are large pieces of work that require a team of people and weeks/months to complete. Please continue to open tickets in the normal way for bugs, issues, etc. Dont forget to view our taiga board to see the projects we are currently working on, what we have scoped and whats in our backlog https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null CPE Product Owner Office Hours * Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1 * Every second Tuesday @ 1500 UTC on #centos-meeting (next meeting 23rd June) * Meeting Logs * Fedora: https://meetbot.fedoraproject.org/teams/cpe_product_owner_office_hours/cpe_… * CentOS: https://www.centos.org/minutes/2020/June/centos-meeting.2020-06-09-15.00.lo… ## Fedora Updates ### Data Centre Move * The final Fedora hardware shipment is due to happen on Tuesday 16th June. * We expect the shipment to arrive in the new data centre the week beginning 22nd June and the team will begin bringing up services that are affected by the move. * A list of affected services is available here https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view * Please read the below email sent by kfenzi if you have not already done so: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… * Details on what this move may mean for you can be found here https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… * If an application is not working correctly at all, please check this list https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view before opening a ticket to make sure its not listed as being moved. If it is being moved, please wait a day or two, then try again. * Similarly, please be patient when opening tickets for service issues in general as we have now reached the critical point in this move and all of our sys-admins and wider teams will be assisting in the successful bringup of the reduced Fedora service and facilitation of the final hardware shipment and move. ### AAA Replacement * The team are working on the changing application code bases to use the new solution * They are also working on the CentOS account integration and the solution will see users be able to select the contributor agreements that are relative to their account. * They are also testing a script to use in data migration from the current FAS system to Noggin to allow for very little, if any, changes to the user * The team are also completing user documentation that includes a how-to migration guide for maintainers and a guide to help users understand the differences between Noggin and the current FAS option (issue #246 on board) * Please feel free to check out the team kanban board for more information on the features the team are working on and have already completed here https://github.com/orgs/fedora-infra/projects/6 ### Mbbox * Project Dashboard here https://github.com/fedora-infra/mbbox/projects/1 * Tasks completed in the project currently * MBS Backend CRD + documentation * MBS Frontend CRD - configuration and certificates * Draft of blog post about MBBox * Tasks underway currently * MBS Frontend CRD - deployment config and service * Staging environment required * MBox shared CRD ### Gitforge With the data centre move taking most of the teams focus this week, discussions with gitlab have been quiet. We are still discussing technical aspects of the project and these are tracked here: https://gitlab.com/gitlab-org/gitlab/-/issues/217350 We will keep you up to date with the developments as and when we have information to share and thank you for your patience. ## CentOS Updates ### CentOS * OCP4 staging cluster in progress * CentOS Linux 8.2.2004 content is in pre-release with more artifacts to come * There was also a recent CentOS AMA on Reddit, logs are here so check it out if you missed it https://www.reddit.com/r/CentOS/comments/gwnvd2/centos_ama/ ### CentOS Stream * The team have been working really hard to get package sources pushed to keep caught up with RHEL * We are also working on tooling for more push automation * And tooling for RealTime and other Variants are coming in Stream soon As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week ahead! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Intent to retire python-ufolib
by Athos Ribeiro 14 Jun '20

14 Jun '20

The upstream project has been deprecated upstream in favor of shipping ufolib2 (available as python3-ufolib2) as part of the fonttools project (python-fonttools). I will retire python-ufolib at some point during this week, unless someone raises any concerns for not proceeding in this manner.

1 0

Package prepared for review and request for sponsorship
by 西木野羰基 14 Jun '20

14 Jun '20

Hello all! With some suggestions given, I think my package is ready for review. Review request itself can be found here. [0] This is my first package, so I need a sponsor for this. For potential sponsors, you can see my pull request [1-3], all of them are prepare for a update. Thanks. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1846175 [1] https://src.fedoraproject.org/rpms/mkdocs/pull-request/1 [2] https://src.fedoraproject.org/rpms/python-lunr/pull-request/1 [3] https://src.fedoraproject.org/rpms/kcm-fcitx/pull-request/1

1 0

It seems that gdb cannot find debuginfo on f32
by Barry Scott 14 Jun '20

14 Jun '20

I'm trying to debug a segv in PyQt5 and I hit a problem with gdb not finding debug info in f32. I have installed python3.8 debug info. $ dnf list installed | grep debug | grep python3 python3-debuginfo.x86_64 3.8.3-1.fc32 @updates-debuginfo python3-debugsource.x86_64 3.8.3-1.fc32 @updates-debuginfo python3-qt5-base-debuginfo.x86_64 5.13.2-5.fc32 @fedora-debuginfo But still gdb says it cannot find the debuginfos. $ gdb /usr/bin/python3.8 GNU gdb (GDB) Fedora 9.1-5.fc32 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/python3.8... Reading symbols from .gnu_debugdata for /usr/bin/python3.8... (No debugging symbols found in .gnu_debugdata for /usr/bin/python3.8) Missing separate debuginfos, use: dnf debuginfo-install python3-3.8.3-1.fc32.x86_64 (gdb) Am I doing something wrong? Should I raise a BZ? Barry

2 2

RFC: Automatically generated BuildRequires for maven-based Java projects
by Fabio Valentini 14 Jun '20

14 Jun '20

Good $LOCAL_TIME_OF_DAY, I've been working on experimental support for automatically generating BuildRequires for maven-based Java projects, and it's now available for testing in rawhide (and in fedora 32, for local testing). There's no "macro support" for this yet, because it's still work-in-progress, though when it proves useful support for it might eventually get merged into the Java packaging macros directly. The good new is: it should basically "just work" if your package isn't doing anything weird, but this is Java we're talking about, so there's at least three limitations I can think of right now (the bad news): 1. no built-in blacklist for irrelevant plugins yet (e.g. maven-release-plugin) 2. no support for different profiles yet 3. no support for plugins that add additional dependencies in their configuration There are workarounds for the first two limitations: 1. It's pretty easy to just disable those plugins manually in %prep with "%pom_remove_plugin :maven-foo-plugin". 2. If you know ahead of time which submodules will get activated (e.g. based on a previous package build), just specify those modules on the mvn-genbr command line instead of letting mvn-genbr fail to find them. 3. just continue to specify those non-discoverable dependencies manually Usage in .spec files should be pretty simple, and similar to how other tools handle generated BuildRequires: - replace all java / "mvn(foo:bar)" dependencies with "BuildRequires: mvn-genbr", - but keep "BuildRequires: maven-local" (this is not automatically generated). - keep your "pom.xml" modifications in %prep, as usual (e.g. removing unnecessary maven plugins, changing dependencies, modifying XML with XPath queries) - add the following section to your .spec after %prep: %generate_buildrequires mvn-genbr -t . If you're not running the test suite (%mvn_build -f), then drop the -t / --with-tests flag. If the root directory of the maven project is not the toplevel directory, specify the name of the root directory / directories instead of "." (mvn-genbr accepts multiple arguments for this purpose. use "mvn-genbr --help" for current list of command line options). If you want to check out what automatic dependencies mvn-genbr will generate for your package, you can try it without kicking off a package build by dnf-installing "mvn-genbr" (available fedora 32+), and running it with the same arguments as in your .spec file in the source directory that's generated and processed by "fedpkg prep". Comparisons between the generated dependency lists and those that were curated "manually" would be of interest, especially for bug reports :) Since this is still work-in-progress (though it works for a few simple packages I tried it with), please feel free to report your experiences, and - more importantly - open issues when the tool either crashes (it shouldn't, since the POM parser successfully parsed all non-broken maven project files from all fedora packages), or when it generates too many (not that problematic) or too few (not so good) dependencies. The code for the POM parser and mvn-genbr lives in this project on pagure: https://pagure.io/ironthree/pommes Go forth and break my code! Fabio

2 1

Unretire python-sqlalchemy_schemadisplay
by Mattia Verga 14 Jun '20

14 Jun '20

I'd like to unretire python-sqlalchemy_schemadisplay since it's needed by Bodhi to produce its documentation. I know upstream isn't very active, but the only alternative I see is eralchemy, which is even less maintained... Any objections/alternative suggestions? Mattia

1 0

Review swap - antimicroX
by Gombos Gergely 14 Jun '20

14 Jun '20

Hi, I'm kind of a newbie packager, waiting for a review for: antimicroX - Graphical program used to map keyboard buttons and mouse controls to a gamepad https://bugzilla.redhat.com/show_bug.cgi?id=1844850 (A maintained fork of the now unmaintained and orphaned antimicro package.) It's a rather simple specfile, and a very useful piece of software for e.g. retro gaming. I'm not an expert at reviewing either, but I'm happy to take a look at some simpler packages in exchange. Thanks! Best regards, Greg (FAS: gombosg)

2 1

how to correctly remove a subpackage ?
by josef radinger 13 Jun '20

13 Jun '20

hi, i would like to know how to remove a subpackage from the distribution. eg. there is a package X, which is in rawhide with version 1 and has subpackages a and b. we have X-1 X-a-1 (dependent on X and Y) X-b-1 (dependent on X) now the dependency Y is removed from rawhide and i create a new version 2 of package X without the dependency on Y and thus no subpackage X-a- 1. now we have: X-2 (which obsoletes X-a-1) X-b-2 questions: a) do i have to add X-a-1 to fedora-obsolete-packages? b) is there a difference between rawhide and other branches? the docs - at least those i found (mainly https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life#Obsol… )- are not too clear for me in that regard. besides: we should have a search-engine on docs.fedoraproject.org or even better over all our websites. google helps, but is not that great when it comes to not track users. yours josef

3 3

← Newer
1
...
16
17
18
19
20
21
22
...
32
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2020