Bug#895540: marked as done (nx-libs: FTBFS with parallel > 1 due to errors cleaning)

Your message dated Fri, 20 Apr 2018 09:35:04 + with message-id and subject line Bug#895540: fixed in nx-libs 2:3.5.99.16-2 has caused the Debian Bug report #895540, regarding nx-libs: FTBFS with parallel > 1 due to errors cleaning to be marked as done.

Bug#896153: mpich needs Breaks+Replaces: libmpich-dev (<< 3.3~b2-3~)

Package: mpich Version: 3.3~b2-3 Severity: serious Preparing to unpack .../mpich_3.3~b2-3_amd64.deb ... Unpacking mpich (3.3~b2-3) over (3.3~b2-2) ... dpkg: error processing archive /var/cache/apt/archives/mpich_3.3~b2-3_amd64.deb (--unpack): trying to overwrite

Bug#895540: Bug #895540 in nx-libs marked as pending

Control: tag -1 pending Hello, Bug #895540 in nx-libs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #895540 in nx-libs marked as pending

Processing control commands: > tag -1 pending Bug #895540 [src:nx-libs] nx-libs: FTBFS with parallel > 1 due to errors cleaning Added tag(s) pending. -- 895540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896141: msxpertsuite: binary-all FTBFS

On Fri, Apr 20, 2018 at 10:21:36AM +0200, Filippo Rusconi wrote: >... > Can you provide more insight into this copy error? As I tell you, that error > does not happen on my unstable chroot, running dpkg-buildpackage -A exactly > the > same. This is what I got 2 minutes ago (see the parallel with

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

The package also compiles fine in my local sbuild environment and on debomatic-amd64: http://debomatic-amd64.debian.net/distribution#unstable/flif/0.3-1/buildlog Paride

Bug#896141: msxpertsuite: binary-all FTBFS

Greetings Adrian, thanks for your build work. On Fri, Apr 20, 2018 at 10:05:25AM +0300, Adrian Bunk wrote: Source: msxpertsuite Version: 5.0.0-1 Severity: serious $ dpkg-buildpackage -A ... make[1]: Entering directory '/tmp/msxpertsuite-5.0.0/debian/build/massxpert/user-manual' make[2]:

Processed: Re: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Processing control commands: > forwarded 896109 https://github.com/FLIF-hub/FLIF/issues/498 Bug #896109 [src:flif] flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam Warning: Unknown package 'src:flif' Set Bug forwarded-to-address to

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Control: forwarded 896109 https://github.com/FLIF-hub/FLIF/issues/498 On Thu, 19 Apr 2018 17:34:44 +0300 Adrian Bunk wrote: > > flif FTBFS (also reproduced on amd64): > > https://buildd.debian.org/status/package.php?p=flif=sid Dear Adrian, Thanks for your report. I noticed

Bug#896144: tpm2-tss FTBFS on big endian: test failures

Source: tpm2-tss Version: 1.4.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=tpm2-tss=sid ... FAIL: test/unit/CopyCommandHeader = [==] Running 3 test(s). [ RUN ] CopyCommandHeader_nextData_unit [ OK ]

Bug#895476: marked as done (fwbuilder FTBFS: Cannot find file: .)

Your message dated Fri, 20 Apr 2018 07:34:28 + with message-id and subject line Bug#895476: fixed in fwbuilder 5.3.7-2 has caused the Debian Bug report #895476, regarding fwbuilder FTBFS: Cannot find file: . to be marked as done. This means that you claim

Bug#893039: libccnet0: contains a python module

I uploaded Version 6.1.7-1 yesterday. It is currently in the NEW queue. Christoph Am 17.04.2018 um 12:04 schrieb Moritz Schlarb: > Hi Helmut, > > I addressed this issue in 6.1.5-2, but since this leads to a new binary > upload, I can't upload it myself since I'm just a DM. > My mentor/sponsor

Bug#896141: msxpertsuite: binary-all FTBFS

Source: msxpertsuite Version: 5.0.0-1 Severity: serious $ dpkg-buildpackage -A ... make[1]: Entering directory '/tmp/msxpertsuite-5.0.0/debian/build/massxpert/user-manual' make[2]: Entering directory '/tmp/msxpertsuite-5.0.0/debian/build' make[3]: Entering directory

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

On Fri, Apr 20, 2018 at 02:25:15AM -0400, Jeremy Bicha wrote: > On Fri, Apr 20, 2018 at 2:09 AM, Adrian Bunk wrote: > > Control: reassign -1 libpango1.0-dev 1.42.1-1 > > Control: retitle -1 "pkg-config --libs pango" incorrectly contains -lfribidi > > > > On Thu, Apr 19, 2018 at

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

On Fri, Apr 20, 2018 at 2:09 AM, Adrian Bunk wrote: > Control: reassign -1 libpango1.0-dev 1.42.1-1 > Control: retitle -1 "pkg-config --libs pango" incorrectly contains -lfribidi > > On Thu, Apr 19, 2018 at 11:56:18PM -0400, Jeremy Bicha wrote: >> Control: reassign -1 d-shlibs

Processed: Close the correct bug

Processing commands for cont...@bugs.debian.org: > reopen 896016 Bug #896016 {Done: Alastair McKinstry } [src:strace] strace: please make the build reproducible 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and

Processed: Re: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

Processing control commands: > reassign -1 libpango1.0-dev 1.42.1-1 Bug #895235 [d-shlibs] sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it Bug reassigned from package 'd-shlibs' to 'libpango1.0-dev'. No longer marked as found in

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

Control: reassign -1 libpango1.0-dev 1.42.1-1 Control: retitle -1 "pkg-config --libs pango" incorrectly contains -lfribidi On Thu, Apr 19, 2018 at 11:56:18PM -0400, Jeremy Bicha wrote: > Control: reassign -1 d-shlibs 0.82 > > The build itself completes fine. If pango were broken, I'd expect a >

Bug#896132: thermald uninitialised member causes loss of temperature control

Ben, I tried restarting thermald (1.7.0-5) at least 10 times, and the system always see the same broken sensor, the same as in 1.7.0-4 and the same as in 1.7.0-6. Perhaps by luck (or perhaps because some library or compiler version difference) thermald 1.7.0-5 worked fine on my ubuntu 18.04

<    1   2   3   4