Santiago Vila writes:
>
> Please cancel the NMU, as it has a version number higher than the
> upload I've just made and it already contains your changes.
>
Done.
You can cancel the NMU or just let it expire and be autorejected,
at your option.
Oops, no, what I said is not ok.
Please cancel the NMU, as it has a version number higher than the
upload I've just made and it already contains your changes.
Thanks.
El 15/3/25 a las 20:55, David Bremner escribió:
Would it make a big difference if I put the diff between
old and new tarball as a patch in debian/patches ?
I guess git history would be a little bit more clear that way.
It's your call, but I personally would not carry upstream changes in
debian
Santiago Vila writes:
> Hi.
>
> Thanks for the NMU. The debdiff is a little messy indeed.
>
> I'm considering to make a proper "team upload" from this
> (with attribution of course).
>
> Would it make a big difference if I put the diff between
> old and new tarball as a patch in debian/patches ?
Santiago Vila writes:
> Maybe what scares me is the number of dgit artifacts.
>
> At the very minimum, I'd try to make a team upload without them.
>
> Thanks.
Sure, whatever you think is best.
Maybe what scares me is the number of dgit artifacts.
At the very minimum, I'd try to make a team upload without them.
Thanks.
Hi.
Thanks for the NMU. The debdiff is a little messy indeed.
I'm considering to make a proper "team upload" from this
(with attribution of course).
Would it make a big difference if I put the diff between
old and new tarball as a patch in debian/patches ?
I guess git history would be a little
Control: tags 1098664 + patch
Dear maintainer,
I've prepared an NMU for afew (versioned as 3.0.1.post63-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
David
diff -Nru afew-3.0.1/afew/configparser.py afew-3.0.1.post63/afew/configparser.py
---
8 matches
Mail list logo
