Your message dated Thu, 16 Jul 2020 05:05:56 +
with message-id
and subject line Bug#964944: fixed in libreoffice 1:7.0.0~rc2-1
has caused the Debian Bug report #964944,
regarding language pack not selectable in libreoffice settings
to be marked as done.
This means that you claim that the prob
Rob Browning writes:
> Bdale Garbee writes:
>
>> I'm not interested in maintaining pcb any more.
>
> Does that mean geda-gaf etc? If so might it make sense for you (or
> who?) to file a removal request, i.e. ROM or similar?
Sorry, you make a good point, geda-gaf and pcb aren't the same thing.
On 7/7/20 8:13 PM, Ben Hutchings wrote:
Control: reassign -1 src:linux
Control: tag -1 moreinfo
On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote:
Package: linux-signed-amd64
Version: 4.19.0-9-amd64
We've had two separate reports now of debian buster users running
4.19.0-9-amd64 who experi
Your message dated Thu, 16 Jul 2020 03:48:40 +
with message-id
and subject line Bug#959947: fixed in m2crypto 0.36.0-1
has caused the Debian Bug report #959947,
regarding python-m2crypto-doc: missing Breaks+Replaces: m2crypto-doc (<<
0.35.2-2)
to be marked as done.
This means that you claim
Your message dated Thu, 16 Jul 2020 03:48:40 +
with message-id
and subject line Bug#964299: fixed in m2crypto 0.36.0-1
has caused the Debian Bug report #964299,
regarding src:m2crypto: fails to migrate to testing for too long: unfixed RC
bug and maintainer built arch:all binaries
to be marked
Control: tag -1 pending
Hello,
Bug #959947 in m2crypto 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/m2crypto/-/commit/57061b5a380fd51a7b7
Processing control commands:
> tag -1 pending
Bug #959947 [python-m2crypto-doc] python-m2crypto-doc: missing Breaks+Replaces:
m2crypto-doc (<< 0.35.2-2)
Added tag(s) pending.
--
959947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959947
Debian Bug Tracking System
Contact ow...@bugs.debian
Package: searx
Severity: grave
Version: 0.17.0+dfsg1-1
There appears to be a missing Python dependency (werkzeug.contrib) in
the new Searx 17.0 package uploaded to unstable.
Tested in Debian unstable container.
Error log from /var/log/uwsgi/app/searx.log
---
Traceback (most recent call last):
Helmut Grohne writes:
> It is surprising that this didn't fail with earlier versions of make.
> The shell substitution is clearly wrong. It is unclear what it is
> supposed to achieve. In any case, deleting these lines makes the build
> proceed.
>
Hah, I just hit and fixed this last night when I
Bdale Garbee writes:
> I'm not interested in maintaining pcb any more.
Does that mean geda-gaf etc? If so might it make sense for you (or
who?) to file a removal request, i.e. ROM or similar?
(I can of course, but I suspect it'll be more quickly accepted if one of
the existing maintainers doe
Matthias Klose writes:
> After fixing the build with make 4.3, the build then fails with a test
> failure.
> Only seen on amd64, not on other architectures.
>
> [...]
> make check-TESTS
> make[4]: Entering directory '/<>/guile-2.0-2.0.13+1'
> Testing /<>/guile-2.0-2.0.13+1/meta/guile ...
> with
On Wed, Jul 15, 2020 at 5:22 PM Jessica Clarke wrote:
>
> [H.J. Lu Cc'ed as author of what looks like the problematic commit]
>
> On Wed, 15 Jul 2020 23:47:27 +0200 (CEST) Thorsten Glaser
> wrote:
> > Some more analysis:
> >
> > We enter libc from openssh code with the correct values in rsi and
[H.J. Lu Cc'ed as author of what looks like the problematic commit]
On Wed, 15 Jul 2020 23:47:27 +0200 (CEST) Thorsten Glaser
wrote:
> Some more analysis:
>
> We enter libc from openssh code with the correct values in rsi and rdi:
>
>
> (gdb) u
> => 0x56560e45 : call 0x5655d0b0
> (gdb)
Hello,
My 2¢ on this: speech-dispatcher build-depends on systemd in order to
get systemd.pc and read systemdsystemunitdir from it, but that fails on
experimental buildds because they currently have systemctl installed
instead of systemd:
https://buildd.debian.org/status/package.php?p=speech-dispa
I'm happy to NMU this since it's affecting some of my packages (zimlib,
libkiwix, zim-tools, etc.). debdiff is attached.
It's not clear to me why the dependency was commented out in the first
place, but it fixes the immediate issue. Let me know if that's OK and if
you'd like me to go ahead.
-- Ku
Processing commands for cont...@bugs.debian.org:
> affects 965091 openssh-server
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from
2.30]
Added indication that 965091 affects openssh-server
> affects 965091 postfix
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/
Your message dated Wed, 15 Jul 2020 23:58:56 + (UTC)
with message-id
and subject line Re: Bug#965086: ssh: setgroups: Bad address [preauth]
has caused the Debian Bug report #965087,
regarding postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address
to be marked as done.
This means
On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre wrote:
> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote:
> > There is no 2.1.0 beta4, just a beta1, so I don't know what was packaged
> in
> > February 2020. However the tests now fail with mpfr 4.1.0, seems to be
> > consistent across all archit
I seem to have attached the wrong set of patches to this bug earlier.
Here are the correct ones. Upstream bug already has the correct set of
patches.
--
Sunil
From 0a325e7847daf150885911706926b7b8f5d7a66e Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa
Date: Wed, 17 Jun 2020 14:07:30 -0700
Subj
Your message dated Wed, 15 Jul 2020 23:35:55 +0100
with message-id <20200715223555.gj2...@riva.ucam.org>
and subject line Re: Bug#965086: ssh: setgroups: Bad address [preauth]
has caused the Debian Bug report #965086,
regarding ssh: setgroups: Bad address [preauth]
to be marked as done.
This means
Hi Colin,
>sshd.c:privsep_preauth_child. But its setgroups() call seems
>straightforward, and I don't see how it could produce EFAULT:
thanks for also looking at it, yes, I tracked it down in gdb,
and the __nptl_setxid code is compiled differently, and I’m
fresh out of ideas how to track it furt
> So something clearly changed…
Compiler output, most probably. I cannot reproduce it. I tried:
struct xid_command
{
int syscall_no;
long int id[3];
volatile int cntr;
volatile int error; /* -1: no call yet, 0: success seen, >0: error
seen.
Your message dated Wed, 15 Jul 2020 22:03:39 +
with message-id
and subject line Bug#965073: fixed in macs 2.2.7.1-3
has caused the Debian Bug report #965073,
regarding macs: shared library is not properly linked with libm
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 15 Jul 2020 22:03:49 +
with message-id
and subject line Bug#961852: fixed in python-matrix-nio 0.12.0-2
has caused the Debian Bug report #961852,
regarding python-matrix-nio: autopkgtest failure: No module named 'matrix_nio'
to be marked as done.
This means that you cl
Some more analysis:
We enter libc from openssh code with the correct values in rsi and rdi:
(gdb) u
=> 0x56560e45 : call 0x5655d0b0
(gdb) info r
rax0xfffe 65534
rbx0x5663a000 1449369600
rcx0x0 0
rdx0x0
On Thu, Jul 09, 2020 at 01:08:43PM +0200, Lucas Nussbaum wrote:
> Source: diagnostics
> Version: 0.3.3-12
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200709 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package fail
Your message dated Wed, 15 Jul 2020 21:36:50 +
with message-id
and subject line Bug#963750: Removed package(s) from unstable
has caused the Debian Bug report #959981,
regarding Trademark issues with Chef/Cinc package included in Debian
to be marked as done.
This means that you claim that the
Your message dated Wed, 15 Jul 2020 21:33:46 +
with message-id
and subject line Bug#964653: fixed in freeimage 3.18.0+ds2-4
has caused the Debian Bug report #964653,
regarding freeimage: FTBFS: Source/FreeImage/PluginJPEG.cpp:506:1: error: ‘BOOL
jpeg_read_icc_profile(j_decompress_ptr, JOCTET*
On Wed, Jul 15, 2020 at 10:41:11PM +0200, Thorsten Glaser wrote:
> Package: openssh-server
> Version: 1:8.3p1-1
> Severity: grave
> Justification: renders package unusable
>
> After an upgrade of libc6 today, I can no longer log into my
> system using ssh:
Would it perhaps make sense to reassign
Package: libc6
Version: 2.31-1
Severity: grave
Justification: renders package unusable
This is related to #965086 and #965087 (and, in fact, possibly
causing them). After a glibc upgrade half the system services
(postfix, sshd, apt-get(!)) don’t work any more.
Downgrading with dpkg -i the followi
Processing control commands:
> tags 962720 + pending
Bug #962720 {Done: Adrian Bunk } [src:gst-plugins-bad1.0]
gst-plugins-bad1.0: FTBFS in sid
Added tag(s) pending.
--
962720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags 962720 + pending
Dear maintainer,
I've prepared an NMU for gst-plugins-bad1.0 (versioned as 1.16.2-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru gst-plugins-bad1.0-1.16.2/debian/build-deps gst-plu
Your message dated Wed, 15 Jul 2020 21:09:49 +
with message-id
and subject line Bug#964041: fixed in git-repair 1.20200102-2
has caused the Debian Bug report #964041,
regarding git-repair: FTBFS: duration parse error
to be marked as done.
This means that you claim that the problem has been de
Package: openssh-server
Version: 1:8.3p1-1
Severity: grave
Justification: renders package unusable
After an upgrade of libc6 today, I can no longer log into my
system using ssh:
tglase@tglase:~ $ ssh localhost
Connection reset by 127.0.0.1 port 22
Jul 15 22:33:17 tglase sshd[27084]: fatal: setgr
Package: postfix
Version: 3.5.4-1
Severity: grave
Justification: renders package unusable
After a glibc upgrade today, I cannot start postfix any more.
I first noticed that after reportbug syslog was strangely quiet,
and sudo mailq does say:
postqueue: warning: Mail system is down -- accessing qu
Control: tags 961811 + patch
Control: tags 961811 + pending
Dear maintainer,
I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru baresip-0.6.1/debian/changelog bar
Processing control commands:
> tags 961811 + patch
Bug #961811 [src:baresip] baresip FTBFS with make 4.3
Added tag(s) patch.
> tags 961811 + pending
Bug #961811 [src:baresip] baresip FTBFS with make 4.3
Added tag(s) pending.
--
961811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961811
Deb
Your message dated Wed, 15 Jul 2020 20:40:50 +
with message-id
and subject line Bug#963808: fixed in ruby-sanitize 4.6.6-2.1
has caused the Debian Bug report #963808,
regarding ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize
to be marked as done.
This means that you claim t
Your message dated Wed, 15 Jul 2020 19:04:28 +
with message-id
and subject line Bug#964666: fixed in libopenshot 0.2.5+dfsg1-3
has caused the Debian Bug report #964666,
regarding libopenshot: FTBFS: dh_missing: error: missing files, aborting
to be marked as done.
This means that you claim tha
Processing control commands:
> tag -1 pending
Bug #964666 [src:libopenshot] libopenshot: FTBFS: dh_missing: error: missing
files, aborting
Added tag(s) pending.
--
964666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Control: tag -1 pending
Hello,
Bug #964666 in libopenshot 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/multimedia-team/libopenshot/-/commit/43689f7b3b058dfd0
Your message dated Wed, 15 Jul 2020 18:47:03 +0100
with message-id
and subject line
has caused the Debian Bug report #925789,
regarding nsntrace: ftbfs with GCC-9
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 respons
Processing commands for cont...@bugs.debian.org:
> block 961195 with 965073
Bug #961195 [release.debian.org] transition: glibc
961195 was blocked by: 964227 964226 964220 964225 955368 964231 964223 964229
961195 was not blocking any bugs.
Added blocking bug(s) of 961195: 965073
> thanks
Stopping
Your message dated Wed, 15 Jul 2020 17:04:26 +
with message-id
and subject line Bug#964822: fixed in pandoc 2.9.1.1-1
has caused the Debian Bug report #964822,
regarding pandoc: BD-Uninstallable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Package: macs
Version: 2.2.7.1-2
Severity: serious
Tags: patch
macs use the log() math function, but doesn't link link with libm.so.
This causes the non-versioned __log_finite symbol to be used, which in
turn causes issues when glibc version is upgraded:
https://ci.debian.net/data/autopkgtest/tes
tags 964922 +pending
thanks
Thorsten Glaser writes:
> On Sun, 12 Jul 2020, Bdale Garbee wrote:
>
>> However, since your but report caused *me* to go read that and realize @
>> is now preferred to # for that directive, I'm updating the default
>> sudoers file for Debian to use @. Perhaps that wi
Processing commands for cont...@bugs.debian.org:
> tags 964922 +pending
Bug #964922 {Done: Bdale Garbee } [sudo] sudo: segmentation
fault when include directive is active in /etc/sudoers
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964922
Your message dated Wed, 15 Jul 2020 17:36:20 +0200
with message-id
and subject line gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared
has caused the Debian Bug report #921290,
regarding gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared
to be marked as done.
This means th
Processing commands for cont...@bugs.debian.org:
> fixed 921290 gnunet-gtk/1.13.1-1
Bug #921290 [src:gnunet-gtk] gnunet-gtk: FTBFS with gnutls 3.6:
'GNUTLS_CRT_RAW' undeclared
The source gnunet-gtk and version 1.13.1-1 do not appear to match any binary
packages
Marked as fixed in versions gnunet
On Sun, 12 Jul 2020, Bdale Garbee wrote:
> However, since your but report caused *me* to go read that and realize @
> is now preferred to # for that directive, I'm updating the default
> sudoers file for Debian to use @. Perhaps that will help reduce this
> particular form of confusion in the fut
Your message dated Wed, 15 Jul 2020 15:05:03 +
with message-id
and subject line Bug#964774: fixed in freetype 2.10.2+dfsg-3
has caused the Debian Bug report #964774,
regarding freetype: libfreetype6-udeb should not depend on non-udeb libbrotli1
to be marked as done.
This means that you claim
Your message dated Wed, 15 Jul 2020 15:07:04 +
with message-id
and subject line Bug#964643: fixed in sonic-visualiser 4.1-1
has caused the Debian Bug report #964643,
regarding sonic-visualiser: FTBFS: src/plugincandidates.cpp:235:13: error:
‘void QTime::start()’ is deprecated: Use QElapsedTim
Processing control commands:
> fixed -1 4.1-1
Bug #965067 [googler] googler: "No results"
Marked as fixed in versions googler/4.1-1.
--
965067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: googler
Version: 3.7.1-1
Severity: grave
Control: fixed -1 4.1-1
googler in buster seems completely broken.
I get "No results" every time.
--
Jakub Wilk
On Wed, Jul 15, 2020 at 02:40:39PM +0100, Dimitri John Ledkov wrote:
> • No instance for (MonadFail Action) arising from a use of ‘fail’
AFAIK (slightly out of the loop), this is because fail is not a part of
Monad any more
https://downloads.haskell.org/~ghc/8.8.1/docs/html/users_guide/8.
Processing commands for cont...@bugs.debian.org:
> severity 965001 serious
Bug #965001 [src:python-gmpy2] strange version 2.1.0 beta4 fails tests with
mpfr4 4.1.0
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
965001: http
Hi,
Thanks for maintaining ca-certificates.
I just wanted to let you know that a number of customers of $work are
affected by this, and we would very much welcome a return of the
GeoTrust Global CA.
It'd be nice if the uploaders of the ca-certificates could state what
they intend to do, so we co
Processing control commands:
> tag -1 pending
Bug #964774 [src:freetype] freetype: libfreetype6-udeb should not depend on
non-udeb libbrotli1
Ignoring request to alter tags of bug #964774 to the same tags previously set
--
964774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964774
Debian
Control: tag -1 pending
Hello,
Bug #964774 in freetype 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/debian/freetype/-/commit/59066db6afdd51052330ea906f89b9f4
control: tags -1 patch pending
Hello, I uploaded in deferred/5 the following debdiff (and submitted upstream)
Feel free to cancel/reschedule as you wish.
diff -Nru ibus-pinyin-1.5.0/debian/changelog ibus-pinyin-1.5.0/debian/changelog
--- ibus-pinyin-1.5.0/debian/changelog 2019-12-07 21:11:35.000
Processing control commands:
> tags -1 patch pending
Bug #964680 [src:ibus-pinyin] ibus-pinyin: FTBFS: lmyoslib.c:68:36: error:
expected ‘)’ before ‘LUA_QS’
Added tag(s) patch and pending.
--
964680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964680
Debian Bug Tracking System
Contact ow.
Processing commands for cont...@bugs.debian.org:
> severity 956354 important
Bug #956354 [libuser] libuser: Please stop using deprecated
and headers
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956354: https://bugs.
severity 956354 important
thanks
Well actually, selinux support is not enabled in libuser, so this is not
RC ATM
Package: src:guile-2.0
Version: 2.0.13+1-5.4
Severity: serious
Tags: sid bullseye
After fixing the build with make 4.3, the build then fails with a test failure.
Only seen on amd64, not on other architectures.
[...]
make check-TESTS
make[4]: Entering directory '/<>/guile-2.0-2.0.13+1'
Testing /<
Processing commands for cont...@bugs.debian.org:
> severity 950473 serious
Bug #950473 [src:openssh-ssh1] Please remove usage of hardcoded SELinux
security classes
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950473:
Processing commands for cont...@bugs.debian.org:
> severity 956354 serious
Bug #956354 [libuser] libuser: Please stop using deprecated
and headers
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956354: https://bugs.de
Processing commands for cont...@bugs.debian.org:
> severity 956355 serious
Bug #956355 [pam] pam: Please stop using deprecated and
headers
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956355: https://bugs.debian.org
Processing commands for cont...@bugs.debian.org:
> severity 964710 serious
Bug #964710 [src:abinit] abinit: FTBFS: /usr/bin/env: ‘python’: No such file or
directory
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964710: ht
Control: tag -1 pending
Hello,
Bug #964038 in rabbitmq-server 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/openstack-team/third-party/rabbitmq-server/-/commi
Processing control commands:
> tag -1 pending
Bug #964038 [rabbitmq-server] rabbitmq-server: Prometheus plugin doesn't
support Erlang v23
Added tag(s) pending.
--
964038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Your message dated Wed, 15 Jul 2020 07:48:29 +
with message-id
and subject line Bug#965050: fixed in flask-babel 0.12.2-1
has caused the Debian Bug report #965050,
regarding python3-flask-babel: flask_babel broken after recent werkzeug update
to be marked as done.
This means that you claim th
Control: tag -1 pending
Hello,
Bug #965050 in flask-babel 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/flask-babel/-/commit/a4e9ce6a08b73
Processing control commands:
> tag -1 pending
Bug #965050 [python3-flask-babel] python3-flask-babel: flask_babel broken after
recent werkzeug update
Added tag(s) pending.
--
965050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965050
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing commands for cont...@bugs.debian.org:
> severity 965050 serious
Bug #965050 [python3-flask-babel] python3-flask-babel: flask_babel broken after
recent werkzeug update
Severity set to 'serious' from 'normal'
> affects 965050 searx
Bug #965050 [python3-flask-babel] python3-flask-babel: f
Your message dated Wed, 15 Jul 2020 08:57:08 +0200
with message-id <20200715065708.ga3...@bogon.m.sigxcpu.org>
and subject line Re: Bug#960762: [Pkg-libvirt-maintainers] Bug#960762: libvirt:
random (?) test hangs
has caused the Debian Bug report #960762,
regarding libvirt: random (?) test hangs
to
75 matches
Mail list logo
