Hi Mike,
On 12.08.2014 17:02, Mike Gabriel wrote:
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.
I'm not sure how vinagre uses freerdp, but it doesn't build-depend on
libfreerdp-dev and the binary package only recommends freerdp-x11.
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.
There are only four packages build-depending on libfreerdp-dev:
* guacamole-server: builds with new API
* remmina: fails to build for unrelated reasons
* vlc: FAILS with new API
* xrdp: builds with new API
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?
Given that there are only 4 reverse-build-dependencies and only one of
them fails to build with the new API, this plan seems to be overkill.
I think it would be better to:
a) fix the current breakage by reverting to the version in jessie
b) upload the new version with new package names to experimental
c) create a patch for VLC (possibly with upstream help)
d) upload the new freerdp to unstable
e) upload the patched VLC and request binNMUs for the others
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
