Bug#292478: oops on boot with usb cdburner attached

Works fine for me booting with Kernel 2.6.8-2, IBM ThinkPad R40e type 2684, external USB Plextor PX-S2410TU using USB 1.1.

Bug#305469: marked as done (cupsys: /usr/lib/cups/backend/http missing)

Your message dated Wed, 20 Apr 2005 15:11:05 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#305469: cupsys: /usr/lib/cups/backend/http missing 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

Bug#305469: cupsys: /usr/lib/cups/backend/http missing

Package: cupsys Version: 1.1.23-9 Severity: grave Justification: renders package unusable When starting up cuspsys and attempting to print, this shows up in the logs: I [19/Apr/2005:22:53:36 -0700] Started backend /usr/lib/cups/backend/http (PID 17285) for job 67. E [19/Apr/2005:22:53:36 -0700]

Bug#302378: samba: smbd exits with SIGABRT

And now... the patch. :) Cheers, -- Steve Langasek postmodern programmer On Tue, Apr 19, 2005 at 10:33:44PM -0700, Steve Langasek wrote: > And valgrind reveals all in the end. Attached is a patch which fixes up a > rounding error in the use of malloc_array(); this is probably a bit wasteful > c

Bug#302378: samba: smbd exits with SIGABRT

tags 302378 patch pending thanks And valgrind reveals all in the end. Attached is a patch which fixes up a rounding error in the use of malloc_array(); this is probably a bit wasteful compared to the original code, but at least it never allocates too little and gives us malloc corruption. I'll g

Processed: Re: Bug#302378: samba: smbd exits with SIGABRT

Processing commands for [EMAIL PROTECTED]: > tags 302378 patch pending Bug#302378: samba: smbd exits with SIGABRT Tags were: woody Bug#305043: samba stumbles over logrotate Tags added: patch, pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug trackin

Bug#305395: marked as done (mozilla-browser: Typo in /usr/bin/mozilla-suite)

Your message dated Wed, 20 Apr 2005 14:27:26 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#305395: mozilla-browser: Typo in /usr/bin/mozilla-suite 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 no

Processed: closing 297554, tagging 297554

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > close 297554 Bug#297554: libwvstreams4.0-extras: failure in initializing USB modem 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#297694: SmartLink WinMo

Bug#300532: marked as done (hunit: FTBFS: dh_haskell crash)

Your message dated Tue, 19 Apr 2005 23:45:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Corrected version in testing 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 respo

Processed: Re: Processed: Re: Bug#305412: p2c segfaults on specific input

Processing commands for [EMAIL PROTECTED]: > tags 305412 - security Bug#305412: p2c segfaults on specific input Tags were: security Tags removed: security > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#299702: Hugs98-2005 shouldn't go into sarge yet

Thanks for the patient explanation. I know it's too late, but ... On Tue, Apr 19, 2005 at 11:41:02PM +0100, Ian Lynagh wrote: > Given you suggest workarounds I'm going to assume this really means "why > isn't the new hugs in sarge?" and answer accordingly, but FWIW I don't > remember anything not

Bug#305438: php4-spplus: No longer depends on ANY phpapi...

Package: php4-spplus Version: 1.0-6 Severity: serious In the upload of version 1.0-6 of php4-spplus, I see this in the changelog: * debian/rules: removed stupid debian/substvars modification. And, indeed, the packages no longer depend on the phpapi they were compiled with, meaning two things:

Bug#305383: marked as done (grub: kopt arguments not properly parsed)

Your message dated Wed, 20 Apr 2005 09:47:02 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#305383: grub: kopt arguments not properly parsed 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 c

Bug#305435: bazaar: ftbfs [sparc] test-framework: line 28: 13580 Bus error

Package: bazaar Version: 1.3.2-1 Severity: serious Tags: sid Justification: fails to build from source bazaar fails to build from source on sparc, duplicated on sparc pbuilder. === TESTING: id-tagging-defaults === Test 1: id-tagging-defaults Test 1: PASS /tmp/buildd/bazaar-1.3.2/src/baz/t

Bug#305068: marked as done (Integer and heap overflow in gocr)

Your message dated Tue, 19 Apr 2005 19:02:40 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#305068: fixed in gocr 0.39-5 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 r

Bug#299702: Hugs98-2005 shouldn't go into sarge yet

On Tue, Apr 19, 2005 at 11:12:55AM +0100, Ross Paterson wrote: > Ian Lynagh <[EMAIL PROTECTED]> writes: > > We're not sure the new hugs should go into sarge without matching new > > ghc/nhc98 due to library changes. We also need to check these changes > > don't cause any breakage elsewhere. > > Wh

Bug#302711: plib: FTBFS: linker error

Hi, On Mon, 2005-04-18 at 17:34 +0300, Lars Wirzenius wrote: > > building the package plib in a clean sid build environment > > (with pbuilder) on i386 results in: > > I tried to reproduce this on my machine, with a clean sid build environment > for pbuilder, but failed. > > Roland, can you stil

Processed: tagging 305403, severity of 305403 is serious

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > tags 305403 sid Bug#305403: lilypond: pseudo-bug There were no tags set. Tags added: sid > severity 305403 serious Bug#305403: lilypond: pseudo-bug Severity set to `serious'. > End

Processed: tagging 305395

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > tags 305395 sid Bug#305395: mozilla-browser: Typo in /usr/bin/mozilla-suite There were no tags set. Tags added: sid > End of message, stopping processing here. Please contact me if

Bug#304779: readjust package + severity

reassign #304779 boot-floppies severity 304779 normal stop the boot-floppy kernel is not maintained by the debian kernel team. nobody would expect 2.4.18 to work on modern hardware. you'd better use the new d-i at: http://www.debian.org/devel/debian-installer/ and if you still need a woody base

Bug#305412: p2c segfaults on specific input

Package: p2c Severity: grave Tags: security Justification: user security hole I'm not really sure if this can be exploited, but I'm getting segfaults while trying to convert specific program... It is small enough to inline: { Copyright 2005 Zdenek Hrdina, distribute under GPLv2 } progra

Bug#305411: cal3d: FTBFS: cp: cannot stat `debian/tmp//usr/share/doc/libcal3d-doc/html/functions_rela.html': No such file or directory

Package: cal3d Version: 0.9.1+cvs20041122-1 Severity: serious Hi, Your package is failing to build with the following error: dh_installman -i dh_install -i --sourcedir=debian/tmp cp: cannot stat `debian/tmp//usr/share/doc/libcal3d-doc/html/functions_rela.html': No such file or directory dh_insta

Bug#305414: libgnomemm-2.6-dev: libgnomemm-2.6.la still references libhowl.la

Package: libgnomemm-2.6-dev Version: 2.8.0-1 Severity: serious Hi, The libgnomemm-2.6.la file still mentions the libhowl.la file. This causes other programs build depending on libgnomemm-2.6-dev to fail to build because they can't find that file. libhowl was removed from unstable, so you should

Bug#305413: libfreetype6: Many packages which use freetype now segfault

Package: libfreetype6 Version: 2.1.7-2.3 Severity: grave Justification: renders package unusable A number of packages which were previously working now segfault. The ones I've found so far include Mozilla and Firefox downloaded from mozilla.org, the Firefox installer from the same source, gaim, xc

Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 0000007c

severity 305123 normal stop On Mon, 18 Apr 2005, TAKAIZUMI Koichi wrote: > package: kernel-source-2.4.19 2.4.19-4.woody2 > system: IBM x335, memory 4G, Xeon x 2(4)(HT on) 2.4.19 kernels are not supported by the debian-kernel team. please upgrade to something more recent like 2.4.27 or 2.6.8 fo

Processed: Re: Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 0000007c

Processing commands for [EMAIL PROTECTED]: > severity 305123 normal Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 007c Severity set to `normal'. > stop Stopping processing here. Please contact me if you need assistance. Debian

Processed: readjust package + severity

Processing commands for [EMAIL PROTECTED]: > reassign #304779 boot-floppies Bug#304779: impossible to install debian 3.0 r4 with bf24 kernel Bug#304780: impossible to install debian 3.0 r4 with bf24 kernel Bug#304782: impossible to install debian 3.0 r4 with bf24 kernel Bug#304783: impossible to i

Bug#292478: More on this bug

Daniel Burrows writes... > I've run into what looks like the same thing on a new Dell Latitude x300. An I'm not convinced that the two Dell related bug reports in this bug are related to the original problem that I reported, other than the fact that they are all probably bugs due to the quali

Bug#302711: plib: successfully reproduced on powerpc

Package: plib Followup-For: Bug #302711 I've reproduced this compilation error on powerpc both on pbuilder environment (sarge) and my current system (sid). Full pbuilder logs are available here: http://stone-head.org/debian/pkg/build/plib_1.8.4-pbuilder.build regards, Rudy -- System Information:

Bug#305403: lilypond: pseudo-bug

Package: lilypond Severity: critical This is a pseudo-bug to prevent the new lilypond from entering sarge. In my opinion there is a likelihood of interoperation bugs which will take a while to iron out, and I am not confident that we should ship the new version in sarge. Thomas -- To UNSUBSCR

Bug#305395: mozilla-browser: Typo in /usr/bin/mozilla-suite

Package: mozilla-browser Version: 2:1.7.7-1 Severity: grave Justification: renders package unusable Typo in /usr/bin/mozilla-suite. If started from console, the bash shows following lines: $ mozilla /usr/bin/mozilla: line 75: syntax error near unexpected token `elif' /usr/bin/mozilla: line 75: `e

Bug#305374: marked as done (gnucash: does not start, can't find "slib/require.scm")

Your message dated Tue, 19 Apr 2005 13:13:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line gnucash: does not start, can't find "slib/require.scm" 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

Bug#292478: More on this bug

I've run into what looks like the same thing on a new Dell Latitude x300. An interesting twist is that this bug only manifests itself if I boot the -686 variant of the kernel; the default -386 variant boots without any problems. If I don't plug the drive in, everything works fine at first, but

Bug#305374: gnucash: does not start, can't find "slib/require.scm"

Thomas Bushnell BSG wrote: Gnucash does not start and gives the following error: ERROR: Could not find slib/require.scm in ("/usr/share/guile" "/usr/share/gnucash/guile-modules" "/usr/share/gnucash/scm" "" "/usr/share/guile/site" "/usr/share/guile/1.6" "/usr/share/guile" ".") Can you please show

Bug#305383: grub: kopt arguments not properly parsed

Package: grub Version: 0.95+cvs20040624-16 Severity: critical Justification: breaks the whole system After upgrading grub, update-grub generated an unusable menu.lst file. My kopt= argument was not parsed, so the root parameter was not passed to any of the automagic kernels. My system boots off t

Bug#254122: eroaster: transport layer indicator patch

Package: eroaster Version: 2.2.0-0.8-2 Severity: normal Followup-For: Bug #254122 tags 254122 +patch I hope this would satisfy both sides. This patch adds 2 preference options: transport layer indicators (TLI) for reader and recorder. Instead of using of USE_ATAPI variable in the code there is

Processed: tagging

Processing commands for [EMAIL PROTECTED]: > tags 305374 + unreproducible, moreinfo Bug#305374: gnucash: does not start, can't find "slib/require.scm" Tags were: moreinfo Tags added: unreproducible, moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug

Bug#305374: gnucash: does not start, can't find "slib/require.scm"

> Gnucash does not start and gives the following error: > ERROR: Could not find slib/require.scm in ("/usr/share/guile" > "/usr/share/gnucash/guile-modules" "/usr/share/gnucash/scm" "" > "/usr/share/guile/site" "/usr/share/guile/1.6" "/usr/share/guile" ".") Can you please show me the output of

Processed: tagging

Processing commands for [EMAIL PROTECTED]: > tags 305374 + unreproducable,moreinfo Unknown tag/s: unreproducable. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experiment

Processed: [Fwd: Processed: tagging tea bugs]

Processing commands for [EMAIL PROTECTED]: > tag 303352 pending fixed-upstream Bug#303352: conflicting file: /usr/bin/tea also in package dak Tags were: sid Tags added: pending, fixed-upstream > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#305374: gnucash: does not start, can't find "slib/require.scm"

Package: gnucash Version: 1.8.10-10 Severity: grave Justification: renders package unusable Gnucash does not start and gives the following error: ERROR: Could not find slib/require.scm in ("/usr/share/guile" "/usr/share/gnucash/guile-modules" "/usr/share/gnucash/scm" "" "/usr/share/guile/site" "/

Bug#305246: marked as done (mozilla-browser: mozilla doesn't start: syntax error)

Your message dated Tue, 19 Apr 2005 13:47:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#305246: fixed in mozilla 2:1.7.7-2 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

Bug#304559: marked as done (postfix: upgrade doesn't work cleanly)

Your message dated Tue, 19 Apr 2005 12:17:31 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#304559: fixed in postfix 2.2.2-2 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 yo

Bug#279870: Any progress regarding Woody?

Hello Gotom, any progress regarding woody and CAN-2004-0769, CAN-2004-0771, CAN-2004-0694, CAN-2004-0745? Greetings Helge -- Dr. Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferred 64bit GNU powered http://www

Bug#302378: another smb.conf

And here is my smb.conf, I hope it helps. An interesting observation is that the smbd crash occurs every Sunday around 6:30 AM, some minutes after my /etc/cron.daily has run (which is scheduled at 6:25 AM). Greetings, Joris # # Sample configuration file for the Samba suite for Debian GNU/Linux. #

Bug#305339: cupsys: 1.1.23-9 unsintallable

severity 305339 important tags 305339 unreproducible thanks At Tue, 19 Apr 2005 14:06:05 +0200, Artur R. Czechowski wrote: > Setting up cupsys (1.1.23-9) ... > cannot create dhelp file '/usr/share/doc/cupsys/online-docs/.dhelp': No such > file or directory > dpkg: error processing cupsys (--confi

Processed: Re: Bug#305339: cupsys: 1.1.23-9 unsintallable

Processing commands for [EMAIL PROTECTED]: > severity 305339 important Bug#305339: cupsys: 1.1.23-9 unsintallable Severity set to `important'. > tags 305339 unreproducible Bug#305339: cupsys: 1.1.23-9 unsintallable Tags were: sid Tags added: unreproducible > thanks Stopping processing here. Ple

Processed: tagging 305339

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > tags 305339 sid Bug#305339: cupsys: 1.1.23-9 unsintallable There were no tags set. Tags added: sid > End of message, stopping processing here. Please contact me if you need assistan

Bug#302378: possible workaround

And here is another. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |

Bug#301709: marked as done (qgis: please depend upon xerces26 instead of xerces21)

Your message dated Tue, 19 Apr 2005 08:32:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#301709: fixed in qgis 0.6.0-2 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#305343: Exploitable buffer overflow in RTSP streaming code

Package: libxine1 Version: 1.0-1 Severity: grave Tags: security Two streaming related security issues have been reported in MPlayer. At least one of them is present in xine-lib as well. The MPlayer reports can be found at http://www.mplayerhq.hu/homepage/design7/news.html. The vulnerable MMST code

Bug#304665: xmms-wmdiscotux: FTBFS: Missing Build-Depends

Daniel Schepler: > Adding libxpm-dev to the Build-Depends allows the package to build. I've checked that Daniel is correct and that the package built with the added build-dependency still works (on i386). Unless there's an objection, I'll do an NMU with the attached patch in a few days (end of thi

Bug#305339: cupsys: 1.1.23-9 unsintallable

Package: cupsys Version: 1.1.23-9 Severity: grave Justification: renders package unusable Setting up cupsys (1.1.23-9) ... cannot create dhelp file '/usr/share/doc/cupsys/online-docs/.dhelp': No such file or directory dpkg: error processing cupsys (--configure): subprocess post-installation scri

Processed: Fixed in NMU of tspc 2.1.1-4.1

Processing commands for [EMAIL PROTECTED]: > tag 304431 + fixed Bug#304431: tspc_2.1.1-4(mips/unstable): FTBFS with -rsudo There were no tags set. Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator

Bug#305120: marked as done (ogre-tools: package depends upon too-new libc)

Your message dated Tue, 19 Apr 2005 13:00:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line closing bug 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 responsibility to reop

Bug#304431: tspc_2.1.1-4(mips/unstable): FTBFS with -rsudo

> By remove the "/*" from the rm command line, the build works (on i386, > didn't try under mips; I did verify that the build problem was > reproducible on i386 first, though). Since there has not been any reaction to this bug from the maintainer in the past week I'll do a non-maintainer upload.

Bug#299702: Hugs98-2005 shouldn't go into sarge yet

Ian Lynagh <[EMAIL PROTECTED]> writes: > We're not sure the new hugs should go into sarge without matching new > ghc/nhc98 due to library changes. We also need to check these changes > don't cause any breakage elsewhere. What incompatibilities with GHC 6.2 and nhc98 1.16 have you discovered that w

Processed: severity of 304784 is critical

Processing commands for [EMAIL PROTECTED]: > severity 304784 critical Bug#304784: impossible to install debian 3.0 r4 with bf24 kernel Bug#304779: impossible to install debian 3.0 r4 with bf24 kernel Bug#304780: impossible to install debian 3.0 r4 with bf24 kernel Bug#304782: impossible to install

Bug#304428: marked as done (stk_4.2.0-3(mipsel/unstable): fails to build with -rsudo)

Your message dated Tue, 19 Apr 2005 05:32:41 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#304428: fixed in stk 4.2.0-4 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 r

Bug#305313: marked as done (cupsys: 1.1.23-8 is uninstallable)

Your message dated Tue, 19 Apr 2005 18:30:34 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#305313: cupsys: 1.1.23-8 is uninstallable 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#294404: The commited fix is WRONG

Hi Michael, On Thu, Apr 14, 2005 at 10:16:36AM +0400, Michael Tokarev wrote: > The last mdadm change -- 1.9.0-2.1 -- did NOT fix the bug, > but made the situation worse. > rcS.d/S04mdadm-raid is now the FIRST thing the system is > doing when booting. At that stage, /proc is not mounted > (it is

Bug#302378: possible workaround

Hi, a possible workaround is to have logrotate do a samba restart instead of a reload. This will disconnect all users, but it that is not an issue at the time logrorate is running, this might be an improvement over crashing... appended is an smb.conf of an affected server regards, Olivie

Bug#300520: Any downside on making the build-dependency versioned?

On Tue, Apr 19, 2005 at 10:10:10AM +0200, Helge Kreutzmann wrote: > Hello, > is there any reason *not* to make the build dependency versioned? I > think this would be the proper version. Especially if people rebuild > the package locally. Also I think it is not good practice to "If it > gets built

Bug#302629: slapd: Unstable upgrade (2.1 -> 2.2) failures

On Mon, Apr 18, 2005 at 11:41:48AM +0200, Torsten Landschoff wrote: > > this particular LDIF incompatibility be dealt with in fix_ldif? > In theory fix_ldif could be improved to handle all incompatibilities. If > we know them... > > > > The issue seems to be that slapcat created the root

Bug#300520: Any downside on making the build-dependency versioned?

Hello, is there any reason *not* to make the build dependency versioned? I think this would be the proper version. Especially if people rebuild the package locally. Also I think it is not good practice to "If it gets built on all architectures then we don't have to worry about it." Slower or overl

Processed: tagging 305313

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > tags 305313 sid Bug#305313: cupsys: 1.1.23-8 is uninstallable There were no tags set. Tags added: sid > End of message, stopping processing here. Please contact me if you need assis

Bug#303343: Removeal of package libdata-dumper-perl

Package: ftp.debian.org Severity: normal The libdata-dumper-perl package is obsolate becase the functionality is provided allready by the perl-base package. Please remove this package and all releated files from the archive. -- System Information: Debian Release: 3.1 APT prefers testing APT

Bug#305311: postfix: dpkg-buildpackage only works once

fixed in 2.2.2-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305311: marked as done (postfix: dpkg-buildpackage only works once)

Your message dated Tue, 19 Apr 2005 01:51:49 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#305311: postfix: dpkg-buildpackage only works once 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

Bug#305313: cupsys: 1.1.23-8 is uninstallable

Package: cupsys Version: 1.1.23-8 Severity: grave Justification: renders package unusable iam-ma-010:~# apt-get install cupsys Reading Package Lists... Done Building Dependency Tree... Done Suggested packages: cupsys-driver-gimpprint foomatic-bin xpdf-korean xpdf-japanese xpdf-chinese-traditio

Processed: reassign 262925 to cman,cman-kernel,ccs,dlm-kernel,fence,gfs,gfs-kernel,gnbd,gnbd-kernel,iddev,magma,magma-plugins

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > reassign 262925 > cman,cman-kernel,ccs,dlm-kernel,fence,gfs,gfs-kernel,gnbd,gnbd-kernel,iddev,magma,magma-plugins Bug#262925: gfs framework should not enter testing Bug reassigned fr

Bug#305311: postfix: dpkg-buildpackage only works once

Package: postfix Severity: serious Justification: no longer builds from source The source cant be build more than once using dpkg-buildpackage. It seems that the dh_clean section dont works correctly. This is the Error Message from make make[2]: Entering directory `/home/debian-build/buildpackage