Hi,
I just add maintainer and uploader to the loop. Hopefully, they should
know something about the package/code/issue.
Le 04/01/2017 à 21:42, Salvatore Bonaccorso a écrit :
> On Sun, Mar 27, 2016 at 01:33:01PM +0200, Moritz Mühlenhoff wrote:
>> On Sun, Feb 07, 2016 at 02:28:04PM -0400, David Pr
Package: quagga-bgpd
Version: 1.1.0-3
Severity: grave
Hi,
I lost all of my IPv6 connectivity this morning; a bit of searching shows that
it is due to an automated upgrade of:
2017-01-05 07:36:26 upgrade quagga:amd64 1.0.20160315-2 1.1.0-3
None of the neighbors see my IPv6 route anymore; it is
Processing commands for cont...@bugs.debian.org:
> severity 850196 normal
Bug #850196 {Done: Niels Thykier } [release.debian.org]
unblock: dgit/2.14
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850196: http://bugs.debian.o
Peter Palfrader writes:
> It's a serious bug that makes it break in many cases, requiring the
> sysadmin to clean up and/or reboot the system. Whether or not it's RC
> in the end is the decision of the release team, but this severity was
> set after discussing this on #debian-release.
Is anythi
On 05.01.2017 07:01, Salvatore Bonaccorso wrote:
> Source: zendframework
> Version: 1.12.9+dfsg-1
> Severity: grave
> Tags: upstream security
> Justification: user security hole
>
> Hi,
>
> the following vulnerability was published for zendframework.
>
> CVE-2016-10034[0]:
> | The setFrom functi
Hi
On Thu, Jan 05, 2017 at 10:34:29AM +0100, Markus Frosch wrote:
> On 05.01.2017 07:01, Salvatore Bonaccorso wrote:
> > Source: zendframework
> > Version: 1.12.9+dfsg-1
> > Severity: grave
> > Tags: upstream security
> > Justification: user security hole
> >
> > Hi,
> >
> > the following vulner
Hello,
in
d/gnustep-dl2-postgresql-adaptor.maintscript
the first link uses "Current" which is already a symlink. When one
replaces this with "0" the upgrade works fine. (I tested this with
-9+nmu build on sid upgrading to the patched -15 which also failed here
for the unpatched version.
I
Hi,
CCing upstream author for confirmation. Nicola we are trying to understand
what security fix went into tcpdf 6.2.0. The bug is private on
sourceforge, could you make it public now?
For more details see: https://bugs.debian.org/814030
On Wed, 04 Jan 2017, David Prévot wrote:
> >> Can you cont
Package: src:dune-grid
Version: 2.5.0-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:python-django
Version: 1:1.10.3-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
-
Package: src:fabric
Version: 1.13.1-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
--
Hi,
I tried this from a fresh git build and can not reproduce it. Could you
please double check that
"Settings/Preferences/Marking Changes/Ask to confirm changes that also
affect other packages"
is set?
Cheers,
Michael
On 05/01/17 09:23, Brian May wrote:
Peter Palfrader writes:
It's a serious bug that makes it break in many cases, requiring the
sysadmin to clean up and/or reboot the system. Whether or not it's RC
in the end is the decision of the release team, but this severity was
set after discussing th
Package: src:nuitka
Version: 0.5.24.4+ds-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
-
Package: src:heat
Version: 1:7.0.0-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
---
Processing commands for cont...@bugs.debian.org:
> severity 849718 normal
Bug #849718 [synaptic] [synaptic] Synaptic does not ask about changes anymore
Severity set to 'normal' from 'grave'
> tags 849718 + unreproducible
Bug #849718 [synaptic] [synaptic] Synaptic does not ask about changes anymore
Processing control commands:
> reopen -1
Bug #850160 {Done: Reiner Herrmann } [firejail] firejail:
CVE-2017-5180: local root exploit
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer
Control: reopen -1
Hi Salvatore,
On Thu, Jan 05, 2017 at 07:54:24AM +0100, Salvatore Bonaccorso wrote:
> On Wed, Jan 04, 2017 at 11:21:05PM +, Debian Bug Tracking System wrote:
> >* Add upstream fix for CVE-2017-5180 (Closes: #850160).
>
> Thanks. The fix had a followup which does not se
Processing commands for cont...@bugs.debian.org:
> reassign 844781 dietlibc 0.34~cvs20160606-3
Bug #844781 [src:libowfat] libowfat FTBFS on s390x: undefined reference to
`__libc_waitpid'
Bug reassigned from package 'src:libowfat' to 'dietlibc'.
No longer marked as found in versions libowfat/0.30-
Source: forge
Version: 0.9.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Since the latest update of the packaging, src:forge fails to build due
to configuration error whilst looking for glm. Multiple architectures
are affecte
Package: reconserver
Version: 0.13.0-1
Severity: serious
Your package failed to build on ppc64el (twice), blocking the resiprocate
transition.
reConServer.cxx: In member function 'virtual int
recon::ReConServerProcess::main(int, char**)':
reConServer.cxx:941:164: error: no matching function for
Processing commands for cont...@bugs.debian.org:
> tags 850025 + pending
Bug #850025 [python-crypto] python-crypto: regression: 2.6-4+deb7u4 breaks
python-paramiko
Ignoring request to alter tags of bug #850025 to the same tags previously set
> tags 850077 + pending
Bug #850077 [python-paramiko] p
Package: python-social-auth
Version: 0.3.0-1
Severity: grave
Hi
The library is now completely unusable as it requires at least
social_core, which is not yet packaged. All files are currently stub
which should map old social auth API to new modularized code and
without the dependencies this is jus
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
Source: forge
Version: 0.9.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Since the latest update of the packaging, src:fo
Control: tag -1 + patch
The same issue is noticed on mips64el:
https://buildd.debian.org/status/fetch.php?pkg=libowfat&arch=mips64el&ver=0.30-2&stamp=1483522524
Both archs (s390x and mips64el) do not supportwaitpid, wait4 is used instead.
(https://github.com/ensc/dietlibc/blob/master/s390x/__wai
Processing control commands:
> tag -1 + patch
Bug #844781 [dietlibc] libowfat FTBFS on s390x and mips64: undefined reference
Added tag(s) patch.
--
844781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi
On 05/01/2017 12:05, Santiago Vila wrote:
Status:FAILED
Output:
--
There are not enough slots available in the system to satisfy the 2
slots
that were requested by the application:
Processing commands for cont...@bugs.debian.org:
> retitle 844781 libowfat FTBFS on s390x and mips64: undefined reference
Bug #844781 [dietlibc] libowfat FTBFS on s390x and mips64: undefined reference
Ignoring request to change the title of bug#844781 to the same title
> to __libc_waitpid
Unknown
Processing commands for cont...@bugs.debian.org:
> retitle 844781 libowfat FTBFS on s390x and mips64el: undefined reference
Bug #844781 [dietlibc] libowfat FTBFS on s390x and mips64: undefined reference
Changed Bug title to 'libowfat FTBFS on s390x and mips64el: undefined
reference' from 'libowfa
latinovic dixit:
> The patch that solves this is attached.
I think the patch is broken, wait4() requires an additional
argument which must be zero for waitpid() emulation, not some
random stack (or register, depending on the architecture) garbage.
bye,
//mirabilos
--
Stéphane, I actually don’t
Processing control commands:
> retitle -1 dietlibc: waitpid broken w/ -lpthread on s390, s390x, mips64, ia64
Bug #844781 [dietlibc] libowfat FTBFS on s390x and mips64el: undefined reference
Changed Bug title to 'dietlibc: waitpid broken w/ -lpthread on s390, s390x,
mips64, ia64' from 'libowfat FT
Control: retitle -1 dietlibc: waitpid broken w/ -lpthread on s390, s390x,
mips64, ia64
Control: tags -1 + confirmed
Control: tags -1 - patch
Thanks for reassigning this.
On 01/05/2017 11:48 AM, latinovic wrote:
> Both archs (s390x and mips64el) do not support waitpid, wait4 is used instead.
> (h
Processing commands for cont...@bugs.debian.org:
> # let me help you...
> retitle 844781 libowfat FTBFS on s390x and mips64: undefined reference to
> __libc_waitpid
Bug #844781 [dietlibc] dietlibc: waitpid broken w/ -lpthread on s390, s390x,
mips64, ia64
Changed Bug title to 'libowfat FTBFS on s
Processing commands for cont...@bugs.debian.org:
> found 842244 4.0.0+dfsg1-3
Bug #842244 {Done: Thomas Goirand } [src:congress] congress:
FTBFS randomly (failing tests)
Marked as found in versions congress/4.0.0+dfsg1-3; no longer marked as fixed
in versions congress/4.0.0+dfsg1-3 and reopened.
Processing commands for cont...@bugs.debian.org:
> # sorry Christian, got your mail later than mine was sent
> retitle 844781 dietlibc: waitpid broken with -lpthread on s390, s390x,
> mips64, ia64
Bug #844781 [dietlibc] libowfat FTBFS on s390x and mips64: undefined reference
to __libc_waitpid
Ch
found 842244 4.0.0+dfsg1-3
severity 842244 important
thanks
Hi.
Sorry for the reopening, but this is still failing for me.
Quite often indeed. I built this 100 times yesterday and it failed 86 times.
Downgrading to "important" only to be on par with every other
FTBFS-randomly bug I've detected
Package: retty
Version: 1.0-2
Severity: grave
Hi,
while looking at fixing #817652 I tried to use retty but couldn't get
it to work. In the second terminal, nothing happens:
$ retty 3733
codesize: 138 codeaddr: ff99840c
stack: ff9983fc eip: ff998414 sub:48
^C
^\Verlassen
^C doesn't quit retty; o
On Thu, 2017-01-05 at 12:59 +0200, Graham Inggs wrote:
> On 05/01/2017 12:05, Santiago Vila wrote:
> > Status:FAILED
> > Output:
> > --
> >
> > There are not enough slots available in the system to
>
Your message dated Thu, 05 Jan 2017 12:03:31 +
with message-id
and subject line Bug#817461: fixed in freepwing 1.5-2
has caused the Debian Bug report #817461,
regarding freepwing: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt wit
Processing control commands:
> severity -1 serious
Bug #850142 [libmariadb-dev] libmariadb-dev: mariadb_config emits trailing
binary bullshit on mips64el
Severity set to 'serious' from 'important'
--
850142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850142
Debian Bug Tracking System
Cont
CC'd the Debian CMake Team, who might be able to help.
On 05/01/17 10:48, Ghislain Vaillant wrote:
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
Source: forge
Version: 0.9.2-2
Severity: serious
Justification: fails to build from source (bu
Now CC'd to the Debian CMake Team
On 05/01/17 12:26, Ghislain Vaillant wrote:
CC'd the Debian CMake Team, who might be able to help.
On 05/01/17 10:48, Ghislain Vaillant wrote:
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
Source: forge
Processing commands for cont...@bugs.debian.org:
> found 848414 0.6.1-1
Bug #848414 {Done: Free Ekanayaka } [src:systemfixtures]
systemfixtures: FTBFS randomly (failing tests)
Marked as found in versions systemfixtures/0.6.1-1; no longer marked as fixed
in versions systemfixtures/0.6.1-1 and reo
found 848414 0.6.1-1
severity 848414 important
thanks
Hi.
Sorry for the reopening but this is still (randomly) failing for me.
The following test failed for me:
ERROR: test_listen (systemfixtures.tests.test_executable.FakeExecutableTest)
at least three times.
Build logs available here:
https:
Processing commands for cont...@bugs.debian.org:
> found 849813 0.6.5.8-2
Bug #849813 [zfs-zed] [openmediavault.local] zfs-zed.service can't start
Marked as found in versions zfs-linux/0.6.5.8-2.
> severity 849813 grave
Bug #849813 [zfs-zed] [openmediavault.local] zfs-zed.service can't start
Sever
On 2017-01-04 21:55, Paul Gevers wrote:
> Hi Frederic-Emmanuel, Andreas,
>
> @Andreas, am I correct in the assumption that jessie to stretch with
> tango-db was fine until MariaDB became the default? Or was this
> migration with tango-db just never tested before? Have you seen other
> dbconfig-com
Hi
Aurelien Jarno writes:
> On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote:
>> On 29/12/16 20:56, Gaudenz Steinlin wrote:
>
> The problem is indeed a memory issue, not that the buildd doesn't have
> enough memory, but just that you can allocate only 2GB per process on a
> 32-bit MIPS machine
Processing commands for cont...@bugs.debian.org:
> unarchive 802706
Bug #802706 {Done: Drew Parsons } [src:slepc] slepc:
FTBFS: Unable to link with PETSc
Unarchived Bug 802706
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
802706: http://bugs.debian.org
Your message dated Thu, 05 Jan 2017 13:07:39 +
with message-id
and subject line Bug#800182: fixed in esix 1-3
has caused the Debian Bug report #800182,
regarding esix: Please migrate a supported debhelper compat level
to be marked as done.
This means that you claim that the problem has been d
Your message dated Thu, 05 Jan 2017 13:07:04 +
with message-id
and subject line Bug#849660: fixed in ceph 10.2.5-3
has caused the Debian Bug report #849660,
regarding ceph: FTBFS on armel: error: field 'result' has incomplete type
'std::promise'
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> found 802706 3.7.3+dfsg1-3
Bug #802706 {Done: Drew Parsons } [src:slepc] slepc:
FTBFS: Unable to link with PETSc
Marked as found in versions slepc/3.7.3+dfsg1-3 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assis
found 802706 3.7.3+dfsg1-3
thanks
Hi.
Sorry for the reopening but this is happening again in stretch.
(I built this package 200 times, and it failed 200 times).
Build logs available here:
https://people.debian.org/~sanvila/build-logs/slepc/
Thanks.
Processing commands for cont...@bugs.debian.org:
> tag 849660 pending
Bug #849660 {Done: Gaudenz Steinlin } [src:ceph] ceph:
FTBFS on armel: error: field 'result' has incomplete type
'std::promise'
Added tag(s) pending.
> --
Stopping processing here.
Please contact me if you need assistance.
--
tag 849660 pending
--
We believe that the bug #849660 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:
http://anonscm.debian.org/cgit/pkg-ceph/ceph.git/diff/?id=eeff8d6
(This message was generated automatically by
Hi,
Daniel Kahn Gillmor:
> The remaining problem for me ws that when i use tor, if i get back
> records, the connections fail, but the IPv6 records are not marked as
> dead, so they fail repeatedly.
Same here, with a package built from commit
32bae0c609cb0c6180e9405a3d6a8fb3c0dec20e in the V
Your message dated Thu, 05 Jan 2017 13:19:00 +
with message-id
and subject line Bug#831195: fixed in xmacro 0.3pre-2911-7
has caused the Debian Bug report #831195,
regarding xmacro: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro "min"
passed 3 arguments, but takes just 2
to be mark
Processing commands for cont...@bugs.debian.org:
> unarchive 834959
Bug #834959 {Done: Martín Ferrari } [src:golang-goleveldb]
golang-goleveldb: FTBFS too much often (failing tests)
Unarchived Bug 834959
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
83
On 05/01/17 14:00, Gaudenz Steinlin wrote:
>
> Hi
>
> Aurelien Jarno writes:
>
>> On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote:
>>> On 29/12/16 20:56, Gaudenz Steinlin wrote:
>>
>> The problem is indeed a memory issue, not that the buildd doesn't have
>> enough memory, but just that you ca
Processing commands for cont...@bugs.debian.org:
> found 834959 0+git20160825.6ae1797-2
Bug #834959 {Done: Martín Ferrari } [src:golang-goleveldb]
golang-goleveldb: FTBFS too much often (failing tests)
Marked as found in versions golang-goleveldb/0+git20160825.6ae1797-2 and
reopened.
> retitle 8
Package: libsrtp2-dev
Severity: serious
Version: 2.0.0-1
Hi,
it seems like the headers in the crypto subdirectory should also be
included, at least partially. Without this, constants like
SRTP_AES_128_ICM
SRTP_NULL_CIPHER
and others are missing and they seem to be needed for usage of the API.
found 834959 0+git20160825.6ae1797-2
retitle 834959 golang-goleveldb: FTBFS randomly (failing tests)
severity 834959 important
thanks
Hi.
Sorry for the reopening but this is still failing (randomly) for me.
Build logs available here:
https://people.debian.org/~sanvila/build-logs/golang-goleveld
Hi
The problem is that the mariadb-connector-c package adds symbol
versioning to
the mariadb_config binary. By doing so it fails to correctly export the
_IO_stdin_used symbol added by the GNU libc.
The attached patch fixes the problem on mips64el.
This solution was used to fix lua5.2 package w
Hi,
It seems that maxparallel=1, which is used for arm64, helps.
Using only 1 job I have got libatomic issue as well.
Errors with atomic functions occurs because mips32 arches does not
support use of 8-byte atomics functions.
Linking with "latomic" library resolves this problem.
export DEB_LD
Processing commands for cont...@bugs.debian.org:
> reassign 850216 libmariadbclient18
Bug #850216 [src:mysql-5.6] mysql-server-5.6: Listens on * by default after
installation (related to use of alternatives)
Bug reassigned from package 'src:mysql-5.6' to 'libmariadbclient18'.
No longer marked as
reassign 850216 libmariadbclient18
thanks
Hi Salvatore,
Thank you for the report. I can reproduce this on stretch.
Otto: please could you take a look at this?
It seems that the problem is that libmariadbclient18 depends on
mariadb-common directly. mariadb-common's postinst adds
/etc/mysql/maria
Re: Adrian Bunk 2016-12-21 <20161221212734.64mvgghokxot7...@bunk.spdns.de>
> On Wed, Nov 30, 2016 at 04:53:58PM +0100, Marvin Stark wrote:
> > Am 2016-11-10 23:33, schrieb Sebastian Andrzej Siewior:
> >...
> > > Marvin: unless Adrian pulls out a patch I suggest you prepare a package
> > > to build
Your message dated Thu, 5 Jan 2017 15:25:50 +0100
with message-id <20170105142550.dkycj4qlbaagp...@home.ouaza.com>
and subject line Re: Bug#850236: python-django: FTBFS (AssertionError)
has caused the Debian Bug report #850236,
regarding python-django: FTBFS (AssertionError)
to be marked as done.
On Thu, Jan 05, 2017 at 03:25:50PM +0100, Raphael Hertzog wrote:
> This is https://code.djangoproject.com/ticket/27637 and has been fixed
> in version 1.10.5 that just got uploaded. The failure only happens during
> one week every 4 years.
A whole week? I am not sure the security team would be ha
On Thu, 05 Jan 2017, Santiago Vila wrote:
> It depends. My goal is to build 25000 source packages in a row and have
> 0.5 failures on average in total (i.e. closer to 0 than to 1).
>
> If we have 50 packages which FTBFS randomly, they should fail less
> than 1% on average.
>
> One week every 4 ye
Your message dated Thu, 05 Jan 2017 15:10:13 +
with message-id
and subject line Bug#828556: fixed in sslscan 1.11.5-rbsec-1.1
has caused the Debian Bug report #828556,
regarding sslscan: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt w
Quoting Michal Čihař :
The library is now completely unusable as it requires at least
social_core, which is not yet packaged. All files are currently stub
which should map old social auth API to new modularized code and
without the dependencies this is just completely unusable.
Oh, sh*t, big fa
On Thu, Jan 05, 2017 at 04:07:58PM +0100, Raphael Hertzog wrote:
> On Thu, 05 Jan 2017, Santiago Vila wrote:
> > It depends. My goal is to build 25000 source packages in a row and have
> > 0.5 failures on average in total (i.e. closer to 0 than to 1).
> >
> > If we have 50 packages which FTBFS ran
Control: clone -1 -2
Control: retitle -2 Various regressions in unit tests when linking against
-lpthread
On 01/05/2017 12:17 PM, Christian Seiler wrote:
> The correct solution is to change the name of the function to
> __libc_waitpid in __waitpid.c and to define a weak alias for
> waitpid there.
Processing control commands:
> clone -1 -2
Bug #844781 [dietlibc] dietlibc: waitpid broken with -lpthread on s390, s390x,
mips64, ia64
Bug 844781 cloned as bug 850276
> retitle -2 Various regressions in unit tests when linking against -lpthread
Bug #850276 [dietlibc] dietlibc: waitpid broken with
Your message dated Thu, 05 Jan 2017 16:00:10 +
with message-id
and subject line Bug#848851: fixed in linux 4.8.15-2
has caused the Debian Bug report #848851,
regarding linux: FTBFS on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> tags 849813 + pending
Bug #849813 [zfs-zed] [openmediavault.local] zfs-zed.service can't start
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
849813: http://bugs.debian.org/cgi-bin/bugreport
control: block -1 by 850277
Processing control commands:
> block -1 by 850277
Bug #850243 [src:forge] forge: FTBFS on multiple architectures
850243 was not blocked by any bugs.
850243 was not blocking any bugs.
Added blocking bug(s) of 850243: 850277
--
850243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850243
Debian
Processing control commands:
> retitle -1 dietlibc: libpthread overrides __errno_location even with TLS
> enabled
Bug #850276 [dietlibc] Various regressions in unit tests when linking against
-lpthread
Changed Bug title to 'dietlibc: libpthread overrides __errno_location even with
TLS enabled'
Your message dated Thu, 05 Jan 2017 16:20:14 +
with message-id
and subject line Bug#849813: fixed in zfs-linux 0.6.5.8-3
has caused the Debian Bug report #849813,
regarding [openmediavault.local] zfs-zed.service can't start
to be marked as done.
This means that you claim that the problem has
Control: retitle -1 dietlibc: libpthread overrides __errno_location even with
TLS enabled
I've now tracked this down: libpthread apparently overrode
__errno_location to point it to td->errno, where td is POSIX
thread descriptor. This is just plain wrong, because errno is
now a (TLS) variable, whi
Source: python-gitdb
Version: 2.0.0-2
Severity: serious
X-debbugs-Cc: on...@debian.org
python-gitdb FTBFS on mips on the buildd:
https://buildd.debian.org/status/fetch.php?pkg=python-gitdb&arch=mips&ver=2.0.0-2&stamp=148361
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B
Processing commands for cont...@bugs.debian.org:
> fixed 85 2.0.21-18
Bug #85 {Done: Takatsugu Nokubi }
[namazu2,namazu2-index-tools] namazu2-index-tools and namazu2: error when
trying to install together
Marked as fixed in versions namazu2/2.0.21-18.
> thanks
Stopping processing here.
On 05/01/17 10:08, Roger Leigh wrote:
On 05/01/17 09:23, Brian May wrote:
Peter Palfrader writes:
It's a serious bug that makes it break in many cases, requiring the
sysadmin to clean up and/or reboot the system. Whether or not it's RC
in the end is the decision of the release team, but th
Package: lambdabot
Version: 5.0.3-4
Severity: serious
Tags: stretch sid
# apt-get build-dep lambdabot
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or
Hello,
I discuss with the tango-db upstream and he found that
this one line fixed the problem, befrore doing the tango-db upgrade
UPDATE mysql.proc SET Definer='tango@localhost' where Db='tango';
Ideally it should be something like
UPDATE mysql.proc SET Definer='xxx' where Db='yyy';
where xxx
Hi,
Please CC me, I only just saw this email when I checked on the bugreport.
On 30/12/16 17:17, Ghislain Vaillant wrote:
> CC'd to d-science,
>
> On Fri, 30 Dec 2016 01:24:07 + James Cowgill wrote:
>> On 30/12/16 00:50, Ghislain Vaillant wrote:
>> > On Thu, 29 Dec 2016 00:30:58 + James
Your message dated Thu, 5 Jan 2017 16:30:53 -0200
with message-id
and subject line Re: redet: Removal of debhelper compat 4
has caused the Debian Bug report #817649,
regarding redet: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt wit
Control: severity -1 important
On Thu, Mar 17, 2016 at 5:14 PM, Yves-Alexis Perez wrote:
> On jeu., 2016-03-17 at 14:22 +0100, László Böszörményi (GCS) wrote:
>> But as mentioned above, I think six months
>> updates may be enough for advanced users. You get new features while
>> not compile a ne
Processing control commands:
> severity -1 important
Bug #810349 [src:linux-patch-grsecurity2] linux-patch-grsecurity2: removal of
linux-patch-grsecurity2?
Severity set to 'important' from 'serious'
--
810349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810349
Debian Bug Tracking System
Co
Source: mate-polkit
Version: 1.16.0-1
Severity: serious
mate-polkit has Provides: policykit-1-gnome but the xdg autostart
contains
OnlyShowIn=Mate;
As a result, desktop environments like Cinnamon, which have a dependency
on policykit-1-gnome will be broken, unless the real policykit-1-gnome
packa
It may be too late for this, but here goes:
In the source package's control file, if you replace the Build-Depends
on libssl-dev with:
libssl1.0-dev | libssl-dev (<< 1.1.0~)
the package builds and appears to work normally. This is what OpenSSH
(and maybe others) used to get past this FTBFS
On 2017-01-05 14:00, Gaudenz Steinlin wrote:
>
> Hi
>
> Aurelien Jarno writes:
>
> > On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote:
> >> On 29/12/16 20:56, Gaudenz Steinlin wrote:
> >
> > The problem is indeed a memory issue, not that the buildd doesn't have
> > enough memory, but just that
Processing control commands:
> severity -1 normal
Bug #848178 [libtesseract3] libtesseract3: generated shlibs dependencies are
not strict enough
Severity set to 'normal' from 'grave'
--
848178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848178
Debian Bug Tracking System
Contact ow...@bugs
Control: severity -1 normal
On Fri, 16 Dec 2016 12:23:03 +0100 Philip Rinn wrote:
> Hi Adrian,
>
> On 15.12.2016 at 20:50, Adrian Bunk wrote:
> > Please do not close bugs that are actual bug - the generated
> > dependencies must ensure that problems like the issue in this
> > bug won't happen.
On 2017-01-05 15:08:00 [+0100], Christoph Berg wrote:
> NMU diff:
>
>
> Control files: lines which differ (wdiff format)
>
> Build-Depends: debhelper (>= 9), {+libssl1.0-dev |+} libssl-dev {+(<<
> 1.1.0~)+}
why on libssl-dev (<< 1.1.0~)?
Otherwi
Package: reportbug
Version: 7.1.2
Severity: grave
Justification: causes non-serious data loss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When attaching a gzip'ed tarball to a bug report, reportbug crashes
without writing the drafted bug report anywhere:
application/gzip; charset=binary
Tra
Source: mock
Version: 1.3.2-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Hi,
the following vulnerability was published for mock. I'm not too
familiar with it, but following the code and the applied upstream
commit 1.3.2-1 should be vulnerable.
CVE-2016-6299[0
Dear Dan,
Thanks for getting in touch - sorry for not replying sooner. "winrm"
is the name of a Microsoft Windows command, so users might expect a
Linux command with the same name to perform a similar function. I'm
not familiar with what the command in your package does, and it's a
while since I d
Your message dated Thu, 05 Jan 2017 22:53:38 +0100
with message-id <85k2a9i36l@boum.org>
and subject line Re: Bug#834007: bookletimposer: Should not be part of Stretch
has caused the Debian Bug report #834007,
regarding bookletimposer: Should not be part of Stretch
to be marked as done.
This m
1 - 100 of 142 matches
Mail list logo
