Re: Macros in side-tag
Hi Vít, Vít Ondruch writes: > Hi, > > Koji has grown new functionality to enable setting macros in side-tag: > > https://pagure.io/releng/issue/11254 > > I have asked FeSCo to approve to use them: > > https://pagure.io/fesco/issue/3046 > > My immediate use case is to improve the package bootstrapping > experience. This is great news, thank you for working on this! Although I personally have no immediate use for this, I believe this could be of great help for release-engineering and packagers performing large scale experiments. Setting macros in side-tags gives is one of the key features that the open build service provides via the so-called project-config. This would allow simpler experimentation to globally toggle build flags, build options or develop new macros entirely (although COPR might be a better fit in a few instances). Cheers, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
> I've been actually using dnf5 daily and while it's a little rough > around the edges it seems usable enough. I agree, I would like to see dnf5 staying in rawhide. Otherwise I don't think it will receive sufficient testing. > (1) The allow_vendor_change option makes things strange. I think this > feature should be turned off (ie True) until it is fixed properly. > https://github.com/rpm-software-management/dnf5/issues/722 (I believe this happened upstream already. :) Jens ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: IBus 1.5.29 (System-Wide)
Sorry, I missed the reply. Currently the default input method is the Qt IBus IM module by setting QT_IM_MODULE=ibus environment variable with imsettings module in Plasma Wayland and this Change is to make another IBus Wayland IM module and users switch the input method by manual using systemsettings5 utility because the new module will be under the testing in Fedora 39. I'd like to make another Change to change the system default change in Fedora 40. So this change would be enough as Self-Contained for Fedora 39. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: DNF5-5.0.1 has a stable API
> On Mon, 24 Jul 2023 at 13:10, James Ralston Personally I would have preferred to call this a new tool versus trying to > use dnf name still. It makes it clearer that the break is going to happen. How about going back to yum? The yum name never completely went away in RHEL docs and still lingers in things like yum.repos.d ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, 2023-07-27 at 23:04 +0100, Naheem Zaffar wrote: > On Thu, 27 Jul 2023, 21:23 Kevin Fenzi, wrote: > > > On Thu, Jul 27, 2023 at 02:54:13PM -0400, DJ Delorie wrote: > > > Samantha Bueno writes: > > > > We've gone ahead and decided not to replace DNF with DNF05 in Fedora > > > > 39 and, perhaps notably, Fedora 40 as well. > > > > > > For those of us who upgraded to DNF05 in rawhide to test it, is there a > > > quick reference for our paths forward? Er, backward? I upgraded at the > > > wrong time and spent half a day recovering my system, I'd rather avoid > > > that if I have to go back to DNF04... > > > > I would expect a revert back to where /usr/bin/dnf is dnf4 (but > > hopefully dnf5 is still available/seperate). > > > > Dont they have different/incompatible database formats/locations where > dnf4 does not track updates via dnf5 and vice versa? Sure, but that's not really a problem. We've had both available in parallel for quite a long time now. The situation Kevin describes (/usr/bin/dnf is dnf4, you can install dnf5 and get /usr/bin/dnf5 alongside it if you like) is what was the state in Rawhide for several months before we flipped it so dnf5 provided /usr/bin/dnf , and is still the state in F38. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Retiring python-pytest-flake8
On 27-07-2023 22:57, Sandro wrote:
On 27-07-2023 21:02, Michel Alexandre Salim wrote:
Thanks Miro!
On Thu, 2023-07-27 at 19:28 +0200, Miro Hrončok wrote:
On 27. 07. 23 18:26, Michel Alexandre Salim wrote:
⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide --
enablerepo=fedora-source --whatrequires python-pytest-flake8
Always use the actual binary package name for queries like this, as
only the
actual package name will show all dependencies that happen to require
a
differetn virtual provide:
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-
pytest-flake8
cvise-0:2.4.0-3.fc36.src
python-cssutils-0:2.6.0-2.fc38.src
python-nashpy-0:0.0.37-1.fc39.src
python-pyunicorn-0:0.6.1-12.fc38.src
nashpy is fixed, but I'll take a look at the others. Given the disttags
they look like they FTBFSed anyway (cvise is fc36, ouch!)
I can take care of pyunicorn. It looks simple enough.
Consider pyunicorn fixed. The package itself is still broken, but that's
numpy related not due to the removal of pytest-flake8.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Fri, Jul 28, 2023 at 12:05 AM Naheem Zaffar wrote: > > > > On Thu, 27 Jul 2023, 21:23 Kevin Fenzi, wrote: >> >> On Thu, Jul 27, 2023 at 02:54:13PM -0400, DJ Delorie wrote: >> > Samantha Bueno writes: >> > > We've gone ahead and decided not to replace DNF with DNF05 in Fedora >> > > 39 and, perhaps notably, Fedora 40 as well. >> > >> > For those of us who upgraded to DNF05 in rawhide to test it, is there a >> > quick reference for our paths forward? Er, backward? I upgraded at the >> > wrong time and spent half a day recovering my system, I'd rather avoid >> > that if I have to go back to DNF04... >> >> I would expect a revert back to where /usr/bin/dnf is dnf4 (but >> hopefully dnf5 is still available/seperate). > > > > Dont they have different/incompatible database formats/locations where dnf4 > does not track updates via dnf5 and vice versa? As far as I know, the database that keeps transaction history and the database that keeps track of why packages are installed have different formats. But neither of these should affect normal operation (installing / updating packages etc.). Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, 27 Jul 2023, 21:23 Kevin Fenzi, wrote: > On Thu, Jul 27, 2023 at 02:54:13PM -0400, DJ Delorie wrote: > > Samantha Bueno writes: > > > We've gone ahead and decided not to replace DNF with DNF05 in Fedora > > > 39 and, perhaps notably, Fedora 40 as well. > > > > For those of us who upgraded to DNF05 in rawhide to test it, is there a > > quick reference for our paths forward? Er, backward? I upgraded at the > > wrong time and spent half a day recovering my system, I'd rather avoid > > that if I have to go back to DNF04... > > I would expect a revert back to where /usr/bin/dnf is dnf4 (but > hopefully dnf5 is still available/seperate). Dont they have different/incompatible database formats/locations where dnf4 does not track updates via dnf5 and vice versa? > > > Hopefully that can happen before branching in a few weeks. > > kevin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, Jul 27, 2023 at 2:23 PM Kevin Fenzi wrote: > On Thu, Jul 27, 2023 at 02:54:13PM -0400, DJ Delorie wrote: > > Samantha Bueno writes: > > > We've gone ahead and decided not to replace DNF with DNF05 in Fedora > > > 39 and, perhaps notably, Fedora 40 as well. > > > > For those of us who upgraded to DNF05 in rawhide to test it, is there a > > quick reference for our paths forward? Er, backward? I upgraded at the > > wrong time and spent half a day recovering my system, I'd rather avoid > > that if I have to go back to DNF04... > > I would expect a revert back to where /usr/bin/dnf is dnf4 (but > hopefully dnf5 is still available/seperate). > > Hopefully that can happen before branching in a few weeks. > With the intention of carrying two versions side by side for a while longer, does it make sense to use alternatives for this? It might be more work than it's worth. However, it would be nice to have `dnf4`, `dnf5` and `dnf` commands all available with the default easily configurable. -- Jonathan Steffan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Retiring python-pytest-flake8
On 27-07-2023 21:02, Michel Alexandre Salim wrote:
Thanks Miro!
On Thu, 2023-07-27 at 19:28 +0200, Miro Hrončok wrote:
On 27. 07. 23 18:26, Michel Alexandre Salim wrote:
⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide --
enablerepo=fedora-source --whatrequires python-pytest-flake8
Always use the actual binary package name for queries like this, as
only the
actual package name will show all dependencies that happen to require
a
differetn virtual provide:
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-
pytest-flake8
cvise-0:2.4.0-3.fc36.src
python-cssutils-0:2.6.0-2.fc38.src
python-nashpy-0:0.0.37-1.fc39.src
python-pyunicorn-0:0.6.1-12.fc38.src
nashpy is fixed, but I'll take a look at the others. Given the disttags
they look like they FTBFSed anyway (cvise is fc36, ouch!)
I can take care of pyunicorn. It looks simple enough.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, Jul 27, 2023 at 02:54:13PM -0400, DJ Delorie wrote: > Samantha Bueno writes: > > We've gone ahead and decided not to replace DNF with DNF05 in Fedora > > 39 and, perhaps notably, Fedora 40 as well. > > For those of us who upgraded to DNF05 in rawhide to test it, is there a > quick reference for our paths forward? Er, backward? I upgraded at the > wrong time and spent half a day recovering my system, I'd rather avoid > that if I have to go back to DNF04... I would expect a revert back to where /usr/bin/dnf is dnf4 (but hopefully dnf5 is still available/seperate). Hopefully that can happen before branching in a few weeks. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, 2023-07-27 at 21:21 +0200, Pierre-Yves Chibon wrote: > On Thu, Jul 27, 2023 at 11:27:37AM -0700, Kevin Fenzi wrote: > > On Thu, Jul 27, 2023 at 08:41:42AM -0400, Samantha Bueno wrote: > > > I want to close on a positive note and commend my team for the incredible > > > amount of hard work they have poured into this project thus far, as well > > > as > > > people we've been collaborating with and who have been testing and > > > offering > > > feedback. We have more test days planned and will continue to operate > > > transparently as we proceed through development. > > > > I wanted to repeat what I noted in the FESCo meeting: > > > > I'd like to also thank the dnf5 team. It can't be easy to retarget > > something you > > were working on so long. My thanks for being honest about the status and > > realistic about timeframes and needed work. Kudos! > > I'd like to second that, these decisions are never easy to take and thank you > for having the courage of making it. Me too, thanks to Samantha and the team. There's nothing to be ashamed of here! It's fine to take our time, and this was a good decision well made. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, Jul 27, 2023 at 11:27:37AM -0700, Kevin Fenzi wrote: > On Thu, Jul 27, 2023 at 08:41:42AM -0400, Samantha Bueno wrote: > > I want to close on a positive note and commend my team for the incredible > > amount of hard work they have poured into this project thus far, as well as > > people we've been collaborating with and who have been testing and offering > > feedback. We have more test days planned and will continue to operate > > transparently as we proceed through development. > > I wanted to repeat what I noted in the FESCo meeting: > > I'd like to also thank the dnf5 team. It can't be easy to retarget something > you > were working on so long. My thanks for being honest about the status and > realistic about timeframes and needed work. Kudos! I'd like to second that, these decisions are never easy to take and thank you for having the courage of making it. Pierre signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Retiring python-pytest-flake8
Thanks Miro!
On Thu, 2023-07-27 at 19:28 +0200, Miro Hrončok wrote:
> On 27. 07. 23 18:26, Michel Alexandre Salim wrote:
> > ⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide --
> > enablerepo=fedora-source --whatrequires python-pytest-flake8
>
> Always use the actual binary package name for queries like this, as
> only the
> actual package name will show all dependencies that happen to require
> a
> differetn virtual provide:
>
> $ repoquery -q --repo=rawhide{,-source} --whatrequires python3-
> pytest-flake8
> cvise-0:2.4.0-3.fc36.src
> python-cssutils-0:2.6.0-2.fc38.src
> python-nashpy-0:0.0.37-1.fc39.src
> python-pyunicorn-0:0.6.1-12.fc38.src
>
>
nashpy is fixed, but I'll take a look at the others. Given the disttags
they look like they FTBFSed anyway (cvise is fc36, ouch!)
I won't retire pytest-flake8 until after checking the dependents, just
in case we still need to hotfix it (though my preference will be to
drop it as it should never have been run)
Best,
--
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
Samantha Bueno writes: > We've gone ahead and decided not to replace DNF with DNF05 in Fedora > 39 and, perhaps notably, Fedora 40 as well. For those of us who upgraded to DNF05 in rawhide to test it, is there a quick reference for our paths forward? Er, backward? I upgraded at the wrong time and spent half a day recovering my system, I'd rather avoid that if I have to go back to DNF04... ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Update on DNF05 in Fedora
On Thu, Jul 27, 2023 at 08:41:42AM -0400, Samantha Bueno wrote: > I want to close on a positive note and commend my team for the incredible > amount of hard work they have poured into this project thus far, as well as > people we've been collaborating with and who have been testing and offering > feedback. We have more test days planned and will continue to operate > transparently as we proceed through development. I wanted to repeat what I noted in the FESCo meeting: I'd like to also thank the dnf5 team. It can't be easy to retarget something you were working on so long. My thanks for being honest about the status and realistic about timeframes and needed work. Kudos! Thanks. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Summary/Minutes from today's FESCo Meeting (2023-07-27)
On 7/27/23 11:03, Tom Stellard wrote: = #fedora-meeting-2: FESCO (2023-07-27) = Meeting started by tstellar at 17:00:28 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2023-07-27/fesco.2023-07-27-17.00.log.html . Meeting summary --- * init process (tstellar, 17:01:13) * #3039 RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism (tstellar, 17:04:33) * AGREED: APPROVED(+7,0,-0) The switch to DNF5 will be postponed (likely to Fedora 41, to be determined by the Change Owners) and reverted in Rawhide for the time being (i.e. dnf 4 will provide /usr/bin/dnf again). (tstellar, 17:27:21) * #3035 Change: Build JDKs once, repack everywhere (tstellar, 17:28:30) * AGREED: APPROVED(+5,0,-3) (tstellar, 17:43:10) * Next week's chair (tstellar, 17:45:22) * ACTION: decathorpe will chair next meeting (tstellar, 17:48:46) We also decided to cancel next week's meeting due to Flock, so the next meeting will be August 10. -Tom * Open Floor (tstellar, 17:48:56) * ACTION: nirik will update fesco meeting location in the calendar. (tstellar, 17:59:50) Meeting ended at 18:01:04 UTC. Action Items * decathorpe will chair next meeting * nirik will update fesco meeting location in the calendar. Action Items, by person --- * decathorpe * decathorpe will chair next meeting * nirik * nirik will update fesco meeting location in the calendar. * **UNASSIGNED** * (none) People Present (lines said) --- * tstellar (53) * decathorpe (37) * nirik (32) * mhroncok (29) * dcantrell (18) * zodbot (16) * Eighth_Doctor (14) * jmracek (12) * sbueno (5) * sgallagh (4) * salimma (1) * zbyszek (0) * mhayden (0) * Conan_Kudo (0) * Pharaoh_Atem (0) * Son_Goku (0) * King_InuYasha (0) * Sir_Gallantmon (0) Generated by `MeetBot`_ 0.4 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Summary/Minutes from today's FESCo Meeting (2023-07-27)
= #fedora-meeting-2: FESCO (2023-07-27) = Meeting started by tstellar at 17:00:28 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2023-07-27/fesco.2023-07-27-17.00.log.html . Meeting summary --- * init process (tstellar, 17:01:13) * #3039 RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism (tstellar, 17:04:33) * AGREED: APPROVED(+7,0,-0) The switch to DNF5 will be postponed (likely to Fedora 41, to be determined by the Change Owners) and reverted in Rawhide for the time being (i.e. dnf 4 will provide /usr/bin/dnf again). (tstellar, 17:27:21) * #3035 Change: Build JDKs once, repack everywhere (tstellar, 17:28:30) * AGREED: APPROVED(+5,0,-3) (tstellar, 17:43:10) * Next week's chair (tstellar, 17:45:22) * ACTION: decathorpe will chair next meeting (tstellar, 17:48:46) * Open Floor (tstellar, 17:48:56) * ACTION: nirik will update fesco meeting location in the calendar. (tstellar, 17:59:50) Meeting ended at 18:01:04 UTC. Action Items * decathorpe will chair next meeting * nirik will update fesco meeting location in the calendar. Action Items, by person --- * decathorpe * decathorpe will chair next meeting * nirik * nirik will update fesco meeting location in the calendar. * **UNASSIGNED** * (none) People Present (lines said) --- * tstellar (53) * decathorpe (37) * nirik (32) * mhroncok (29) * dcantrell (18) * zodbot (16) * Eighth_Doctor (14) * jmracek (12) * sbueno (5) * sgallagh (4) * salimma (1) * zbyszek (0) * mhayden (0) * Conan_Kudo (0) * Pharaoh_Atem (0) * Son_Goku (0) * King_InuYasha (0) * Sir_Gallantmon (0) Generated by `MeetBot`_ 0.4 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Retiring python-pytest-flake8
On 27. 07. 23 18:26, Michel Alexandre Salim wrote:
⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide
--enablerepo=fedora-source --whatrequires python-pytest-flake8
Always use the actual binary package name for queries like this, as only the
actual package name will show all dependencies that happen to require a
differetn virtual provide:
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-pytest-flake8
cvise-0:2.4.0-3.fc36.src
python-cssutils-0:2.6.0-2.fc38.src
python-nashpy-0:0.0.37-1.fc39.src
python-pyunicorn-0:0.6.1-12.fc38.src
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Retiring python-pytest-flake8
On Thu, Jul 27, 2023 at 6:26 PM Michel Alexandre Salim wrote: > > Dear all, > > We are retiring python-pytest-flake8. > > It FTBFS: https://bugzilla.redhat.com/show_bug.cgi?id=2226304 > > and abandoned upstream: https://github.com/tholo/pytest-flake8/issues/98 > (some suggest using ruff instead) ... ruff, you say? /me gets cold shivers It's still at a pre-pre-release stage and right now has dependencies on git snapshots, downstream forks, and / or forks copy-pasted into their repo ... So I don't think it can (or should) be packaged at this stage. Maybe once the project matures and stabilizes, but certainly not now. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Retiring python-pytest-flake8
Dear all, We are retiring python-pytest-flake8. It FTBFS: https://bugzilla.redhat.com/show_bug.cgi?id=2226304 and abandoned upstream: https://github.com/tholo/pytest-flake8/issues/98 (some suggest using ruff instead) and in addition, running linters in %check is discouraged anyway: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_linters I did a dependency analysis a couple of days ago and only python-nashpy popped up, this was a leftover because of manually specified test dependencies since fixed in https://src.fedoraproject.org/rpms/python-nashpy/pull-request/2 And there are no more dependents. If I miss anything in this query -- your package is FTBFS already anyway after the mass rebuild, so please remove the dependency. ``` michel in fedora/reviews/other took 13m39s ⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide --enablerepo=fedora-source --whatrequires python-pytest-flake8 Fedora rawhide - x86_64 19 MB/s | 73 MB 00:03 Fedora rawhide - Source 7.2 MB/s | 8.1 MB 00:01 Fedora rawhide - x86_64 - Updates 1.2 MB/s | 1.7 MB 00:01 Last metadata expiration check: 0:00:01 ago on Thu Jul 27 11:21:52 2023. michel in fedora/reviews/other took 37s ⬢ [fedora-toolbox:38] ❯ ``` Best regards, -- Michel Alexandre Salim identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: DNF5-5.0.1 has a stable API
On Wed, Jul 26, 2023 at 09:05:08AM +0200, Miroslav Suchý wrote: > Dne 24. 07. 23 v 22:43 Chuck Anderson napsal(a): > > I propose "qzw". It's so easy to type on a qwerty keyboard layout. > > English qwerty layout. Because on Czech layout "z" and "y" are swappe. :) Oh yeah, we need to find a better name that takes equal effort for trained touch-typists on all keyboard layouts. Gotta work that left pinky finger. (Can you tell I'm still bitter because of the yum --> dnf rename?) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Update on DNF05 in Fedora
Greetings, I'm here in my capacity as manager of the DNF team. Probably everyone who reads this mailing list is aware that DNF05 has been in development for a while and that we planned to introduce it as the default (replacing DNF) with the upcoming Fedora 39 release. I'm sure some of you have also seen the recent FESCo ticket and discussion concerning its readiness and whether or not to invoke the contingency plan for shipping DNF05 in F39, since there is still a substantial amount of functionality lacking. We've gone ahead and decided not to replace DNF with DNF05 in Fedora 39 and, perhaps notably, Fedora 40 as well. Fedora 41 is the safest option at the moment. With a core system component like DNF, it's crucial that we provide a stable, complete, and thoroughly tested experience to everyone. In its current state, we would not be able to deliver that. With more time, we'll be able to regain our footing and do things properly. Furthermore, this team, which has worked tirelessly over these last several months especially, will be able to avoid burnout. This was not an easy decision to make, but it is the best decision for the team, for this project, and for Fedora. I want to close on a positive note and commend my team for the incredible amount of hard work they have poured into this project thus far, as well as people we've been collaborating with and who have been testing and offering feedback. We have more test days planned and will continue to operate transparently as we proceed through development. Thanks, -- Samantha N. Bueno (she/hers) Manager, Linux Engineering Red Hat, Inc | Boston, MA ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2023-07-28 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10531/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Macros in side-tag
Dne 26. 07. 23 v 15:57 Zbigniew Jędrzejewski-Szmek napsal(a):
On Wed, Jul 26, 2023 at 03:45:32PM +0200, Vít Ondruch wrote:
Dne 26. 07. 23 v 13:13 Zbigniew Jędrzejewski-Szmek napsal(a):
On Wed, Jul 26, 2023 at 12:30:00PM +0200, Vít Ondruch wrote:
Hi,
Koji has grown new functionality to enable setting macros in side-tag:
https://pagure.io/releng/issue/11254
I have asked FeSCo to approve to use them:
https://pagure.io/fesco/issue/3046
My immediate use case is to improve the package bootstrapping experience.
I made a proposal in the ticket to allowlist %_with_bootstrap.
I was wondering though: what about other macros? Would/should users
set %_with_tests or other macros in this way?
Thinking about this, we could probably update `%{dist}` macro and leverage
similar mechanism for mass rebuilds. Saving all the commits which don't
provide too much value IMHO.
Commits for mess rebuilds are already empty (when %autorelease and
%autochangelog are used). But I think we do want the information that
the package was rebuilt for the mess rebuild to be present in the
changelog, so we need the empty commit.
If the information was present in NVR, it could be enough (and I don't
think additional `.1` in dist tag would be enough for this case, more
likely something like `~massrebuild.2023.1` would be needed). I think
the information about mass rebuild is not of historical importance.
Seeing such entries in e.g. RHEL is quite questionable (being part of
changelog or git log does not necessarily make a difference).
But this might be matter of personal preferences.
In any case, I'm not going to pursue anything like this any time soon ;)
Vít
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Macros in side-tag
Dne 26. 07. 23 v 16:30 Zbigniew Jędrzejewski-Szmek napsal(a): On Wed, Jul 26, 2023 at 04:19:05PM +0200, Ralf Corsépius wrote: Am 26.07.23 um 13:46 schrieb Vít Ondruch: I think that Perl folks are using something aka %perl_bootstrap. Not sure if this is just for historic reasons and they could eventually migrate to regular bootstrap method. No, it's not historical. Historical in a sense that it predates the boostrap guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping Vít Perl has cyclic dependencies. To break them, some perl modules are built twice. The question is why it's %perl_bootstrap instead of %_with_bootstrap, which is the documented macro for bootstrapping (and which also has automatic support in %dist, etc.). Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
Dne 26. 07. 23 v 21:11 Björn Persson napsal(a): Vitaly Zaitsev via devel wrote: On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote: You could, for example, buy a supported Logitech Receiver I don't recommend anyone to buy this proprietary hardware: For years I tried to use Bluetooth mice, thinking a standard would be preferable over a proprietary protocol. But Bluetooth never worked well for me. For years, I am using MS IntelliMouse Explorer for BT, which might be already ~15 years old and the only problem I remember is that once, I have forgotten that the mouse does not need to be paired so I struggled to install it. Other then that, no issues at all. Vít It's not just mice. Everything I've tried to do with Bluetooth has been unstable and unreliable. Eventually I gave up and concluded that Bluetooth in Fedora is not a thing to rely on. The mice I've used that connect to Logitech dongles have always been responsive and never had any connection problems. Mouse cables get in my way and disturb my work. As long as GUIs and web programs require a mouse, I need a wireless mouse. Since Bluetooth is out, Logitech is it. I'd never use a wireless keyboard though. Whether Bluetooth or Logitech, I'm not going to type passphrases over some iffy radio protocol using a random number generator of unknown quality. Alexander Ploumistos wrote: And thanks to fwupd and Logitech's embracing it, we had the fix in a very short time. I never knew about it until now, because nothing notified me that a firmware update was available. I have now enabled fwupd-refresh.timer. I seem to get notifications only in SSH, not on the console, but that's something at least. If it had been on by default, then it would probably have been less than four years before I found out about those vulnerabilities. If the firmware files are properly authenticated, then I think notifications about firmware updates should be enabled on all installations. Björn Persson ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: List of long term FTBFS packages to be retired (and similar reports)
On Thu, Jul 27, 2023 at 12:54 PM Vít Ondruch wrote: > > I think the current order is fine. Because if I am not mistaken, should > I be listed in the PACKAGER section, I would also receive personal copy > of this email as an affected maintainer. Otherwise, looking at the > PACKAGE section is the right thing to do. That only works if you're fortunate to use an E-Mail provider that doesn't deduplicate identical emails (such as GMail). Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: List of long term FTBFS packages to be retired (and similar reports)
Dne 27. 07. 23 v 11:46 Fabio Valentini napsal(a): On Wed, Jul 26, 2023 at 6:25 PM Frank Dana wrote: On Tue, Jul 25, 2023, 10:18 AM Miro Hrončok wrote: Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 39 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 2 weeks, i.e. around 2023-08-01. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 36. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Apologies if this has been discussed in the past, but... Perhaps I'm unusual, perhaps not. But the way I typically consume any of Miro's packaging reports is, I scroll down to the "affected (co-)maintainers" section, look for my userid to see if there's anything I need to deal with urgently, and then... Well, depends how much time I have. Sometimes, that's it. Other times, I look over the rest of the mail to see if any packages of interest to me are listed. But I always start by looking for my own name. So, because the PACKAGER, rather than PACKAGE, names are actually the most important part of the email (at least for me), I was wondering if it would make sense to list them second or even first, rather than third / last? I am doing something similar - mostly giving the list of packages a glance, and then checking if I am marked as affected by anything. So moving things around (1, 3, 2, in your numbering scheme) would help :) Though with the Packager Dashboard listing "affected by orphaned packages" data, this has become less important. Maybe the "affected by long-term FTBFS" data could be integrated into the Packager Dashboard as well? I think the current order is fine. Because if I am not mistaken, should I be listed in the PACKAGER section, I would also receive personal copy of this email as an affected maintainer. Otherwise, looking at the PACKAGE section is the right thing to do. Vít Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: List of long term FTBFS packages to be retired (and similar reports)
On Wed, Jul 26, 2023 at 6:25 PM Frank Dana wrote: > > > > On Tue, Jul 25, 2023, 10:18 AM Miro Hrončok wrote: >> >> Dear maintainers. >> >> Based on the current fail to build from source policy, the following packages >> should be retired from Fedora 39 approximately one week before branching. >> >> 5 weekly reminders are required, hence the retirement will happen >> approximately in 2 weeks, i.e. around 2023-08-01. >> >> Policy: >> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ >> >> The packages in rawhide were not successfully built at least since Fedora 36. >> >> This report is based on dist tags. >> >> Packages collected via: >> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb >> >> If you see a package that was built, please let me know. >> If you see a package that should be exempted from the process, >> please let me know and we can work together to get a FESCo approval for that. >> >> If you see a package that can be rebuilt, please do so. > > > > Apologies if this has been discussed in the past, but... > > Perhaps I'm unusual, perhaps not. But the way I typically consume any of > Miro's packaging reports is, I scroll down to the "affected (co-)maintainers" > section, look for my userid to see if there's anything I need to deal with > urgently, and then... Well, depends how much time I have. Sometimes, that's > it. Other times, I look over the rest of the mail to see if any packages of > interest to me are listed. But I always start by looking for my own name. > > So, because the PACKAGER, rather than PACKAGE, names are actually the most > important part of the email (at least for me), I was wondering if it would > make sense to list them second or even first, rather than third / last? I am doing something similar - mostly giving the list of packages a glance, and then checking if I am marked as affected by anything. So moving things around (1, 3, 2, in your numbering scheme) would help :) Though with the Packager Dashboard listing "affected by orphaned packages" data, this has become less important. Maybe the "affected by long-term FTBFS" data could be integrated into the Packager Dashboard as well? Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
koji: BuildError: error retrieving sources
Hi, Trying to go after an FTBFS, I am once again, facing a weird koji build errors: From https://koji.fedoraproject.org/koji/taskinfo?taskID=103995751 ... BuildError: error retrieving sources, mock exited with status 56; see root.log for more information ... From https://kojipkgs.fedoraproject.org//work/tasks/5751/103995751/root.log ... DEBUG util.py:442: curl: (56) OpenSSL SSL_read: OpenSSL/3.0.8: error:0A00010B:SSL routines::wrong version number, errno 0 ... WTH? Ralf ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: List of long term FTBFS packages to be retired in August
Miro Hrončok wrote on 2023/07/25 21:24: Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 39 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 2 weeks, i.e. around 2023-08-01. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 36. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers nom-tam-fits gil, lupinix, zbyszek telepathy-qt jgrulich, jreznik, kde-sig, rdieter Rescued these 2 packages (fixed FTBFS). Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Unannounced soname bump: libotf
On Wed, Jul 26, 2023 at 5:32 PM Jason L Tibbitts III wrote:
>
> > Gary Buhrmaster writes:
>
> > I have found that using something like libfoo.so.X{,.*} in the %files
> > directive can be a useful reminder (enforcer) to reduce such surprises
> > (that particular glob presumes semantic versioning, and that minor and
> > patch level updates do not require rebuilds, but that is true much of
> > the time).
>
> In fact, excessively wide globbing here is explicitly discouraged by the
> packaging guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files
>
> Looking at the current spec, it uses "%{_libdir}/*.so.*"; had it
> followed this guideline, I believe this issue would not have occurred.
I agree, fixed:
https://src.fedoraproject.org/rpms/libotf/c/0ccd534c?branch=rawhide
--
Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat
--
On Wed, Jul 26, 2023 at 5:32 PM Jason L Tibbitts III wrote:
>
> > Gary Buhrmaster writes:
>
> > I have found that using something like libfoo.so.X{,.*} in the %files
> > directive can be a useful reminder (enforcer) to reduce such surprises
> > (that particular glob presumes semantic versioning, and that minor and
> > patch level updates do not require rebuilds, but that is true much of
> > the time).
>
> In fact, excessively wide globbing here is explicitly discouraged by the
> packaging guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files
>
> Looking at the current spec, it uses "%{_libdir}/*.so.*"; had it
> followed this guideline, I believe this issue would not have occurred.
>
> - J<
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
