Hi all,sorry for not checking the API/ABI dependencies/compatibilities of libfreerdp any better.
There are requests to have the new API/ABI (e.g. from the vinagre maintainer), as well. But at the same time, we break several packages from upstream projects that have not migrated their code to the new freerdp-1.1 ABI/API.
On Di 12 Aug 2014 16:29:12 CEST, Luca Falavigna wrote:
2014-08-12 16:19 GMT+02:00 Andreas Cadhalpun <andreas.cadhal...@googlemail.com>:As the API apparently changed, the SONAME change is correct, but according to Policy 8.1, the package name of the library must be changed in such a case.IIRC, API changes should be quite easy to address, renaming the -dev package should be avoided as it introduces a much higher maintenance burden on top of reverse-dependencies, which have to be transitioned with sourceful uploads.Probably the best way forward is to revert to the version in jessie (possibly via an epoch) and then package the new upstream version properly.I think the problem could be better addressed by renaming the library package to libfreerdp1d0, and make sure it builds on all architectures (apparently, it fails in several architectures due to missing symbols, another clue of a potential ABI break).
My suggestion would be to:(1) rename bin:package libfreerdp1 to some other name (actually, I am thinking to package
all lib*.so.* files in individual bin:packages)
(2) rename bin:package libfreerdp-dev to some other name
(3) re-introduce a libfreerdp-1-0 package (providing libfreerdp1)
and a libfreerdp-dev
package providing the older headers. This then would be a new
src:package ((lib)freerdp-1.0).
I guess, this should fix those current issues, right? Happy about feedback... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgp11EbgrSufR.pgp
Description: Digitale PGP-Signatur
