Bug#381622: textclass.lst

I did not look into this very deep but as far as I can tell those files are now longer existing as global files. They're now created in ~/lyx/ for every user. Same for packages.lst if this pops up somewhere else. Sven -- If you won't forgive me the rest of my life Let me apologize while I'm

Bug#380421: marked as done (libgnome-mag2 should provide libgnome-mag.so.2, not libgnome-mag.so.1)

Your message dated Sun, 06 Aug 2006 14:17:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#380421: fixed in gnome-mag 1:0.13.1-1 has caused the attached Bug report 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

Processed: retitle 335274 to matanza: completely broken packaging

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 retitle 335274 matanza: completely broken packaging Bug#335274: completly broken packaging Changed Bug title. End of message, stopping processing here. Please contact me if you need

Bug#381655: marked as done (python-jaxml: Problems installing the package (post-installation))

Your message dated Sun, 06 Aug 2006 14:32:17 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#381655: fixed in jaxml 3.01-3 has caused the attached Bug report 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

Bug#381622: textclass.lst

Per Olofsson a écrit : Hi, You're right, these files should be removed upon upgrade. Regarding the FTBFS, the problem seems to be that lyx doesn't automatically perform a Reconfigure if run in batch mode. We should probably forward this bug upstream. Well you mean this file is now

Bug#381718: marked as done (lyskom-elisp-client: wipes out /usr/share/$FLAVOR/*.el)

Your message dated Sun, 06 Aug 2006 13:48:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#381718: fixed in lyskom-elisp-client 0.48-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#365698: marked as done (pan_0.95-2(sparc/experimental): FTBFS: missing b-d on dpatch)

Your message dated Sun, 6 Aug 2006 23:11:22 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in upload of 0.106 to unstable has caused the attached Bug report 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

Bug#381572: Downgrade

* Matthias Klose [EMAIL PROTECTED] [2006-08-06 23:40]: If I understand correctly, this bug only applies to m68k, non-release architecture, so I'm downgrading to important. no. Actually, yes, because I split the Alpha bug off into its own bug, and even the Alpha bug shouldn't be grave since

Processed: severity of 381572 is important

Processing commands for [EMAIL PROTECTED]: severity 381572 important Bug#381572: [m68k] ICE in extract_insn, at recog.c:2084 Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#381512: 381512 notes

Reverting the obvious patch does not fix this problem. I will have to spend more time looking at what is changing between -4 and -5. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer

Bug#335274: matanza: 335274: new packaging

Paul, Your matanza_0.13-3.2.diff.gz applies cleanly against the 0.13 orig.tar.gz but you need to include the matanza_0.13-3.1.diff.gz. Re-edit the files and recreate the -3.2.diff.gz so that the 3.1 changes are incorporated. Your patch fails because it tries to back out some of the -3.1 changes.

Bug#381512: Reverting patch seems to fix it

Reverting the linelist patch appears to fix the problem. I'll have to test it a bit better. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer csmall at : enc.com.au

Bug#380663: cupsys not starting at all

Package: cupsys Version: 1.1.23-10sarge1 Followup-For: Bug #380663 -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=C

Bug#378712: zope-ttwtype

Hi, I wonder whether anybody is interested to take over zope-ttwtype that has one serious bug (#378712). While there is a quite simple patch attached I hesitate to apply this without testing. The problem is that I stopped using this Product for years and upstream did not updated it since 3

Bug#380663: [Pkg-cups-devel] Bug#380663: cupsys not starting at all

At Mon, 07 Aug 2006 09:57:29 +0530, Debansu Saha wrote: Package: cupsys Version: 1.1.23-10sarge1 Followup-For: Bug #380663 ii libcupsimage2 1.1.23-10sarge1Common UNIX Printing System(tm) - pi libcupsys2 [libcupsys 1.2.1-2bpo1Common UNIX Printing System(tm) - pi

Bug#381666: libselinux: FTBFS on powerpc (refers to PAGE_SIZE not supplied by ppc kernel-headers)

On Sun, 06 Aug 2006 03:34:31 -0700, Devin Carraway [EMAIL PROTECTED] said: Package: libselinux Severity: serious Justification: no longer builds from source This may be the fault of linux-kernel-headers more than libselinux, but as of linux-kernel-headers 2.6.17-6-1, I can't build

<    1   2