Or we can do such as Debian and its apt-listbugs. For people who don't know that, it's a "script" that works with apt-get and when we do an apt-get install/upgrade/dist-upgrade, we receive a report with eventual bugs (open or closed). So it will be a nice idea I think and it's independant from the mailing-list or forum and what you want.
Attila a écrit : > On Freitag, 9. Dezember 2005 07:39 Benoit Chesneau wrote: > >> Think mailing-list is the best way to get information about futures >> changes since mail client is always loaded. On the contrary rss reader >> or brower force us to think about it. > > A rss header arrives here in the same automatic way as an email so i like this > rss feeds very much. But it is right that email is the no. 1 on the list what > have the most users installed. > >> I specify "future" changes because what we neetd is to be inform before >> the changes not after. The problem is to prepare the update not to >> repair after the update. Nobody answered about this. Seems this isn't >> the problem for some mainteners/developers as I see in answers... Just >> to insist more about it, we have more and more problem since 5-7 months >> after updates and if some people don't think this isn't a problem to >> have to spend 2 hours to try to find a solution or a patch (especially >> when we can't downgrade or have problem to downgrade), I think this a >> very annoying problem. I can't spend 2 hours sometimes when I have a >> custommer to deliver. And I haven't this problem months ago. > > Okay, i have no customers so my situation is another because i spent only my > private time where the only pressure is my girlfriend is something is > broken.-) And if you say that since 5-7 months the updates getting worser i > can only say that i use arch since about this period and the update situation > is for me very much better than the former distro what i have used. > > And this big step to the new gcc including a new kde was here on two pc's an > update without any problem. I don't think a lot of other distros will do this > in the same perfect way without the danger of an new installation. > > I never make an automatic updates so the cycle is for me even: First i read > about an update in my rss feedreader and then i make a pacman -Syu. During > this time i have a look on some packages what have changed and so i can even > control what happens ... if i understand it.-) I don't know if you have the > time to do the same on a test pc where perhaps the testing repo is activ and > you have a tool as at example trueimage to step back to the last working. > configuration. Vmware is from my view the best idea for testings of such > things. > > See you, Attila > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
