In that case python3-nbxmpp 4.x must not migrate either, because it breaks Gajim 1.5.x. I'm not sure what's the proper way to achieve that, should I file another bug or is there some "blocks" mechanism in the BTS?
- Bug#1028192: gajim: Gajim 1.6.0-1 crashes on connect Fiona Klute
- Bug#1028192: gajim: Gajim 1.6.0-1 crashes on connec... Martin
- Bug#1028192: Needs to block python3-nbxmpp Fiona Klute
- Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in ... Martin
- Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in ... Martin
- Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in ... Martin
- Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in ... Sebastian Reichel
- Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes... Martin
- Bug#1028638: libproxy1v5: Gajim 1.6.0-1 cra... Sebastian Reichel
- Bug#1028638: libproxy1v5: Gajim 1.6.0-1... Sebastian Reichel
- Bug#1028192: gajim: Same for Gajim 1.6.1-2 bert