Your message dated Sun, 06 Aug 2017 21:57:09 -0400 with message-id <tslshh4f8cq....@suchdamage.org> and subject line Re: Bug#870946: moonshot-trust-router: should moonshot-trust-router be removed from unstable? has caused the Debian Bug report #870946, regarding moonshot-trust-router: should moonshot-trust-router be removed from unstable? 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.) -- 870946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: moonshot-trust-router User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: moonshot-trust-router -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.html
--- End Message ---
--- Begin Message ---Hi! Thanks for your great work with QA and thanks for asking me to review the state of this package. I'm closing the bug because I believe the package should remain in unstable, but I wanted to document my reasoning because I'm very open to someone arguing I'm wrong, and because I want others to be able to see what's going on. Here's where things stand. During most of Stretch and Jessie, significant parts of trust-router were not useful in Debian because Freeradius 3 was not in Debian. You could run a trust router, but not a client or server for the trust router protocol. Freeradius3 did make it into stretch. However by that point the trust router had evolved significantly including changes to the protocol. There was a release late last year. I took a look at https://launchpad.net/moonshot-tr and concluded that I thought the version in Debian already was more stable than the current development version. Development has continued. I spoke to upstream this July and it looks like the 3.x release is going to be strong enough that it is desirable to get it into Debian and see if it's solid enough to support for the buster cycle. I've started work on the dependencies for new moonshot software; there is a new moonshot-ui in experimental. I'm hoping to update moonshot-gss-eap this week. The big obstacle there is updating the copyright file because of significant upstream churn. After that I think it would be reasonable to get trust router 3.x (or a snapshot if it is not out yet) into unstable and close the RC bug holding moonshot-trust-router out of testing. Thanks again, --Sam
--- End Message ---
