Bug#894795: kde-full currently uninstallable

Package: kde-full Version: 5:100 Severity: serious Dear Maintainer, kde-full from meta-kde 5:100 depends on kdepim 4:17.12.xxx, but meta-kde provides the packages kdepim in Version 4:17.08.xxx. Two untested fixes (choose one!) have been provided at

Bug#868868: emacs25: Please include patch to fix FTBFS on m68k

> On Jul 19 2017, John Paul Adrian Glaubitz > wrote: > >> "sizeof(struct Lisp_Symbol) is 22 bytes on m68k, but the code expects >> the >> size of the object to be dividable by 8." > > No, it doesn't. See union aligned_Lisp_Symbol. Yes, it does, although this most

Bug#849270: tin: forced authentication (-A) broken

without authentication, so forced authentication is needed here. Regards, Michael Karcher -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386

Bug#828141: firebird2.5: Please add platform support for m68k

On 30.06.2016 02:29, John Paul Adrian Glaubitz wrote: Hello! Attaching an updated patch which includes an additional alignment fix for m68k by Michael Karcher. He discovered that "sem_t" was incorrectly aligned to 16 bits which resulted in "create_db" crashing with [1]: s

Bug#792204: Setting default CPU to ultrasparc for -m32 on sparc64 does not work

providing lock-free atomics. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768574: gcc-4.9: Miscompilation of boolean negation on SH4 using -O2

Package: gcc-4.9 Version: 4.9.1-16 Severity: important The currently available version of gcc 4.9 for mips miscompiles boolean negation under certain circumstances. The assembly contains the not instruction, which represents bitwise negation, which is not appropriate, as both 0 and 1 get mapped

Bug#768574: Acknowledgement (gcc-4.9: Miscompilation of boolean negation on SH4 using -O2)

Of course I meant to write The currently available version of gcc 4.9 for sh4... in the first paragraph of the bug description. I am sorry for any confusion this might have caused. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#682067: git can not clone fai config space

to unset it temporarily in a subshell: ( unset GIT_WORK_TREE; git clone --branch ... ) I would be happy if someone tested this suggestion and can confirm that it works. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe

Bug#682067: git can not clone fai config space

is thus a different patch: unset GIT_WORK_TREE for the checkout by running GIT_WORK_TREE= git clone --branch $gitbranch $giturl $FAI you don't need to specify the work tree in the environment variable, as you already pass the value on the command line. Regards, Michael Karcher

Bug#707215: [kdevelop] Crashes when opening some C files

Package: kdevelop Version: 4:4.3.1-3+b1 Followup-For: Bug #707215 The solution to this bug is indeed to rebuild kdevelop, as this bug is caused by a bug in g++ 4.7.0 and 4.7.1 that caused ABI changes in returning std::pairs (see http://gcc.gnu.org/gcc-4.7/changes.html). The solution is to

Bug#703281: rygel security issue

available while rygel is running. Regards, Michael Karcher -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.0+ (SMP w/2 CPU cores

Bug#704769: FTBFS on s390x sid buildds.

-backed directory makes it fail on the porterbox, too. The upstream diff from the mentioned commit is attached. Regards, Michael Karcher -- System Information: Debian Release: 6.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.1-amd64

Bug#624507: #624507 - Started looping and continuously rewriting metadata file - Debian Bug report logs

recording on remote file systems would help in scenario a, but not in scenario b. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#634261: [sparc] iceweasel: Bus Error in setbuf()

are still waiting for a real manifestation of the original bug, which should occur with libio 2.0 programs only. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#695614: CVE-2012-6303: buffer overflows

The attached patch fixes the buffer overrun for the fixed-size header buffer. --- snack-2.2.10-dfsg1/generic/jkSoundFile.c 2005-12-14 12:29:38.0 +0100 +++ snack-2.2.10-dfsg1+karcher/generic/jkSoundFile.c 2013-01-02 00:29:56.836287036 +0100 @@ -1796,7 +1796,14 @@ GetHeaderBytes(Sound *s,

Bug#634261: [sparc] iceweasel: Bus Error in setbuf()

assumptions and breaks on sparc. Regards, Michael Karcher [1] This is why Bernhard R. Link observed the two different alignof values. You choose between the two variants of FILE/_IO_FILE by defining or not defining _IO_USE_OLD_IO_FILE. In oldstdfile.c, the symbol is defined, while in genops.c

Bug#660411: libxi6: Memory corruption when used with recent X servers

for a stable update. Commit http://cgit.freedesktop.org/xorg/lib/libXi/commit/?id=635c2c029b1e73311c3f650bcaf7eeb9e782134b fixes the problem and applies (with offset and fuzz, though). Regards, Michael Karcher -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500

Bug#660413: ia32-libs: contained libxi corrupts memory with recent X servers

Package: ia32-libs Version: 20120102 Severity: important ia32-libs contains libxi6 2:1.3-6, which is affected by #660411. Recent versions of Wine use XInput 2 if available, which causes memory corruption and possible crashes. As mentioned in #660411 this affects security in case of a malign X

Bug#637931: results obtained with the perl debugger

further why there was no call to open_log. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#600589: hostapd + bridge for post 2.6.32

bridge_hw 00:0f:b5:80:d3:25 hostapd /etc/hostapd/hostapd.conf And in /etc/hostapd/hostapd.conf I have interface=wlan0 bridge=br0 Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#553412: imapsync: Fixable by uncommenting 'use Term::ReadKey;'

by changing the 'grep use' with 'grep use or require'. Did you even bother to check whether debian uses automatic tools to find the dependency? And now to something productive: Debian should just upgrade to a newer upstream version to fix the bug. Regards, Michael Karcher -- To UNSUBSCRIBE, email

Bug#553412: imapsync: Fixable by uncommenting 'use Term::ReadKey;'

in stable, too, even up to the point of recompiling patched packages. Regards, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#571640: debhelper: qmake build system can't be set to use qmake-qt3 or qmake-qt4

Debian Systems, without needing a Build-Conflicts on Qt3's qmake. Thanks for your response to the bug report, Michael Karcher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#571640: debhelper: qmake build system can't be set to use qmake-qt3 or qmake-qt4

the automatic build system unable to build Qt 4 packages. An option to choose either qmake-qt3 or qmake-qt4, or even hard wiring qmake-qt4 as the automatic build system is mainly used for new packages that mainly use qt4 would be nice, IMHO. Regards, Michael Karcher -- System Information: Debian

Bug#551783: libgpgme11: FTBFS with concurrency enabled (-jN)

Package: libgpgme11 Version: 1.2.0-1 Severity: normal while debian policy does not mandate that debian/rules is concurrency-safe, it is surely a nice thing. Regretfully the debian/rules contains a flaw that makes it unsafe: begin quote build: configure-stamp build-stamp build-stamp: end quote

Bug#550958: gparted: The error message for NTFS partitions if ntfsprogs is not installed is too generic

Package: gparted Version: 0.4.6-2 Severity: wishlist When I run gparted on a system without ntfsprogs installed, I get the warning sign on NTFS partitions because gparted can't work on NTFS partitions without ntfsprogs. That's all fair, but the explanation for the warning sign is Unable to read

Bug#548124: xmakemol-gl is compiled without GL support

sneaked into the package that should be OpenGL enabled. Regards, Michael Karcher -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31

Bug#483975: xosview: Interrupt indicator shows a dead place before last IRQ

Package: xosview Version: 1.8.3+debian-6 Severity: minor Tags: patch xosview parses /proc/interrupts and stops parsing a little bit too late, so the last number from /proc/interrupts gets processed twice. Please apply the attached patch. Regards, Michael Karcher -- System Information: Debian

Bug#483815: xosview crashes if interrupt numbers exceed 1024

Package: xosview Version: 1.8.3+debian-6 Severity: normal Tags: patch xosview has a fixed-size array mapping numbers from /proc/interrupts to interrupt indicator positions. The size of this map is 1024. On some x86-64 system (and probably modern i386 systems too) with PCI express, the interrupt

Bug#245282: dmsetup: So, please at least document --showkeys

Package: dmsetup Version: 2:1.02.24-3 Followup-For: Bug #245282 While I agree on not documenting everything about possible mappings in dmsetup, I am not happy about the lack of documentation of features dmsetup itself provides, in this case, --showkeys. A patch is included. Regards, Michael

Bug#353494: Xserver SIGILL on processors without CPUID

-party repository that includes this kind of harmless bug fixes (I would call it something like stable-recommended-updates), do you have any pointers to a discussion on debian-devel about this subject? Regards, Michael Karcher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#353494: Xserver SIGILL on processors without CPUID

might not get around to before christmas), but the obviously wrong x86 code in gdb's disassembly is gone. Regards, Michael Karcher --- xorg-server-1.1.1/fb/fbpict.c.orig 2007-12-24 10:37:26.0 +0100 +++ xorg-server-1.1.1/fb/fbpict.c 2007-12-24 10:37:50.0 +0100 @@ -1378,7 +1378,7

Bug#353494: Xserver SIGILL on processors without CPUID

. And it looks like the f suffix is there now. So if you are right, the bug should be fixed in unstable already. Any chance of getting the fix in the next point release? Probably not, as it is not security related. Regards, Michael Karcher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Bug#408562: joe: Bug is known upstream

Package: joe Version: 3.5-1.1 Followup-For: Bug #408562 This bug is in the upstream bug tracker at http://sourceforge.net/tracker/index.php?func=detailaid=1626910group_id=23475atid=378598 reported since 11 months now. A patch is present, which works. Please apply in debian. Regards, Michael

Bug#453310: joe: This bug is known upstream.

Package: joe Version: 3.5-1.1 Followup-For: Bug #453310 This bug is in the upstream bug tracker at http://sourceforge.net/tracker/index.php?func=detailaid=1626910group_id=23475atid=378598 reported since 11 months now. A patch is present, which works. Please apply in debian. Regards, Michael

Bug#455503: joe: No replace possible in german translation

, Michael Karcher -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (490, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-rc1-hrt1 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF

Bug#449395: unace-nonfree: Unace-Nonfree not 64-bit clean, but available for amd64

to unace (the old, free version). I will probably supply a patch this week, and attach it to this bug. Regards, Michael Karcher -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (490, 'unstable'), (1, 'experimental

Bug#436146: wodim: Prints hint to use dvd+rw-mediainfo on -msinfo invocation

. 0,0 The extra first line is confusing programs like gnomebaker, so multisession disks cannot be created. I also consider it as quite useless in this case. A patch that prints this hint only in verbose mode is attached. Greetings, Michael Karcher -- System Information: Debian Release: lenny/sid

Bug#360373: evolution: Also appears in 2.6.1

Package: evolution Version: 2.6.1-2 Followup-For: Bug #360373 This problem also occurs in the version of evolution in sid, at least with the library version my mixed system uses. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (930, 'testing'), (500, 'unstable'),

Bug#350743: libkexi-dev: kexidb/connection.h includes tristate.h instead of kexidb/tristate.h

path, so it should read #include kexidb/tristate.h Michael Karcher -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (930, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.15-rc4-g785a6436 Locale: LANG=de_DE, LC_CTYPE=de_DE

Bug#350743: libkexi-dev: kexidb/connection.h includes tristate.h instead of kexidb/tristate.h

Am Dienstag, den 31.01.2006, 15:40 + schrieb Martin Ellis: On Tuesday 31 January 2006 14:13, Michael Karcher wrote: /usr/include/kde/kexidb/connection.h contains the line #include tristate.h which should include the provided tristate header file. The other include directives indicate

Bug#350743: libkexi-dev: kexidb/connection.h includes tristate.h instead of kexidb/tristate.h

. Can I rely on kde_includes to be a stable interface that contains the path to the KDE headers even if they are in a standard location, so that -I$(kde_includes)/kexidb will work? If so, I will close the bug. Michael Karcher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject