On 29-10-2022 17:37, Neal Gompa wrote:
On Sat, Oct 29, 2022 at 10:49 AM Orion Poplawski wrote:
On 10/28/22 22:53, Todd Zullinger wrote:
It seems that it's not so much a failed migration as a
migration which is never attempted. :/
Likely in certain situations.
What I don't understand is
On Sat, Oct 29, 2022 at 10:49 AM Orion Poplawski wrote:
>
> On 10/28/22 22:53, Todd Zullinger wrote:
> > 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/2
On 10/28/22 22:53, Todd Zullinger wrote:
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/
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 happe
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.
___
deve
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 rpmdb-mig
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 se
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 messa
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
# system
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
Fedo
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?]
>
> Y
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.
Interesti
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:
○ rpmdb-migra
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.
_
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
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 upgrad
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 p
17 matches
Mail list logo
