Hi, (this is maybe more to pkg-privacy-maintainers@ than to -release@, maybe not.)
On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> Thanks. Please go ahead.
so far I've only tested binary builds of these changes and when doing a source
build now I realized that cherry-picking these patches of course changed the
source and thus debuild -S failed like this:
dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/torbrowser-launcher_0.1.9-1+deb8u2.diff.1bVtM1
dpkg-source: info: you can integrate the local changes with dpkg-source --
commit
I then ran "dpkg-source --commit" which indeed created one big patch with all
the changes from the cherry-picked commits and the actual source code
modifications reverted.
Obviously I could upload this as it is but currently I'm not yet convinced
this is the best course of action… as this will make further maintenance a bit
more annoyed and this is exactly why I sympathised with the idea of uploading
0.2.2 to stable in the first place.
Oh well, I will go afk to think about this. Comments or other ideas welcome.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
