29210 – Conflict upgrading 7->8 between hdf5 and hdf5_10

Bug 29210 - Conflict upgrading 7->8 between hdf5 and hdf5_10

Summary: Conflict upgrading 7->8 between hdf5 and hdf5_10

Status:	RESOLVED FIXED

Alias:	None

Product:	Mageia
Classification:	Unclassified
Component:	RPM Packages (show other bugs)
Version:	8
Hardware:	All Linux

Priority:	Normal Severity: critical
Target Milestone:	---
Assignee:	Chris Denice
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2021-07-04 08:54 CEST by papoteur
Modified:	2023-02-25 22:51 CET (History)
CC List:	2 users (show)

See Also:
Source RPM:	hdf5-1.10.7-3.mga8.x86_64
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description papoteur 2021-07-04 08:54:48 CEST

Description of problem:
While upgrading, I got a conflict:
hdf5>=1.10.4 hdf5_10-1.8.21-5.mga7.x86_64 
hdf5>=1.10.4 hdf5_10-1.8.21-6.mga8.x86_64 is conflicting with hdf5-1.10.7-3.mga8.x86_64

Comment 1 Lewis Smith 2021-07-04 21:07:24 CEST

This is Chris's baby, so assigning to you.

Assignee: bugsquad => eatdirt

Comment 2 Dave Hodgins 2021-07-04 22:03:34 CEST

Package conflicts should be ok and just result in the old package being
removed.

File conflicts are critical and must be fixed as they will abort the rpm
transaction which may lead to other package upgrades failing causing the
upgrade to leave the system un-bootable.

CC: (none) => davidwhodgins

Comment 3 Chris Denice 2021-07-05 20:49:00 CEST

Let me know if the upgrade fails due to this, it shouldn't indeed!

Status: NEW => NEEDINFO

Comment 4 papoteur 2021-07-05 21:03:49 CEST

Hello,
I don't remember exactly, but if I caught it, this is because I had time to read it and write, thus the migration has been stopped when the error occurred.
I was in runlevel 3, and using urpmi --auto-update --auto.

Comment 5 Dave Hodgins 2021-07-05 22:47:29 CEST

Did it stop the upgrade or did it just happen to occur right before a pause
while rpm prepares the next transaction?

Comment 6 Aurelien Oudelet 2021-07-06 13:15:08 CEST Comment hidden (obsolete)

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 7 papoteur 2021-07-06 17:23:29 CEST

It stops the upgrade.

Comment 8 Aurelien Oudelet 2021-07-06 17:43:38 CEST

(In reply to papoteur from comment #7)
> It stops the upgrade.

Reassigning against Mageia 8.
Raising this as Critical as it breaks the upgrade path.

Status: NEEDINFO => NEW
Version: 7 => 8
CC: (none) => ouaurelien
Severity: normal => critical

Comment 9 Chris Denice 2021-09-09 16:43:55 CEST

Hi there,
I was unable to reproduce this issue. I indeed have a package conflict between hdf5_10 and hdf5, but the upgrade went through by deinstalling hdf5_10. I'll try with another machine to check again.

Comment 10 papoteur 2023-02-25 22:51:12 CET

This is old, and I think solved. Thus closing.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Note You need to log in before you can comment on or make changes to this bug.