Processed: Re: Bug#983807: spring builds with -march=native on amd64

Processing control commands: > severity -1 serious Bug #983807 {Done: Markus Koschany } [src:spring] spring builds with -march=native on amd64 Severity set to 'serious' from 'normal' -- 983807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983807 Debian Bug Tracking System Contact

Bug#983829: marked as done (tk-doc: copyright file missing (policy 12.5))

Your message dated Tue, 02 Mar 2021 07:33:47 + with message-id and subject line Bug#983829: fixed in tcltk-defaults 8.6.11+1 has caused the Debian Bug report #983829, regarding tk-doc: copyright file missing (policy 12.5) to be marked as done. This means that you claim that the problem has

Bug#983825: marked as done (python3-gevent: copyright file missing (policy 12.5))

Your message dated Tue, 02 Mar 2021 06:48:36 + with message-id and subject line Bug#983825: fixed in python-gevent 20.9.0-2 has caused the Debian Bug report #983825, regarding python3-gevent: copyright file missing (policy 12.5) to be marked as done. This means that you claim that the

Bug#983829: [Pkg-tcltk-devel] Bug#983829: tk-doc: copyright file missing (policy 12.5)

Hi Andreas, On Tue, Mar 2, 2021 at 4:54 AM Andreas Beckmann wrote: > > Hi, > > a test with piuparts revealed that your package misses the copyright > file, which is a violation of Policy 12.5: > https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information > > From the attached log

Bug#983381: marked as done (openzwave-controlpanel: FTBFS in sid)

Your message dated Tue, 02 Mar 2021 06:33:37 + with message-id and subject line Bug#983381: fixed in openzwave-controlpanel 0.2a+git20161006.a390f35-2.2 has caused the Debian Bug report #983381, regarding openzwave-controlpanel: FTBFS in sid to be marked as done. This means that you claim

Bug#980935: marked as done (pyzo: Crash at startup with python3.9)

Your message dated Tue, 02 Mar 2021 06:33:48 + with message-id and subject line Bug#980935: fixed in pyzo 4.11.2-1 has caused the Debian Bug report #980935, regarding pyzo: Crash at startup with python3.9 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#983829: tk-doc: copyright file missing (policy 12.5)

Package: tk-doc Version: 8.6.11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

Bug#983828: libseqan3-dev: copyright file missing (policy 12.5)

Package: libseqan3-dev Version: 3.0.2+ds-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5:

Bug#983827: python3-lmfit: copyright file missing (policy 12.5)

Package: python3-lmfit Version: 1.0.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5:

Bug#983825: python3-gevent: copyright file missing (policy 12.5)

Package: python3-gevent Version: 20.9.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5:

Bug#973474: gnome: Unable to log back in in after screen lock

On Mon, 01 Mar 2021 at 22:48:47 +0100, Marcin Owsiany wrote: > I installed from debian-bullseye-DI-alpha3-amd64-netinst.iso in virt-manager > VM > with 2 VCPUs and 4GB of RAM. > Other than selecting Polish locale and installing ssh server and all possible > display managers and window

Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module

Package: src:linux Version: 5.10.13-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, When booting recent kernels on a RockPro64 board (rk3399), eth0 often fails to come up, leaving this headless box practically unusable without serial console intervention. Logging

Processed: Re: Bug#983807: spring builds with -march=native on amd64

Processing control commands: > severity -1 normal Bug #983807 [src:spring] spring builds with -march=native on amd64 Severity set to 'normal' from 'serious' -- 983807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#983807: spring builds with -march=native on amd64

Control: severity -1 normal Am Dienstag, den 02.03.2021, 01:32 +0200 schrieb Adrian Bunk: [...] > > I would really like to understand what the current drawback is for our > > users. > > If you could provide the build flags with march=native and march=x86-64 and > > then prove that march=x86-64

Processed: Re: Bug#983807: spring builds with -march=native on amd64

Processing control commands: > severity -1 serious Bug #983807 [src:spring] spring builds with -march=native on amd64 Severity set to 'serious' from 'normal' -- 983807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983807 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#983815: python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on armhf if built on 64bit hardware

Source: python-crc32c Version: 2.2-1 Severity: serious Tags: ftbfs patch For the FTBFS: https://buildd.debian.org/status/logs.php?pkg=python-crc32c=armhf Fix is attached. Description: Fix baseline violations on x86 and arm These extensions are not part of the baseline of any port. Author:

Processed: Re: Bug#983807: spring builds with -march=native on amd64

Processing control commands: > severity -1 normal Bug #983807 [src:spring] spring builds with -march=native on amd64 Severity set to 'normal' from 'serious' -- 983807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#983807: spring builds with -march=native on amd64

Control: severity -1 normal Am Dienstag, den 02.03.2021, 01:02 +0200 schrieb Adrian Bunk: > On Mon, Mar 01, 2021 at 11:39:00PM +0100, Markus Koschany wrote: > > Am Montag, den 01.03.2021, 23:53 +0200 schrieb Adrian Bunk: > > > Source: spring > > > Version: 105.0.1+dfsg-1 > > > Severity: serious >

Bug#983807: spring builds with -march=native on amd64

On Mon, Mar 01, 2021 at 11:39:00PM +0100, Markus Koschany wrote: > Am Montag, den 01.03.2021, 23:53 +0200 schrieb Adrian Bunk: > > Source: spring > > Version: 105.0.1+dfsg-1 > > Severity: serious > > Tags: patch > > > > spring builds with -march=native on amd64, which makes spring > > only work

Bug#983807: spring builds with -march=native on amd64

Am Montag, den 01.03.2021, 23:53 +0200 schrieb Adrian Bunk: > Source: spring > Version: 105.0.1+dfsg-1 > Severity: serious > Tags: patch > > spring builds with -march=native on amd64, which makes spring > only work on machines compatible with whatever buildd built it. What Policy violation

Bug#957553: marked as done (mmh: ftbfs with GCC-10)

Your message dated Mon, 01 Mar 2021 22:19:32 + with message-id and subject line Bug#957553: fixed in mmh 0.4-4 has caused the Debian Bug report #957553, regarding mmh: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#983786: affects to bullseye too

Source: courier Version: 1.0.14-2 Severity: serious hi markus.. sorry but this bug also affected freeze released bulleye.. but noted that the commit is a changelog only entry.. so i asked to SAM https://sourceforge.net/p/courier/mailman/courier-users/?viewmonth=202103=1 so this bug is closed

Bug#983365: linphone-desktop: chat messages

I haven't found the bug yet, but at least somewhat cornered in linphone-desktop/linphone-app/src/components/chat/ChatModel.cpp in ChatModel::setSipAddress(): ... for (auto : mChatRoom->getHistory(0)) mEntries << qMakePair( QVariantMap{ { "type", EntryType::MessageEntry },

Bug#983807: spring builds with -march=native on amd64

Source: spring Version: 105.0.1+dfsg-1 Severity: serious Tags: patch spring builds with -march=native on amd64, which makes spring only work on machines compatible with whatever buildd built it. Fix: --- debian/rules.old2021-03-01 21:06:07.743433910 + +++ debian/rules2021-03-01

Bug#973474: gnome: Unable to log back in in after screen lock

Hello again, sob., 27 lut 2021 o 22:28 Simon McVittie napisał(a): > (and then after pressing Enter > for my test user's password, I'm back to my unlocked session, equivalent > to ). At what point does > what

Bug#983183: Aw: Bug#983183: Acknowledgement (libpam-script: Wrong path for pam_script.so)

Dear Martijn, as I saw at TDO libpam-script is now marked for autoremoval. This is the last thing I intended and the proper solution seems obvious to me.   Is there anything I can do to keep libpam-script in Debian 11?   Thanks a lot Christian Meyer  

Processed: found 945506 in 1.8.6-5, user debian...@lists.debian.org, usertagging 983382, affects 983382 ...

Processing commands for cont...@bugs.debian.org: > found 945506 1.8.6-5 Bug #945506 [openafs-modules-dkms] openafs-modules-dkms: module wants to build with gcc instead of kernel's compiler Marked as found in versions openafs/1.8.6-5. > user debian...@lists.debian.org Setting user to

Processed: closing 982693

Processing commands for cont...@bugs.debian.org: > close 982693 Bug #982693 [src:siconos] siconos: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test "ARGS=-E 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest'" ARGS\+=-j1 returned exit code 2 Marked Bug as done >

Bug#983786: marked as done (fix crash caused by a malformed DNS query/response.)

Your message dated Mon, 01 Mar 2021 20:33:40 + with message-id and subject line Bug#983786: fixed in courier 1.0.16-1 has caused the Debian Bug report #983786, regarding fix crash caused by a malformed DNS query/response. to be marked as done. This means that you claim that the problem has

Bug#983478: marked as done (courier: Please revert the fam -> gamin change for bullseye)

Your message dated Mon, 01 Mar 2021 20:33:40 + with message-id and subject line Bug#983478: fixed in courier 1.0.16-1 has caused the Debian Bug report #983478, regarding courier: Please revert the fam -> gamin change for bullseye to be marked as done. This means that you claim that the

Bug#983764: /usr/share/chipcard/cards/README missing

Hi Micha, thanks for your super-quick response. On Mon, Mar 01, 2021 at 02:57:31PM +0100, Micha Lenk wrote: > When removing that apparently bogus file, I didn't expect it to break the > chipcard-tool binary. What a weird dependency... Indeed, it is a very big surprise to me that the code would

Processed: Re: Bug#983763: package unconditionally b-d's on libreoffice-writer

Processing control commands: > severity -1 important Bug #983763 [src:gpredict] package unconditionally b-d's on libreoffice-writer Severity set to 'important' from 'serious' -- 983763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983763 Debian Bug Tracking System Contact

Bug#983763: package unconditionally b-d's on libreoffice-writer

Control: severity -1 important Re: Matthias Klose > Package: src:gpredict > Version: 2.3-72-gc596101-3 > Severity: serious > Tags: sid bullseye > > package unconditionally b-d's on libreoffice-writer, not available on all > platforms, prohibiting migration to testing. This is not true, the

Bug#983793: grc needs a source-only upload for testing migration

Source: grc Version: 1.12-1 Severity: serious https://tracker.debian.org/pkg/grc Migration status for grc (1.11.3-1.1 to 1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: Not built on buildd: arch all binaries uploaded by garabik, a new

Bug#941624: Recommending ibus breaks fcitx

On Tue, Mar 2, 2021 at 3:26 AM Andreas Henriksson wrote: > > Hello Shengjing Zhu, > > (FYI I've not been part of pkg-gnome maintenance for the better part of > bullseye development cycle and don't speak for pkg-gnome team, but I > feel this is not a new issue and hopefully my input can hopefully

Bug#941624: Recommending ibus breaks fcitx

On Tue, Mar 2, 2021 at 3:26 AM Andreas Henriksson wrote: > > Hello Shengjing Zhu, > > (FYI I've not been part of pkg-gnome maintenance for the better part of > bullseye development cycle and don't speak for pkg-gnome team, but I > feel this is not a new issue and hopefully my input can hopefully

Bug#983238: marked as done (libbio-db-biofetch-perl: test failure if internet available)

Your message dated Mon, 01 Mar 2021 19:49:16 + with message-id and subject line Bug#983238: fixed in libbio-db-biofetch-perl 1.7.3-4 has caused the Debian Bug report #983238, regarding libbio-db-biofetch-perl: test failure if internet available to be marked as done. This means that you claim

Bug#983777: libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4)

On 3/1/21 8:26 PM, Andreas Beckmann wrote: > Just don't forget B+R: libgnunet0.14 > if libgnunet0.15 gets uploaded some day ... ;-) jep :) Thanks, Daniel

Bug#983723: marked as done (rna-star FTBFS on ppc64el due to -march=native)

Your message dated Mon, 01 Mar 2021 19:34:35 + with message-id and subject line Bug#983723: fixed in rna-star 2.7.8a+dfsg-2 has caused the Debian Bug report #983723, regarding rna-star FTBFS on ppc64el due to -march=native to be marked as done. This means that you claim that the problem has

Bug#983478: some hints to take in consideration

> Incorrect information was given in #981513: > - the release team has now decided that fam will stay in bullseye, > it is expected that fam will be removed for bookworm that's true.. some ports need fam cos gamin is linux only.. and remenber that debian it build for others kernel/archs

Bug#983727: thinkfan should not ship an example in /etc/thinkfan.yaml

found 983727 1.2.1-1 thanks Hey David! Thanks for the report. On February 28, 2021 9:29:54 PM UTC, "David Prévot" wrote: >Package: thinkfan >Version: 1.2.1-3 >Severity: serious > >The “thinkfan Example Config File” currently shipped as >/etc/thinkfan.yaml “is NOT a working config file that can

Processed: Re: Bug#983727: thinkfan should not ship an example in /etc/thinkfan.yaml

Processing commands for cont...@bugs.debian.org: > found 983727 1.2.1-1 Bug #983727 [thinkfan] thinkfan should not ship an example in /etc/thinkfan.yaml Ignoring request to alter found versions of bug #983727 to the same values previously set > thanks Stopping processing here. Please contact me

Bug#983777: libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4)

On 01/03/2021 19.42, Daniel Baumann wrote: On 3/1/21 6:33 PM, Andreas Beckmann wrote: IMO only the /usr/lib/* part belongs into libgnunet0.14, the remaining ones should have stayed in gnunet. the idea here is that the stuff in libgnunet0.14 is used by the If it's intentional, that is fine.

Bug#983786: fix crash caused by a malformed DNS query/response.

Source: courier Version: 1.0.15-1 Severity: serious already upstream in Fixes a crash caused by a malformed DNS query/response. in details: backporting this: https://github.com/svarshavchik/courier/commit/91b3f7ca6c38c9b56c93484f8687c99d6c62c091 -- Lenz McKAY Gerardo (PICCORO)

Bug#983365: Info received (Bug#983365: linphone-desktop: chat messages)

Hello, Thanks all for having worked on this. Sorry for the little delay in answering, I actually thought the packages would 'find their way' to bullseye, so I was (and still am) updating daily, a few times per day actually, but now I see you said sid, not bullseye ... > an updated liblinphone

Bug#983777: marked as done (libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4))

Your message dated Mon, 01 Mar 2021 19:18:32 + with message-id and subject line Bug#983777: fixed in gnunet 0.14.0-5 has caused the Debian Bug report #983777, regarding libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4) to be marked as done. This means that you claim that the

Bug#982795: marked as done (neat: autopkgtest failure on several architectures)

Your message dated Mon, 01 Mar 2021 19:18:42 + with message-id and subject line Bug#982795: fixed in neat 2.3.2-2 has caused the Debian Bug report #982795, regarding neat: autopkgtest failure on several architectures to be marked as done. This means that you claim that the problem has been

Bug#941624: Recommending ibus breaks fcitx

Hello Shengjing Zhu, (FYI I've not been part of pkg-gnome maintenance for the better part of bullseye development cycle and don't speak for pkg-gnome team, but I feel this is not a new issue and hopefully my input can hopefully help shed some light on the situation at hand...) First let me be

Bug#983785: wims-lti: fails to install: post-installation script subprocess returned error exit status 2

Package: wims-lti Version: 0.4.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the

Bug#983784: obs-api: fails to install: Could not find gem 'data_migrate (= 5.3.1)'

Package: obs-api Version: 2.9.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the

Bug#983777: libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4)

Hi Andreas, thanks for reporting, I totally missed one the breaks/replaced like you pointed out. On 3/1/21 6:33 PM, Andreas Beckmann wrote: > IMO only the /usr/lib/* part belongs into libgnunet0.14, > the remaining ones should have stayed in gnunet. the idea here is that the stuff in

Bug#983026: marked as done (libglib2.0-0: After update GDM3 does not longer start)

Your message dated Mon, 01 Mar 2021 17:49:08 + with message-id and subject line Bug#983026: fixed in glib2.0 2.67.5-1 has caused the Debian Bug report #983026, regarding libglib2.0-0: After update GDM3 does not longer start to be marked as done. This means that you claim that the problem has

Processed: [bts-link] source package scipy

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package scipy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Bug#983777: libgnunet0.14: missing Breaks+Replaces: gnunet (<< 0.14.0-4)

Package: libgnunet0.14 Version: 0.14.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it

Bug#983775: libgrokj2k: Baseline violation on amd64/i386

Source: libgrokj2k Version: 7.6.6-1 Severity: serious Tags: patch https://buildd.debian.org/status/fetch.php?pkg=libgrokj2k=amd64=7.6.6-1=1612309672=0 ... cd /<>/obj-x86_64-linux-gnu/src/lib/jp2 && /usr/bin/c++ -DSPDLOG_COMPILED_LIB -Dgrokj2k_EXPORTS -I/<>/obj-x86_64-linux-gnu/src/lib/jp2

Bug#983365: linphone-desktop: chat messages

On Sun, Feb 28, 2021 at 11:07:31PM +0100, Bernhard Schmidt wrote: > an updated liblinphone has been uploaded to sid yesterday. Could you > please try liblinphone10 and liblinphone++10 from sid (4.4.21-2) and > report back? If it does not work you might need libsoci-core4.0 and >

Bug#982586: otrs2: CVE-2021-21435

On Mon, Mar 01, 2021 at 11:46:17AM +0100, Patrick Matthäi wrote: > Hi > > Am 12.02.21 um 08:26 schrieb Salvatore Bonaccorso: > > Source: otrs2 > > Version: 6.0.30-2 > > Severity: important > > Tags: security upstream > > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > > > > Hi, > >

Processed: Re: Bug#941624: Recommending ibus breaks fcitx

Processing control commands: > severity -1 serious Bug #941624 [gnome-shell] Recommending ibus breaks fcitx Severity set to 'serious' from 'important' > affects -1 src:tasksel Bug #941624 [gnome-shell] Recommending ibus breaks fcitx Added indication that 941624 affects src:tasksel -- 941624:

Bug#983653: task-japanese-gnome-desktop: no Japanese input method available out of the box

Hi, Nobuhiro Iwamatsu wrote (Mon, 1 Mar 2021 06:00:51 +0900): > 2021年2月28日(日) 13:12 YOSHINO Yoshihito : > > > > Adding some Japanese input method to the ibus framework should work > > around the problem > > for Japanese users. Specifically, adding Recommends: ibus-mozc (or > > ibus-anthy on > >

Processed: dh-r: pkg-r-autopkgtest breaks autopkgtests

ger marked as fixed in versions dh-r/20210301. -- 983748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

Control: reopen -1 Hi Andreas This didn't work [1]. You need root in order to run 'apt-get install': E: No packages found E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you

Processed: closing as invalid, not reproducible, no feedback

Processing control commands: > severity -1 normal Bug #980906 [libpython3.9] libpython3.9: _collections_abc.py :type 'types.GenericAlias' is not an acceptable base type Severity set to 'normal' from 'critical' -- 980906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980906 Debian Bug

Bug#980906: closing as invalid, not reproducible, no feedback

Control: severity -1 normal closing as invalid, not reproducible, no feedback

Processed: rnp: FTBFS on 32-bit platforms (test suite failures)

Processing control commands: > forwarded -1 https://github.com/rnpgp/rnp/issues/1436 Bug #983770 [rnp] rnp: FTBFS on 32-bit platforms (test suite failures) Set Bug forwarded-to-address to 'https://github.com/rnpgp/rnp/issues/1436'. -- 983770:

Bug#983770: rnp: FTBFS on 32-bit platforms (test suite failures)

Package: rnp Version: 0.14.0-5 Severity: critical Control: forwarded -1 https://github.com/rnpgp/rnp/issues/1436 RNP's test suites are failing on all of the 32-bit platforms in debian. I've reported this upstream so that hopefully it can be resolved. It should not migrate into testing in this

Bug#983764: marked as done (/usr/share/chipcard/cards/README missing)

Your message dated Mon, 01 Mar 2021 14:35:06 + with message-id and subject line Bug#983764: fixed in libchipcard 5.1.5rc2-7 has caused the Debian Bug report #983764, regarding /usr/share/chipcard/cards/README missing to be marked as done. This means that you claim that the problem has been

Processed (with 1 error): Bug#983706: gzip FTBFS on mips64el: FAIL: timestamp

Processing commands for cont...@bugs.debian.org: > clone 983706 -1 Bug #983706 [src:gzip] gzip FTBFS on mips64el: FAIL: timestamp Bug 983706 cloned as bug 983769 > retitile -1 mips64 y2106 problem; gzip FTBFS on mips64el: FAIL: timestamp Unknown command or malformed arguments to command. >

Processed: Re: Bug#983764: /usr/share/chipcard/cards/README missing

Processing control commands: > severity -1 serious Bug #983764 [libchipcard-data] /usr/share/chipcard/cards/README missing Severity set to 'serious' from 'important' -- 983764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983764 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#983766: xphyle ftbfs from source

Package: src.xphyle Version: 4.4.1-1 Severity: serious Tags: sid bullseye xphyle ftbfs from source, it needs at least the following changes: * Build-depend on python3-setuptools-scm. * Build-depend on python3-pytest. * Depend on python3-pkg-resources. But then it still fails in the test

Bug#983763: package unconditionally b-d's on libreoffice-writer

Package: src:gpredict Version: 2.3-72-gc596101-3 Severity: serious Tags: sid bullseye package unconditionally b-d's on libreoffice-writer, not available on all platforms, prohibiting migration to testing.

Bug#983762: pokrok is missing a dependency on pkg_resources

Package: src:pokrok Version: 0.2.0-1 Severity: serious Tags: patch sid bullseye pokrok is missing a dependency on pkg_resources. patch at http://launchpadlibrarian.net/525689938/pokrok_0.2.0-1_0.2.0-1ubuntu1.diff.gz

Processed: tagging 983577

Processing commands for cont...@bugs.debian.org: > tags 983577 + ftbfs Bug #983577 [vuls] FTBFS: src/github.com/future-architect/vuls/oval/util.go:239:43: not enough arguments in call to driver.GetByPackName Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need

Bug#983723: Additional issues on arm64 and mips64el (Was: Bug#983723: rna-star FTBFS on ppc64el due to -march=native)

Hi, On Mon, 1 Mar, 2021, 6:13 pm Andreas Tille, wrote: > Hi, > > besides this on arm64[1] and mips64el: > > ... > cd opal && \ > g++ -c -O3 -std=c++11 -march=native opal.cpp > opal.cpp:9:10: fatal error: immintrin.h: No such file or directory > 9 | #include // AVX2 and lower > |

Bug#983760: java3d FTBFS on 32bit: error: conflicting types for ‘GLsizeiptr’

Source: java3d Version: 1.5.2+dfsg-16 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/java3d.html https://buildd.debian.org/status/package.php?p=java3d=sid ... [exec] In file included from /usr/include/GL/gl.h:2050, [exec]

Bug#983723: Additional issues on arm64 and mips64el (Was: Bug#983723: rna-star FTBFS on ppc64el due to -march=native)

Hi, besides this on arm64[1] and mips64el: ... cd opal && \ g++ -c -O3 -std=c++11 -march=native opal.cpp opal.cpp:9:10: fatal error: immintrin.h: No such file or directory 9 | #include // AVX2 and lower | ^ compilation terminated. Since this seems to be somehow

Bug#983758: python-xarray: autopkgtest regression on several architectures

Source: python-xarray Version: 0.17.0-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-xarray/10765498/log.gz https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-xarray/10765498/log.gz ... === FAILURES

Bug#982927: marked as done (Support for 6.x has ceased, newer branches no longer FLOSS)

Your message dated Mon, 01 Mar 2021 12:03:58 + with message-id and subject line Bug#982927: fixed in otrs2 6.0.32-1 has caused the Debian Bug report #982927, regarding Support for 6.x has ceased, newer branches no longer FLOSS to be marked as done. This means that you claim that the problem

Bug#982379: marked as done (gatos FTBFS with gcc 10)

Your message dated Mon, 01 Mar 2021 12:03:46 + with message-id and subject line Bug#982379: fixed in gatos 0.0.5-19.1 has caused the Debian Bug report #982379, regarding gatos FTBFS with gcc 10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#983755: trapperkeeper-webserver-jetty9-clojure FTBFS on IPV6-only buildds

Source: trapperkeeper-webserver-jetty9-clojure Version: 4.1.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=trapperkeeper-webserver-jetty9-clojure=all

Bug#983653: task-japanese-gnome-desktop: no Japanese input method available out of the box

Hi, On Mon, Mar 1, 2021 at 7:51 PM Holger Wansing wrote: > May I ask how that interacts with the uim framework? > > We currently have > > Recommends: > [...] > uim, > uim-mozc | uim-anthy, > > in task-japanese-desktop, so if you now add

Bug#982586: marked as done (otrs2: CVE-2021-21435)

Your message dated Mon, 1 Mar 2021 11:46:17 +0100 with message-id <13aeb4ae-5b68-3740-6b2b-116217a35...@linux-dev.org> and subject line Re: Bug#982586: otrs2: CVE-2021-21435 has caused the Debian Bug report #982586, regarding otrs2: CVE-2021-21435 to be marked as done. This means that you claim

Bug#983706: gzip FTBFS on mips64el: FAIL: timestamp

Adrian Bunk 于2021年3月1日周一 下午5:27写道： > > On Mon, Mar 01, 2021 at 10:59:20AM +0800, YunQiang Su wrote: > > Adrian Bunk 于2021年3月1日周一 上午7:13写道： > > > > > > Source: gzip > > > Version: 1.10-2 > > > Severity: serious > > > Tags: ftbfs > > > > > >

Bug#982904: marked as done (mumble: CVE-2021-27229)

Your message dated Mon, 01 Mar 2021 10:48:35 + with message-id and subject line Bug#982904: fixed in mumble 1.3.4-1 has caused the Debian Bug report #982904, regarding mumble: CVE-2021-27229 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: found 983727 in 1.2.1-1

Processing commands for cont...@bugs.debian.org: > found 983727 1.2.1-1 Bug #983727 [thinkfan] thinkfan should not ship an example in /etc/thinkfan.yaml Marked as found in versions thinkfan/1.2.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 983727:

Bug#981422: xdg-utils: autopkgtest failure: make: dh: No such file or directory

On 30/01/2021 22:22, Nicholas Guriev wrote: Hello! On Sat, 2021-01-30 at 21:54 +0100, Paul Gevers wrote: You recently added an autopkgtest to your package xdg-utils, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the

Bug#982904: mumble: CVE-2021-27229

Hi [Adding CC to security-team alias] On Mon, Mar 01, 2021 at 08:31:54AM +, Chris Knadle wrote: > Salvatore Bonaccorso: > > Source: mumble > > Version: 1.3.3-1 > > Severity: grave > > Tags: security upstream > > Justification: user security hole > > Forwarded:

Bug#983706: gzip FTBFS on mips64el: FAIL: timestamp

On Mon, Mar 01, 2021 at 10:59:20AM +0800, YunQiang Su wrote: > Adrian Bunk 于2021年3月1日周一 上午7:13写道： > > > > Source: gzip > > Version: 1.10-2 > > Severity: serious > > Tags: ftbfs > > > > https://buildd.debian.org/status/fetch.php?pkg=gzip=mips64el=1.10-3=1614531854=0 > > It seems due to some

Bug#981846: closed by Graham Inggs (python-argcomplete: multiple tests failure)

On Sun, 2021-02-28 at 07:15 +, Debian Bug Tracking System wrote: > Version: 1.8.1-1.4 > > Hi Ritesh > > 1.8.1-1.4 builds in sbuild and on the buildds [1]. > > Perhaps you ran into #873149 ?  That should be fixed now in 1.8.1- > 1.5. THank you. The fix in this upload indeed fixes the

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

Hi Andreas On Mon, 1 Mar 2021 at 10:49, Andreas Tille wrote: > However, the issue should have been become obvious even in unstable > 10 days ago. Well, it was visible in unstable, e.g. in r-bioc-destiny [1], and also on the tracker page [2] it says "Debci reports failed tests", but certainly

Bug#982904: mumble: CVE-2021-27229

Salvatore Bonaccorso: Source: mumble Version: 1.3.3-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/mumble-voip/mumble/pull/4733 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for

Bug#983748: marked as done (dh-r: pkg-r-autopkgtest breaks autopkgtests)

Your message dated Mon, 01 Mar 2021 09:03:22 + with message-id and subject line Bug#983748: fixed in dh-r 20210301 has caused the Debian Bug report #983748, regarding dh-r: pkg-r-autopkgtest breaks autopkgtests to be marked as done. This means that you claim that the problem has been dealt

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

Hi Graham, I've uploaded a change that (hopefully!) fixes the issue. On Mon, Mar 01, 2021 at 08:24:09AM +0200, Graham Inggs wrote: > The recent upload of dh-r causes autopkgtests using pkg-r-autopkgtest > to fail. See for example the output of r-bioc-affy [1] below. > Presumably caused by this