Your message dated Sun, 18 Aug 2019 18:33:58 +0200 with message-id <20190818163358.GB21960@nouzonket> and subject line ns3 does not actually depends on Qt4 has caused the Debian Bug report #875071, regarding [ns3] Future Qt4 removal from Buster to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ns3 Version: 3.26+dfsg-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg00006.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---Hello, I fail to see why this bug was ever open. This is the netanim part of ns3 that (used to) depends on Qt4. According to the changelog and git logs, I built netanim from the ns3 sources for 3 days only: from v3.25+dfsg2-2 (released 17 Apr 2016) to v3.25+dfsg2-3 (released 20 Apr 2016). I removed it right away because of #821369 (ns3 and netanim: error when trying to install together). This bug, #875071, was opened against ns3 source package v3.26+dfsg-1 on 9 Sep 2017. I did not close it before because we need to re-integrate netanim at some point since both ns3 and netanim are built (partially) from the same sources. This is still to be done, but that's not a reason to leave #875071 open, thus closing. Sorry for the delay, Mt. -- I don't suffer from Insanity, I enjoy every minute of it...signature.asc
Description: PGP signature
--- End Message ---