> damn...I knew I made a mistake with the feisty stuff...let me fix it.
> Dapper and Edgy do have dpatch as build-dep but don't use it anywhere.
I think it works -- they just have no debian/patches directory. It
looks like the debian/rules file uses it correctly ("patch", "unpatch"
are called). Go ahead and add the directory and the patch there.
That'll make a clean update for future fixes too.
> Feisty and Gutsy are using dpatch for sure.
>
> libwzd-core/wzd_protocol.c is not in the versions of dapper and edgy.
> The fixed part in dapper and edgy are libwzd-core/wzd_ClientThread.c
Ah-ha, that explains it. :)
> Should I remove the dpatch from build-deps in dapper and edgy?
No, dpatch is required for the build; dapper and edgy just happen to not
have any patches (yet).
> damn...I knew I made a mistake with the feisty stuff...let me fix it.
> Dapper and Edgy do have dpatch as build-dep but don't use it anywhere.
I think it works -- they just have no debian/patches directory. It
looks like the debian/rules file uses it correctly ("patch", "unpatch"
are called). Go ahead and add the directory and the patch there.
That'll make a clean update for future fixes too.
> Feisty and Gutsy are using dpatch for sure. core/wzd_ protocol. c is not in the versions of dapper and edgy. core/wzd_ ClientThread. c
>
> libwzd-
> The fixed part in dapper and edgy are libwzd-
Ah-ha, that explains it. :)
> Should I remove the dpatch from build-deps in dapper and edgy?
No, dpatch is required for the build; dapper and edgy just happen to not
have any patches (yet).
Thanks!