[opensuse-packaging] Prefered Procedure to Merge Two Packages into One
Hi, currently, I'm facing the problem of how to merge two separate packages into one. In my example, it's the (Java) packages jing and trang. It doesn't make sense anymore to maintain them separately. Upstream develops it in a single repository so it makes sense to do the same in OBS. So my idea was to combine both into a "jing-trang" package project on OBS which creates the two RPM packages jing and trang as output. See [1] for the details. Now, I'm wondering how to proceed. Should I submit the jing-trang to Java:packages first and do a delete request for jing and trang afterwards? Or should there be a bug report at the first place to refer to it in the changelog? What's the preferred procedure here? Thanks! ---- Reference [1] https://build.opensuse.org/package/show/home:thomas-schraitle:java/jing-tran... -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, 2017-11-24 at 13:52 +0100, Thomas Schraitle wrote:
Hi,
currently, I'm facing the problem of how to merge two separate packages into one. In my example, it's the (Java) packages jing and trang.
It doesn't make sense anymore to maintain them separately. Upstream develops it in a single repository so it makes sense to do the same in OBS.
Following upstream is always a good reason
So my idea was to combine both into a "jing-trang" package project on OBS which creates the two RPM packages jing and trang as output. See [1] for the details.
Now, I'm wondering how to proceed.
Should I submit the jing-trang to Java:packages first and do a delete request for jing and trang afterwards? Or should there be a bug report at the first place to refer to it in the changelog?
Is this openSUSE-only or also relevant for SLE? If openSUSE-only, the requirements for bug reports is much lower (unless you target maintenance releases) - for such package rework, a bug is not nescessary and you can just submit the new package to Java:packages and from there to openSUSE:Factory, together with the delete requests (The del req on the devel prj can only be accepted once the packages disappear from openSUSE:Factory) Cheers, Dominique
Hi Dominique, thanks for your answer!
[...] Following upstream is always a good reason
Yes, and it makes maintenance a lot easier. :)
[...] Is this openSUSE-only or also relevant for SLE?
Well, I think for both.
If openSUSE-only, the requirements for bug reports is much lower (unless you target maintenance releases) - for such package rework, a bug is not nescessary and you can just submit the new package to Java:packages and from there to openSUSE:Factory, together with the delete requests (The del req on the devel prj can only be accepted once the packages disappear from openSUSE:Factory)
So if I understood you correct, if it is relevant for both (openSUSE and SLE) I better open a bug report, right? Another, hopefully, final question: Is there a difference in order in regards to submit and delete requests? Does the project prefer to first submit the new package and then the delete request or vice versa? Thanks! :) -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
On Fri, 2017-11-24 at 14:46 +0100, Thomas Schraitle wrote:
If openSUSE-only, the
requirements for bug reports is much lower (unless you target maintenance releases) - for such package rework, a bug is not nescessary and you can just submit the new package to Java:packages and from there to openSUSE:Factory, together with the delete requests (The del req on the devel prj can only be accepted once the packages disappear from openSUSE:Factory)
So if I understood you correct, if it is relevant for both (openSUSE and SLE) I better open a bug report, right?
It does make things easier on the SLE side.
Another, hopefully, final question: Is there a difference in order in regards to submit and delete requests? Does the project prefer to first submit the new package and then the delete request or vice versa?
If you first send delete requests and then the new package names, there can be a couple snapshots without the packages. Likely not a big drama here - for other things it could be fatal. For TW, I can work with bot approaches Cheers Dominique
Hi Dominique,
[...]
So if I understood you correct, if it is relevant for both (openSUSE and SLE) I better open a bug report, right?
It does make things easier on the SLE side.
Ok, I did it now, bsc#1069796.
Is there a difference in order in regards to submit and delete requests? Does the project prefer to first submit the new package and then the delete request or vice versa?
If you first send delete requests and then the new package names, there can be a couple snapshots without the packages. Likely not a big drama here - for other things it could be fatal.
For TW, I can work with bot approaches
Thanks for the clarification. Much appreciated! :) -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
participants (2)
-
Dominique Leuenberger / DimStar -
Thomas Schraitle