Is it ok? It doesn't currently block anything, but I have a dep (net-p2p/retroshare) that will need. Otherwise I wouldn't mind a more recent snapshot if there is any and go for stabilizing that one. CC arches if you agree
if you don't want net-libs/qmf stabilized we can just mask the "messaging" useflag then
I was actually preparing a snapshot bump for qt-mobility but got distracted by RL issues. I believe it'll happen next week, and I'd rather try to stabilize that if you don't mind waiting an additional 30 days. qmf-4.0.2 is ok.
(In reply to Davide Pesavento from comment #2) > I was actually preparing a snapshot bump for qt-mobility but got distracted > by RL issues. I believe it'll happen next week, and I'd rather try to > stabilize that if you don't mind waiting an additional 30 days. That's ok > > qmf-4.0.2 is ok. Please fix title and CC arches.
(In reply to Davide Pesavento from comment #2) > qmf-4.0.2 is ok. FYI, qmf-4.0.3 is recently released (although it mostly seems to be your upstream patches :P).
(In reply to Michael Palimaka (kensington) from comment #4) > FYI, qmf-4.0.3 is recently released (although it mostly seems to be your > upstream patches :P). Then I'll bump that too and stabilize qt-mobility and qmf together after 30 days.
Arches, please proceed.
amd64 stable
x86 stable. Last arch, closing