http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c5 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |okurz@suse.com Severity|Normal |Major --- Comment #5 from Oliver Kurz <okurz@suse.com> --- (In reply to Stephan Kulow from comment #4)
perhaps this is better tracked as SP3 bug - to actually get attention
yes, good idea. I can write a script to clone every openSUSE bug to SLE tomorrow ;-) Honestly, I don't consider cloning bugs with no further information just to raise attention is not a sustainable workflow. Leap bug reports by default in components like "basesystem" or "kernel" should also be tracked for SLE and also Tumbleweed should be crosschecked for issues which have been "backported" already or do apply nevertheless. recent example on openSUSE Leap 42.3: https://openqa.opensuse.org/tests/379388#step/yast2_clone_system/13 recent example on SUSE Linux Enterprise Server 12 SP3 build 0313: https://openqa.suse.de/tests/855580#step/yast2_clone_system/13 At least with the previously auto-generated comments the bug can be found with queries like https://bugzilla.suse.com/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=REOPENED&bug_status=RESOLVED&chfieldfrom=3w&chfieldto=Now&f1=longdesc&f2=bug_status&known_name=open%2Bosd_referenced%2Bchange-3w&list_id=6202124&o1=regexp&o2=notsubstring&query_based_on=open%2Bosd_referenced%2Bchange-3w&query_format=advanced&v1=This%20bug%20is%20still%20referenced%20in%20a%20failing%20openQA%20test.%2Aopenqa.suse.de already -- You are receiving this mail because: You are on the CC list for the bug.