Quoting Mark Brown ([email protected]): > This *really* sounds like you've got an issue with your tools here.
Indeed, one day or another, such changes will flow in the files. IN that case, because gettext tools have evolved slightly. Anyway, this is of low importance. > > All this is exactly the reason for a delayed NMU with a delay that is > > as long as possible. Please note that I used an NMU as very last > > option: for whatever reason, I saw no answer to my "ping" mails. I > > really didn't want to be invasive or appear as "aggressive", indeed... > > I've answered every mail except the very last one. Half the problem I think that's most of the problem. For whatever reason, I missed those answers (high mail rate at my place? More likely I was unsubscribed to the PTS). So, I was thinking that, for whatever reason you were unavailable. > from my point of view is that the whole translation process creates very > long delays, meaning that by the time you're actually ready for > maintainers to do anything all sense of urgency that might have existed > is lost. In this case, there is no real urgency. It's just that the package gets high on my survey "radar" because it has several translation updates that are pending. And as I can't do all this work in months before the release, I start early in the release process....:) > > Anyway, like I say I've now cleaned up after the NMU. Hopefully I'll > get time to restore the stuff I was working on later. Sounds like it would be really really better if I hold off the NMU in the delayed queue and let you process things the way you prefer, no? Or is it too late already (the NMU will reach unstable in only 9 days so we have plenty of time to discuss this..:-))= --
signature.asc
Description: Digital signature
