devel:languages:python/python-urwid@35 -> openSUSE:Leap:15.0/python-urwid

expected origin is 'SUSE:SLE-15:GA' (changed)

the submitted sources are in or accepted for Factory

I tried it yesterday then I declined myself https://build.opensuse.org/request/show/586385 , the reason as I noted on that request, urwid is from SLE, unless someone submit a update to SLE15 otherwise I afraid python-mitmproxy's dep can fulfill.

Luigi Baldoni (alois) - about 6 years ago

author

As I understand, it's not set in stone that Leap should have everything coming from SLE. At least that was the case for another python module I submitted for 42.3 last year.

---

Max Lin (mlin7442) - about 6 years ago

reviewer

not everything, but if SLE has that package then they must be stay in sync

---

Luigi Baldoni (alois) - about 6 years ago

author

Like I said, it didn't seem like a fixed rule when I submitted stuff last year. Perhaps it is now?

---

Ludwig Nussel (lnussel) - about 6 years ago

reviewer

the general guideline is that if it's in SLE we should try hard to stick with it. 42 had more packages diverging due to it's history coming after 13.2. Now with Leap 15 I want us to get as close as possible.

python-urwid might be special here. Seems not to be in any product and might get removed from SLE actually. Then we would be free to use whatever we want.

Ludwig Nussel (lnussel) - about 6 years ago

reviewer

I filed a delete request on SLE side, let's see. put this on hold for now.

Via https://build.opensuse.org/request/show/592051 from SLE

SUSE:SLE-15:GA/python-urwid@106f7e26be0b082dee8e729cd03bdc2d -> openSUSE:Leap:15.0/python-urwid

expected origin is 'SUSE:SLE-15:GA' (unchanged)

python-urwid submitted from SUSE:SLE-15:GA, no maintainer review needed