Bug#733266: pu: package whois/5.1.0

2014-01-21 Thread Adam D. Barratt
Control: tags -1 + pending On Sun, 2014-01-12 at 17:51 +, Adam D. Barratt wrote: > On Sun, 2014-01-12 at 18:00 +0100, Marco d'Itri wrote: > > If there are no objections, I will upload 5.1.1~deb7u1 to > > proposed-updates. > > Ack, looks okay to me. Flagged for acceptance; thanks. Regards,

Bug#733266: pu: package whois/5.1.0

2014-01-12 Thread Adam D. Barratt
On Sun, 2014-01-12 at 18:00 +0100, Marco d'Itri wrote: > If there are no objections, I will upload 5.1.1~deb7u1 to > proposed-updates. Ack, looks okay to me. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact

Bug#733266: pu: package whois/5.1.0

2014-01-12 Thread Marco d'Itri
If there are no objections, I will upload 5.1.1~deb7u1 to proposed-updates. FYI, I have no plan to systematically feed back to stable the database entries for the new gTLDs, since they will not be active for many months at least. -- ciao, Marco diff -Nru whois-5.1.0/config.h whois-5.1.1/confi

Bug#733266: pu: package whois/5.1.0

2013-12-28 Thread Adam D. Barratt
[Re-sending with a gzipped attachment, as the BTS's spam-checking ate the original] Control: tags -1 + wheezy confirmed On Fri, 2013-12-27 at 23:15 +0100, Marco d'Itri wrote: > whois in stable should be updated due to the many changes in the > database. > I think that the smartest choice would b

Bug#733266: pu: package whois/5.1.0

2013-12-28 Thread Marco d'Itri
On Dec 28, "Adam D. Barratt" wrote: > This change isn't explicitly documented afaics. Have servers stopped > supporting the "S" flag, or was it not actually supported to begin with? I have forgot the exact details of what it meant, but it was not commonly used and it is not supported anymore by

Bug#733266: pu: package whois/5.1.0

2013-12-27 Thread Marco d'Itri
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu whois in stable should be updated due to the many changes in the database. I think that the smartest choice would be to reupload the latest release, once it will have transitioned to testing. A