On 04/16/2018 08:23 AM, Gianfranco Costamagna wrote:
> I hope I did read it correctly, and the workflow is completely correct, also
> git history should be ok now
>
> lets see how the merge looks!
> https://salsa.debian.org/openstack-team/python/python-msgpack/merge_requests/1
>
> thanks
>
>
Hello,
>You'd just "git merge -X theirs 0.5.6", edit the changelog, and then run
>again:
>
>./debian/rules gen-orig-xz
>
>to generate the new orig tarball based on the new upstream tag.
the tarball didn't change, same
0d0cbcde2ed8e903bf0da729fd385663 ../python-msgpack_0.5.6.orig.tar.xz
On 04/15/2018 06:55 PM, Gianfranco Costamagna wrote:
> Hello,
>
>
>> ./debian/rules fetch-upstream-remote
>> ./debian/rules gen-orig-xz
>
>
> I cloned, run the two commands, updated the changelog and uploaded in
> deferred/10, thanks!
>
> I don't know how to mix the upstream commits and the
Hello,
>./debian/rules fetch-upstream-remote
>./debian/rules gen-orig-xz
I cloned, run the two commands, updated the changelog and uploaded in
deferred/10, thanks!
I don't know how to mix the upstream commits and the debian history, so for now
I prefer
to avoid sending a pr unless I find
It is ok to NMU if you send the debdiff to the BTS and upload to delayed queue.
Bonus point if you send a pull request to the BTS. Note that we use a git based
workflow, so you must:
./debian/rules fetch-upstream-remote
./debian/rules gen-orig-xz
Sent from my Cyanogen phone
On Apr 15,
Source: python-msgpack
Version: 0.5.1-3
Severity: important
Dear maintainer, can you please update to 0.5.6, borgbackup has issues with
previous versions, see [1]
thanks!
I can NMU if needed, just let me know!
Gianfranco
[1] [18:38:34] zigo, please update msgpack? rationale is there
6 matches
Mail list logo
