On Wed, 2014-06-25 14:12:17 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > On Wednesday 25 June 2014 22:30:34 Aníbal Monsalve Salazar wrote: >> debdiff soprano_2.9.4+dfsg-1.dsc soprano_2.9.4+dfsg-1.1.dsc >> diff -Nru soprano-2.9.4+dfsg/debian/changelog >> soprano-2.9.4+dfsg/debian/changelog >> --- soprano-2.9.4+dfsg/debian/changelog 2013-11-04 15:13:52.000000000 >> +0000 >> +++ soprano-2.9.4+dfsg/debian/changelog 2014-06-24 10:47:30.000000000 >> +0100 @@ >> -1,3 +1,13 @@ >> +soprano (2.9.4+dfsg-1.1) unstable; urgency=medium >> + >> + * Non-maintainer upload. >> + * Update symbols file. >> + Patch by Sphinx Jiang <yishan...@gmail.com>. >> + Work done for Debian GSOC2014. >> + Closes: #746916. > > This doesn't seems to be a patch generated by pkgkde-symbolshelper. > I'm not even sure if it was done with build logs of all archs > available or just one arch. > > Symbols need to be managed differently, it's not just a matter of > building in one arch and diffing. You can take a look at [0] > > [0] <http://pkg-kde.alioth.debian.org/symbolfiles.html> > > Even after completing those steps you need to push to the archive and > see what FTBFS, as (AFAIU) not all archs have already switched to gcc > 4.9. > > So it's not strange to need more than one upload to fix the issue. > > I would recommend letting the maintainer solve this with time (maybe > even waiting for a new upstream release, except if the package is > holding a transition). > > Kinds regards, Lisandro. > > -- > > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/
Hello Lisandro and Sphinx, I tested the patch by building soprano on three arches: mips, mipsel and amd64. I think Sphinx did the same on mips64el and maybe other arches but I'm not sure. Yesterday, I uploaded soprano_2.9.4+dfsg-1.1 to delayed/2 and today I moved it to delayed/10. Please let me know what would you like me to do. :-) Regards, Aníbal
signature.asc
Description: Digital signature
