Hi,
I stopped doing pkg-voip work sometime in 2013. I was fairly active for
some time before that, and had (foolishly :) gotten myself in the
Uploaders field of all kinds of pkg-voip packages that I did uploads
for. 4+ years later I seem to be listed still as an maintainer/uploader
for certain pac
Your message dated Thu, 4 Jan 2018 13:02:30 +0100
with message-id <20180104120230.gd15...@home.ouaza.com>
and subject line Re: Bug#886114: Please support X-GitLab-Project in addition to
X-Git-Repo.
has caused the Debian Bug report #886114,
regarding Please support X-GitLab-Project in addition to X
On Thu, Jan 04, 2018 at 01:51:59PM +0200, Faidon Liambotis wrote:
> - src:asterisk-prompt-es: last upload was almost 10 years ago, in
> February 2008. Before that, a handful of uploads in 2005-2006. Should
> probably be adopted by the Asterisk maintainers or they should ask for
> its removal
Hi,
> - src:openam: last upload was in June 2010. Upstream Homepage doesn't
> even work. Popcon inst 9...
>
> - src:gnugk: last upload for v3.6 was in May 2014, but upstream seems
> active (v4.7 was released in September 2017):
> https://www.gnugk.org/
>
> - src:h323plus: last maintainer u
On Wed, Jan 03, 2018 at 01:52:44PM -0800, Steve Langasek wrote:
> Neither humans nor tools should have to guess which is the correct branch in
> a git repository corresponding to the packaging, when we have ways to
> specify this unambiguously.
I'm not sure why humans need to specify things if to
On Thu, Jan 04, 2018 at 02:44:41PM +, Holger Levsen wrote:
> So I made that change in debian/control here locally and then checked
> tracker.d.o/munin but the issue seems to be gone, so I refrained from
> commiting this to git and pushing.
It is gone because I modified the value in the local v
On Thu, Jan 04, 2018 at 04:12:31PM +0100, Mattia Rizzolo wrote:
> It is gone because I modified the value in the local vcswatch override
> database at https://qa.debian.org/cgi-bin/vcswatch?package=munin (if you
> log in with a valid Debian SSO certificate a text fields appears and you
> can then m
On Thu, Jan 04, 2018 at 03:22:41PM +, Holger Levsen wrote:
> ah, ok, so I should modify the line
> Vcs-Git: https://anonscm.debian.org/git/collab-maint/munin.git
> to
> Vcs-Git: https://anonscm.debian.org/git/collab-maint/munin.git -b debian
> ?
Personally, in this case I would say you need t
On Thu, Jan 04, 2018 at 04:54:35PM +0100, Mattia Rizzolo wrote:
> On Thu, Jan 04, 2018 at 03:22:41PM +, Holger Levsen wrote:
> > ah, ok, so I should modify the line
> > Vcs-Git: https://anonscm.debian.org/git/collab-maint/munin.git
> > to
> > Vcs-Git: https://anonscm.debian.org/git/collab-main
Package: qa.debian.org
Severity: normal
For git repositories, vcswatch should check the configuration file
debian/gbp.conf (if it exists) in the source package to determine what branch to
use as its packaging branch. For example, vcswatch reports
Error: changelog package prerex does not matc
On Thu, Jan 04, 2018 at 04:01:18PM +, Holger Levsen wrote:
> > Personally, in this case I would say you need to change two things:
> > 1) edit the remote repository configuration so HEAD points to the debian
> >branch
> > 2) change Vcs-Git of the version in experimental by adding '-b
> > d
Control: tag -1 moreinfo
On Thu, Jan 04, 2018 at 11:11:30AM -0500, Ryan Kavanagh wrote:
> on vprerex[0] because the HEAD of the git repository specified in Vcs-Git
> points
> to the prerex packaging instead of the vprerex packaging. However, the file
> debian/gbp.conf[1] in the vprerex sources sp
Processing control commands:
> tag -1 moreinfo
Bug #886334 [qa.debian.org] vcswatch: use the debian-branch specified in
gbp.conf for Git
Added tag(s) moreinfo.
--
886334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Your message dated Thu, 4 Jan 2018 11:54:23 -0500
with message-id <20180104165423.y6r7orikuutd5...@zeta.ryanak.ca>
and subject line Re: Bug#886334: vcswatch: use the debian-branch specified in
gbp.conf for Git
has caused the Debian Bug report #886334,
regarding vcswatch: use the debian-branch spec
Your message dated Thu, 4 Jan 2018 21:58:43 +0100
with message-id <20180104205843.auwmy4ofcnixu...@crans.org>
and subject line Re: tracker.debian.org: "action needed" details show only with
Javascript enabled
has caused the Debian Bug report #838178,
regarding tracker.debian.org: "action needed" d
Hi,
Pierre-Elliott Bécue wrote:
> I pushed a patch to have the tracker behaving in a proper way even though
> javascript is disabled.
That's great news. Since today i began to ponder whether pointing to
https://www.react-etc.net/entry/exploiting-speculative-execution-meltdown-spectre-via-javas
Le jeudi 04 janvier 2018 à 23:23:01+0100, Thomas Schmitt a écrit :
> Hi,
>
> Pierre-Elliott Bécue wrote:
> > I pushed a patch to have the tracker behaving in a proper way even though
> > javascript is disabled.
>
> That's great news. Since today i began to ponder whether pointing to
>
> https:
Package: tracker.debian.org
Severity: normal
Take a look at Vcs: field in:
https://tracker.debian.org/pkg/aptitude
For Vcs-Git, the hyperlink yields:
https://anonscm.debian.org/git/aptitude/aptitude.git%20-b%20debian-sid
Which is definitely wrong and will leads to 404.
Regards,
Boyuan Yang
18 matches
Mail list logo
