Bugzilla – Bug 371745
changelog system: auto close bugzilla entries with refered project and package name, including version and source release number.
Last modified: 2012-01-26 15:25:19 UTC
+++ 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.
can't be done with the current system, but something to consider for build service
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).
sorry, but Factory _is_ our testing. Old versions are often asked for, but Factory is just too big to make that feasible ;(
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.
both are symlinks to 10.3 - the http protocol just has no concept of symlinks. I guess I should move -current to alpha2 actually
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 :)
No activity for 6 month, is it worth to keep it open ?
Another 9 month passed by...