From: "Philip Tellis"
Well, as a sidenote, please note that upstream always avoid '-' (dash) in version scheme :)
Doesn't debian use - to mark its own patch level? If that is the case, then I'd suggest patching upstream directly and building your package off of CVS. Ayttm doesn't release all patch level versions, but every single CVS commit raises the patch level. This will probably change when we go to 1.0.
Hi,
Fixed. No issue with version 0.5.0-6, since Debian consider last - (dash) as Debian revision number.
Cheers, Kartik
On 20/08/07, Kartik Mistry kartik.mistry@gmail.com wrote:
Fixed. No issue with version 0.5.0-6, since Debian consider last - (dash) as Debian revision number.
Well, my question was more about whether Debian can just use ayttm's revision number as its own, since ideally there should be no patch that is in the debian release but not in the ayttm source tree.
I'll let Siddhesh make the commitment, but basically, if the ayttm devs commit to getting debian patches into CVS (after suitable review) quick enough, then is it necessary to have a separate patch? Or is it necessary that debian patches be against released tarballs only?
On 20/08/07, Kartik Mistry kartik.mistry@gmail.com wrote:
Fixed. No issue with version 0.5.0-6, since Debian consider last - (dash) as Debian revision number.
Well, my question was more about whether Debian can just use ayttm's revision number as its own, since ideally there should be no patch that is in the debian release but not in the ayttm source tree.
I'll let Siddhesh make the commitment, but basically, if the ayttm devs commit to getting debian patches into CVS (after suitable review) quick enough, then is it necessary to have a separate patch? Or is it necessary that debian patches be against released tarballs only?
On 8/21/07, Philip Tellis philip.tellis@gmail.com wrote:
Well, my question was more about whether Debian can just use ayttm's revision number as its own, since ideally there should be no patch that is in the debian release but not in the ayttm source tree.
I guess we should be OK as long as we in sync. It could be problematic only if a Debian patch is rejected upstream for some reason (unlikely?).
I'll let Siddhesh make the commitment, but basically, if the ayttm devs commit to getting debian patches into CVS (after suitable review) quick enough, then is it necessary to have a separate patch? Or is it necessary that debian patches be against released tarballs only?
I'm OK with it ( I'm assuming quick means within a couple of days, not hours unless it's a critical fix ;) ).
-
Kartik Mistry -
Philip Tellis -
Philip Tellis -
Siddhesh Poyarekar