Bug#979312: Re: Bug#979312: vokoscreen-ng: Segmentation fault when screenAdded

reassign 979312 deepin-qt5dxcb-plugin 5.0.17-1 thanksSorry, wrong package name.

Bug#979312: Re: Bug#979312: vokoscreen-ng: Segmentation fault when screenAdded

reassign 979312 qt5dxcb-plugin 5.0.17-1 thanks Hi, I found it works fine after removing the qt5dxcb-plugin, so I reassign this to it. and the bt also shows it caused by deepin_platform_plugin: (gdb) bt #0 0x76e604e0 in QGuiApplication::screenAdded(QScreen*) () at

Bug#957265: marked as done (geekcode: ftbfs with GCC-10)

Your message dated Wed, 06 Jan 2021 07:33:25 + with message-id and subject line Bug#957265: fixed in geekcode 1.7.3-8 has caused the Debian Bug report #957265, regarding geekcode: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#943512: closing 943512

close 943512 thanks I just tested the build of the latest release (4.0.1+dfsg-2) on i386, and it appears to build ok. I'm closing the bug. Please re-open if you continue to see it fail on your end.

Processed: closing 943512

Processing commands for cont...@bugs.debian.org: > close 943512 Bug #943512 [src:notion] notion: FTBFS on i386 with test failure Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 943512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943512

Bug#979312: vokoscreen-ng: Segmentation fault when screenAdded

Hi handsome_feng, I did some tests on vokoscreen-ng and on a clean installation of debian sid the package worked perfectly. When did you specifically observe this segmantation fault? Could you give some more details so that I can reproduce the error? Regards === $

Bug#978377: marked as done (apertium-eo-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace))

Your message dated Wed, 06 Jan 2021 05:33:26 + with message-id and subject line Bug#978377: fixed in apertium-eo-fr 0.9.1-1 has caused the Debian Bug report #978377, regarding apertium-eo-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace) to be marked

Bug#957775: marked as done (sawfish: ftbfs with GCC-10)

Your message dated Wed, 06 Jan 2021 03:18:24 + with message-id and subject line Bug#957775: fixed in sawfish 1:1.11.90-1.2 has caused the Debian Bug report #957775, regarding sawfish: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#975677: marked as done (sawfish: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it)

Your message dated Wed, 06 Jan 2021 03:18:24 + with message-id and subject line Bug#975677: fixed in sawfish 1:1.11.90-1.2 has caused the Debian Bug report #975677, regarding sawfish: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it to be marked as done.

Bug#978478: marked as done (tegrarcm: upload required for libcrypto++ transition)

Your message dated Wed, 06 Jan 2021 00:20:03 + with message-id and subject line Bug#978478: fixed in tegrarcm 1.8-2 has caused the Debian Bug report #978478, regarding tegrarcm: upload required for libcrypto++ transition to be marked as done. This means that you claim that the problem has

Bug#979376: marked as done (CVE-2020-35681: potential leakage of session identifiers using legacy AsgiHandler)

Your message dated Tue, 05 Jan 2021 23:20:17 + with message-id and subject line Bug#979376: fixed in python-django-channels 3.0.3-1 has caused the Debian Bug report #979376, regarding CVE-2020-35681: potential leakage of session identifiers using legacy AsgiHandler to be marked as done.

Bug#979289: marked as done (libliberator-clojure: broken dependencies libdata.csv-clojure libdata.json-clojure)

Your message dated Tue, 05 Jan 2021 23:19:39 + with message-id and subject line Bug#979289: fixed in liberator-clojure 0.15.3-1 has caused the Debian Bug report #979289, regarding libliberator-clojure: broken dependencies libdata.csv-clojure libdata.json-clojure to be marked as done. This

Processed: Bug#979376 marked as pending in python-django-channels

Processing control commands: > tag -1 pending Bug #979376 [src:python-django-channels] CVE-2020-35681: potential leakage of session identifiers using legacy AsgiHandler Added tag(s) pending. -- 979376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979376 Debian Bug Tracking System Contact

Bug#979376: marked as pending in python-django-channels

Control: tag -1 pending Hello, Bug #979376 in python-django-channels 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:

Processed: bug 979377 is forwarded to https://github.com/Tlf/tlf/issues/210

Processing commands for cont...@bugs.debian.org: > forwarded 979377 https://github.com/Tlf/tlf/issues/210 Bug #979377 [src:tlf] tlf: FTBFS on mips*: test failures Set Bug forwarded-to-address to 'https://github.com/Tlf/tlf/issues/210'. > thanks Stopping processing here. Please contact me if you

Bug#979381: Useless in Debian

Package: php-db-dataobject Severity: serious X-Debbugs-Cc: Sunil Mohan Adapa , Rajasekhar Ponakala , Bhuvan Krishna Devabhaktuni Hi Sunil and other uploaders, As per #979156, I believe php-db-dataobject was introduced in Debian as part of the gnusocial packaging effort, but Sunil already

Processed: tagging 976997

Processing commands for cont...@bugs.debian.org: > tags 976997 - sid bullseye Bug #976997 [src:haproxy] haproxy: flaky ppc64el autopkgtest on ci.debian.net: 503 Service Unavailable Removed tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#979377: tlf: FTBFS on mips*: test failures

Source: tlf Version: 1.4.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org tlf fails to build on mips*: | |Tlf 1.4.1: test/test-suite.log |

Bug#979366: marked as done (openvswitch-common: openswitch-common uninstallable on non-amd64)

Your message dated Tue, 05 Jan 2021 21:48:58 + with message-id and subject line Bug#979366: fixed in openvswitch 2.13.0+dfsg1-15 has caused the Debian Bug report #979366, regarding openvswitch-common: openswitch-common uninstallable on non-amd64 to be marked as done. This means that you

Processed: Bug#979366 marked as pending in openvswitch

Processing control commands: > tag -1 pending Bug #979366 [openvswitch-common] openvswitch-common: openswitch-common uninstallable on non-amd64 Added tag(s) pending. -- 979366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979366 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#979366: marked as pending in openvswitch

Control: tag -1 pending Hello, Bug #979366 in openvswitch 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:

Bug#979376: CVE-2020-35681: potential leakage of session identifiers using legacy AsgiHandler

Source: python-django-channels Version: 3.0.2-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for python-django-channels. CVE-2020-35681[0]: | Potential leakage of

Processed: asterisk: CVE-2020-35652

Processing control commands: > found -1 1:16.2.1~dfsg-1+deb10u2 Bug #979372 [src:asterisk] asterisk: CVE-2020-35652 Marked as found in versions asterisk/1:16.2.1~dfsg-1+deb10u2. -- 979372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979372 Debian Bug Tracking System Contact

Bug#979372: asterisk: CVE-2020-35652

Source: asterisk Version: 1:16.15.0~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:16.2.1~dfsg-1+deb10u2 Hi, The following vulnerability was published for asterisk. Rationale: Choosed RC

Bug#950761: RFS: ipmitool/1.8.18-11 [RC] -- utility for IPMI control with kernel driver or LAN interface (daemon)

Hi Jörg, Thanks a lot for your work on this package! On Sun, Jan 03, 2021 at 05:21:42PM +0100, Jörg Frings-Fürst wrote: > tags 950761 - pending > thanks > > Hello Salvatore, > hello @All, > > > following a tip from Salvatore, I have added the missing commits. > Although these can be

Processed: affects 979366

Processing commands for cont...@bugs.debian.org: > affects 979366 netplan.io Bug #979366 [openvswitch-common] openvswitch-common: openswitch-common uninstallable on non-amd64 Added indication that 979366 affects netplan.io > thanks Stopping processing here. Please contact me if you need

Bug#975372: minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge

Hi Adam, hi Alexander, On Fri, Jan 01, 2021 at 06:20:32PM +, Adam D. Barratt wrote: > Hi, > > On Fri, 2021-01-01 at 14:21 +0100, Salvatore Bonaccorso wrote: > > Uplaoding 1.2.1+dfsg-1 + CVE fix cannot work. We have already > > released 1.2.1+dfsg-2+deb10u1 in the security archives, so any >

Bug#971216: doxygen build error

On Sat, Dec 19, 2020 at 11:29:36PM +0100, Sven Mueller wrote: > Could you imagine (no pun intended) to include the change in the > imagemagick version of the dh_doxygen script into the version in the > doxygen package, possibly behind an option? It replaces known (currently > only jquery) .js

Processed: found 975372 in 1.2.1+dfsg-2+deb10u1

Processing commands for cont...@bugs.debian.org: > found 975372 1.2.1+dfsg-2+deb10u1 Bug #975372 {Done: Alexander GQ Gerasiov } [src:minidlna] minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge Marked as found in versions minidlna/1.2.1+dfsg-2+deb10u1. > thanks Stopping

Bug#979366: openvswitch-common: openswitch-common uninstallable on non-amd64

Package: openvswitch-common Version: 2.13.0+dfsg1-13 Severity: grave Dear Maintainer, openswitch-common hardcodes x86_64-linux-gnu in its postinst, making it uninstallable on non-amd64: Setting up openvswitch-common (2.13.0+dfsg1-14) ... update-alternatives: using

Bug#979291: marked as done (xonsh autopkgtests fail with pytest 6)

Your message dated Tue, 05 Jan 2021 20:20:31 + with message-id and subject line Bug#979291: fixed in xonsh 0.9.24+dfsg-3 has caused the Debian Bug report #979291, regarding xonsh autopkgtests fail with pytest 6 to be marked as done. This means that you claim that the problem has been dealt

Bug#979364: nodejs: CVE-2020-8265 CVE-2020-8287

Source: nodejs Version: 12.19.0~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 10.21.0~dfsg-1~deb10u1 Control: found -1 14.13.0~dfsg-1 Hi, The following vulnerabilities were published for

Processed: nodejs: CVE-2020-8265 CVE-2020-8287

Processing control commands: > found -1 10.21.0~dfsg-1~deb10u1 Bug #979364 [src:nodejs] nodejs: CVE-2020-8265 CVE-2020-8287 Marked as found in versions nodejs/10.21.0~dfsg-1~deb10u1. > found -1 14.13.0~dfsg-1 Bug #979364 [src:nodejs] nodejs: CVE-2020-8265 CVE-2020-8287 Marked as found in versions

Processed: dovecot: CVE-2020-24386 CVE-2020-25275

Processing control commands: > found -1 1:2.3.4.1-5+deb10u4 Bug #979363 [src:dovecot] dovecot: CVE-2020-24386 CVE-2020-25275 Marked as found in versions dovecot/1:2.3.4.1-5+deb10u4. > fixed -1 1:2.3.4.1-5+deb10u5 Bug #979363 [src:dovecot] dovecot: CVE-2020-24386 CVE-2020-25275 Marked as fixed in

Bug#979363: dovecot: CVE-2020-24386 CVE-2020-25275

Source: dovecot Version: 1:2.3.11.3+dfsg1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:2.3.4.1-5+deb10u4 Control: fixed -1 1:2.3.4.1-5+deb10u5 Control: found -1 1:2.2.27-3+deb9u6 Control:

Bug#967123: debian-installer: Unversioned Python removal in sid/bullseye

Cyril Brulebois, le mar. 05 janv. 2021 20:28:52 +0100, a ecrit: > Matthias Klose (2020-08-04): > > Your package either build-depends, depends on one of those packages. > > I couldn't find any hit on “python” (that would be relevant) in current > git, current version, or the version you filed

Bug#979322: libcacard: missing runtime glib2.0 dependency?

05.01.2021 13:44, Gianfranco Costamagna wrote: ... after installing it looks still missing Package 'libpcsclite', required by 'libcacard', not found Oh. I missed this one. Will do another upload. /mjt

Bug#967123: marked as done (debian-installer: Unversioned Python removal in sid/bullseye)

Your message dated Tue, 5 Jan 2021 20:28:52 +0100 with message-id <20210105192852.w4f55x4yyqh6a...@mraw.org> and subject line Re: Bug#967123: debian-installer: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967123, regarding debian-installer: Unversioned Python

Bug#979361: tpm2-tss: FTBFS: missing BD on dh-pyhon

Source: tpm2-pkcs11 Version: 1.5.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org tpm2-pkcs11 fails to build: | debian/rules clean | dh clean --exclude=.la --exclude=.pc --with python3 | dh: error:

Bug#977604: smarty3: broken internal parsetree code

After encountering this problem today, what worked for me was to download v3.1.36 from GitHub and use that directly, instead of using the Debian package. So, I wonder, is the problem in the Debian packaging somehow?

Bug#976836: marked as done (libgnutls30: 3.7.0-3 fails to connect HTTPS servers which send the intermediate certificate twice)

Your message dated Tue, 5 Jan 2021 19:16:57 +0100 with message-id and subject line Re: Bug#976836: libgnutls30: 3.7.0-3 fails to connect on debian.ethz.ch has caused the Debian Bug report #976836, regarding libgnutls30: 3.7.0-3 fails to connect HTTPS servers which send the intermediate

Bug#979357: src:libloki: invalid maintainer address

Source: libloki Version: 0.1.7-3 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning

Bug#979322: marked as done (libcacard: missing runtime glib2.0 dependency?)

Your message dated Tue, 05 Jan 2021 18:21:23 + with message-id and subject line Bug#979322: fixed in libcacard 1:2.8.0-2 has caused the Debian Bug report #979322, regarding libcacard: missing runtime glib2.0 dependency? to be marked as done. This means that you claim that the problem has

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

Hi Sebastian, On 05-01-2021 10:46, Sebastian Dröge wrote: > On Mon, 28 Dec 2020 18:40:38 +0100 Paul Gevers wrote: >> >> If you believe your package is unable to migrate to testing due to >> issues beyond your control, don't hesitate to contact the Release Team. >> In this case, I think it may be

Bug#976472: marked as done (rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Tue, 5 Jan 2021 18:01:42 + with message-id <9cd43ac0-4924-73b6-5ac3-320afbf68...@p10link.net> and subject line re: rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 has caused the Debian Bug report #976472, regarding

Bug#979026: marked as done (r-cran-rgdal: autopkgtest failure with PROJ 7.2.1)

Your message dated Tue, 05 Jan 2021 17:52:30 + with message-id and subject line Bug#979026: fixed in r-cran-rgdal 1.5-18+dfsg-2 has caused the Debian Bug report #979026, regarding r-cran-rgdal: autopkgtest failure with PROJ 7.2.1 to be marked as done. This means that you claim that the

Bug#971297: python-oauth2client: Switch to python3-pycryptodome

On 2021-01-05 12:53:10 +0100, Thomas Goirand wrote: > On 12/30/20 11:21 AM, Sebastian Ramacher wrote: > > Hi Thomas > > > > FYI: you need to CC the submitter otherwise I don't see the mail. > > > > On 2020-11-22 12:41:29 +0100, Thomas Goirand wrote: > >> Hi Sebastian, > >> > >> Thanks for your

Bug#979329: marked as done (fastboot: Undeclared dependency on android-libunwind)

Your message dated Tue, 05 Jan 2021 17:48:43 + with message-id and subject line Bug#979329: fixed in android-platform-system-core 1:10.0.0+r36-4 has caused the Debian Bug report #979329, regarding fastboot: Undeclared dependency on android-libunwind to be marked as done. This means that you

Bug#976472: rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

Version: 0.3.3-6 Sorry forgot to close this bug in the changelog.

Bug#973621: marked as done (finit: file conflicts with other init systems)

Your message dated Tue, 05 Jan 2021 17:33:58 + with message-id and subject line Bug#973621: fixed in finit 3.2~rc3-2 has caused the Debian Bug report #973621, regarding finit: file conflicts with other init systems to be marked as done. This means that you claim that the problem has been

Bug#977953: marked as done (sigviewer FTBFS: .../libxdf.so: undefined reference to `pugi::...')

Your message dated Tue, 05 Jan 2021 16:48:44 + with message-id and subject line Bug#977953: fixed in libxdf 0.99.6+dfsg-3 has caused the Debian Bug report #977953, regarding sigviewer FTBFS: .../libxdf.so: undefined reference to `pugi::...' to be marked as done. This means that you claim

Bug#979322: libcacard: missing runtime glib2.0 dependency?

On Tue, 5 Jan 2021 15:40:42 +0300 Michael Tokarev wrote: > 05.01.2021 13:44, Gianfranco Costamagna wrote: > > Source: libcacard > > Version: 1:2.8.0-1 > > Severity: serious > > > > Hello, libglib2.0-dev looks missing on -dev package? > > > > pkg-config --short-errors --print-errors --cflags

Bug#979290: pytest-mpi autopkgtests fail with pytest 6

forwarded 979290 https://github.com/aragilar/pytest-mpi/issues/14 thanks There is a proposed fix in PR12, https://github.com/aragilar/pytest-mpi/pull/12

Processed: Re: Bug#979290: pytest-mpi autopkgtests fail with pytest 6

Processing commands for cont...@bugs.debian.org: > forwarded 979290 https://github.com/aragilar/pytest-mpi/issues/14 Bug #979290 [src:pytest-mpi] pytest-mpi autopkgtests fail with pytest 6 Set Bug forwarded-to-address to 'https://github.com/aragilar/pytest-mpi/issues/14'. > thanks Stopping

Processed: openmpi affects

Processing commands for cont...@bugs.debian.org: > affects 979041 + src:mpi4py Bug #979041 [libopenmpi3] libopempi3: aborts python code due to libfabric fork() issues Added indication that 979041 affects src:mpi4py > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#979300: sabnzbdplus autopkgtests fail with pytest 6

Control: tag 979300 + confirmed pending On Tue, 5 Jan 2021 00:17:12 +0100 Christian Kastner wrote: > sabnzbdplus autopkgtests fail with pytest 6 in unstable. The problem > seems to be the -k expression used to exclude particular tests: Thanks for your bug report. I already committed a fix [1]

Processed: haproxy not mpi4py

Processing commands for cont...@bugs.debian.org: > reassign 976997 src:haproxy 2.2.6-1 Bug #976997 [src:mpi4py] haproxy: flaky ppc64el autopkgtest on ci.debian.net: 503 Service Unavailable Bug reassigned from package 'src:mpi4py' to 'src:haproxy'. No longer marked as found in versions

Bug#979347: src:apt-venv: invalid maintainer address

Source: apt-venv Version: 1.0.0-2 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning

Bug#979345: src:maildirsync: invalid maintainer address

Source: maildirsync Version: 1.2-2 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning

Bug#975145: marked as done (ser-player: FTBFS: src/frame_slider.cpp:372:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

Your message dated Tue, 05 Jan 2021 15:39:11 + with message-id and subject line Bug#975145: fixed in ser-player 1.7.3-2 has caused the Debian Bug report #975145, regarding ser-player: FTBFS: src/frame_slider.cpp:372:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be

Bug#961814: marked as pending in golang-google-protobuf

Hi Anthony, On Tue, Jan 5, 2021 at 11:27 PM Anthony Fok wrote: > > Control: tag -1 pending > > Hello, > > Bug #961814 in golang-google-protobuf 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

Bug#961814: marked as done (Not ready for using)

Your message dated Tue, 05 Jan 2021 15:34:23 + with message-id and subject line Bug#961814: fixed in golang-google-protobuf 1.25.0+git20201208.160c747-1 has caused the Debian Bug report #961814, regarding Not ready for using to be marked as done. This means that you claim that the problem

Bug#979329: I think I have a fix

Control: tags -1 pending confirmed This is also confirmed by CI: https://salsa.debian.org/android-tools-team/android-platform-system-core/-/jobs/1310262 Testing a fix here: https://salsa.debian.org/eighthave/android-platform-system-core/-/jobs/1314158

Processed: I think I have a fix

Processing control commands: > tags -1 pending confirmed Bug #979329 [fastboot] fastboot: Undeclared dependency on android-libunwind Added tag(s) pending and confirmed. -- 979329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979329 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Bug#961814 marked as pending in golang-google-protobuf

Processing control commands: > tag -1 pending Bug #961814 [golang-google-protobuf] Not ready for using Added tag(s) pending. -- 961814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#961814: marked as pending in golang-google-protobuf

Control: tag -1 pending Hello, Bug #961814 in golang-google-protobuf 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:

Processed: severity of 973599 is serious

Processing commands for cont...@bugs.debian.org: > severity 973599 serious Bug #973599 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers-legacy-340xx: EoL driver should not be released with bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here.

Bug#979344: nvidia-graphics-drivers-tesla-440: EoL driver should not be released with bullseye

Source: nvidia-graphics-drivers-tesla-440 Severity: serious The tesla-440 series was a "New Feature Branch" and reached EoL in November 2020. It does not provide any features over the tesla-450 driver (which is a "Long Term Service Branch" supported until July 2023).

Bug#979219: 關於 Debian 中 moblin 的老套件.

移除吧，根本没人用了 On Tue, Jan 5, 2021 at 6:10 PM Ying-Chun Liu (PaulLiu) wrote: > Hi 侯總, > > 好久不見.. 近來可好?? > > 我這邊收到幾個 Debian 的 bug. > > > moblin-cursor-theme > > https://bugs.debian.org/979219 > > > moblin-icon-theme > >

Bug#975741: marked as done (tpm2-pkcs11: FTBFS: build-dependency not installable: libtss2-esys0 (>= 2.0))

Your message dated Tue, 05 Jan 2021 14:10:19 + with message-id and subject line Bug#975741: fixed in tpm2-pkcs11 1.5.0-1 has caused the Debian Bug report #975741, regarding tpm2-pkcs11: FTBFS: build-dependency not installable: libtss2-esys0 (>= 2.0) to be marked as done. This means that you

Processed: notfound 974975 in 0.2-1, fixed 974975 in 0.2-1, tagging 975819

Processing commands for cont...@bugs.debian.org: > notfound 974975 0.2-1 Bug #974975 {Done: Sudip Mukherjee } [src:libbpf] libbpf: please upload to buster-backports No longer marked as found in versions libbpf/0.2-1. > fixed 974975 0.2-1 Bug #974975 {Done: Sudip Mukherjee } [src:libbpf] libbpf:

Bug#977502: podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz

Hi Reinhard, Thanks for reaching out! I just returned from the Christmas break. I will defer the answer to Dan who moved the man page to c/common. Dan, where do you want the mounts.conf to live in the future? Given the change is comparatively young, I assume that no package is using it at the

Processed: tagging 979325, tagging 979244, tagging 979246, tagging 978371, tagging 979283 ..., affects 979085

Processing commands for cont...@bugs.debian.org: > tags 979325 + sid bullseye Bug #979325 [src:abicheck] src:abicheck: invalid maintainer address; maintainer gone? Added tag(s) sid and bullseye. > tags 979244 + sid bullseye Bug #979244 [src:moblin-sound-theme] src:moblin-sound-theme: invalid

Processed: For version tracking, assign 896426 to source package

Processing commands for cont...@bugs.debian.org: > reassign 896426 src:brian Bug #896426 {Done: Andreas Tille } [python-brian] python-brian: brian fails to import Bug reassigned from package 'python-brian' to 'src:brian'. No longer marked as found in versions brian/1.4.3-1. No longer marked as

Bug#979220: marked as done (src:tourney-manager: invalid maintainer address)

Your message dated Tue, 05 Jan 2021 13:20:31 + with message-id and subject line Bug#979220: fixed in tourney-manager 20070820-5 has caused the Debian Bug report #979220, regarding src:tourney-manager: invalid maintainer address to be marked as done. This means that you claim that the problem

Processed: found 974797 in 1.5-6, bug 975931 is not forwarded

Processing commands for cont...@bugs.debian.org: > found 974797 1.5-6 Bug #974797 [pocl] pocl: Please upgrade to llvm-toolchain-11 Bug #974823 [pocl] pocl: Please upgrade to llvm-toolchain-11 There is no source info for the package 'pocl' at version '1.5-6' with architecture '' Unable to make a

Processed: reassign 979322 to libcacard-dev, found 979322 in 1:2.5.0-1a

Processing commands for cont...@bugs.debian.org: > reassign 979322 libcacard-dev Bug #979322 [src:libcacard] libcacard: missing runtime glib2.0 dependency? Bug reassigned from package 'src:libcacard' to 'libcacard-dev'. No longer marked as found in versions libcacard/1:2.8.0-1. Ignoring request

Bug#979314: libccp4: The endianness check in ccp4_sysdep.h is incorrect assuming powerpc is always big endian

Source: libccp4 Version: 6.5.1-4 Severity: grave Tags: patch upstream Justification: renders package unusable X-Debbugs-Cc: maar...@hekkelman.com -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel:

Bug#979334: Useless in Debian

Source: magpierss Severity: serious X-Debbugs-Cc: Marcelo Jorge Vieira [ Reported by a team member to see the package removed from testing ] Hi Marcelo, It looks like libphp-magpierss isn’t used by anything in Debian currently, that upstream is inactive for fifteen years, and that alternatives

Processed: Re: python3-venv is gone

Processing commands for cont...@bugs.debian.org: > severity 970808 normal Bug #970808 [thonny] python3-venv is gone Severity set to 'normal' from 'serious' > tags 970808 moreinfo unreproducible Bug #970808 [thonny] python3-venv is gone Added tag(s) unreproducible and moreinfo. > End of message,

Processed: Re: sigviewer FTBFS: .../libxdf.so: undefined reference to `pugi::...'

Processing control commands: > reassign -1 src:libxdf libxdf/0.99.6+dfsg-1 Bug #977953 [src:sigviewer] sigviewer FTBFS: .../libxdf.so: undefined reference to `pugi::...' Bug reassigned from package 'src:sigviewer' to 'src:libxdf'. No longer marked as found in versions sigviewer/0.6.4-1. Ignoring

Bug#977953: sigviewer FTBFS: .../libxdf.so: undefined reference to `pugi::...'

Control: reassign -1 src:libxdf libxdf/0.99.6+dfsg-1 Control: affects -1 src:sigviewer Control: tag -1 patch On Wed, 23 Dec 2020 10:51:30 +0100 Helmut Grohne wrote: > Source: sigviewer > Version: 0.6.4-1 > Severity: serious > Tags: ftbfs > > sigviewer fails to build from source in unstable. A

Bug#979322: libcacard: missing runtime glib2.0 dependency?

05.01.2021 13:44, Gianfranco Costamagna wrote: Source: libcacard Version: 1:2.8.0-1 Severity: serious Hello, libglib2.0-dev looks missing on -dev package? pkg-config --short-errors --print-errors --cflags --libs "libcacard >= 2.5.1" Package 'glib-2.0', required by 'libcacard', not found I

Bug#979329: fastboot: Undeclared dependency on android-libunwind

Package: fastboot Version: 1:10.0.0+r36-3 Severity: grave Justification: renders package unusable $ fastboot fastboot: error while loading shared libraries: lib7z.so: cannot open shared object file: No such file or directory This file is provided only by package android-libunwind, but fastboot

Processed: Re: Bug#979300: sabnzbdplus autopkgtests fail with pytest 6

Processing control commands: > tag 979300 + confirmed pending Bug #979300 [src:sabnzbdplus] sabnzbdplus autopkgtests fail with pytest 6 Added tag(s) confirmed and pending. -- 979300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979300 Debian Bug Tracking System Contact

Bug#979314: marked as done (libccp4: The endianness check in ccp4_sysdep.h is incorrect assuming powerpc is always big endian)

Your message dated Tue, 05 Jan 2021 12:04:46 + with message-id and subject line Bug#979314: fixed in libccp4 6.5.1-5 has caused the Debian Bug report #979314, regarding libccp4: The endianness check in ccp4_sysdep.h is incorrect assuming powerpc is always big endian to be marked as done.

Bug#971297: python-oauth2client: Switch to python3-pycryptodome

On 12/30/20 11:21 AM, Sebastian Ramacher wrote: > Hi Thomas > > FYI: you need to CC the submitter otherwise I don't see the mail. > > On 2020-11-22 12:41:29 +0100, Thomas Goirand wrote: >> Hi Sebastian, >> >> Thanks for your bug report, and sorry it took that long to address. >> >> In many of

Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1

FYI, deleting the user's config under ~/.config, ~/.local/share and ~/.cache fixes the issue and geary starts successfully after that. Of course that is a disruptive operation (user config is gone, and what about pop accounts that cannot resync emails later on). I can probably reproduce the

Bug#979325: src:abicheck: invalid maintainer address; maintainer gone?

Source: abicheck Version: 1.2-5 Severity: serious X-Debbugs-Cc: m...@qa.debian.org, Holger Levsen The maintainer address seamus@d.o forwards to a non-working address, see below. The maintainer doesn't seem to have been active since 2009 and their key was removed from the keyring in 2015 (1024

Bug#964658: marked as done (liblxqt: FTBFS: lxqtpowermanager.cpp:99:27: error: ‘QFile’ has not been declared)

Your message dated Tue, 05 Jan 2021 11:03:35 + with message-id and subject line Bug#964658: fixed in liblxqt 0.16.0-1 has caused the Debian Bug report #964658, regarding liblxqt: FTBFS: lxqtpowermanager.cpp:99:27: error: ‘QFile’ has not been declared to be marked as done. This means that

Bug#979322: libcacard: missing runtime glib2.0 dependency?

Source: libcacard Version: 1:2.8.0-1 Severity: serious Hello, libglib2.0-dev looks missing on -dev package? pkg-config --short-errors --print-errors --cflags --libs "libcacard >= 2.5.1" Package 'glib-2.0', required by 'libcacard', not found after installing it looks still missing Package

Bug#979219: 關於 Debian 中 moblin 的老套件.

Hi 侯總, 好久不見.. 近來可好?? 我這邊收到幾個 Debian 的 bug. moblin-cursor-theme https://bugs.debian.org/979219 moblin-icon-theme https://bugs.debian.org/979223 moblin-sound-theme

Bug#979232: lighttpd: does not start with media-types 1.1.0

Package: lighttpd Version: 1.4.57-1 Followup-For: Bug #979232 X-Debbugs-Cc: pitsior...@gmail.com I have that one too! Downgrading media-types to 1.0.1 from testing fixes the issue, so I am pinning it until the next lighttpd update. Thank you both. -- System Information: Debian Release:

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

On Mon, 28 Dec 2020 18:40:38 +0100 Paul Gevers wrote: > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > In this case, I think it may be wise to upload to > testing-proposed-updates and ask for an

Processed: python-crypto removal

Processing commands for cont...@bugs.debian.org: > severity 971297 serious Bug #971297 [src:python-oauth2client] python-oauth2client: Switch to python3-pycryptodome Severity set to 'serious' from 'important' > severity 971291 serious Bug #971291 [src:salutatoi] salutatoi: Switch to

Bug#971296: python-crypto removal

severity 971297 serious severity 971291 serious severity 971308 serious severity 971299 serious severity 971289 serious severity 971311 serious severity 971309 serious thanks Dear maintainers, the freeze is coming closer and I've filed the removal bug for python-crypto (#979318) and raised the

Processed: RM: python-crypto -- ROM; unmaintained upstream, replaced by pycryptodome

Processing control commands: > block -1 by 971297 971296 971291 971308 971299 971289 971311 971309 Bug #979318 [ftp.debian.org] RM: python-crypto -- ROM; unmaintained upstream, replaced by pycryptodome 979318 was not blocked by any bugs. 979318 was not blocking any bugs. Added blocking bug(s) of

Processed: closing 979085

Processing commands for cont...@bugs.debian.org: > close 979085 4.1.0-4 Bug #979085 [openmpi] FTBFS on mips64el There is no source info for the package 'openmpi' at version '4.1.0-4' with architecture '' Unable to make a source version for version '4.1.0-4' Marked as fixed in versions 4.1.0-4.

Bug#979243: marked as done (FTBFS: rust-cpp-demangle - obsolete dep on rust-if-cfg-0.1-dev)

Your message dated Tue, 5 Jan 2021 09:56:50 +0100 with message-id and subject line Re: [Pkg-rust-maintainers] Bug#979243: FTBFS: rust-cpp-demangle - obsolete dep on rust-if-cfg-0.1-dev has caused the Debian Bug report #979243, regarding FTBFS: rust-cpp-demangle - obsolete dep on

Bug#979243: [Pkg-rust-maintainers] Bug#979243: FTBFS: rust-cpp-demangle - obsolete dep on rust-if-cfg-0.1-dev

Hi Peter. Odd. We are rebuilding packages in debian testing, but for some unknown reason (I'm still looking into it), the rust-cfg-if-0.1 source package was not considered. After manually adding it, everything works fine, thanks for the hint. Cheers, Sven Am Mo., 4. Jan. 2021 um 18:34 Uhr

  1   2   >