Bug#582570: marked as done (megahal: produces broken binaries with current python-support)

Your message dated Sat, 22 May 2010 01:31:32 +0200 with message-id <4bf717d4.1030...@debian.org> and subject line Bug#582570: fixed in megahal 9.1.1a-7 has caused the Debian Bug report #582570, regarding megahal: produces broken binaries with current python-support to be marked as done. This means

megahal_9.1.1a-8_amd64.changes ACCEPTED

Accepted: megahal_9.1.1a-8.diff.gz to main/m/megahal/megahal_9.1.1a-8.diff.gz megahal_9.1.1a-8.dsc to main/m/megahal/megahal_9.1.1a-8.dsc megahal_9.1.1a-8_amd64.deb to main/m/megahal/megahal_9.1.1a-8_amd64.deb Override entries for your package: megahal_9.1.1a-8.dsc - source misc megahal_

megahal_9.1.1a-7_amd64.changes ACCEPTED

Accepted: megahal_9.1.1a-7.diff.gz to main/m/megahal/megahal_9.1.1a-7.diff.gz megahal_9.1.1a-7.dsc to main/m/megahal/megahal_9.1.1a-7.dsc megahal_9.1.1a-7_amd64.deb to main/m/megahal/megahal_9.1.1a-7_amd64.deb Override entries for your package: megahal_9.1.1a-7.dsc - source misc megahal_

Processing of megahal_9.1.1a-8_amd64.changes

megahal_9.1.1a-8_amd64.changes uploaded successfully to localhost along with the files: megahal_9.1.1a-8.dsc megahal_9.1.1a-8.diff.gz megahal_9.1.1a-8_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-re

Processing of megahal_9.1.1a-7_amd64.changes

megahal_9.1.1a-7_amd64.changes uploaded successfully to localhost along with the files: megahal_9.1.1a-7.dsc megahal_9.1.1a-7.diff.gz megahal_9.1.1a-7_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-re

Bug#582570: megahal: produces broken binaries with current python-support

Package: megahal Version: 9.1.1a-6 Severity: serious Hello, When rebuild in sid environment, megahal binaries didn't contain any Python modules: $ debdiff --nocontrol {archive,sid}/megahal_9.1.1a-6_*.deb [The following lists of changes regard files as different if they have different names,

Bug#463598: /var/run/utmp exists, but wdm still doesn't register the session

Package: wdm Version: 1.28-3.5 Followup-For: Bug #463598 Hello! Let me firstly thank you for your work on this package and for reading this:) So here's what the report is about: I've also noticed that wdm doesn't register the session it starts to utmp, but in my case /var/run/utmp exists on my s

Bug#582538: (knetfilter_3.5.0-2/avr32): FTBFS: Outdated config.{sub,guess}

Package: knetfilter Version: 3.5.0-2 Severity: wishlist User: bradsm...@debian.org Usertags: avr32 Hi, Whilst building your package on AVR32, the build failed due to outdated config.{sub,guess} files. Full build logs available: http://buildd.debian-ports.org/build.php?pkg=knetfilter&arch=avr3

Bug#582535: (kcemirror_0.1.5-3/avr32): FTBFS: Outdated config.{sub,guess}

Package: kcemirror Version: 0.1.5-3 Severity: wishlist User: bradsm...@debian.org Usertags: avr32 Hi, Whilst building your package on AVR32, the build failed due to outdated config.{sub,guess} files. Full build logs available: http://buildd.debian-ports.org/build.php?pkg=kcemirror&arch=avr32&

crystalcursors 1.1.1-11 MIGRATED to testing

FYI: The status of the crystalcursors source package in Debian's testing distribution has changed. Previous version: 1.1.1-10 Current version: 1.1.1-11 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you wil

Bug#582517: crystalcursors: Update-alternatives errors

Subject: crystalcursors: Update-alternatives errors Package: crystalcursors Version: 1.1.1-11 Severity: normal Hi, last update made crystalcursos uninstallable: Setting up crystalcursors (1.1.1-11) ... update-alternatives: using /etc/X11/cursors/crystalblue_classic.theme to provide /usr/share/ico

Bug#555325: Bug located, patch will follow

Please ignore my previous message, it was targeting a different gq bug. But somehow i fear it might be related. signature.asc Description: PGP signature

Bug#555325: Bug located, patch will follow

Hi! Michael Stapelberg successfully located the problematic piece of code. For some reason, the problem is only visible on amd64. On i386, gq behaves just fine and shows an error message. The problem is an incorrect reuse of a va_list structure in errorchain.c. I'm currently preparing a patch.