Re: Bug#709382: Built-Using, libgcc, and libc_nonshared

2013-05-23 Thread Thorsten Glaser
Russ Allbery dixit: >Thorsten Glaser writes: >> If not… well, since snapshot.d.o is an official service now, I’d say, […] >Hm, that's an interesting point, indeed. >> Are those source packages (that would not otherwise be kept in the >> archive) released along with “stable”, despite having no bi

Re: Bug#709382: Built-Using, libgcc, and libc_nonshared

2013-05-23 Thread Russ Allbery
Thorsten Glaser writes: > There’s something else about Built-Using: > Are those source packages (that would not otherwise be kept in the > archive) released along with “stable”, despite having no binary > packages? Yes, I believe that's how the implementation works. > If not… well, since snaps

Re: Bug#709382: Built-Using, libgcc, and libc_nonshared

2013-05-23 Thread Thorsten Glaser
Russ Allbery dixit: >of the GPLv2, the GPLv2 itself requires that all of the *source* for the >binary be distributed under the GPLv2. And the libgcc *source* is only >available under the GPLv3, and the runtime exception doesn't allow one to >distribute the *source* under different terms, only the

Re: Bug#709382: Built-Using, libgcc, and libc_nonshared

2013-05-23 Thread Thorsten Glaser
Russ Allbery dixit: >If we do need to preserve source for the libcc and libc components >incorporated into binary builds, that's going to mean Built-Using for >nearly the whole archive, and a lot of complexity on the DAK side. That's >obviously not very desirable. We would rather decide that we