sean finney wrote: > hi everyone, Hi
> excuse the cross-posting, i just want to make sure everyone's on the > same page for what should be next for php5 -> lenny Ok, though I don't think it's that controversial :-) > someone suggested to look at using testing-security as a path to lenny for > this change since many (but not all) of the fixes are security related > it feels a little sketchy to me to be honest, so i was hoping for a direct > ACK/NACK on that from the security/release folks. particularly, if it does > go through testing-security, i'd want to know that when lenny becomes stable > that the packages are somehow transitioned as well. I don't see any reason why it can't go via testing-security personally. Note that currently testing-security uploads reach tpu automatically and are processed by the Release Team to get it into lenny proper. > for better review i've attached a second diff, which is the result > of unpacking both versions of package, applying all the quilt patches, > removing the ".pc" quilt directories, and and doing a diff between the two > patched trees (diff -x debian -Nrub lenny1 lenny2). this should hopefully > make examining the changes from the quilt patches a little easier. Thanks, appreciated. > so please let us know whether this is suitable for either/neither the t-p-u > route or the testing-security route, and if neither, what needs to be done > to get something to lenny. If testing-security is not wanted, t-p-u is fine by me. Cheers Luk -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
