> There isn't any need to add the debdiff to the bug report if the updated > version of the package has already been uploaded to the SRU queue. Is > this documented somewhere that I've forgotten or don't know about?
Mh, that has been my interpretation of the procedure for the last 5+ years I've been doing SRUs at least. Even reading the procedure now, at point 4 it says "Prepare the upload, attach a debdiff to the bug, [...] There is no need to wait before uploading. After upload, the bug status should be changed to In Progress" Besides, my experience with the SRU process is also that I can't quite expect a nowhere timely reply *unless* I also upload, but if I infer from your question here it feels more like that debdiff is only for sponsored uploads and is actually totally unneeded for anybody else. Incidentally, I wouldn't like that it makes unnecessary hard (if not impossible) for non-SRU members to see the diff of what was done while waiting for approval (say I wanted to build the package myself because I'm affected by the bug and can't wait for the SRU team) or if it was rejected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: [SRU] firejail missing the setuid bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
