Bug#685230: unblock hylafax 3:6.0.6-4
Hello!
Ivo De Decker wrote on 2012-12-22 22:35:
> As there is still an RC bug in sid, I don't think it makes sense to do a TPU
> upload for the other one now. I'm attaching the TPU fix for 682824 for
> reference.
As said I will try to update capi4hylafax because of this RC bug. If I can
fix this RC in capi4hylafax, then I must move this bug to the capi4hylafax
package before upload, right?
> It might be best to revert all the changes in unstable (since -1) that are not
> suitable for wheezy, and try to get a version in unstable that fixes both RC
> bugs in a non-intrusive way (based on -1). That way, the package could be
> tested in unstable before it gets to wheezy. The changes that are in -2 could
> go to experimental for now.
Which is the best way?
a) create the updated version 3:6.0.6-5 which is the same as 3:6.0.6-1
and then create the next version 3:6.0.6-6 which all needed patches
for Wheezy, or
b) create the updated version 4:6.0.6-1 which is the same as 3:6.0.6-1
and then create the next version 4:6.0.6-2 which all needed patches
for Wheezy, or
c) create a special Wheezy version 3:6.0.6-2+deb7u1 with all needed patches
for Wheezy.
What is your opinion? I would prefer way c).
---
Have a nice day.
Joachim (Germany)
Reply to: