Re: upstream release of unreleased package

2019-02-21 Thread lluvia
Hello, I continue trying to fix issue. In a clean directory, I tried to follow all the steps from https://wiki.debian.org/Python/GitPackaging without git-pushing to see if I was able to understand better what I did bad last time. I followed the sections "Creating new repositories" using

Re: upstream release of unreleased package

2019-02-21 Thread Dmitry Shachnev
Hi Daniel, On Thu, Feb 21, 2019 at 09:15:59PM +, llu...@autistici.org wrote: > I paste below a (reproducible) log of what I did. Maybe you can show me what > I did wrong this time so I am not able to build package for 0.3.8. > > [...] > $ gbp buildpackage --git-tag-only > gbp:info: Tagging

Re: upstream release of unreleased package

2019-02-21 Thread lluvia
Hi Dmitry, On 2019-02-21 21:54, Dmitry Shachnev wrote: And I cannot reproduce the failure that you are getting later. Does this mean you are using git-buildpackage older than 0.8.0? Yes, it was older. With 0.8.12.2 I success. Thanks a lot for solving the mystery, I will use version 0.8.12.2

Re: upstream release of unreleased package

2019-02-21 Thread lluvia
Hello, Now that my system is working properly I propose a solution for the repository. It is based in git-revert the three branches (debian/master, upstream and pristine-tar) and invoke gbp import-orig with option --upstream-tag=upstream/0.3.8-aux. I paste a log of my proposal. Do you think

Bug#922938: RFS: python-css-parser/1.0.4-1~bpo9+1

2019-02-21 Thread Nicholas D Steeves
Package: sponsorship-requests Severity: normal Justification: necessary for to update the bpo for Calibre Dear mentors, I am looking for a sponsor for my package "python-css-parser" Package name: python-css-parser Version : 1.0.4-1~bpo9+1 Upstream Author : Christof Hoeke, Walter