On 2019-06-10, Vagrant Cascadian wrote: > On 2019-06-10, Vagrant Cascadian wrote: > I updated to b3fa6273210200cf2694491b07ed5a328e9a4e62 from upstream, > added a few packaging updates, and... The current branch builds a > package! > > https://salsa.debian.org/vagrant/mes
Updated to 0.20 a while back and have iterated through a few test builds on i386, and it appears to be working: https://salsa.debian.org/vagrant/mes > A few test failures on amd64, but i386 tests run fine. Still one test suite failure on amd64, i386 works fine. The failing test on amd64 is: lib/tests/dirent/90-readdir.c Is there any way to mark the failing test as XFAIL conditionally by architecture? A bigger blocker at this point is that mes installs numerous files in /usr/include/, such as /usr/include/alloca.h, that conflict with other packages such as libc6-dev. In a Debian environment, we typically can't have multiple packages shipping the same files in the same PATHS. Other libc implementations seem to put them in /usr/include/IMPLEMENTATION/ subdirs, e.g. /usr/include/mes/. With the /usr/include issue solved and ideally the test suite failure too, it would in my opinion be feasible to upload to Debian! live well, vagrant
signature.asc
Description: PGP signature
