On Mon, 26 Nov 2012 13:25:12 +0100 Sylvestre Ledru <sylves...@debian.org> wrote: > > Regarding the current clang packages in the repositories (3.0 in > > testing, 3.1 in unstable), you would have to add an epoch to > > downgrade clang to 3.0 in unstable with a fix and then have to fix > > migrated to testing. This would also fix the issue above, but > > epochs are, well, not beautiful... > > > > What is your opinion regarding those issues? > I don't know. It is why I asked to the release team for guidance. IMO, the correct way to deal with this is to prepare an upload of clang 3.0-7 (currently in testing is 3.0-6) which includes *ONLY* the fix necessary for closing this bugreport. I have looked at both versions (3.0-6 and 3.2~rc3), but I can’t say for sure which change it is.
Afterwards, generate a debdiff between clang_3.0-6.dsc and clang_3.0-7.dsc and attach it to this bugreport, asking the release team for approval to upload it to testing-proposed-updates. See also: http://www.debian.org/doc/manuals/developers-reference/pkgs.html#t-p-u http://release.debian.org/wheezy/freeze_policy.html -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
