Thanks Stefano already for the test fixups in -3. I think we will discuss the "no-py2" rule in regard to this later to day in the MIR team meeting. Maybe python-lxml already has a strategy to get out of main for 20.04 and we can it ignore it in regard to this MIR here as it will just "follow" that. >From what I found (see below) it might depend on the openstack off-of-py2 plan >and be ok for now? Feel free to join in #ubuntu-meeting in about ~5 hours from now.
The subscriber is what puzzles me most atm. I found that atm [1] that is actually the server Team. Checking the old MIRs it was Chuck and James - maybe it is actually for openstack still? Or is it actually no more needed? Of the full reverse depends only: - python-lxml (<- python-keystoneauth1 ...) - python3-lxml (<- python3-ceilometer / python3-cinder / ...) - python3-webtest (<- python3-pecan <- ceph-mgr / python3-aodh / python3-barbican / python3-neutron ...) are in main. That all seems like openstack to me which matches Chuck/James working on the past MIRs. I'll discuss it with people longer in the Team than myself if they remember more of the history behind this - after all the subscriber for the new package might have to be the server team again ?!. [1]: https://bugs.launchpad.net/ubuntu/+source/beautifulsoup4/+subscriptions [2]: https://bugs.launchpad.net/ubuntu/+source/beautifulsoup/+bug/492560 [3]: https://bugs.launchpad.net/ubuntu/+source/beautifulsoup4/+bug/1252623 ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814500 Title: [MIR] soupsieve (dependency of beautifulsoup4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backports.functools-lru-cache/+bug/1814500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
