Your message dated Sat, 15 Feb 2020 09:50:01 +0200
with message-id <20200215075001.mbohjg7oaopsqmf3@cbuster.nuvreauspam>
and subject line Re: Bug#951312: networking: unsetting ipv6 brings many problems
has caused the Debian Bug report #951312,
regarding networking: unsetting ipv6 brings many proble
Processing commands for cont...@bugs.debian.org:
> reassign 933479 src:objcryst-fox
Bug #933479 [objcryst-fox] objcryst-fox: Please rebuild against wxWidgets GTK 3
package
Bug reassigned from package 'objcryst-fox' to 'src:objcryst-fox'.
Ignoring request to alter found versions of bug #933479 to
Dear Matthias, thanks for your report.
I have just send an email to the Nominatim system administrator
to see what we can do.
Best,
Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C6
Processing control commands:
> tags -1 + patch
Bug #950816 [mpv] mpv: unintended code execution vulnerability
Added tag(s) patch.
> found -1 mpv/0.29.1-1
Bug #950816 [mpv] mpv: unintended code execution vulnerability
Marked as found in versions mpv/0.29.1-1.
--
950816: https://bugs.debian.org/cg
Control: tags -1 + patch
Control: found -1 mpv/0.29.1-1
FYI, the patch below works for me.
Also, I think the version in stable is also affected. The code differs
slightly so the patch will need a little tweak.
Cheers.
--
>From 937749b545407aa68b1d15ea5e19a6c23d62da42 Mon Sep 17 00:00:00 2001
Your message dated Sat, 15 Feb 2020 06:05:00 +
with message-id
and subject line Bug#949142: fixed in firehol 3.1.6+ds-9
has caused the Debian Bug report #949142,
regarding firehol: FTBFS: configure: error: cannot produce all pandoc outputs,
bailing out
to be marked as done.
This means that y
Your message dated Sat, 15 Feb 2020 03:04:36 +
with message-id
and subject line Bug#874870: fixed in doomsday 2.2.2+ds1-1~exp1
has caused the Debian Bug report #874870,
regarding [doomsday] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has bee
Your message dated Sat, 15 Feb 2020 02:38:59 +
with message-id
and subject line Bug#948428: fixed in html5lib 1.0.1-2
has caused the Debian Bug report #948428,
regarding html5lib ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tag -1 pending
Hello,
Bug #948428 in html5lib 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:
https://salsa.debian.org/python-team/modules/html5lib/commit/70f3b00e63cc3c93d3154
Processing control commands:
> tag -1 pending
Bug #948428 [src:html5lib] html5lib ftbfs in unstable
Added tag(s) pending.
--
948428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 14 Feb 2020 16:08:12 -0700
with message-id <20200214230812.GA801560@debian-Aspire-M5-481G.FokFamily>
and subject line Bug#935296: fixed in reposurgeon 4.2-1
has caused the Debian Bug report #935296,
regarding reposurgeon: FTBFS on amd64
to be marked as done.
This means that
On Fri, 14 Feb 2020 at 17:48:53 -0500, Boyuan Yang wrote:
> I will seek for the switch back to /usr/games/ surely but that means patches
> onto the build system. Luckily doomsday 2.x is using CMake with
> GNUInstallDirs, which means pretty standard way of handling this issue.
You can probably just
Hi Markus,
在 2020-02-14五的 23:33 +0100，Markus Koschany写道：
> Hi,
>
> Am 14.02.20 um 23:12 schrieb Boyuan Yang:
> [...]
> > Since the complete removal of Qt4 is just around the corner, I am
> > proposing to
> > do the following work to keep doomsday in Debian's development repository:
> >
> > * A T
Hi,
Am 14.02.20 um 23:12 schrieb Boyuan Yang:
[...]
> Since the complete removal of Qt4 is just around the corner, I am proposing to
> do the following work to keep doomsday in Debian's development repository:
>
> * A Team-upload onto experimental of v2.2.2 with Qt5 support,
> * NO support for /u
X-Debbugs-CC: a...@debian.org mgilb...@debian.org
Hi all,
(see bottom)
On Tue, 1 Oct 2019 19:42:50 +0200 Markus Koschany wrote:
> Hello,
>
> Am 29.09.19 um 22:38 schrieb Moritz Mühlenhoff:
> > On Sun, Mar 18, 2018 at 09:11:24PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> >> Hi! Version
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Processing commands for cont...@bugs.debian.org:
> severity 936358 important
Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Your message dated Fri, 14 Feb 2020 20:38:13 +
with message-id
and subject line Bug#950937: fixed in hw-probe 1.4-2
has caused the Debian Bug report #950937,
regarding hw-probe: FTBFS due to missing build dependency help2man
to be marked as done.
This means that you claim that the problem has
Control: reopen -1
Control: severity -1 important
Hello,
The new repository[1] that was supposedly fixing this bug report
doesn't even include the upstream sources (or their git history).
It's a plain packaging repo with only the debian/ directory.
I don't see how that's supposed to fulfil the ne
Processing control commands:
> reopen -1
Bug #888670 {Done: Debian FTP Masters }
[src:gnome-system-tools] gnome-system-tools: has been unmaintained upstream for
a long time
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may ne
Control: severity -1 normal
Hi,
Francesco Poli (wintermute) wrote:
> After upgrading
>
> [UPGRADE] libkeyutils1:amd64 1.6-6 -> 1.6.1-2
>
> I get the following warning with
>
> # rkhunter --sk -c
>
> in /var/log/rkhunter.log:
>
> Info: Starting test name 'running_procs'
> Checking
Processing control commands:
> severity -1 normal
Bug #951338 [libkeyutils1] libkeyutils1: rkhunter warns that libkeyutils.so.1.9
may contain a possible rootkit
Severity set to 'normal' from 'grave'
--
951338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951338
Debian Bug Tracking System
C
[Dimitri John Ledkov]
> Anyway, I hacked up something that works, albeit looks ugly.
Thank you very much. I hope upstream will accept the fix or some
variant of it. :)
--
Happy hacking
Petter Reinholdtsen
Package: libkeyutils1
Version: 1.6.1-2
Severity: grave
Tags: security
Justification: user security hole
Hello!
After upgrading
[UPGRADE] libkeyutils1:amd64 1.6-6 -> 1.6.1-2
I get the following warning with
# rkhunter --sk -c
in /var/log/rkhunter.log:
Info: Starting test name 'running_
I've uploaded new packages of toil, cwltool, and python-schema-salad that
should fix this
On Fri, 27 Dec 2019 23:14:46 +0100 Andreas Beckmann wrote:
> Package: casparcg-server
> Version: 2.2.0+dfsg-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
>
> Hi,
>
> casparcg-server FTBFS in a current sid pbuilder environment:
>
> CMake Error at CMakeModules/FindG
Your message dated Fri, 14 Feb 2020 18:05:37 +
with message-id
and subject line Bug#950072: fixed in python-asttokens 2.0.3-1
has caused the Debian Bug report #950072,
regarding python-asttokens FTBFS with Python 3.8 as supported version
to be marked as done.
This means that you claim that th
Ralf Treinen writes:
> snek build-depends on picolibc-arm-none-eabi which does not exist (yet)
> in sid.
Yup. It's been stuck in the 'new' queue for several months now.
--
-keith
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> severity 945442 grave
Bug #945442 [neomutt] Possible to backspace past beginning of string, which
appears to be identical to having pressed Enter immediately, without any
backspace
Severity set to 'grave' from 'normal'
> thanks
Stopping processi
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Processing control commands:
> tags 950720 - patch + pending
Bug #950720 [wp2latex] FTBFS: error: conflicting declaration ‘typedef long long
unsigned int __u64’
Removed tag(s) patch.
Bug #950720 [wp2latex] FTBFS: error: conflicting declaration ‘typedef long long
unsigned int __u64’
Added tag(s)
Control: tags 950720 - patch + pending
Am 05.02.2020 um 12:11 teilte Hilmar Preusse mit:
> the package FTBFS on s390x & arm64.
>
> ./atoms/include/typedfs.h:73:14: note: previous declaration as ‘typedef long
> int __s64’
>73 | typedef int __s64 __attribute__((mode(DI)));
> |
Your message dated Fri, 14 Feb 2020 15:05:34 +
with message-id
and subject line Bug#950638: fixed in pykwalify 1.7.0-3
has caused the Debian Bug report #950638,
regarding pykwalify FTBFS: TestCore.test_core_files failure
to be marked as done.
This means that you claim that the problem has bee
Package: user-mode-linux
Version: 4.19-1um-1
Severity: serious
Tags: patch
Dear maintainer,
The current user-mode-linux package in buster fails to build the latest
linux kernel in buster due to the fix-port-helper-path.patch:
Applying patch
/build/user-mode-linux-4.19-1um/debian/patches/fix-por
Hi Ralf,
I would have bet I have uploaded r-cran-kutils together with
r-cran-rockchalk to new - but it does not seem to be the case.
@Thorsten: If you have time could you please have a look at the
just uploaded r-cran-kutils?
Thanks a lot
Andreas.
On Fri, Feb 14, 2020 at 08:57:41AM +010
On Thu, 30 Jan 2020 12:08:33 +0300 Dmitry Shachnev
wrote:
> setuptools-scm has removed Python 2 support (see #938470), so python-keyring
> build-dependencies are no longer satisfiable.
It has since been reintroduced.
> Thus I am going to remove Python 2 support from python-keyring, so I am
> bum
Your message dated Fri, 14 Feb 2020 13:05:40 +
with message-id
and subject line Bug#951139: fixed in toil 3.24.0-1
has caused the Debian Bug report #951139,
regarding toil fails it's autopkg tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: networking
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation? lost of networking, caused by dhcp not
renewing IP address
* What exactly did you do (or not do) that was effective (or
ineffective)? disabled ipv6
* Wha
On 2/14/20 2:30 AM, Holger Levsen wrote:
> On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote:
>> thanks! I'm gonna go ahead and file an RM bug for the following pkgs
>> too: yum createrepo python-lzma yum-metadata-parser mock yum-utils
>> dtc-xen deltarpm
>>
>> they are a closed set
>
>
Cant' reproduce, I was using 68.4.1esr-1~deb10u1, today I upgraded to
68.5.0esr-1~deb10u1, everything works fine.
System is Debian Buster 10 on AMD64.
Source: snek
Version: 1.3-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Hi,
snek build-depends on picolibc-arm-none-eabi which does not exist (yet)
in sid.
-Ralf.
Source: r-cran-rockchalk
Version: 1.8.144+dfsg-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Hi,
r-cran-rockchalk build-depends on r-cran-kutils which does not exist in
sid.
-Ralf
42 matches
Mail list logo
