Overview
Request History
leaper created request
Automatic request from SUSE:SLE-12:Update by UpdateCrawler
leaper accepted review
ok
jberry_factory added openSUSE:Leap:42.3:Staging:B as a reviewer
Being evaluated by staging project "openSUSE:Leap:42.3:Staging:B"
jberry_factory accepted review
Picked openSUSE:Leap:42.3:Staging:B
jberry_factory accepted review
Removing from openSUSE:Leap:42.3:Staging:B, re-evaluation needed
jberry_factory approved review
Removing from openSUSE:Leap:42.3:Staging:B, re-evaluation needed
jberry_factory added factory-staging as a reviewer
Requesting new staging review
lnussel_factory added openSUSE:Leap:42.3:Staging:B as a reviewer
Being evaluated by staging project "openSUSE:Leap:42.3:Staging:B"
lnussel_factory accepted review
Picked openSUSE:Leap:42.3:Staging:B
maxlin_factory accepted review
ready to accept
maxlin_factory approved review
ready to accept
maxlin_factory accepted request
Accept to openSUSE:Leap:42.3
SUSE:SLE-12:Update/timezone.4418@2a50ca3925d986105124e8d338073d14 -> openSUSE:Leap:42.3/timezone
expected origin is 'SUSE:SLE-12:Update' (unchanged)
timezone submitted from SUSE:SLE-12:Update, no maintainer review needed
needs python-pytz update (pending singlespec) and postgresql94 update to fix tests
neither of those is in ring0, so this can't be the case
ah, you mean they break with this update? Did you file bug reports?
in TW, the fixes in python-pytz is go along with singlespec change https://build.opensuse.org/request/show/481643 however switched to singlespec that means we have to drop python3-pytz, fine for TW, not that well for Leap. postgresql fixes were in Factory already.
the timezone update comes from SLE and python-pytz is also in SLE. In fact, we have the same package even though the lookup file said 42.2. So the python-pytz fix also needs to come from sle. postgresql94 also is a SLE package.
Yeah, there were previous requests that this superseded which had more detail (or so I remember), but seems the same build failure in B for postgres.