List Info

Thread: to commit or not to commit (yet)?




to commit or not to commit (yet)?
user name
2006-03-27 10:30:47
After a very long break, last sunday I resumed my hlfs work
on cvs and on 
friday I could finally finish the entire build without any
errors.  However, 
the grsecurity patch conflicts with these:
openswan natt patch
openswan klips patch

With these two and grsecurity applied, the installer kernel
oopses very early 
on.  With just the grsecurity patch applied, it loads fine. 
With these 
applied and grsecurity applied but disabled, the resulting
kernel still 
oopses in the same manner.

The question is: Do you want me to commit my changes now, or
after I try to 
isolate the problem?  If I commit now, more people will be
able to give it a 
try and have a better chance of finding the offender
quicker.  If I hold off 
committing, it might take me awhile because I can't be
burning and testing 
cds at work, so I'll be limitted to only a couple hours a
day, after work, 
and of course weekends.

What's the consensus?

IvanK.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

to commit or not to commit (yet)?
user name
2006-03-27 10:39:35
Le Lundi 27 Mars 2006 12:30, Ivan Kabaivanov a écrit :
> After a very long break, last sunday I resumed my hlfs
work on cvs and on
> friday I could finally finish the entire build without
any errors. 
> However, the grsecurity patch conflicts with these:
> openswan natt patch
> openswan klips patch
>
> With these two and grsecurity applied, the installer
kernel oopses very
> early on.  With just the grsecurity patch applied, it
loads fine.  With
> these applied and grsecurity applied but disabled, the
resulting kernel
> still oopses in the same manner.
>
> The question is: Do you want me to commit my changes
now, or after I try to
> isolate the problem?  If I commit now, more people will
be able to give it
> a try and have a better chance of finding the offender
quicker.  If I hold
> off committing, it might take me awhile because I
can't be burning and
> testing cds at work, so I'll be limitted to only a
couple hours a day,
> after work, and of course weekends.
>
> What's the consensus?
>
> IvanK.
>

Commit with explaining somewhere easily found/read 
where howto disable offending modules.

Franck


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http:
//sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$
1720&dat1642
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )