Processing commands for cont...@bugs.debian.org:
> tags 985376 + upstream
Bug #985376 {Done: Valentin Vidic } [crmsh] CVE-2020-35459
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
985376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
Processing commands for cont...@bugs.debian.org:
> found 985376 4.2.1-1
Bug #985376 {Done: Valentin Vidic } [crmsh] CVE-2020-35459
Marked as found in versions crmsh/4.2.1-1.
> found 985376 4.0.0~git20190108.3d56538-3
Bug #985376 {Done: Valentin Vidic } [crmsh] CVE-2020-35459
Marked as found in ver
Your message dated Sun, 21 Mar 2021 18:48:23 -0700
with message-id
and subject line Re: Bug#985675: plover 4.0.0~dev8~66~g685bd33-2 is missing
Conflicts/Replaces plover-common 3.0.0-1
has caused the Debian Bug report #985675,
regarding plover 4.0.0~dev8~66~g685bd33-2 is missing Conflicts/Replaces
Processing commands for cont...@bugs.debian.org:
> found 857522 1:9.11.19+dfsg-2
Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks:
/usr/lib/x86_64-linux-gnu/liblwres-export.so ->
/lib/x86_64-linux-gnu/liblwres-export.so.141,
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.
On March 21, 2021 1:06:29 PM PDT, Harlan Lieberman-Berg
wrote:
>tag 985675 +moreinfo
>thanks
>
>On Sun, Mar 21, 2021 at 3:39 PM Don Armstrong wrote:
>> plover-common 3.0.0-1 and plover 4.0.0~dev8~66~g685bd33-2 both ship
>> /usr/share/plover/assets/american_english_words.txt, but the latter
>is
>
On Sun, Mar 21, 2021 at 7:04 PM Don Armstrong wrote:
> Hrm. It was maintained by you, but there's a non-zero chance I installed it
> directly from source. If it's never been uploaded, that's probably what
> happened.
Iiiinteresting. The plover repo that I've been working out of has
3.1.1 as t
Hi Aurelien,
On 21-03-2021 00:03, Aurelien Jarno wrote:
> Yes, could you please provide a full log? I am not able to reproduce the
> issue locally nor on barriere.d.o, so I have no idea what fails.
Of course when you try to, it doesn't work. I had 5 runs on arm64 which
all succeeded. I'm wonderin
Your message dated Sun, 21 Mar 2021 21:03:29 +
with message-id
and subject line Bug#985376: fixed in crmsh 4.2.1-2
has caused the Debian Bug report #985376,
regarding CVE-2020-35459
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Processing commands for cont...@bugs.debian.org:
> tag 985675 +moreinfo
Bug #985675 [plover] plover 4.0.0~dev8~66~g685bd33-2 is missing
Conflicts/Replaces plover-common 3.0.0-1
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
985675: https:/
tag 985675 +moreinfo
thanks
On Sun, Mar 21, 2021 at 3:39 PM Don Armstrong wrote:
> plover-common 3.0.0-1 and plover 4.0.0~dev8~66~g685bd33-2 both ship
> /usr/share/plover/assets/american_english_words.txt, but the latter is
> missing the appropriate Conflicts/Replaces.
Hi Don,
Where have you in
Your message dated Sun, 21 Mar 2021 19:48:37 +
with message-id
and subject line Bug#975711: fixed in sks 1.1.6+git20210302.c3ba6d5a-2
has caused the Debian Bug report #975711,
regarding sks: autopkgtest failure since git snapshot update
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 985670 + upstream
Bug #985670 [ceph] CVE-2020-27781 CVE-2020-27839
Added tag(s) upstream.
> tags 985671 + upstream
Bug #985671 [src:cgal] CVE-2020-35636 CVE-2020-35628 CVE-2020-28636
CVE-2020-28601
Added tag(s) upstream.
> tags 985673 + upst
Package: plover
Severity: serious
Version: 4.0.0~dev8~66~g685bd33-2
Preparing to unpack .../2-plover_4.0.0~dev8~66~g685bd33-2_all.deb ...
Unpacking plover (4.0.0~dev8~66~g685bd33-2) over (3.0.0-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-P6rk1s/2-plover_4.0.0~dev8~66~g685bd33-2_al
Processing commands for cont...@bugs.debian.org:
> severity 985632 important
Bug #985632 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] RPi4B 5GHz
WiFi stopped working with 20210208-4, 20201218-3 was fine
Severity set to 'important' from 'grave'
> tags 985632 moreinfo
Bug #985632 [firmware
severity 985632 important
tags 985632 moreinfo
stop
On Sun, Mar 21, 2021 at 09:59:45AM +0900, Ryutaroh Matsumoto wrote:
> Package: firmware-brcm80211
> Version: 20210208-4
> Severity: grave
> Tags: sid bullseye
> Justification: renders package unusable
please provide info on the affected hardware
Source: cgal
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team
CVE-2020-35636
https://talosintelligence.com/vulnerability_reports/TALOS-2020-1225
CVE-2020-35628
https://talosintelligence.com/vulnerability_reports/TALOS-2020-1225
CVE-2020-28636
https://talosintelligence.c
wf...@niif.hu writes:
> Andreas Beckmann writes:
>
>> According to policy 7.2 you cannot rely on the depends being available
>> during purge, only the essential packages are available for sure.
>
> I can't see coturn rely on any of its dependencies during purge, do you?
Hi Andreas,
Have you got
Package: voltron
Version: 0.1.7+git20200109-1
Followup-For: Bug #983702
Dear Maintainer,
I am attaching a patch.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.11.0 (SMP w/8 CPU threads)
Kern
On Sat, 20 Mar 2021 12:29:56 -0400 Jerome Charaoui
wrote:
> user debian-rele...@lists.debian.org
> usertags 985543 + bsp-2021-03-ca-montreal
> tag 985543 + unreproducible moreinfo
> thank you
>
> Hello,
>
> I've attempted, but was unable, to reprodu
Hi,
First of all thank you for your afford!
I successfully managed to unlock my LUKS partition by generating
the response on a different machine (with package 'ykpersonalize'
using the command 'ykchalresp') and typing it manually. the system
Package: progress-linux-server
Version: 20210101-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
with --install-recommends enabled. (It installed fine with
--install-recommends disabled.) Apt does not
Hi Jerome,
On Sat, 2021-03-20 at 12:29 -0400, Jerome Charaoui wrote:
> I've attempted, but was unable, to reproduce this bug.
>
> I set up the yubikey-luks challenge-response on a fresh stretch system,
> and after upgrading to bullseye, it was working as before, which
> suggests the package is
Hi Daniel,
On Sun, 2021-03-21 at 13:52 +0200, Daniel Hevron Pereh wrote:
> I successfully managed to unlock my LUKS partition by generating the response
> on a different machine (with package 'ykpersonalize' using the command
> 'ykchalresp') and typing it manually. the system was updated as I thou
Processing control commands:
> tags -1 pending
Bug #985512 [liblingot-dev] liblingot-dev: broken symlink:
/usr/lib/x86_64-linux-gnu/liblingot.so -> liblingot.so.0.0.0
Added tag(s) pending.
--
985512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985512
Debian Bug Tracking System
Contact ow.
Package: liblingot-dev
Followup-For: Bug #985512
Control: tags -1 pending
The VCS contains a trivial fix.
https://salsa.debian.org/debian/lingot/-/commit/5ef26d260e2f6858e3226223290e052237b92e00
Processing control commands:
> retitle -1 flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds
Bug #985556 [src:flatpak] flatpak/1.2.5-0+deb10u4 FTBFS on i386
Changed Bug title to 'flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds' from
'flatpak/1.2.5-0+deb10u4 FTBFS on i386'.
> reassign -1 glib2.
Control: retitle -1 flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds
Control: reassign -1 glib2.0 2.50.0-1
Control: affects -1 + flatpak
Control: severity -1 important
Control: close -1 2.63.1-1
On Sun, 21 Mar 2021 at 12:15:15 +0100, Philipp Kern wrote:
> I have commented out stretch and buster
Your message dated Sun, 21 Mar 2021 12:18:28 +
with message-id
and subject line Bug#985585: fixed in cura 4.8-4
has caused the Debian Bug report #985585,
regarding cura: TypeError when saving materials or printing
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tag 973474 -unreproducible -moreinfo
Bug #973474 [gnome] gnome: Unable to log back in in after screen lock
Removed tag(s) unreproducible.
Bug #973474 [gnome] gnome: Unable to log back in in after screen lock
Removed tag(s) moreinfo.
> thanks
Stopp
tag 973474 -unreproducible -moreinfo
thanks
I think now that I have provided the requested information and we know how
to reproduce the bug, and have a rough idea what the issue is, we can
remove these tags.
Marcin
Processing commands for cont...@bugs.debian.org:
> severity 985585 serious
Bug #985585 [cura] cura: TypeError when saving materials or printing
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
985585: https://bugs.debian.org/
On 20.03.21 13:32, Simon McVittie wrote:
> On Sat, 20 Mar 2021 at 09:16:45 +0100, Salvatore Bonaccorso wrote:
>> On Sat, Mar 20, 2021 at 12:12:39AM +, Simon McVittie wrote:
>>> Could x86-conova-01.debian.org be an IPv6-only buildd?
> ...
>>> Or, if not that, could it be the case that this build
Your message dated Sun, 21 Mar 2021 11:03:25 +
with message-id
and subject line Bug#985607: fixed in gtkglext 1.2.0-11
has caused the Debian Bug report #985607,
regarding pkg-config --libs gdkglext-1.0 misses -lpangox-1.0
to be marked as done.
This means that you claim that the problem has be
Your message dated Sun, 21 Mar 2021 10:18:22 +
with message-id
and subject line Bug#985286: fixed in ocaml-batteries 3.1.0-2
has caused the Debian Bug report #985286,
regarding libbatteries-ocaml-doc: unhandled symlink to directory conversion:
/usr/share/doc/libbatteries-ocaml-dev/examples ->
Processing control commands:
> tag -1 pending
Bug #985286 [libbatteries-ocaml-doc] libbatteries-ocaml-doc: unhandled symlink
to directory conversion: /usr/share/doc/libbatteries-ocaml-dev/examples ->
../libbatteries-ocaml-doc/examples
Added tag(s) pending.
--
985286: https://bugs.debian.org/cg
Control: tag -1 pending
Hello,
Bug #985286 in ocaml-batteries 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/ocaml-team/ocaml-batteries/-/commit/728f2e4d94eb62
Your message dated Sun, 21 Mar 2021 09:48:28 +
with message-id
and subject line Bug#985392: fixed in r-cran-shiny 1.5.0+dfsg-2
has caused the Debian Bug report #985392,
regarding r-cran-shiny: broken symlinks:
/usr/lib/R/site-library/shiny/www/shared/font-awesome/fonts/fontawesome-webfont.*
t
Awesome, thank you for the confirmation. I've rolled out the
announcement and published the website update.
Thanks, everyone! \o/
- u
38 matches
Mail list logo
