Re: Releasing package updates in multiple Fedora releases

On Sun, Jun 18, 2023 at 5:17 AM Mattia Verga via devel wrote: > > For the 99% of packages I maintain I usually perform the same workflow > when updating them: > > 1. Update spec and source in Rawhide > 2. commit and push > 3. fedpkg build > 4. fedpkg switch-branch f* > 5. git merge rawhide > 6.

[Bug 2215815] New: perl-re-engine-RE2-0.18 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2215815 Bug ID: 2215815 Summary: perl-re-engine-RE2-0.18 is available Product: Fedora Version: rawhide Status: NEW Component: perl-re-engine-RE2 Keywords: FutureFeature, Triaged

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-93f6303432 trafficserver-9.2.1-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing chromium-114.0.5735.133-1.el7

[EPEL-devel] Fedora EPEL 9 updates-testing report

The following Fedora EPEL 9 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-faf5368307 trafficserver-9.2.1-1.el9 The following builds have been pushed to Fedora EPEL 9 updates-testing chromium-114.0.5735.133-1.el9

[EPEL-devel] Fedora EPEL 8 updates-testing report

The following Fedora EPEL 8 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-600bc2a0d2 trafficserver-9.2.1-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f48765fe4c iniparser-4.1-6.el8 3

Re: Fedora ELN Plans for Summer 2023

* Dan Čermák: >> A bit related to the CentOS 10 bringup, the CentOS ISA SIG is currently >> porting CentOS 9 Stream to the x86-64-v3 ISA level. I believe there are >> some failures that are not yet fixed in ELN/upstream, and we'll be >> sharing our workarounds with rawhide/ELN as appropriate. >

Fedora rawhide compose report: 20230618.n.0 changes

OLD: Fedora-Rawhide-20230617.n.0 NEW: Fedora-Rawhide-20230618.n.0 = SUMMARY = Added images:2 Dropped images: 1 Added packages: 2 Dropped packages:0 Upgraded packages: 40 Downgraded packages: 0 Size of added packages: 59.16 MiB Size of dropped packages:0 B

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

> On 18 Jun 2023, at 17:41, Miro Hrončok wrote: > > On 18. 06. 23 15:17, Barry Scott wrote: >>> On 17 Jun 2023, at 10:50, Miro Hrončok wrote: >>> >>> Please avoid further rawhide builds of them until the side tag is merged. >> I have been fixing pycxx and pysvn for python 3.12. >> I have

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

> On 18 Jun 2023, at 17:41, Miro Hrončok wrote: > > On 18. 06. 23 15:17, Barry Scott wrote: >>> On 17 Jun 2023, at 10:50, Miro Hrončok wrote: >>> >>> Please avoid further rawhide builds of them until the side tag is merged. >> I have been fixing pycxx and pysvn for python 3.12. >> I have

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

On 18. 06. 23 15:17, Barry Scott wrote: On 17 Jun 2023, at 10:50, Miro Hrončok wrote: Please avoid further rawhide builds of them until the side tag is merged. I have been fixing pycxx and pysvn for python 3.12. I have released new pycxx and pysvn upstream that fix the 3.12 issues. But I

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

On 18. 06. 23 15:17, Barry Scott wrote: On 17 Jun 2023, at 10:50, Miro Hrončok wrote: Please avoid further rawhide builds of them until the side tag is merged. I have been fixing pycxx and pysvn for python 3.12. I have released new pycxx and pysvn upstream that fix the 3.12 issues. But I

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

On 13. 06. 23 14:02, Tomas Hrnciar wrote: Hello, in order to deliver Python 3.12, we are running a coordinated rebuild in a side tag. https://fedoraproject.org/wiki/Changes/Python3.12 We anticipate starting this rebuildsometimethis week.

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

On 13. 06. 23 14:02, Tomas Hrnciar wrote: Hello, in order to deliver Python 3.12, we are running a coordinated rebuild in a side tag. https://fedoraproject.org/wiki/Changes/Python3.12 We anticipate starting this rebuildsometimethis week.

Re: releng-bot owns my package in SCM - belcard

On Sun, 2023-06-18 at 17:35 +0200, Kalev Lember wrote: > On Sun, Jun 18, 2023 at 12:01 PM Philip Wyett > wrote: > > Hi, > > > > After completing a package-review for belcard[1], I tried to create the > > repo, seems that the > > repo > > after a couple of attempts got created, but is owned by

Re: Releasing package updates in multiple Fedora releases

On Sun, Jun 18, 2023 14:51:01 +0200, Sandro wrote: > On 18-06-2023 14:16, Vitaly Zaitsev via devel wrote: > > On 18/06/2023 11:16, Mattia Verga via devel wrote: > > > This is quite boring and time wasting... is there a more efficient way > > > to use my packaging time? Do you think fedpkg can be

Re: releng-bot owns my package in SCM - belcard

On Sun, Jun 18, 2023 at 12:01 PM Philip Wyett wrote: > Hi, > > After completing a package-review for belcard[1], I tried to create the > repo, seems that the repo > after a couple of attempts got created, but is owned by 'releng-bot' and > not myself 'kathenas'. How > can I get this resolved? >

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

> On 17 Jun 2023, at 10:50, Miro Hrončok wrote: > > Please avoid further rawhide builds of them until the side tag is merged. I have been fixing pycxx and pysvn for python 3.12. I have released new pycxx and pysvn upstream that fix the 3.12 issues. But I did not see your message about not

Re: Releasing package updates in multiple Fedora releases

On 18-06-2023 14:16, Vitaly Zaitsev via devel wrote: On 18/06/2023 11:16, Mattia Verga via devel wrote: This is quite boring and time wasting... is there a more efficient way to use my packaging time? Do you think fedpkg can be enhanced to have a single command which makes 4-5-6 to all

Re: Releasing package updates in multiple Fedora releases

On 18/06/2023 11:16, Mattia Verga via devel wrote: This is quite boring and time wasting... is there a more efficient way to use my packaging time? Do you think fedpkg can be enhanced to have a single command which makes 4-5-6 to all specified branches? Add to your ~/.bashrc the following:

Re: Releasing package updates in multiple Fedora releases

On Sun, 2023-06-18 at 09:16 +, Mattia Verga via devel wrote: > For the 99% of packages I maintain I usually perform the same workflow > when updating them: > > 1. Update spec and source in Rawhide > 2. commit and push > 3. fedpkg build > 4. fedpkg switch-branch f* > 5. git merge rawhide > 6.

releng-bot owns my package in SCM - belcard

Hi, After completing a package-review for belcard[1], I tried to create the repo, seems that the repo after a couple of attempts got created, but is owned by 'releng-bot' and not myself 'kathenas'. How can I get this resolved? [1] https://bugzilla.redhat.com/show_bug.cgi?id=2211811 Regards

Re: Releasing package updates in multiple Fedora releases

On 18-06-2023 11:16, Mattia Verga via devel wrote: And repeat 4-5-6 for every f*/epel* branches where I want to push the update. That drill sounds familiar. ;) If you look at he output of 'fedpkg build --help', there seems to be an option to submit koji builds for multiple targets at once.

Re: Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates

On Tue, 2023-06-13 at 08:57 +0200, Petr Pisar wrote: > V Mon, Jun 12, 2023 at 08:29:13AM -0700, Adam Williamson napsal(a): > > On Mon, 2023-06-12 at 12:05 +0200, Petr Pisar wrote: > > > or there must be some one else to do it. > > > > We (QA team) will do this. > > > > > I would expect answers

Releasing package updates in multiple Fedora releases

For the 99% of packages I maintain I usually perform the same workflow when updating them: 1. Update spec and source in Rawhide 2. commit and push 3. fedpkg build 4. fedpkg switch-branch f* 5. git merge rawhide 6. push and fedpkg build And repeat 4-5-6 for every f*/epel* branches where I want

Re: Modules without modularity

On Sat, Jun 17, 2023 at 9:12 PM Kevin Kofler via devel wrote: > > Petr Pisar wrote: > > I understand the horror that you can have two packages which cannot be > > installed at the same time. The same as you cannot start httpd and nginx > > services at the same time. But now the conflict is