I've asked other AAs for input on this, but my gut feeling is that adding ruby-jaeger-client to sync-blocklist is the wrong way to go. Presumably if it comes in through Debian again, it's because *somebody* on the Debian side has started maintaining it again (fsvo maintaining).
I actually think we shouldn't block anything, but if we really want to block something it'd be ruby-gitlab-labkit through extra-removals (from the same repo) conditioned on ruby-jaeger-client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100996 Title: [p-m] Please remove from Plucky, obsolete upstream and will be removed from Testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gitlab-labkit/+bug/2100996/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
