[opensuse-factory] Please check your packages in scope of 15.1
Hi, Leap 15.1 will enter it's beta phase soon. Time to review whether 15.1 has the right versions of your packages! You can do that by either installing the current Alpha versions¹ or by checking OBS². Also, please have a look at your personal page in OBS and check for open reviews³. (Semi)automated submissions from Factory need maintainer review as usual. So in case you missed the notifications from OBS please have a look if there are submissions that need your approval. cu Ludwig [1] https://software.opensuse.org/ [2] https://build.opensuse.org/project/show/openSUSE:Leap:15.1 [3] https://build.opensuse.org/user/tasks -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 29. Januar 2019, 16:58:26 CET schrieb Ludwig Nussel:
Hi,
Leap 15.1 will enter it's beta phase soon. Time to review whether 15.1 has the right versions of your packages!
You can do that by either installing the current Alpha versions¹ or by checking OBS². Also, please have a look at your personal page in OBS and check for open reviews³. (Semi)automated submissions from Factory need maintainer review as usual. So in case you missed the notifications from OBS please have a look if there are submissions that need your approval.
For 15.1, is there no automatic version bump to the version that is in Factory? Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Axel Braun schrieb:
Am Dienstag, 29. Januar 2019, 16:58:26 CET schrieb Ludwig Nussel:
Hi,
Leap 15.1 will enter it's beta phase soon. Time to review whether 15.1 has the right versions of your packages!
You can do that by either installing the current Alpha versions¹ or by checking OBS². Also, please have a look at your personal page in OBS and check for open reviews³. (Semi)automated submissions from Factory need maintainer review as usual. So in case you missed the notifications from OBS please have a look if there are submissions that need your approval.
For 15.1, is there no automatic version bump to the version that is in Factory?
No. Same procedure as usual :-) https://en.opensuse.org/openSUSE:Leap_development_process cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 1/29/19 5:37 PM, Ludwig Nussel wrote:
No. Same procedure as usual :-)
Maybe it's me but I don't understand it. This "process description" is full of jargon not understandable for an outsider like me. A simple question: Which action is appropriate if one thinks that a package should be updated from Factory? I've checked these packages and I'd recommend to update them to the version in Factory to get upstream's bugfix releases into Leap: - openldap2 - freeradius-server - unbound - nsd - nss-pam-ldapd - sudo Ciao, Michael.
Am 29.01.19 um 18:55 schrieb Michael Ströder:
On 1/29/19 5:37 PM, Ludwig Nussel wrote:
No. Same procedure as usual :-)
Maybe it's me but I don't understand it. This "process description" is full of jargon not understandable for an outsider like me.
A simple question: Which action is appropriate if one thinks that a package should be updated from Factory?
I've checked these packages and I'd recommend to update them to the version in Factory to get upstream's bugfix releases into Leap: - openldap2 - freeradius-server - unbound - nsd - nss-pam-ldapd - sudo
I'm not authoritative here but can try to explain what I understood so far. Start with checking the current package origin for 15.1: curl -s https://build.opensuse.org/package/view_file/openSUSE:Leap:15.1/00Meta/looku... | grep openldap2 openldap2: SUSE:SLE-15:Update There are several possible results: - SUSE:SLE-15* - openSUSE:Leap:15.0(:Update) - openSUSE:Factory openSUSE:Factory: means you have nothing to do. The latest version in Factory will be pulled in at a certain point (before package freeze). SUSE:SLE-15*: That seems to be the hardest as you need to convince SUSE to consider an update for SLE15 SP1. So there should be good reasons for the update request. Please check out this recent thread: https://lists.opensuse.org/archive/opensuse-factory/2019-01/msg00486.html openSUSE:Leap:15.0(:Update): this has two sub-cases - you are the maintainer: Go ahead and just submit your package to openSUSE:Leap:15.1 - you are not the maintainer: if you are convinced about your request you can directly submit the package as above because the package maintainer has to approve the request; a probably more friendly approach is to ask the maintainer if it's ok to do so You can find the maintainer via "osc maintainer -e $PACKAGE" in case that was not known.
On 30/01/2019 05:19, Wolfgang Rosenauer wrote:
Am 29.01.19 um 18:55 schrieb Michael Ströder:
On 1/29/19 5:37 PM, Ludwig Nussel wrote:
No. Same procedure as usual :-)
Maybe it's me but I don't understand it. This "process description" is full of jargon not understandable for an outsider like me.
A simple question: Which action is appropriate if one thinks that a package should be updated from Factory?
I've checked these packages and I'd recommend to update them to the version in Factory to get upstream's bugfix releases into Leap: - openldap2 - freeradius-server - unbound - nsd - nss-pam-ldapd - sudo
I'm not authoritative here but can try to explain what I understood so far.
Start with checking the current package origin for 15.1: curl -s https://build.opensuse.org/package/view_file/openSUSE:Leap:15.1/00Meta/looku... | grep openldap2 openldap2: SUSE:SLE-15:Update
There are several possible results: - SUSE:SLE-15* - openSUSE:Leap:15.0(:Update) - openSUSE:Factory
openSUSE:Factory: means you have nothing to do. The latest version in Factory will be pulled in at a certain point (before package freeze).
SUSE:SLE-15*: That seems to be the hardest as you need to convince SUSE to consider an update for SLE15 SP1. So there should be good reasons for the update request. Please check out this recent thread: https://lists.opensuse.org/archive/opensuse-factory/2019-01/msg00486.html
There is sometimes another alternative here where if the package maintainer feels that the newer version is of significant benefit to openSUSE users but doesn't meet the requirements for a SUSE update. The package could be swapped to being a openSUSE:Leap:15 package as long as someone is willing to do the extra work to maintain it. If someone from the community is happy to work with the SUSE maintainer to do the work its probably more likely. But this will vary greatly from package to package so the first step is still creating a bug report to discuss it with the maintainer. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Simon Lees schrieb:
[...] There is sometimes another alternative here where if the package maintainer feels that the newer version is of significant benefit to openSUSE users but doesn't meet the requirements for a SUSE update. The package could be swapped to being a openSUSE:Leap:15 package as long as someone is willing to do the extra work to maintain it.
We worked very hard to align SLE and Leap and SUSE is accepting compromises in SLE here and there to accommodate Leap. As such accepting more deviations in Leap for packages that are in SLE is unlikely in 15.
If someone from the community is happy to work with the SUSE maintainer to do the work its probably more likely. But this will vary greatly from package to package so the first step is still creating a bug report to discuss it with the maintainer.
Yup, that's the way to go. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Ströder schrieb:
On 1/29/19 5:37 PM, Ludwig Nussel wrote:
No. Same procedure as usual :-)
Maybe it's me but I don't understand it. This "process description" is full of jargon not understandable for an outsider like me.
Feel free to rephrase and extend the wiki text with the expanations Wolfgang gave. I'm sure you are not the only one who finds that article rather terse :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 1/30/19 9:46 AM, Ludwig Nussel wrote:
Michael Ströder schrieb:
On 1/29/19 5:37 PM, Ludwig Nussel wrote:
No. Same procedure as usual :-)
Maybe it's me but I don't understand it. This "process description" is full of jargon not understandable for an outsider like me.
Feel free to rephrase and extend the wiki text with the expanations Wolfgang gave.
I somewhat expected this answer. The problem is that I cannot even extract something from the answers in this thread which would make up a clear and concise process description. Which in itself might indicate that there is no clear process.
I'm sure you are not the only one who finds that article rather terse :-)
Length of an article does not make it more clear. Ciao, Michael.
participants (5)
-
Axel Braun -
Ludwig Nussel -
Michael Ströder -
Simon Lees -
Wolfgang Rosenauer