-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/12/2012 18:24, Julien Cristau wrote: > On Mon, Nov 26, 2012 at 11:40:06 +0100, Sylvestre Ledru wrote: > >> So, to fix this issue, should I do the following ? >> >> * ask for a removal of clang 3.1 in unstable * upload a version >> 3.0 in unstable with Peter patch * ask for an exception >> > I'm not sure what the point of your first step would be. But yes, > to fix this issue you need to upload a fix to sid, and then either > get that fix migrated or get a fix in to tpu. Why is this so > hard? Because the version in unstable is 3.1 and in testing, we have 3.0.
If I upload a 3.0 in unstable, I guess it is going to be rejected, isn't it ? Sylvestre -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlDgNZ8ACgkQiOXXM92JlhAmUwCfa5iVhoJLYTb7oHsO0adb0j7K Z9UAnRH4VR+H0BSbQ1qKSJpFjRAGQd1W =YtJW -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
