Bug#950155: marked as done (apertium-oc-ca FTBFS with apertium 3.6.1)

Your message dated Thu, 26 Mar 2020 05:04:14 + with message-id and subject line Bug#950155: fixed in apertium-oc-ca 1.0.6~r57551-4 has caused the Debian Bug report #950155, regarding apertium-oc-ca FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has

Bug#952070: marked as done (ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby2.5" failed: Failure/Error: Puppet::Parser::Functions.expects(:function).with('my_func').returns(false))

Your message dated Thu, 26 Mar 2020 04:20:04 + with message-id and subject line Bug#952070: fixed in ruby-puppetlabs-spec-helper 2.6.2-2 has caused the Debian Bug report #952070, regarding ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby2.5" failed: Failure/Error: Puppet::Parser::Functi

Bug#952078: marked as done (ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed.)

Your message dated Thu, 26 Mar 2020 04:05:53 +0100 with message-id <0ac1a5dd2c7fab5312d5f0f7866ef95f371009da.ca...@debian.org> and subject line Unreproducible, possibly caused by different package has caused the Debian Bug report #952078, regarding ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed. t

Bug#954756: marked as done (puppet-module-aboe-chrony depends on obsolete transitional package.)

Your message dated Thu, 26 Mar 2020 02:21:00 + with message-id <9195a083-bf5c-579a-4cd4-6f2c7bc6a...@p10link.net> and subject line re: puppet-module-aboe-chrony depends on obsolete transitional package. has caused the Debian Bug report #954756, regarding puppet-module-aboe-chrony depends on ob

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 954470 + patch Bug #954470 [src:pysha3] src:pysha3: Autopkgtest failure due to use of py3versions -i Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 954470: https://bugs.debian.org/cgi-bi

Bug#954470: pysha3: Autopkgtest failure due to use of py3versions -i

Hi, I attach a NMU patch. Please, consider apply it. Thanks Cheers, -- Emmanuel Arias @eamanu yaerobi.com From db724cd1aa5c7bc37c9210e3cdf5a2c252ae504d Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 25 Mar 2020 23:04:36 -0300 Subject: [PATCH] pysha3: fix autopkgtest regression. Use

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 954461 + patch Bug #954461 [src:editorconfig-core-py] src:editorconfig-core-py: Autopkgtest failure due to use of py3versions -i Ignoring request to alter tags of bug #954461 to the same tags previously set > thanks Stopping processing here.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 954468 + patch Bug #954468 [src:pyethash] src:pyethash: Autopkgtest failure due to use of py3versions -i Added tag(s) patch. > tags 954469 + patch Bug #954469 [src:pyrlp] src:pyrlp: Autopkgtest failure due to use of py3versions -i Added tag

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > tags 954461 954468 954469 + patch Unknown tag/s: 954468, 954469. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid

Bug#954469: src:pyrlp: Autopkgtest failure due to use of py3versions -i

Hi, I attach a NMU patch. Please, consider apply it. Thanks! Cheers, -- Emmanuel Arias @eamanu yaerobi.com From 05d4ad3f70ed004e4d4bee65fa39c302b02ad640 Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 25 Mar 2020 22:12:31 -0300 Subject: [PATCH] pyrlp: Fix autopkgtest regression. Use

Processed: Bug#954948 marked as pending in fonts-noto

Processing control commands: > tag -1 pending Bug #954948 [fonts-noto] [d-i bullseye alpha2] Sinhala font missing Added tag(s) pending. -- 954948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954948: marked as pending in fonts-noto

Control: tag -1 pending Hello, Bug #954948 in fonts-noto reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/fonts-team/fonts-noto/-/commit/cf3d2b40bad2ccd42800ab83

Bug#954468: src:pyethash: Autopkgtest failure due to use of py3versions -i

Hi, I attach a NMU patch. Please, consider apply it. Thanks! Cheers, -- Emmanuel Arias @eamanu yaerobi.com From 86054609e4f0c6526fdb21ebe6fd90088366ec62 Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 25 Mar 2020 21:56:15 -0300 Subject: [PATCH] pyethash: d/tests/smoke-python3: fix au

Bug#954533: This is likely libssl1.1 problem

This happens in othe packages - well, not the FTBFS, but the error, like getmail. It's been reported in other distros as well, e.g. see https://bugs.archlinux.org/task/65976. Maybe re-assign to libssl1.1?

Bug#952027: marked as done (ruby-declarative: FTBFS: ERROR: Test "ruby2.5" failed: Invalid gemspec in [declarative.gemspec]: No such file or directory - git)

Your message dated Thu, 26 Mar 2020 00:49:48 + with message-id and subject line Bug#952027: fixed in ruby-declarative 0.0.10-2 has caused the Debian Bug report #952027, regarding ruby-declarative: FTBFS: ERROR: Test "ruby2.5" failed: Invalid gemspec in [declarative.gemspec]: No such file or d

Bug#950983: marked as done (clickhouse FTBFS in bullseye/sid)

Your message dated Thu, 26 Mar 2020 00:19:28 + with message-id and subject line Bug#950983: fixed in clickhouse 18.16.1+ds-6 has caused the Debian Bug report #950983, regarding clickhouse FTBFS in bullseye/sid to be marked as done. This means that you claim that the problem has been dealt wit

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

On Wed, Mar 25, 2020 at 08:57:14AM -0400, Justin Erenkrantz wrote: > James, > > Thanks for the bug report.  For reference, the upstream OpenSSL commit looks > to > be: > > https://github.com/openssl/openssl/commit/ > d924dbf4ae127c68463bcbece04b6e06abc58928 > > I strongly suspect that the patch

Bug#943402: I have the same issue

I have exactly the same issue. Found it while trying to use Festival with Asterisk. If I use the italian voice I get the same error, and if I use the english voice it works flawlessly. Steps to reproduce: install festlex-ifd and its dependencies. run festival with italian language:

Bug#947564: FTBFS with scons 3.1.2-1

Hello Jörg, On Sat, Dec 28, 2019 at 08:51:25AM +0100, Jörg Frings-Fürst wrote: > Source: gpick > Version: 0.2.6~rc1-1 > Severity: important > Usertags: scons_ftbfs > > > Hello, > > in the context of the change to Python3 also Scons was revised. With > the current version 3.1.2-1 from Experimen

Processed: severity of 936659 is serious

Processing commands for cont...@bugs.debian.org: > severity 936659 serious Bug #936659 [src:gr-hpsdr] gr-hpsdr: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936659: https://bugs.debian.org/

Bug#920371: telnetd-ssl: SSL_CTX_use_certificate, ee key too small

Hi, FYI, there is more info about this issue on https://github.com/debauchee/barrier/issues/126 . Best regards, -- Marcos Marado

Bug#938622: tahoe-lafs: Python2 removal in sid/bullseye

On Wed, Mar 18, 2020 at 10:38:17AM +0530, Vasudev Kamath wrote: > > Sorry for the delayed response here. I let the package to fall of from > testing as upstream does not yet any support for building python3. > Though currently there is some work going on for supporting python3 in > upstream, I'm n

Bug#954916: another breakage due to LaTeX changes?

On 25/03/2020 20:32, Norbert Preining wrote: Hi Joseph, See attached Thanks (although order was reversed ;-) Should we upload that to CTAN? Best Norbert You can go for it; CTAN might not allow ... Joseph

Bug#954916: another breakage due to LaTeX changes?

Hi Joseph, > See attached Thanks (although order was reversed ;-) Should we upload that to CTAN? Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3

Bug#954915: Error still not fixed

cat /etc/apt/sources.list # deb http://deb.debian.org/debian/ sid main deb http://deb.debian.org/debian/ sid main non-free contrib # deb-src http://deb.debian.org/debian/ sid main non-free contrib ``` sudo apt full-upgrade [sudo] password for sina: Reading package lists... Done Building dependency

Bug#954954: libstdc++6: symbols file on armel incomplete

package: libstdc++6 severity: serious Hi, It seems the symbols file for libstdc++6 is missing some symbols on armel. The build adds these with the latest version. This causes new builds that use these symbols to pick up an (unnecessary) versioned dependency on the latest gcc in unstable. As this

Bug#951634: Broken package in testing repository

Hi Alexander, Hugo, Graham On Wed, 25 Mar 2020, 21:45 Alexander van der Meij, < vandermeij.t...@gmail.com> wrote: > > > > Hi Debian Science team, > > As described in bug 951634 > , Debian is > currently distributing a broken development b

Bug#954948: [d-i bullseye alpha2] Sinhala font missing

Control: reassign -1 fonts-noto Holger Wansing wrote: > Package: debian-installer > Severity: grave > > > While testing the alpha2 netinst image I noticed that the graphical installer > has no fonts for Sinhala anymore, this was ok until alpha1. > > Screenshots attached. > According to ../

Processed: Re: Bug#954948: [d-i bullseye alpha2] Sinhala font missing

Processing control commands: > reassign -1 fonts-noto Bug #954948 [debian-installer] [d-i bullseye alpha2] Sinhala font missing Bug reassigned from package 'debian-installer' to 'fonts-noto'. Ignoring request to alter found versions of bug #954948 to the same values previously set Ignoring reques

Bug#954916: another breakage due to LaTeX changes?

Control: reassign -1 src:lgrind Control: tags -1 + patch Am 25.03.2020 um 15:57 teilte Joseph Wright mit: > On 25/03/2020 11:24, Norbert Preining wrote: >> On Wed, 25 Mar 2020, Joseph Wright wrote: >>> 'normal', i.e. moving the \begin{document} line, but I'm not sure if >>> that is >>> an accept

Processed: Re: Bug#954916: another breakage due to LaTeX changes?

Processing control commands: > reassign -1 src:lgrind Bug #954916 [src:lgrind,src:texlive-base] lgrind: FTBFS with current texlive Bug reassigned from package 'src:lgrind,src:texlive-base' to 'src:lgrind'. No longer marked as found in versions texlive-base/2020.20200313-1, lgrind/3.67-3.1, texliv

Bug#954912: marked as done (Please switch to gupnp/gssdp 1.2)

Your message dated Wed, 25 Mar 2020 17:34:50 + with message-id and subject line Bug#954912: fixed in librm 2.1.2-3 has caused the Debian Bug report #954912, regarding Please switch to gupnp/gssdp 1.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#954461: Autopkgtest failure due to use of py3versions -i

Hi, I attach a NMU patch. Please consider apply it. Thanks! Cheers, -- Emmanuel Arias @eamanu yaerobi.com From 7bb9a35414b61d9392aa5673f63b538b96b7a4cb Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 25 Mar 2020 14:11:33 -0300 Subject: [PATCH] d/tests/smoke-python3: fix autopkgtest r

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

On Wed, 25 Mar 2020 10:54:22 +0100 =?utf-8?B?SsO2cmc=?= Sommer wrote: > > A quick and dirty workaround is: > > ``` > # egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed > 's,^,/usr,' |tee -a $I/libc6:amd64.list > /usr/lib/x86_64-linux-gnu/ld-2.30.so > /usr/lib/x86_64-linux-

Bug#936561: freshen: Python2 removal in sid/bullseye

Hi Federico, 在 2020-03-24星期二的 22:32 +，Federico Ceratto写道： > On Tue, Mar 24, 2020 at 2:54 PM Boyuan Yang wrote: > > Hi Federico, > > > > I believe your package is a candidate for removal due to upstream > > inactivity > > and that the package received no upload in the last 9 years. Besides, t

Bug#954130: marked as done (libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be installed)

Your message dated Wed, 25 Mar 2020 16:49:41 + with message-id and subject line Bug#954130: fixed in libxmlada 19-3 has caused the Debian Bug report #954130, regarding libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be installed to be marked as done. This means that you cl

Processed: Re: Broken package in testing repository

Processing control commands: > severity -1 serious Bug #951634 [gummi] gummi: request to bump gummi package from development to release build Severity set to 'serious' from 'normal' -- 951634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951634 Debian Bug Tracking System Contact ow...@bugs

Bug#954940: marked as done (arcp: d/copyright: needs copyright years for the upstream source)

Your message dated Wed, 25 Mar 2020 16:19:17 + with message-id and subject line Bug#954940: fixed in arcp 0.2.1-3 has caused the Debian Bug report #954940, regarding arcp: d/copyright: needs copyright years for the upstream source to be marked as done. This means that you claim that the probl

Bug#954897: pydxcluster: should this package be removed?

Re: Sandro Tosi 2020-03-25 <158509215087.18239.15325100274815623896.report...@zion.matrix.int> > i believe this package should be removed: +1 from me. Christoph

Bug#954940: arcp: d/copyright: needs copyright years for the upstream source

Source: arcp Version: 0.2.1-1 Severity: serious Justification: Policy 2.3, 4.5, 12.5 Hello, During review in NEW I noticed this copyright claim is invalid because there is no year given: Files: * Copyright: Stian Soiland-Reyes License: Apache-2.0 (I ACCEPTed from NEW because Apache

Bug#953069: marked as done (libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range)

Your message dated Wed, 25 Mar 2020 15:37:39 + with message-id and subject line Bug#953069: fixed in libgnatcoll-db 19.2-3 has caused the Debian Bug report #953069, regarding libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range to be marked as done. This means that you

Bug#938327: marked as done (rabbitvcs: Python2 removal in sid/bullseye)

Your message dated Wed, 25 Mar 2020 15:08:25 + with message-id and subject line Bug#938327: fixed in rabbitvcs 0.18-1 has caused the Debian Bug report #938327, regarding rabbitvcs: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#954916: another breakage due to LaTeX changes?

On 25/03/2020 11:24, Norbert Preining wrote: On Wed, 25 Mar 2020, Joseph Wright wrote: The structure of the .dtx is ... unusual. It's got the \begin{document} in Yes, this is what I saw, too, but it was working before ;-) 'normal', i.e. moving the \begin{document} line, but I'm not sure if t

Bug#950382: marked as done (apertium-mk-en FTBFS with apertium 3.6.1)

Your message dated Wed, 25 Mar 2020 14:50:09 + with message-id and subject line Bug#950382: fixed in apertium-mk-en 0.1.1~r57554-3 has caused the Debian Bug report #950382, regarding apertium-mk-en FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has

Bug#954480: python-tinyrpc: Autopkgtest failure due to use of py3versions -i

Hi, I attach a NMU patch. Please, consider apply it. Thanks! Cheers, -- Emmanuel Arias @eamanu yaerobi.com From 12441b71f337e965c3304ab6700f84d455c6dadc Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 25 Mar 2020 11:03:55 -0300 Subject: [PATCH] d/tests/smoke-python3: fix autopkgtest r

Bug#953069: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

control: tag -1 + patch On 2020-03-25 09:51, Aurelien Jarno wrote: > Hi, > > On 2020-03-12 13:55, Emilio Pozuelo Monfort wrote: > > Control: severity -1 serious > > > > On Wed, 4 Mar 2020 01:53:25 +0100 Nicolas Boulenguez > > wrote: > > > Source: libgnatcoll-db > > > Version: 19.2-2 > > > Seve

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 954480 + patch Bug #954480 [src:python-tinyrpc] src:python-tinyrpc: Autopkgtest failure due to use of py3versions -i Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 954480: https://bugs.d

Processed: Re: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

Processing control commands: > tag -1 + patch Bug #953069 [src:libgnatcoll-db] libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range Added tag(s) patch. -- 953069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953069 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#954566: marked as done (cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

Your message dated Wed, 25 Mar 2020 14:58:25 +0100 with message-id <20200325135825.gd1590...@msg.df7cb.de> and subject line Re: [3dprinter-general] Bug#954566: cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 has caused the Debian B

Bug#954915: marked as pending in glibc

On Wed, 25 Mar 2020 at 13:15:03 +, Aurelien Jarno wrote: > debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no > easy way to check if a file belongs to a package with usrmerge. Just drop all > safety checks... Closes: #954915. The /usr merge merges /foo with /usr/foo

Bug#954915: marked as done ([libc6] upgrade fail: A copy of the C library was found in an unexpected directory)

Your message dated Wed, 25 Mar 2020 13:35:22 + with message-id and subject line Bug#954915: fixed in glibc 2.30-4 has caused the Debian Bug report #954915, regarding [libc6] upgrade fail: A copy of the C library was found in an unexpected directory to be marked as done. This means that you c

Bug#954933: marked as done (libc6: Not installing package libc6. Problem script.)

Your message dated Wed, 25 Mar 2020 13:35:22 + with message-id and subject line Bug#954915: fixed in glibc 2.30-4 has caused the Debian Bug report #954915, regarding libc6: Not installing package libc6. Problem script. to be marked as done. This means that you claim that the problem has been

Bug#938327: Upstream references

On Tue, 2020-03-24 at 21:42 +0100, Moritz Mühlenhoff wrote: > On Sun, Dec 15, 2019 at 02:01:30PM +, Jelmer Vernooij wrote: > > > FWIW Upstream is working on Python 3 support here: > > https://github.com/rabbitvcs/rabbitvcs/issues/279 > > > Hi Ritesh, > > this is fixed in 0.18, could you ple

Processed: forcibly merging 954915 954933

Processing commands for cont...@bugs.debian.org: > forcemerge 954915 954933 Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in an unexpected directory Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in an unexpected directory Marked as foun

Bug#954222: marked as done (src:appdirs: Fails autopkgtest with non-default python3 installed)

Your message dated Wed, 25 Mar 2020 13:19:12 + with message-id and subject line Bug#954222: fixed in appdirs 1.4.3-2.1 has caused the Debian Bug report #954222, regarding src:appdirs: Fails autopkgtest with non-default python3 installed to be marked as done. This means that you claim that the

Bug#954915: marked as pending in glibc

Control: tag -1 pending Hello, Bug #954915 in glibc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/glibc-team/glibc/-/commit/49d137c4392cb1144f2313f78f31466aaa

Processed: Bug#954915 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in an unexpected directory Added tag(s) pending. -- 954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#954608: marked as done (godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Wed, 25 Mar 2020 13:04:37 + with message-id and subject line Bug#954608: fixed in godot 3.2-stable-2 has caused the Debian Bug report #954608, regarding godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This me

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

James, Thanks for the bug report. For reference, the upstream OpenSSL commit looks to be: https://github.com/openssl/openssl/commit/d924dbf4ae127c68463bcbece04b6e06abc58928 I strongly suspect that the patch on our side (against 1.3.x) is something akin to below. I'm having trouble getting a te

Processed: tagging 954222

Processing commands for cont...@bugs.debian.org: > tags 954222 + pending Bug #954222 [src:appdirs] src:appdirs: Fails autopkgtest with non-default python3 installed Ignoring request to alter tags of bug #954222 to the same tags previously set > thanks Stopping processing here. Please contact me

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

On 2020-03-25 10:21, Jörg Sommer wrote: > jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben: > > Package: libc6 > > Version: 2.30-3 > > > > sudo aptitude upgrade just now: > > > > ``` > > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ... > > Unpacking libc6-dev:amd64 (2.30-3) ove

Bug#954926: Acknowledgement (x264: symbol lookup error)

Yes. Indeed. I'm an idiot as I thought removing ALL packages sourcing Christian's repo from the system had be done long time ago. This one: libx264-155 3:0.155.2901+git7d0ff22-dmo3 was a silient keeper though. Thanks for your patience. Bug can be closed/thrown into the pit.

Processed: Link to upstream issue

Processing commands for cont...@bugs.debian.org: > forwarded 954632 > https://github.com/unknown-horizons/unknown-horizons/pull/2910 Bug #954632 [src:unknown-horizons] unknown-horizons: FTBFS: AttributeError: module 'platform' has no attribute 'dist' Set Bug forwarded-to-address to 'https://git

Bug#954926: marked as done (x264: symbol lookup error)

Your message dated Wed, 25 Mar 2020 12:24:05 +0100 with message-id <20200325112405.ga4115...@ramacher.at> and subject line Re: Bug#954926: x264: symbol lookup error has caused the Debian Bug report #954926, regarding x264: symbol lookup error to be marked as done. This means that you claim that th

Bug#954916: another breakage due to LaTeX changes?

On Wed, 25 Mar 2020, Joseph Wright wrote: > The structure of the .dtx is ... unusual. It's got the \begin{document} in Yes, this is what I saw, too, but it was working before ;-) > 'normal', i.e. moving the \begin{document} line, but I'm not sure if that is > an acceptable fix. Can you send a pa

Bug#954926: x264: symbol lookup error

Package: x264 Version: 2:0.155.2917+git0a84d98-2 Severity: grave Justification: renders package unusable Dear Maintainer, x264 (latest package from upstream does not) exites on my testing setup: (gdb) [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linu

Bug#954916: another breakage due to LaTeX changes?

On Wed, 25 Mar 2020, Joseph Wright wrote: > Where can we find lgrind.dtx? It was attached ... Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0

Processed: tagging 954915

Processing commands for cont...@bugs.debian.org: > tags 954915 + confirmed Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in an unexpected directory Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 954915: https

Bug#954916: another breakage due to LaTeX changes?

On 25/03/2020 11:03, Enrico Gregorio wrote: On 25 Mar 2020, at 11:57 , Joseph Wright wrote: Hi Norbert, Where can we find lgrind.dtx? http://mirrors.ctan.org/support/lgrind/lgrind.dtx Ciao Enrico The structure of the .dtx is ... unusual. It's got the \begin{document} in the 'input'

Bug#954916: another breakage due to LaTeX changes?

> On 25 Mar 2020, at 11:57 , Joseph Wright > wrote: > > Hi Norbert, > > Where can we find lgrind.dtx? http://mirrors.ctan.org/support/lgrind/lgrind.dtx Ciao Enrico

Bug#954916: another breakage due to LaTeX changes?

On 25/03/2020 10:47, Norbert Preining wrote: Hi all, in particular LaTeX group, it seems that some old documents (.dtx) don't translate anymore correctly. That might be simply a bug in the old code, but maybe some oversight in the LaTeX code. The attached lgrind.dtx was used and always properly

Bug#954916: another breakage due to LaTeX changes?

Hi all, in particular LaTeX group, it seems that some old documents (.dtx) don't translate anymore correctly. That might be simply a bug in the old code, but maybe some oversight in the LaTeX code. The attached lgrind.dtx was used and always properly build up to recent changes (2020 LaTeX), but n

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben: > Package: libc6 > Version: 2.30-3 > > sudo aptitude upgrade just now: > > ``` > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ... > Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ... > Preparing to unpack .../libc-dev-bin_2.30

Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben: > Package: libc6 > Version: 2.30-3 > > sudo aptitude upgrade just now: > > ``` > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ... > Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ... > Preparing to unpack .../libc-dev-bin_2.30

Bug#954203: Client splash and exit after login in

Hello Gulfstream, > Thanks for your reply! My next question is How to connect the xrdp server > using remmina client? I don't find where to set the glyph cache. in the previous mentioned upstream link to the remmina bug tracker in comment [1] is written that they added such flags, but I guess t

Bug#954568: marked as done (gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE')

Your message dated Wed, 25 Mar 2020 10:57:41 +0100 with message-id <82cca473-f6bb-da29-ced8-3b277ad61...@debian.org> and subject line Re: Bug#954568: gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE' has caused the De

Bug#954608: godot: Team upload

Control: tags -1 +pending Dear Federico, I have prepared an upload for godot/3.2-stable-2 as a team upload, as the package's maintainer is Debian Games Team. The upload should fix #944168 and #954608. I am looking for a sponsor to upload it. The code is at https://salsa.debian.org/jnumm-guest/go

Processed: godot: Team upload

Processing control commands: > tags -1 +pending Bug #954608 [src:godot] godot: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 954608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954608 Debian Bug Tracking System Contact ow...@b

Bug#954916: lgrind: FTBFS with current texlive

Source: lgrind,texlive-base Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source Control: found -1 3.67-3.1 Control: found -1 2020.20200313-1 Hi, lgrind FTBFS with the current texlive in bullseye and sid: debian/rules build dh_testdir latex lgrind.ins This is pdf

Processed: lgrind: FTBFS with current texlive

Processing control commands: > found -1 3.67-3.1 Bug #954916 [src:lgrind,src:texlive-base] lgrind: FTBFS with current texlive The source 'texlive-base' and version '3.67-3.1' do not appear to match any binary packages Marked as found in versions lgrind/3.67-3.1 and texlive-base/3.67-3.1. > found

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 954915 serious Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in an unexpected directory Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assi

Bug#953069: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

Hi, On 2020-03-12 13:55, Emilio Pozuelo Monfort wrote: > Control: severity -1 serious > > On Wed, 4 Mar 2020 01:53:25 +0100 Nicolas Boulenguez > wrote: > > Source: libgnatcoll-db > > Version: 19.2-2 > > Severity: normal > > > > The relevant lines are: > > > > xref/gnatcoll-xref.adb: In functi

Bug#954147: marked as done (src:dateparser: Requires a package outside of Main)

Your message dated Wed, 25 Mar 2020 08:45:04 + with message-id and subject line Bug#954147: fixed in dateparser 0.7.2-2 has caused the Debian Bug report #954147, regarding src:dateparser: Requires a package outside of Main to be marked as done. This means that you claim that the problem has b

Processed: tagging 947568

Processing commands for cont...@bugs.debian.org: > tags 947568 + ftbfs Bug #947568 [src:mixxx] FTBFS with scons 3.1.2-1 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 947568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947568 Debian Bug

Bug#954912: Please switch to gupnp/gssdp 1.2

Source: librm Version: 2.1.2-2 Severity: serious Tags: patch Hello, Could you please switch the build-dependencies to gupnp/gssdp 1.2 instead of 1.0? We are currently trying to get rid of the version 1.0 librm has reintroduced a reverse-dependencies against that old version. Kind regards Lauren

Bug#952278: marked as done (kwindowsystem: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE

Your message dated Wed, 25 Mar 2020 07:49:13 + with message-id and subject line Bug#948827: fixed in kwindowsystem 5.62.0-3 has caused the Debian Bug report #948827, regarding kwindowsystem: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE

Bug#948827: marked as done (kwindowsystem FTBFS: The XFixes library could not be found.)

Your message dated Wed, 25 Mar 2020 07:49:13 + with message-id and subject line Bug#948827: fixed in kwindowsystem 5.62.0-3 has caused the Debian Bug report #948827, regarding kwindowsystem FTBFS: The XFixes library could not be found. to be marked as done. This means that you claim that the

Processed: tagging 948827

Processing commands for cont...@bugs.debian.org: > tags 948827 + pending Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could not be found. Bug #952278 [src:kwindowsystem] kwindowsystem: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PR

Processed: tagging 952240

Processing commands for cont...@bugs.debian.org: > tags 952240 + fixed-in-experimental Bug #952240 {Done: Christoph Biedl } [src:clevis] clevis: FTBFS: dh_install: error: missing files, aborting Added tag(s) fixed-in-experimental. > thanks Stopping processing here. Please contact me if you need

Processed: forcibly merging 948827 952278

Processing commands for cont...@bugs.debian.org: > forcemerge 948827 952278 Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could not be found. Bug #948827 [src:kwindowsystem] kwindowsystem FTBFS: The XFixes library could not be found. Added tag(s) bullseye and sid. Bug #