Hello Ian, > > By the way, I see that you addressed the "rsync maintainers" in the > > beginning but I didn't receive any email. Just saying because you > > might have forgotten to CC us. > > Interesting. > > I used "X-Debbugs-CC: rs...@packages.debian.org" and the bug system > does say this: Copy sent to rs...@packages.debian.org > > I wonder what happened to the mail. Let us try to debug it ourselves > before we ask owner@bugs to try to find a bounce or something. I just > sent a test to that address.
Hmm, apparently I'm not receiving those, I tested with another package I maintain, but I know that the other maintainer of rsync is receiving it so it should be something on my side. > It looks like dgit will migrate today. I think the CI will pick up > the new dgit automatically and retest with it, so I'm hoping no > further manual action will be needed. Thanks, and I believe rsync will migrate today. > BTW I looked at > https://tracker.debian.org/pkg/rsync > and it says under "versions" > NEW/unstable: 3.1.3-9 > which is rather odd. I thought you should be told. It is odd indeed, but I'm aware of the issue already, what happened was that I had introduced rsync-udeb on 3.1.3-9 but then it stayed long enough in the NEW queue that a new release happened (3.2.0) and with this new release it came new dependencies for which there is no udeb, I decided to revert the udeb for now so 3.2.0-1 went directly to unstable. This inclusion of dependencies left me wondering about the maintainability of rsync-udeb, I don't want to have to perform two builds and this means the with the addition of dependencies we would either be blocked until the udebs are there or we would have to revert the udeb. I will soon post an update to #729069 and #764320. Regards, -- Samuel Henrique <samueloph>
