Bug#922005: RM: mash [mips mips64el mipsel s390x hppa hurd-i386 ia64 powerpc ppc64 sparc64] -- ROM; Does not build on all architectures due to new Build-Depends
On Mon, Feb 11, 2019 at 12:26:46PM +, James Clarke wrote: > I don't see why this is necessary. Upload a fixed libmurmurhash and then > we don't have to regress. The only reason libmurmurhash is currently not > built on those architectures is because the test suite runs the > non-portable reference implementation, which fails to byte-swap on > big-endian machines and therefore gives a (consistent) different output. > This has been fixed upstream in [1]. Just upload a -3 with this patch. > Unless there's something else I'm missing, I'm disappointed that this is > the action you take rather than spend the 5-10 minutes required to fix > the problem. Sorry for disappointing you. My action was motivated by the upcoming freeze. I wanted to see mash migrating to testing before tomorrow. If the fixed libmurmurhash would be uploaded the other arches become build automatically and will be back again - it was not a wimpy attempt to loose that architectures that should create any disappointment. Thank you Andreas. > [1] > https://github.com/kloetzl/libmurmurhash/commit/3b6fc731ae4b6405a2073a2b839884f75b6e6f31 -- http://fam-tille.de
Bug#922005: RM: mash [mips mips64el mipsel s390x hppa hurd-i386 ia64 powerpc ppc64 sparc64] -- ROM; Does not build on all architectures due to new Build-Depends
Control: tags -1 moreinfo On Mon, Feb 11, 2019 at 08:08:22AM +0100, Andreas Tille wrote: > Package: ftp.debian.org > Severity: normal > > Hi, > > due to the new dependency libmurmurhash which is not yet build on all > architectures mash is not build on all architectures where it has build > before. The background is that the new version of mash (as many other > Debian packages) was shipping a code copy of libmurmurhash which was > even less portable than the libmurmurhash package. There is work > ongoing to make libmurmurhash building on all supported architectures > but since we are approaching the freeze this will not happen right in > time. So please remove the said architectures for the time beeing to > enable mash migrating to testing. > > Thank you for your work as ftpmaster I don't see why this is necessary. Upload a fixed libmurmurhash and then we don't have to regress. The only reason libmurmurhash is currently not built on those architectures is because the test suite runs the non-portable reference implementation, which fails to byte-swap on big-endian machines and therefore gives a (consistent) different output. This has been fixed upstream in [1]. Just upload a -3 with this patch. Unless there's something else I'm missing, I'm disappointed that this is the action you take rather than spend the 5-10 minutes required to fix the problem. James [1] https://github.com/kloetzl/libmurmurhash/commit/3b6fc731ae4b6405a2073a2b839884f75b6e6f31
Bug#922005: RM: mash [mips mips64el mipsel s390x hppa hurd-i386 ia64 powerpc ppc64 sparc64] -- ROM; Does not build on all architectures due to new Build-Depends
Package: ftp.debian.org Severity: normal Hi, due to the new dependency libmurmurhash which is not yet build on all architectures mash is not build on all architectures where it has build before. The background is that the new version of mash (as many other Debian packages) was shipping a code copy of libmurmurhash which was even less portable than the libmurmurhash package. There is work ongoing to make libmurmurhash building on all supported architectures but since we are approaching the freeze this will not happen right in time. So please remove the said architectures for the time beeing to enable mash migrating to testing. Thank you for your work as ftpmaster Andreas.
