惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 司徒正美
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Last Week in AI
Last Week in AI
大猫的无限游戏
大猫的无限游戏
博客园 - Franky
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
爱范儿
爱范儿
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
博客园 - 叶小钗
博客园_首页
有赞技术团队
有赞技术团队
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
V
V2EX
V
Visual Studio Blog
博客园 - 三生石上(FineUI控件)
S
SegmentFault 最新的问题
量子位
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队

Ana Guerrero Lopez - planet-debian

Introducing debos, a versatile images generator Debconf15 and ... happy birthday Debian! Keysigning, it's never too late DebConf14 and ten years contributing to Debian Debian in the Google Summer of Code 2012 Debian accepted for the Google Summer of Code 2012. Students wanted! RCBSaturday | Ana Guerrero Lopez Help wanted for Google Code-in Qt 3 looking for adopters
long due TO-DO item: removal of Qt3 from Debian
Ana Guerrero Lopez · 2012-05-20 · via Ana Guerrero Lopez - planet-debian

Posts | Tags | Archive

A couple of weeks ago was the first anniversary of orphaning Qt3 in Debian, see bug 625502.

In this year, Qt3 has got a few QA uploads with the most relevant change being support to multiarch. And, more importantly, nobody seemed to care enough to step into maintaining it.

In the last days, I have taken a look into how much needed to be done to remove Qt3 and there were slightly more than 50 packages depending directly or indirectly from Qt3. A removal from Wheezy seemed doable given that removing packages is never a problem during the Debian freeze ;-)
All the packages affected have a bug opened since more than one year and half ago and I have pinged all the bugs with some maintainers responding quick (thanks!). I also filed some removals for packages that were clearly unmaintained and didn't seem worth keeping, with ftp-masters responding quick too (Thanks!). And finally, a couple of QA upload for orphaned software that were still useful without Qt3.

There is a wiki page tracking the status of the removal if you are curious:
http://wiki.debian.org/qt3-x11-freeRemoval

If in the future, you are reading this and you need Qt3 in Wheezy, you can fetch it from Debian snapshots.

Comments

  • Z_God said, on 2012-05-20 22:27:26+02:00:

    I hope the Trinity Desktop project effort is also considered regarding this. See http://www.trinitydesktop.org/

    Second, as far as I am aware, Qt3 is part of the LSB. I suggest caution with making Qt3 unavailable other than regarding the packaged software.

  • ana said, on 2012-05-20 22:33:19+02:00:

    @Z_God: The Trinity Desktop project is understaffed so you hardly can rely on them to give support.

    About LSB, well... a small collateral damages.

  • Kevin Kofler said, on 2012-05-21 14:42:48+02:00:

    Meanwhile, Fedora is still shipping both qt3 and kdelibs3. We found those packages to require very little effort to keep them going, so IMHO dropping them is a pointless disservice to your users.

  • Malvin said, on 2012-05-21 14:57:15+02:00:

    @Kevin Kofler: People wanting the packages it in Debian had a year to take over them and nobody seemed to care.

  • ana said, on 2012-05-21 15:01:13+02:00:

    @Kevin Kofler: Nobody in Debian is willing to invest that 'very little effort' that you say. I disagree greatly that is little effort... Time is very scarce and it is better invested in getting KDE 4.8 or Qt5 pre-releases packaged. We are talking here about software that was EOL 5 years ago :-)

  • Sven said, on 2012-05-21 18:44:21+02:00:

    Maybe there is a slight misunderstanding about what is meant by "keep going". To keep a package building is certainly easy, yet maintaining is something completely different and requires activity as well as knowledge of the code. Which is very hard to cope with if all experts on that code moved on.

    I think it is a good decision to drop packages that build but are de-facto unmaintained.

  • ana said, on 2012-05-21 21:10:57+02:00:

    @Sven: thank sven, good point. When I talk of maintenance I talk of both: Debian maintenance (that needs some time but it is feasible) and 'upstream maintenance' (that requires a lot of knowledge and can quite time consuming)

  • Z_God said, on 2012-05-23 19:21:56+02:00:

    Here is the (positive!) response from the primary Trinity developer: http://trinity-devel.pearsoncomputing.net/?0::8388

  • Kevin Kofler said, on 2012-05-26 12:18:24+02:00:

    @Sven: Those libraries have very few bugs that need fixing (mainly FTBFS issues with current g++, a couple aliasing issues with newer g++, and the occasional security issue). Given that those are compatibility libraries, I don't see what other "upstream" maintenance you'd even need other than build fixes, build-induced regression fixes (e.g. stricter GCC/g++ strict aliasing) and (of course) security fixes. Nobody is (nor should be) reporting functionality bugs (and definitely not feature requests) against those libraries.

  • Kevin Kofler said, on 2012-05-26 12:22:04+02:00:

    PS: To be clear, the FTBFS/aliasing/security bugs we know about are already fixed in the current Fedora packages.

  • Malvin said, on 2012-05-26 12:25:07+02:00:

    @Kevin Kofler: Does Fedora also support all the archs that debian does?

  • poroto said, on 2012-05-28 17:46:44+02:00:

    Removing qt3 is a BAD IDEA, too many software non-Debian packaged still depends on it. Will make life harder for many people.

  • ana said, on 2012-05-28 17:50:28+02:00:

    @poroto: could you please share the information you use to say 'too many' software out of Debian do use Qt3?