+++ This bug was initially created as a clone of Bug #1988236 +++

Description of problem:
Now the mdadm version is old. Update to latest upstream

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Ben Cotton on 2021-08-10 13:33:07 UTC ---

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

--- Additional comment from XiaoNi on 2021-08-11 05:14:55 UTC ---

Hi Ben

Thanks for the help. Can this mdadm update be released with f35? I did fedpkg update before.
But now, it looks like the fedpkg update is done automatically. 

Thanks
Xiao

--- Additional comment from Adam Williamson on 2021-08-12 15:56:21 UTC ---

Your recent build is tagged for both f35 and f36 (Rawhide) already. You do not need to create updates manually for F35 yet, only after the "Bodhi updates-testing activation point" on 2021-08-24 (see https://fedorapeople.org/groups/schedule/f-35/f-35-devel-tasks.html ).

However, the build was versioned wrong. You cannot just use "rc2" as the 'release' component. Versioning guidelines are here:

https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/

with examples here:

https://fedoraproject.org/wiki/Package_Versioning_Examples

this package should have been versioned 4.2-0.1.rc2, the 'release' component should have been "0.1.rc2". If you then updated the package without going to a new upstream release, the next would be "0.2.rc2". If upstream released an rc3, then you'd go to "0.3.rc3".

Thanks!

--- Additional comment from XiaoNi on 2021-08-13 00:32:14 UTC ---

Hi Adam

Thanks for pointing about this. Do I need to fix this problem this time and do a new build?
Or I can fix this in next build in the future?

Thanks
Xiao

--- Additional comment from Adam Williamson on 2021-08-13 05:46:27 UTC ---

In this case it should be OK to just fix it with the next build.

--- Additional comment from Dominik 'Rathann' Mierzejewski on 2022-02-21 12:59:24 UTC ---

4.2 is out, can we get this updated in F35+?

--- Additional comment from XiaoNi on 2022-02-23 05:08:09 UTC ---

4.2 will be updated in rawhide. For f35/f36, we only fix bugs. Is it ok?

--- Additional comment from XiaoNi on 2022-02-23 05:09:28 UTC ---

Hi Adam

I see mdadm-4.2-rc2 is already in f35/f36/rawhide. In rhel produce, the errata can be change the bug to ON_QA.
Then qe team verify the bug and move it to Verified. At last, the bug is closed.

How about fedora? It's still New now. What should I do for this one now? close it? Do you know a doc or something else
that can help me to understand the process.

Thanks
Xiao

--- Additional comment from Dominik 'Rathann' Mierzejewski on 2022-02-23 13:04:56 UTC ---

XiaoNi, 4.2rc2 (release candidate) is not 4.2 final release. Changes between rc2 and final are bugfixes, so it's definitely OK to update in F35+.

--- Additional comment from XiaoNi on 2022-02-28 00:39:19 UTC ---

It makes sense. I'll do it this week