[Bug 371745] New: block / remove packages that are broken from repositories
https://bugzilla.novell.com/show_bug.cgi?id=371745 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c370121 Summary: block / remove packages that are broken from repositories Product: openSUSE 11.0 Version: Alpha 2 Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: jsrain@novell.com CC: maw@novell.com, coolo@novell.com, sbrabec@novell.com, rguenther@novell.com, casualprogrammer@yahoo.com Found By: Beta-Customer +++ This bug was initially created as a clone of Bug #370121 +++ As demonstrated (once again) by Bug 370121 packages are recognized as broken, yet not only does the fix not get distributed immediately, but also the broken packages are left in place or get replaced by an updated broken package, thus letting numerous people break their systems and also creating a flood of unnecessary bug reports. This should be handled in a more user friendly manner. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c1 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Update Problems |BuildService Product|openSUSE 11.0 |openSUSE.org QAContact|jsrain@novell.com |adrian@novell.com Version|Alpha 2 |unspecified --- Comment #1 from Stephan Kulow <coolo@novell.com> 2008-03-17 08:31:25 MST --- can't be done with the current system, but something to consider for build service -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User rguenther@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c2 --- Comment #2 from Richard Guenther <rguenther@novell.com> 2008-03-17 08:38:07 MST --- An archive of old package versions would be a nice thing to have. Or a general staging of Factory, like there is 'testing' and 'unstable' in Debian (even opening BETA as an 'experimental' equivalent would be nice). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c3 --- Comment #3 from Stephan Kulow <coolo@novell.com> 2008-03-17 09:11:59 MST --- sorry, but Factory _is_ our testing. Old versions are often asked for, but Factory is just too big to make that feasible ;( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c4 --- Comment #4 from Casual J. Programmer <casualprogrammer@yahoo.com> 2008-03-18 01:42:27 MST --- I am not sure I am viewing this correctly, but there are http://download.opensuse.org/distribution/openSUSE-stable/ as well as http://download.opensuse.org/distribution/openSUSE-current/ both are frozen and offering a state of 04-Oct-2007 06:49 I would have assumed, that proven alpha/beta packages go to stable from factory, so anybody experiencing a broken package can easily go back to the status quo ante. I currently keep a copy of the iso images locally, but they don't reflect the progress made with proven, tested packages. Please review. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c5 --- Comment #5 from Stephan Kulow <coolo@novell.com> 2008-03-18 01:47:48 MST --- both are symlinks to 10.3 - the http protocol just has no concept of symlinks. I guess I should move -current to alpha2 actually -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |adrian@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User adrian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c6 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|adrian@novell.com |freitag@novell.com Summary|block / remove packages that are broken from |changelog system: auto close bugzilla entries |repositories |with refered project and package name, including | |version and source release number. --- Comment #6 from Adrian Schröter <adrian@novell.com> 2008-07-09 01:41:01 MDT --- I doubt that we can do anything about the basic problem that changes are not distributed immediatly (at least only of the price of inconsitent builds and lots of other problems). What we can do, is predicting the version/release number in which a bug is fixed on submission time. So we can add automatically a bugzilla comment & setting it to fixed including this information. So the bugreporter can see when this package appears and check this one. This is something for our next generation change log system, so I assign this to our architect therefore :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371745 User casualprogrammer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=371745#c7 --- Comment #7 from Casual J. Programmer <casualprogrammer@gmail.com> 2009-01-14 12:41:18 MST --- No activity for 6 month, is it worth to keep it open ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com