[yast-devel] All changes have to have ID (bnc, CVE, etc. )
Hi, For master we need to have for all changes ID (bnc, CVE, etc. ), otherwise automatic script decline it. If needed, new bug just for this purpose can be used. Goal is that due to new SUSE core initiative there is script that ensure all IDs for SLE12SP1 is also in opensuse factory. If such IDs is missing plan is to open bug report that it missing ( similar like we have hardening for SLE12 ). Currently only problematic package is yast2-devtools. I am adding to CC coolo, so he can answer your question or add parts that I forget. Thanks Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 6.5.2015 10:57, Josef Reidinger wrote:
Hi, For master we need to have for all changes ID (bnc, CVE, etc. ), otherwise automatic script decline it. If needed, new bug just for this purpose can be used. Goal is that due to new SUSE core initiative there is script that ensure all IDs for SLE12SP1 is also in opensuse factory. If such IDs is missing plan is to open bug report that it missing ( similar like we have hardening for SLE12 ). Currently only problematic package is yast2-devtools.
I am adding to CC coolo, so he can answer your question or add parts that I forget.
I've just fixed a build by adding BuildRrequires, and I guess that "all changes" really means "all changes", so I need to create a bugreport? What about GitHub issue? Is that also accepted? In which format? Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06.05.2015 11:01, Lukas Ocilka wrote:
On 6.5.2015 10:57, Josef Reidinger wrote:
Hi, For master we need to have for all changes ID (bnc, CVE, etc. ), otherwise automatic script decline it. If needed, new bug just for this purpose can be used. Goal is that due to new SUSE core initiative there is script that ensure all IDs for SLE12SP1 is also in opensuse factory. If such IDs is missing plan is to open bug report that it missing ( similar like we have hardening for SLE12 ). Currently only problematic package is yast2-devtools.
I am adding to CC coolo, so he can answer your question or add parts that I forget.
I've just fixed a build by adding BuildRrequires, and I guess that "all changes" really means "all changes", so I need to create a bugreport?
You can also reuse an existant bugreport. E.g. if you need to submit yast2-network to fix a bug and your master requires new yast2-devtools stuff, add a changelog entry to devtools referencing that bug. You can use this list: bnc#, cve-, fate#, boo#, bsc# and bgo# Greetings, Stephan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVJ3hwACgkQwFSBhlBjoJZNQwCgjyeSFCvZ6Y61SAJctNrdl+5j st8AoJ1AKWk+XR5S1PVPJtCMp1KS+Cbc =NQpf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Josef Reidinger -
Lukas Ocilka -
Stephan Kulow