Bug#1099025: angband: commented out code in maintscripts cause false positives for QA efforts

Source: angband Version: 1:4.2.5+dfsg1-2 X-Debbugs-CC: debian-qa@lists.debian.org Hi, angband has a lot of code in maintscripts looking like left over templates. These include keywords relevant for archive-wide QA efforts like "dpkg-divert" and others. Please delete unused

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

On Wed, Jan 08, 2025 at 08:22:22PM -0800, Otto Kekäläinen wrote: > There have been discussions about adding adequate to Salsa CI and run > it by default as part of the piuparts job. If you are now preparing to > have adequate by default in piuparts, then it would make sense to have > it by default

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

On Wed, Jan 08, 2025 at 09:11:02PM +0100, Serafeim (Serafi) Zanikolas wrote: > hi Holger, as you have addressed me here and... > On Wed Jan 8, 2025 at 11:57 AM CET, Holger Levsen wrote: > > (actually adequate is run on many more binary packages on piuparts.d.o, > > because > > p.d.o is not only

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

> > two things: first, what is a "core component of Debian" is very much up to > > debate, but I'd be quite surprised if anybody made the case that adequate > > is. > > adequate is run on all 7 binary packages on piuparts.debian.org. I'm > really > curious whether this will blow up when piupa

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

hi Holger, On Wed Jan 8, 2025 at 11:57 AM CET, Holger Levsen wrote: > On Tue, Jan 07, 2025 at 11:55:30PM +0100, Serafeim (Serafi) Zanikolas wrote: > > two things: first, what is a "core component of Debian" is very much up to > > debate, but I'd be quite surprised if anybody made the case that ade

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

On Tue, Jan 07, 2025 at 11:55:30PM +0100, Serafeim (Serafi) Zanikolas wrote: > two things: first, what is a "core component of Debian" is very much up to > debate, but I'd be quite surprised if anybody made the case that adequate is. adequate is run on all 7 binary packages on piuparts.debian.

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

Wouter, thank you so much for this response. your message has motivated me to change adequate to target gccgo (rather than golang-go, which is a couple of years ahead), to extend the availability of adequate to more ports On Wed Dec 18, 2024 at 9:34 PM CET, Wouter Verhelst wrote: > Hi, > > On Wed,

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

On Fri Dec 27, 2024 at 10:49 PM CET, Serafeim (Serafi) Zanikolas wrote: > hi Jonathan, > > On Thu Dec 12, 2024 at 3:36 PM CET, Jonathan Dowland wrote: [..] > > "likely in many ports too" is dancing around the fact that it *doesn't* > > run on at least one port, hence Holger's complaint. > > which

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

extent that it helps > > reason about general principles. > > That's going to be pretty hard, because the scenario you present is > still pretty specific. > > > so we have a qa testing package that was written 11y ago in perl, and > > has been orphaned for almost all

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

the > > > viability of those ports, than the suitability of go for Debian tooling.. > > > if you > > > feel strongly otherwise, I'd be happy to continue this discussion with a > > > wider > > > audience at rather than reply here > > > > I do

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

e scenario you present is still pretty specific. so we have a qa testing package that was written 11y ago in perl, and has been orphaned for almost all of that time (10y!). it's not critical but it does serve a purpose, and it's therefore nonideal that it's been orphaned for

Re: criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

ling. > > > if you > > > feel strongly otherwise, I'd be happy to continue this discussion with a > > > wider > > > audience at rather than reply here > > > > I dont feel strongly about this, but I'd like to point out that I > >

criteria for acceptable languages for central QA tools in Debian (was: Re: coordination between lintian/piuparts/adequate)

e happy to continue this discussion with a > > wider > > audience at rather than reply here > > I dont feel strongly about this, but I'd like to point out that I > disagree. IMO it was wrong to rewrite adequate (as any central QA tool > for Debian) in a language wh

Re: QA BTS graphs currently return an Internal Server Error

Hmn, nevermind the below. Étienne Mollier, on 2024-05-23: > I witnessed some HTTP error 500 affecting the BTS graph system > this evening, e.g. trying to access debian-med-packaging bts > graph[1] returned: […] I am not subscribed to debian-qa and did not realize there is a maintenance

QA BTS graphs currently return an Internal Server Error

> > Please contact the server administrator at > debian-qa@lists.debian.org to inform them of the time this > error occurred, and the actions you performed just before this > error. So per this instruction, here is my email. :) > More information about this error may be available

Re: Seeking MR and QA upload for python-openflow

Yogeswaran Umasankar wrote on 12/01/2024 at 03:57:19+0100: > Hi, > Anyone would like to MR and sponsor QA upload of python-openflow? > Forked from Debian / python-openflow, I have updated it to latest > version 2021.1, and made other changes in autopkgtest for Python 3.12 > [0

Seeking MR and QA upload for python-openflow

Hi, Anyone would like to MR and sponsor QA upload of python-openflow? Forked from Debian / python-openflow, I have updated it to latest version 2021.1, and made other changes in autopkgtest for Python 3.12 [0]. The upstream repo of python-openflow is in [1]. Thank you! [0] https

Re: Joining QA team

On Thu, Jan 11, 2024 at 12:12:14PM +, Jelmer Vernooij wrote: > [...] The > best way to get started is probably to contribute patches/MRs and > get review from DDs - you may want to ping here if there > are no responses to those (which is probably common with orphaned packages). https://wiki.de

Re: Joining QA team

On Wed, Jan 10, 2024 at 07:58:31PM -0500, Yogeswaran Umasankar wrote: > I want to join the QA team and get access to orphaned packages in > salsa git. I want to contribute by fixing them. Would you provide me > access to my salsa ID: yogu Orphaned packages on salsa live under the debi

Joining QA team

Hi, I want to join the QA team and get access to orphaned packages in salsa git. I want to contribute by fixing them. Would you provide me access to my salsa ID: yogu Thank you, Yogeswaran.

Assistance with Debian QA efforts

Good evening. I would like to assist in the QA efforts for Debian. Kinly clarify the next steps. Best regards, Glaucio Pessoa, P.E.

Debian-qa!

Debian-qa, I’m in videochat

Processed: tagging 1055043, bug 1055043 is forwarded to https://salsa.debian.org/qa/qa/-/merge_requests/49

Processing commands for cont...@bugs.debian.org: > tags 1055043 + patch Bug #1055043 [qa.debian.org] Debian carnivore: port from Python 2 to 3 Added tag(s) patch. > forwarded 1055043 https://salsa.debian.org/qa/qa/-/merge_requests/49 Bug #1055043 [qa.debian.org] Debian carnivore: port from

Enquiry about one QA page I do not understand

Greetings, [ Previous message sent last 22 June] I am having trouble with the Salsa git repos for my package (upstream also) minexpert2. The ddpo page (https://qa.debian.org/cgi-bin/vcswatch?package=minexpert2) says this: minexpert2 (9.2.1-1) [PTS] [DDPO] ERROR: Git: https://salsa.debian.org/de

Bug#1042950: Trends: add orphaned/QA maint to the co-maintenance diagram

* not co-maintained > * Orphaned (Maint=QA) > > Where the latter is when the maintainer is explicitly set to the QA / > orphaned maintainer. > > Obviously, it will not catch packages that are orphaned in wnpp only, but I > think it would still make an interesting trend.

Re: Debian QA

On Tue, 2022-07-19 at 16:29 +0300, Dayana wrote: > I want to join your team as a QA, > I have no experience as a QA, > but I would be happy to help. Please take a look at our web and wiki pages: https://wiki.debian.org/qa.debian.org/Join https://qa.debian.org/ https://wiki.d

Debian QA

Hi Debian, I want to join your team as a QA, I have no experience as a QA, but I would be happy to help. I would like to help with the removal of buggy packages. Thank you.

Bug#539014: marked as done (qa.debian.org: show link to removal bug on package QA page)

Your message dated Tue, 4 Jan 2022 00:02:59 +0100 with message-id and subject line Re: qa.debian.org: show link to removal bug on package QA page has caused the Debian Bug report #539014, regarding qa.debian.org: show link to removal bug on package QA page to be marked as done. This means that

Processed: bug 901500 is forwarded to https://salsa.debian.org/qa/distro-tracker/-/issues/44

Processing commands for cont...@bugs.debian.org: > forwarded 901500 https://salsa.debian.org/qa/distro-tracker/-/issues/44 Bug #901500 [tracker.debian.org] tracker.debian.org: does not remove the versions panel when the package has been removed entirely Bug #955213 [tracker.debian.org] Trac

Re: Re: Re: a tiny contribution to Debian QA work?

t/) and Debian Code Search ( > https://codesearch.debian.net/) are not in the list 'Wiki Page of the Debian > QA > Group', is it voluntary? These aren't really QA related so they aren't listed. > Also how this list is related to: https://wiki.debian.org/Services That

Re: Re: Re: a tiny contribution to Debian QA work?

://trends.debian.net/) and Debian Code Search ( https://codesearch.debian.net/) are not in the list 'Wiki Page of the Debian QA Group', is it voluntary? Also how this list is related to: https://wiki.debian.org/Services Thanks, Patrice

Re: Re: a tiny contribution to Debian QA work?

> Also http://duck.debian.net/sourcepackages.txt is empty, is this a bug? Please contact the DUCK maintainer about this. > Regarding 'Watch file checker' in Wiki Page of the Debian QA Group, > it is just an indirect link to the uscan manpage. Is this ok? IIRC that runs u

Re: Re: a tiny contribution to Debian QA work?

On Tue, 25 Feb 2020 11:23:56 +0100, Patrice Duroux wrote: > I also working on a tool that tries checking (and suggest updates) to a given > list of URLs: bad links, different cases of redirections, replacing http by > https, etc. That sounds like what duck is doing: http://duck.debian.net/ https:

Re: Re: a tiny contribution to Debian QA work?

? Regarding 'Watch file checker' in Wiki Page of the Debian QA Group, it is just an indirect link to the uscan manpage. Is this ok? Well, how could I consider a contribution to Debian if this should be the case? Report a bug to each source packages after a human check from my side (if n

Re: a tiny contribution to Debian QA work?

.org/ https://udd.debian.org/cgi-bin/ https://wiki.debian.org/UltimateDebianDatabase https://salsa.debian.org/qa/udd/ -- bye, pabs https://wiki.debian.org/PaulWise

a tiny contribution to Debian QA work?

Dear QA Team, I hope to address here an interesting point otherwise sorry for the noise. You may already have a (better) way to track this but... where? (I did not see something related in the long list of the Debian QA Group's Wiki) Also I hope to not offend any maintainer work providing a

Bug#678135: marked as done (qa.debian.org: Tables on Developer's QA page are quite inaccessible)

Your message dated Wed, 9 Jan 2019 09:22:36 +0100 with message-id <20190109082236.ga10...@msg.df7cb.de> and subject line Re: Bug#678135: qa.debian.org: Tables on Developer's QA page are quite inaccessible has caused the Debian Bug report #678135, regarding qa.debian.org: Tables on Dev

Processed: Re: Bug#678135: qa.debian.org: Tables on Developer's QA page are quite inaccessible

Processing control commands: > tags -1 moreinfo Bug #678135 [qa.debian.org] qa.debian.org: Tables on Developer's QA page are quite inaccessible Added tag(s) moreinfo. -- 678135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678135 Debian Bug Tracking System Contact ow...@bugs.de

Bug#678135: qa.debian.org: Tables on Developer's QA page are quite inaccessible

Control: tags -1 moreinfo Re: Mario Lang 2012-06-19 <87d34vqwqr@x4.delysid.org> > Package: qa.debian.org > Severity: wishlist > > I am looking at > > http://qa.debian.org/developer.php?login=mlang%40debian.org > > and notice that the way how the information presented there is rendered > as

Processed: bug 882737 is forwarded to https://salsa.debian.org/qa/qa/merge_requests/4

Processing commands for cont...@bugs.debian.org: > forwarded 882737 https://salsa.debian.org/qa/qa/merge_requests/4 Bug #882737 [qa.debian.org] qa.debian.org: DDPO links to stable-new diffs are wrong (and wrongly placed) Set Bug forwarded-to-address to 'https://salsa.debian.o

Processed: bug 902438 is forwarded to https://salsa.debian.org/qa/distro-tracker/issues/29

Processing commands for cont...@bugs.debian.org: > forwarded 902438 https://salsa.debian.org/qa/distro-tracker/issues/29 Bug #902438 [tracker.debian.org] tracker.debian.org: broken links in VCS field Set Bug forwarded-to-address to 'https://salsa.debian.org/qa/distro-tracker/issues/29&#x

Bug#626254: marked as done (DEHS and QA pages lacking upstream data -> div by zero)

Your message dated Tue, 19 Jun 2018 12:40:55 +0200 with message-id <20180619104055.gb7...@home.ouaza.com> and subject line Re: Bug#626254: Suggestion to Close This Bug Report has caused the Debian Bug report #626254, regarding DEHS and QA pages lacking upstream data -> div by zero to be

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

invented for (bibliographic references) in VCS. But you are definitely correct that there are packages with upstream files outside VCS (and if you ask me its a shame ;-) ). Kind regards Andreas. [1] https://salsa.debian.org/qa/udd/commit/a6a9c3bebbba4ce9f08307aeea00b433466f5070 -- http://fam-tille.de

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Wed, May 16, 2018 at 3:01 AM, Andreas Tille wrote: > On Thu, May 10, 2018 at 01:46:46PM +0800, Paul Wise wrote: >> This is using upstream-metadata.debian.net, seems like it will need >> updating if a replacement shows up. > > I can not parse this? The UDD gatherer is not using > upstream-metada

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

Hi Paul, On Thu, May 10, 2018 at 01:46:46PM +0800, Paul Wise wrote: > > > The Debian Med team includes upstream information from these files > > in its "tasks" pages (see > > for example), using the UDD as a gatherer. > > This is using upstream-metadata.

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Tue, May 08, 2018 at 06:02:36PM +1000, Stuart Prescott wrote: > Are there any other consumers of these files? Definitely. > If there are no longer any consumers, should we really be nagging > maintainers to include them? > > $ lintian-info --list-tags | grep upstream-metadata > upstream-met

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

Le Thu, May 10, 2018 at 01:46:46PM +0800, Paul Wise a écrit : > On Thu, May 10, 2018 at 1:21 PM, Charles Plessy wrote: > > > I was a bit over-zealous and cleaned the Alioth repository recently, but > > the source is still on and I can > > transfer it to Salsa if t

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Thu, May 10, 2018 at 1:21 PM, Charles Plessy wrote: > I was a bit over-zealous and cleaned the Alioth repository recently, but > the source is still on and I can > transfer it to Salsa if there is interest. Branchable is missing a few of the commits from aliot

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

m/> and I can transfer it to Salsa if there is interest. Regarding the bug that I could not track down, here is the link to the call for help that I sent in 2014: https://lists.debian.org/debian-qa/2014/06/msg00022.html Le Tue, May 08, 2018 at 06:02:36PM +1000, Stuart Prescott a écrit : >

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Tue, 08 May 2018 17:22:40 +0800, Paul Wise wrote: > On Tue, May 8, 2018 at 4:02 PM, Stuart Prescott wrote: > > Are there any other consumers of these files? > No services, but potentially tracker.d.o and packages.d.o. > People interacting with the source package might use them. Right, in the

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Tue, May 8, 2018 at 4:02 PM, Stuart Prescott wrote: > or looking at Contents-source.gz and linking to sources.debian.net. (or > asking ftp-master to export these files like they do with changelogs, > copyright files etc.) Good idea. vcswatch could take over the VCS scanning too. > Are there a

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

Paul Wise wrote: > If someone revives this service, this approach missed packages that do > not use a VCS. This could be worked around by the addition of fetching > from source packages when there is no VCS. The VCS should be preferred > since source packages don't need to be updated immediately wh

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

On Mon, May 7, 2018 at 8:37 PM, Charles Plessy wrote: > At the moment, the PTS points to files in the collab-qa repository > via Alioth' viewvc browser. Can somebody disable the links ? The > repository is completely outdated anyway. Done in git: https://salsa.debian.org

What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

Hello everybody, sorry for the longish title... In brief, some years ago I was aiming at gathering debian/upstream/metadata files from the VCS in which each source packages is stored, and mirror them in a central repository easily accessible. As a repository I chose the collab-qa Subversion

Re: QA svn converted to git, again

On Mon, Jan 01, 2018 at 12:18:57PM +0100, Mattia Rizzolo wrote: > On Mon, Jan 01, 2018 at 11:59:40AM +0100, Christoph Berg wrote: > > https://salsa.debian.org/qa/qa > > https://salsa.debian.org/qa/pts https://salsa.debian.org/qa/distro-tracker > > Thank you again! ;) >

Re: QA svn converted to git, again

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/

Re: QA svn converted to git, again

On Mon, Jan 1, 2018 at 6:59 PM, Christoph Berg wrote: > I've put pre-receive hooks in place to disable the git repos on > alioth. I'd suggest deleting the so that people fetching know they moved. OTOH, there is still the possibility of salsa db reset, so... -- bye, pabs https://wiki.debian.or

Re: QA svn converted to git, again

Re: Mattia Rizzolo 2018-01-01 <2018010857.gb11...@mapreri.org> > > I've put pre-receive hooks in place to disable the git repos on > > alioth. > > Did you do this also for distro-tracker? buxy? Done now. Christoph

Re: QA svn converted to git, again

On Mon, Jan 01, 2018 at 11:59:40AM +0100, Christoph Berg wrote: > The two gits are now on salsa: > > https://salsa.debian.org/qa/qa > https://salsa.debian.org/qa/pts Thank you again! ;) > > - commit messages can't close bugs > > This had been fixed for alioth, bu

QA svn converted to git, again

Re: To debian-qa@lists.debian.org 2017-12-15 <20171215204613.ga31...@msg.df7cb.de> > QA: https://anonscm.debian.org/cgit/qa/qa.git/ > PTS (previously a subdirectory of QA): >https://anonscm.debian.org/cgit/qa/pts.git/ The two gits are now on salsa: https://salsa.debian.

[qa] branch master updated (815aa61 -> 5ce6a2c)

This is an automated email from the git hooks/post-receive script. mattia pushed a change to branch master in repository qa. from 815aa61 Sort cronjobs new 5ce6a2c Support git pulling through https with the debian.org SSL setup The 1 revisions listed above as "new

[qa] 01/01: Support git pulling through https with the debian.org SSL setup

This is an automated email from the git hooks/post-receive script. mattia pushed a commit to branch master in repository qa. commit 5ce6a2c84ceb4f50a4d5c9dc99a68777907ea4ee Author: Mattia Rizzolo Date: Sat Dec 16 12:59:20 2017 +0100 Support git pulling through https with the debian.org

Re: QA svn converted to git, finally

On Sat, Dec 16, 2017 at 4:46 AM, Christoph Berg wrote: > - the QA commits don't seem to end up on the mailing list yet This has since been fixed by someone, but I would prefer that they go through the tracker.debian.org or gitlab subscription stuff, so folks who want commits can get

Re: QA svn converted to git, finally

On Fri, Dec 15, 2017 at 09:46:13PM +0100, Christoph Berg wrote: > I forgot the reasons why we haven't moved the QA svn to git over the > past years, so I figured I could just do that now. \o/ Thank you for this!! ♥♥♥ > - the QA commits don't seem to end up on the mailing l

[qa] 01/01: Sort cronjobs

This is an automated email from the git hooks/post-receive script. myon pushed a commit to branch master in repository qa. commit 815aa61235ce629dd92fcb533425310e6f65399f Author: Christoph Berg Date: Fri Dec 15 21:35:34 2017 +0100 Sort cronjobs --- data/cronjobs/Makefile | 2 +- 1 file

[qa] branch master updated (9720e36 -> 815aa61)

This is an automated email from the git hooks/post-receive script. myon pushed a change to branch master in repository qa. from 9720e36 Move some svn links to git new 815aa61 Sort cronjobs The 1 revisions listed above as "new" are entirely new to this repository a

[qa] 01/01: Move some svn links to git

This is an automated email from the git hooks/post-receive script. myon pushed a commit to branch master in repository qa. commit 9720e36d032f443c2198eb82395fd7321f3e87ee Author: Christoph Berg Date: Fri Dec 15 21:32:54 2017 +0100 Move some svn links to git --- README

[qa] branch master updated (27cd9cb -> 9720e36)

This is an automated email from the git hooks/post-receive script. myon pushed a change to branch master in repository qa. from 27cd9cb Remove pts tree, it's a separate git now new 9720e36 Move some svn links to git The 1 revisions listed above as "new" are

QA svn converted to git, finally

I forgot the reasons why we haven't moved the QA svn to git over the past years, so I figured I could just do that now. QA: https://anonscm.debian.org/cgit/qa/qa.git/ PTS (previously a subdirectory of QA): https://anonscm.debian.org/cgit/qa/pts.git/ The old svn repository has been moved

[qa] branch master updated (852af2d -> 27cd9cb)

This is an automated email from the git hooks/post-receive script. myon pushed a change to branch master in repository qa. from 852af2d Remove $Id$ tags new 27cd9cb Remove pts tree, it's a separate git now The 1 revisions listed above as "new" are entir

Re: upgrading quantz.d.o (qa) to stretch

On Tue, Oct 31, 2017 at 18:23:36 +0100, Christoph Berg wrote: > Re: Lucas Nussbaum 2017-10-27 > <20171027172527.nqt2p7kedlcrn...@xanadu.blop.info> > > Oh, during DebConf, I thought I understood that you found it hard to > > deal with quantz because it has no clear "service owner" and also hosts >

Re: upgrading quantz.d.o (qa) to stretch

Re: Lucas Nussbaum 2017-10-27 <20171027172527.nqt2p7kedlcrn...@xanadu.blop.info> > Oh, during DebConf, I thought I understood that you found it hard to > deal with quantz because it has no clear "service owner" and also hosts > many different services which their own breakage patterns. > But if tha

Re: upgrading quantz.d.o (qa) to stretch

On 27/10/17 at 19:20 +0200, Julien Cristau wrote: > On Fri, Oct 27, 2017 at 15:07:53 -0200, Lucas Nussbaum wrote: > > > On 27/10/17 at 18:59 +0200, Mattia Rizzolo wrote: > > > On Fri, Oct 27, 2017 at 02:30:11PM -0200, Lucas Nussbaum wrote: > > > > At DebConf, I expressed the opinion that it would

Re: upgrading quantz.d.o (qa) to stretch

On Fri, Oct 27, 2017 at 15:07:53 -0200, Lucas Nussbaum wrote: > On 27/10/17 at 18:59 +0200, Mattia Rizzolo wrote: > > On Fri, Oct 27, 2017 at 02:30:11PM -0200, Lucas Nussbaum wrote: > > > At DebConf, I expressed the opinion that it would be better NOT to > > > upgrade it to stretch, but rather to

Re: upgrading quantz.d.o (qa) to stretch

On 27/10/17 at 18:59 +0200, Mattia Rizzolo wrote: > On Fri, Oct 27, 2017 at 02:30:11PM -0200, Lucas Nussbaum wrote: > > At DebConf, I expressed the opinion that it would be better NOT to > > upgrade it to stretch, but rather to finish identifying services that > > should be split away to seperate h

Re: upgrading quantz.d.o (qa) to stretch

or else, we are going to > continue to maintain the qa svn for the next two years. Well, it's not like there is such a huge maintenance overhead to that, imho. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .'&

Re: upgrading quantz.d.o (qa) to stretch

On 27/10/17 at 15:13 +0200, Julien Cristau wrote: > [Bcc: qa-core group members] > > Hi, > > I'd like to upgrade quantz.debian.org to stretch in the near future. > Are there any known blockers from the qa side? Barring any blockers I > am planning on proceeding with t

Re: upgrading quantz.d.o (qa) to stretch

On Fri, Oct 27, 2017 at 04:01:52PM +0200, Mattia Rizzolo wrote: > On Fri, Oct 27, 2017 at 03:13:16PM +0200, Julien Cristau wrote: > > I'd like to upgrade quantz.debian.org to stretch in the near future. > > Are there any known blockers from the qa side? > > None are k

Re: upgrading quantz.d.o (qa) to stretch

On Fri, Oct 27, 2017 at 03:13:16PM +0200, Julien Cristau wrote: > I'd like to upgrade quantz.debian.org to stretch in the near future. > Are there any known blockers from the qa side? None are known. Please upgrade quantz like last few times, whenever convenient to you and we wil

upgrading quantz.d.o (qa) to stretch

[Bcc: qa-core group members] Hi, I'd like to upgrade quantz.debian.org to stretch in the near future. Are there any known blockers from the qa side? Barring any blockers I am planning on proceeding with the upgrade some time early next week. Let me know if you would prefer to coordinate a

Re: Reminder: Debian QA IRC meeting @ 23.08.2017 18:00 (UTC)

On Mon, Aug 21, 2017 at 6:00 PM, Tomasz Nitecki wrote: > This is a friendly reminder that a monthly Debian QA Team Meeting will > take place at #debian-qa on irc.oftc.net on 23.08.2017 18:00 (UTC) (Yup, > that's the customary 4th Wednesday of the current month). Local times and a

Reminder: Debian QA IRC meeting @ 23.08.2017 18:00 (UTC)

Hey, This is a friendly reminder that a monthly Debian QA Team Meeting will take place at #debian-qa on irc.oftc.net on 23.08.2017 18:00 (UTC) (Yup, that's the customary 4th Wednesday of the current month). Logs from older meetings can be found at [1]. Regards, T. [1]

Re: QA at DebConf17?

Hi Paul, On Wed, Mar 15, 2017 at 08:48:03AM +0800, Paul Wise wrote: > Any QA folks coming to DebConf17? > > What events have folks submitted? I have not commited anything QA specific. What I would *really* like to hear is some introduction how to effectively use gdb when trying to t

QA at DebConf17?

Hi all, Any QA folks coming to DebConf17? What events have folks submitted? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part

Re: Package removed from unstable still in QA overview

* Peter Colberg , 2016-09-11, 16:29: Two months ago I requested the removal of two packages from unstable, golang-github-square-go-jose (#828201) and golang-github-cheggaaa-pb (#830747). The former no longer appears on my QA overview, but the latter continues to linger around: https

Re: Package removed from unstable still in QA overview

On Sun, Sep 11, 2016 at 04:29:25PM -0400, Peter Colberg wrote: > Dear Debian QA team, > > Two months ago I requested the removal of two packages from unstable, > golang-github-square-go-jose (#828201) and golang-github-cheggaaa-pb > (#830747). The former no longer appears on my Q

Package removed from unstable still in QA overview

Dear Debian QA team, Two months ago I requested the removal of two packages from unstable, golang-github-square-go-jose (#828201) and golang-github-cheggaaa-pb (#830747). The former no longer appears on my QA overview, but the latter continues to linger around: https://qa.debian.org

Re: [Qa-jenkins-dev] IRC meeting to plan further team maintenace of jenkins.debian.(net|org)

ut up > this agenda as well: > > * next steps for the jenkins.debian.org migration > * how to move to more team maintenance > * finding a schedule for (bi-)monthly irc meetings > * any other business (AOB) just a quick reminder that we will meet in #debian-qa on OFTC in 2.5

Re: developer summary on QA

On 07/12/2016 02:48 PM, Massimo Manghi wrote: > https://qa.debian.org/developer.php?email=mxmanghi%40apache.org > > still displays links to the old PTS pages. I don't know if it's > intentional, but I definitely would like to see around a unique > reference for PTS pages DDPO links both the new T

developer summary on QA

Dear Debian QA team, It seemed to me the transition to tracker.d.o had completed: the pages look very good and are quite complete and helpful. Therefore I thought that web site to be now the proper tool to check a package status: Nonetheless I noticed the package summary table at https

QA BOF tomorrow

Hi, As a reminder, there's a QA BOF scheduled tomorrow (Thursday). I've started a gobby document with some topics that we could discuss, but feel free to add more. Lucas

Re: [Adduser-devel] Intent to issue a documentation QA upload for adduser

decided > > to prepare a QA upload. Before uploading, I would also issue a call for > > translation (updates), for debconf, the programm translation and the > > man page translation. > > Please hold off your work for two weeks. I have just gotten in touch > with three people

Re: [Adduser-devel] Intent to issue a documentation QA upload for adduser

On Thu, May 26, 2016 at 08:32:27PM +0200, Helge Kreutzmann wrote: > Is there any problem for me asking the translators > for updates? No, go ahead. > Usually a two week time frame is given for that, which would fit > nicely, i.e. in about two weeks the QA upload is ready in its >

Re: [Adduser-devel] Intent to issue a documentation QA upload for adduser

> > to prepare a QA upload. Before uploading, I would also issue a call for > > translation (updates), for debconf, the programm translation and the > > man page translation. > > Please hold off your work for two weeks. I have just gotten in touch > with three people who

Re: Intent to issue a documentation QA upload for adduser

Hello Paul, On Thu, May 26, 2016 at 12:27:04PM +0800, Paul Wise wrote: > On Wed, May 25, 2016 at 8:56 PM, Helge Kreutzmann wrote: > > > * Lintian overrides are no longer present. Closes: #669979. > > Bugs closed in earlier versions should be not be closed in your > upload. Instead, close it by

Re: [Adduser-devel] Intent to issue a documentation QA upload for adduser

Hi, On Wed, May 25, 2016 at 02:56:11PM +0200, Helge Kreutzmann wrote: > there are quite a few pending documentation / translation issues for > adduser. We discussed the matter on debian-l10n-german and I decided > to prepare a QA upload. Before uploading, I would also issue a

Re: Intent to issue a documentation QA upload for adduser

On Wed, May 25, 2016 at 8:56 PM, Helge Kreutzmann wrote: > * Lintian overrides are no longer present. Closes: #669979. Bugs closed in earlier versions should be not be closed in your upload. Instead, close it by mailing 669979 with a Version pseudo-header indicating which version removed the li

Intent to issue a documentation QA upload for adduser

Hello *, there are quite a few pending documentation / translation issues for adduser. We discussed the matter on debian-l10n-german and I decided to prepare a QA upload. Before uploading, I would also issue a call for translation (updates), for debconf, the programm translation and the man page

Re: Support for version 4 watchfiles on qa webpages

n"; } -- 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

Re: Support for version 4 watchfiles on qa webpages

On 20/05/16 at 14:43 +0800, Paul Wise wrote: > On Fri, May 20, 2016 at 4:23 AM, Sascha Steinbiss wrote: > > > I was wondering what version of scan is used for > > https://qa.debian.org/cgi-bin/watch? > > The version from jessie-backports. > > > However, this seems to result in an error in the a

  1   2   3   4   5   6   7   8   9   10   >