Override component to main
soupsieve 1.8+dfsg-1 in disco: universe/misc -> main
pypy-soupsieve 1.8+dfsg-1 in disco amd64: universe/python/optional/100% -> main
pypy-soupsieve 1.8+dfsg-1 in disco arm64: universe/python/optional/100% -> main
pypy-soupsieve 1.8+dfsg-1 in disco armhf: universe/python/o
Override component to main
backports.functools-lru-cache 1.5-2 in disco: universe/misc -> main
pypy-backports.functools-lru-cache 1.5-2 in disco amd64:
universe/python/optional/100% -> main
pypy-backports.functools-lru-cache 1.5-2 in disco arm64:
universe/python/optional/100% -> main
pypy-backpor
ubuntu-server subscribed
--
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.launc
ubuntu-server subscribed
--
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.launc
For now server Team is subscribed, all is in place and ready.
Status: Fix Committed
Next: AA to promote the packages
** Changed in: backports.functools-lru-cache (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: soupsieve (Ubuntu)
Status: Triaged => Fix Committed
--
You re
Sorry, but I have found that this is in the responsibility nimbus for
now, give it a few days so that Powersj can sort that out. Then we can
mark it ready and do the promotion.
** Changed in: backports.functools-lru-cache (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: soupsieve (
Thanks btw Stefano for all the great packaging!
--
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
I almost forgot to state it here, this also covers the extra dep to
backports.functools-lru-cache.
TL;DR:
- I reviewed it and package content and quality looks fine
- we will be able to demote it "soon" once Openstack has let go python2 which
is WIP
Details:
[Duplication]
ok - Parth of the py3/p
Thanks Seth for the review.
The Lintian warning is fine, that is just because it has no Ubuntu Delta at the
moment.
I think overall this MIR concluded and is approved.
Since the code change to trigger is already waiting in disco-proposed:
beautifulsoup4 (4.6.3-2 to 4.7.1-1build1) in proposed for
Because this package is derived from code that was previously in main,
we decided to give this package a very light review.
I reviewed version 1.8+dfsg-1 from disco. I needed to enable the
-proposed pocket in order to build this package. (Probably that's the
whole point of this process.)
The code
Discussed with the more experienced members of the MIR Team.
Since this is a new leaf package to a chain of already existing python2
dependencies it does not hit the red flag of "new py2 dependencies" as defined
by the MIR process.
Mid Term it will be demotable once Openstack is off of python2.
While the subscribers will eventually be resolved between server and
openstack team I asked powersj to subscribe the server Team for now as
we are the beautifulsoup4 owner atm.
I haven't reached any of the more experienced MIR members last week on IRC,
will write a mail.
While my py2 question sti
** Tags removed: 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:
http
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" th
> That should be resolved so that there is a good baseline and broken uploads
> will be gated.
> Seems to be the same set of errors in py2 and the py3 case.
They're resolved in -3 and the tests are passing.
> So I assume that is part of the +dfsg packaging and should be improved
just to be sure.
FYI some references:
- initial beautifulsoup MIR
https://bugs.launchpad.net/ubuntu/+source/beautifulsoup/+bug/492560
- switching to beautifulsoup4
https://bugs.launchpad.net/ubuntu/+source/beautifulsoup4/+bug/1252623
Ack on the rationale, here the ref's of both projects [1][2] for this switch.
** Changed in: soupsieve (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
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 beautifuls
** Summary changed:
- [MIR] soupsieve
+ [MIR] soupsieve (dependency of beautifulsoup4)
** Description changed:
[Availability]
From Debian. Bootstrapped in disco.
[Rationale]
beautifulsoup4 4.7 introduced soupsieve as a new dependency. This is
replacing the same functionality that use
18 matches
Mail list logo
