Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

2016-01-19 Thread Jochen Sprickerhof
Hi, I've pushed changes to libxmlrpcpp-dev to move the base64.h to /usr/include/xmlrpcpp [1]. Would it be ok if I reassign this to libxmlrpcpp-dev and close it, or should we split it, to leave one open for heimdal-dev? * Wookey [2016-01-16 03:26]: > Debian now has this

Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

2016-01-19 Thread Jelmer Vernooij
On Tue, Jan 19, 2016 at 09:38:35AM +0100, Jochen Sprickerhof wrote: > Hi, > > I've pushed changes to libxmlrpcpp-dev to move the base64.h to > /usr/include/xmlrpcpp [1]. Would it be ok if I reassign this to > libxmlrpcpp-dev and close it, or should we split it, to leave one open > for

Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

2016-01-15 Thread Wookey
The two base64.h files are not at all similar, so just referring to the other one does not help. heimdal's just provides two function headers (in a win32-compatible way): ROKEN_LIB_FUNCTION int base64_encode(const void *, int, char **); ROKEN_LIB_FUNCTION int base64_decode(const char *, void *);

Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

2016-01-14 Thread Andreas Beckmann
Package: libxmlrpcpp-dev,heimdal-dev Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1.11.16-2 Control: found -1 1.6~rc2+dfsg-10 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package