Lisandro Damián Nicanor Pérez Meyer dixit: >m68k is not a release arch so the severity should be at most normal.
No: for non-release archs, “important” is the cap, and FTBFS are RC if the package built before (means important due to the cap) and important if it did not build before. >The patch won't work because on the next upload we will be using the system's >double-conversion lib. Just check that the lib builds on m68k and problem >fixed. I’ll have a look. It was previously marked Not-For-Us due to, I assume, this exact problem, but it appears having been fixed upstream. >By the way, don't waste your time with symbols patches. We get symbols from >build logs, and m68k is already present in debian-ports, so they will be used >on the next upload. This is wrong for several reasons, mostly that the symbols list is wrong, so the next (regular) upload would fail, and only the second-to-next upload would succeed. Plus, we actually need the lib *right now*, to be able to build things such as qt5webkit, so I need to prepare the symbols file patches *anyway* because I have to upload the package to dpo “unreleased”. bye, //mirabilos -- This space for rent. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1502181821240.26...@herc.mirbsd.org
