Bug#1003298: vim-gtk3: Wrong colors and font in terminal in 2:8.2.3995-1

On Sunday, January 9th, 2022 at 8:05 AM, James McCoy wrote: > There were a couple of issues in Vim that led to this change in > > behavior, due to wanting the terminal running Vim's normal colors to be > > used if Vim's highlight groups didn't specify any colors. > > -

Bug#934926: [Pkg-zsh-devel] Bug#934926: update (overridding of default fpath causes uncessary complexity and pain for software providing zsh completions)

Hi Daniel, Daniel Shahaf wrote: > That's not to say that things can't be improved going forward. The big question to me seems "how?". > […], or /etc/zsh/zshrc.d/ could be added (there's a separate ticket > for that but my quick grep didn't find it), You probably had

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/9/22 00:56, Andres Salomon wrote: On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland

Bug#1003298: vim-gtk3: Wrong colors and font in terminal in 2:8.2.3995-1

On Sun, Jan 09, 2022 at 03:47:40AM +, Håvard Moen wrote: > On Sunday, January 9th, 2022 at 2:30 AM, James McCoy > wrote: > > > > Some more details about how things differ would be useful. Maybe even > > > > > screen shots. > > Attaching screenshots showing the difference. I also see

Bug#1003378: More data for Bug 1003378

I tried again. This time, I did $ aptitude install kde-standard and then tried adding the same .mp4 file to Kdenlive's project bin. Kdenlive didn't crash this time, but it 1.) openned an orange error window that says "Cannot open file

Bug#813771: reportbug: It can't unselect item in 'Do any of the following apply to this report' page.

Dear Nis Martensen, I registered my account to salsa. And I implemented all your requests shown below, > > - Is it possible to more clearly highlight the selected row(s)? Some > > of > > the menus can be quite long with a lot of text, and the radiobutton > > or > > checkbox is relatively

Bug#1003138: Some related links

A related/similar post on Windows is https://stackoverflow.com/questions/44153858/linking-against-boost-python-3-6-cant-find-boost-python-instead-of-boost-pytho As I had set using python 3.9, but ld will always tried to link libboost_python instead of libboost_python3.9 I also checked the header

Bug#1003380: ITP: golang-github-goccy-go-yaml -- yet another golang library for YAML support

Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: golang-github-goccy-go-yaml Version : 1.9.4 Upstream Author : Masaaki Goshima * URL : https://github.com/goccy/go-yaml * License : Expat Programming Lang: Go Description : yet

Bug#1003379: last-align: reproducible-builds: cpu-specific features embedded in manpages

Source: last-align Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: cpu X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Various manpages embed the relevent SIMD variant of the CPU used in the build environment:

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland automatically, in case that's related to

Bug#1001979: ITS: libxml-tokeparser-perl

Source: libxml-tokeparser-perl Followup-For: Bug #1001979 X-Debbugs-Cc: Nathan Scott Dear Maintainer, libxml-tokeparser-perl (0.05-4) has been uploaded to unstable (DELAYED/7) to fix #999272 per the Package Salvaging process:

Bug#1000336: Upgrading tbb

Hi Mo, thanks a lot. I asked on IRC for priorisation of this package. Kind regards Andreas. Am Sat, Jan 08, 2022 at 08:30:57PM -0500 schrieb M. Zhou: > Hi all, > > The good news is that I managed to upgrade onetbb. It  > is in the NEW queue now: >

Bug#934926: update

Joey Hess wrote on Sat, Jan 08, 2022 at 16:27:53 -0400: > The simple fact is that as an upstream author who used the debian > locations because they were the ones that worked on my system, I get bug > reports from users of other systems that it's not right for wider uses > of zsh. And Debian seems

Bug#1003378: QFSFileEngine::open: No file name specified...

Package: kdenlive Version: 21.12.1-1 Severity: important Hi Padrick, Thank you for maintaining Debian's kdenlive package. It can be a lot of fun! I seem to have found a bug after upgrading to version 21.12.1-1. I ran kdenlive on the command line user$ kdenlive & then followed the menu

Bug#1003160:

as an update to the report above, I since noticed that this issue also occurs if I try to boot from the 5.10.0-10 kernel instead of the original 5.10.0-09

Bug#1003377: getmail6: Ignores netrc_file configuration settings

Package: getmail6 Version: 6.18.4-2 Severity: normal X-Debbugs-Cc: Olaf Meeuwissen Dear Maintainer, I tried moving my credentials to $HOME/.authinfo by setting use_netrc = true netrc_file = $HOME/.authinfo and removing the username and password from a working configuration file. That

Bug#1003376: ITP: python-circuitbreaker -- Python "Circuit Breaker" implementation

Package: wnpp Severity: wishlist Owner: Paul Wise X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org Control: block 1003372 by -1 * Package name: python-circuitbreaker Version : 1.3.2 Upstream Author : Fabian Fuelling * URL :

Bug#1003375: clfft: reproducible-builds: BuildId differences triggered by RPATH

Source: clfft Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid:

Bug#1003374: ITP: golang-github-aquasecurity-go-version -- A Go library for parsing and verifying versions and version constraints.

Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: golang-github-aquasecurity-go-version Version : 0.0~git20210121.637058c Upstream Author : Aqua Security * URL : https://github.com/aquasecurity/go-version * License : Apache-2.0

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

> I am eager to revert mistune (and therefore django-hyperkitty) back to > previous versions, and to open bugs against reverse deps, with new > uploads in experimental for both mistune and django-hyperkitty. this would be great indeed, thanks! > I consider a delay between bug opening and making

Bug#1003373: go-for-it: reproducible-builds: BuildId differences triggered by RPATH

Source: go-for-it Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid:

Bug#1003372: ITP: oci-python-sdk -- Oracle Cloud Infrastructure Python SDK

Package: wnpp Severity: wishlist Owner: Paul Wise X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org * Package name: oci-python-sdk Version : 2.53.1 Upstream Author : Vyas Bhagwat and others * URL : https://github.com/oracle/oci-python-sdk/ *

Bug#1003371: libavif: reproducible-builds: BuildId differences triggered by RPATH

Source: libavif Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid:

Bug#1003370: libxtrxll: reproducible-builds: BuildId differences triggered by RPATH

Source: libxtrxll Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid:

Bug#1003313: [pkg-gnupg-maint] Bug#1003313: libgpg-error FTCBFS for musl: refuses to use generic lock object detection

Control: forwarded 1003313 https://dev.gnupg.org/T5762 On Sat 2022-01-08 01:15:16 +0100, Helmut Grohne wrote: > A while ago, libgpg-error gained a feature that enabled configure to > introspect lock objects without running code (via objdump). > Unfortunately, this code is only used for glibc.

Bug#1003298: vim-gtk3: Wrong colors and font in terminal in 2:8.2.3995-1

Control: found -1 2:8.2.3995-1 Control: notfound -1 2:8.2.2434-3+deb11u1 On Fri, Jan 07, 2022 at 07:30:35PM +0100, Håvard Moen wrote: > I upgraded vim-gtk3 to version 2:8.2.3995-1 that is in unstable, but > noticed that the colors and font in the terminal (:terminal) is not > set from my

Bug#1000336: Upgrading tbb

Hi all, The good news is that I managed to upgrade onetbb. It  is in the NEW queue now: https://ftp-master.debian.org/new/onetbb_2021.4.0-1~exp1.html All changes have been pushed onto salsa (master branch). SOVERSION was bumped from 2 to 12 so NEW is inevitable. There are also some non-trivial

Bug#993857: [pkg-gnupg-maint] Bug#993857: Bug#993857: gnupg2: Please remove librsvg2-bin from BD

On Sat 2022-01-08 21:39:25 +0100, Laurent Bigonville wrote: > My understanding of the policy has always been that the source tarball > shipped in debian must indeed contain all the files in their "preferred > form of modification" but the fact that the resulting artifact has to be > rebuilt

Bug#998426: man reports a "malformed .lf request"

Control: tag -1 fixed-upstream On Thu, Nov 04, 2021 at 12:45:59AM +, Bjarni Ingi Gislason wrote: >* What led up to the situation? > > man -l groff/contrib/gpinyin/gpinyin.1.man (or groff/build/contrib/...) > >* What was the outcome of this action? > > /usr/bin/man: -:250: warning:

Bug#1001577: m17n-lib: internal vs external symbols

Hi Boyuan, On 14/12/21 21:47, Boyuan Yang wrote: I wasn't aware of the issue around internal & external symbols. Sorry for the issue! Since the change was made back in 2018, I could not recall my exact thought when I made those changes. Please feel free to correct the symbol file. Done. The

Bug#971009: man-db: bad documentation for $MANROFFSEQ

On Sat, Sep 26, 2020 at 09:33:20AM +0200, Jakub Wilk wrote: > The man(1) man page reads: "Firstly, the command line option -p or the > environment variable $MANROFFSEQ is interrogated. If -p was not used and the > environment variable was not set, the initial line of the nroff file is > parsed for

Bug#1003368: dino-im: reproducible-builds: BuildId differences triggered by RPATH

Source: dino-im Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid:

Bug#970482: "lexgrog" uses UTF-8 encoding in its output, not "locale"

Control: tag -1 fixed-upstream On Thu, Sep 17, 2020 at 02:58:30AM +, Bjarni Ingi Gislason wrote: >* What exactly did you do (or not do) that was effective (or > ineffective)? > > lexgrog -d /usr/share/man/man7/groff_me.7.gz [...] >* What outcome did you expect instead? > >

Bug#996328: further information

debian bug 996328: I have been testing video playback and browser graphics/ javascript (?) issues on Debian 9, 10, and 11 with Xfce on two computers: 1. Dell Latitude E6520 with Intel i7-2720QM processor (Intel HD Graphics 3000) and NVIDIA NVS 4200M (NVIDIA Optimus). 2. Tower desktop

Bug#1003259: firejail should blacklist rxvt when Perl is blacklisted

Control: tags -1 fixed-upstream On 2022-01-07 03:57:46 +0100, Vincent Lefevre wrote: > I've submitted a pull request upstream. The corresponding patch: > https://github.com/netblue30/firejail/pull/4831/commits/ed5c259fcc106b8b07f056f65e828c680fec9562 This has been merged. -- Vincent Lefèvre -

Bug#1003367: upgrade-reports: samba seriously broken after upgrade - major config changes

Package: upgrade-reports Severity: important (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) My previous release is: buster I am upgrading to: bullseye Upgrade date: Jan 06 2021 uname -a after upgrade:

Bug#951354: wget2: Please package new version (1.99.2)

X-Debbugs-CC: n...@debian.org Dear maintainer, It has been a while; is there any update on packaging new wget2? If you are in lack of time doing packaging, please let us know so that those interested can have a chance to step in. Thanks, Boyuan Yang On Fri, 15 Oct 2021 16:34:47 -0400 Boyuan

Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable

On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that

Bug#1003366: reportbug: open-iscsi-udeb : iscsid unable to start. Missing libsystemd.so.0 in installer environment

Package: open-iscsi Version: 2.1.3-5 Severity: important Tags: d-i -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU

Bug#900253: nslcd: disabling ppolicy breaks authentication

On Sat, 2022-01-08 at 20:19 +0100, Nicolas Peugnet wrote: > I just ran into this bug. If I understand correctly it should have > been fixed by this commit: > > which is in Debian since version

Bug#1003365: projectm-pulseaudio: Doesn't work on Thinkpad T410 with Iron Lake GPU

Package: projectm-pulseaudio Version: 3.1.12-1 Severity: normal Dear Maintainer, as I tried to startup a projectM-session with my oldy laptop, I got that output from command-line: projectM-pulseaudio Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use

Bug#1003364: RM: python-asynctest -- RoQA; Orphaned; Unused; Upstream Inactive; RC-Buggy

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove Dear FTP Masters, As discussed in https://bugs.debian.org/954554 , this package is orphaned, RC- buggy (FTBFS) and no longer needed. Please consider removing python-asynctest from Debian archive.

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: > If you want to try with chromium 97; it now builds as an official build, so > those DCHECKs shouldn't even be compiled in. It also supports wayland > automatically, in case that's related to your slowdowns. > >

Bug#954554: python-asynctest: FTBFS, maybe-RM

X-Debbugs-CC: jo...@jones.dk andrew.shad...@collabora.co.uk Hi, I just checked the condition in Debian Sid, and it looks like no package still depends or build-depends on package python3-asynctest. As a result, I am going to submit a RM bug to have this package removed soon. Thanks, Boyuan

Bug#1002962: recode: Please switch to upstream as redirected by GNU

Hi, 在 2022-01-04星期二的 22:59 +，Reuben Thomas写道： > On Tue, 4 Jan 2022 at 22:09, Santiago Vila wrote: > > > > Working on it now. > > Great! > > > (I'm curious: In which way is this bug different than #961136, also > > reported by you?) > > Looks to me like the sort of memory failure I am

Bug#1003363: installation-reports: Cubietruck installation - No USB

Package: installation-reports Boot method: MMC Image version: https://deb.debian.org/debian/dists/stable/main/installer-armhf/current/ images/netboot/SD-card-images/ Date: 05.01.2022 Machine: Cubietruck Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =

Bug#1003362: Git repository no longer updated

Source: isc-dhcp Version: 4.4.1-2.3 According to https://packages.debian.org/source/sid/isc-dhcp the Git repository of the package is on Salsa. However, looking at the repository, it has been inactive for more than 2 years and the latest patches are not part of it. See:

Bug#970721: xom: new releases available

Hi Andrius, On Sat, Jan 08, 2022 at 09:58:18AM +0200, Andrius Merkys wrote: > > * diffoscope_198: not enough disk space to rebuild locally, will look > > for another machine. > > Does not fail with xom_1.3.7+ds-2. I was also able to build diffoscope_199 successfully with xom 1.3.7:

Bug#1003339: findutils: find manpage definition of "-delete" misses that it can delete directories

On 08/01/2022 17:41, Andreas Metzler wrote: Given that manpage and info are part of the upstream release I have submitted a suggested patch to sync the wording. Thank you. Appreciated smime.p7s Description: S/MIME Cryptographic Signature

Bug#1002850: journalctl -f for SD card in USB adapter.

From bi...@debian.org, Sat, 8 Jan 2022 20;29:23 +0100, Are you sure you have a custom udev rules file in /etc/udev/rules.d? Oops, 10-local.rules is attached but the preceding exercise was misguided, inadvertently of course. With reference to /dev/disk/by-label/GRNSD in /etc/fstab, the

Bug#976811: [pkg-php-pear] Bug#976811: Bug#976811: transition: php8.1

Hi, Le 08/01/2022 à 17:38, Paul Gevers a écrit : On 01-01-2022 14:20, Ondřej Surý wrote: […] I also see some autopkgtest regressions which have this (eg. [1, 2]): """ PHPUnit requires the "dom" extension. """ where should that get fixed? There are several php7.4-* packages pulled in those

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

Jonas Smedegaard wrote on 22/12/2021 at 23:52:11+0100: > [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at > 2021-12-22T23:52:06+0100 using RSA]] > Quoting Pierre-Elliott Bécue (2021-12-22 21:42:41) >> >> Jonas Smedegaard wrote on 22/12/2021 at 21:55:13+0100: >> >> > [[PGP

Bug#976811: [pkg-php-pear] Bug#976811: transition: php8.1

Hi, Back from holidays. On 01-01-2022 14:20, Ondřej Surý wrote: Some rebuilds failed, e.g. php-horde-lz4 [6], The FTBFS is unrelated to PHP 8.1 transition php-wmerrors [7], owfs [8]. These two need upstream update. I see no activity and no bug reports. Can somebody please update these

Bug#996997: marked as done (buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster"))

[ Thanks for pinging ] Adam D. Barratt wrote... > How does this sound as text for an SUA? To me, it seems worth a idea describing the impact a bit more in detail, so ... > " > http-parser is a parser for HTTP messages, designed to be used in high > performance HTTP applications. > > The

Bug#993857: [pkg-gnupg-maint] Bug#993857: Bug#993857: gnupg2: Please remove librsvg2-bin from BD

Daniel Kahn Gillmor wrote... > So the debian-generated image is both more policy-compliant and more > correct. We shouldn't stop building it from source. Quite frankly, I don't think even it's necessary to stress the policy here, shipping a "more correct" PNG should be motivation enough. And it

Bug#1003352: Acknowledgement (mdadm: Intel RST RAID not detected because /sys/firmware/efi/efivars wasn't mount)

So the same issue was fixed in Arch Linux by explicitly mounting efivars inside initramfs: - https://bugs.archlinux.org/task/52768 - https://github.com/archlinux/mkinitcpio/commit/70511e5ccb7e2500213e04173a70c067a7c9aa35 Maybe the issue should be transferred to Debian's counterpart

Bug#811294: ITP: tabview -- curses command-line CSV and list (tabular data) viewer

On 2022-01-08 07 h 41, Yuri D'Elia wrote: > I'd be glad if you could take over on the packaging I'm currently not planning to, as tabview is only an optional dependency of a package I'm maintaining because it's a build-dep for another package that is a build-dep of a package I care about :) --

Bug#993620: vip-manager: test failure with some network configurations

Control: severity -1 serious Hi, On Fri, 3 Sep 2021 12:17:10 -0600 Dan Bungert wrote: vip-manager behavior_test can fail, depending on the device network configuration. If the test device has a network device of type ether and a zero hardware address, and it selects this network device as

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Fri, Jan 07, 2022 at 06:34:06AM -0300, Leandro Cunha wrote: > > > I also haven't heard from anyone on the chromium team yet - should I > > > add myself as an uploader and do a normal (non-NMU) upload? Do any of > > > them care? > > > > Without hearing from them, adding yourself to Uploaders

Bug#1001668: downgrading severity

Control: severity -1 serious Hi Gordon, On Fri, 7 Jan 2022 15:50:43 + Gordon Ball wrote: Reducing severity to `normal`, since this does not appear to happen consistently. Looking through the CI logs, there are occasional failures on ppc64el, but since it does not appear to happen

Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation

Hello, D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:47:17 -0500, a ecrit: > Here's the files from the Buster installation from /var/log/installer - > attached. Ok, thanks! So the "ALC888: SKU not ready 0x0100" message was already there at the time. What's new in bullseye is snd_hda_intel

Bug#1003361: ITP: mlyacc-polyml -- LALR parser generator for Standard ML

Package: wnpp Severity: wishlist Owner: Ryan Kavanagh X-Debbugs-Cc: debian-de...@lists.debian.org, r...@debian.org * Package name: mlyacc-polyml Version : x.y.z Upstream Author : Name * URL : https://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.)

Bug#1003360: golang-github-satori-go.uuid: Remove prior to bookworm release

Source: golang-github-satori-go.uuid Version: 1.2.0-2 Severity: important Tags: bookworm The upstream project github.com/satori/go.uuid appears to be dead, and the community seems to be migrating to github.com/gofrs/uuid, which is a maintained fork of that library. github.com/gofrs/uuid is

Bug#1003359: golang-github-dgrijalva-jwt-go: Remove prior to bookworm release

Source: golang-github-dgrijalva-jwt-go Version: 3.2.0-3 Severity: important Tags: bookworm The upstream project github.com/dgrijalva/jwt-go is no longer maintained, and users are being instructed to switch to github.com/golang-jwt/jwt. github.com/golang-jwt/jwt has just recently been packaged

Bug#993857: [pkg-gnupg-maint] Bug#993857: Bug#993857: gnupg2: Please remove librsvg2-bin from BD

On 8/01/22 20:04, Daniel Kahn Gillmor wrote: Control: reopen 993857 Control: retitle 993857 gnupg2: gnupg-module-overview.png is not built from source On Wed 2021-12-15 23:40:23 +0100, Christoph Biedl wrote: Control: tags 993857 pending Laurent Bigonville wrote... Could you please drop

Bug#934926: update

The simple fact is that as an upstream author who used the debian locations because they were the ones that worked on my system, I get bug reports from users of other systems that it's not right for wider uses of zsh. And Debian seems to be leaving it up to me to deal with it, which just makes me

Bug#1000152:

Hi, Bug #1002697 and #1000152 are duplicates of #1003355 which I just filed, with an upstream fix and salsa PR at https://salsa.debian.org/debian/cyrus-sasl2/-/merge_requests/8 Ubuntu jammy (devel release) has the same issue and it boils down to SPNEGO being disabled accidentally in the

Bug#1003358: ITP: mllex-polyml -- lexical analyzer generator for Standard ML

Package: wnpp Severity: wishlist Owner: Ryan Kavanagh X-Debbugs-Cc: debian-de...@lists.debian.org, r...@debian.org * Package name: mllex-polyml Upstream Author : Takayuki Goto * URL : https://github.com/eldesh/mllex-polyml * License : Apache and HPND Programming Lang:

Bug#1002326: python-schema-salad: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13]

Control: blocked -1 by 1001591 - Weitergeleitete Nachricht von Sandro Tosi - Date: Fri, 7 Jan 2022 21:01:30 -0500 From: Sandro Tosi To: Andreas Tille , 1002...@bugs.debian.org Cc: "Michael R. Crusoe" Subject: Re: Bug#1002326: python-schema-salad: FTBFS: dh_auto_test: error: pybuild

Bug#1002709: webext-ublock-origin-firefox: ublock-origin makes firefox-esr 91 consumes 100% of a CPU core

On Thu, 06 Jan 2022 17:27:13 +0100 Markus Koschany wrote: > It seems this issue is fixed in Firefox 95 > but the fix has not been backported to > Firefox ESR yet. Let's wait for an update. For reference, here is the bug against firefox-esr:

Bug#1003357: src:view3dscene: fails to migrate to testing for too long: FTBFS on armel

Source: view3dscene Version: 3.18.0-4 Severity: serious Control: close -1 4.0.0-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1002961 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#999249: Package will now be considered for auto-removal

Hello! On 1/8/22 20:35, Graham Inggs wrote: > The release team no longer [1] considers popcon a criterion for > inclusion in the list of key packages [2]. > > This email is a courtesy reminder of this bug, and should prevent > instant auto-removal once the rule is changed in britney. discover

Bug#1003356: fontconfig-config: fonts-conf(5) man page: undocumented

Package: fontconfig-config Version: 2.13.1-4.2 Severity: minor In the fonts-conf(5) man page: Alias elements provide a shorthand notation for the set of common match operations needed to substitute one font family for another. They contain a element followed by

Bug#1003355: cyrus-sasl2: GSS-SPNEGO not detected with autoconf 2.71

Package: cyrus-sasl2 Version: 2.1.27+dfsg2-2 Dear Maintainer, with autoconf 2.71, there is an undetected error in the ./configure run that results in GSS-SPNEGO being disabled: >From >https://buildd.debian.org/status/fetch.php?pkg=cyrus-sasl2=amd64=2.1.27%2Bdfsg2-2=1637264771=0: ... checking

Bug#1003354: src:jupyter-client: fails to migrate to testing for too long: autopkgtest regression

Source: jupyter-client Version: 6.1.12-1 Severity: serious Control: close -1 7.1.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1000271 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1003353: lintian: Cannot use brackets in suppression rules?

Package: lintian Version: 2.114.123 Severity: normal Hello, Seeing that qa.debian.org is using version 2.114.123 of lintian, I upgraded my lintian from its git tree, only to find that it seems I cannot update my suppression rule according to the new output: W: libbrlapi-dev: bad-whatis-entry

Bug#1003352: mdadm: Intel RST RAID not detected because /sys/firmware/efi/efivars wasn't mount

Package: mdadm Version: 4.2~rc2-7 Severity: normal X-Debbugs-Cc: cuihao@gmail.com Dear Maintainer, I installed Debian bullseye on a Intel RST (also known as IMSM/PCH RAID) RAID 1 volume. The system couldn't boot itself because the RAID volume which the rootfs is on wasn't detected. I am

Bug#1000681: linux-image-5.15.0-1-amd64: 5.15 upgrade causes all apps to flicker

Source: linux Source-Version: 5.16~rc8-1~exp1 On Sat, Jan 08, 2022 at 06:15:16PM +0100, Stefan Fritsch wrote: > > On 09.12.21 23:14, Stefan Fritsch wrote: > > There is discussion and a fix for this issue at > > > > https://lists.freedesktop.org/archives/nouveau/2021-December/039597.html > >

Bug#1003351: Update package to upstream version 5.0 (patches provided)

Source: libunibreak Version: 1.1-2.1 Severity: wishlist Tags: patch Dear Maintainer, while there aren't any known grave issues with the packaged version 1.1, released 2013, this is severely lagging behind upstream's newest version 5.0 released in late 2021. Upgrading to 5.0 brings the benefit of

Bug#1002521: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#999730: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#1002360: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#1002143: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#1002192: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#1001841: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#1000896: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#999249: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#999037: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#998999: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#998516: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997763: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997652: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997601: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997406: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997367: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997287: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#997194: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#993882: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#993716: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

Bug#993350: Package will now be considered for auto-removal

Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1]

  1   2   >