fai bugs against policy - lets get this fixed NOW...

[Holger Levsen]

unblock 340608 by 212434 
unblock 340608 by 230217 
unblock 340608 by 344158
unblock 311524 by 212434 
unblock 311524 by 230217 
unblock 311524 by 344158
unblock 315080 by 212434 
unblock 315080 by 230217 
unblock 315080 by 344158
unblock 336650 by 212434 
unblock 336650 by 230217 
unblock 336650 by 344158
thanks

Hi,

those four bugs I just unblocked all where blocked by FHS 2.3 not in policy. 

But they were all violating policy (the blocker was only there because Thomas 
didnt want to fix them at that time against FHS 2.x and then later again 
against 2.3) therefore they all have the wrong severity, "important" instead 
of "serious". 

Therefore I could adjust the severity to "serious" and do/propose a 0-day NMU 
now. But as we discussed this long time ago, I wont play "BTS games", though 
I actually now fail to see why this would be a BTS game. (IIRC we rather 
agreed that Thomas would fix them soon anyway..)

The new version of policy has been uploaded in april, some of those four bugs 
are more than three years known. Thomas, I would really really really be 
happy if you fix these simply bugs _before_ the developer weekend. At least I 
am completly unhappy to work on fai with this wrong pathes which have been 
there for ages (and two of them only requiere changes of the default 
configuration values!! (and the others also only requiere find and replace 
skills))

If you'd fix them before the developer weekend, we could use the weekend to 
test the changes and spend energy on useful stuff. (I am changing those 
pathes everytime I do anything with fai because I cannot 
see /usr/local/share/fai or /usr/lib/fai/nfsroot anymore - it's just plain 
wrong and I've wasted too much time with this.)

Also as I see it you will now upload a new fai version anyway, to fix the 
incorrectly NMUed package: as I see it also the 2nd NMU is broken, the 
fai-apt-conf needs to be deleted from $target/... and neither from 
$FAI_ROOT/... nor /... (but I might be too tired to see this correctly :)


BTW, please note that the 0-day NMU was formally "only" wrong in the sense 
that it was not tested.
 
Steinar, still I'd suggest that you handle the 0-NMU policy more "friendly", 
that is, wait for example 24h before uploading, but send the proposed patches 
to the BTS immediatly. If the package is well maintained, like fai, 24h is 
fair to the maintainer. And if the last upload is 3 years ago, waiting one 
more day wont hurt anymore as well :)


regards,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.uni-koeln.de/pipermail/linux-fai-devel/attachments/20060710/6ef40ecf/attachment.bin