Bug#1049806: mozc: Fails to build binary packages again after successful build

Control: tags -1 unreproducible Hi, > > /usr/lib/x86_64-linux-gnu/libprotobuf.a(arena.o): relocation > > R_X86_64_TPOFF32 against symbol > > `_ZN6google8protobuf8internal15ThreadSafeArena13thread_cache_E' can > > not be used when making a shared object; recompile with -fPIC > > /usr/bin/ld:

Bug#1045435: mozc: Fails to build source after successful build

s > User: lu...@debian.org > Usertags: ftbfs-sab-20230813 ftbfs-source-after-build > User: debian...@lists.debian.org > Usertags: qa-doublebuild > >From 987fc8f5ffe6a9bb2f9d163b557db67b0180d655 Mon Sep 17 00:00:00 2001 From: Kentaro Hayashi Date: Sun, 19 May 2024 21:49:36 +0900 Sub

Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared

Hi, On Fri, 17 May 2024 21:16:15 +0900 Kentaro HAYASHI wrote: > Control: tags -1 patch > > On Fri, 17 May 2024 14:06:37 +0900 Kentaro HAYASHI > > > This issue was already fixed in upstream. > > > > Non-public Abseil API is used for CLI parsing > > h

Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared

Control: tags -1 patch On Fri, 17 May 2024 14:06:37 +0900 Kentaro HAYASHI > This issue was already fixed in upstream. > > Non-public Abseil API is used for CLI parsing > https://github.com/google/mozc/issues/790 > > Above ftbfs error was fixed with the following commi

Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared

Control: tags -1 fixed-upstream Hi, On Mon, 1 Apr 2024 15:35:41 +0200 Sebastian Ramacher wrote: > Source: mozc > Version: 2.28.4715.102+dfsg-2.2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in > the past) X-Debbugs-Cc:

Bug#1071048: rust-coreutils: FTBFS on armhf,armel (`timespec` with struct literal syntax due to private fields)

Source: rust-coreutils Severity: serious Tags: ftbfs Control: found -1 0.0.26-1 Dear Maintainer, rust-coreutils fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-coreutils=armel=0.0.26-1=1714571498=0

Bug#1071046: rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity)

Source: rust-mimalloc Severity: serious Tags: ftbfs Control: found -1 0.1.29-1+b2 Dear Maintainer, rust-mimalloc fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-mimalloc=armhf=0.1.29-1%2Bb2=1714283560=0 Regards,

Bug#1071044: rust-libmimalloc-sys : FTBFS on armhf (signal: 11, SIGSEGV: invalid memory reference)

Source: rust-libmimalloc-sys Severity: serious Tags: ftbfs Control: found -1 0.1.25-1+b2 Dear Maintainer, rust-libmimalloc-sys fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-libmimalloc-sys=armhf=0.1.25-1%2Bb2=1714271391=0 Regards,

Bug#1059706: epics-base.pc is still broken

17 00:00:00 2001 From: Kentaro Hayashi Date: Sat, 4 May 2024 21:39:41 +0900 Subject: [PATCH 1/2] debian/rule: fix embedded path of installed path Without this change, build root path will be embedded into epics-base.pc. See documentation/RELEASE_NOTES.md. Signed-off-by: Kentaro Hayashi --- deb

Bug#1059706: epics-base.pc is still broken

Hi, On Wed, 10 Apr 2024 16:31:03 +0300 Andrius Merkys wrote: > control: reopen -1 > control: found -1 7.0.8+dfsg1-1 > > Hello, > > As epics-base.pc still contains incorrect paths, I am reopening this > bug. Maybe FINAL_LOCATION=/usr must be specified in debian/rules.

Bug#1069347: rust-servo-freetype-sys: FTBFS on armel,armhf CMake Error: The source directory "/<>/freetype2" does not exist.

Source: rust-servo-freetype-sys Severity: serious Tags: ftbfs Control: found -1 4.0.5-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, rust-servo-freetype-sys fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-servo-freetype-sys=armel=4.0.5-2=1688825741=0

Bug#1069345: qwinff : FTBFS on armel,armhf

Source: qwinff Severity: important Tags: ftbfs Control: found -1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, qwinff fails to build on armhel,armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=qwinff=armel=0.2.1%2Bgit20201215-2=1685891638=0

Bug#1069344: netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test]

Source: netgen Severity: serious Tags: ftbfs Control: found -1 6.2.2401+dfsg1-1.1+b1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, netgen fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=netgen=armhf=6.2.2401%2Bdfsg1-1.1%2Bb1=1712667539=0 Regards,

Bug#1068928: lammps : FTBFS on armhf (undefined symbol: pmix_value_load or error: subprocess-exited-with-error)

Source: lammps Severity: important Tags: ftbfs Control: found -1 20240207+dfsg-1.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, lammps fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=lammps=armhf=20240207%2Bdfsg-1.1%2Bb1=1712551793=0 Note that build error

Bug#1068925: macromoleculebuilder: FTBFS on armhf (error: inconsistent deduction for auto return type: 'long int' and then 'long long int')

Source: macromoleculebuilder Severity: important Tags: ftbfs Control: found -1 4.0.0+dfsg-3.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, macromoleculebuilder fails to build on armhf. FYI:

Bug#1068327: flexc++: FTBFS on armel, armhf (Segmentation fault)

Source: flexc++ Severity: serious Tags: ftbfs Control: found -1 2.15.00-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, flexc++ fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=flexc%2B%2B=armel=2.15.00-1=1712127698=0

Bug#1068325: bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)

Source: bisonc++ Severity: serious Tags: ftbfs Control: found -1 6.08.00-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, bisonc++ fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=bisonc%2B%2B=armel=6.08.00-1=1712127818=0

Bug#1068067: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))

Source: fpzip Severity: serious Tags: ftbfs Control: found -1 1.3.0-3 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, fpzip fails to build on armel, armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=fpzip=armel=1.3.0-3=1685884820=0

Bug#1068066: docker-registry: FTBFS on armhf (test failure with DriverSuite.TestDeleteOnlyDeletesSubpaths)

Source: docker-registry Severity: serious Tags: ftbfs Control: found -1 2.8.2+ds1-1+b4 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, docker-registry fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=docker-registry=armhf=2.8.2%2Bds1-1%2Bb4=1704669577=0 Regards,

Bug#1068065: quorum: FTBFS on armel, armhf,i386 (error: no matching function for call to ‘min(const long long unsigned int&, unsigned int)’)

Source: quorum Severity: serious Tags: ftbfs Control: found -1 1.1.2-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, quorum fails to build on armel, armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=quorum=armel=1.1.2-2=1701603381=0

Bug#1068063: sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x)

Source: sssd Severity: serious Tags: ftbfs Control: found -1 2.9.4-1.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, sssd fails to build on armel, armhf. Though test suite failure was already reported, but target version is 1.11.5.1-1, not 2.x branch. so I've filed as a new bug to raise

Bug#1068058: libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb failed)

Source: libgtkada Severity: serious Tags: ftbfs Control: found -1 24.0.0-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, libgtkada fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=libgtkada=armhf=24.0.0-2=1710988310=0 Regards,

Bug#1068057: libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! )

Source: libgtkada Severity: serious Tags: ftbfs Control: found -1 24.0.0-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, libgtkada fails to build on armel. FYI: https://buildd.debian.org/status/fetch.php?pkg=libgtkada=armel=24.0.0-2=1711025590=0 Regards,

Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')

Control: notfound -1 2.6.0-1

Bug#1041803: [Debian-pan-maintainers] Bug#1041803: hyperspy: FTBFS test_image fails

Control: tags -1 ftbfs

Bug#1068056: ccls: FTBFS on armhf,i386 (test_response failures)

Source: ccls Severity: serious Tags: ftbfs Control: found -1 0.20230717-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, ccls fails to build on armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=ccls=armhf=0.20230717-1=1694985920=0

Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')

Control: found -1 Control: found -1 0.20230717-1

Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')

Source: ccls Severity: serious Tags: ftbfs Control: found -1 2.6.0-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, ccls fails to build on armel. (missing linking against with -latomic) FYI: https://buildd.debian.org/status/fetch.php?pkg=ccls=armel=0.20230717-1=1694985537=0 Regards,

Bug#1068054: rauc: FTBFS on armel, armhf (1 test failure)

Source: rauc Severity: serious Tags: ftbfs Control: found -1 1.11.3-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, rauc fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rauc=armel=1.11.3-1=1710786055=0

Bug#1068053: postsrsd: FTBFS on armel, armhf (bats run_postsrsd_tests.bats failure)

Source: postsrsd Severity: serious Tags: ftbfs Control: found -1 1.10-2.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, postsrsd fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=postsrsd=armel=1.10-2.1=1710920668=0

Bug#1068052: openms: FTBFS on armel,armhf (error: ‘QOpenGLFunctions_2_0’ does not name a type)

Source: openms Severity: serious Tags: ftbfs Control: found -1 2.6.0+cleaned1-4 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, openms fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=openms=armel=2.6.0%2Bcleaned1-4=1703355142=0

Bug#1068051: tilix: FTBFS on armhf, s390x (undefined reference to `_D4core8internal5array8equality...)

Source: tilix Severity: serious Tags: ftbfs Control: found -1 1.9.6-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, tilix fails to build on armhf, s390x. FYI: https://buildd.debian.org/status/fetch.php?pkg=tilix=armhf=1.9.6-2=1711367535=0

Bug#1067959: sambamba: FTBFS on armhf (supported compiler issue)

Source: sambamba Severity: serious Tags: ftbfs Control: found -1 1.0.1+dfsg-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, sambamba fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=sambamba=armhf=1.0.1%2Bdfsg-1=1699230688=0 Regards,

Bug#1067958: ruy: FTBFS on armel, armhf

Source: ruy Severity: serious Tags: ftbfs Control: found -1 0.0.0~git20230215.21a85fe-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, ruy fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=ruy=armel=0.0.0%7Egit20230215.21a85fe-1=1688810281=0

Bug#1067956: rocalution: FTBFS on armhf (test failure with memory allocation)

Source: rocalution Severity: serious Tags: ftbfs Control: found -1 5.7.1-2 Control: user -1 debian-...@lists.debian.org Control: usertags -1 + armhf X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, rocalution fails to build on armhf. FYI:

Bug#1067954: openmesh: FTBFS on armel,armhf

Source: openmesh Severity: serious Tags: ftbfs Control: found -1 9.0-4 Control: user -1 debian-...@lists.debian.org Control: usertags -1 + armel armhf X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, openmesh fails to build on armel, armhf. FYI

Bug#1067952: mes: FTBFS on armhf

Source: mes Severity: serious Tags: ftbfs Control: found -1 0.26-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, mes 0.26-1 fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=mes=armhf=0.26-1=1704511792=0 Regards,

Bug#1067603: contextfree: FTBFS on armhf: test failure with missing codec

Hi, On Wed, 27 Mar 2024 20:58:51 -0700 John Horigan wrote: > That error message indicates that libavcodec60 does not support the > libx264 codec for encoding H.264 files. libavcodec60 lists > libx264-164 as a dependency, with no exception for armel or armhf > systems, so I don't know why the

Bug#1067839: triton: FTBFS on armel (undefined reference to symbol '__atomic_compare_exchange_4@@LIBATO)

Control: severity -1 serious Change severity because of ftbfs.

Bug#1067841: libopenshot-audio: FTBFS on armel (error: static assertion failed)

Source: libopenshot-audio Severity: important Tags: ftbfs X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, libopenshot-audio fails to build on armel. FYI: See https://buildd.debian.org/status/fetch.php?pkg=libopenshot-audio=armel=0.3.2%2Bdfsg1-2.1=1709160782=0

Bug#1067839: triton: FTBFS on armel (undefined reference to symbol '__atomic_compare_exchange_4@@LIBATO)

Source: triton Version: 2.0.0.post1-4 Severity: important Tags: ftbfs X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, triton fails to build on armel. FYI: https://buildd.debian.org/status/fetch.php?pkg=triton=armel=2.0.0.post1-4=1708226979=0 /usr/bin/ld:

Bug#1067837: tremotesf: FTBFS on armel (dh_auto_build: error: ninja -j8 -v returned exit code 1)

Source: tremotesf Severity: serious Tags: ftbfs Control: found -1 2.6.0-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, tremotesf fails to build on armel. FYI: https://buildd.debian.org/status/fetch.php?pkg=tremotesf=armel=2.6.0-1=1705039418=0 [96/131] /usr/bin/c++ -DFMT_SHARED

Bug#1067603: contextfree: FTBFS on armhf: test failure with missing codec

Package: contextfree Version: 3.4+dfsg-1.1 Severity: important Tags: ftbfs X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? contextfree can't build on armel,armhf. * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#1066519: buildd.debian.org: giveback script doesn't allow to give-back packages in "Installed" state

Package: buildd.debian.org X-Debbugs-Cc: ken...@xdump.org Severity: normal Dear Maintainer, * What led up to the situation? giveback.cgi script doen't accept giveback action in "Installed" state. e.g. https://buildd.debian.org/auth/giveback.cgi?pkg=zeromq3=armhf=sid * What

Bug#1066031: Your mail

Control: retitle -1 nmu: zeromq3 It seems that it should be nmu instead of gb because currently they are "Installed" state. As buildd given-back action says: > Package in state Installed, cannot giveback. ✗ nmu zeromq3_4.3.5-1+b1 . ANY . unstable . -m "Rebuild to sync with 64bit time_t

Bug#1066031: Your mail

Control: retitle -1 gb: zeromq3 Regards, On Mon, 11 Mar 2024 20:59:54 +0900 Kentaro HAYASHI wrote: > Package: release.debian.org > Control: affects -1 + src:zeromq3 > X-Debbugs-Cc: zero...@packages.debian.org > User: release.debian@packages.debian.org > Usertags: binnmu >

Bug#1066031: (no subject)

Package: release.debian.org Control: affects -1 + src:zeromq3 X-Debbugs-Cc: zero...@packages.debian.org User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: ken...@xdump.org Severity: normal libzmq5 depends on obsolete runtime libraries. $ apt-cache depends libzmq5

Bug#1065647: lists.debian.org: Refresh list of category in https://lists.debian.org/

Package: lists.debian.org Severity: normal X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? Currently, list of category in https://lists.debian.org are like this: * Debconf * Users * Developers * Internationalization and Translations * Ports * Bug

Bug#1064956: libh3-dev: Using find_package(h3) can't be resolved

Package: libh3-dev Severity: important X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? It seems that Using find_package(h3) can't be resolved correctly. This bug found in the following version. $ dpkg -l |grep libh3 ii libh3-1:amd64

Bug#1064823: libvte-2.91-gtk4-0: Please enable SIXEL support when rendering regression issue was resolved in upstream

Package: libvte-2.91-gtk4-0 Version: 0.75.91-2 Severity: normal X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? It seems that there is sixel support, but not enabled yet. https://gitlab.gnome.org/GNOME/vte/-/commits/master?ref_type=heads In

Bug#1062131: groonga: NMU diff for 64-bit time_t transition

NOTE: I've found the SEGV issue with 13.1.1+dfsg-1 on armhf. With patched abi=+time64 version 13.1.1+dfsg-1.2 in experimental, the issue was resolved. Before: 13.1.1+dfsg-1 on armhf groonga db/test < load-last-modified.grn [[0,1708379668.191548,0.02317619323730469],1]

Bug#1056354: python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0

Control: fixed -1 0.4.0-1 This bug was fixed in hinawa-utils 0.4.0-1. On Tue, 21 Nov 2023 17:09:35 +0200 Adrian Bunk wrote: > Package: python3-hinawa-utils > Version: 0.3.0-3 > Severity: serious > > src:libhinawa now builds gir1.2-hinawa-4.0 instead of > gir1.2-hinawa-3.0 > >

Bug#1062131: groonga: NMU diff for 64-bit time_t transition

Thanks, According to https://github.com/groonga/groonga/discussions/1698, it will not affected during 64bit time_t transition in practical use case. There are some points. * time_t is used but the value of it was treated as 64bit value internally. (See GRN_TIME_PACK. it use int64_t) *

Bug#1061104: xtl-dev is not installed with libxsimd-dev transparently (missing Depends:)

FYI: I've created MR. debian: require xtl-dev with runtime https://salsa.debian.org/science-team/xsimd/-/merge_requests/4 Regards,

Bug#1061104: xtl-dev is not installed with libxsimd-dev transparently (missing Depends:)

Package: libxsimd-dev Version: 10.0.0-3 Severity: important X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? libxsimd-dev requires xtl-dev with Build-Depends: but it should be Depends: so it does not require xtl-dev: $ apt depends libxsimd-dev

Bug#1059075: lltsv: Please add loong64 binary output for Loongarch

Control: close 1059075 Duplicate report of #1059025.

Bug#1059025: lltsv: add build support for loongarch64

Control: block 1059025 by 1055087 FYI: No loong64 support for golang yet. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055087 https://buildd.debian.org/status/package.php?p=golang%2d1%2e21

Bug#1052037: fixed in fasttext 0.9.2+ds-6

Control: found -1 0.9.2+ds-6 >* debian/patches/explicitly-link-libatomic.patch > - Fix import error on armel (Closes: #1052037) It was inappropriate a bit. If LD_PRELOAD was set, it was overlooked.

Bug#1059350: debian-keyring: missing update since 2023.09.24

On Sat, 23 Dec 2023 07:23:12 + Jonathan McDowell wrote: > The debian-keyring package is a convenience package and we only make > efforts to ensure it is up to date around release time. The actual > keyring used by the Debian infrastructure is served via rsync and > matches the version that is

Bug#1059350: debian-keyring: missing update since 2023.09.24

Package: debian-keyring X-Debbugs-Cc: ken...@xdump.org Version: 2023.09.24 Severity: normal Dear Maintainer, * What led up to the situation? debian-keyring package has not updated for a while. (last update was debian-keyring 2023.09.24) * What exactly did you do (or not do) that was effective

Bug#1058535: libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25

On Tue, 12 Dec 2023 21:51:47 +0100 Lucas Nussbaum wrote: > Source: libhinawa > Version: 4.0.0-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231212 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package

Bug#1056585: RM: hinawa-utils/0.3.0-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: ken...@xdump.org Here is the some reasons to remove hinawa-utils from testing: * The hinawa-utils depends on libhinawa (2.x), and the newer release of libhinawa (4.x) drops

Bug#1042697: Your mail

Control: fixed -1 13.0.9+dfsg-1 I've forgot to close with uploaded version. On Sat, 5 Aug 2023 15:14:10 +0900 Kentaro HAYASHI wrote: > NOTE for sphinx 7 when it is landed into sid: > > * doc/files.am should be patched to eliminate jquery.js and > underscore.js dependency or

Bug#1054433: node-puppeteer: website is build with Docusaurus not packaged for debian

Control: severity -1 important Hi, It seems that already repacked. Surely regenerating omitted content (website and docs) may be recommended in the future, so marked as important. Regards,

Bug#1050554: budgie-desktop: after logging to budgie desktop, taskbar becomes unresponsive

Package: budgie-desktop Version: 10.8-2 Severity: important X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? Just logging into budgie desktop and wait for minutes. * What exactly did you do (or not do) that was effective (or ineffective)? 1. Just logging into

Bug#1049999: vagrant: the future of packaging vagrant in Debian

Package: vagrant Version: 2.3.4+dfsg-1 Severity: normal X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? HashiCorp adopts the BSL. https://ir.hashicorp.com/news-releases/news-release-details/hashicorp-adopts- business-source-license-future-releases-its

Bug#967462: growl-for-linux: depends on deprecated GTK 2

Thank you for contribution. It seems that the fix is reasonable. On Mon, 24 Jul 2023 14:04:03 +0200 Bastian Germann wrote: > Control: unblock 967462 by -1 > > I am uploading a NMU to DELAYED/10 to get rid of the build dependency > libayatana-appindicator, which is not needed. The debdiff is

Bug#1042697: (no subject)

NOTE for sphinx 7 when it is landed into sid: * doc/files.am should be patched to eliminate jquery.js and underscore.js dependency or use python3-sphinxcontrib.jquery and so on. * debian/control * add missing libjs-sphixdoc dependency. * debian/groonga-doc.links should be updated. * drop

Bug#1037256: debian-installer: GUI font for Japanese was incorrectly rendered

FYI: I've updated a PoC patch. Mainly the explanation of patch was updated. 0001-frontend-avoid-han-unification-for-Japanese-take2.patch >From b388a793b19a0afeb9110a6dd7633b1734ffb759 Mon Sep 17 00:00:00 2001 From: Kentaro Hayashi Date: Wed, 7 Jun 2023 17:50:40 +0900 Subject: [PATCH] front

Bug#1037256: debian-installer: GUI font for Japanese was incorrectly rendered

FYI: I've posted a message to ML for collecting feedback. Proposal: change Japanese font for GUI installer https://lists.debian.org/debian-boot/2023/06/msg00224.html Regards,

Bug#1037256: debian-installer: GUI font for Japanese was incorrectly rendered

On Fri, 9 Jun 2023 22:02:16 +0900 Kentaro Hayashi wrote: > Prerequisite for fix issue: > > Step1: Bundle MotoyaLCedar (MTLc3m.ttf) for fonts-android-udeb. > Step2: Apply this patch for cdebconf package As MotoyaLCedar is packaged as fonts-motoya-l-cedar already, making fonts-mo

Bug#1038387: bookworm-pu: package groonga/13.0.0+dfsg-2~deb12u1

Package: release.debian.org Control: affects -1 + src:groonga User: release.debian@packages.debian.org Usertags: pu Tags: bookworm X-Debbugs-Cc: ken...@xdump.org Severity: normal [ Reason ] This request is aimed to fix broken symlink issue which is originally reported [1] during bookworm

Bug#1026886: watch file for packages on github

Control: tags -1 wontfix > > Anyway, it may be a trivial exceptional case, so I'll close it.

Bug#1026886: watch file for packages on github

Hi, > It is possible to write watch files dealing with pre-releases without using > fakeupstream.cgi. Here are some variants: > ... > > The 'failure scenario' describes just one of many mistakes upstream can make, > and fakeupstream.cgi isn't meant to correct such upstream human mistakes. It

Bug#1033407: duplicate bugs

FYI: It seems this bug was fixed in #1032989, so this bug also have to be closed. NOTE: this fix is not landed to bookworm yet. On Sat, 25 Mar 2023 13:20:27 +0100 Dominik Stadler wrote: > merge 1033407 1032989 > > -- > These two bug-reports sound very similar, #1032989 has a lot of >

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

Hi, On Thu, 2 Mar 2023 09:42:36 + Simon McVittie wrote: > Control: tags -1 + moreinfo > snip > > Is there consensus among Japanese-speaking users of Debian that mozc is > a better default for all Japanese speakers, including new users who are > not familiar with GNOME or Debian? At

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

Hi, On Wed, 01 Mar 2023 16:47:22 + James Addison wrote: > Package: libgnome-desktop-4-2 > Followup-For: Bug #1029821 > X-Debbugs-Cc: yy.y.ja...@gmail.com > > I'd like to contribute by testing d-i with Japanese input (I'm not a Japanese > speaker, but can offer some time to help). > > My

Bug#1000130: condor: depends on obsolete pcre3 library

FYI: It seems that this issue was fixed in version 9.10.0 https://htcondor.readthedocs.io/en/latest/version-history/development-release-series-91.html#version-9-10-0

Bug#1000129: maildrop: depends on obsolete pcre3 library

FYI: It seems that changes are already merged into master, but not ready to upload yet. https://salsa.debian.org/debian/maildrop/-/commit/16c6b1bf9f660ff2e195a87840922162b9bef84c

Bug#1026886: fakeupstream.cgi: support functionality to ignore pre-release on GitHub.com

FYI: I've sent a merge request https://salsa.debian.org/qa/qa/-/merge_requests/43

Bug#1026886: fakeupstream.cgi: support functionality to ignore pre-release on GitHub.com

Package: qa.debian.org Severity: normal X-Debbugs-Cc: ken...@xdump.org # Problem Currently, it seems that there is no comprehensive way to ignore pre-release on GitHub.com [1] Adding a feature upstream=github_releases to avoid unexpected failure to do packaging pre-release as an official

Bug#1014314: lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail

FYI: similar issue was reported in the past lvm2: initramfs generation fails if neither /etc/udev/rules.d/69-lvm-metad.rules nor /lib/udev/rules.d/69-lvm-metad.rules exists https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881916

Bug#1010465: aptly doesn't support zstd compressed packages

Package: aptly Version: 1.4.0+ds1-6+b1 Severity: normal Tags: upstream X-Debbugs-Cc: ken...@xdump.org # Problem aptly cannot handle Zstandard compressed control.tar.zst and data.tar.zst within debian package. # How to reproduce Apply aptly repo add command which contains Zstd compressed

Bug#1008525: peek: SEGV when starting record with backend=gnome-shell

Package: peek Version: 1.5.1+git20211214-1 Severity: important X-Debbugs-Cc: ken...@xdump.org # Problem When starting capture, it causes SEGV. It seems that it does not depends on supported formats. gif, apng, webm, mp4, all of them will crash. When using with --backend=ffmpeg, SEGV does not

Bug#999609: budgie-desktop: ALt+Shift_L causes budgie-wm SEGV

FYI: PR was merged into budgie-desktop, now. On Wed, 23 Feb 2022 17:49:50 +0900 Kentaro Hayashi wrote: > > I've sent a PR to fix this issue. > > Fix SEGV when input source was switched by Alt+Shift_L > https://github.com/BuddiesOfBudgie/budgie-desktop/pull/61 > >

Bug#1005444: ruby-webauthn: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `rescue in block in activate_dependencies': Could not find 'openssl' (~>

FYI: upstream try to support OpenSSL gem requirement 2.2 or later, but there is a compatibility issue. Bump OpenSSL gem requirement to 2.2 #324 https://github.com/cedarcode/webauthn-ruby/pull/324 Regards,

Bug#990577: ruby-bindata: CVE-2021-32823

Hi, Trying to upgrade to ruby-bindata 2.4.10, meta/build reports the following: inished in 0.406237s, 1836.3670 runs/s, 20507.7387 assertions/s. 746 runs, 8331 assertions, 0 failures, 0 errors, 0 skips mv ./.gem2deb.lib lib autopkgtest [14:40:10]: test gem2deb-test-runner:

Bug#995354: Requires to package ruby-thread-local

At least, updating to async-http 0.56.0 or later will satisfy dependency. https://rubygems.org/gems/async-http/versions/0.56.0 async-http 0.56.0 or later requires protocol-http >= 0.22.0 < 0.23, but ruby-protocol-http 0.22.5-1 is packaged in sid. It also adds new development dependency for

Bug#999609: budgie-desktop: ALt+Shift_L causes budgie-wm SEGV

On Mon, 21 Feb 2022 09:29:05 + David Mohammed wrote: > Raised upstream for you > https://github.com/BuddiesOfBudgie/budgie-desktop/issues/56 > Thanks. I've sent a PR to fix this issue. Fix SEGV when input source was switched by Alt+Shift_L

Bug#999609: budgie-desktop: ALt+Shift_L causes budgie-wm SEGV

As for 10.5.3+git20220217a-1, it seems that Workaround 2 is not effective anymore. On Sat, 13 Nov 2021 22:37:32 +0900 Kentaro Hayashi wrote: > Package: budgie-desktop > Version: 10.5.3-4 > Severity: important > X-Debbugs-Cc: ken...@xdump.org > > > * Workaround2

Bug#995607: ITP: libfreeaptx -- Free implementation of Audio Processing Technology codec (aptX)

Now in new queue. https://ftp-master.debian.org/new.html

Bug#995607: ITP: libfreeaptx -- Free implementation of Audio Processing Technology codec (aptX)

Hi, Rejected by missing appropriate copyright, so I've tried re-uploading again. > Hello, > > Any news about the packaging of this library? > > Kind regards, >

Bug#1000013: nginx: depends on obsolete pcre3 library

FYI: https://forum.nginx.org/read.php?29,281263,292622#msg-292622 It seems that it taks a time to be ready PCRE2 support.

Bug#997189: liboping: FTBFS: oping.c:1159:25: error: format not a string literal and no format arguments [-Werror=format-security]

FYI: For the latter case, it seems that it has already submitted a fix as a PR. See https://github.com/octo/liboping/pull/60/files On Sat, 23 Oct 2021 21:06:58 +0200 Lucas Nussbaum wrote: > > oping.c: In function ‘update_host_hook’: > > oping.c:1640:38: error: too many arguments for format > >

Bug#999609: budgie-desktop: ALt+Shift_L causes budgie-wm SEGV

Package: budgie-desktop Version: 10.5.3-4 Severity: important X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, * What led up to the situation? Typing specific combination key causes budgie-wm segfault. At most twice or so is enough to reproduce this issue. * What exactly did you

Bug#993615: ITP: golang-github-slack-go-slack -- This is Slack API in Go

Control: owner -1 Takuma Shibuya

Bug#993615: ITP: golang-github-slack-go-slack -- This is Slack API in Go

Control: reassign -1 wnpp Control: severity -1 wishlist Control: owner -1 shib5%40gmail.com

Bug#995607: ITP: libfreeaptx -- Free implementation of Audio Processing Technology codec (aptX)

Package: wnpp Severity: wishlist Owner: Kentaro Hayashi X-Debbugs-Cc: debian-de...@lists.debian.org, ken...@xdump.org * Package name: libfreeaptx Version : 0.1.1 Upstream Author : Hunter Wardlaw * URL : https://github.com/iamthehorker/libfreeaptx * License

Bug#978916: varnish: ftbfs with autoconf 2.70

FYI: It is still reproducible on unstable with: * varnish 6.5.2-1 * autoconf 2.71-2 It seems that autoreconf generates broken configure. (without autoreconf, ./configure just works) I'm not sure but in source tree, m4/ax_pthread.m4 around AC_CACHE_CHECK([for PTHREAD_PRIO_INHERIT], causes the

Bug#992610: dh-make-golang make fails when no main, no external module

dependency Message-Id: <20210824220059.fd903aa6fb90557a5d7d4...@xdump.org> In-Reply-To: <20210821135114.e63a59d4081f25cf08081...@xdump.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit

  1   2   3   4   >