Re: Failed RPM database migrations

Hi, Richard W.M. Jones wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=2042147#c2 > https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr > https://bugzilla.redhat.com/2042099 > > The RPM database is supposed to move from /var/lib/rpm to > /usr/lib/sysimage/rpm. This was supposed to

[Bug 2138492] New: perl-DateTime-TimeZone-2.56 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2138492 Bug ID: 2138492 Summary: perl-DateTime-TimeZone-2.56 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime-TimeZone Keywords: FutureFeature,

Re: [Test-Announce] 2022-10-31 @ 16:00 UTC - Fedora 37 Blocker Review Meeting

On Sat, Oct 29, 2022 at 12:44 AM Adam Williamson wrote: > > # F36 Blocker Review meeting If this was a test to see if anyone noticed the title being wrong, I am afraid I have failed that test for the entire cycle. ___ devel mailing list --

[Test-Announce] 2022-10-31 @ 16:00 UTC - Fedora 37 Blocker Review Meeting

# F36 Blocker Review meeting # Date: 2022-10-31 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 1 proposed Final freeze exception to review, but also we can probably kick around the plans for the release process over the next couple of weeks (hence the

[Test-Announce] Proposal to CANCEL: 2022-10-31 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have anything much for the agenda again. There will be a blocker review meeting, though. If you're aware of anything it would be useful to discuss this week, please do reply to this mail and we can run the meeting. Thanks folks!

libxml2-2.10.3-1.fc36 breaks (part of) GraphicsMagick

With this libxml2 update: ``` gm convert -list format ... gm convert: Unable to load module ("/usr/lib64/GraphicsMagick-1.3.38/modules-Q16/coders/url.la: file not found") ``` In fact, `url.so` is there but cannot be dlopen'ed. This works after downgrading libxml2 to 2.9. I noticed because my

Heads up home brewers - brewtarget update and license change

I recently adopted brewtarget and updated it to the latest release (3.0.2). Since this is a major update, it contains quite a few changes. ### License The new SPDX license string is: GPL-3.0-or-later AND BSD-2-Clause AND WTFPL AND (CC-BY-SA-3.0 OR LGPL-3.0-only) AND LGPL-2.1-only The

CPE Weekly Update – Week 43 2022

*Hi everyone,This is a weekly report from the CPE (Community Platform Engineering) Team.The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-43-2022 /.If you want to receive weekly

Re: Failed RPM database migrations

On Fri, 28 Oct 2022 14:59:54 - "Sergey Mende" wrote: > thank you, I got the recipe from the previous conversations. I just > asked if I could help with logs analysis or somehow else before I fix > the issue. Sorry for the misunderstanding. ___

Re: Failed RPM database migrations

On Fri, Oct 28, 2022 at 13:49:21 +0100, Richard W.M. Jones wrote: > On Fri, Oct 28, 2022 at 01:45:32PM +0100, Tom Hughes wrote: > > On 28/10/2022 13:31, Richard W.M. Jones wrote: > > >On Fri, Oct 28, 2022 at 12:29:30PM +0100, Tom Hughes wrote: > > >>The reason it hadn't completed is that

Re: Failed RPM database migrations

Rich, stan, thank you, I got the recipe from the previous conversations. I just asked if I could help with logs analysis or somehow else before I fix the issue. Regards, Sergey ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

Re: Failed RPM database migrations

On Fri, Oct 28, 2022 at 07:46:03AM -0700, stan via devel wrote: > On Fri, 28 Oct 2022 13:08:19 - > "Sergey Mende" wrote: > > > I upgraded from 35 to 36 in the beginning of Sept this year. The > > migration failed. May I help somehow? > > I used the advice from Tom Hughes in his earlier

Re: Failed RPM database migrations

On Fri, 28 Oct 2022 13:08:19 - "Sergey Mende" wrote: > I upgraded from 35 to 36 in the beginning of Sept this year. The > migration failed. May I help somehow? I used the advice from Tom Hughes in his earlier message to complete my failed migration. # systemctl enable rpmdb-migrate #

Re: openvdb 10.0.0 build issue

With my zswap doubled I made it to 77% before it failed... Time to disable LTO? Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: Failed RPM database migrations

Hi, I upgraded from 35 to 36 in the beginning of Sept this year. The migration failed. May I help somehow? Regards, Sergey. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

openvdb 10.0.0 build issue

Since it was released I figured I would just play around building it locally in mock but I'm running into a failure I haven't seen before at about 56%: Container 6cbaadceeecc4c62a1c029207e4389f1 terminated by signal KILL. So my gut telling me it was a resource issue I ran glances on the next

Re: Failed RPM database migrations

On Fri, Oct 28, 2022 at 01:45:32PM +0100, Tom Hughes wrote: > On 28/10/2022 13:31, Richard W.M. Jones wrote: > >On Fri, Oct 28, 2022 at 12:29:30PM +0100, Tom Hughes wrote: > >>The reason it hadn't completed is that rpmdb-migrate.service > >>was enabled on that machine. > >[was not, I guess?] > >

Re: Failed RPM database migrations

On 28/10/2022 13:31, Richard W.M. Jones wrote: On Fri, Oct 28, 2022 at 12:29:30PM +0100, Tom Hughes wrote: The reason it hadn't completed is that rpmdb-migrate.service was enabled on that machine. [was not, I guess?] Yes ;-) Enabling (and starting) that service made it complete.

Re: Failed RPM database migrations

On Fri, Oct 28, 2022 at 12:29:30PM +0100, Tom Hughes wrote: > The reason it hadn't completed is that rpmdb-migrate.service > was enabled on that machine. [was not, I guess?] > Enabling (and starting) that service made it complete. Interesting. The current state of that service is: ○

Re: Heads up! OpenImageIO 2.4 series coming to rawhide

On Fri, Oct 28, 2022 at 1:24 AM Adam Williamson wrote: > On Thu, 2022-10-27 at 19:42 -0500, Richard Shaw wrote: > > On Thu, Oct 27, 2022 at 5:15 PM Tom Rix wrote: > > > > > Sorry, I did not run into the freeglut-devel problem with the manual > build > > > > > > > I think I have something funny

Fedora 37 compose report: 20221028.n.0 changes

OLD: Fedora-37-20221027.n.0 NEW: Fedora-37-20221028.n.0 = SUMMARY = Added images:8 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

[Bug 2136603] perl-CPAN-Perl-Releases-5.20221020 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2136603 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2

Re: Failed RPM database migrations

I've just checked 4 systems (2x Workstation, MATE and Cloud), and the migration was successful on all of them. They were all upgraded to the latest versions in testing at the time with dnf system-upgrade. Regular package updates were performed weekly at the latest.

Re: Failed RPM database migrations

The reason it hadn't completed is that rpmdb-migrate.service was enabled on that machine. Enabling (and starting) that service made it complete. Tom On 28/10/2022 12:24, Tom Hughes via devel wrote: I have one machine that has failed. It was an upgrade from 35 to 36 done using dnf distro-sync

Re: Failed RPM database migrations

I have one machine that has failed. It was an upgrade from 35 to 36 done using dnf distro-sync but I have plenty of others done the same way that worked. One difference is that it's a machine that wasn't upgraded until August while other ones were done back in May as a result of which the

[Bug 2136603] perl-CPAN-Perl-Releases-5.20221020 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2136603 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In

Failed RPM database migrations

https://bugzilla.redhat.com/show_bug.cgi?id=2042147#c2 https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr https://bugzilla.redhat.com/2042099 The RPM database is supposed to move from /var/lib/rpm to /usr/lib/sysimage/rpm. This was supposed to happen automatically when you upgraded the rpm

Re: [Test-Announce] Fedora Linux 37 Final is NO-GO

On Fri, Oct 28, 2022 at 5:27 AM Michael J Gruber wrote: > > In this context, since we are still in freeze: > > Can dnf distinguish between updates in testing and updates in testing > submitted for stable? > > People might want to dist-upgrade to F37 now (I'm not critizing the release >

Re: Inactive packagers to be removed after the F37 release

Hi, On to, 15 syys 2022, Kevin Fenzi wrote: > CentOS folks still use certs for their koji: > https://wiki.centos.org/Authentication#TLS_certificate > (and thats using the same account system/ipa servers as fedora). > > > I hope we can plan to work together on this improvement again, similar > >

Re: [Test-Announce] Fedora Linux 37 Final is NO-GO

In this context, since we are still in freeze: Can dnf distinguish between updates in testing and updates in testing submitted for stable? People might want to dist-upgrade to F37 now (I'm not critizing the release decision) and want to get "the same updates as on F36". Ideally, no F36 package

Re: Heads up! OpenImageIO 2.4 series coming to rawhide

On Thu, 2022-10-27 at 19:42 -0500, Richard Shaw wrote: > On Thu, Oct 27, 2022 at 5:15 PM Tom Rix wrote: > > > Sorry, I did not run into the freeglut-devel problem with the manual build > > > > I think I have something funny going on with the conditionals. Initially > they were negative