[opensuse-buildservice] Patchinfo usage, downgrading via maintenance process
Hi, we made a distribution release with our OBS instance where we included a package in a version that has to be downgraded now. Say we included foo 5.0 in the distribution but want to downgrade to 4.9, codefreeze is passed, project is locked, first distributions are shipped. Can the patchinfo checkbox "Block release?" be used for that? Like creating a maintenance release for foo 5.0 with that checkbox enabled and then create a maintenance release for foo 4.9? I had success with repository priorities but that requires that the software is not yet installed to prefer the lower version. And zypper does not support a "ignore foo >= 5.0" syntax as it seems to ignore certain packages. Best regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Sep 07, 2020 at 11:09:32AM +0000, Morschhäuser, Mark wrote:
Hi,
we made a distribution release with our OBS instance where we included a package in a version that has to be downgraded now. Say we included foo 5.0 in the distribution but want to downgrade to 4.9, codefreeze is passed, project is locked, first distributions are shipped. Can the patchinfo checkbox "Block release?" be used for that? Like creating a maintenance release for foo 5.0 with that checkbox enabled and then create a maintenance release for foo 4.9? I had success with repository priorities but that requires that the software is not yet installed to prefer the lower version. And zypper does not support a "ignore foo >= 5.0" syntax as it seems to ignore certain packages.
Not sure what "block release" you are seeing, but it is probably the checkbox for stopping the patchinfo based release process and not the target. the "patch" based workflow with zypper does not allow downgrades, it only does upgrades. You will probably need to issue an update with a 5.0revertto4.9 as package version for instance. ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi,
On 7. Sep 2020, at 13:09 , Morschhäuser, Mark
wrote: Hi,
we made a distribution release with our OBS instance where we included a package in a version that has to be downgraded now. Say we included foo 5.0 in the distribution but want to downgrade to 4.9, codefreeze is passed, project is locked, first distributions are shipped. Can the patchinfo checkbox "Block release?" be used for that? Like creating a maintenance release for foo 5.0 with that checkbox enabled and then create a maintenance release for foo 4.9? I had success with repository priorities but that requires that the software is not yet installed to prefer the lower version. And zypper does not support a "ignore foo >= 5.0" syntax as it seems to ignore certain packages.
If I understood you correctly you want to update version 5.0 of a package with version 4.9? That could be done in adding an epoch into the version, e.g. 1:4.9 would be "later" than 0:5.0 see http://rpm.org/user_doc/dependencies.html#versioning -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Andreas Gauger, Carsten Dirks, Stephan Martin, Dirk Valbert Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Carsten Höger
-
Marcus Meissner
-
Morschhäuser, Mark