openSUSE Leap 15.4 - Beta code submission deadline is on 16th of February
Hello openSUSE! this is a friendly reminder that the code submission deadline for openSUSE Leap 15.4 Beta is February 16th. Same as the code submission deadline for SUSE Linux Enterprise 15 SP4 Public Beta. SLE 15 SP4 has additionally a feature cutoff deadline of February 2nd. This is when SUSE Linux Enterprise 15 SP4 should be feature-full and we should ideally receive only bug fixes later. The later features would be late features handled via a separate late feature process (ECO) https://en.opensuse.org/ECO . We're here to help you with these cases. This and more details in https://en.opensuse.org/openSUSE:Roadmap and https://en.opensuse.org/Feature_Planning_15.4 ** Two tips that I'd like to share with you ** If you're submitting a new package to openSUSE Leap: Please submit it directly to openSUSE Backports. I had to reject some new package submissions that were accidentally submitted to SUSE:SLE- 15*. Simply do osc sr ... openSUSE:Backports:SLE-15-SP4 If you're trying to update a SLE package please reference an issue in the SR text. Examples boo#123456 or feature jsc#SLE-12345 / jsc#OPENSUSE-12345. Submit requests without issue references will be rejected with an ask to resubmit with issue reference. How to report bugs? https://en.opensuse.org/openSUSE:Submitting_bug_reports How to report features? https://en.opensuse.org/Feature_Planning_15.4 For general guidance with submit requests please use https://en.opensuse.org/openSUSE:Packaging_for_Leap -- Best regards Lubos Kocman openSUSE Leap Release Manager
On 1/13/22 17:08, Lubos Kocman wrote:
** Two tips that I'd like to share with you **
Hi, I would like to ask you about a third situation: how to update a non-SLES package? In my case it's the syslog-ng package, and I would like to update it to 3.35 (as in Base:System/syslog-ng and in Factory) for the next Leap release, as it contains a number of bug fixes and some interesting new features. Thanks, Peter
On Thu, Jan 13, 2022 at 11:47 AM Peter Czanik <peter@czanik.hu> wrote:
On 1/13/22 17:08, Lubos Kocman wrote:
** Two tips that I'd like to share with you **
Hi,
I would like to ask you about a third situation: how to update a non-SLES package? In my case it's the syslog-ng package, and I would like to update it to 3.35 (as in Base:System/syslog-ng and in Factory) for the next Leap release, as it contains a number of bug fixes and some interesting new features.
Just submit to openSUSE:Backports:SLE-15-SP4. -- 真実はいつも一つ！/ Always, there's only one truth!
Hi Lubos, Am Donnerstag, 13. Januar 2022, 17:08:01 CET schrieb Lubos Kocman:
** Two tips that I'd like to share with you **
If you're submitting a new package to openSUSE Leap: Please submit it directly to openSUSE Backports. I had to reject some new package submissions that were accidentally submitted to SUSE:SLE- 15*. Simply do osc sr ... openSUSE:Backports:SLE-15-SP4
If you're trying to update a SLE package please reference an issue in the SR text. Examples boo#123456 or feature jsc#SLE-12345 / jsc#OPENSUSE-12345. Submit requests without issue references will be rejected with an ask to resubmit with issue reference.
Just for my curiosity, how does one know if it is a SLE package? You cant see it when you submit, e.g. from d:l:p Second point, if $NEWPACKAGE from the first paragraph requires updates to the historic packages ins SLE, we need a new bug for each or can we use a collective bug (like 'Updates to python packages' )? Thanks Axel
On 1/14/22 05:18, Axel Braun wrote:
Hi Lubos,
Am Donnerstag, 13. Januar 2022, 17:08:01 CET schrieb Lubos Kocman:
** Two tips that I'd like to share with you **
If you're submitting a new package to openSUSE Leap: Please submit it directly to openSUSE Backports. I had to reject some new package submissions that were accidentally submitted to SUSE:SLE- 15*. Simply do osc sr ... openSUSE:Backports:SLE-15-SP4
If you're trying to update a SLE package please reference an issue in the SR text. Examples boo#123456 or feature jsc#SLE-12345 / jsc#OPENSUSE-12345. Submit requests without issue references will be rejected with an ask to resubmit with issue reference.
Just for my curiosity, how does one know if it is a SLE package? You cant see it when you submit, e.g. from d:l:p
If you go to https://build.opensuse.org/project/show/openSUSE:Leap:15.4 Click on "Inherited Packages" and then use the search to filter for the package you want, it will list the origin in the "From" Column. There used to be a metadata file you could look at as well but its either moved or doesn't exist anymore so I don't know where it is. If someone does know i'd love to find out, I used to have a simple script that did the following. function lookup151 --description 'Where does a leap packages come from' osc -A https://api.opensuse.org cat openSUSE:Leap:15.1:Update 00Meta lookup.yml | grep $argv end -- 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
Simon Lees wrote:
... Just for my curiosity, how does one know if it is a SLE package? You cant see it when you submit, e.g. from d:l:p If you go to https://build.opensuse.org/project/show/openSUSE:Leap:15.4 Click on "Inherited Packages" and then use the search to filter for the
On 1/14/22 05:18, Axel Braun wrote: package you want, it will list the origin in the "From" Column. There used to be a metadata file you could look at as well but its either moved or doesn't exist anymore so I don't know where it is. If someone does know i'd love to find out, I used to have a simple script that did the following. function lookup151 --description 'Where does a leap packages come from' osc -A https://api.opensuse.org cat openSUSE:Leap:15.1:Update 00Meta lookup.yml | grep $argv end
Simon, I believe you are looking for `osc maintained PACKAGE_NAME` or just `osc sm PACKAGE_NAME`: geeko $ osc maintained bash SUSE:SLE-15-SP3:Update/bash geeko $ osc maintained bbswitch openSUSE:Leap:15.3:Update/bbswitch geeko $ osc maintained variety openSUSE:Backports:SLE-15-SP1:Update/variety openSUSE:Backports:SLE-15-SP2:Update/variety openSUSE:Backports:SLE-15-SP3:Update/variety using sources from openSUSE:Maintenance:17349/variety.openSUSE_Backports_SLE-15-SP3_Update https://en.opensuse.org/openSUSE:Maintenance_update_process#Check_if_a_Leap_...
On 1/13/22 17:08, Lubos Kocman wrote:
If you're trying to update a SLE package please reference an issue in the SR text. Examples boo#123456 or feature jsc#SLE-12345 / jsc#OPENSUSE-12345. Submit requests without issue references will be rejected with an ask to resubmit with issue reference.
Like many time in the past this is the usual situation for me with coreutils-9.0 now: How to update a package which is also in SLE but where no boo# or whatever exists, but we just fix bugs and have some minor new features via a new upstream version, and that version has been in Tumbleweed without problems for several months? Thanks & have a nice day, Berny
Hi, On 1/13/22 5:08 PM, Lubos Kocman wrote:
this is a friendly reminder that the code submission deadline for openSUSE Leap 15.4 Beta is February 16th. Same as the code submission deadline for SUSE Linux Enterprise 15 SP4 Public Beta. SLE 15 SP4 has additionally a feature cutoff deadline of February 2nd. This is when SUSE Linux Enterprise 15 SP4 should be feature-full and we should ideally receive only bug fixes later.
Does anyone have a (semi-automated) workflow to check which of the packages one's maintaining could be relevant for a submission for Leap, i.e. comparing versions between Factory and Leap? The decision would be human step of course, for example updating just the patch release. Thanks and best regards Sebastian
Hello Sebix, Max has a tool which refreshes Leap packages from Factory. I suppose it's also semy manual. ^@Max? Lubos On Fri, 2022-01-14 at 10:38 +0100, Sebix wrote:
Hi,
On 1/13/22 5:08 PM, Lubos Kocman wrote:
this is a friendly reminder that the code submission deadline for openSUSE Leap 15.4 Beta is February 16th. Same as the code submission deadline for SUSE Linux Enterprise 15 SP4 Public Beta. SLE 15 SP4 has additionally a feature cutoff deadline of February 2nd. This is when SUSE Linux Enterprise 15 SP4 should be feature-full and we should ideally receive only bug fixes later.
Does anyone have a (semi-automated) workflow to check which of the packages one's maintaining could be relevant for a submission for Leap, i.e. comparing versions between Factory and Leap? The decision would be human step of course, for example updating just the patch release.
Thanks and best regards Sebastian
-- Best regards Lubos Kocman openSUSE Leap Release Manager
On Thu, Jan 13, 2022 at 5:08 PM Lubos Kocman <lubos.kocman@suse.com> wrote:
this is a friendly reminder that the code submission deadline for openSUSE Leap 15.4 Beta is February 16th. Same as the code submission deadline for SUSE Linux Enterprise 15 SP4 Public Beta. SLE 15 SP4 has additionally a feature cutoff deadline of February 2nd. This is when SUSE Linux Enterprise 15 SP4 should be feature-full and we should ideally receive only bug fixes later.
can we pretty please really get current stuff from different upstream projects ;) sorry to bother ddclient 7zip/7z/7-zip openvpn wireguard linux-kernel (current LTS and or with current amd platforms, hwsensors, etc.) thank you a lots i.a.
On Fri, Jan 28, 2022 at 7:30 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
can we pretty please really get current stuff from different upstream projects ;) sorry to bother ddclient 7zip/7z/7-zip openvpn wireguard linux-kernel (current LTS and or with current amd platforms, hwsensors, etc.)
moreutils moreutils-parallel how do we actually request fresh upstream stuff for already existing projects and packagtes in newer leaps? do maintainers of packages look into their sources for their maintained packages and pull in new stuff regularly? tia.
On 01/02/2022 20:59, cagsm <cumandgets0mem00f@gmail.com> wrote:
how do we actually request fresh upstream stuff for already existing projects and packagtes in newer leaps? do maintainers of packages look into their sources for their maintained packages and pull in new stuff regularly? tia.
Nothing and nobody stops you from submitting your request with changes. Matěj
On 2/2/22 07:41, mcepl@cepl.eu wrote:
On 01/02/2022 20:59, cagsm <cumandgets0mem00f@gmail.com> wrote:
how do we actually request fresh upstream stuff for already existing projects and packagtes in newer leaps? do maintainers of packages look into their sources for their maintained packages and pull in new stuff regularly? tia.
Nothing and nobody stops you from submitting your request with changes.
No, but its much nicer if you speak to the maintainer first, although they will have to review it at some point. But to answer the question more generally, for most packages its simply up to the maintainers discretion,, for SLE packages there are further rules that maintainers may also choose to apply such as not updating packages if they break there config or compatibility Leap is meant to be stable after all. -- 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
On Fri, Jan 28, 2022 at 07:30:05PM +0100, cagsm wrote:
On Thu, Jan 13, 2022 at 5:08 PM Lubos Kocman <lubos.kocman@suse.com> wrote:
this is a friendly reminder that the code submission deadline for openSUSE Leap 15.4 Beta is February 16th. Same as the code submission deadline for SUSE Linux Enterprise 15 SP4 Public Beta. SLE 15 SP4 has additionally a feature cutoff deadline of February 2nd. This is when SUSE Linux Enterprise 15 SP4 should be feature-full and we should ideally receive only bug fixes later.
can we pretty please really get current stuff from different upstream projects ;) sorry to bother
ddclient 7zip/7z/7-zip openvpn wireguard linux-kernel (current LTS and or with current amd platforms, hwsensors, etc.)
thank you a lots i.a.
fwiw the kernel will be 5.14 based + thousands of backported patches from newer kernels. For openvpn we check 2.5 update in 15.4. Ciao, Marcus
participants (11)
-
Axel Braun -
Bernhard Voelker -
cagsm -
Lubos Kocman -
Luciano Santos -
Marcus Meissner -
mcepl＠cepl.eu -
Neal Gompa -
Peter Czanik -
Sebix -
Simon Lees