Package: sponsorship-requests
Severity: important
Dear mentors,
Following #841876, I am looking for a sponsor for the package "ucommon":
gbp clone https://anonscm.debian.org/git/pkg-voip/ucommon.git
For verification, these are the current branch heads:
git show-ref --heads
48abd035fefb6d
OK, I've added:
- a manpage
- patat to DHG's package-plan
I hope everything is good now...
signature.asc
Description: PGP signature
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "qspeakers"
* Package name: qspeakers
Version : 1.0-1
Upstream Author : Benoît Rouits
* URL : http://brouits.free.fr/qspeakers/
* License : GPL-3+
On 2016-10-23 11:51-0700, Sean Whitton wrote:
> You should use "Forwarded: not-needed" (see DEP-3).
This does not seem to work with gbp-pq (see #785274), I propose to add this as
soon as gbp-pq supports DEP-3.
>>> 2. You can fix all of these Lintian tags, except possibly
>>> hardening-no-fortify-
Hi again
>If builders can't pick it up, it means that something else in the toolchain is
>blocking
>it.
and now we have the good reason:nodejs is not available anymore on armel,
so you have to file an RM bug
against ftpmasters if you want to see it migrate.
e.g.
https://bugs.debian.org/cgi-
On Sun, Oct 23, 2016 at 06:02:05PM +, Gianfranco Costamagna wrote:
> just a question, why aren't you packaging the Python2 version?
> (the question is that I would like to avoid another binNEW queue in case some
> other people asks for it)
In this document
https://www.debian.org/doc/packagi
Hi,
>available at the time of building r-cran-knitr. However, this seems
>to have fixed now since r-base-core=3.3.1.20161024-1 is now available
>for all architectures. If my assumption that testing migration of
>r-cran-knitr is blocked due to the missing armel Build-Dependency -
>how can I ask f
Hi,
as far as I can see here[1] there was no
r-base-core:armel (>= 3.3.1.20161024-1)
available at the time of building r-cran-knitr. However, this seems
to have fixed now since r-base-core=3.3.1.20161024-1 is now available
for all architectures. If my assumption that testing migration of
r-cr
Package: sponsorship-requests
Severity: normal [wishlist]
Dear mentors,
I am looking for a sponsor for my package "highlighterpdf"
* Package name: highlighterpdf
Version : 0.7-1
Upstream Author : Gerry Webster https://mentors.debian.net/package/highlighterpdf
Alterna
Package: sponsorship-requests
Severity: wishlist
Dear mentors (cc debian-python),
I am looking for a sponsor for my package "bundlewrap":
* Package name: bundlewrap
Version : 2.9.1
Upstream Author : Torsten Rehn
Peter Hofmann
Tim Buchwald
Hello, pabs.
On 18-10-2016 11:42, Paul Wise wrote:
>
> You may want to run lintian and check-all-the-things over it, there
> are some things like spelling errors and resource leaks that should
> get fixed upstream.
I had run lintian, but not check-all-the-things. Thanks for the tip.
I got most o
On Tue, Oct 25, 2016 at 06:46:51AM +, Gianfranco Costamagna wrote:
> I would have sponsored in deferred/4, but deferred is not working :)
> there is no indication of a fix in progress, the bug is two months old
> and it was planned to become rc soon.
> The maintainer didn't answer, so even if
On 25/10/2016 08:53, Jonathan Carter (highvoltage) wrote:
> Will do, I also want to rename this package and ensure its upstream
> tarball is the same as in Kali Linux, since they have it packaged
> already and would like to avoid breakage (see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841
13 matches
Mail list logo
