On Thu, 2025-07-31 at 16:35 -0700, Soren Stoutner wrote: > On Thursday, July 31, 2025 4:14:04 PM Mountain Standard Time Tiago Bortoletto > Vaz wrote: > > On Thu, Jul 31, 2025 at 04:10:25PM -0700, Soren Stoutner wrote: > > > On Thursday, July 31, 2025 1:03:51 PM Mountain Standard Time Tiago > > > Bortoletto > > > > > > Vaz wrote: > > > > Hi, > > > > > > > > On Thu, Jul 31, 2025 at 08:02:39AM +0100, Phil Wyett wrote: > > > > > All, > > > > > > > > > > This is in the NEW queue, closing. > > > > > > > > Please do not close ITP bugs as they'll be automatically closed once > > > > the packaged is accepted by ftp-master. They're in NEW but can still be > > > > rejected. > > > > > > As far as I can tell, Phil closed the RFS bug, not the ITP bug. Closing > the > > > RFS bug is the correct behavior when a package enters NEW. You are > correct > > > that any ITP bug should remain open and will automatically be closed when > a > > > package clears NEW. > > > > All good then, thanks for pointing out! > > The name of the bug is non-standard and includes both RFS and [ITP], so it is > easy to get confused about which bug it actually is. > Morning Soren, I am dropping a recipient, but hope they see this email. I am not allowed direct contact with Debian Application Managers and until stated otherwise I am sticking to the letter of things to avoid being kicked out of Debian. I am sure you understand why I am being so cautious. On to business and fun stuff... Not really non-standard[1] going by the page linked. Also not sure how 'reportbug' generates an RFS as I have never used it to do one. It can get confusing and will admit it, a double take to look again at subject lines is a common occurrence here. :-) As you know, closing the RFS on upload has always been the norm and yes we leave all ITP bugs for auto closing when they are accepted into Debian. I hope all is clarified now and we can move on. [1] https://mentors.debian.net/sponsors/rfs-howto/ -- Blog: https://blog.kathenas.org GPG Fingerprint: 70A0 AC45 AC77 9EFE 84F6 3AED 724A A9B5 2F02 4C8B
Attachment:
signature.asc
Description: This is a digitally signed message part