-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi all.
To this day, the release 2.0.0 of 'SeqAn' [1] seems incompatible with ARM architectures [2]. Latest release fully built in Fedora is seqan-1.4.2-9 [3] but its tests are not all executable in aarch64 [2], so i need to fix it.
Is it a problem if i downgrade the current release of SeqAn on pkgdb until the new 2.0.0 is fully ready ?
[1] http://www.seqan.de/ [2] http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=18320 [3] http://koji.fedoraproject.org/koji/packageinfo?packageID=18665
- -- Antonio Trande
mailto: sagitter 'at' fedoraproject 'dot' org http://fedoraos.wordpress.com/ https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x565E653C Check on https://keys.fedoraproject.org/
"AT" == Antonio Trande anto.trande@gmail.com writes:
AT> Is it a problem if i downgrade the current release of SeqAn on pkgdb AT> until the new 2.0.0 is fully ready ?
I'm not sure what pkgdb has to do with that; it doesn't track versions.
Basically, if you didn't have a successful non-scratch koji build (and it appears you did not), you are entirely free to go backwards. Just revert the last commits and push that. Or simply leave the package where it is and keep trying to fix the bugs. You don't always have to build what is currently in git.
If you had a successful build, though, things are more complicated. And if you created an update that went to testing, you cannot downgrade without increasing Epoch:.
- J<