Control: tags -1 patch
Hi, attached patch will solve FTBFS.
I hope it will help you.
Regards,
Description: Fix FTBFS #1081856 invalid conversion pointer
Fix FTBFS #1081856 invalid conversion pointer, this error
was raised from agg_font_freetype.cpp because of type mismatch
with 'unsigned char
Recently, I've also hit this bug.
This bug was already fixed in upstream but not released yet.
I hope patch was applied in Debian because it breaks idempotence.
FYI:
copy module: modify time on the file (mtime) is not updating
https://github.com/ansible/ansible/issues/83013
Regards,
Hi,
I've stepped on this bug on 6.10.6-1 and it seems that this
bug was fixed by 6.10.7-1.
I guess the following change affects us, but I'm not sure yet.
https://tracker.debian.org/news/1561446/accepted-linux-signed-amd64-61071-source-into-unstable/
> - Bluetooth: HCI: Invert LE State quirk to
FYI:
It seems that this FTBFS issue was already fixed in master, but not
released yet.
https://salsa.debian.org/nlp-ja-team/mecab/-/commit/0c8c0d1b3730758ef0ea98927e25c12596e39cf9
Regards,
On Fri, 9 Aug 2024 14:16:05 +0200 Santiago Vila
wrote:
> Package: src:docker.io
> Version: 26.1.4+dfsg1-9
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to
> build:
FYI: It seems that go install fails like this:
go
There was feedback about gr- namespace.
It seems that gr- namespace is already used for GNU Radio.
https://lists.debian.org/debian-devel/2024/08/msg00084.html
It might better to improve short description.
Package: wnpp
Severity: wishlist
Owner: Kentaro Hayashi
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: gr-framework
Version : 0.73.7
Upstream Contact: Josef Heinen
* URL : https://github.com/sciapp/gr
* License : MIT
Programming Lang: C
Hi,
It seems that it becomes serious because mutter 46 was landed onto
unstable.
we can't fresh install bugdie-desktop anymore...
Any progress?
This FTBFS was caused by rapidjson [1]
and fixed-in-upstream. [2]
It seems that upstream will not ship new one,
so need to wait patched version of rapidjson.
[1] rapidjson: FTBFS with GCC-14
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075575
[2]
https://github.com/Tencent/rapidjson/pul
Hi,
FYI: I've created MR to send this feedback.
https://salsa.debian.org/debian/lz4/-/merge_requests/8
Regards,
Hi,
On Mon, 17 Jun 2024 22:12:24 +0900 Kentaro HAYASHI
wrote:
> Control: tags -1 patch
>
> Hi, I've tried a PoC patch to build lz4 with CMake.
>
> It is not fully achieved yet because
> it causes a diff for .symbols, that is not intended.
>
> In other wor
Hi,
On Mon, 29 Apr 2024 15:41:02 +0200 Daniel Leidert
wrote:
> Package: remmina
> Version: 1.4.35+dfsg-1+b1
> Severity: serious
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> when I try to connect to a windows (11) system, I get errors saying
> something like "check security
0 2024-04-03 02:18
./usr/lib/x86_64-linux-gnu/liblz4.so -> liblz4.so.1
Anyway, I hope it will help to make it forward.
>From bbd1377d5ffcc2155909a6ce22142bc23612f5e4 Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi
Date: Mon, 17 Jun 2024 21:58:30 +0900
Subject: [PATCH] Use CMake to build
Source: lz4
Version: 1.9.4-2
Severity: normal
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
* What led up to the situation?
Currently, liblz4-dev does not ship lz4Config.cmake which is
used to find LZ4 from CMake.
* What exactly did you do (or not do) that was effective (or
ineff
Control: tags -1 pending
> [1]
> https://salsa.debian.org/bazel-team/bazel-bootstrap/-/merge_requests/2
FYI:
MR!2 was already merged.
Source: nextpnr
Severity: serious
Tags: ftbfs
Control: found -1 0.7-1
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
nextpnr fails to build on armel, armhf.
FYI:
https://buildd.debian.org/status/fetch.php?pkg=nextpnr&arch=armel&ver=0.7-1&stamp=1714863100&raw=0
https://buildd.debian.org/status
FYI:
I've created MR for it.
https://salsa.debian.org/bazel-team/bazel-bootstrap/-/merge_requests/3
s/cpp/bsd_cc_toolchain_config.bzl:
flag_groups = [flag_group(flags = ["-std=c++0x"])],
Regards,
>From e7f756e9e328516517e7b14ad1070c41c5688d5a Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi
Date: Sun, 2 Jun 2024 23:36:37 +0900
Subject: [PATCH] Fix FTBFS with std=c++0x (C++11)
It will
Control: tags -1 - unreproducible
Control: found -1 2.28.4715.102+dfsg-2.3
I've tried with newer mozc_2.28.4715.102+dfsg-2.3 again,
it was reproduced.
Drop unappropriate unreproducible tag.
Regargs,
FYI:
I've also sent patch [1] as MR for mozc. [2]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045435#10
[2] https://salsa.debian.org/debian/mozc/-/merge_requests/11
Regards,
I've just tried it with debian:sid container,
it seems that there is no test failure about 4 reported failures.
[ OK ] XWindowsKeyStateTests.setActiveGroup_poll_groupIsNotSet
(21 ms) [ RUN ]
XWindowsKeyStateTests.setActiveGroup_customGroup_groupWasSet
[2024-05-27T11:26:31] DEBUG: openi
On Sat, 4 May 2024 22:53:36 +0900 Kentaro HAYASHI
wrote:
> Control: tags -1 patch
>
> I've attached PoC patches which are
> based on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059706#33
>
I've created MR too.
https://salsa.debian.org/science-team/epics-base
Source: mozc
Version: 2.28.4715.102+dfsg-2.2
Severity: normal
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
* What led up to the situation?
When try to build package from git repository, it
can't be built because of missing pristine tar commmit.
* What exactly did you do (or not
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: faile
ftbfs
> 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 +090
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
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
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: sramac...@debian.org
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&arch=armel&ver=0.0.26-1&stamp=1714571498&raw=0
https://buildd.debian.org/status/fetch.php?p
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&arch=armhf&ver=0.1.29-1%2Bb2&stamp=1714283560&raw=0
Regards,
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&arch=armhf&ver=0.1.25-1%2Bb2&stamp=1714271391&raw=0
Regards,
n Sep 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
---
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.
override_dh_auto_build:
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&arch=armel&ver=4.0.5-2&stamp=16888
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&arch=armel&ver=0.2.1%2Bgit20201215-2&stamp=1685891638&raw=0
https://buildd.debian.
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&arch=armhf&ver=6.2.2401%2Bdfsg1-1.1%2Bb1&stamp=1712667539&raw=0
Regard
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&arch=armhf&ver=20240207%2Bdfsg-1.1%2Bb1&stamp=1712551793&raw=0
Note tha
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:
https://buildd.debian.org/status/fetch.php?pkg=macromoleculebuilder&arch=armhf&ver=4.0.0%2Bdfsg-3.
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&arch=armel&ver=2.15.00-1&stamp=1712127698&raw=0
https://buildd.debian
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&arch=armel&ver=6.08.00-1&stamp=1712127818&raw=0
https://buildd.deb
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&arch=armel&ver=1.3.0-3&stamp=1685884820&raw=0
https://buildd.debian.org/st
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&arch=armhf&ver=2.8.2%2Bds1-1%2Bb4&stamp=1704669577&
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&arch=armel&ver=1.1.2-2&stamp=1701603381&raw=0
https://buildd.debian.org/
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 atten
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&arch=armhf&ver=24.0.0-2&stamp=1710988310&raw=0
Regards,
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&arch=armel&ver=24.0.0-2&stamp=1711025590&raw=0
Regards,
Control: notfound -1 2.6.0-1
Control: tags -1 ftbfs
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&arch=armhf&ver=0.20230717-1&stamp=1694985920&raw=0
https://buildd.debian.org/sta
Control: found -1
Control: found -1 0.20230717-1
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&arch=armel&ver=0.20230717-1&stamp=1694985537&raw=0
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&arch=armel&ver=1.11.3-1&stamp=1710786055&raw=0
https://buildd.debian.org/status/fet
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&arch=armel&ver=1.10-2.1&stamp=1710920668&raw=0
https://buildd.debian.or
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&arch=armel&ver=2.6.0%2Bcleaned1-4&stamp=1703355142&raw=0
https://buil
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&arch=armhf&ver=1.9.6-2&stamp=1711367535&raw=0
https://buildd.debian.org/status/fe
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&arch=armhf&ver=1.0.1%2Bdfsg-1&stamp=1699230688&raw=0
Regards,
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&arch=armel&ver=0.0.0%7Egit20230215.21a85fe-1&stamp=1688810281&raw=0
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:
https://buildd.debian.org/status/fetch.php?pkg=rocalution
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
https://buildd.debian.org/status/fetch.php?pkg=open
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&arch=armhf&ver=0.26-1&stamp=1704511792&raw=0
Regards,
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 code
Control: severity -1 serious
Change severity because of ftbfs.
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&arch=armel&ver=0.3.2%2Bdfsg1-2.1&stamp=1709160782&raw=0
/home/kenhys
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&arch=armel&ver=2.0.0.post1-4&stamp=1708226979&raw=0
/usr/bin/ld:
/usr/lib/llvm-14/
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&arch=armel&ver=2.6.0-1&stamp=1705039418&raw=0
[96/131] /usr/bin/c++ -DFMT_
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)?
apt-g
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&arch=armhf&suite=sid
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 runtime
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
>
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
libzmq5
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 tr
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 4.1
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 vte-0-76
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]
root@debian:/home/
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
>
>
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)
* last_
FYI:
I've created MR.
debian: require xtl-dev with runtime
https://salsa.debian.org/science-team/xsimd/-/merge_requests/4
Regards,
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
libxsimd-de
Control: close 1059075
Duplicate report of #1059025.
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
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.
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
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 (
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 f
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 obsole
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 dependenc
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,
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 bu
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
Currently,
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 att
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
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]
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,
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
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 har
Control: tags -1 wontfix
>
> Anyway, it may be a trivial exceptional case, so I'll close it.
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
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
> invest
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 least,
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 pla
1 - 100 of 330 matches
Mail list logo