> human maintainer". 1 was "why are you asking me, I am only an
> uploader,
> the package is team maintained" even though that person was the only
> actual uploader (since 2002 till 2012). I've sent the list of my
> pings to
> the MIA team.
I don't like the way you are picturing this. The question
On Fri, Dec 02, 2016 at 10:56:07PM +0500, Andrey Rahmatullin wrote:
> * So, the first question is: should I spend my time on getting these
> packages back to testing so they would be a part of the next release? Or
> should I spend my time on other RC bugs fixing which will help release
> stretch fa
On 03/12/16 11:42, Mattia Rizzolo wrote:
> On Fri, Dec 02, 2016 at 10:56:07PM +0500, Andrey Rahmatullin wrote:
>> * So, the final question: how much time should pass since the last
>> maintainer upload (since removal from testing, since the first still
>> unfixed RC bug, how many NMUs should exist
On Sat, Dec 03, 2016 at 12:23:17PM +0100, Emilio Pozuelo Monfort wrote:
> I would suggest to come up with some algorithm to determine if a package is
> effectively unmaintained, and implement it in an automatic way that gives
> maintainers prior notice and a chance to react, like we do with auto-re
On Fri, Dec 02, 2016 at 10:03:07PM +0200, Kyle Robbertze wrote:
> Package: wnpp
>
> * Package name: iterum
> Version : 0.1
> Upstream Author : Kyle Robbertze
> * URL : http://iterum.io/
> * License : MIT/X/Expat
> Programming Lang: Python
> Description
On Sat, Dec 03, 2016 at 12:23:17PM +0100, Emilio Pozuelo Monfort wrote:
> I would suggest to come up with some algorithm to determine if a package is
> effectively unmaintained, and implement it in an automatic way that gives
> maintainers prior notice and a chance to react, like we do with auto-re
On Sat, Dec 03, 2016 at 11:42:02AM +0100, Mattia Rizzolo wrote:
> And: you're suggesting to do a QA upload without changing maintainer
> field? That seems ridiculous to me: QA uploads are uploads where
> maintainer is QA, right? You're suggesting to change the meaning to
> "big NMU", basically?
On Sat, Dec 03, 2016 at 12:23:17PM +0100, Emilio Pozuelo Monfort wrote:
> I think we should also have an auto-removals-from-sid[1] (the crowd applauded
> when I mentioned that in my Debconf talk), which would solve/help your high
> number of orphaned packages.
What real problems will this solve apa
Hi,
The URL https://manpages.debian.org/man/1/uscan gives me a 403 error.
This e-mail is to report that issue.
Is there a better place then ML d-devel@l.d.o to report?
What I did myself: replaced httpS into http (same HTTP 403 error)
Where the link was found: https://wiki.debian.org/debian/
On Sat, Dec 03, 2016 at 02:33:44PM +0100, Geert Stappers wrote:
> The URL https://manpages.debian.org/man/1/uscan gives me a 403 error.
https://manpages.debian.org/ gives me "The service you have requested is
currently disabled."
Googling for "manpages.debian.org" gives me
https://wiki.debian.org/m
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia
* Package name: tendermint-go-config
Version : 0.0~git20160626.0.e64b424
Upstream Author : Tendermint Project
* URL : http://www.tendermint.com
* License : Apache-2.0
Programming Lang: Golang
Descripti
On Sat, Dec 03, 2016 at 02:01:10PM +0100, Geert Stappers wrote:
> > I plan on maintaining it within the PAPT. I will need a
> > sponsor.
>
> I don't know what PAPT is.
https://wiki.debian.org/Teams/PythonAppsPackagingTeam
> Other thing I couldn't find: the "debian directory"
That's probably fin
On Sat, Dec 03, 2016 at 06:23:17PM +0500, Andrey Rahmatullin wrote:
> > I think we should also have an auto-removals-from-sid[1] (the crowd
> > applauded
> > when I mentioned that in my Debconf talk), which would solve/help your high
> > number of orphaned packages.
> What real problems will this
On 03/12/16 14:40, Andrey Rahmatullin wrote:
> On Sat, Dec 03, 2016 at 02:33:44PM +0100, Geert Stappers wrote:
>> The URL https://manpages.debian.org/man/1/uscan gives me a 403 error.
> https://manpages.debian.org/ gives me "The service you have requested is
> currently disabled."
> Googling for "m
Hi,
On Fri, 2 Dec 2016 10:55:23 +0100
Raphael Hertzog wrote:
> Hideki, would you sponsor a new maintainer if s/he does not have upload
> rights? (bccing debian-mentors in case new contributors are interested in
> taking it over)
Of course, I'll sponsor it, and hope someone can step up to new ma
On Sat, Dec 03, 2016 at 09:25:11AM +0100, Michael Meskes wrote:
> > human maintainer". 1 was "why are you asking me, I am only an
> > uploader,
> > the package is team maintained" even though that person was the only
> > actual uploader (since 2002 till 2012). I've sent the list of my
> > pings to
On Sat, Dec 03, 2016 at 03:31:17PM +0100, Emilio Pozuelo Monfort wrote:
> On 03/12/16 14:40, Andrey Rahmatullin wrote:
> > On Sat, Dec 03, 2016 at 02:33:44PM +0100, Geert Stappers wrote:
> >> The URL https://manpages.debian.org/man/1/uscan gives me a 403 error.
> > https://manpages.debian.org/ give
On Sat, Dec 03, 2016 at 06:22:18PM +0100, Geert Stappers wrote:
> > >> The URL https://manpages.debian.org/man/1/uscan gives me a 403 error.
> > > https://manpages.debian.org/ gives me "The service you have requested is
> > > currently disabled."
> > > Googling for "manpages.debian.org" gives me
>
Hi,
debian-keyring git changelog shows 2016.11.13 as the latest, even the
tags reflect this.
https://anonscm.debian.org/cgit/keyring/keyring.git/tree/debian/changelog
But https://tracker.debian.org/pkg/debian-keyring shows 2016.09.04 as
the latest version.
apt-cache policy debian-keyrin
On Sat, Dec 03, 2016 at 11:21:26PM +0530, Pirate Praveen wrote:
> debian-keyring git changelog shows 2016.11.13 as the latest, even the
> tags reflect this.
> https://anonscm.debian.org/cgit/keyring/keyring.git/tree/debian/changelog
>
> But https://tracker.debian.org/pkg/debian-keyring shows
On ശനി 03 ഡിസംബര് 2016 11:26 വൈകു, Mattia Rizzolo wrote:
> Yes, the package is not updated every time there is a keyring push.
> What's tagged is what is live on the debian.org infrastructure, not
> what's in the package (and probably you shouldn't rely on that either if
> you need an up-to-date k
> > The question is absolutely valid, but maybe I should rephrase it to
> > "Why
> > are you contacting the uploader only and not the team as well?"
>
> Because it's the first step.
Would have been nice to know. Anyway, I can see your point.
> > > * Also: what should we do with packages that are
Package: wnpp
Severity: wishlist
Owner: Ingo Bauersachs
* Package name: libsip-api-java
Version : 1.2
Upstream Author : Daniel Pocock
* URL : https://github.com/opentelecoms-org/java-sip-api
* License : Apache 2.0
Programming Lang: Java
Description : S
Package: wnpp
Severity: wishlist
Owner: Ingo Bauersachs
* Package name: libsdp-api-java
Version : 1.0
Upstream Author : Daniel Pocock
* URL : https://github.com/opentelecoms-org/java-sdp-api
* License : Apache 2.0
Programming Lang: Java
Description : S
On Sun, Dec 4, 2016 at 2:09 AM, Pirate Praveen wrote:
> Previous uploads were more frequent so I wondered if there was an issue.
Probably best to talk to keyring maint than debian-devel.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-has-gulplog
Version : 0.1.0
Upstream Author : Blaine Bublitz (http://iceddev.com)
* URL : https://github.com/gulpjs/has-gulplog#readme
* License
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-glogg
Version : 1.0.0
Upstream Author : Blaine Bublitz
(http://iceddev.com/)
* URL : https://github.com/undertakerjs/glogg#readme
* License
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-fancy-log
Version : 1.2.0
Upstream Author : Blaine Bublitz (http://iceddev.com)
* URL : https://github.com/phated/fancy-log#readme
* License
28 matches
Mail list logo
