[UDD] Does anybody care about PET VCS import into UDD?
Hi, since some time UDD cron job is spamming me with messages like these but I do not speal Ruby so can't help here. Kind regards Andreas. - Forwarded message from Cron Daemon - Date: Mon, 29 Oct 2012 14:00:03 + From: Cron Daemon To: lu...@debian.org, laney-...@debian.org, ti...@debian.org Subject: Cron $UAR vcs X-Spam_score: -2.9 /usr/lib/ruby/1.8/dbd/pg/database.rb:82:in `initialize': could not connect to server: Connection refused (DBI::OperationalError) Is the server running on host "pet.debian.net" (217.196.43.134) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused Is the server running on host "pet.debian.net" (217.196.43.132) and accepting TCP/IP connections on port 5432? from /usr/lib/ruby/1.8/dbd/Pg.rb:157:in `new' from /usr/lib/ruby/1.8/dbd/Pg.rb:157:in `connect' from /usr/lib/ruby/1.8/dbi/handles/driver.rb:33:in `connect' from /usr/lib/ruby/1.8/dbi.rb:148:in `connect' from /srv/udd.debian.org/udd/scripts/update-vcs-status:17 - End forwarded message - -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121029153416.ga10...@an3as.eu
Re: [UDD] Does anybody care about PET VCS import into UDD?
On Mon, 29 Oct 2012 16:34:16 +0100, Andreas Tille wrote: > since some time UDD cron job is spamming me with messages like these > but I do not speal Ruby so can't help here. PET moved from Ansgar's machine to Alioth not so long ago; 217.196.43.134 resolves to alioth.d.o but maybe something else needs to be changed? CC'ing Ansgar who probably knows best the details behind PET :) > - Forwarded message from Cron Daemon - > > Date: Mon, 29 Oct 2012 14:00:03 + > From: Cron Daemon > To: lu...@debian.org, laney-...@debian.org, ti...@debian.org > Subject: Cron $UAR vcs > X-Spam_score: -2.9 > > /usr/lib/ruby/1.8/dbd/pg/database.rb:82:in `initialize': could not connect to > server: Connection refused (DBI::OperationalError) > Is the server running on host "pet.debian.net" (217.196.43.134) and > accepting > TCP/IP connections on port 5432? > could not connect to server: Connection refused > Is the server running on host "pet.debian.net" (217.196.43.132) and > accepting > TCP/IP connections on port 5432? > from /usr/lib/ruby/1.8/dbd/Pg.rb:157:in `new' > from /usr/lib/ruby/1.8/dbd/Pg.rb:157:in `connect' > from /usr/lib/ruby/1.8/dbi/handles/driver.rb:33:in `connect' > from /usr/lib/ruby/1.8/dbi.rb:148:in `connect' > from /srv/udd.debian.org/udd/scripts/update-vcs-status:17 > > > - End forwarded message - Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Dhafer Youssef: Ysamy signature.asc Description: Digital signature
Bug#498108: marked as done (qa.debian.org: package with comment-only 'debian/watch' reported as "Error")
Your message dated Tue, 30 Oct 2012 06:26:15 + with message-id <20121030062615.gc25...@master.debian.org> and subject line DDPO: comment-only 'debian/watch' reported as "Error" has caused the Debian Bug report #498108, regarding qa.debian.org: package with comment-only 'debian/watch' reported as "Error" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 498108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qa.debian.org Severity: normal Some packages do not have an upstream that can be checked. In many cases, such packages have a 'debian/watch' file consisting only of comments that explain why 'uscan' cannot be used for the package. The DEHS reports this as a package "without a checkable upstream", which is not an error. It also uses the comments in the 'debian/watch' file as the explanation. http://dehs.alioth.debian.org/maintainer.php?name=lojban-common> The QA package summary incorrectly lists "Error" for the package, linking to the DEHS report (which shows it as not an error). http://qa.debian.org/developer.php?packages=lojban-common> The QA package summary should, instead, report this situation indicating the upstream version is unknown, but *not* as an error. -- \ “Pinky, are you pondering what I'm pondering?” “Um, I think so, | `\Brainie, but why would anyone want to Pierce Brosnan?” —_Pinky | _o__) and The Brain_ | Ben Finney signature.asc Description: Digital signature --- End Message --- --- Begin Message --- This bug seems solved already. Feel free to reopen if you find examples illustrating that the bug is not yet fully solved.--- End Message ---
