On 16/02/16 17:45, Martín Ferrari wrote:
> Hi Christopher,
>
> On 15/02/16 17:40, Christopher Baines wrote:
>
>> Not sure quite how to handle this package, as I am the upstream author as
>> well.
>
> Ideally, keep the debian packaging separate from the upstream
> development. I'd recommend creating a repository on alioth (maybe in
> collab-maint?) where you can add your main repo as a remote, but only
> push debian-related commits to the alioth remote.
I am still not quite sure where I stand on this, currently I have all
the stuff related to getting the package in to a proper state for
inclusion in to Debian in a separate branch (which changes the source
format to quilt, adds a watch file and updates the changelog). Keeping a
fully working package in master has the benefit of allowing me (as the
upstream developer) to use all the useful Debian tooling (e.g. autopkgtest).
> I am the maintainer for a few prometheus packages, so if you need help
> or sponsored uploads, feel free to reach to me (I am also Tincho in
> oftc/freenode)
Thank you so much for packaging Proemtheus! Your work on it enabled me
to use it, and I use it literally every day :) Which has led on to
writing exporters to make it even more useful.
I am looking for a sponsor for the prometheus-pgbouncer-exporter
package, you can find the package on the Debian mentors site [1], or in
the debian branch of this Git repository [2].
1: https://mentors.debian.net/package/prometheus-pgbouncer-exporter
2: http://git.cbaines.net/prometheus-pgbouncer-exporter/
