Bug#999567: severity

2022-02-03 Thread Alex Thiessen
that this bug is important to you or do you think it's so minor that it can be ignored? My colleagues are also bothered by the IT, but we can file an exception for this instead of building our own versions, and a rationale from you might be helpful to all of us. Have a nice day, Alex Thiessen

Bug#998054: libxstream-java: vulnerable to CVE-2021-391{{39..41},{44..54}}

2021-10-29 Thread Alex Thiessen
Package: libxstream-java Version: 1.4.15-3 Severity: important X-Debbugs-Cc: alex.thiessen.de+deb...@gmail.com Dear Maintainer, * What led up to the situation? Package installed, the machine scanned by the IT department and found vulnerable to a set of CVEs. According to

Bug#992444: make: Segmentation fault regression in make 4.3 vs. 4.2.1 (upstream bug 59093)

2021-08-18 Thread Alex Thiessen
Package: make Version: 4.3-4.1 Severity: important Tags: upstream X-Debbugs-Cc: alex.thiessen.de+deb...@gmail.com Dear Maintainer, * What led up to the situation? Using a "filter-out" function call in a makefile in context of buildroot. * What exactly did you do (or not do) that

Bug#959518: apt-transport-http: Repeatable 'Undetermined Error' during package download from snapshot.debian.org

2020-08-25 Thread Alex Thiessen
) - ‘openjdk-11-jdk-headless_11.0.3+7-5_amd64.deb’ saved [207236812/207236812] Best regards, Alex Thiessen

Bug#928119: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#928119: fixed in bumblebee 3.2.1-21)

2020-03-28 Thread Alex Thiessen
uIKiJBc0WUq2sEPpe > JMhRikfl+atCZtxysdj5FukAYYG+XlG7EnnNn/TB4eD8EVX5N8xIY23xQ3FAX2K7 > QPwQIr6sHvoMmalGhOjcZTPaTlYvi7egGgjrvqR1K3SKj/DoO3W4aTX8al2UvhgA > eAyi/0dlYHckvi6d+ZEYYo41m0MRgg8AkcD+xIefwM0pMqCuUGGZXLQBIe+yBTzD > xAO1HP5+ALClYvf29Ytgykc57bIbe9c21PNFOkP7FS+CRG1U11+OKC9RpAw4ZOOh

Bug#928119: bumblebee: Fails to install on a domain-joined machine

2019-04-28 Thread Alex Thiessen
Package: bumblebee Version: 3.2.1-14 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I have a notebook which is joined a (Windows) domain, as provided by my company's IT department. It