Bug#864251: RFS: quark-sphinx-theme/0.5.0-1

[Felix Krull]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "quark-sphinx-theme"

* Package name: quark-sphinx-theme
  Version : 0.5.0-1
  Upstream Author : Felix Krull 
* URL : https://pypi.python.org/pypi/quark-sphinx-theme
* License : BSD
  Section : python

It builds those binary packages:

 python-quark-sphinx-theme - Sphinx theme designed for QTextBrowser (Python 2)
 python3-quark-sphinx-theme - Sphinx theme designed for QTextBrowser (Python 3)

To access further information about this package, please visit the
following URL:

 https://mentors.debian.net/package/quark-sphinx-theme

Alternatively, one can download the package with dget using this command:

 dget -x 
https://mentors.debian.net/debian/pool/main/q/quark-sphinx-theme/quark-sphinx-theme_0.5.0-1.dsc

Changes since the last upload:

 * Import quark-sphinx-theme_0.5.0.orig.tar.bz2
 * debian/control: update build dependencies to include tinycss and mock.
 * debian/copyright: update copyright.

This is an upload for a new upstream release. Since tinycss is now
packaged in Debian,
I could also finally enable that dependency for the tests.

Regards,
Felix Krull

Re: PAPT git migration

[Mattia Rizzolo]

On Fri, Jun 02, 2017 at 04:23:20PM +0200, Raphael Hertzog wrote:
> Hi,
> 
> On Thu, 01 Jun 2017, Brian May wrote:
> > On 2017-06-01 07:32, Barry Warsaw wrote:
> > 
> > > Let's assume not (which is fine with me; i.e. why adopt git-dpm for PAPT 
> > > when
> > > we know we just want to get rid of it later?).  Then i tried to import a 
> > > new
> > > upstream as described here https://wiki.debian.org/Python/GitPackagingPQ
> > 
> > Another problem I have noticed with that document - but not had time to
> > come up with a solution yet. 
> > 
> > There are several places where "git push --all" (or variant) is
> > recommended. But this will also push the gbp pq branch(es), which should
> > never get pushed.
> 
> "git push origin : --tags" is what I use in general, it pushes branches
> available on both sides and tags.


I have recently discovered the config push.followTags=true, which pushes
all tags which reference objects that are being pushed.
That should save the '--tags' flag :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature