Hi,
Wilmer van der Gaast wrote (17 Sep 2013 13:33:53 GMT) :
> Argh! I had no idea this was blocking other packages, sorry. :-( Well
> it'd be easy to just omit the bitlbee-plugin-otr package from Debian for
> now while this is getting resolved.
> Although omitting a single binary package is probably easier said than
> done.
> I have very little time for this stuff at the moment, sadly. :-(
Would you mind a NMU that disables building of bitlbee-plugin-otr in
debian/control, drops the build-dep on libotr2-dev, comments out
everything related to otr in debian/rules, and disables building of
the OTR stuff at configure time? (+ everything I'm missing)
If we decide to go this way: I don't use bitlbee myself, so I would
not mind if someone could test the packages before I upload them.
My knowledge of transitions is near-zero, but I believe the
alternatives to be:
1. $someone actually finishes the porting work $soon
2. remove bitlbee from testing altogether to make it stop blocking
the libotr5 transition
What do you think?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
