block version that requires zimlib 8.1.0

Bug #2008603 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-libzim (Debian)
Fix Released
Unknown
python-libzim (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

python-libzim 2.1.0 is stuck in Debian unstable because it requires zimlib 8.1.0 which was briefly in Debian but was rolled back. When in the future zimlib moves forward again, python-libzim 2.1.0 will be releasable so we don't want to delete this version from the archive, but we do want it to wait in -proposed until it can migrate without being buggy.

Steve Langasek (vorlon)
tags: added: block-proposed
Revision history for this message
Graham Inggs (ginggs) wrote :

removing block-proposed so that 1.1.1+ds-3build1 can migrate

tags: removed: block-proposed
Changed in python-libzim (Debian):
status: Unknown → New
Revision history for this message
Steve Langasek (vorlon) wrote :

1.1.1+ds-3build1 migrated, re-syncing 2.1.0 to -proposed and re-adding block tag.

tags: added: block-proposed
Changed in python-libzim (Debian):
status: New → Fix Released
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Debian has released zimlib 8.1.1 to Unstable so I synced it to clear up this todo item.

Changed in python-libzim (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.