Bug#684385: marked as done (nmu: qt4-x11_4:4.8.2-2)
Your message dated Fri, 10 Aug 2012 22:02:40 +0100
with message-id <1344632560.2978.19.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#684385: nmu: qt4-x11_4:4.8.2-2
has caused the Debian Bug report #684385,
regarding nmu: qt4-x11_4:4.8.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
684385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684385
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Hello, there was a bug in GCC 4.7.1-2 that made apps like okular fail.
Rebuilding with -6 seems to solve this bug.
nmu qt4-x11_4:4.8.2-2 . ALL . -m "Rebuild with gcc/4.7.1-6 (Closes: #684177)."
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: mips
i386
Kernel: Linux 3.2.21+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Thu, 2012-08-09 at 07:42 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hello, there was a bug in GCC 4.7.1-2 that made apps like okular fail.
> Rebuilding with -6 seems to solve this bug.
>
> nmu qt4-x11_4:4.8.2-2 . ALL . -m "Rebuild with gcc/4.7.1-6 (Closes: #684177)."
Scheduled, but only for {kfreebsd-,}{amd64,i386}. gcc-4.7 isn't the
default on most architectures, so the bug won't be manifesting
elsewhere. hurd-i386 buildd admins CCed, as I wasn't sure if all of
their chroots had been upgraded so haven't scheduled a binNMU there.
Please note that binNMUs don't get closure mails generated by dak, so
you'll need to manually close the bug.
Regards,
Adam
--- End Message ---
Reply to: