Re: [Mageia-dev] Release_blocker bugs
Pascal Terjan wrote: > On Sun, Apr 8, 2012 at 15:57, David Walser wrote: > >> Anne nicolas wrote: >> > Security updates >> > = >> > To be closed after RC >> > 5046 bugsq...@mageia.org [Tracker] Security updates for Mageia 2 >> >> I could really use some help with Bug 5063 (libzip security update). It >> sounds serious, but I can't reproduce the make check error on the >> build system. >> >> I submitted it and it succeeded Just in case it wasn't clear to anyone else, the one in Cauldron is the one with the problem. It builds, but fails in make check.
Re: [Mageia-dev] Release_blocker bugs
On Sun, Apr 8, 2012 at 15:57, David Walser wrote: > Anne nicolas wrote: > > Security updates > > = > > To be closed after RC > > 5046 bugsq...@mageia.org [Tracker] Security updates for Mageia 2 > > I could really use some help with Bug 5063 (libzip security update). It > sounds serious, but I can't reproduce the make check error on the > build system. > > I submitted it and it succeeded
Re: [Mageia-dev] Release_blocker bugs
Anne nicolas wrote: > Security updates > = > To be closed after RC > 5046 bugsq...@mageia.org [Tracker] Security updates for Mageia 2 I could really use some help with Bug 5063 (libzip security update). It sounds serious, but I can't reproduce the make check error on the build system.
Re: [Mageia-dev] Release_blocker bugs
Le 06/04/2012 13:17, Anne nicolas a écrit : GNOME 3 --- 4553o...@vitters.nl Gnome 3 starts in fallback mode after boot, but Gnome Shell available after logout 4419o...@vitters.nl Change default background in gdm and default gnome-sessions (shell+fallback) 4357thierry.vign...@gmail.com [debloat] consider moving Suggests: seahorse to task-gnome 3774bugsq...@mageia.org GNOME3 on free DVD? (requires non-free drivers) Given the decision criteria given during the meeting (mainly "can't be fixed after the release"), I would only consider the last one (3774) as a release blocker. 4453 seems a past technical issue 4419 is purely a cosmetic issue, and probably easy to fix 4357 is not really a technical issue, and requires some discussion, but should not block the release if not properly fnished before 3774 just requires an (easy IMHO) decision to be made. -- BOFH excuse #47: Complete Transient Lockout
Re: [Mageia-dev] Release_blocker bugs
'Twas brillig, and Thierry Vignaud at 06/04/12 19:24 did gyre and gimble: > On 6 April 2012 19:38, Thomas Backlund wrote: >>> There was one issue regarding the kernel *bin depmods files and dracut >>> that someone reported as being due to that dracut was using kmod but the >>> kernel's *.bin files were created with m-i-t... I forget the details, so >>> not sure if it's an issue or not. >> >> Since everything else uses kmod, even if it's late in the game I think >> we should do the switch now for the userland tools too before we release >> beta3. >> >> That way the tools would be unified, and we still would have time to >> revert for RC if needed... >> >> Any objections ? > > No Sounds good to me. New kmod should be with you shortly. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Release_blocker bugs
On 6 April 2012 19:38, Thomas Backlund wrote: >> There was one issue regarding the kernel *bin depmods files and dracut >> that someone reported as being due to that dracut was using kmod but the >> kernel's *.bin files were created with m-i-t... I forget the details, so >> not sure if it's an issue or not. > > Since everything else uses kmod, even if it's late in the game I think > we should do the switch now for the userland tools too before we release > beta3. > > That way the tools would be unified, and we still would have time to > revert for RC if needed... > > Any objections ? No
Re: [Mageia-dev] Release_blocker bugs
06.04.2012 19:19, Colin Guthrie skrev: > 'Twas brillig, and Maarten Vanraes at 06/04/12 16:43 did gyre and gimble: >> Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas: >> [...] >>> Does not seem to be release_blocker >>> === >>> 4301bugsq...@mageia.org Migration of module-init-tools to kmod >>> lib in >>> Mageia 2 - specifications >>> => 4802 >> [...] >> >> i may understand this wrong, but iinm, module-init-tools doesn't work with >> current kernel anymore, and kmod is now required => doublecheck with tmb > > I'm not sure what the specifications specifically meant in this regard, > but we did used to have a lib made from module-init-tools which was then > used elsewhere. We've not dropped that lib, and now use libkmod directly > everywhere it's needed. > > The only thing we've not done is to actually use the kmod binaries for > modprobe, insmod, rmmod, lsmod, etc. > > That said, it's a simple switch in the kmod spec to turn it on (and > obsolite module-init-tools). I've mentioned this before, but no one > really picked up on it. It's very late in the day to do this switch > (although I have personally be running it for a while without any issues). > > There was one issue regarding the kernel *bin depmods files and dracut > that someone reported as being due to that dracut was using kmod but the > kernel's *.bin files were created with m-i-t... I forget the details, so > not sure if it's an issue or not. > Since everything else uses kmod, even if it's late in the game I think we should do the switch now for the userland tools too before we release beta3. That way the tools would be unified, and we still would have time to revert for RC if needed... Any objections ? -- Thomas
Re: [Mageia-dev] Release_blocker bugs
'Twas brillig, and Maarten Vanraes at 06/04/12 16:43 did gyre and gimble: > Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas: > [...] >> Does not seem to be release_blocker >> === >> 4301 bugsq...@mageia.org Migration of module-init-tools to kmod lib in >> Mageia 2 - specifications >> => 4802 > [...] > > i may understand this wrong, but iinm, module-init-tools doesn't work with > current kernel anymore, and kmod is now required => doublecheck with tmb I'm not sure what the specifications specifically meant in this regard, but we did used to have a lib made from module-init-tools which was then used elsewhere. We've not dropped that lib, and now use libkmod directly everywhere it's needed. The only thing we've not done is to actually use the kmod binaries for modprobe, insmod, rmmod, lsmod, etc. That said, it's a simple switch in the kmod spec to turn it on (and obsolite module-init-tools). I've mentioned this before, but no one really picked up on it. It's very late in the day to do this switch (although I have personally be running it for a while without any issues). There was one issue regarding the kernel *bin depmods files and dracut that someone reported as being due to that dracut was using kmod but the kernel's *.bin files were created with m-i-t... I forget the details, so not sure if it's an issue or not. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Release_blocker bugs
Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas: [...] > Does not seem to be release_blocker > === > 4301 bugsq...@mageia.org Migration of module-init-tools to kmod lib in > Mageia 2 - specifications > => 4802 [...] i may understand this wrong, but iinm, module-init-tools doesn't work with current kernel anymore, and kmod is now required => doublecheck with tmb
[Mageia-dev] Release_blocker bugs
Hi there Here is a first review of release_blocker bugs. Please have a look, comment Release Blocker (given the criteria defined during Packagers meeting) Install - 5044thierry.vign...@gmail.com lilo failed commande introuvable .. sh ligne 0 erreur d'ecriture / broken pipe 4696thierry.vign...@gmail.com Install freeze after licence acceptation (system without floppy disk in the drive) (error I/O fd0) dracut - 4298bugsq...@mageia.org [Tracker] Implement dracut in Mageia 2 - specifications => 3315, release_blocker 4364 4562 Systemd - 2120dmorga...@gmail.com [Tracker] Implement systemd in Mageia 2 - specifications => 3253 3740 3744 3817 4177 4327 4541 4672 4910 5122 5143 5148 5184 , release_blocker 4772 Upgrade 3342bugsq...@mageia.org [Tracker] Upgrade Mga 1 > Mga 2 => 4136 4150 4541 4569 5100 5103 5219 oxygen -- 5034bugsq...@mageia.org [TRACKER] Oxygen integration issues => 5132 non blocker GNOME 3 --- 4553o...@vitters.nl Gnome 3 starts in fallback mode after boot, but Gnome Shell available after logout 4419o...@vitters.nl Change default background in gdm and default gnome-sessions (shell+fallback) 4357thierry.vign...@gmail.com [debloat] consider moving Suggests: seahorse to task-gnome 3774bugsq...@mageia.org GNOME3 on free DVD? (requires non-free drivers) Wifi -- no release_blocker one but still wifi status is not good enough given the number of bugs 5015bugsq...@mageia.org TRACKER: WLAN - WIFI not or badly working in cauldron => 1015 1452 1562 1806 2160 2372 3344 3398 3798 4046 4142 4635 4963 Security updates = To be closed after RC 5046bugsq...@mageia.org [Tracker] Security updates for Mageia 2 Live CDs === We are starting tests on new set of isos (pre release) and it seems for now it's fixing blocker bugs opened on very first isos. 1812mag...@blino.orgClosing an "Advanced settings" window during live-install quits the installer without warning 3212mag...@blino.orgmgaonline/update tries to perform update on a LiveCD 3621bugsq...@mageia.org [ 2 alpha1 ] LiveCD: missing desktop/menu items for installing from the CD 3801mag...@blino.orgdrakx-finish-install doesn't set the root password and dont create/migrate the live user Others == 4999bugsq...@mageia.org Mga2 Beta2 fails to boot fully into KDE 4772bugsq...@mageia.org boot hangs at 'Starting cpufreq (via systemctl)' 4645bugsq...@mageia.org udisks is not installed from x86-64 DVD causing urpmi/rpmdrake to fail on first boot 4299bugsq...@mageia.org syslinux, gfxboot in Mageia 2 3803watersnowr...@gmail.com boot screen entries get corrupted when switching between them, highlighting for selected and unselected items not working properly 3375t...@iki.fi after hibernation system starts booting from scratch Does not seem to be release_blocker === 4301bugsq...@mageia.org Migration of module-init-tools to kmod lib in Mageia 2 - specifications => 4802 4300bugsq...@mageia.org General artwork in Mageia 2 - specifications => 41 107 261 1919 3898 3900 4181 4269 4419 4651 4858 5049 5211 (no release_blocker bug) -- Anne http://www.mageia.org
Re: [Mageia-dev] Release_blocker bugs
Le jeudi 08 mars 2012 à 09:37 +0100, Michael Scherer a écrit : > Le mercredi 07 mars 2012 à 21:43 +0100, Manuel Hiebel a écrit : > > Hello, > > > > How can we (the bugsquad or other people) determinate what can be a > > release_blocker bug ? > > > > in the triage guide we can see: > > > > "The release_blocker priority is only relevant to bugs filed on Cauldron > > or beta releases, and should only be used for issues which are > > sufficiently critical that it would severely impair the overall quality > > of a release if it were made available without the issue being > > resolved." > > > > That is not clear for me. And the only mail relating to that, was from > > Anne in May and not useful for me. > > I would say "stuff that cannot be fixed after release" would be release > blocker. Not to say that the rest cannot be too, but at least, that's > the first criteria. > > So a software on livecd that crash on startup would also be a blocker. > Ok thanks, I will keep that in mind.
Re: [Mageia-dev] Release_blocker bugs
Le mercredi 07 mars 2012 à 21:43 +0100, Manuel Hiebel a écrit : > Hello, > > How can we (the bugsquad or other people) determinate what can be a > release_blocker bug ? > > in the triage guide we can see: > > "The release_blocker priority is only relevant to bugs filed on Cauldron > or beta releases, and should only be used for issues which are > sufficiently critical that it would severely impair the overall quality > of a release if it were made available without the issue being > resolved." > > That is not clear for me. And the only mail relating to that, was from > Anne in May and not useful for me. I would say "stuff that cannot be fixed after release" would be release blocker. Not to say that the rest cannot be too, but at least, that's the first criteria. So a software on livecd that crash on startup would also be a blocker. -- Michael Scherer
Re: [Mageia-dev] Release_blocker bugs
On 07/03/12 20:43, Manuel Hiebel wrote: Hello, How can we (the bugsquad or other people) determinate what can be a release_blocker bug ? in the triage guide we can see: "The release_blocker priority is only relevant to bugs filed on Cauldron or beta releases, and should only be used for issues which are sufficiently critical that it would severely impair the overall quality of a release if it were made available without the issue being resolved." That is not clear for me. And the only mail relating to that, was from Anne in May and not useful for me. So what about for release blockers: An default installed soft not working out of the box ? Any soft that cannot be launched ? Issue that a lot people can have ? something other ? Comments is welcome, thanks BTW: The current one are: https://bugs.mageia.org/buglist.cgi?priority=release_blocker&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED And related to trackers (also set to release blocker) https://bugs.mageia.org/showdependencytree.cgi?id=1994&hide_resolved=1 Could bug 2317 please be added as a release blocker for final release.
[Mageia-dev] Release_blocker bugs
Hello, How can we (the bugsquad or other people) determinate what can be a release_blocker bug ? in the triage guide we can see: "The release_blocker priority is only relevant to bugs filed on Cauldron or beta releases, and should only be used for issues which are sufficiently critical that it would severely impair the overall quality of a release if it were made available without the issue being resolved." That is not clear for me. And the only mail relating to that, was from Anne in May and not useful for me. So what about for release blockers: An default installed soft not working out of the box ? Any soft that cannot be launched ? Issue that a lot people can have ? something other ? Comments is welcome, thanks BTW: The current one are: https://bugs.mageia.org/buglist.cgi?priority=release_blocker&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED And related to trackers (also set to release blocker) https://bugs.mageia.org/showdependencytree.cgi?id=1994&hide_resolved=1
[Mageia-dev] release_blocker bugs
Hi there Another item to follow on a weekly base will be release_blocker bugs https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=release_blocker&sharer_id=5 Please have a look reporters and packagers. Cheers -- Anne http://www.mageia.org
