Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread Michael Ott
I did the same and it works. This mail will be send from Evolution > This issue goes away for me after a rebuild of src:evolution-data- server > and installing the freshly rebuilt libebook-contacts-1.2-4. > > Maybe we can kick off a rebuild via the transition.  If not that, would > you be

Processed: Re: dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1022387 [src:dxf2gcode] dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory Added tag(s) patch. -- 1022387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022387 Debian Bug Tracking System

Bug#1022387: dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory

2022-11-22 Thread Petter Reinholdtsen
Control: tags -1 + patch Look like setuptool changed behaviour, and now require --install-data=/usr and --install-scripts=/usr/bin to function properly. This patch should fix the issue: diff --git a/debian/rules b/debian/rules index c86b1a6..2d5dbe3 100755 --- a/debian/rules +++ b/debian/rules

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread tony mancill
On Wed, Nov 23, 2022 at 06:28:04AM +0100, Christoph Anton Mitterer wrote: > On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote: > > I guess it must be doing some kind of dynamic loading stuff? OTOH, it > seems to be just linked as a plain shared lib: > $ libtree

Bug#1021754: marked as done (rust-zoxide: build-dependencies unsatisfiable.)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Nov 2022 06:19:13 + with message-id and subject line Bug#1021754: fixed in rust-zoxide 0.4.3-5 has caused the Debian Bug report #1021754, regarding rust-zoxide: build-dependencies unsatisfiable. to be marked as done. This means that you claim that the problem has

Bug#1017621: seahorse-nautilus: Fails to build with Nautilus 43

2022-11-22 Thread Andreas Metzler
On 2022-08-18 Jeremy Bicha wrote: > Source: seahorse-nautilus [...] > The newest release of Nautilus, version 43, has switched to GTK4 and > includes major changes in the extensions API. > seahorse-nautilus will need to be converted to GTK4 and make other changes > for the new version. >

Processed: protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java)

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > block 1023535 by -1 Bug #1023535 [release.debian.org] transition: protobuf 1023535 was blocked by: 1022248 1018945 1023535 was not blocking any bugs. Added blocking bug(s) of 1023535: 1024677 -- 1023535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023535

Bug#1024677: protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java)

2022-11-22 Thread Bas Couwenberg
Source: protobuf Version: 3.21.9-3 Severity: serious Tags: upstream patch Control: block 1023535 by -1 Dear Maintainer, The autopkgtest for your package is failing: autopkgtest [02:27:53]: test simple: [--- *** Building example programs protoc $PROTO_PATH --cpp_out=.

Bug#1022413: marked as done (sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Nov 2022 06:04:17 + with message-id and subject line Bug#1022413: fixed in sqlmodel 0.0.8-1 has caused the Debian Bug report #1022413, regarding sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 to

Processed: retitle 1024674 to libebook-contacts-1.2-4 needs rebuild after protobuf transition, affects 1024674 ...

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1024674 libebook-contacts-1.2-4 needs rebuild after protobuf > transition Bug #1024674 [libphonenumber8] libphonenumber8: breaks Evolution Changed Bug title to 'libebook-contacts-1.2-4 needs rebuild after protobuf transition' from

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread tony mancill
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > Package: libphonenumber8 > Version: 8.12.57+ds-1+b2 > Severity: serious > > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: >

Processed: Bug#1022413 marked as pending in sqlmodel

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1022413 [src:sqlmodel] sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 Added tag(s) pending. -- 1022413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022413 Debian Bug

Bug#1022413: marked as pending in sqlmodel

2022-11-22 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1022413 in sqlmodel 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#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread Christoph Anton Mitterer
On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote: > Yes, totally.  I didn't mean to imply that the bug shouldn't be here. Sure... just wanted to point out, that I don't consider it your fault or so :-) > > I had evolution running, while I've upgraded. And didn't restart it > > afterwards

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread tony mancill
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: > /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol: >

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread tony mancill
On Wed, Nov 23, 2022 at 05:51:50AM +0100, Christoph Anton Mitterer wrote: > Hey Tony. > > On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote: > > Thank you for the bug report.  libphonenumber 8.12.57+ds-1 has been > > in > > testing for longer than a month at this point [1].  Has it been > >

Processed: tagging 1022308

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1022308 + patch Bug #1022308 [src:crawl] crawl: FTBFS: glwrapper-ogl.cc:29:14: fatal error: GL/glu.h: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022308:

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread Christoph Anton Mitterer
Hey Tony. On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote: > Thank you for the bug report.  libphonenumber 8.12.57+ds-1 has been > in > testing for longer than a month at this point [1].  Has it been > broken > all of this time?  If not, I suspect this is related the protobuf > transition

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread tony mancill
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > Package: libphonenumber8 > Version: 8.12.57+ds-1+b2 > Severity: serious > > > Hey. > > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: >

Bug#1024674: libphonenumber8: breaks Evolution

2022-11-22 Thread Christoph Anton Mitterer
Package: libphonenumber8 Version: 8.12.57+ds-1+b2 Severity: serious Hey. After the upgrade, evolution crashes when started: $ evolution evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol:

Bug#1022307: [Debian-med-packaging] Bug#1022307: status on t_coffee causing biopython ftbfs

2022-11-22 Thread Charles Plessy
Le Tue, Nov 22, 2022 at 11:54:48PM +0100, Étienne Mollier a écrit : > > Hi, mostly retitling the open entry against biopython for the > sake of clarity, and also pinging both bugs to reset auto- > removal counters. We don't have much news from t_coffee > upstream to day unfortunately. Maybe it

Bug#1020851: elpa-ement: fails to install along emacs

2022-11-22 Thread Sean Whitton
Hello, On Tue 22 Nov 2022 at 05:39PM +01, Andreas Beckmann wrote: > On 28/09/2022 16.55, Sean Whitton wrote: >> transient is included in Emacs 28 so I'm inclined to leave this to fix >> itself when Emacs 28 migrates. > > Can't this be expressed as a package relationship? > e.g. Depends: emacs-el

Bug#1012950: itk-4.y buildability status

2022-11-22 Thread Étienne Mollier
Hi, I've been reviewing whether it would be feasible at t time to fallback to gcc-11 for insighttoolkit4, but I hit another build problem. I ended up disabling python3 bindings, at last. The itk-4.y branch on salsa currently builds properly on Debian sid amd64, but I stopped producing the

Processed: severity of 1012572 is serious

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1012572 serious Bug #1012572 {Done: Roger Shimizu } [src:android-platform-frameworks-base] android-platform-frameworks-base: FTBFS with protobuf 3.20.1+ Severity set to 'serious' from 'important' > thanks Stopping processing here.

Processed: status on t_coffee causing biopython ftbfs

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Bug #1022307 [src:python-biopython] python-biopython: FTBFS: mv: cannot stat 'Tests/test_NACCESS_tool.py': No such file or directory Changed Bug title to 'python-biopython: FTBFS: tests choke on

Processed: status on t_coffee causing biopython ftbfs

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Bug #1022307 [src:python-biopython] python-biopython: FTBFS: tests choke on t_coffee Ignoring request to change the title of bug#1022307 to the same title -- 1022307:

Bug#1022307: status on t_coffee causing biopython ftbfs

2022-11-22 Thread Étienne Mollier
Control: retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Hi, mostly retitling the open entry against biopython for the sake of clarity, and also pinging both bugs to reset auto- removal counters. We don't have much news from t_coffee upstream to day unfortunately. Maybe it will

Bug#1011084: marked as done (cargo: FTBFS on mips64el)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 23:44:54 +0100 with message-id and subject line Re: Bug#1011084: cargo: FTBFS on mips64el has caused the Debian Bug report #1011084, regarding cargo: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'

2022-11-22 Thread Andreas Beckmann
On 22/11/2022 18.40, Diane Trout wrote: On Tue, 2022-11-22 at 18:24 +0100, Andreas Beckmann wrote: There needs to be either a   Depends: emacs-el (>= 1:28) or an equivaent   Breaks: (emacs-el (<< 1:28) or the installation must be skipped if emacs is too old. So it looks like elpa-snakemake

Bug#1019675: marked as done (ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 22:20:34 + with message-id and subject line Bug#1019675: fixed in ruby-versionomy 0.5.0-3 has caused the Debian Bug report #1019675, regarding ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. to be marked as done. This means that you

Bug#1019675: marked as pending in ruby-versionomy

2022-11-22 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #1019675 in ruby-versionomy 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#1019675 marked as pending in ruby-versionomy

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1019675 [src:ruby-versionomy] ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. -- 1019675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019675 Debian Bug Tracking System Contact

Processed: src:filezilla: fails to migrate to testing for too long: FTBFS on i386

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.61.0-1 Bug #1024664 [src:filezilla] src:filezilla: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions filezilla/3.61.0-1. Bug #1024664 [src:filezilla] src:filezilla: fails to migrate to testing for too long: FTBFS on

Bug#1024664: src:filezilla: fails to migrate to testing for too long: FTBFS on i386

2022-11-22 Thread Paul Gevers
Source: filezilla Version: 3.60.2-1 Severity: serious Control: close -1 3.61.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1020327 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

2022-11-22 Thread Paul Gevers
Hi all, On 21-11-2022 21:36, Paul Gevers wrote: On 21-11-2022 16:01, Andrius Merkys wrote: On 2022-11-20 18:18, Paul Gevers wrote:  From the BSP in Tilburg, I uploaded the attached NMU to DELAYED/5. Please let me know if I should delay more or cancel. Thanks, IMO this NMU is fine. Similar

Bug#1024661: r-bioc-bitseq: orphaned upstream and blocking BioC 3.16 transition

2022-11-22 Thread Andreas Tille
Source: r-bioc-bitseq Version: 1.40.0+dfsg-1 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org, debia...@lists.debian.org As per upstream https://lists.debian.org/debian-r/2022/11/msg00058.html r-bioc-bitseq is not supported any

Bug#1024651: ruby-gpgme: FTBFS against libgpgme-dev >= 1.18.0-2

2022-11-22 Thread Andreas Metzler
Source: ruby-gpgme Version: 2.0.20-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition^ The package relies on gpgme-config to detect gpgme. gpgme-config has

Processed: Re: [Pkg-utopia-maintainers] Bug#1024275: network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher.

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1024275 [network-manager-openvpn] network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher. Severity set to 'normal' from 'serious' > notforwarded -1 Bug #1024275 [network-manager-openvpn]

Bug#1024275: [Pkg-utopia-maintainers] Bug#1024275: network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher.

2022-11-22 Thread Michael Biebl
Control: severity -1 normal Control: notforwarded -1 Am 16.11.22 um 22:54 schrieb Daniel Serpell: Package: network-manager-openvpn Version: 1.10.2-1 Severity: normal Dear maintainer, After upgrading to 1.10.2-1, I can't connect to the VPN anymore. This is the logs from NetworkManager:

Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'

2022-11-22 Thread Diane Trout
On Tue, 2022-11-22 at 18:24 +0100, Andreas Beckmann wrote: > > There needs to be either a >   Depends: emacs-el (>= 1:28) > or an equivaent >   Breaks: (emacs-el (<< 1:28) > or the installation must be skipped if emacs is too old. So it looks like elpa-snakemake depends on the transient package

Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'

2022-11-22 Thread Andreas Beckmann
Package: elpa-snakemake Version: 2.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install if emacs 27 (currently still in bookworm) is already installed. As per definition of the release team this makes

Bug#1024627: gitlab: Fails to install

2022-11-22 Thread Fabien (Debian)
I've encountered this problem, here is a workaround: apt install omniauth-oauth2=1.7.1

Bug#1022326: marked as done (ruby-combustion: FTBFS: ERROR: Test "ruby3.1" failed. Bundler::GemNotFound: Could not find gem 'mysql2' in locally installed gems.)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 17:04:59 + with message-id and subject line Bug#1022326: fixed in ruby-combustion 1.3.7-1 has caused the Debian Bug report #1022326, regarding ruby-combustion: FTBFS: ERROR: Test "ruby3.1" failed. Bundler::GemNotFound: Could not find gem 'mysql2' in

Processed: tagging 1024632, found 1024632 in 1:24.3.4.1+dfsg-1

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1024632 + upstream fixed-upstream Bug #1024632 [erlang] erlang: CVE-2022-37026 Client Authentication Bypass Added tag(s) upstream and fixed-upstream. > found 1024632 1:24.3.4.1+dfsg-1 Bug #1024632 [erlang] erlang: CVE-2022-37026 Client

Bug#1024647: trac: The versiuon packaged by debian contain a bug fixed upstream that prevent it to work with python3

2022-11-22 Thread Eric Valette
Package: trac Version: 1.5.3+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Afterupgrading and oldoldstable distrib to stable 11.5, becaue of the move to python3 I had to update trac to the sid version as there is not stable version yet. It did not work at all

Bug#1024627: Acknowledgement (gitlab: Fails to install)

2022-11-22 Thread Pirate Praveen
On Tue, Nov 22 2022 at 02:39:40 PM +01:00:00 +01:00:00, Kurt Roeckx wrote: fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab Some of the version requirements for

Bug#1020851: elpa-ement: fails to install along emacs

2022-11-22 Thread Andreas Beckmann
On 28/09/2022 16.55, Sean Whitton wrote: transient is included in Emacs 28 so I'm inclined to leave this to fix itself when Emacs 28 migrates. Can't this be expressed as a package relationship? e.g. Depends: emacs-el (>= 1:28) Andreas

Bug#1023874: marked as done (node-readable-stream: FTBFS: Cannot use import statement outside a module)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 16:35:01 + with message-id and subject line Bug#1023874: fixed in node-readable-stream 4.2.0+~cs9.0.2-1 has caused the Debian Bug report #1023874, regarding node-readable-stream: FTBFS: Cannot use import statement outside a module to be marked as done.

Bug#1024642: pgcharts: FTBFS: Fatal NAME-CONFLICT: [...] PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES

2022-11-22 Thread Andreas Beckmann
Source: pgcharts Version: 1.0+2017-09-16-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source Hi, pgcharts recently started to FTBFS in both testing (emacs 27) and unstable (emacs 28): debian/rules override_dh_auto_build make[1]: Entering directory

Bug#1016633: marked as done (pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value')

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 15:39:20 + with message-id and subject line Bug#1016633: fixed in pyhst2 2020c-6 has caused the Debian Bug report #1016633, regarding pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' to be marked as done. This

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-22 Thread Timo Röhling
Hi Daniel, * Daniel Kahn Gillmor [2022-11-21 19:24]: The attached patch appears to fix things for me so that neomutt builds successfully against libgpgme-dev 1.18.0-3, though i don't know enough about how to adequately test neomutt to be confident in the results (i don't use neomutt myself).

Bug#1024458: marked as done (seqan-needle: binary-all FTBFS)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 14:44:46 + with message-id and subject line Bug#1024458: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-3 has caused the Debian Bug report #1024458, regarding seqan-needle: binary-all FTBFS to be marked as done. This means that you claim that the problem

Bug#1023807: marked as done (seqan-needle: /usr/bin/needle is already shipped by emboss)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 14:44:46 + with message-id and subject line Bug#1023807: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-3 has caused the Debian Bug report #1023807, regarding seqan-needle: /usr/bin/needle is already shipped by emboss to be marked as done. This means that

Bug#1024637: libmartchus-qtforkawesome1: missing Breaks+Replaces: libmartchus-qtforkawesome0.0.3

2022-11-22 Thread Andreas Beckmann
Package: libmartchus-qtforkawesome1 Version: 0.1.0-1~exp1 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'

Processed: Re: libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998228 [src:libretro-snes9x] libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const Added tag(s) pending. -- 998228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998228 Debian Bug Tracking System

Bug#998228: libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const

2022-11-22 Thread Andreas Beckmann
Followup-For: Bug #998228 Control: tag -1 pending Hi, I've just uploaded a NMU to DELAYED/10 fixing this FTBFS. Please let me know if I should delay it longer or cancel it. Andreas

Bug#1024627: Acknowledgement (gitlab: Fails to install)

2022-11-22 Thread Kurt Roeckx
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab

Processed: CVE-2022-37026 fixed in unstable

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1024632 1:24.3.4.5+dfsg-1 Bug #1024632 [erlang] erlang: CVE-2022-37026 Client Authentication Bypass Marked as fixed in versions erlang/1:24.3.4.5+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass

2022-11-22 Thread Markus Koschany
Package: erlang X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for erlang. Initially the security team triaged this issue as minor but further investigation showed the impact might be much more severe. Red Hat and other vendors

Processed: Re: tome: FTBFS with GCC 10 due to insufficient #includes

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #966065 [src:tome] tome: FTBFS with GCC 10 due to insufficient #includes Added tag(s) pending. -- 966065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966065: tome: FTBFS with GCC 10 due to insufficient #includes

2022-11-22 Thread Andreas Beckmann
Followup-For: Bug #966065 Control: tag -1 pending Hi, I've just uploaded a NMU to DELAYED/10 fixing this FTBFS. Please let me know if I should delay it longer or cancel it. Andreas

Bug#1024627: gitlab: Fails to install

2022-11-22 Thread Kurt Roeckx
Package: gitlab Version: 15.4.2+ds1-1~fto11+3 Severity: serious Setting up gitlab (15.4.2+ds1-1~fto11+3) ... Bundler could not find compatible versions for gem "omniauth-oauth2": In Gemfile: omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on omniauth-oauth2 (~> 1.4)

Bug#1019652: marked as done (ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result[1]).to eq token)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 13:08:53 + with message-id and subject line Bug#1019652: fixed in ruby-regexp-parser 2.1.1-2.1 has caused the Debian Bug report #1019652, regarding ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Bug#1005422: marked as done (ruby-redis-store: FTBFS: ERROR: Test "ruby2.7" failed.)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 13:08:46 + with message-id and subject line Bug#1005422: fixed in ruby-redis-store 1.9.0-2 has caused the Debian Bug report #1005422, regarding ruby-redis-store: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the

Bug#1024626: blender FTBFS on 32bit

2022-11-22 Thread Adrian Bunk
Source: blender Version: 3.3.1+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=blender=3.3.1%2Bdfsg-1 Different errors on different architectures, e.g. ... In file included from /<>/obj-mipsel-linux-gnu/source/blender/makesdna/intern/dna_verify.c:2:

Processed: Re: Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated

2022-11-22 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/csound/csound/issues/1651 Bug #1024169 [src:csound, src:csound-plugins] csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated Set Bug forwarded-to-address to

Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated

2022-11-22 Thread Nilesh Patra
Control: forwarded -1 https://github.com/csound/csound/issues/1651 On Tue, 15 Nov 2022 23:50:51 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: > this looks like caused by a disaggrement about the size of type OPARMS. > In libcsound64-6.0 it has 264 bytes, but in csound-plugins > only 260

Processed: tagging 1024561, tagging 1024576, tagging 1024497, found 1024555 in 4.1.0-0.1, tagging 1024506 ...

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1024561 + sid bookworm Bug #1024561 [src:maradns] Unmaintained, keep out of stable Added tag(s) sid and bookworm. > tags 1024576 + sid bookworm Bug #1024576 [src:librepo] librepo: FTBFS against libgpgme-dev >= 1.18.0-2 Added tag(s) sid and

Processed: retitle 732570 to RM: libarch-perl -- RoM; dead upstream, very low popcon count

2022-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 732570 RM: libarch-perl -- RoM; dead upstream, very low popcon count Bug #732570 [ftp.debian.org] libarch-perl should be removed Changed Bug title to 'RM: libarch-perl -- RoM; dead upstream, very low popcon count' from 'libarch-perl

Bug#1023046: marked as done (zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod))

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 10:07:40 + with message-id and subject line Bug#1023046: fixed in zabbix 1:6.0.10+dfsg-1 has caused the Debian Bug report #1023046, regarding zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod) to be marked as done.

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

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 09:51:39 + with message-id and subject line Bug#983815: fixed in python-crc32c 2.3-1.1 has caused the Debian Bug report #983815, regarding python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on armhf if built on 64bit hardware to be marked as

Bug#1023959: marked as done (python-crc32c ftbfs on arm64)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 09:51:39 + with message-id and subject line Bug#983815: fixed in python-crc32c 2.3-1.1 has caused the Debian Bug report #983815, regarding python-crc32c ftbfs on arm64 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1024000: marked as done (pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 09:51:28 + with message-id and subject line Bug#1024000: fixed in pink-pony 1.4.1-3.1 has caused the Debian Bug report #1024000, regarding pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1 to be marked as done. This means that you

Bug#1023999: marked as done (stormbaancoureur: build-depends on missing: plib1.8.4-dev)

2022-11-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Nov 2022 09:51:56 + with message-id and subject line Bug#1023999: fixed in stormbaancoureur 2.1.6-3.1 has caused the Debian Bug report #1023999, regarding stormbaancoureur: build-depends on missing: plib1.8.4-dev to be marked as done. This means that you claim that

Bug#1020153: magit: FTBFS: make[2]: *** [Makefile:111: test] Error 255

2022-11-22 Thread intrigeri
Hi, I ended up here after realizing that a bunch of Emacs packages I use got removed from testing due to this bug. Lucas Nussbaum (2022-09-18): > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): >> make[2]: Entering directory