On Sat, Dec 12, 2020 at 10:32:15AM +0100, Lucas Nussbaum wrote: > Hi Andreas, > > Is the above problem going to be a problem at runtime as well?
It depends on which part of /proc you use and how it deviates on your architecture, but yes... eventually you'll hit something that errors out in parsing or worse returns an answer that's just wildly wrong/unexpected. > If so, I wonder if you should make this package "Architecture: amd64" > instead of "Architecture: all". [...] In theory, the right question is probably what anyone is willing to support. Debian usually takes the naive approach of assuming porters will fix up any issues once they're found, but that's not really how things turn out in practise. (Also if we limit the archs, what is the correct subset? The ones where the testsuite succeeds? The ones where it actually works? The ones which someone is actually promising to support?) The practical problem is that if the arch field is changed what happens to the entire reverse dependency tree that has accumulated? Getting one thing removed from the archive is hard and painful enough.... Regards, Andreas Henriksson
