On Tue, 06 Nov 2018 19:47:34 -0500 Scott Kitterman
wrote:
> Would someone who is still having this problem please try the attached
> configure-instance.sh in place of the installed version in /usr/lib/postfix?
>
> This one avoids postmulti in every case and might actually work, but I have
> a
Control: severity -1 important
On Wed, 5 Dec 2018 13:16:29 +0100
=?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?=
wrote:
> There's any new data about this bug?
Since I can't reproduce it in multiple systems, I'm reducing the severity. Did
you try 11.4.9?
--
Sent from my Android device
Processing control commands:
> severity -1 important
Bug #915136 [gitlab] Gitlab: Error 503 loading some projects
Severity set to 'important' from 'grave'
--
915136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: nullmailer
Version: 1:2.2-1
Severity: serious
Tags: upstream
Justification: ftbfs
nullmailer 2.2 should not transition to testing until we figure out what is
going on with the test
Testing auth permanent failure with smtp
which seems to fail or hang on various
Processing commands for cont...@bugs.debian.org:
> close 915287 1.0.7-4.2
Bug #915287 [src:ruby-eventmachine] ruby-eventmachine: B-D against libssl1.0-dev
Marked as fixed in versions ruby-eventmachine/1.0.7-4.2.
Bug #915287 [src:ruby-eventmachine] ruby-eventmachine: B-D against libssl1.0-dev
close 915287 1.0.7-4.2
thanks
On Thu, 6 Dec 2018 14:05:22 +0100 Sebastian Andrzej Siewior
wrote:
> On 2018-12-06 12:42:50 [+0100], gregor herrmann wrote:
> > On Wed, 05 Dec 2018 13:57:05 +, Debian Bug Tracking System wrote:
> >
> > > ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium
>
Your message dated Mon, 10 Dec 2018 00:49:35 +
with message-id
and subject line Bug#909978: fixed in erlang-cuttlefish 2.0.11+dfsg-4
has caused the Debian Bug report #909978,
regarding erlang-cuttlefish FTBFS with Erlang 21.1
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> notfixed 847642 uglifyjs/2.8.29-2
Bug #847642 [node-uglify] node-uglify: neither manpage nor --help output useful
Bug #847643 [node-uglify] node-uglify: neither manpage nor --help output useful
Ignoring request to alter fixed versions of bug
Control: reopen -1
> The command ‘uglifyjs’ has a manual page ‘uglifyjs(1)’ that does not
> helpfully describe the command:
>
> NAME
>uglify-js - manual page for uglify-js 2.7.5
This is still the case; the manual page (now for version 2.8.29) does
not contain a useful ‘NAME’
Processing control commands:
> reopen -1
Bug #847642 {Done: Adrian Bunk } [node-uglify] node-uglify:
neither manpage nor --help output useful
Bug #847643 {Done: Adrian Bunk } [node-uglify] node-uglify:
neither manpage nor --help output useful
'reopen' may be inappropriate when a bug has been
Control: tag -1 pending
Hello,
Bug #909181 in mariadb-connector-c 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:
Processing control commands:
> tag -1 pending
Bug #909181 [libmariadb-dev] libmariadb-dev: does not depend on zlib1g-dev,
while mariadb_config reports `-lz`
Added tag(s) pending.
--
909181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909181
Debian Bug Tracking System
Contact
Your message dated Sun, 09 Dec 2018 22:51:48 +
with message-id
and subject line Bug#916070: fixed in rootskel 1.126
has caused the Debian Bug report #916070,
regarding rootskel FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 09 Dec 2018 22:50:34 +
with message-id
and subject line Bug#915256: fixed in luksmeta 9-2
has caused the Debian Bug report #915256,
regarding luksmeta FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> tag -1 pending
Bug #916070 [src:rootskel] rootskel FTBFS with glibc 2.28
Added tag(s) pending.
--
916070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #916070 in rootskel 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:
Your message dated Sun, 09 Dec 2018 22:35:50 +
with message-id
and subject line Bug#916001: fixed in partconf 1.52
has caused the Debian Bug report #916001,
regarding partconf FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 09 Dec 2018 22:34:30 +
with message-id
and subject line Bug#915235: fixed in cypari2 1.2.1-2
has caused the Debian Bug report #915235,
regarding cypari2 FTBFS with Python 3.7 as default
to be marked as done.
This means that you claim that the problem has been dealt
Control: tag -1 pending
Hello,
Bug #916001 in partconf 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:
Processing control commands:
> tag -1 pending
Bug #916001 [src:partconf] partconf FTBFS with glibc 2.28
Added tag(s) pending.
--
916001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Dear Maintainer,
I just tried to reproduce and collect some more information,
used a minimal buster amd64 qemu VM.
This issue seems to be more located in libt4k-common0.
It uses "rsvg_handle_get_desc(file_handle)" to retrieve
a char pointer to the description and tries to convert that
into an
Your message dated Sun, 09 Dec 2018 21:50:07 +
with message-id
and subject line Bug#916004: fixed in makefs 20100306-7
has caused the Debian Bug report #916004,
regarding makefs FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 09 Dec 2018 21:50:53 +
with message-id
and subject line Bug#906094: fixed in psi4 1:1.1-6
has caused the Debian Bug report #906094,
regarding psi4: missing dependency on python3
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 09 Dec 2018 21:50:53 +
with message-id
and subject line Bug#897492: fixed in psi4 1:1.1-6
has caused the Debian Bug report #897492,
regarding psi4: FTBFS: pybind11.h:1010:105: error: cannot convert 'void
(psi::SuperFunctional::*)(int) const' to 'void
Your message dated Sun, 09 Dec 2018 21:49:53 +
with message-id
and subject line Bug#911437: fixed in gitlab-ci-multi-runner 11.2.0+dfsg-2
has caused the Debian Bug report #911437,
regarding gitlab-ci-multi-runner: FTBFS with
golang-github-prometheus-client-golang/0.9.0-1
to be marked as
Hi Adrian,
>Tags: ftbfs
>
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pax.html
>
>...
>cpio.c: In function 'vcpio_wr':
>pax.h:261:18: warning: implicit declaration of function 'major'
>[-Wimplicit-function-declaration]
> #define MAJOR(x) major(x)
> ^
Control: tag -1 pending
Hello,
Bug #916004 in makefs 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:
Processing control commands:
> tag -1 pending
Bug #916004 [src:makefs] makefs FTBFS with glibc 2.28
Added tag(s) pending.
--
916004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sun, 09 Dec 2018 21:27:06 +
with message-id
and subject line Bug#915639: fixed in shibboleth-resolver 3.0.0-2
has caused the Debian Bug report #915639,
regarding shibboleth-resolver: FTBFS: missing pkg-config/log4shib/log4cpp
to be marked as done.
This means that you claim
Your message dated Sun, 09 Dec 2018 21:27:32 +
with message-id
and subject line Bug#899837: fixed in xfce4-datetime-plugin 0.7.0-2
has caused the Debian Bug report #899837,
regarding xfce4-datetime-plugin: Invalid maintainer address
pkg-xfce-de...@lists.alioth.debian.org
to be marked as
Hello,Here is a patch trying to address that, as suggested by Simon McVittie in https://github.com/stevegrubb/libcap-ng/issues/5and Carlos O'Donell at https://sourceware.org/bugzilla/show_bug.cgi?id=13502Using the package built with this patch also fixes this
Your message dated Sun, 09 Dec 2018 21:22:18 +
with message-id
and subject line Bug#916037: fixed in liquidwar 5.6.4-6
has caused the Debian Bug report #916037,
regarding liquidwar FTBFS with allegro4.4 2:4.4.2-13
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 09 Dec 2018 21:20:53 +
with message-id
and subject line Bug#914145: fixed in liborigin2 2:20110117-3
has caused the Debian Bug report #914145,
regarding liborigin2 FTBFS with boost 1.67
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 09 Dec 2018 21:18:45 +
with message-id
and subject line Bug#915619: fixed in golang-gopkg-lxc-go-lxc.v2
0.0~git20181101.0aadfc3-1
has caused the Debian Bug report #915619,
regarding golang-gopkg-lxc-go-lxc.v2: not compatible with LXC v3
to be marked as done.
This
Your message dated Sun, 09 Dec 2018 21:19:32 +
with message-id
and subject line Bug#916035: fixed in kraptor 0.0.20040403+ds-2
has caused the Debian Bug report #916035,
regarding kraptor FTBFS with allegro4.4 2:4.4.2-13
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 09 Dec 2018 21:16:44 +
with message-id
and subject line Bug#916033: fixed in alex4 1.1-8
has caused the Debian Bug report #916033,
regarding alex4 FTBFS with allegro4.4 2:4.4.2-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Tuesday, 20 November 2018 5:26:02 AM AEDT Andreas Henriksson wrote:
> It seems you've forgot to push upstream/pristine-tar branches
> and tags when you did the last update/upload of the package.
> Could you please push them?
Done. FYI I did not forget to push - I was working in haste and just
Processing commands for cont...@bugs.debian.org:
> tags 914556 + pending
Bug #914556 [src:linux] linux: FTBFS on arm64: changed ABI
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914556:
Source: hyperic-sigar
Version: 1.6.4+dfsg-2.1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hyperic-sigar.html
...
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1148:22: error:
called object 'major' is not a function or
Control: tag -1 pending
Hello,
Bug #911437 in gitlab-ci-multi-runner 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:
Processing control commands:
> tag -1 pending
Bug #911437 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS with
golang-github-prometheus-client-golang/0.9.0-1
Added tag(s) pending.
--
911437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911437
Debian Bug Tracking System
Contact
On Sun, 9 Dec 2018 20:35:02 +0100
Markus Koschany wrote:
>Hello Andreas,
>
>
>Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
>> tags 916037 + patch
>> thanks
>>
>> Patch attached to fix this build error (Which I am the cause of).
>
>Please feel free to upload your fix as needed. Since all
Hi.
I am not sure how I managed to produce the binary package for amd64. I
*thought* that I used sbuild in a clean sid chroot to do so, but it's
quite clear from trying to reproduce that that I failed. I'm somewhat
baffled because my work flow makes it hard for something not coming out
of
Package: virtualbox-dkms
Version: 5.2.22-dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + virtualbox-guest-additions-iso
Hi,
virtualbox-dkms fails to build a module for 4.18.0-3-686,
4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case
Processing control commands:
> affects -1 + virtualbox-guest-additions-iso
Bug #916077 [virtualbox-dkms] virtualbox-dkms: module FTBFS for 4.18.0-3-686,
4.18.0-3-686-pae
Added indication that 916077 affects virtualbox-guest-additions-iso
--
916077:
Package: pcc
Version: 1.2.0~DEVEL+20181202-1
Severity: serious
Control: block -1 by 915633
Without libpcc-dev, pcc cannot compile any but the most trivial C
programs (e.g. #including causes the preprocessor to complain
about a missing stddef.h) and cannot link any C program because ld fails
to
Processing control commands:
> block -1 by 915633
Bug #916074 [pcc] pcc: useless without libpcc-dev
916074 was not blocked by any bugs.
916074 was not blocking any bugs.
Added blocking bug(s) of 916074: 915633
--
916074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916074
Debian Bug
Control: tag -1 pending
Hello,
Bug #916062 in cowdancer 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:
Processing control commands:
> tag -1 pending
Bug #916062 [src:cowdancer] cowdancer FTBFS with glibc 2.28
Added tag(s) pending.
--
916062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hello Andreas,
Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
> tags 916037 + patch
> thanks
>
> Patch attached to fix this build error (Which I am the cause of).
Please feel free to upload your fix as needed. Since all packages are
team-maintained and you are a member of the team and know
Your message dated Sun, 09 Dec 2018 19:36:03 +
with message-id
and subject line Bug#916053: fixed in ocfs2-tools 1.8.5-7
has caused the Debian Bug report #916053,
regarding ocfs2-tools FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
Package: src:gnat-gps
Followup-For: Bug #913371
gnat-gps/18 now fails to build on armhf, while 18-3 was succeeding on
the same architecture.
After investigation, the only successful builds of gnat-gps/18 on 32
bits architectures so far (armhf i386 powerpc) were registered with a
32 bits chroot
Source: rootskel
Version: 1.125
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rootskel.html
...
gcc -Os -Wall get-real-console-linux.c -o get-real-console-linux
get-real-console-linux.c: In function 'main':
get-real-console-linux.c:30:23:
Your message dated Sun, 9 Dec 2018 20:08:02 +0100
with message-id <295a3971-6655-315d-b593-410c64d74...@debian.org>
and subject line Re: libsoundio1: Missing hard dependency on libjack-jackd2-0
has caused the Debian Bug report #835590,
regarding libsoundio1: Missing hard dependency on
Source: fdutils
Version: 5.5-20060227-7
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fdutils.html
...
driveprm.c: In function 'getdrivenum':
driveprm.c:143:6: warning: implicit declaration of function 'major'
Source: ext4magic
Version: 0.3.2-10
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ext4magic.html
...
recover.c: In function 'recover_file':
recover.c:478:35: warning: implicit declaration of function 'makedev'
[-Wimplicit-function-declaration]
Source: fuse-umfuse-ext2
Version: 0.4-1.1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fuse-umfuse-ext2.html
...
op_create.c: In function 'old_valid_dev':
op_create.c:45:9: warning: implicit declaration of function 'major'
Processing commands for cont...@bugs.debian.org:
> severity 915390 serious
Bug #915390 [clazy] clazy: Segmentation fault compiling any file
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915390:
Processing commands for cont...@bugs.debian.org:
> tags 916061 + buster sid
Bug #916061 [src:diod] diod FTBFS with glibc 2.28
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916061:
Source: cowdancer
Version: 0.87
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cowdancer.html
...
qemuarch.c: In function 'qemu_create_arch_serialdevice':
qemuarch.c:60:16: warning: implicit declaration of function 'makedev'
Your message dated Sun, 09 Dec 2018 18:34:33 +
with message-id
and subject line Bug#913382: fixed in fbreader 0.12.10dfsg2-3
has caused the Debian Bug report #913382,
regarding fbreader FTBFS with curl 7.62.0
to be marked as done.
This means that you claim that the problem has been dealt
Source: diod
Version: 1.0.24-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diod.html
...
ops.c: In function 'diod_mknod':
ops.c:808:38: warning: implicit declaration of function 'makedev'
[-Wimplicit-function-declaration]
if (mknod
Package: tuxmath
Version: 2.0.3-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When trying to start Tuxmath, it looks like it starts and immediately (msec)
closes.
When run from terminal it shows:
$ tuxmath
Initializing Tux4Kids-Common 0.1.1
libpng warning: iCCP:
Processing commands for cont...@bugs.debian.org:
> retitle 914495 linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: linux image installed via
4.18.0-3 stops
Source: procmeter3
Version: 3.6-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/procmeter3.html
...
longrun.c:41:24: error: unknown type name 'loff_t'; did you mean 'off_t'?
static void read_cpuid(loff_t address, int *eax, int *ebx,
Source: ocfs2-tools
Version: 1.8.5-6
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocfs2-tools.html
...
In file included from o2cb_abi.c:52:
../include/ocfs2/ocfs2.h:222:2: error: unknown type name 'loff_t'
loff_t d_off; /* Offset of structure
Source: alsa-oss
Version: 1.1.6-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html
...
In file included from alsa-oss.c:736:
stdioemu.c:40:10: fatal error: libio.h: No such file or directory
#include
^
compilation
Source: cloop
Version: 3.14.1.2
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cloop.html
...
cc -Wall -O2 -g -O2 -ffile-prefix-map=/build/1st/cloop-3.14.1.2=.
-fstack-protector-strong -Wformat -Werror=format-security -flto
Source: nwchem
Version: 6.8+47+gitdf6c956-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nwchem.html
...
util_fadvise.c: In function 'util_fadvise':
util_fadvise.c:47:5: error: unknown type name 'loff_t'; did you mean 'off_t'?
loff_t
Package: libsqlite3-0
Version: 3.26.0-1
Severity: serious
Control: block -1 by 915938
Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)
(assuming #915938 will be fixed in version 0.11.0-4)
might be correct to prevent people using testing or stretch-backports
to end up using
Processing control commands:
> block -1 by 915938
Bug #916046 [libsqlite3-0] libsqlite3-0 might need Breaks: python-migrate (<<
0.11.0-4~), python3-migrate (<< 0.11.0-4~)
916046 was not blocked by any bugs.
916046 was not blocking any bugs.
Added blocking bug(s) of 916046: 915938
--
916046:
Processing commands for cont...@bugs.debian.org:
> severity 915938 serious
Bug #915938 [migrate] migrate: Enable compatability with sqlite >= 3.26
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915938:
Andreas Metzler writes:
> ncbi-blast+ FTBFS on current sid:
Thanks for the report! It looks like ncbi-blast+ needs another round of
formal patches for compatibility with current Boost. The following
upstream changes should collectively take care of it:
On Tue, 12 Jun 2018 06:22:09 +0100 Colin Watson
wrote:
> On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> > On 2018-06-11 Colin Watson wrote:
> > > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > > yes, resetting IFS to its default value in confmodule
Your message dated Sun, 09 Dec 2018 15:40:26 +
with message-id
and subject line Bug#891778: fixed in zatacka 0.1.8-5.2
has caused the Debian Bug report #891778,
regarding zatacka crashes on map selection
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Wed, 05 Dec 2018 12:21:05 -0700 Ted Percival wrote:
> So the solution might just be to add the versioned Build-Depends: g++ (>= 4:7)
> and rebuild to get the old symbols back into the library, rather than bumping
> the soname.
That reminds me of https://bugs.debian.org/911090 where
On
Processing commands for cont...@bugs.debian.org:
> tags 916035 + patch
Bug #916035 [src:kraptor] kraptor FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916035:
tags 916035 + patch
thanks
Attached patch to fix building with fixmul instead of fmul. (I am the
cause of the problem with my allegro4.4 upload)
thanks
-- Andreas Rönnquist
gus...@debian.org
--- a/src/explos.c
+++ b/src/explos.c
@@ -126,10 +126,10 @@
while (tmp) {
x2 =
Processing commands for cont...@bugs.debian.org:
> tags 916037 + patch
Bug #916037 [src:liquidwar] liquidwar FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916037:
Processing commands for cont...@bugs.debian.org:
> tags 916033 + patch
Bug #916033 [src:alex4] alex4 FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916033:
tags 916037 + patch
thanks
Patch attached to fix this build error (Which I am the cause of).
/Andreas
gus...@debian.org
--- a/src/distor.c
+++ b/src/distor.c
@@ -194,7 +194,7 @@
cycle_tmp /= 2;
speed--;
}
- cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
+ cycle_tmp = fixsqrt
Your message dated Sun, 09 Dec 2018 14:48:20 +
with message-id
and subject line Bug#899739: fixed in xfce4-messenger-plugin 0.1.0-7
has caused the Debian Bug report #899739,
regarding xfce4-messenger-plugin: Invalid maintainer address
pkg-xfce-de...@lists.alioth.debian.org
to be marked as
Your message dated Sun, 09 Dec 2018 14:46:52 +
with message-id
and subject line Bug#907159: fixed in mudlet 1:3.7.1-1.1
has caused the Debian Bug report #907159,
regarding mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class
QTabBar')
to be marked as done.
This means that you
Your message dated Sun, 09 Dec 2018 14:46:58 +
with message-id
and subject line Bug#916003: fixed in nfswatch 4.99.11-5
has caused the Debian Bug report #916003,
regarding nfswatch FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 09 Dec 2018 14:48:13 +
with message-id
and subject line Bug#899732: fixed in xfce4-cpugraph-plugin 1.0.5-2
has caused the Debian Bug report #899732,
regarding xfce4-cpugraph-plugin: Invalid maintainer address
pkg-xfce-de...@lists.alioth.debian.org
to be marked as
Your message dated Sun, 09 Dec 2018 14:46:06 +
with message-id
and subject line Bug#915577: fixed in haskell-mode 16.1-5
has caused the Debian Bug report #915577,
regarding elpa-haskell-mode: missing Breaks+Replaces: haskell-mode (<< 16.1-4)
to be marked as done.
This means that you claim
On 2018-12-09 Adrian Bunk wrote:
> Source: wmhdplop
> Version: 0.9.10-1
[...]
> devnames.c: In function 'device_id_from_name':
> devnames.c:207:13: warning: implicit declaration of function 'major'
> [-Wimplicit-function-declaration]
>*pmajor = major(stat_buf.st_rdev);
> ^
Processing commands for cont...@bugs.debian.org:
> # version information lost in reassign
> found 913346 1.0.27-3
Bug #913346 [sane-backends] libsane1: Cannot update libsane1
There is no source info for the package 'sane-backends' at version '1.0.27-3'
with architecture ''
Unable to make a
This patch fixes this problem for alex4. (I am the cause of the problem,
and I'll post patches to the other allegro4.4-related failures too).
-- Andreas Rönnquist
gus...@debian.org
--- a/src/shooter.c
+++ b/src/shooter.c
@@ -500,12 +500,12 @@
break;
case SM_SIN_WAVE:
o->x += o->vx;
-
Control: tags -1 patch pending
Dear maintainer,
I've uploaded a new revision of mudlet versioned as 1:3.7.1-1.1.
To fix this issue I had to patch src/TCommandLine.cpp and add the
missing include for QTabBar. I also had to export CCACHE_DIR because
otherwise the build would fail on my system
Processing control commands:
> tags -1 patch pending
Bug #907159 [src:mudlet] mudlet: FTBFS in buster/sid (invalid use of incomplete
type 'class QTabBar')
Added tag(s) patch and pending.
--
907159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907159
Debian Bug Tracking System
Contact
Il 09/12/18 14:10, Adrian Bunk ha scritto:
Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bootchart2.html
...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47:
Source: liquidwar
Version: 5.6.4-5
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/liquidwar.html
...
distor.c: In function 'create_wave_line':
distor.c:197:15: warning: implicit declaration of function 'fsqrt'; did you
mean 'fixsqrt'?
Processing control commands:
> found -1 2.9.11~20110321-12
Bug #916034 [sl-modem-dkms] sl-modem-dkms: module FTBFS for 4.18.0-3-amd64,
4.9.0-8-amd64
Marked as found in versions sl-modem/2.9.11~20110321-12.
--
916034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916034
Debian Bug Tracking
Source: alex4
Version: 1.1-7
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alex4.html
...
shooter.c: In function 's_update_object':
shooter.c:503:26: warning: implicit declaration of function 'fmul'; did you
mean 'fixmul'?
Chris Lamb wrote:
> > However, the git does not seem to have been moved to salsa.
>
> I fixed a number of CVEs recently and I would love to push my changes
> to suitable branches. Can the PEAR maintainers please migrate this
> repo ASAP?
Gentle ping on this folks? :)
Best wishes,
--
Hi,
same issue here. Deterministic (always fails at boot with -3, and works with
-2).
below, kernel log of 4.18.0-2 and 4.18.0-3 (with something wrong in
i915_request_alloc)
kernel log of 4.18.0-2 (the WORKING one) follows:
[0.00] Linux version 4.18.0-2-amd64
Package: sl-modem-dkms
Version: 2.9.11~20110321-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.9.11~20110321-12
Hi,
sl-modem-dkms fails to build a module for 4.18.0-3-amd64 and 4.9.0-8-amd64
Selecting previously unselected package sl-modem-dkms.
Source: kraptor
Version: 0.0.20040403+ds-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kraptor.html
...
src/explos.c: In function 'dibujar_explosion':
src/explos.c:129:20: warning: implicit declaration of function 'fmul'; did you
mean
Package: moria
Version: 5.7.10+20181022-1
Severity: serious
Dear maintainer,
moria fails to build from source on mips64el. This prevents the
package migration to testing. According to the build log the error is
caused by
src/ui_io.cpp:521:31: error: cast from 'int*' to 'fd_set*' increases
1 - 100 of 158 matches
Mail list logo
