I really shouldn't bite, but still... Looking at the deja-dup package changelog, first mention of packagekit is in 2015. That tells me that the request in question was not about not wanting to drag duplicity in main (and indeed, it's been in main quite a while) but rather about not wanting to have both python2 and python3 on the install media, probably for space reasons (python2 was still in main in 18.04). In other words, it's an ugly software solution to a hardware problem (optical media size).
Looking at the deja-dup changelog entry, Marco explicitly mentions the fact that restic and rclone are not in main. Those are not the same thing. Now, if we can't add a dependency for MIR reasons, then the solution is to *not use* the dependency, rather than side-loading it. An MIR is always *possible*, and if it's rejected it's normally for good reasons that won't go away. I couldn't care less about the route that is taken (patch, revert, MIR), but one of them must be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120709 Title: deja-dup relies on universe dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2120709/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
