plugwash

"This is caused by CFLAGS in the environment." In addition to the automated test I have also tested this locally by cloning https://github.com/alexcrichton/cc-rs and manually running cargo test, I got...

> Yes, this is an incorrect test. Thanks for confirming > It is true that this allocation will always cause the bump pointer to overflow inside i'm not convinced that...

I guess the remaining question is how should the test distinguish between an uncaught bump pointer overflow (bad) and a successful follow-up allocation (good). And I think the answer to...

Writing a byte per page is not a good idea because the allocation may be HUGE and Linux overcommits memory, so the outcome of doing that may well be that...

Curiously the debian experimental autobuilders build 1.1.1 successfully with gcc6/boost1.61

I just fixed this in Debian, a patch can be found at https://salsa.debian.org/rust-team/debcargo-conf/-/blob/master/src/num-format/debian/patches/fix-tests-32-bit.diff

Debian is in the process of phasing out python 2. The python-fasteners source package has already dropped the python-fasteners binary package which goopg depends on. More packages will likely be...

Using information from https://staff.washington.edu/dittrich/misc/fatgen103.pdf I was able to construct the following recipie to make an image which I believe will suffer from the issue (note: this requires a recent losetup,...

ok i've posted the SD card image I created with the process above at https://plugwash.raspbian.org/badfreespace.bz2 Try writing that to a SD card, then copying the noobs files and booting it...

I am far from an expert (just a maintainer of a Debian derivative who ran into this build failure) but here is my interpretation of what is going on. mapbox::geometry::geometry...