Bug#1071818: __lxcapi_create: 1760 Template "debian" not found on riscv64

[Bo YU]

Source: debci
Version: 3.10
Severity: important

Dear Maintainer,

When I am trying to setup debci env on riscv64 hardware, I got:

```
sudo apt install debci autopkgtest lxc
sudo adduser YOUR_USERNAME debci
sudo env debci_mirror=https://mirror.iscas.ac.cn/debian debci setup
...
I: testbed setup [unstable/riscv64/lxc]: starting at Sat May 25 13:01:56 CST 
2024
debian-distro-info: unknown distribution series `unstable'
lxc-create: autopkgtest-unstable-riscv64: ../src/lxc/utils.c: 
get_template_path: 1105 No such file or directory - bad template: debian
lxc-create: autopkgtest-unstable-riscv64: ../src/lxc/lxccontainer.c: 
__lxcapi_create: 1760 Template "debian" not found
lxc-create: autopkgtest-unstable-riscv64: ../src/lxc/tools/lxc_create.c: 
lxc_create_main: 318 Failed to create container autopkgtest-unstable-riscv64
```

I will investigate next days also.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1071362: rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s.......Fatal Python error: Segmentation fault

[Bo YU]

Hi,
On Sat, May 18, 2024 at 06:41:53AM -0500, Dirk Eddelbuettel wrote:


On 17 May 2024 at 23:05, Santiago Vila wrote:
| Dirk Eddelbuettel wrote:
| > Is there a chance this could be spurious?
|
| Unlikely because it also happens here:
|
| https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rpy2.html

Ok, I will get in touch with Laurent.


hmm, the failure will not happen on riscv64 real hardware when I am
trying to get below diff file.

--
Regards,
--
  Bo YU

diff -Nru rpy2-3.5.16/debian/changelog rpy2-3.5.16/debian/changelog
--- rpy2-3.5.16/debian/changelog2024-04-05 04:42:35.0 +0800
+++ rpy2-3.5.16/debian/changelog2024-05-19 22:32:19.0 +0800
@@ -1,3 +1,10 @@
+rpy2 (3.5.16-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Skip some tests on riscv64. (Closes: #-1) 
+
+ -- BO YU   Sun, 19 May 2024 22:32:19 +0800
+
 rpy2 (3.5.16-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru rpy2-3.5.16/debian/patches/series rpy2-3.5.16/debian/patches/series
--- rpy2-3.5.16/debian/patches/series   2023-08-27 00:04:33.0 +0800
+++ rpy2-3.5.16/debian/patches/series   2024-05-19 22:30:46.0 +0800
@@ -1,3 +1,3 @@
 #relax_cffi_version_requirement
 #comment_out_one_test
-skip_complex_tests_on_mips64el
+skip_complex_tests_on_mips64el_and_riscv64
diff -Nru rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el 
rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el
--- rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el   2023-08-27 
00:59:57.0 +0800
+++ rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el   1970-01-01 
08:00:00.0 +0800
@@ -1,148 +0,0 @@
-Description: Skip complex-valued tests on mips64el
-Bug-Debian: https://bugs.debian.org/1050432
-Reviewed-By: Dirk Eddelbuettel 
-Last-Update: 2023-08-26
-
 rpy2-3.5.13.orig/rpy2/tests/rinterface/test_na.py
-+++ rpy2-3.5.13/rpy2/tests/rinterface/test_na.py
-@@ -1,6 +1,8 @@
- import pytest
- import math
- import rpy2.rinterface as ri
-+import sys
-+import platform
- 
- ri.initr()
- 
-@@ -147,7 +149,8 @@ def test_NACharacter_in_vector():
- assert x.get_charsxp(1).rid == na_str.rid
- assert x[2] == 'cd'
- 
--
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_R_to_NAComplex():
- r_na_complex = ri.evalr('NA_complex_')[0]
- assert math.isnan(r_na_complex.real)
 rpy2-3.5.13.orig/rpy2/tests/rinterface/test_vector_complex.py
-+++ rpy2-3.5.13/rpy2/tests/rinterface/test_vector_complex.py
-@@ -1,9 +1,13 @@
- import pytest
- import rpy2.rinterface as ri
-+import sys
-+import platform
- 
- ri.initr()
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_init_from_seqr():
- seq = [1+2j, 5+7j, 0+1j]
- v = ri.ComplexSexpVector(seq)
-@@ -18,17 +22,23 @@ def test_init_from_seq_invalid_item():
- ri.ComplexSexpVector(seq)
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getitem():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- assert vec[1] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setitem():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[1] = 100+3j
- assert vec[1] == 100+3j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getslice():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec_s = vec[0:2]
-@@ -37,6 +47,8 @@ def test_getslice():
- assert vec_s[1] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getslice_negative():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec_s = vec[-2:-1]
-@@ -44,6 +56,8 @@ def test_getslice_negative():
- assert vec_s[0] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setslice():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[0:2] = ri.ComplexSexpVector([100+3j, 5-5j])
-@@ -52,6 +66,8 @@ def test_setslice():
- assert vec[1] == 5-5j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setslice_negative():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[-2:-

Bug#1071579: RFS: tla/1.3.5+dfsg1-5 [QA] [RC] -- GNU Arch revision control system

[Bo YU]

Hi pere!

On Wed, May 22, 2024 at 4:15 PM Petter Reinholdtsen  wrote:
>
> If you want me to sponsor it, my preferences are listed in

Thanks for your sponsor for this package and your works on this package.

> http://www.hungry.com/~pere/debian-sponsoring.html >.

I have read the page and I agree with the statement from the page.

I am worried about one thing is whether if I should drop lintian's
error about the orphaned package to meet your sponsor standard. My
initial goal is to fix the FTBFS issue but never thought the upload
will bring lintian error. It seems the package needs to be repacked to
fix the lintian error.

Or we first upload it to fix the FTBFS issue on some arches and then
raise one serious reportbug to remind the license issue(if true).

BR,
Bo


>
> --
> Happy hacking
> Petter Reinholdtsen
>

Bug#1071579: RFS: tla/1.3.5+dfsg1-5 [QA] [RC] -- GNU Arch revision control system

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "tla":

 * Package name : tla
   Version  : 1.3.5+dfsg1-5
   Upstream contact : [fill in name and email of upstream]
 * URL  : http://savannah.gnu.org/projects/gnu-arch/
 * License  : [fill in]
 * Vcs  : https://salsa.debian.org/debian/tla
   Section  : vcs

The source builds the following binary packages:

  tla - GNU Arch revision control system
  tla-doc - GNU Arch revision control system (documentation)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/tla/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/t/tla/tla_1.3.5+dfsg1-5.dsc

Changes since the last upload:

 tla (1.3.5+dfsg1-5) unstable; urgency=medium
 .
   * QA upload.
 .
   * Use dh_update_autotools_config/dh_autoreconf_clean to update config
 correctly. (Closes: #1071544)

-- 
Regards,
--
  Bo YU

diff -Nru tla-1.3.5+dfsg1/debian/changelog tla-1.3.5+dfsg1/debian/changelog
--- tla-1.3.5+dfsg1/debian/changelog2024-05-17 18:07:34.0 +0800
+++ tla-1.3.5+dfsg1/debian/changelog2024-05-21 17:49:51.0 +0800
@@ -1,3 +1,12 @@
+tla (1.3.5+dfsg1-5) unstable; urgency=medium
+
+  * QA upload.
+
+  * Use dh_update_autotools_config/dh_autoreconf_clean to update config
+correctly. (Closes: #1071544)
+
+ -- Bo YU   Tue, 21 May 2024 17:49:51 +0800
+
 tla (1.3.5+dfsg1-4) unstable; urgency=medium
 
   * QA upload.
diff -Nru tla-1.3.5+dfsg1/debian/rules tla-1.3.5+dfsg1/debian/rules
--- tla-1.3.5+dfsg1/debian/rules2024-05-17 16:57:58.0 +0800
+++ tla-1.3.5+dfsg1/debian/rules2024-05-21 17:47:05.0 +0800
@@ -19,6 +19,7 @@
 
 configure-stamp:
dh_testdir
+   dh_update_autotools_config
rm -rf debian/build
rm -rf src/expat/  # Let's play safe
rm -f src/libneon/PLUGIN/REQ
@@ -52,6 +53,7 @@
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
+   dh_autoreconf_clean
dh_clean
$(RM) -r debian/build
 


signature.asc
Description: PGP signature

Bug#1071140: gcc-14: internal compiler error: in find_or_generate_expression, at tree-ssa-pre.cc:2780 on riscv64

[Bo YU]

Source: gcc-14
Version: 14-20240429-1
Severity: important
X-Debbugs-Cc: numbk...@gmail.com

Dear Maintainer,

We found a gcc internal compiler error when compile a c source code(from
ksco):


```
#include 
typedef int npy_intp;
static inline __attribute__(()) int vaddq_f32();
static inline __attribute__(()) int npyv_load2_tillz_f32(int nlane) {
  vint32m1_t __trans_tmp_9;
  {
int __trans_tmp_10 = nlane;
{
  vint32m1_t __trans_tmp_8;
  vint64m1_t __trans_tmp_6;
  vint64m1_t __trans_tmp_4;
  vint64m1_t __trans_tmp_3;
  vint64m1_t __trans_tmp_2;
  vint64m1_t __trans_tmp_1;
  if (__trans_tmp_10 == 1) {
{
  __trans_tmp_3 =
  __riscv_vslideup_vx_i64m1(__trans_tmp_1, __trans_tmp_2, 1, 2);
}
__trans_tmp_4 = __trans_tmp_3;
  }
  __trans_tmp_6 = __trans_tmp_3;
  __trans_tmp_8 = __riscv_vreinterpret_v_i64m1_i32m1(__trans_tmp_3);
  __trans_tmp_9 = __trans_tmp_8;
}
  }
  return vaddq_f32(__trans_tmp_9);
}
char CFLOAT_add_args_2;
char CFLOAT_add_args_1;
char CFLOAT_add_args_0;
const npy_intp *CFLOAT_add_dimensions;
const npy_intp *CFLOAT_add_steps;
const npy_intp CFLOAT_add_steps_0;
__attribute__(()) void CFLOAT_add() {
  npy_intp len = CFLOAT_add_dimensions[0];
  char *b_src0 = _add_args_0, *b_src1 = _add_args_1,
   *b_dst = _add_args_2;
  const float *src1 = (float *)b_src1;
  float *dst = (float *)b_dst;
  const npy_intp ssrc1 = CFLOAT_add_steps[1] / sizeof(float);
  const npy_intp sdst = CFLOAT_add_steps[2] / sizeof(float);
  const int hstep = 4 / 2;
  {
vfloat32m1x2_t a;
ssrc1 == 2 && sdst == ssrc1;
for (; len > 0; len -= hstep, src1 += 4, dst += 4) {
  int b = npyv_load2_tillz_f32(len);
  int r = vaddq_f32(a.__val[0], b);
}
  }
  for (; len > 0; --len, b_src0 += CFLOAT_add_steps_0,
  b_src1 += CFLOAT_add_steps[1], b_dst += CFLOAT_add_steps[2])
;
}

```
error:

```
gcc-14 -c -O2 -w -march=rv64gcv test.c
during GIMPLE pass: pre
test.c: In function ‘CFLOAT_add’:
test.c:35:24: internal compiler error: in find_or_generate_expression, at 
tree-ssa-pre.cc:2780
   35 | __attribute__(()) void CFLOAT_add() {
  |^~
0xe5d75f find_or_generate_expression
../../src/gcc/tree-ssa-pre.cc:2780
0xe5d97b find_or_generate_expression
../../src/gcc/tree-ssa-pre.cc:2777
0xe5d97b create_component_ref_by_pieces_1
../../src/gcc/tree-ssa-pre.cc:2696
0xe5cdc5 create_component_ref_by_pieces
../../src/gcc/tree-ssa-pre.cc:2764
0xe5cdc5 create_expression_by_pieces
../../src/gcc/tree-ssa-pre.cc:2933
0xe63275 do_hoist_insertion
../../src/gcc/tree-ssa-pre.cc:3762
0xe63275 insert
../../src/gcc/tree-ssa-pre.cc:3907
0xe63275 execute
../../src/gcc/tree-ssa-pre.cc:4499
Please submit a full bug report, with preprocessed source (by using 
-freport-bug).
Please include the complete backtrace with any bug report.
See  for instructions.
```

Please tell me if I can do help here.

-- 
Regards,
--
  Bo YU

#include 
typedef int npy_intp;
static inline __attribute__(()) int vaddq_f32();
static inline __attribute__(()) int npyv_load2_tillz_f32(int nlane) {
  vint32m1_t __trans_tmp_9;
  {
int __trans_tmp_10 = nlane;
{
  vint32m1_t __trans_tmp_8;
  vint64m1_t __trans_tmp_6;
  vint64m1_t __trans_tmp_4;
  vint64m1_t __trans_tmp_3;
  vint64m1_t __trans_tmp_2;
  vint64m1_t __trans_tmp_1;
  if (__trans_tmp_10 == 1) {
{
  __trans_tmp_3 =
  __riscv_vslideup_vx_i64m1(__trans_tmp_1, __trans_tmp_2, 1, 2);
}
__trans_tmp_4 = __trans_tmp_3;
  }
  __trans_tmp_6 = __trans_tmp_3;
  __trans_tmp_8 = __riscv_vreinterpret_v_i64m1_i32m1(__trans_tmp_3);
  __trans_tmp_9 = __trans_tmp_8;
}
  }
  return vaddq_f32(__trans_tmp_9);
}
char CFLOAT_add_args_2;
char CFLOAT_add_args_1;
char CFLOAT_add_args_0;
const npy_intp *CFLOAT_add_dimensions;
const npy_intp *CFLOAT_add_steps;
const npy_intp CFLOAT_add_steps_0;
__attribute__(()) void CFLOAT_add() {
  npy_intp len = CFLOAT_add_dimensions[0];
  char *b_src0 = _add_args_0, *b_src1 = _add_args_1,
   *b_dst = _add_args_2;
  const float *src1 = (float *)b_src1;
  float *dst = (float *)b_dst;
  const npy_intp ssrc1 = CFLOAT_add_steps[1] / sizeof(float);
  const npy_intp sdst = CFLOAT_add_steps[2] / sizeof(float);
  const int hstep = 4 / 2;
  {
vfloat32m1x2_t a;
ssrc1 == 2 && sdst == ssrc1;
for (; len > 0; len -= hstep, src1 += 4, dst += 4) {
  int b = npyv_load2_tillz_f32(len);
  int r = vaddq_f32(a.__val[0], b);
}
  }
  for (; len > 0; --len, b_src0 += CFLOAT_add_steps_0,
  b_src1 += CFLOAT_add_steps[1], b_dst += CFLOAT_add_steps[2])
;
}


signature.asc
Description: PGP signature

Bug#1071098: Onboard: FTBFS on riscv64 due to test failed

[Bo YU]

Package: onboard
Version: 1.4.1-6
Severity: important
Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org


Dear Maintainer,

Onboard has a FTBFS issue on riscv64:

```
task-0:  self._get_model_files(), "test " + 
str(i))
task-0: E   AssertionError: Lists differ: [['en_US.lm', 1]] != 
[['user.lm', 1]]
task-0: E   
task-0: E   First differing element 0:
task-0: E   ['en_US.lm', 1]
task-0: E   ['user.lm', 1]
task-0: E   
task-0: E   - [['en_US.lm', 1]]
task-0: E   ? 
task-0: E   
task-0: E   + [['user.lm', 1]]
task-0: E   ?++ ^
task-0: E: test 0
```

The full build log is here: 
https://buildd.debian.org/status/fetch.php?pkg=onboard=riscv64=1.4.1-6=1715586733=0

In fact, this is not a specially riscv64 issue, it has the same FTBFS on
alpha, hppa, sparc64 also. But unfortunately, I was failed to fix the
root cause for the issue. So I am appreciated if you can hint me how to
fix it. I thought maybe there is one config was missing on these
architectures.

Instead of finding a perfect solution, I propose one patch to skip the
test on riscv64 to get the package will be built. If this is okay, i
think we should keep the reportbug opening until it is completely
resolved. 

Any helps would be great!

alpha: 
https://buildd.debian.org/status/fetch.php?pkg=onboard=alpha=1.4.1-6=1712238333=0
hppa: 
https://buildd.debian.org/status/fetch.php?pkg=onboard=hppa=1.4.1-6=1712271520=0
sparc64: 
https://buildd.debian.org/status/fetch.php?pkg=onboard=sparc64=1.4.1-6=1715474713=0

-- 
Regards,
--
  Bo YU

diff -Nru onboard-1.4.1/debian/patches/2003_skip_testmigration_on_riscv64.patch 
onboard-1.4.1/debian/patches/2003_skip_testmigration_on_riscv64.patch
--- onboard-1.4.1/debian/patches/2003_skip_testmigration_on_riscv64.patch   
1970-01-01 08:00:00.0 +0800
+++ onboard-1.4.1/debian/patches/2003_skip_testmigration_on_riscv64.patch   
2024-04-04 00:11:22.0 +0800
@@ -0,0 +1,26 @@
+Description: skip the test on riscv64
+Author: tsu.y...@gmail.com
+Last-Update: 2024-05-14
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: onboard-1.4.1/Onboard/test/test_migration.py
+===
+--- onboard-1.4.1.orig/Onboard/test/test_migration.py
 onboard-1.4.1/Onboard/test/test_migration.py
+@@ -18,6 +18,7 @@
+ # along with this program. If not, see <http://www.gnu.org/licenses/>.
+ 
+ import os
++import platform
+ import time
+ import glob
+ import tempfile
+@@ -39,7 +40,7 @@ class TestMigration(unittest.TestCase):
+ with self._run_onboard() as p:
+ self.assertEqual([],
+  self._get_model_files())
+-
++@unittest.skipIf(platform.machine() == 'riscv64', "skip the test due to 
failed")
+ def test_migrate_user_model(self):
+ tests = [
+ [
diff -Nru onboard-1.4.1/debian/patches/series 
onboard-1.4.1/debian/patches/series
--- onboard-1.4.1/debian/patches/series 2024-04-04 00:07:08.0 +0800
+++ onboard-1.4.1/debian/patches/series 2024-04-04 00:11:22.0 +0800
@@ -12,3 +12,4 @@
 2001_drop-gui-test.patch
 2002_drop-dbus-test.patch
 1011_python-distutils-byebye.patch
+2003_skip_testmigration_on_riscv64.patch


signature.asc
Description: PGP signature

Bug#1022540: build-essential: please add riscv64 support

[Bo YU]

Hi,

On Wed, Sep 13, 2023 at 12:59:02PM +0200, Matthias Klose wrote:
the package won't migrate, afaiu. we have to have a testing pocket 
first. I don't want to upload a package which is not able to migrate.


Maybe you have noticed testing for riscv64 which has been created, so
could you add support riscv64 for this package? IIUC, Helmut needs it to
setup crossbuild for riscv64 also.

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1070853: strace: test failures on 32bit with 64bit time_t

[Bo YU]

Hi,
On Sat, May 11, 2024 at 12:21:05AM +0300, Adrian Bunk wrote:

Control: retitle -1 strace: test failures on 32bit

The tests also fail on i386, so do not seem to be related to time_t.


Thanks for working on this. I will report this to upstream.


--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1054698: pixmap: FTBFS: ././Pixmap.c:1145:(.text+0xe631): undefined reference to `xpmReadRgbNames'

[Bo YU]

Hi,
On Thu, Nov 23, 2023 at 03:00:58PM +0100, Paul Slootman wrote:

On Fri 27 Oct 2023, Lucas Nussbaum wrote:


...

on libxpm:
Explicitly mark non-static symbols as export or hidden

Hides private API from external linkage

Signed-off-by: Alan Coopersmith 

That commit marks those functions as hidden for some reason.

I'm contacting the libxpm maintainers.


Thanks for working on it.

Is there any progress here? If so,  could you update some 
progress/news here?


--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1035566: ITP: gl4es -- OpenGL 2.1/1.5 to GLES 2.0/1.1 translation library title

[Bo YU]

Hi,
On Fri, May 05, 2023 at 10:15:01PM +0800, 李程 wrote:

  Package: wnpp
  Severity: wishlist
  Owner: Cheng Li <[1]ship...@gmail.com>
  X-Debbugs-Cc: [2]debian-de...@lists.debian.org
  * Package name: gl4es
Version : 1.1.4
Upstream Author : ptitSeb
  * URL : [3]https://github.com/ptitSeb/gl4es
  * License : MIT
Programming Lang: c


Many thanks for your upstream work and initail package!
As we have talked about it some days ago I have packaged
it based on your work(and I have ownered it now):

https://salsa.debian.org/vimerbf-guest/gl4es

Please review it if you have free time.:)

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1070417: rxtx: FTBFS: src/RawImp.c:223:23: error: implicit declaration of function ‘inl’ [-Werror=implicit-function-declaration]

[Bo YU]

Source: rxtx
Version: 2.2.0+dfsg-3
Severity: serious 

Dear Maintainer,

The package has a ftbfs issue like:

```
...
/<>/./src/RawImp.c: In function ‘Java_gnu_io_RawPort_open’:
/<>/./src/RawImp.c:128:12: error: implicit declaration of function 
‘ioperm’ [-Werror=implicit-function-declaration]
  128 | if(ioperm(ciAddress, 3, 1))
  |^~
/<>/./src/RawImp.c: In function ‘Java_Bus_read8’:
/<>/./src/RawImp.c:168:23: error: implicit declaration of function 
‘inb’ [-Werror=implicit-function-declaration]
  168 | return (jint) inb((unsigned) piPort);
  |   ^~~
/<>/./src/RawImp.c: In function ‘Java_Bus_write8’:
/<>/./src/RawImp.c:182:9: error: implicit declaration of function 
‘outb’ [-Werror=implicit-function-declaration]
  182 | outb((unsigned char) piData ,(unsigned) piPort);
...
```

See 
https://buildd.debian.org/status/fetch.php?pkg=rxtx=arm64=2.2.0%2Bdfsg-3=1714559641=0
 
and 
https://buildd.debian.org/status/fetch.php?pkg=rxtx=riscv64=2.2.0%2Bdfsg-3=1714560663=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1070132: sponsorship-requests: libkal/0.9.0-3.1 [NMU] [RC] -- library for converting dates between various calendar systems

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "libkal":

 * Package name : libkal
   Version  : 0.9.0-3.1
   Upstream contact : Petr Tomasek 
 * URL  : http://www.etf.cuni.cz/~tomasek/pub/my/
 * License  : LGPL-2+
 * Vcs  : https://salsa.debian.org/debian/libkal
   Section  : libs

The source builds the following binary packages:

  libkal-dev - library for converting dates between various calendar systems

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libkal/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libk/libkal/libkal_0.9.0-3.1.dsc

Changes since the last upload:

 libkal (0.9.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add fix-impfuncdef-issue.diff to fix ftbfs. (Closes: #1066513)


-- 
Regards,
--
  Bo YU

diff -Nru libkal-0.9.0/debian/changelog libkal-0.9.0/debian/changelog
--- libkal-0.9.0/debian/changelog   2023-04-25 10:11:53.0 +0800
+++ libkal-0.9.0/debian/changelog   2024-04-30 16:19:46.0 +0800
@@ -1,3 +1,10 @@
+libkal (0.9.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix-impfuncdef-issue.diff to fix ftbfs. (Closes: #1066513)
+
+ -- Bo YU   Tue, 30 Apr 2024 16:19:46 +0800
+
 libkal (0.9.0-3) unstable; urgency=medium
 
   [ Jelmer Vernooij ]
diff -Nru libkal-0.9.0/debian/patches/fix-impfuncdef-issue.diff 
libkal-0.9.0/debian/patches/fix-impfuncdef-issue.diff
--- libkal-0.9.0/debian/patches/fix-impfuncdef-issue.diff   1970-01-01 
08:00:00.0 +0800
+++ libkal-0.9.0/debian/patches/fix-impfuncdef-issue.diff   2024-04-30 
16:18:31.0 +0800
@@ -0,0 +1,19 @@
+Description: fix impfuncdef issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066513
+Forwarded: send to Petr Tomasek 
+Last-Update: 2024-04-30
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/kal_getdate.c
 b/kal_getdate.c
+@@ -18,6 +18,9 @@
+  */
+ 
+ #include 
++#include 
++
++#include "kal_main.h"
+ 
+ /* 
+  * Get current date (jd)
diff -Nru libkal-0.9.0/debian/patches/series libkal-0.9.0/debian/patches/series
--- libkal-0.9.0/debian/patches/series  2023-04-25 10:11:53.0 +0800
+++ libkal-0.9.0/debian/patches/series  2024-04-30 10:30:01.0 +0800
@@ -1 +1,2 @@
 Makefile.diff
+fix-impfuncdef-issue.diff


signature.asc
Description: PGP signature

Bug#1069254: nwipe: FTBFS: configure: error: libconfig library not found

[Bo YU]

Tags: patch

hi,
On Thu, Apr 18, 2024 at 10:00:30PM +0200, Sebastian Ramacher wrote:


checking for libconfig... no
checking for main in -llibconfig... no
configure: error: libconfig library not found


It seems it shuold use libconfig-dev.


Cheers
--
Sebastian Ramacher


--
Regards,
--
  Bo YU

diff -Nru nwipe-0.36/debian/changelog nwipe-0.36/debian/changelog
--- nwipe-0.36/debian/changelog 2024-04-17 01:37:21.0 +0800
+++ nwipe-0.36/debian/changelog 2024-04-29 14:28:41.0 +0800
@@ -1,3 +1,11 @@
+nwipe (0.36-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use libconfig-dev instead of pkgconf on debian/control. 
+(Closes: #1069254)
+
+ -- Bo YU   Mon, 29 Apr 2024 14:28:41 +0800
+
 nwipe (0.36-1) unstable; urgency=medium
 
   * New upstream release(closes: #1069072, #1034262 ).
diff -Nru nwipe-0.36/debian/control nwipe-0.36/debian/control
--- nwipe-0.36/debian/control   2024-04-17 01:37:21.0 +0800
+++ nwipe-0.36/debian/control   2024-04-29 14:28:41.0 +0800
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Martijn van Brummelen 
-Build-Depends: debhelper-compat (=13), libparted-dev, libncurses-dev, dpkg-dev 
(>= 1.16.1~), pkgconf
+Build-Depends: debhelper-compat (=13), libparted-dev, libncurses-dev, dpkg-dev 
(>= 1.16.1~), libconfig-dev
 Standards-Version: 4.7.0
 Homepage: https://github.com/martijnvanbrummelen/nwipe
 Vcs-Browser: https://salsa.debian.org/mvb/nwipe


signature.asc
Description: PGP signature

Bug#1066225: Bug#1069722: RFS: libtranscript/0.3.3-1.1 [NMU] [RC] -- Character set conversion library

[Bo YU]

Hi!

Thanks for NMUing this!

On Thu, Apr 25, 2024 at 4:29 AM Salvo Tomaselli  wrote:
>
> Hello,
>
> tilde is going to be autoremoved very soon because of libt3key.
>
> I'd say that if the maintainer hasn't taken any action about this for over a
> months, it's possible to contact the MIA team right away.

Yeah, this is my consideration also.
>
> If you don't want tilde to be dropped, you have to fix also libt3key and get 
> it
> sponsored, because just this one won't help basically.

I have uploaded it to mentor[0].

Thanks again.

BR,
Bo

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069801
>

Bug#1069801: RFS: libt3key/0.2.10-1.1 [NMU] [RC] -- Utilities for working with libt3key terminal descriptions

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "libt3key":

 * Package name : libt3key
   Version  : 0.2.10-1.1
   Upstream contact : Gertjan Halkes 
 * URL  : https://os.ghalkes.nl/t3/libt3key.html
 * License  : GPL-3
 * Vcs  : [fill in URL of packaging vcs]
   Section  : libs

The source builds the following binary packages:

  libt3key-dev - Development files for libt3key
  libt3key1 - Terminal key sequence database library
  libt3key-bin - Utilities for working with libt3key terminal descriptions

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libt3key/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libt/libt3key/libt3key_0.2.10-1.1.dsc

Changes since the last upload:

 libt3key (0.2.10-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
 (Closes: #1066618)

-- 
Regards,
--
  Bo YU

diff -Nru libt3key-0.2.10/debian/changelog libt3key-0.2.10/debian/changelog
--- libt3key-0.2.10/debian/changelog2019-11-30 21:16:41.0 +0800
+++ libt3key-0.2.10/debian/changelog2024-04-25 10:54:51.0 +0800
@@ -1,3 +1,11 @@
+libt3key (0.2.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
+(Closes: #1066618)
+
+ -- Bo YU   Thu, 25 Apr 2024 10:54:51 +0800
+
 libt3key (0.2.10-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch 
libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
--- libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
1970-01-01 07:30:00.0 +0730
+++ libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
2024-04-25 10:53:18.0 +0800
@@ -0,0 +1,17 @@
+Description: fix impfuncdef issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066618
+Forwarded: Forward this patch to the author of upstream
+Last-Update: 2024-04-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/config.pkg
 b/config.pkg
+@@ -144,6 +144,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ int main(int argc, char *argv[]) {
+   int args[9], error, fd;
diff -Nru libt3key-0.2.10/debian/patches/series 
libt3key-0.2.10/debian/patches/series
--- libt3key-0.2.10/debian/patches/series   1970-01-01 07:30:00.0 
+0730
+++ libt3key-0.2.10/debian/patches/series   2024-04-25 10:02:49.0 
+0800
@@ -0,0 +1 @@
+00-fix-impfuncdef-issue.patch


signature.asc
Description: PGP signature

Bug#1069722: RFS: libtranscript/0.3.3-1.1 [NMU] [RC] -- Character set conversion library

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "libtranscript":

 * Package name : libtranscript
   Version  : 0.3.3-1.1
   Upstream contact : Gertjan Halkes 
 * URL  : https://os.ghalkes.nl/libtranscript.html
 * License  : GPL-3
 * Vcs  : [fill in URL of packaging vcs]
   Section  : libs

The source builds the following binary packages:

  libtranscript-dev - Development files for libtranscript
  libtranscript1 - Character set conversion library

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libtranscript/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libt/libtranscript/libtranscript_0.3.3-1.1.dsc

Changes since the last upload:

 libtranscript (0.3.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
 (Closes: #1066225)


-- 
Regards,
--
  Bo YU

diff -Nru libtranscript-0.3.3/debian/changelog 
libtranscript-0.3.3/debian/changelog
--- libtranscript-0.3.3/debian/changelog2017-12-29 00:43:51.0 
+0800
+++ libtranscript-0.3.3/debian/changelog2024-04-24 00:14:00.0 
+0800
@@ -1,3 +1,11 @@
+libtranscript (0.3.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue. 
+(Closes: #1066225)
+
+ -- Bo YU   Wed, 24 Apr 2024 00:14:00 +0800
+
 libtranscript (0.3.3-1) unstable; urgency=low
 
   * Initial release. (Closes: #885600)
diff -Nru libtranscript-0.3.3/debian/patches/00-fix-impfuncdef-issue.patch 
libtranscript-0.3.3/debian/patches/00-fix-impfuncdef-issue.patch
--- libtranscript-0.3.3/debian/patches/00-fix-impfuncdef-issue.patch
1970-01-01 07:30:00.0 +0730
+++ libtranscript-0.3.3/debian/patches/00-fix-impfuncdef-issue.patch
2024-04-24 00:13:15.0 +0800
@@ -0,0 +1,17 @@
+Description: fix implicit-function-declaration issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066225
+Forwarded: forward this to the author of upstream
+Last-Update: 2024-04-24
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/config.pkg
 b/config.pkg
+@@ -66,6 +66,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ int main(int argc, char *argv[]) {
+   DIR *dir;
diff -Nru libtranscript-0.3.3/debian/patches/series 
libtranscript-0.3.3/debian/patches/series
--- libtranscript-0.3.3/debian/patches/series   1970-01-01 07:30:00.0 
+0730
+++ libtranscript-0.3.3/debian/patches/series   2024-04-24 00:06:47.0 
+0800
@@ -0,0 +1 @@
+00-fix-impfuncdef-issue.patch


signature.asc
Description: PGP signature

Bug#1065420: RFS: ocaml-linenoise/1.5-1 [ITP] -- Lightweight readline alternative with OCaml

[Bo YU]

Hi Stéphane!

Thanks for reviewing it.

On Tue, Apr 23, 2024 at 7:57 PM Stéphane Glondu  wrote:
>
> Dear Bo,
>
> On Mon, 4 Mar 2024 16:40:29 +0800 Bo YU  wrote:
> > I am looking for a sponsor for my package "ocaml-linenoise":
>
> Here is my review of the packaging:
>
> - There is a comment about ocaml-parany in debian/salsa-ci.yml I don't
> understand.

Ah, sorry, I forgot to drop it when I referred to the salsa yaml file
of ocaml-cpu[0]. Now I update it with more precise salsa ci target.
But to my confusion, I can not enable the ci on salsa repo on my side.
>
> - In debian/liblinenoise-ocaml.install.in, the *.cma should not be
> prefixed by "OPT: " and the *.cmxs should be prefixed by "DYN: ".

Done. I mixed them sometime but I think I will have a clear
understanding of these files.

Thanks again.

BR,
Bo

[0]: 
https://salsa.debian.org/ocaml-team/ocaml-cpu/-/blob/master/debian/salsa-ci.yml?ref_type=heads
> Cheers,
>
> --
> Stéphane
>

Bug#1066491: libt3window: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [-Werror=implicit-function-declaration]

[Bo YU]

Hi,
On Wed, Mar 13, 2024 at 12:52:51PM +0100, Lucas Nussbaum wrote:

https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):

gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection `pkg-config 
--cflags tinfo` -c -o .config.o .config.c
.config.c: In function ‘main’:
.config.c:8:13: error: implicit declaration of function ‘setupterm’; did you 
mean ‘set_term’? [-Werror=implicit-function-declaration]
8 | if (setupterm(NULL, fd, ) == OK) {
  | ^
  | set_term
.config.c:12:17: error: implicit declaration of function ‘tputs’; did you mean 
‘puts’? [-Werror=implicit-function-declaration]
   12 | tputs("\033[0m", 1, putchar);
  | ^
  | puts
cc1: some warnings being treated as errors
make[2]: *** [.Makefile:19: .config.o] Error 1


I have sent one RFS[0] to fix the issue.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069662

Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1069662: RFS: libt3window/0.4.0-1.1 [NMU] [RC] -- Library for creating window-based terminal programs

[Bo YU]

Package: sponsorship-requests
Severity: important
Tags: patch
X-Debbugs-Cc: 1066...@bugs.debian.org


Dear mentors,

I am looking for a sponsor for my package "libt3window":

 * Package name : libt3window
   Version  : 0.4.0-1.1
   Upstream contact : Gertjan Halkes 
 * URL  : https://os.ghalkes.nl/t3/libt3window.html
 * License  : GPL-3
 * Vcs  : [fill in URL of packaging vcs]
   Section  : libs

The source builds the following binary packages:

  libt3window-dev - Development files for libt3window
  libt3window0 - Library for creating window-based terminal programs

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libt3window/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libt/libt3window/libt3window_0.4.0-1.1.dsc

Changes since the last upload:

 libt3window (0.4.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add 00-fix-implicit-function-declaration.patch to fix impfuncdef
 issue. (Closes: #1066491)


-- 
Regards,
--
  Bo YU

diff -Nru libt3window-0.4.0/debian/changelog libt3window-0.4.0/debian/changelog
--- libt3window-0.4.0/debian/changelog  2019-12-01 00:53:56.0 +0800
+++ libt3window-0.4.0/debian/changelog  2024-04-22 16:01:09.0 +0800
@@ -1,3 +1,11 @@
+libt3window (0.4.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 00-fix-implicit-function-declaration.patch to fix impfuncdef
+issue. (Closes: #1066491)
+
+ -- Bo YU   Mon, 22 Apr 2024 16:01:09 +0800
+
 libt3window (0.4.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
libt3window-0.4.0/debian/patches/00-fix-implicit-function-declaration.patch 
libt3window-0.4.0/debian/patches/00-fix-implicit-function-declaration.patch
--- libt3window-0.4.0/debian/patches/00-fix-implicit-function-declaration.patch 
1970-01-01 07:30:00.0 +0730
+++ libt3window-0.4.0/debian/patches/00-fix-implicit-function-declaration.patch 
2024-04-22 15:33:59.0 +0800
@@ -0,0 +1,18 @@
+Description: fix implicit-function-declaration issue
+ No upstream issue report online, will forward this to the author of upstream.
+ New upstream release 0.4.1 has not fixed the issue yet.
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066491
+Last-Update: 2024-04-22
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/config.pkg
 b/config.pkg
+@@ -121,6 +121,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ int main(int argc, char *argv[]) {
+   int args[9], error, fd;
diff -Nru libt3window-0.4.0/debian/patches/series 
libt3window-0.4.0/debian/patches/series
--- libt3window-0.4.0/debian/patches/series 1970-01-01 07:30:00.0 
+0730
+++ libt3window-0.4.0/debian/patches/series 2024-04-21 09:27:28.0 
+0800
@@ -0,0 +1 @@
+00-fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1068651: RFS: bisect-ppx/2.8.3-1 [ITP] -- Code coverage for OCaml and ReScript (dev files)

[Bo YU]

Hi,

On Tue, Apr 16, 2024 at 1:45 PM Stéphane Glondu  wrote:
>
> Hi,
>
> Le 15/04/2024 à 17:12, Bo YU a écrit :
> >> Again, I've seen this issue several times with OCaml packages, but I
> >> didn't bother to investigate. It looks like another toolchain issue,
> >> which should be fixed in a more central package, not in bisect-ppx
> >> itself. So just leave the lintian warnings as is.
> >
> > It seems the issue should be fixed on lintian side as your analyst.
> > But unfortunately, this is one lintian error that will lead to
> > ftp-master auto-rejected if uploaded:
> >
> > ```
> > E: libbisect-ppx-ocaml-dbgsym: stripped-library
> > [usr/lib/debug/.dwz/x86_64-linux-gnu/libbisect-ppx-ocaml.debug]
> > E: libbisect-ppx-ocaml-dev-dbgsym: stripped-library
> > [usr/lib/debug/.dwz/x86_64-linux-gnu/libbisect-ppx-ocaml-dev.debug]
> > ```
> > I tried many attempts but failed. One common workaround is shipping
> > one lintian-override via dh_lintian, like[0] and [1]. Although the
> > error was gone, but we will get another error:
> >
> > ```
> > libbisect-ppx-ocaml-dev-dbgsym: non-debug-file-in-debug-package
> > [usr/share/lintian/overrides/libbisect-ppx-ocaml-dev-dbgsym]
> > ```
> > Passing `--no-dwz-multifile` to dh_dwz maybe has side effects on the
> > debug package but it seems this is a workaround if we can upload to
> > upstable.And
>
> I agree.
>
> I've pushed two minor changes. Please review them. Then, I will upload
> the package.

Okay, thanks. I have checked the two commits. LGTM.

>
> > I will open two separate reportbugs to track these issues once the
> > package unloaded to unstable.
>
> Thank you for your work.

Thanks for your work also and patience for me:)

BR,
Bo
>
>
> Cheers,
>
> --
> Stéphane

Bug#1068651: RFS: bisect-ppx/2.8.3-1 [ITP] -- Code coverage for OCaml and ReScript (dev files)

[Bo YU]

Hi,

Thanks for your review and loop in me with #1017530.

On Mon, Apr 15, 2024 at 2:03 PM Stéphane Glondu  wrote:
>
> Dear Bo,
>
> Le 14/04/2024 à 16:30, Bo YU a écrit :
...
> > ```
> > In fact, the original solution is that I refer to this[1]. But I am
> > not sure if this is a toolchain issue or not, so I have reported this
> > to upstream[2] also. The workaround for this issue I could think of:
> > 1. Keep those lintian messages here and open a reportbug to track the
> > issue until upstream fix the issue;
> > 2. Use the solution like [1] as my previous post and open a reportbug
> > to track the issue until upstream fix the issue;
> > 3. Wait to upstream to fix this issue;
> > 4. Persuading the maintainers of debhelper to strip static library
> > with broader name scheme.But I think this is not a good wishlist.:)
> > Personally I prefer to option 2 still.
>
> Thank you for looking into this, I wasn't expecting that!
>
> By a "toolchain issue", I meant an issue in debhelper or lintian (or
> maybe in dh-ocaml or ocaml itself). This is definitely not an upstream
> issue (of bisect-ppx), as all OCaml packages face it.
>
> One possible fix would be to change dh_strip, for example by telling it
> to strip $FOO.a if $FOO.cmxa exists, if this is correct (I'm not sure: I
> don't know why lib*.a are stripped in the first place). That would be
> your option 4. Or fix lintian to not issue the warning for $FOO.a if
> $FOO.cmxa exists. Right now, I don't know which option is correct.
>
> But this should not hinder bisect-ppx packaging, so I would go to option
> 1 first, then investigate which of my two options is the correct one.

Okay, I can do some experimental/feedback on these both tools here also.
>
> > For dh_dwz issue. It seems that the issue will be fixed by passing
> > `--no-dwz-multifile` arg. In my understanding, there is two ELF
> > binaries on the debug package, so the no-mutlifile arg can assure
> > dropping `../.dwz/../.debug`.
>
> Again, I've seen this issue several times with OCaml packages, but I
> didn't bother to investigate. It looks like another toolchain issue,
> which should be fixed in a more central package, not in bisect-ppx
> itself. So just leave the lintian warnings as is.

It seems the issue should be fixed on lintian side as your analyst.
But unfortunately, this is one lintian error that will lead to
ftp-master auto-rejected if uploaded:

```
E: libbisect-ppx-ocaml-dbgsym: stripped-library
[usr/lib/debug/.dwz/x86_64-linux-gnu/libbisect-ppx-ocaml.debug]
E: libbisect-ppx-ocaml-dev-dbgsym: stripped-library
[usr/lib/debug/.dwz/x86_64-linux-gnu/libbisect-ppx-ocaml-dev.debug]
```
I tried many attempts but failed. One common workaround is shipping
one lintian-override via dh_lintian, like[0] and [1]. Although the
error was gone, but we will get another error:

```
libbisect-ppx-ocaml-dev-dbgsym: non-debug-file-in-debug-package
[usr/share/lintian/overrides/libbisect-ppx-ocaml-dev-dbgsym]
```
Passing `--no-dwz-multifile` to dh_dwz maybe has side effects on the
debug package but it seems this is a workaround if we can upload to
upstable.And
I will open two separate reportbugs to track these issues once the
package unloaded to unstable.

Thanks again.

BR,
Bo
[0]: 
https://www.mail-archive.com/pkg-kde-talk@alioth-lists.debian.net/msg00457.html
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820310#22
>
>
> Cheers,


>
> --
> Stéphane
>

Bug#1068651: RFS: bisect-ppx/2.8.3-1 [ITP] -- Code coverage for OCaml and ReScript (dev files)

[Bo YU]

Hi,

On Tue, Apr 9, 2024 at 2:18 PM Stéphane Glondu  wrote:
>
> Dear Bo,
>
> Le 08/04/2024 à 17:05, Bo YU a écrit :
> > I am looking for a sponsor for my package "bisect-ppx":
> > [...]
>
> I've reviewed the packaging and I have a few comments.
>
> Standards-Version is not the latest.
>
> Upstream copyright years are missing in debian/copyright.
>
> A .cma file is in a "OPT:" line in an .install.in file.
>

Done.
> I would not override dh_dwz nor dh_strip. My opinion is that what you
> are trying to fix are deficiencies of the toolchain that should be fixed
> there.
First to address dh_strip issue. From what I've researched. The issue
was raised by the static library generated from bisect_ppx did not
obey the standard static library name scheme. The dh_strip[0] will
strip the static library with `lib-*` prefix. But as we can observe
the building:
```
I: libbisect-ppx-ocaml-dev: unstripped-static-library
(bisect__Runtime.o) [usr/lib/ocaml/bisect_ppx/runtime/bisect.a]
I: libbisect-ppx-ocaml-dev: unstripped-static-library
(bisect_common.o) [usr/lib/ocaml/bisect_ppx/common/bisect_common.a]
I: libbisect-ppx-ocaml-dev: unstripped-static-library
(bisect_ppx__Exclude.o bisect_ppx__Exclude_lexer.o
bisect_ppx__Exclude_parser.o bisect_ppx
__Exclusions.o bisect_ppx__Instrument.o bisect_ppx__Register.o)
[usr/lib/ocaml/bisect_ppx/bisect_ppx.a]
```
In fact, the original solution is that I refer to this[1]. But I am
not sure if this is a toolchain issue or not, so I have reported this
to upstream[2] also. The workaround for this issue I could think of:
1. Keep those lintian messages here and open a reportbug to track the
issue until upstream fix the issue;
2. Use the solution like [1] as my previous post and open a reportbug
to track the issue until upstream fix the issue;
3. Wait to upstream to fix this issue;
4. Persuading the maintainers of debhelper to strip static library
with broader name scheme.But I think this is not a good wishlist.:)
Personally I prefer to option 2 still.

For dh_dwz issue. It seems that the issue will be fixed by passing
`--no-dwz-multifile` arg. In my understanding, there is two ELF
binaries on the debug package, so the no-mutlifile arg can assure
dropping `../.dwz/../.debug`.

[0]: https://github.com/Debian/debhelper/blob/master/dh_strip#L239C2-L244C27
[1]: https://lists.debian.org/debian-mentors/2015/10/msg00027.html
[2]: https://github.com/aantron/bisect_ppx/issues/439
>
> It is not right to override source-contains-prebuilt-javascript-object
> in this case; you should filter the .js file out and make sure the
> package works without it. Or get the actual sources and build from them.
> Or find it in another Debian package. (These are just examples of how to
> tackle the issue.)
Okay, I repacked it by removing the prebuilt javascript file and put
its source code which pulled from upstream into debian/missing-sources
and then to get the file during the building.

>
> I am wondering about long-term maintainability of the manpage. I suppose
> you've generated the manpage from running the command with --help?
> Please make a rule to automatically generate it.

Done.

All commits I have pushed into the salsa [3] and mentor[4].

Thanks for your time again and please let me know any issues.

BR,
Bo

[3]: https://salsa.debian.org/ocaml-team/bisect-ppx
[4]: https://mentors.debian.net/package/bisect-ppx/


>
>
> Thank you for your work,
>
> --
> Stéphane
>

Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

[Bo YU]

Hi,

On Sun, Apr 14, 2024 at 5:11 AM Graham Inggs  wrote:
>
> Hi Bo
>
> > I have attached one debdiff and it can be built with it. So could you
> > upload it with it?
>
> The attached patch just seems to be papering over the problem, so I
> would rather not.
I agree with that.

I should add some background on the original post:
https://trac.macports.org/ticket/61842. On this thread, the maintainer
prefers to fix it in a correct way as you said. But given upstream of
dx, maybe this is very thorny.

BR,
Bo
>
> Regards
> Graham

Bug#1068899: ITP: qtrvsim -- RISC-V CPU simulator for education purposes

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-ri...@lists.debian.org

* Package name: qtrvsim
  Version : 0.9.7
  Upstream Contact: p...@cmp.felk.cvut.cz
* URL : https://github.com/cvut/qtrvsim
* License : GPL-3.0
  Programming Lang: C++, Python, shell
  Description : RISC-V CPU simulator for education

This is a widely recommended riscv emulator in the riscv community so I
want to bring it to Debian also.

The simulator accepts ELF statically linked executables compiled for
RISC-V target (--march=rv64g). The simulator will automatically select
endianness based on the ELF file header. Simulation will execute as
XLEN=32 or XLEN=32 according to the ELF file header.

64-bit RISC-V ISA RV64IM and 32-bit RV32IM ELF executables are supported.
Compressed instructions are not yet supported.
You can use compile the code for simulation using specialized RISC-V
GCC/Binutils toolchain (riscv32-elf) or using unified Clang/LLVM toolchain
with LLD.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1066658: sup: FTBFS: scm.c:316:9: error: implicit declaration of function ‘setproctitle’ [-Werror=implicit-function-declaration]

[Bo YU]

Tags: patch

Hi,

,On Wed, Mar 13, 2024 at 12:57:21PM +0100, Lucas Nussbaum wrote:

scm.c: In function ‘service’:
scm.c:316:9: error: implicit declaration of function ‘setproctitle’ 
[-Werror=implicit-function-declaration]
  316 | setproctitle("Serving %s", remotehost());
  | ^~~~
scm.c: In function ‘request’:
scm.c:448:16: warning: ignoring return value of ‘write’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  448 | (void) write(netfile, , sizeof(int));
  |^~~
scmio.c: In function ‘readfile’:


I have uploaded it to mentor to wait for sponsoring[0]. But there is one
debdiff if you can review it.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068814

Thanks.

--
Regards,
--
  Bo YU

diff -Nru sup-20100519/debian/changelog sup-20100519/debian/changelog
--- sup-20100519/debian/changelog   2020-08-05 19:53:16.0 +0800
+++ sup-20100519/debian/changelog   2024-04-11 16:41:22.0 +0800
@@ -1,3 +1,12 @@
+sup (20100519-4) unstable; urgency=medium
+
+  * QA upload.
+  * set std-ver to 4.7.0.
+  * Add 07_fix-implicit-function-declaration.patch to fix ftbfs issue.
+(Closes: #1066658)
+
+ -- Bo YU   Thu, 11 Apr 2024 16:41:22 +0800
+
 sup (20100519-3) unstable; urgency=medium
 
   * QA upload.
diff -Nru sup-20100519/debian/control sup-20100519/debian/control
--- sup-20100519/debian/control 2020-08-05 19:48:03.0 +0800
+++ sup-20100519/debian/control 2024-04-11 16:03:18.0 +0800
@@ -3,7 +3,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13), libwrap0-dev
 Maintainer: Debian QA Group 
-Standards-Version: 4.5.0
+Standards-Version: 4.7.0
 
 Package: sup
 Architecture: any
diff -Nru 
sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch 
sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch
--- sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch  
1970-01-01 07:30:00.0 +0730
+++ sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch  
2024-04-11 15:59:50.0 +0800
@@ -0,0 +1,17 @@
+Description: fix implicit-function-declaration issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066658
+Last-Update: 2024-04-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/scm.c
 b/scm.c
+@@ -195,6 +195,8 @@
+ #define   INADDR_LOOPBACK (u_long)0x7f01  /* 127.0.0.1 */
+ #endif
+ 
++void setproctitle(const char *fmt, ...);
++
+ char scmversion[] = "4.3 BSD";
+ extern int silent;
+ 
diff -Nru sup-20100519/debian/patches/series sup-20100519/debian/patches/series
--- sup-20100519/debian/patches/series  2020-08-05 19:43:02.0 +0800
+++ sup-20100519/debian/patches/series  2024-04-11 15:01:34.0 +0800
@@ -4,3 +4,4 @@
 04_fix_man.patch
 05_unconst.patch
 06_fix_ftbfs.patch
+07_fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1068814: RFS: sup/20100519-4 [QA] [RC] -- Software Upgrade Protocol implementation

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "sup":

 * Package name : sup
   Version  : 20100519-4
   Upstream contact : [fill in name and email of upstream]
 * URL  : [fill in URL of upstream's web site]
 * License  : [fill in]
 * Vcs  : [fill in URL of packaging vcs]
   Section  : devel

The source builds the following binary packages:

  sup - Software Upgrade Protocol implementation

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/sup/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/s/sup/sup_20100519-4.dsc

Changes since the last upload:

 sup (20100519-4) unstable; urgency=medium
 .
   * QA upload.
   * set std-ver to 4.7.0.
   * Add 07_fix-implicit-function-declaration.patch to fix ftbfs issue.
 (Closes: #1066658)

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1068731: falcosecurity-libs: FTBFS on riscv64 and ppc64el

[Bo YU]

Source: falcosecurity-libs
Version: 0.15.1-1
Severity: serious
Tags: ftbfs, patch

Dear Maintainer,

It seems new upstream release ftbfs on riscv64 and ppc64el due to:

```
/<>/userspace/chisel/chisel.cpp: In static member function ‘static 
bool sinsp_chisel::init_lua_chisel(chisel_desc&, const std::string&)’:
/<>/userspace/chisel/chisel.cpp:978:9: error: ‘luaL_setfuncs’ was 
not declared in this scope; did you mean ‘lua_setfenv’?
  978 | luaL_setfuncs(ls, ll_tool, 0);
  | ^
  | lua_setfenv
/<>/userspace/chisel/chisel.cpp: In member function ‘void 
sinsp_chisel::load(std::string, bool)’:
/<>/userspace/chisel/chisel.cpp:1189:9: error: ‘luaL_setfuncs’ was 
not declared in this scope; did you mean ‘lua_setfenv’?
 1189 | luaL_setfuncs(m_ls, ll_tool, 0);
  | ^
  | lua_setfenv
[ 53%] Building CXX object 
test/drivers/CMakeFiles/drivers_test.dir/test_suites/syscall_exit_suite/vfork_x.cpp.o
```

See 
https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-libs=riscv64=0.15.1-1=1712602717=0
 
and 
https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-libs=riscv64=0.15.1-1=1712602717=0

And there is no still luajit support for riscv64(or ppc64el?), so this[0] is 
right. but maybe we need upgrade to >liblua5.3[1].

BTW, it was build failed again with the patch on ppc64el but I tested it
on qemu-user and I ddi not have look more this.

Apart from these two architectures, FTBFS on other architectures due to
test failed[2]. But I think this is another story.

[0]: 
https://salsa.debian.org/debian/falcosecurity-libs/-/blob/master/debian/control?ref_type=heads#L24
[1]: 
https://github.com/owasp-modsecurity/ModSecurity/issues/1622#issuecomment-345841731
[2]: https://buildd.debian.org/status/package.php?p=falcosecurity-libs

-- 
Regards,
--
  Bo YU

diff -Nru falcosecurity-libs-0.15.1/debian/changelog 
falcosecurity-libs-0.15.1/debian/changelog
--- falcosecurity-libs-0.15.1/debian/changelog  2024-04-07 02:54:51.0 
+0800
+++ falcosecurity-libs-0.15.1/debian/changelog  2024-04-09 22:22:39.0 
+0800
@@ -1,3 +1,11 @@
+falcosecurity-libs (0.15.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use liblua5.3-dev instead of liblua5.1-dev to fix ftbfs 
+on riscv64 and ppc64el. (Closes: #-1)
+
+ -- Bo YU   Tue, 09 Apr 2024 22:22:39 +0800
+
 falcosecurity-libs (0.15.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru falcosecurity-libs-0.15.1/debian/control 
falcosecurity-libs-0.15.1/debian/control
--- falcosecurity-libs-0.15.1/debian/control2024-02-03 14:44:31.0 
+0800
+++ falcosecurity-libs-0.15.1/debian/control2024-04-09 22:22:04.0 
+0800
@@ -21,7 +21,7 @@
protobuf-compiler,
protobuf-compiler-grpc,
libprotobuf-dev,
-   libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x] 
| liblua5.1-0-dev,
+   libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x] 
| liblua5.3-dev,
libelf-dev,
libre2-dev,
libcap-dev,


signature.asc
Description: PGP signature

Bug#1068651: RFS: bisect-ppx/2.8.3-1 [ITP] -- Code coverage for OCaml and ReScript (dev files)

[Bo YU]

Hi!

Thanks for your review of it quickly.

On Tue, Apr 9, 2024 at 2:18 PM Stéphane Glondu  wrote:
>
> Dear Bo,
>
> Le 08/04/2024 à 17:05, Bo YU a écrit :
> > I am looking for a sponsor for my package "bisect-ppx":
> > [...]
>
> I've reviewed the packaging and I have a few comments.
>
> Standards-Version is not the latest.
Now is the latest Standards-Version 4.7.0? Just noticed the
announcement from the d-announcement mail list some days ago.
>
> Upstream copyright years are missing in debian/copyright.
>
> A .cma file is in a "OPT:" line in an .install.in file.
Both above are easy to fix for me.:)
>
> I would not override dh_dwz nor dh_strip. My opinion is that what you
> are trying to fix are deficiencies of the toolchain that should be fixed
> there.
Here I want to get some help with how to fix the issue. In your view,
which toolchain is the most likely cause of this problem? I mean dh_*
or just bisect-ppx build toolchain itself. For these OCaml packages I
packaged in the past weeks, it was about two packages has the same
issue. This will cost more time given I known a little about OCaml but
I will fix the issue definitely.

>
> It is not right to override source-contains-prebuilt-javascript-object
> in this case; you should filter the .js file out and make sure the
> package works without it. Or get the actual sources and build from them.
> Or find it in another Debian package. (These are just examples of how to
> tackle the issue.)
I think repacking it should be fixed the issue, but is it overuse?
Is it possible has another solution to fix it? like this[0] to be
noticed when I was trying to fix another ftbfs issue.

[0]: 
https://salsa.debian.org/ocaml-team/opam/-/blob/master/debian/gbp.conf?ref_type=heads#L4
>
> I am wondering about long-term maintainability of the manpage. I suppose
> you've generated the manpage from running the command with --help?
> Please make a rule to automatically generate it.
>
Ok, got it.

Thanks for your time again. I will fix these issue ASAP.

BR,
Bo

Bug#1068684: bornagain: FTBFS on many architectures

[Bo YU]

Source: bornagain
Version: 21.1+ds3-4
Severity: serious
Tags: ftbfs

Dear Maintainer,

Recently upload did not fixed ftbfs on many architectures, see:
https://buildd.debian.org/status/package.php?p=bornagain


Tests failed on arm64, ppc64el, riscv64 and s390x. Build issue on
arm{el,hf} and i386.


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1068683: zmat: FTBFS: ar: blosc2/blosc/*.o: No such file or directory

[Bo YU]

Source: zmat
Version: 0.9.9+ds.1-2
Severity: serious
Tags: ftbfs

Dear Maintainer,

The package has ftbfs issue but on amd64 and i386, the common issue is
follows:

```
CC obj/conf_91c451f6ae5e059804729dd256611361/static/cover.o
CC obj/conf_91c451f6ae5e059804729dd256611361/static/divsufsort.o
CC obj/conf_91c451f6ae5e059804729dd256611361/static/fastcover.o
CC obj/conf_91c451f6ae5e059804729dd256611361/static/zdict.o
compiling single-threaded static library 1.5.5
make[4]: Leaving directory '/<>/src/blosc2/internal-complibs/zstd'
make[3]: Leaving directory '/<>/src/blosc2'
Building ../lib/libzmat.a
ar cr -o ../lib/libzmat.a zmatlib.o miniz/miniz.o easylzma/compress.o 
easylzma/decompress.o easylzma/lzma_header.o easylzma/lzip_header.o 
easylzma/common_internal.o easylzma/pavlov/LzmaEnc.o easylzma/pavlov/LzmaDec.o 
easylzma/pavlov/LzmaLib.o easylzma/pavlov/LzFind.o easylzma/pavlov/Bra.o 
easylzma/pavlov/BraIA64.o easylzma/pavlov/Alloc.o easylzma/pavlov/7zCrc.o 
blosc2/blosc/*.o blosc2/internal-complibs/zstd/obj/*/static/*.o 
ar: blosc2/blosc/*.o: No such file or directory
make[2]: *** [makefile:194: ../lib/libzmat.a] Error 1
make[2]: Leaving directory '/<>/src'
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2

...
```

See 
https://buildd.debian.org/status/fetch.php?pkg=zmat=arm64=0.9.9%2Bds.1-2=1712139942=0
and 
https://buildd.debian.org/status/fetch.php?pkg=zmat=riscv64=0.9.9%2Bds.1-2=1712403175=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1068651: RFS: bisect-ppx/2.8.3-1 [ITP] -- Code coverage for OCaml and ReScript (dev files)

[Bo YU]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "bisect-ppx":

 * Package name : bisect-ppx
   Version  : 2.8.3-1
   Upstream contact : Xavier Clerc ,
 * URL  : https://github.com/aantron/bisect_ppx
 * License  : Expat
 * Vcs  : https://salsa.debian.org/ocaml-team/bisect-ppx
   Section  : ocaml

The source builds the following binary packages:

  libbisect-ppx-ocaml - Code coverage for OCaml and ReScript (runtime files)
  libbisect-ppx-ocaml-dev - Code coverage for OCaml and ReScript (dev files)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/bisect-ppx/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/bisect-ppx/bisect-ppx_2.8.3-1.dsc

Changes for the initial release:

 bisect-ppx (2.8.3-1) UNRELEASED; urgency=low
 .
   * Initial release. (Closes: #1068621)


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1068621: ITP: bisect-ppx -- Code coverage for OCaml and ReScript

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-ocaml-ma...@lists.debian.org

* Package name: bisect-ppx
  Version : 2.8.3 
  Upstream Contact: Anton Bachin 
Leonid Rozenberg 
* URL : https://github.com/aantron/bisect_ppx
* License : MIT
  Programming Lang: OCaml
  Description : Code coverage for OCaml and ReScript


Bisect-ppx helps you test thoroughly. It is a small preprocessor
that inserts instrumentation at places in your code, such as if-then-else and
match expressions. After you run tests, Bisect-ppx gives a nice HTML report
showing which places were visited and which were missed.

Usage is simple - add package bisect-ppx when building tests, run your tests,
then run the Bisect-ppx report tool on the generated visitation files."

The package is a dependency of sail[0] also. I will package it and
maintianit under Debian OCaml team.

[0]: https://bugs.debian.org/1065419


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1054822: opam: FTBFS: sed: can't read opam.install: No such file or directory

[Bo YU]

Hi,
On Fri, Oct 27, 2023 at 09:42:50PM +0200, Lucas Nussbaum wrote:

 ; windows_unicode = false
 }
 ; instrument_with = []
 }
Actual targets:
- _build/default/opam-installer.install
- _build/default/opam.install
Running[1]: (cd _build/default/src/client && /bin/sh -c 'git describe --exact HEAD || 
echo [dev]') > _build/default/src/client/git-describe 2> /dev/null
Running[2]: (cd _build/default/src/client && /bin/sh -c 'git rev-parse --quiet 
--verify HEAD || echo .') > _build/default/src/client/git-sha 2> /dev/null
sed -f process.sed opam.install > processed-opam.install
sed: can't read opam.install: No such file or directory
make[2]: *** [Makefile:166: processed-opam.install] Error 2


Just fyi, I have commited one patch to salsa:
https://salsa.debian.org/ocaml-team/opam/-/commit/ce22a7ae844e4bb9266748beb23a6750afb3c3f6

It was the same with debdiff file.

But there is one issue was unclear to me, see
https://lists.debian.org/debian-ocaml-maint/2024/04/msg00028.html

--
Regards,
--
  Bo YU

diff -Nru opam-2.1.5/debian/changelog opam-2.1.5/debian/changelog
--- opam-2.1.5/debian/changelog 2023-09-02 13:35:29.0 +0800
+++ opam-2.1.5/debian/changelog 2024-04-06 22:30:28.0 +0800
@@ -1,3 +1,10 @@
+opam (2.1.5-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Add 0003-opam-dune-3.11.patch to fix ftbfs issue. (Closes: #1054822)
+
+ -- Bo YU   Sat, 06 Apr 2024 22:30:28 +0800
+
 opam (2.1.5-1) unstable; urgency=medium
 
   * Team upload
diff -Nru opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch 
opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch
--- opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch 1970-01-01 
08:00:00.0 +0800
+++ opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch 2024-04-06 
22:30:28.0 +0800
@@ -0,0 +1,20 @@
+Description: fix ftbfs due to opam-dune 3.11 
+Origin: 
https://src.fedoraproject.org/rpms/opam/blob/rawhide/f/opam-dune-3.11.patch
+Bug: https://bugs.debian.org/1054822
+Last-Update: 2024-04-05
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Makefile
 b/Makefile
+@@ -162,7 +162,10 @@
+   $(DUNE) install --root . opam-$$p; \
+   done
+ 
+-processed-%.install: %.install
++processed-opam.install: _build/default/opam.install
++  sed -f process.sed $^ > $@
++
++processed-opam-installer.install: _build/default/opam-installer.install
+   sed -f process.sed $^ > $@
+ 
+ install: processed-opam.install processed-opam-installer.install
diff -Nru opam-2.1.5/debian/patches/series opam-2.1.5/debian/patches/series
--- opam-2.1.5/debian/patches/series2023-09-02 13:35:29.0 +0800
+++ opam-2.1.5/debian/patches/series2024-04-06 22:30:28.0 +0800
@@ -1,2 +1,3 @@
 0001-Add-a-test-target.patch
 0002-Use-HOME-env-variable-instead-of.patch
+0003-opam-dune-3.11.patch


signature.asc
Description: PGP signature

Bug#1068487: man-db: Failed to get unit file state for man-db.service: Transport endpoint is not connected

[Bo YU]

Hi,

On Sun, Apr 7, 2024 at 12:14 AM Colin Watson  wrote:
>
> Control: reassign -1 systems
>
...
>
> Hi,
>
> This is all fairly clearly a systemd issue rather than anything
> specifically to do with man-db, so reassigning there.  I'm afraid I
> don't have any further clues though.

Thanks for correcting this. What's even more embarrassing is that I
can not reproduce this on other machines. maybe something else
unexpected happened while I was upgrading the system. So please give
me one or two days to observe more and then close the bug if
everything is okay.

Thanks.

BR,
Bo
>
> --
> Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1068487: man-db: Failed to get unit file state for man-db.service: Transport endpoint is not connected

[Bo YU]

Package: man-db
Version: 2.12.1-1
Severity: important

Dear Maintainer,

Today upgraded my riscv64 sid , I got:

```
Setting up man-db (2.12.1-1) ...
Updating database of manual pages ...
Reload daemon failed: Transport endpoint is not connected

Failed to get unit file state for man-db.service: Transport endpoint is not 
connected
Failed to retrieve unit state: Transport endpoint is not connected
man-db.service is a disabled or a static unit not running, not starting it.
Failed to get unit file state for man-db.timer: Transport endpoint is not 
connected
Failed to retrieve unit state: Transport endpoint is not connected
man-db.timer is a disabled or a static unit not running, not starting it.
...
Setting up openssh-sftp-server (1:9.7p1-4) ...
Setting up openssh-server (1:9.7p1-4) ...
Reload daemon failed: Transport endpoint is not connected
Failed to get properties: Transport endpoint is not connected
Reload daemon failed: Transport endpoint is not connected
Failed to get unit file state for ssh.service: Transport endpoint is not 
connected
Failed to retrieve unit state: Transport endpoint is not connected
ssh.service is a disabled or a static unit not running, not starting it.
^B^[[5~Reload daemon failed: Transport endpoint is not connected
Failed to get unit file state for ssh.socket: Transport endpoint is not 
connected
Failed to retrieve unit state: Transport endpoint is not connected
...
```

And this process is very time-consuming also.


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Bo YU]

On Tue, Apr 2, 2024 at 11:19 PM Sebastian Ramacher  wrote:
>
> Hi
>
> On 2024-04-02 23:16:16 +0800, Bo YU wrote:
> > Tags: patch
> >
> > Hi,
> > >  File "/<>/site_scons/extractdebbuild.py", line 61:
> > >raise RuntimeError("We do not current support different different 
> > > dpkg-buildflags for C vs C++")
> > > make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
> >
> > I have looked into this a bit.
> > As the error hint here, the default cflags in here when build is:
> >
> > ```
> > -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
> > clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -Wno-uninitialized
> > ```
> >
> > But cxxflags without[0] `-Werror=implicit-function-declaration` here. Is it
> > expected?
>
> It is expected. -Werror=implicit-function-declaration makes no sense in
> C++ since C++ simply does not support implicit function declarations.

Thanks for clarification.

Once cleared my local build, I will push this update again.

BR,
Bo
>
> Cheers
>

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Bo YU]

Tags: patch

Hi,

 File "/<>/site_scons/extractdebbuild.py", line 61:
   raise RuntimeError("We do not current support different different dpkg-buildflags 
for C vs C++")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2


I have looked into this a bit.
As the error hint here, the default cflags in here when build is:

```
-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-uninitialized
```

But cxxflags without[0] `-Werror=implicit-function-declaration` here. Is it
expected?



Once we added the build flags for cxx[1] and sorted these config with
compared, the built is okay.

[0]: 
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d
[1]: 
https://salsa.debian.org/science-team/python-escript/-/blob/debian/latest/debian/rules?ref_type=heads#L16

--
Regards,
--
  Bo YU

diff -Nru python-escript-5.6/debian/changelog 
python-escript-5.6/debian/changelog
--- python-escript-5.6/debian/changelog 2023-12-10 18:53:54.0 +0800
+++ python-escript-5.6/debian/changelog 2024-04-02 20:27:27.0 +0800
@@ -1,3 +1,12 @@
+python-escript (5.6-7) unstable; urgency=medium
+
+  * Team upload.
+  * Add fix-dpkg-buildflags-on-c-c++.patch to fix ftbfs issue.
+(Closes: #1068158)
+  * No build dependencies issue again. (Closes: #1067385)
+
+ -- Bo YU   Tue, 02 Apr 2024 20:27:27 +0800
+
 python-escript (5.6-6) unstable; urgency=medium
 
   * Update patch for new buildflags. Closes: #1057593
diff -Nru python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch 
python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
--- python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
1970-01-01 08:00:00.0 +0800
+++ python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
2024-04-02 20:26:55.0 +0800
@@ -0,0 +1,32 @@
+Description: false postive for different build flags
+  Do not support different different dpkg-buildflags for C vs C++
+  In fact, cflags and cxxflags was the same with following config:
+  cxxflags: -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=form
+at-security -fcf-protection -Wno-uninitialized 
-Werror=implicit-function-declaration
+
+  cflags:   -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
+clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-uninitialized
+ so sorted them can fix the issue.
+
+Author: Bo YU 
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068158
+Last-Update: 2024-04-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/site_scons/extractdebbuild.py
 b/site_scons/extractdebbuild.py
+@@ -57,8 +57,12 @@
+ mycflags=val
+ if key=="CXXFLAGS":
+ mycxxflags=val
+-if mycflags is not None and mycxxflags is not None and 
mycflags!=mycxxflags:
+-raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
++if mycflags is not None and mycxxflags is not None: 
++print(mycxxflags)
++print(mycflags)
++
++if sorted(mycflags.split()) != sorted(mycxxflags.split()):
++raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
+ if usedflags[key] is None:
+ continue
+ res.append([usedflags[key],val])
diff -Nru python-escript-5.6/debian/patches/py3.patch 
python-escript-5.6/debian/patches/py3.patch
--- python-escript-5.6/debian/patches/py3.patch 2023-12-10 16:25:14.0 
+0800
+++ python-escript-5.6/debian/patches/py3.patch 2024-04-02 17:40:23.0 
+0800
@@ -4,11 +4,9 @@
 Last-Updated: 2020-03-09
  Updated for python3.8
 
-Index: python-escript-5.6/site_scons/extractdebbuild.py
-===
 python-escript-5.6.orig/site_scons/extractdebbuild.py
-+++ python-escript-5.6/site_scons/extractdebbuild.py
-@@ -35,7 +35,7 @@ def getdebbuildflags():
+--- a/site_scons/extractdebbuild.py
 b/site_scons/extractdebbuild.py
+@@ -35,7 +35,7 @@
mycflags=None
mycxxflags=None
try:
@@ -17,11 +15,9 @@
except OSError:
  return []
res=[]
-Index: python-escript-5.6/site_scons/dependencies.py
-===
 python-escript-5.6.orig/site_scons/dependencies.py
-+++ python-escript-5.6/site_scons/dependencies.py
-@@ -122,7 +122,7 @@ def call_python_config(bin=None):
+--- a/site_scons/dependencies.py
 b/site_scons/dependencies.py
+@@ -122,7 +122,7 @@
  cmd+='  
sp=subprocess.Popen([pythonroot+"python"+pyversion+"-config","--ldflags"], 
stdout=subprocess.PIPE)\n'
  cmd+='d=sp.stdo

Bug#1067819: ITP: linksem -- Semantic model for aspects of ELF static linking and DWARF debug information

[Bo YU]

On Wed, Mar 27, 2024 at 04:36:53PM +0800, Bo YU wrote:

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-ocaml-ma...@lists.debian.org

This is a critical dependency for sail[0]. But it depends on lem[1] first.

For anyone who has interesting to build linksem, please use it here:
https://salsa.debian.org/vimerbf-guest/linksem

Once lem was uplaoded, I will send RFS then.


[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065419
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065658


--
Regards,
--
 Bo YU





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1067819: ITP: linksem -- Semantic model for aspects of ELF static linking and DWARF debug information

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
debian-ocaml-ma...@lists.debian.org 

* Package name: linksem
  Version : 0.8
  Upstream Contact: Linksem Devs 
* URL : https://github.com/rems-project/linksem
* License : BSD-2
  Programming Lang: OCaml 
  Description : Semantic model for aspects of ELF static linking and DWARF 
debug information

 
Linksem is a formalisation of substantial parts of ELF linking and DWARF debug
information. It contains:

A formalisation of the core ELF file format, the de facto standard executable 
and linkable file format on Linux and related systems, written in Lem. This 
formalisation has been tested against approximately 5,000 ELF binaries found 
"in the wild" on various different platforms.

A partial formalisation of various aspects of the platform Application Binary 
Interfaces for AMD64, Power64, AArch64, and X86-32, as well as a partial 
formalisation of the GNU extensions for ELF that the Linux operating system 
expects. These formalisations have been formalised on an ad hoc basis, as they 
were needed and may (almost certainly will be) incomplete.

An executable linker/link-checker built atop the aforementioned ELF and ABI 
formalisations for AMD64, capable of linking complex link-jobs such as bzip2, 
derived from an OCaml extraction of the Lem models above.

A sample proof of correctness for AMD64 relocation, using an Isabelle/HOL 
extraction of the linker, ELF model, and ABI formalisations mentioned above.

A formalisation of the DWARF debug information format, as an executable 
specification that interprets the DWARF information.

The ELF formalisation (and parts of the ABI formalisation) are currently also 
being used as a subcomponent of the rmem architectural exploration tool, for 
parsing ELF files and setting up initial machine states.

-->

This is a critical dependency for sail[0]. But it depends on lem[1] first.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065419
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065658


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064178: RFS: xwayland-run/0.0.2-1 [ITP] -- Set of utilities to run headless X/Wayland clients

[Bo YU]

Hi,
On Sun, Feb 18, 2024 at 11:31:07AM +0800, Bo YU wrote:

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "xwayland-run":

* Package name : xwayland-run
  Version  : 0.0.2-1
  Upstream contact : Olivier Fourdan 
* URL  : https://gitlab.freedesktop.org/ofourdan/xwayland-run
* License  : GPL-2.0+
* Vcs  : https://salsa.debian.org/vimerbf-guest/xwayland-run
  Section  : x11

The source builds the following binary packages:

 xwayland-run - Set of utilities to run headless X/Wayland clients

To access further information about this package, please visit the following 
URL:

 https://mentors.debian.net/package/xwayland-run/

Alternatively, you can download the package with 'dget' using this command:

 dget -x 
https://mentors.debian.net/debian/pool/main/x/xwayland-run/xwayland-run_0.0.2-1.dsc

Changes for the initial release:

xwayland-run (0.0.2-1) UNRELEASED; urgency=low
.
  * Initial release. (Closes: #1061513)


Could anyone to review this package at your free time? I would like to
put this package under Xorg team namespace also.

TUA.


--
Regards,
--
 Bo YU





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1066246: lcm: FTBFS: emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]

[Bo YU]

:
In function ‘sprintf’,
inlined from ‘emit_package’ at emit_python.c:702:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: 
‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a 
destination of size 4096
   30 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   31 |   __glibc_objsize (__s), __fmt,
  |   ~
   32 |   __va_arg_pack ());
  |   ~
emit_python.c: In function ‘emit_package’:
emit_python.c:44:13: warning: ‘__builtin_strncpy’ output may be truncated 
copying between 0 and 4094 bytes from a string of length 4095 
[-Wstringop-truncation]
   44 | strncpy(dirpath, path, i);
  | ^
cc1: some warnings being treated as errors
emit_lua.c: In function ‘emit_package’:
emit_lua.c:762:33: warning: ‘__builtin___sprintf_chk’ may write a terminating 
nul past the end of the destination [-Wformat-overflow=]
  762 | sprintf(package_dir, "%s%s%s", package_dir_prefix, pdname,
  | ^
In file included from /usr/include/stdio.h:906,
 from emit_lua.c:1:
In function ‘sprintf’,
inlined from ‘emit_package’ at emit_lua.c:762:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: 
‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a 
destination of size 4096
   30 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   31 |   __glibc_objsize (__s), __fmt,
  |   ~
   32 |   __va_arg_pack ());
  |   ~
emit_lua.c: In function ‘emit_package’:
emit_lua.c:45:13: warning: ‘__builtin_strncpy’ output may be truncated copying 
between 0 and 4094 bytes from a string of length 4095 [-Wstringop-truncation]
   45 | strncpy(dirpath, path, i);
  | ^
make[3]: *** [Makefile:513: emit_cpp.o] Error 1


Here is a simple fix and I uploaded it to mentor:
https://mentors.debian.net/package/lcm/

But jose.luis.rivero.partida has uploaded it with new upstream release
1.5.1 under the same mentor and the issue was fixed already also.

https://mentors.debian.net/package/lcm/ see v1.

So I am not sure situation how to deal with: if we upload 1.5.1 to
unstale maybe we need SOANME bump first, this is disturb currently t64
transition, right? if we fix the FTBFS first within 1.3.1 the patch is
fine.

--
Regards,
--
  Bo YU

diff -Nru lcm-1.3.1+repack1/debian/changelog lcm-1.3.1+repack1/debian/changelog
--- lcm-1.3.1+repack1/debian/changelog  2023-12-07 04:48:38.0 +0800
+++ lcm-1.3.1+repack1/debian/changelog  2024-03-22 16:45:50.0 +0800
@@ -1,3 +1,10 @@
+lcm (1.3.1+repack1-8) unstable; urgency=medium
+
+  * QA upload.
+  * Fix implicit-function-declaration error issue. (Closes: #1066246)
+
+ -- Bo YU   Fri, 22 Mar 2024 16:45:50 +0800
+
 lcm (1.3.1+repack1-7) unstable; urgency=medium
 
   * QA upload.
diff -Nru 
lcm-1.3.1+repack1/debian/patches/0006-fix-implicit-function-declaration-issue.patch
 
lcm-1.3.1+repack1/debian/patches/0006-fix-implicit-function-declaration-issue.patch
--- 
lcm-1.3.1+repack1/debian/patches/0006-fix-implicit-function-declaration-issue.patch
 1970-01-01 08:00:00.0 +0800
+++ 
lcm-1.3.1+repack1/debian/patches/0006-fix-implicit-function-declaration-issue.patch
 2024-03-22 16:44:30.0 +0800
@@ -0,0 +1,27 @@
+Description: fix -Werror=implicit-function-declaration issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066246 
+Forwarded: https://github.com/lcm-proj/lcm/issues/498
+Last-Update: 2024-03-22
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/lcm-logger/lcm_logger.c
 b/lcm-logger/lcm_logger.c
+@@ -8,6 +8,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include 
+ 
+--- a/lcmgen/emit_cpp.c
 b/lcmgen/emit_cpp.c
+@@ -11,6 +11,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include "lcmgen.h"
+ 
diff -Nru lcm-1.3.1+repack1/debian/patches/series 
lcm-1.3.1+repack1/debian/patches/series
--- lcm-1.3.1+repack1/debian/patches/series 2023-12-06 08:27:57.0 
+0800
+++ lcm-1.3.1+repack1/debian/patches/series 2024-03-22 14:50:00.0 
+0800
@@ -4,3 +4,4 @@
 0004-doxygen-docs-go-to-a-subdir.patch
 0005-I-default-to-java-1.6-instead-of-1.5.patch
 remove-epydoc
+0006-fix-implicit-function-declaration-issue.patch


signature.asc
Description: PGP signature

Bug#1067410: golang-github-go-jose-go-jose-dev: ftbfs on i386 and mips64el due to timeout of test case

[Bo YU]

Hi,
On Thu, Mar 21, 2024 at 11:14:40PM +0530, Nilesh Patra wrote:

The 4.0.1-2 still has timeout on test issue, see:
https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=i386

https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=mips64el

So open this to trace it again.
...
golang-github-go-jose-go-jose (4.0.1-3) unstable; urgency=medium
.
  * Skip one test on some architectures accurately. (Closes: #1067410)


You could instead increase the timeout too with:

override_dh_auto_test:
   dh_auto_test -- -timeout=1h

Unless the tests run on those archs forever.


Thanks. it works. I plan to upload it again, so reopen the bug again.

At first I also thought about how to globally increase the timeout
during build(but fail to find this). Another worried is that it will has
timeout issue on debci. but it seems the timeout does not affect debci.

Thanks again.

BR,
Bo


Best,
Nilesh




--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1055279: tox-current-env: potential bugs on armel

[Bo YU]

Hi,
On Tue, Mar 19, 2024 at 01:31:10PM +0200, Faidon Liambotis wrote:

Control: retitle -1 test_allenvs_print_extras tests are flaky

On Fri, Nov 03, 2023 at 08:57:57PM +0800, Bo YU wrote:

I recently uploaded tox/4.14.1-1. tox-current-env autopkgtests fail on
s390x[1] with a similar error, which in turn is currently preventing tox
from migrating into testing[2]


Thanks your detailed analysis for it. I have uploaded -3 to unstable to
hope to unblock tox migrating. But these are some unexpected maybe.


1: https://ci.debian.net/packages/t/tox-current-env/testing/s390x/44050718/
2: https://qa.debian.org/excuses.php?package=tox

This bug was originally for test_allenvs_print_extras_to_file(); for
this I would imagine think the fix is something like:
 - assert prep_tox_output(result.stdout) == expected
 + assert sorted(prep_tox_output(result.stdout)) == sorted(expected)


I have cherry-picked your comment here:
https://salsa.debian.org/python-team/packages/tox-current-env/-/blob/debian/main/debian/patches/sorted-output-on-tests.patch

It seems it works but I was missing another code snipshot which need be
`sorted` also:
https://salsa.debian.org/python-team/packages/tox-current-env/-/blob/debian/main/tests/test_integration_tox4.py#L217
```
@pytest.mark.parametrize("option", ("--print-deps-to", "--print-deps-to-file"))
def test_allenvs_print_deps_to_file(tmp_path, option):
depspath = tmp_path / "deps"
result = tox(option, str(depspath))
assert sorted(depspath.read_text().splitlines()) == sorted(
["tox", "six", "py"] * len(envs_from_tox_ini())
)
expected = ""
for env in envs_from_tox_ini()[:-1]:
expected += f"{env}: OK\n"
expected += tox_footer(spaces=0) + "\n"
assert prep_tox_output(result.stdout) == expected
```

This will lead a autopkgtest on s390x[0] again from its tracker page[1] to
get the link(UTC+8 13:06 2024/03/22).

But another retry on s390x it passed on s390x[2].

[0]: https://ci.debian.net/packages/t/tox-current-env/testing/s390x/44235641/
[1]: https://tracker.debian.org/pkg/tox-current-env
[2]: https://ci.debian.net/packages/t/tox-current-env/

So if many retries on debci page and it passes all autopkgtest, does it
still block your migration? 



The s390x autopkgtest above fails on test_allenvs_print_extras(), which
is very similar. However, that one seems to have a sorted() already:
45s def test_allenvs_print_extras(print_extras_stdout_arg):
45s result = tox(print_extras_stdout_arg)
45s expected = []
45s for env in envs_from_tox_ini():
45s expected.extend(("dev", "full", f"{env}: OK"))
45s expected.pop()  # The last "py310: OK" is not there
45s expected.append(tox_footer(spaces=0))
45s expected = ("\n".join(expected)).splitlines()
45s >   assert sorted(prep_tox_output(result.stdout).splitlines()) == 
sorted(expected)

For safe to unblock anything, I skip this:
https://salsa.debian.org/python-team/packages/tox-current-env/-/blob/debian/main/debian/patches/flaky-test.patch




Do you think I will need to upload it to unstable again with `sorted`
for `test_allenvs_print_deps_to_file` as I analyzed above?

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1067410: golang-github-go-jose-go-jose-dev: ftbfs on i386 and mips64el due to timeout of test case

[Bo YU]

Package: golang-github-go-jose-go-jose-dev
Version: 4.0.1-2
Severity: serious

The 4.0.1-2 still has timeout on test issue, see:
https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=i386

https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=mips64el

So open this to trace it again.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1067141: kcemu: FTBFS with -Werror=implicit-function-declaration

[Bo YU]

Package: kcemu
Version: 0.5.2+dfsg-1
Followup-For: Bug #1067141
Tags: patch

Hi, 

I just test the patch and it seems it works.


-- 
Regards,
--
  Bo YU

diff -Nru kcemu-0.5.2+dfsg/debian/changelog kcemu-0.5.2+dfsg/debian/changelog
--- kcemu-0.5.2+dfsg/debian/changelog   2022-11-30 05:53:48.0 -0500
+++ kcemu-0.5.2+dfsg/debian/changelog   2024-03-19 11:32:12.0 -0400
@@ -1,3 +1,10 @@
+kcemu (0.5.2+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix implicit-function-declaration issue. (Closes: #1067141) 
+
+ -- a   Tue, 19 Mar 2024 11:32:12 -0400
+
 kcemu (0.5.2+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch
--- 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch   
1969-12-31 19:00:00.0 -0500
+++ 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch   
2024-03-19 11:32:02.0 -0400
@@ -0,0 +1,28 @@
+Description: fix implicit-function-declaration error
+Author: Bo YU 
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067141
+Forwarded: https://github.com/t-paul/kcemu/issues/6
+Last-Update: 2024-03-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/sys/mingw/sys_socket_create.c
 b/src/sys/mingw/sys_socket_create.c
+@@ -18,6 +18,7 @@
+  */
+ 
+ #include 
++#include 
+ 
+ #include "kc/config.h"
+ #include "sys/sysdep.h"
+--- a/src/sys/unix/sys_socket_create.c
 b/src/sys/unix/sys_socket_create.c
+@@ -23,6 +23,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++
+ 
+ #include "kc/config.h"
+ #include "sys/sysdep.h"
diff -Nru kcemu-0.5.2+dfsg/debian/patches/series 
kcemu-0.5.2+dfsg/debian/patches/series
--- kcemu-0.5.2+dfsg/debian/patches/series  1969-12-31 19:00:00.0 
-0500
+++ kcemu-0.5.2+dfsg/debian/patches/series  2024-03-19 05:37:35.0 
-0400
@@ -0,0 +1 @@
+fix-error-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066371: ukwm: FTBFS: default.c:667:15: error: implicit declaration of function ‘waitpid’ [-Werror=implicit-function-declaration]

[Bo YU]

Version 1.2.0-2.2
Tags: patch


Hi,
On Wed, Mar 13, 2024 at 12:46:03PM +0100, Lucas Nussbaum wrote:




The patch attached is trying to fix the issue and I have tested it on my
local build.


--
Regards,
--
  Bo YU

diff -Nru ukwm-1.2.0/debian/changelog ukwm-1.2.0/debian/changelog
--- ukwm-1.2.0/debian/changelog 2024-02-29 05:05:01.0 +0800
+++ ukwm-1.2.0/debian/changelog 2024-03-15 14:10:35.0 +0800
@@ -1,3 +1,10 @@
+ukwm (1.2.0-2.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix implicit-function-declaration ftbfs. (Closes: #1066371)
+
+ -- Bo YU   Fri, 15 Mar 2024 14:10:35 +0800
+
 ukwm (1.2.0-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
ukwm-1.2.0/debian/patches/fix-implicit-function-declaration-error.patch 
ukwm-1.2.0/debian/patches/fix-implicit-function-declaration-error.patch
--- ukwm-1.2.0/debian/patches/fix-implicit-function-declaration-error.patch 
1970-01-01 08:00:00.0 +0800
+++ ukwm-1.2.0/debian/patches/fix-implicit-function-declaration-error.patch 
2024-03-15 14:10:00.0 +0800
@@ -0,0 +1,19 @@
+Description: fix implicit-function-declaration error 
+Author: Bo YU  
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066371
+Last-Update: 2024-03-15
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: ukwm-1.2.0/src/compositor/plugins/default.c
+===
+--- ukwm-1.2.0.orig/src/compositor/plugins/default.c
 ukwm-1.2.0/src/compositor/plugins/default.c
+@@ -53,6 +53,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++#include 
+ 
+ #include 
+ #include 
diff -Nru ukwm-1.2.0/debian/patches/series ukwm-1.2.0/debian/patches/series
--- ukwm-1.2.0/debian/patches/series2023-09-08 00:00:21.0 +0800
+++ ukwm-1.2.0/debian/patches/series2024-03-15 14:06:35.0 +0800
@@ -1 +1,2 @@
 stop-using-gnome-toggle-shaded.patch
+fix-implicit-function-declaration-error.patch


signature.asc
Description: PGP signature

Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

[Bo YU]

On Wed, Mar 13, 2024 at 12:37:02PM +0100, Lucas Nussbaum wrote:
...

cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not 
for C
y.tab.c: In function ‘_dxfccparse’:
_compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ 
[-Werror=implicit-function-declaration]
   51 | #define yylex   _dxfcclex
  | ^
y.tab.c:651:16: note: in expansion of macro ‘yylex’
y.tab.c:1107:16: note: in expansion of macro ‘YYLEX’
_compparse.c:52:17: error: implicit declaration of function ‘_dxfccerror’ 
[-Werror=implicit-function-declaration]
   52 | #define yyerror _dxfccerror
  | ^~~
y.tab.c:1682:2: note: in expansion of macro ‘yyerror’
./_compparse.y: In function ‘_dxfccerror’:
./_compparse.y:432:47: error: implicit declaration of function 
‘_dxfcclexerror’; did you mean ‘_dxfccerror’? 
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[6]: *** [Makefile:961: _compparse.lo] Error 1


I have attached one debdiff and it can be built with it. So could you
upload it with it? I can team upload if nobody response with this sor
some days.

BTW, dx upstream has dead, so refer to:
https://trac.macports.org/ticket/61842


--
Regards,
--
  Bo YU

diff -Nru dx-4.4.4/debian/changelog dx-4.4.4/debian/changelog
--- dx-4.4.4/debian/changelog   2024-02-29 07:06:03.0 +0800
+++ dx-4.4.4/debian/changelog   2024-03-14 14:17:17.0 +0800
@@ -1,3 +1,11 @@
+dx (1:4.4.4-15.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add -Wno-error=implicit-function-declaration into 
+DEB_CFLAGS_MAINT_APPEND. (Closes: #1066310)
+
+ -- Bo YU   Thu, 14 Mar 2024 14:17:17 +0800
+
 dx (1:4.4.4-15.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dx-4.4.4/debian/rules dx-4.4.4/debian/rules
--- dx-4.4.4/debian/rules   2024-02-29 07:06:00.0 +0800
+++ dx-4.4.4/debian/rules   2024-03-14 14:17:05.0 +0800
@@ -4,6 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 DEB_CFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
+DEB_CFLAGS_MAINT_APPEND=-Wno-error=implicit-function-declaration
 DEB_CXXFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 ifeq ($(DEB_HOST_ARCH), alpha)


signature.asc
Description: PGP signature

Bug#1061371: gcc-14 ftbfs on loong64

[Bo YU]

Hi!

On Tue, Mar 12, 2024 at 11:03 AM zhangdandan  wrote:
>
> Hi,
>   Thanks for your feedback on loong64's compilation errors.
>
> > > Package: src:gcc-14
> > > Version: 14-20240121-1
> > > Severity: important
> > > Tags: sid trixie ftbfs
> > > X-Debbugs-CC: debian-loonga...@lists.debian.org
> > >
> > > gcc-14 ftbfs on loong64:
> > >...
> >
> > The remaining build failure is now:
> >
> > https://buildd.debian.org/status/fetch.php?pkg=gcc-14=loong64=14-20240303-1=1709485913=0
> >
> > ...
> > dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 
> > usr/lib/loongarch64-linux-gnu
> > mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
> > debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.
> > mv: cannot stat 'debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1': 
> > No such file or directory
> > make[1]: *** [debian/rules.d/binary-libgcc.mk:291: 
> > stamps/08-binary-stamp-libgcc] Error 1
>
> - For the compilation error raised by Matthias Klose.
> It is because the linux header file linux-libc-dev lacks loong64 support.
> The Debian kernel-team has merged the loong64's patch, please see 
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/879.
>
> - I have reproduced the gcc-14 compilation error locally from Adrian Bunk.
> The compilation error is consistent with the feedback from Adrian Bunk.
> For gcc-14, the loong64's multilib modification is not included in 
> gcc-multilib-multiarch.
> Please consider the following patch. If you have any questions, you can 
> contact me at any time.
> ```
> --- a/src/gcc/config/loongarch/t-linux
> +++ b/src/gcc/config/loongarch/t-linux
> @@ -16,9 +16,9 @@
>  # along with GCC; see the file COPYING3.  If not see
>  # .
>
> -MULTIOSDIR_lp64d := ../lib64$(call if_multiarch,:loongarch64-linux-gnu)
> -MULTIOSDIR_lp64f := ../lib64/f32$(call 
> if_multiarch,:loongarch64-linux-gnuf32)
> -MULTIOSDIR_lp64s := ../lib64/sf$(call if_multiarch,:loongarch64-linux-gnusf)
> +MULTIOSDIR_lp64d := ../lib$(call if_multiarch,:loongarch64-linux-gnu)
> +MULTIOSDIR_lp64f := ../lib/f32$(call if_multiarch,:loongarch64-linux-gnuf32)
> +MULTIOSDIR_lp64s := ../lib/sf$(call if_multiarch,:loongarch64-linux-gnusf)
>
>  # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
>  ifeq ($(filter LA_DISABLE_MULTILIB,$(tm_defines)),)
> ```

Maybe debdiff should be attached here for GCC maintainer with conveniently.

BR,
Bo
>
> BTW, the gcc-14 source package was compiled successfully on my local loong64 
> rootfs environment, for examples,
> ```
> ..
> dh_installdirs -plibgcc-s1 usr/share/doc/libgcc-s1 
> usr/lib/loongarch64-linux-gnu
> mv debian/tmp/usr/lib/loongarch64-linux-gnu/libgcc_s.so.1 
> debian/libgcc-s1/usr/lib/loongarch64-linux-gnu/.
> debian/dh_doclink -plibgcc-s1 gcc-14-base
> ..
> dpkg-deb: building package 'libgfortran-14-dev' in 
> '../libgfortran-14-dev_14-20240201-3_loong64.deb'.
> dpkg-deb: building package 'g++-14-loongarch64-linux-gnu' in 
> '../g++-14-loongarch64-linux-gnu_14-20240201-3_loong64.deb'.
> dpkg-deb: building package 'gccrs-14-loongarch64-linux-gnu-dbgsym' in 
> '../gccrs-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.
> dpkg-deb: building package 'gcc-14-loongarch64-linux-gnu-dbgsym' in 
> '../gcc-14-loongarch64-linux-gnu-dbgsym_14-20240201-3_loong64.deb'.
> ..
> make[1]: Leaving directory '/home/zdd/gcc-14/gcc-14-14-20240201'
>  dpkg-genbuildinfo --build=binary -O../gcc-14_14-20240201-3_loong64.buildinfo
>  dpkg-genchanges --build=binary -O../gcc-14_14-20240201-3_loong64.changes
> ```
>
> thanks,
> Dandan Zhang
>

Bug#1066043: RFS: lem/2022-12-10+dfsg-1 [ITP] -- Tool merging math and logic for executable definitions (tool)

[Bo YU]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "lem":

 * Package name : lem
   Version  : 2022-12-10+dfsg-1
   Upstream contact : Lem Devs 
 * URL  : https://github.com/rems-project/lem
 * License  : GPL-2, BSD-3-clause
 * Vcs  : https://salsa.debian.org/ocaml-team/lem
   Section  : ocaml

The source builds the following binary packages:

  lem - Tool merging math and logic for executable definitions (tool)
  liblem-ocaml-dev - Tool merging math and logic for executable definitions 
(development)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/lem/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lem/lem_2022-12-10+dfsg-1.dsc

Changes for the initial release:

 lem (2022-12-10+dfsg-1) UNRELEASED; urgency=low
 .
   * Initial release. (Closes: #1065658)



-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065476: RFS: omd/1.3.2-1 [ITP] -- Markdown frontend in pure OCaml

[Bo YU]

Hi,
On Tue, Mar 05, 2024 at 04:31:35PM +0800, Bo YU wrote:

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "omd":

* Package name : omd
  Version  : 1.3.2-1
  Upstream contact : [fill in name and email of upstream]
* URL  : https://github.com/ocaml/omd
* License  : ISC
* Vcs  : https://salsa.debian.org/vimerbf-guest/omd


Moved to:

https://salsa.debian.org/ocaml-team/omd

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065420: RFS: ocaml-linenoise/1.5-1 [ITP] -- Lightweight readline alternative with OCaml

[Bo YU]

Hi,

On Mon, Mar 04, 2024 at 04:40:29PM +0800, Bo YU wrote:

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "ocaml-linenoise":

* Package name : ocaml-linenoise
  Version  : 1.5-1
  Upstream contact : Edgar Aroutiounian 
* URL  : https://github.com/ocaml-community/ocaml-linenoise
* License  : BSD-2-Clause
* Vcs  : https://salsa.debian.org/vimerbf-guest/ocaml-linenoise


I have moved the package from personal salsa namespace to Debian OCaml team:

* Vcs  : https://salsa.debian.org/ocaml-team/ocaml-linenoise
   Section  : ocaml

Please let me know any issues,


The source builds the following binary packages:

 liblinenoise-ocaml - Lightweight readline alternative with OCaml (runtime)
 liblinenoise-ocaml-dev - Lightweight readline alternative with OCaml 
(development)

To access further information about this package, please visit the following 
URL:

 https://mentors.debian.net/package/ocaml-linenoise/

Alternatively, you can download the package with 'dget' using this command:

 dget -x 
https://mentors.debian.net/debian/pool/main/o/ocaml-linenoise/ocaml-linenoise_1.5-1.dsc

Changes for the initial release:

ocaml-linenoise (1.5-1) UNRELEASED; urgency=low
.
  * Initial release. (Closes: #1064586)

--
Regards,
--
 Bo YU





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059264: qbs: ftbfs on riscv64: test timeout

[Bo YU]

Hi!

On Sun, Mar 3, 2024 at 10:43 PM Dmitry Shachnev  wrote:
...
>
> Right. I committed the patch so it will be part of the next upload, but
> I am not uploading it until the current version migrates to testing.

Thanks.:)
>
> Also, our debian/rules includes /usr/share/dpkg/default.mk which in turn
> includes architecture.mk, so $(DEB_BUILD_ARCH_CPU) is defined and there is
> no need to call dpkg-architecture explicitly. I have updated the patch
> based on that.

Ah, okay, TIL.

BR,
Bo

Bug#1065658: ITP: lem -- Lem semantic definition language

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: lem
  Version : 2022-12-10 
  Upstream Contact: Lem Devs 
* URL : https://github.com/rems-project/lem
* License : BSD-3
  Programming Lang: OCaml
  Description : Lem semantic definition language


Lem is a tool for lightweight executable mathematics, for writing, managing, 
and publishing large-scale portable semantic definitions, with export to LaTeX, 
executable code (currently OCaml) and interactive theorem provers (currently 
Coq, HOL4, and Isabelle/HOL, though the generated Coq is not necessarily 
idiomatic). It is also intended as an intermediate language for generating 
definitions from domain-specific tools, and for porting definitions between 
interactive theorem proving systems.

The language, originally based on a pure fragment of OCaml, combines features 
familiar from functional programming languages with logical constructs. From 
functional programming languages we take pure higher-order functions, general 
recursion, recursive algebraic datatypes, records, lists, pattern matching, 
parametric polymorphism, a simple type class mechanism for overloading, and a 
simple module system. To these we add logical constructs familiar in provers: 
universal and existential quantification, sets (including set comprehensions), 
relations, finite maps, inductive relation definitions, and lemma statements. 
Then there are facilities to let the user tune how Lem definitions are mapped 
into the various targets (by declaring target representations and controlling 
notation, renaming, inlining, and type classes), to generate witness types and 
executable functions from inductive relations, and for assertions.

->>>>---
The package is a dependency of sail[0] and linksem[1] and then I will
maintian it under Debian ocaml team.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065419
[1]: https://github.com/rems-project/linksem


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065476: RFS: omd/1.3.2-1 [ITP] -- Markdown frontend in pure OCaml

[Bo YU]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "omd":

 * Package name : omd
   Version  : 1.3.2-1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://github.com/ocaml/omd
 * License  : ISC
 * Vcs  : https://salsa.debian.org/vimerbf-guest/omd
   Section  : ocaml

The source builds the following binary packages:

  omd - Markdown frontend in pure OCaml (tools)
  libomd-ocaml-dev - Markdown frontend in pure OCaml (development)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/omd/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/o/omd/omd_1.3.2-1.dsc

Changes for the initial release:

 omd (1.3.2-1) UNRELEASED; urgency=low
 .
   * Initial release. (Closes: #1065417)

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065343: closed by Bo YU (Re: #1065343: libuuid1t64 overwrite)

[Bo YU]

Hi,
On Mon, Mar 04, 2024 at 10:45:41AM +0100, Chris Hofstaedtler wrote:

debootstrap still has issue:

```
...
tar: ./usr/lib/x86_64-linux-gnu/libuuid.so.1.3.0: Cannot open: File exists
tar: ./usr/lib/x86_64-linux-gnu/libuuid.so.1: Cannot create symlink to 
‘libuuid.so.1.3.0’: File exists
tar: Exiting with failure status due to previous errors

```

Anyone's help in assessing when this issue(t64 transition break debootstrap on 
sid) will be resolved would be appreciated!


There is nothing we can do now, that is not already on the todo list
of the people working on the transition.

Just be patient. It is, after all, unstable.


Thanks. Not rush, just hope people to be noteed about the issue.:)

I just reopen the bug given the currently status. Once fixed, I will
close it again. 


Hope #1036884 helps.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884#185



I'm told that other chroot-creation tools might not have this
problem (i.e. mmdebstrap).

Chris




--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065420: RFS: ocaml-linenoise/1.5-1 [ITP] -- Lightweight readline alternative with OCaml

[Bo YU]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "ocaml-linenoise":

 * Package name : ocaml-linenoise
   Version  : 1.5-1
   Upstream contact : Edgar Aroutiounian 
 * URL  : https://github.com/ocaml-community/ocaml-linenoise
 * License  : BSD-2-Clause
 * Vcs  : https://salsa.debian.org/vimerbf-guest/ocaml-linenoise
   Section  : ocaml

The source builds the following binary packages:

  liblinenoise-ocaml - Lightweight readline alternative with OCaml (runtime)
  liblinenoise-ocaml-dev - Lightweight readline alternative with OCaml 
(development)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/ocaml-linenoise/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/o/ocaml-linenoise/ocaml-linenoise_1.5-1.dsc

Changes for the initial release:

 ocaml-linenoise (1.5-1) UNRELEASED; urgency=low
 .
   * Initial release. (Closes: #1064586)

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065419: ITP: sail-ocaml -- Sail architecture definition language

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: sail-ocaml
  Version : 0.17.1
  Upstream Contact: rems-project 
* URL : https://github.com/rems-project/sail
* License : BSD-2-Clause
  Programming Lang: OCaml 
  Description : Sail architecture definition language with OCaml

Sail is a language for describing the instruction-set architecture (ISA) 
semantics of processors. Sail aims to provide a engineer-friendly, 
vendor-pseudocode-like language for describing instruction semantics. It is 
essentially a first-order imperative language, but with lightweight dependent 
typing for numeric types and bitvector lengths, which are automatically checked 
using Z3.

Given a Sail definition, the tool will type-check it and generate 
documentation, executable emulators (in C and OCaml), theorem-prover 
definitions (for Isabelle, HOL4, and Coq), and definitions to integrate with 
our RMEM and isla-axiomatic tools for concurrency semantics. The Isla engine 
provides SMT-based symbolic evaluation for Sail models, and the Islaris 
verification tool integrates Isla output with the Iris program logic to support 
proof about binary code in Coq. Not all models are integrated with all tools - 
see the most recent papers and models for descriptions of the current state.

>>>--
This is a denpendency of sail-riscv[0] and I will maintain it under
Debian OCaml team.

[0]: https://github.com/riscv/sail-riscv
-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065417: ITP: omd -- omd-ocaml

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: omd
  Version : 2.0.0 
  Upstream Contact: a...@recoil.org 
* URL : https://github.com/ocaml/omd
* License : ISC
  Programming Lang: OCaml
  Description : extensible Markdown library and tool in "pure OCaml"

Omd is an OCaml library designed to parse, manipulate, and print Markdown into 
different formats. In addition to the library, a command-line tool omd is 
included to easily convert markdown into HTML.

Omd aims for compliance with the CommonMark standard. We are currently 
compliant with 0.30 of the ComonMark spec.

--->>

This is a denpendency of sail[0].

[0]: https://github.com/rems-project/sail

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1065389: RFS: python-click/8.1.7-1 [ITA] -- Wrapper around optparse for command line utilities - documentation

[Bo YU]

Hi!

On Mon, Mar 4, 2024 at 1:51 AM Akash Doppalapudi
 wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "python-click":
>
>   * Package name : python-click
> Version  : 8.1.7-1
> Upstream contact : cont...@palletsprojects.com
>   * URL  : https://github.com/pallets/click
>   * License  : BSD-3-clause
>   * Vcs  :
> https://salsa.debian.org/python-team/packages/python-click
> Section  : python
>
> The source builds the following binary packages:
>
>python3-click - Wrapper around optparse for command line utilities -
> Python 3.x
>python-click-doc - Wrapper around optparse for command line utilities
> - documentation
>
> To access further information about this package, please visit the
> following URL:
>
>https://mentors.debian.net/package/python-click/
>
> Alternatively, you can download the package with 'dget' using this command:
>
>dget -x
> https://mentors.debian.net/debian/pool/main/p/python-click/python-click_8.1.7-1.dsc
>
> Changes since the last upload:
>
>   python-click (8.1.7-1) unstable; urgency=medium
>   .
> * New upstream version 8.1.7
> * New Maintainer (Closes: #1065251)

I would like to suggest you contact  Peter Pentchev 
as he/she has reported ITA earlier than your ITA.
And would you really want to maintain these packages without Debian
Python Team? No other meaning, just considering these packages should
be maintained under DPT sounds more reasonable.

BR,
Bo

> * d/control:
>   - Change Maintainer name
>   - Add python-click-doc in Suggests for python3-click
> * d/copyright:
>   - Add new maintainer name in copyright stanza
>
> Regards,
> --
>Akash Doppalapudi

Bug#1065194: RFS: python-raccoon/3.1.1-1 -- Python DataFrame with fast insert and appends (Python 3)

[Bo YU]

Hi,
On Fri, Mar 01, 2024 at 11:54:26PM +0530, Akash Doppalapudi wrote:

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-raccoon":

 * Package name : python-raccoon
   Version  : 3.1.1-1
   Upstream contact : Ryan Sheftel 
 * URL  : https://github.com/rsheftel/raccoon
 * License  : MIT
 * Vcs  : https://salsa.debian.org/debian/python-raccoon
   Section  : python

The source builds the following binary packages:

  python3-raccoon - Python DataFrame with fast insert and appends 
(Python 3)


To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/python-raccoon/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-raccoon/python-raccoon_3.1.1-1.dsc

Changes since the last upload:

 python-raccoon (3.1.1-1) unstable; urgency=medium
 .
   * New upstream version 3.1.1
   * New Maintainer


I think you need close this issue also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052685

BR,
Bo


signature.asc
Description: PGP signature

Bug#1059264: qbs: ftbfs on riscv64: test timeout

[Bo YU]

Hi,
On Sat, Mar 02, 2024 at 09:47:08PM +0300, Dmitry Shachnev wrote:

Hi!

On Thu, Feb 29, 2024 at 02:59:28PM +0800, Bo YU wrote:

Thanks for the hint. It seems it works once I enable
QTEST_FUNCTION_TIMEOUT. The value of it I just follow the [2] to set
`90` milliseconds (15 mins). But I am not sure the value is okay
for you.:)


Well, a test running for 15 minutes is not good, but as I said, it is
better than disabling it completely.


Thanks. The situation should be improved if we have more power riscv64
buildd, but unfortunately, we have to wait this for time.




I do not attend one debdiff file because now I have trouble to build
it on sid-riscv64-sbuild. Once done, I will update it here.


Looking forward to that.


Due to 2.1.2-2.1 was t64 transition related, so I have to generate
debdiff based on 2.1.2-2. So please let me know if any issue.

I should wait the 64 trsansition to finish but not sure how long it will
to achive this.


--
Dmitry Shachnev


--
Regards,
--
  Bo YU

diff -Nru qbs-2.1.2/debian/changelog qbs-2.1.2/debian/changelog
--- qbs-2.1.2/debian/changelog  2023-12-08 10:54:19.0 +
+++ qbs-2.1.2/debian/changelog  2024-02-28 07:19:35.0 +
@@ -1,3 +1,11 @@
+qbs (2.1.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Increase the timeout of qtest with QTEST_FUNCTION_TIMEOUT
+for riscv64. (Closes: #1059264)
+
+ -- Bo YU   Wed, 28 Feb 2024 07:19:35 +
+
 qbs (2.1.2-2) unstable; urgency=medium
 
   * Update debian/libqbscore2.1.symbols for loong64 (closes: #1057757).
diff -Nru qbs-2.1.2/debian/rules qbs-2.1.2/debian/rules
--- qbs-2.1.2/debian/rules  2023-12-08 10:54:19.0 +
+++ qbs-2.1.2/debian/rules  2024-02-28 07:19:35.0 +
@@ -3,6 +3,11 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+CPU_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_CPU)
+ifeq (riscv64,$(CPU_ARCH))
+export QTEST_FUNCTION_TIMEOUT=90
+endif
+
 include /usr/share/dpkg/default.mk
 
 BUILDPATH ?= obj-$(DEB_HOST_GNU_TYPE)


signature.asc
Description: PGP signature

Bug#1065137: pam: /usr/lib/x86_64-linux-gnu/libpam.so.0.85.1: Cannot open: File exist

[Bo YU]

Source: pam
Version: 1.5.3-6
Severity: important
Usertags: time-t

if use debootstrap:

```
debootstrap --arch=amd64 --verbose 
--include=fakeroot,symlinks,build-essential,libx11-dev,libxext-dev,libxrender-dev,libxrandr-dev,libxtst-dev,libxt-dev,libcups2-dev,libfontconfig1-dev,libasound2-dev,libfreetype-dev,libpng-dev
  --log-extra-deps --variant=minbase sid sysroot http://ftp.debian.org/debian/
```

will get:

```
2024-03-01 13:30:17 (1.31 MB/s) - 
‘/tmp/tmp/amd64/sysroot//var/cache/apt/archives/partial/zlib1g-dev_1%3a1.3.dfsg-3+b1_amd64.deb’
 saved [918640/918640]

tar: ./usr/lib/x86_64-linux-gnu/libpam.so.0.85.1: Cannot open: File exists
tar: ./usr/lib/x86_64-linux-gnu/libpam_misc.so.0.82.1: Cannot open: File exists
tar: ./usr/lib/x86_64-linux-gnu/libpamc.so.0.82.1: Cannot open: File exists
tar: ./usr/lib/x86_64-linux-gnu/libpam.so.0: Cannot create symlink to 
‘libpam.so.0.85.1’: File exists
tar: ./usr/lib/x86_64-linux-gnu/libpam_misc.so.0: Cannot create symlink to 
‘libpam_misc.so.0.82.1’: File exists
tar: ./usr/lib/x86_64-linux-gnu/libpamc.so.0: Cannot create symlink to 
‘libpamc.so.0.82.1’: File exists
tar: Exiting with failure status due to previous errors

```

The log snap is below:

```
vimer@dev:/tmp/tmp/amd64$ sudo debootstrap --arch=amd64 --verbose 
--include=fakeroot,symlinks,build-essential,libx11-dev,libxext-dev,libxrender-dev,libxrandr-dev,libxtst-dev,libxt-dev,libcups2-dev,libfontconfig1-dev,libasound2-dev,libfreetype-dev,libpng-dev
  --log-extra-deps --variant=minbase sid sysroot http://ftp.debian.org/debian/  
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 4CB50190207B4758A3F73A796ED0E7B82643E131)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found packages in base already in required: apt
I: Found additional required dependencies: debian-archive-keyring gcc-14-base 
gpgv libacl1 libapt-pkg6.0t64 libattr1 libaudit1 libaudit-common libblkid1 
libbz2-1.0 libc6 libcap2 libcap-ng0 libcom-err2t64 libcrypt1 libdebconfclient0 
libext2fs2 libffi8 libgcc-s1 libgcrypt20 libgmp10 libgnutls30 libgpg-error0 
libhogweed6 libidn2-0 liblz4-1 liblzma5 libmd0 libmount1 libnettle8 libp11-kit0 
libpam0g libpam0t64 libpcre2-8-0 libseccomp2 libselinux1 libsemanage2 
libsemanage-common libsepol2 libsmartcols1 libss2t64 libssl3 libstdc++6 
libsystemd0 libtasn1-6 libtinfo6 libudev1 libunistring5 libuuid1 libuuid1t64 
libxxhash0 libzstd1 logsave zlib1g
I: Found additional base dependencies: binutils binutils-common 
binutils-x86-64-linux-gnu bzip2 cpp cpp-13 cpp-13-x86-64-linux-gnu 
cpp-x86-64-linux-gnu dpkg-dev fontconfig-config fonts-dejavu-core 
fonts-dejavu-mono g++ g++-13 g++-13-x86-64-linux-gnu gcc gcc-13 gcc-13-base 
gcc-13-x86-64-linux-gnu gcc-x86-64-linux-gnu g++-x86-64-linux-gnu libasan8 
libasound2-data libasound2t64 libatomic1 libavahi-client3 libavahi-common3 
libavahi-common-data libbinutils libbrotli1 libbrotli-dev libbsd0 libbz2-dev 
libc6-dev libcc1-0 libc-dev-bin libcom-err2 libcrypt-dev libctf0 libctf-nobfd0 
libcups2t64 libcupsimage2-dev libcupsimage2t64 libdb5.3 libdbus-1-3 libdeflate0 
libdeflate-dev libdpkg-perl libexpat1 libexpat1-dev libfakeroot libfontconfig1 
libfontconfig-dev libfreetype6 libgcc-13-dev libgdbm6 libgdbm-compat4 
libgnutls30t64 libgomp1 libgprofng0 libgssapi-krb5-2 libhwasan0 libice6 
libice-dev libisl23 libitm1 libjansson4 libjbig0 libjbig-dev libjpeg62-turbo 
libjpeg62-turbo-dev libjpeg-dev libk5crypto3 libkeyutils1 libkrb5-3 
libkrb5support0 liblerc4 liblerc-dev liblsan0 liblzma-dev libmpc3 libmpfr6 
libnsl2 libnsl-dev libperl5.38 libpkgconf3 libpng16-16 libpng16-16t64 
libpthread-stubs0-dev libquadmath0 libsframe1 libsharpyuv0 libsharpyuv-dev 
libsm6 libsm-dev libstdc++-13-dev libtiff6 libtiff-dev libtiffxx6 libtirpc3 
libtirpc3t64 libtirpc-common libtirpc-dev libtsan2 libubsan1 libwebp7 
libwebpdecoder3 libwebpdemux2 libwebp-dev libwebpmux3 libx11-6 libx11-data 
libxau6 libxau-dev libxcb1 libxcb1-dev libxdmcp6 libxdmcp-dev libxext6 
libxfixes3 libxfixes-dev libxi6 libxi-dev libxrandr2 libxrender1 libxt6 
libxtst6 libzstd-dev linux-libc-dev lsb-base make patch perl perl-modules-5.38 
pkgconf pkgconf-bin rpcsvc-proto uuid-dev x11-common x11proto-core-dev 
x11proto-dev x11proto-record-dev x11proto-render-dev x11proto-xext-dev 
xorg-sgml-doctools xtrans-dev xz-utils zlib1g-dev
I: Checking component main on http://ftp.debian.org/debian...
I: Retrieving apt 2.7.13

```
In 1.5.3-6 we have reomved libpam0t64 I think, but why debootstrap
dependes on it again? Is this a known issue?


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059264: qbs: ftbfs on riscv64: test timeout

[Bo YU]

Hi!

On Mon, Feb 26, 2024 at 4:52 PM Dmitry Shachnev  wrote:
>
> Hi!
>
> On Fri, Dec 22, 2023 at 05:25:52PM +0800, Bo YU wrote:
> > Package: qbs
> > Version: 1.24.1+dfsg-2
> > Severity: important
> > Tags: ftbfs patch
> > User: debian-ri...@lists.debian.org
> > Usertags: riscv64
> > X-Debbugs-Cc: debian-ri...@lists.debian.org
> >
> > Dear Maintainer,
> >
> > qbs has ftbfs on riscv64 since 2.1.1-2(2023/08) on sid. The problem is
> > due to timeout on buildd machines for riscv64 now:
> >
> > [...]
> >
> > So we can see the timeout on tst_blackbox-qt suite mainly. But the
> > question is that failed test function cases are randomized. So I have
> > captured a few cases to temporarily skip over riscv64 buildd(holpe this
> > works). And I would like to suggest that we keep opening the reportbug
> > until we have more powerful buildd machines to close it as expected
> > it. I can build it on vf2 without any patch but it has not been tested
> > many times.
> >
> > So could you apply it on next upload or any ideas?
>
> I would prefer increasing the timeout to disabling the test.
>
> The blackbox tests start qbs in a subprocess and wait for it to finish in a
> reasonable time [1]. The value of testTimeoutInMsecs() can be configured by
> QBS_AUTOTEST_TIMEOUT environment variable, which specifies time in seconds and
> is 600 by default, which is 10 minutes.
>
> However, Qt test library has its own timeout: any test function call is
> interrupted in 5 minutes [2]. This can be configured by QTEST_FUNCTION_TIMEOUT
> variable, which is in milliseconds. It looks like this is the timeout that
> occurs in the log fragments you provided.
>
> Do you have any way to check if increasing QTEST_FUNCTION_TIMEOUT helps to
> get it built on slow riscv64 machines. And if yes, to what value it should
> be increased?

Thanks for the hint. It seems it works once I enable
QTEST_FUNCTION_TIMEOUT. The value of it I just follow the [2] to set
`90` milliseconds (15 mins). But I am not sure the value is okay
for you.:)

I do not attend one debdiff file because now I have trouble to build
it on sid-riscv64-sbuild. Once done, I will update it here.

Thnak you,
BR,
Bo
>
> [1]: 
> https://sources.debian.org/src/qbs/2.1.2-2/tests/auto/blackbox/tst_blackboxbase.cpp/#L100
> [2]: 
> https://doc.qt.io/qt-6/qtest-overview.html#increasing-test-function-timeout
>
> --
> Dmitry Shachnev

Bug#1064650: Bug#1052429: fixed in snapd-glib 1.63-5.1

[Bo YU]

Hi,
On Sun, Feb 25, 2024 at 06:23:33PM +0100, Paul Gevers wrote:

Control: clone -1 -2
Control: retitle -2 FTBFS on mips64el, ppc64el and s390x
Control: reopen -2


I followed the wiki[0] to update the symbols and has tested it on
mips64el,ppc64el,and s390x even arm64 and i386 also with qemu user mode.
so if someone can upload it with the debdiff?

BR,
Bo

[0]: https://www.eyrie.org/~eagle/journal/2012-01/008.html


Paul





--
Regards,
--
  Bo YU

diff -Nru snapd-glib-1.63/debian/changelog snapd-glib-1.63/debian/changelog
--- snapd-glib-1.63/debian/changelog2024-01-08 16:11:01.0 +0800
+++ snapd-glib-1.63/debian/changelog2024-02-25 22:58:46.0 +0800
@@ -1,3 +1,11 @@
+snapd-glib (1.63-5.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update libsnapd-qt-2-1.symbols again to fix ftbfs on mips64el,
+ppc64el, s390x. (Closes: #-1)
+
+ -- Bo YU   Sun, 25 Feb 2024 22:58:46 +0800
+
 snapd-glib (1.63-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols 
snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols
--- snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols  2024-01-08 
16:10:23.0 +0800
+++ snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols  2024-02-25 
20:59:53.0 +0800
@@ -888,8 +888,8 @@
  (optional=templinst)_ZN5QHashI7QString8QVariantED2Ev@Base 1.58
  
(optional=templinst)_ZN5QListI18QSnapdMarkdownNodeE18detach_helper_growEii@Base 
1.58
  (optional=templinst)_ZN5QListI18QSnapdMarkdownNodeE6appendERKS0_@Base 1.58
-#MISSING: 1.63-1# 
(optional=templinst|arch=amd64)_ZN5QListI18QSnapdMarkdownNodeED1Ev@Base 1.58
-#MISSING: 1.63-1# 
(optional=templinst|arch=amd64)_ZN5QListI18QSnapdMarkdownNodeED2Ev@Base 1.58
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa i386 ia64 m68k 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN5QListI18QSnapdMarkdownNodeED1Ev@Base 1.63
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa i386 ia64 m68k 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN5QListI18QSnapdMarkdownNodeED2Ev@Base 1.63
  (optional=templinst)_ZN5QListI7QStringE18detach_helper_growEii@Base 1.58
  (optional=templinst)_ZN5QListI7QStringE6appendERKS0_@Base 1.58
  (optional=templinst)_ZN5QListI7QStringEC1ERKS1_@Base 1.58
@@ -901,8 +901,8 @@
  (optional=templinst)_ZN5QListI8QVariantE6appendERKS0_@Base 1.58
  (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.58
  (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.58
- (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !m68k !mips64el 
!powerpc !ppc64 !ppc64el !s390x !sh4 !sparc64 !x32)_ZN7QStringC1ERKS_@Base 1.63
- (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !m68k !mips64el 
!powerpc !ppc64 !ppc64el !s390x !sh4 !sparc64 !x32)_ZN7QStringC2ERKS_@Base 1.63
+ (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !sh4 !sparc64 
!x32)_ZN7QStringC1ERKS_@Base 1.63
+ (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !sh4 !sparc64 
!x32)_ZN7QStringC2ERKS_@Base 1.63
  _ZN7QStringD1Ev@Base 1.58
  _ZN7QStringD2Ev@Base 1.58
  (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 
1.58


signature.asc
Description: PGP signature

Bug#1052429: fixed in snapd-glib 1.63-5.1

[Bo YU]

Hi,

On Sun, Feb 25, 2024 at 4:27 PM Paul Gevers  wrote:
>
> Hi Bastian, Bo,
>
> On Thu, 11 Jan 2024 00:07:10 + Debian FTP Masters
>  wrote:
> > Maintainer: Ayatana Packagers 
> > Changed-By: Bo YU 
> > Closes: 1052429
> > Changes:
> >  snapd-glib (1.63-5.1) unstable; urgency=medium
> >  .
> >* Non-maintainer upload.
> >* Update libsnapd-qt-2-1.symbols to support riscv64. (Closes: #1052429)
>
> May I remind you that this upload broke the mips64el, ppc64el and s390x
> builds as reported in bug 1063799. Can you please have a look and fix?
> It seems these added symbols are not exclusive to riscv64 and your patch
> is wrong.

Thanks for your reminder here. I will look at it here but I am busy
with other projects so wait it
some days later.

BR,
Bo
>
> Paul

Bug#1064586: ITP: ocaml-linenoise -- Self-contained OCaml bindings to linenoise, easy high level readline functionality in OCaml

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-ocaml-ma...@lists.debian.org

* Package name: ocaml-linenoise
  Version : v1.5 
  Upstream Contact: ocaml-community 
* URL : https://github.com/ocaml-community/ocaml-linenoise/ 
* License : BSD
  Programming Lang: ocaml
  Description : Self-contained OCaml bindings to linenoise, easy high level 
readline functionality in OCaml

Below is descriptions from homepage:

BSD licensed.
No system dependencies, no need for readline on your machine.
Related to 2, these bindings are self-contained, the source for linenoise is in 
this repo and compiled all together with the OCaml.
Written in OCaml + C.
Pretty cool hints feature, see the gif.
Additional features compared to linenoise, such as history search

The package is a dependency of sail[0] and and I will maintain it under
Debian ocaml team.

[0]: https://github.com/rems-project/sail
-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064128: your mail

[Bo YU]

Hi,
On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote:

...and 2.2.4 also fails to build:
https://github.com/savonet/liquidsoap/issues/3752


Thanks.


$ make
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51:
314 | (Decoder.test_file ~log ~mimes:mime_types#get
  ^^
Error: This expression has type string list
  but an expression was expected of type string list option
make: *** [Makefile:4: build] Error 1


Yeah, I got this error after upgrading 2.2.4 also.
And it seems upstream suggests to ship the package wihtout gstreamer:
https://github.com/savonet/liquidsoap/discussions/3751#discussioncomment-8524446

It will cost more time for me how to disable this on Debian packaging.


--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Bo YU]

Source: rnp
Version: 0.17.0-3
Severity: serious 

Dear Maintainer,

The package has a ftbfs issue on my local amd64 build:

```
260/260 Test #255: cli_tests-Encryption 
..   Passed   60.86 sec

98% tests passed, 6 tests failed out of 260

Total Test time (real) =  71.61 sec

The following tests FAILED:
 90 - rnp_tests.test_ffi_security_profile (Failed)
159 - rnp_tests.test_rnp_access (Failed)
166 - rnp_tests.rnpkeys_generatekey_verifykeyHomeDirNoPermission 
(Failed)
174 - rnp_tests.test_key_add_userid (Failed)
258 - cli_tests-EncryptElgamal (Failed)
259 - cli_tests-Misc (Failed)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
make[1]: Leaving directory '/<>/build'
dh_auto_test: error: cd build && make -j16 test ARGS\+=--verbose ARGS\+=-j16 
returned exit code 2
make: *** [debian/rules:33: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Build finished at 2024-02-22T22:48:30Z
```

It was failed on riscv64 also, but less test cases than amd64:

```
The following tests FAILED:
 90 - rnp_tests.test_ffi_security_profile (Failed)
174 - rnp_tests.test_key_add_userid (Failed)
251 - cli_tests-EncryptElgamal (Failed)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=rnp=riscv64=0.17.0-3%2Bb2=1708576037=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064331: nodejs: FTBFS on riscv64: some test cases faileder: debian-riscv@lists.debian.orgertags: riscv64

[Bo YU]

Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

On Tue, Feb 20, 2024 at 10:57:35AM +0800, Bo YU wrote:

Package: nodejs
Version: 18.19.1+dfsg-1
Severity: important

Dear Maintainer,

Nodejs 18.19.1+dfsg-1 has a ftbfs issue due to some test cases failed:

```
...
Failed tests:
./node /<>/test/parallel/test-runner-output.mjs
./node /<>/test/sequential/test-cpu-prof-dir-and-name.js
./node /<>/test/sequential/test-cpu-prof-name.js
...
```

Full buildd log see here:
https://buildd.debian.org/status/fetch.php?pkg=nodejs=riscv64=18.19.1%2Bdfsg-1=1708327149=0

I have flaged these tests with flaky status and confirmed it works.

So could we apply it on next upload?

BTW, there is some tests failed on mips64el, but I have no mips64el
machine to confirm if flag these tests with flaky is okay or not like on
riscv64. See #1064306.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064306

--
Regards,
--
 Bo YU




diff -Nru nodejs-18.19.1+dfsg/debian/changelog 
nodejs-18.19.1+dfsg/debian/changelog
--- nodejs-18.19.1+dfsg/debian/changelog2024-02-19 01:12:23.0 
+0800
+++ nodejs-18.19.1+dfsg/debian/changelog2024-02-19 18:34:13.0 
+0800
@@ -1,3 +1,10 @@
+nodejs (18.19.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update riscv patch to fix ftbfs issue. (Closes: #-1)
+
+ -- Bo YU   Mon, 19 Feb 2024 18:34:13 +0800
+
nodejs (18.19.1+dfsg-1) unstable; urgency=medium

  * New upstream version 18.19.1. Closes: 1064055.
diff -Nru nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch 
nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch
--- nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-15 
06:11:51.0 +0800
+++ nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-19 
18:25:42.0 +0800
@@ -3,9 +3,11 @@
Author: J�r�my Lal , Bo YU 
Forwarded: not-yet

 a/test/sequential/sequential.status
-+++ b/test/sequential/sequential.status
-@@ -65,3 +65,19 @@
+Index: nodejs-18.19.1+dfsg/test/sequential/sequential.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/sequential/sequential.status
 nodejs-18.19.1+dfsg/test/sequential/sequential.status
+@@ -65,3 +65,21 @@ test-watch-mode-inspect: PASS, FLAKY
 [$arch==s390x]
 # https://github.com/nodejs/node/issues/41286
 test-performance-eventloopdelay: PASS, FLAKY
@@ -13,8 +15,10 @@
+[$arch==riscv64]
+test-diagnostic-dir-cpu-prof: PASS, FLAKY
+test-cpu-prof-worker-argv: PASS, FLAKY
++test-cpu-prof-dir-and-name: PASS, FLAKY
+test-cpu-prof-exit: PASS, FLAKY
+test-cpu-prof-kill: PASS, FLAKY
++test-cpu-prof-name: PASS, FLAKY
+test-diagnostic-dir-cpu-prof: PASS, FLAKY
+test-debugger-auto-resume: PASS, FLAKY
+test-debugger-preserve-breaks: PASS, FLAKY
@@ -25,9 +29,11 @@
+test-cpu-prof-dir-absolute: PASS, FLAKY
+
+
 a/test/parallel/parallel.status
-+++ b/test/parallel/parallel.status
-@@ -150,6 +150,22 @@
+Index: nodejs-18.19.1+dfsg/test/parallel/parallel.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/parallel/parallel.status
 nodejs-18.19.1+dfsg/test/parallel/parallel.status
+@@ -150,6 +150,23 @@ test-tls-write-error: PASS, FLAKY
 # https://github.com/nodejs/node/issues/48047
 test-http-pipeline-flood: SKIP

@@ -35,6 +41,7 @@
+test-fetch: PASS, FLAKY
+test-net-socket-connect-without-cb: PASS, FLAKY
+test-runner-inspect: PASS, FLAKY
++test-runner-output: PASS, FLAKY
+test-tcp-wrap-listen: PASS, FLAKY
+test-wasm-web-api: PASS, FLAKY
+test-vm-timeout-escape-promise-module: PASS, FLAKY





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064331: nodejs: FTBFS on riscv64: some test cases failed

[Bo YU]

Package: nodejs
Version: 18.19.1+dfsg-1
Severity: important

Dear Maintainer,

Nodejs 18.19.1+dfsg-1 has a ftbfs issue due to some test cases failed:

```
...
Failed tests:
./node /<>/test/parallel/test-runner-output.mjs
./node /<>/test/sequential/test-cpu-prof-dir-and-name.js
./node /<>/test/sequential/test-cpu-prof-name.js
...
```

Full buildd log see here:
https://buildd.debian.org/status/fetch.php?pkg=nodejs=riscv64=18.19.1%2Bdfsg-1=1708327149=0

I have flaged these tests with flaky status and confirmed it works.

So could we apply it on next upload?

BTW, there is some tests failed on mips64el, but I have no mips64el
machine to confirm if flag these tests with flaky is okay or not like on
riscv64. See #1064306.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064306

-- 
Regards,
--
  Bo YU

diff -Nru nodejs-18.19.1+dfsg/debian/changelog 
nodejs-18.19.1+dfsg/debian/changelog
--- nodejs-18.19.1+dfsg/debian/changelog2024-02-19 01:12:23.0 
+0800
+++ nodejs-18.19.1+dfsg/debian/changelog2024-02-19 18:34:13.0 
+0800
@@ -1,3 +1,10 @@
+nodejs (18.19.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update riscv patch to fix ftbfs issue. (Closes: #-1)
+
+ -- Bo YU   Mon, 19 Feb 2024 18:34:13 +0800
+
 nodejs (18.19.1+dfsg-1) unstable; urgency=medium
 
   * New upstream version 18.19.1. Closes: 1064055.
diff -Nru nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch 
nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch
--- nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-15 
06:11:51.0 +0800
+++ nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-19 
18:25:42.0 +0800
@@ -3,9 +3,11 @@
 Author: Jérémy Lal , Bo YU 
 Forwarded: not-yet
 
 a/test/sequential/sequential.status
-+++ b/test/sequential/sequential.status
-@@ -65,3 +65,19 @@
+Index: nodejs-18.19.1+dfsg/test/sequential/sequential.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/sequential/sequential.status
 nodejs-18.19.1+dfsg/test/sequential/sequential.status
+@@ -65,3 +65,21 @@ test-watch-mode-inspect: PASS, FLAKY
  [$arch==s390x]
  # https://github.com/nodejs/node/issues/41286
  test-performance-eventloopdelay: PASS, FLAKY
@@ -13,8 +15,10 @@
 +[$arch==riscv64]
 +test-diagnostic-dir-cpu-prof: PASS, FLAKY
 +test-cpu-prof-worker-argv: PASS, FLAKY
++test-cpu-prof-dir-and-name: PASS, FLAKY
 +test-cpu-prof-exit: PASS, FLAKY
 +test-cpu-prof-kill: PASS, FLAKY
++test-cpu-prof-name: PASS, FLAKY
 +test-diagnostic-dir-cpu-prof: PASS, FLAKY
 +test-debugger-auto-resume: PASS, FLAKY
 +test-debugger-preserve-breaks: PASS, FLAKY
@@ -25,9 +29,11 @@
 +test-cpu-prof-dir-absolute: PASS, FLAKY
 +
 +
 a/test/parallel/parallel.status
-+++ b/test/parallel/parallel.status
-@@ -150,6 +150,22 @@
+Index: nodejs-18.19.1+dfsg/test/parallel/parallel.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/parallel/parallel.status
 nodejs-18.19.1+dfsg/test/parallel/parallel.status
+@@ -150,6 +150,23 @@ test-tls-write-error: PASS, FLAKY
  # https://github.com/nodejs/node/issues/48047
  test-http-pipeline-flood: SKIP
  
@@ -35,6 +41,7 @@
 +test-fetch: PASS, FLAKY
 +test-net-socket-connect-without-cb: PASS, FLAKY
 +test-runner-inspect: PASS, FLAKY
++test-runner-output: PASS, FLAKY
 +test-tcp-wrap-listen: PASS, FLAKY
 +test-wasm-web-api: PASS, FLAKY
 +test-vm-timeout-escape-promise-module: PASS, FLAKY


signature.asc
Description: PGP signature

Bug#1064255: ITP: aemu -- This is an utility library for common functions used in the Android Emulator. External projects (gfxstream, QEMU) may use to perform C++ functions.

[Bo YU]

Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: aemu
  Version : 0.1.2 
  Upstream Contact: Google 
* URL : 
https://android.googlesource.com/platform/hardware/google/aemu/ 
* License : Apache-2.0 
  Programming Lang: C++ 
  Description : This is an utility library for common functions used in the 
Android Emulator. External projects (gfxstream, QEMU) may use to perform C++ 
functions.

AEMU development files, used by gfxstream to build against.

This is a blocker of #1059295 as above descriptions.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059295

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064178: RFS: xwayland-run/0.0.2-1 [ITP] -- Set of utilities to run headless X/Wayland clients

[Bo YU]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "xwayland-run":

 * Package name : xwayland-run
   Version  : 0.0.2-1
   Upstream contact : Olivier Fourdan 
 * URL  : https://gitlab.freedesktop.org/ofourdan/xwayland-run
 * License  : GPL-2.0+
 * Vcs  : https://salsa.debian.org/vimerbf-guest/xwayland-run
   Section  : x11

The source builds the following binary packages:

  xwayland-run - Set of utilities to run headless X/Wayland clients

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/xwayland-run/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xwayland-run/xwayland-run_0.0.2-1.dsc

Changes for the initial release:

 xwayland-run (0.0.2-1) UNRELEASED; urgency=low
 .
   * Initial release. (Closes: #1061513)

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064128: FTBFS: Error: Unbound module Pcre

[Bo YU]

Package: liquidsoap
Version: 2.2.3-1
Severity: serious

Dear Maintainer,

The package has one ftbfs issue due to:

```
299 | let key = Pcre.get_substring sub 1 in
^^
Error: Unbound module Pcre
(cd _build/default && /usr/bin/ocamlc.opt -w -40 -g -bin-annot -I 
src/core/.liquidsoap_core.objs/byte -I /usr/lib/ocaml/angstrom -I 
/usr/lib/ocaml/bigstringaf -I /usr/lib/ocaml/bytes -I 
/usr/lib/ocaml/camlp-streams -I /usr/lib/ocaml/camomile/lib -I 
/usr/lib/ocaml/cry -I /usr/lib/ocaml/curl -I /usr/lib/ocaml/dtools -I 
/usr/lib/ocaml/dune-build-info -I /usr/lib/ocaml/dune-private-libs/dune-section 
-I /usr/lib/ocaml/dune-site -I /usr/lib/ocaml/dune-site/private -I 
/usr/lib/ocaml/duppy -I /usr/lib/ocaml/fileutils -I /usr/lib/ocaml/gen -I 
/usr/lib/ocaml/inotify -I /usr/lib/ocaml/magic -I /usr/lib/ocaml/menhirLib -I 
/usr/lib/ocaml/metadata -I /usr/lib/ocaml/mm -I /usr/lib/ocaml/mm/audio -I 
/usr/lib/ocaml/mm/base -I /usr/lib/ocaml/mm/image -I /usr/lib/ocaml/mm/midi -I 
/usr/lib/ocaml/mm/video -I /usr/lib/ocaml/re -I /usr/lib/ocaml/sedlex -I 
/usr/lib/ocaml/seq -I /usr/lib/ocaml/stdlib-shims -I /usr/lib/ocaml/stringext 
-I /usr/lib/ocaml/syslog -I /usr/lib/ocaml/threads -I /usr/lib/ocaml/uri -I 
src/console/.console.objs/byte -I src/lang/.liquidsoap_lang.objs/byte 
-no-alias-deps -o src/core/.liquidsoap_core.objs/byte/ffmpeg_format.cmo -c 
-impl src/core/encoder/formats/ffmpeg_format.pp.ml)
File "src/core/encoder/formats/ffmpeg_format.ml", line 136, characters 20-31:
136 | (if Pcre.pmatch ~pat:"video" name then "" else 
"video_content,")
  ^^^
Error: Unbound module Pcre
(cd _build/default && /usr/bin/ocamlopt.opt -w -40 -g -w -9 -alert --deprecated 
-O2 -I src/core/.liquidsoap_core.objs/byte -I 
src/core/.liquidsoap_core.objs/native -I /usr/lib/ocaml/angstrom -I 
/usr/lib/ocaml/bigstringaf -I /usr/lib/ocaml/bytes -I 
/usr/lib/ocaml/camlp-streams -I /usr/lib/ocaml/camomile/lib -I 
/usr/lib/ocaml/cry -I /usr/lib/ocaml/curl -I /usr/lib/ocaml/dtools -I 
/usr/lib/ocaml/dune-build-info -I /usr/lib/ocaml/dune-private-libs/dune-section 
-I /usr/lib/ocaml/dune-site -I /usr/lib/ocaml/dune-site/private -I 
/usr/lib/ocaml/duppy -I /usr/lib/ocaml/fileutils -I /usr/lib/ocaml/gen -I 
/usr/lib/ocaml/inotify -I /usr/lib/ocaml/magic -I /usr/lib/ocaml/menhirLib -I 
/usr/lib/ocaml/metadata -I /usr/lib/ocaml/mm -I /usr/lib/ocaml/mm/audio -I 
/usr/lib/ocaml/mm/base -I /usr/lib/ocaml/mm/image -I /usr/lib/ocaml/mm/midi -I 
/usr/lib/ocaml/mm/video -I /usr/lib/ocaml/re -I /usr/lib/ocaml/sedlex -I 
/usr/lib/ocaml/seq -I /usr/lib/ocaml/stdlib-shims -I /usr/lib/ocaml/stringext 
-I /usr/lib/ocaml/syslog -I /usr/lib/ocaml/threads -I /usr/lib/ocaml/uri -I 
src/console/.console.objs/byte -I src/console/.console.objs/native -I 
src/lang/.liquidsoap_lang.objs/byte -I src/lang/.liquidsoap_lang.objs/native 
-intf-suffix .ml -no-alias-deps -o 
src/core/.liquidsoap_core.objs/native/http.cmx -c -impl 
src/core/tools/http.pp.ml)
File "src/core/tools/http.ml", line 69, characters 10-20:
69 | match Pcre.split ~pat:"=" arg with
   ^^
Error: Unbound module Pcre
dh_auto_build: error: dune build -j 4 -p 
liquidsoap,liquidsoap-core,liquidsoap-lang,liquidsoap-js,liquidsoap-libs,liquidsoap-libs-extra,liquidsoap-mode,tls-liquidsoap,sdl-liquidsoap
 returned exit code 1
make: *** [debian/rules:7: binary-arch] Error 25

```

Although it was failed with -b1 version on buildd[0], but it is reproduced on 
my local build for amd64 and riscv64 also.


[0]: 
https://buildd.debian.org/status/fetch.php?pkg=liquidsoap=amd64=2.2.3-1%2Bb1=1708087445=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1051998: chromium: please to add support for riscv64

[Bo YU]

Version: 121.0.6167.85-1
Tags: patch

Sorry for the wrong version in the previous email.

Bo
On Wed, Jan 17, 2024 at 10:40 AM Bo YU  wrote:
>
> Version: 120.0.6099.216-1
> Tags: patch
>
> On Tue, Dec 19, 2023 at 10:03:18PM +0800, Bo YU wrote:
> >Version: 120.0.6099.109-1
> >Tags: patch
> >
> >Hi,
> >On Fri, Nov 24, 2023 at 11:52:01PM -0500, Daniel Richard G. wrote:
> >>On Thu, 2023 Nov 23 22:44-05:00, Bo YU wrote:
> >>>
> >>>But likely the Chromium developer has picked this now:
> >>>1. angle:
> >>>https://chromium-review.googlesource.com/c/angle/angle/+/5057086
> >>>2. base:
> >>>https://chromium-review.googlesource.com/c/chromium/src/+/5054184
> >>>3. sandbox:
> >>>https://chromium-review.googlesource.com/c/chromium/src/+/5056263
> >>>4. ffmpeg:
> >>>https://chromium-review.googlesource.com/c/chromium/third_party/ffmpeg/+/5054185
> >>>
> >>>we have one dav1d to be left, but the developer told me he has did it.
> >
> >The good news is that angle and base support riscv64 both was merged by
> >chromium upstream.
> >
> >sandbox and ffmpeg support riscv64 was become more complicated: first
> >get approval from Chromium ATLs, see:
> >https://chromium-review.googlesource.com/c/chromium/third_party/ffmpeg/+/5054185/comments/72ecb31a_56bf277d
> >
> >https://chromium-review.googlesource.com/c/chromium/src/+/4935120
> >
> >>
> >>Thanks Bo. It is good that the upstream is willing to accept patches for
> >>riscv64. I was worried that Google would not support the platform, in
> >>the same way that they do not support ppc64el.
> >
> >Thanks. CCing Yahan here also.:)
> >>
> >>I had considered adjusting the patches here so that they can be applied
> >>after the ppc64el patches. (There is no way that a conditional patch set
> >>would be accepted by Debian---all the patches have to apply together.)
> >>But if the patches are accepted by the upstream, then there is no need
> >>to adjust the patches for Debian.
>
> The good news is that I have adjusted these patches which can be applied
> after ppc64el.
>
> These patches did not change since previous update and I have descripted
> their status with upstream support. It seems very pretty that looks like
> got upstream support whole.
>
> BR,
> Bo
> >
> >hmm, this time I have dropped 2 patches which upstream has updated based
> >on 120. Later version we will remove more riscv64 patch here. But we all
> >know, the most two biggest blockers are sandbox and ffmpeg.
> >
> >Thanks your suggestions here.
> >
> >I can cost some time to try apply these patches together and feedback to
> >here also.
> >
> >>
> >
> >--
> >Regards,
> >--
> >  Bo YU
> >
>

Bug#1062075: lomiri-app-launch: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2

[Bo YU]

Source: lomiri-app-launch
Version: 0.1.7-1
Severity: serious 

Dear Maintainer,

The package has a ftbfs issue on my amd64 build:


69% tests passed, 4 tests failed out of 13

Total Test time (real) = 201.54 sec

The following tests FAILED:
  1 - helper-test (Failed)
  4 - liblal-cpp-test (Failed)
 10 - list-apps (Failed)
 13 - desktop-hook-test (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose 
ARGS\+=-j1 returned exit code 2
make[1]: *** [debian/rules:44: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:28: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



And it fails to build on riscv64 also:

```
92% tests passed, 1 tests failed out of 13

Total Test time (real) = 293.12 sec

The following tests FAILED:
  4 - liblal-cpp-test (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8
```

See full buildd log:
https://buildd.debian.org/status/fetch.php?pkg=lomiri-app-launch=riscv64=0.1.7-1=1706578146=0

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059511: [Pkg-opencl-devel] Bug#1059511: pocl: FTBFS on riscv64: testsuite fails: can't link double-float modules with soft-float modules

[Bo YU]

Hi,

On Thu, Jan 18, 2024 at 5:41 PM Andreas Beckmann  wrote:
>
> On 18/01/2024 08.41, Bo YU wrote:
> > Obviously these tests failed was due to vectors missing from riscv64
> > now. This is expected I think.
> >
> > The result is aligned with pocl upstream support riscv64:
> >
> > ```
> > In this release we improved support for RISC-V CPUs. We tested PoCL on a 
> > Starfive VisionFive 2 using a Ubuntu 23.10 preinstalled image. With LLVM 17 
> > and GCC 13.2, 98% tests pass (only 4 tests fail out of 253).
>
> If these tests are expected to fail, they should be annotated as such
> for riscv64 (see e.g. handing of kernel/test_printf_vectors in
> tests/kernel/CMakeLists.txt). Is there an upstream bug about these tests
> failing on risc-v?

I have report the issue to upstream and got their confirmation:
https://github.com/pocl/pocl/issues/1394

>
> printf is a mess on most architectures (even or especially also x86)
> since the ABI for passing the variadic parameters is not well defined,
> especially when it comes to OpenCL vector types.
>
> > So I suspect the `LLC_HOST_CPU='` was overriden by `GENERIC` then the
> > ABI was different. I will look at this more deeper.
>
> GENERIC is a Debian specific patch to build for the LLVM default target
> (i.e. without specifying -march=$whatever), s.t. the generated code
> targets the riscv64 baseline (like all code in Debian binary packages).
> (Assuming llvm targets the same baseline cpu architecture as gcc, which
> unfortunately is not true for all Debian architectures.)
> (By default upstream pocl wants to build for the native CPU which is a
> no-go for distributing binaries. In order to fully utilize capabilities
> for more modern CPUs (e.g. wider SIMD registers), pocl has a distro mode
> where the bitcode libraries are provided for multiple targets and the
> best one for the local CPU is selected at runtime. But first we should
> get a baseline build for risc-v before we look into optimizing it (i.e.
> supporting separately both CPUs without and with vector unit).

Thanks.

So we need to enable to select the best one for local CPU when runtime
for riscv64 here. I looked at the patch:
https://salsa.debian.org/opencl-team/pocl/-/blob/main/debian/patches/generic-cpu.patch?ref_type=heads
But I am not sure how to enable this.

The baseline of riscv64 port here is here:
```
The Debian port uses RV64GC as the hardware baseline and the lp64d ABI
(the default ABI for RV64G systems)
```
https://wiki.debian.org/RISC-V#Hardware_baseline_and_ABI_choice

Is this enough information? Please let me know of any issues or I can
do some experiment about this.

BR,
Bo
>
> Andreas
>
> PS: I'll look into switching pocl to llvm-16 now

Bug#1059511: pocl: FTBFS on riscv64: testsuite fails: can't link double-float modules with soft-float modules

[Bo YU]

Source: pocl
Version: 5.0-1
Followup-For: Bug #1059511

I cost some time to try to fix the issue, progress is below.

Inspired by the commit:
https://github.com/pocl/pocl/issues/1088#issue-1340373438

If i build pocl by manual if follow:

```
cmake .. 
 -DCMAKE_INSTALL_PREFIX='/usr' 
 -DCMAKE_BUILD_TYPE='Debug' 
 -DPOCL_DEBUG_MESSAGES=ON
 -DLLC_HOST_CPU='sifive-u54'
```

Then there are four test failed:

```
98% tests passed, 4 tests failed out of 263

Label Time Summary:
EinsteinToolkit= 190.88 sec*proc (2 tests)
cuda   = 279.87 sec*proc (42 tests)
dlopen =   0.52 sec*proc (3 tests)
hsa=  35.00 sec*proc (4 tests)
hsa-native = 1127.40 sec*proc (82 tests)
internal   = 3317.43 sec*proc (256 tests)
kernel = 1719.95 sec*proc (76 tests)
level0 = 1446.25 sec*proc (124 tests)
matrix =  40.41 sec*proc (4 tests)
poclbin=  38.95 sec*proc (4 tests)
proxy  = 327.09 sec*proc (36 tests)
regression = 933.17 sec*proc (95 tests)
runtime= 179.38 sec*proc (31 tests)
tce=  69.97 sec*proc (9 tests)
vulkan = 176.65 sec*proc (26 tests)
workgroup  = 472.82 sec*proc (31 tests)

Total Test time (real) = 3791.39 sec

The following tests did not run:
 62 - kernel/test_shuffle_half_loopvec (Skipped)
 63 - kernel/test_shuffle_half_cbs (Skipped)
190 - runtime/clGetKernelArgInfo (Disabled)
199 - runtime/test_buffer_migration (Skipped)
200 - runtime/test_buffer_ping_pong (Skipped)

The following tests FAILED:
 76 - kernel/test_printf_vectors_loopvec (Failed)
 77 - kernel/test_printf_vectors_cbs (Failed)
 78 - kernel/test_printf_vectors_ulongn_loopvec (Failed)
 79 - kernel/test_printf_vectors_ulongn_cbs (Failed)
Errors while running CTest
```

Obviously these tests failed was due to vectors missing from riscv64
now. This is expected I think.

The result is aligned with pocl upstream support riscv64:

```
In this release we improved support for RISC-V CPUs. We tested PoCL on a 
Starfive VisionFive 2 using a Ubuntu 23.10 preinstalled image. With LLVM 17 and 
GCC 13.2, 98% tests pass (only 4 tests fail out of 253).

```
http://portablecl.org/docs/html/notes_5_0.html#risc-v-cpu-support-improved

If glance at the buildd log from riscv64:

```
-- udivmodti4 compiles without extra flags
-- Checking if LLVM is a DEBUG build
-- DEBUG build
-- Find out LLC target triple (for host riscv64-unknown-linux-gnu)
-- Find out LLC host CPU with /usr/bin/llc-15
-- Autodetected CPU sifive-u74 overridden by user to GENERIC
-- Checking clang -march vs. -mcpu flag
--   Using -None=
-- Running LLVM link test
-- LLVM link test OK
```
https://buildd.debian.org/status/fetch.php?pkg=pocl=riscv64=5.0-1=1704805199=0

So I suspect the `LLC_HOST_CPU='` was overriden by `GENERIC` then the
ABI was different. I will look at this more deeper.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Bo YU]

Source: shed
Followup-For: Bug #1057613

Hi,

Just fyi, MRs will fix the issue:
https://salsa.debian.org/pkg-security-team/shed/-/merge_requests

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1060388: sponsor for endless-sky

[Bo YU]

Hi!

On Wed, Jan 17, 2024 at 8:07 PM Bo YU  wrote:
>
> Hi!
>
> On Wed, Jan 17, 2024 at 12:21 PM P. J. McDermott  wrote:
> >
> > On 2024-01-17 at 10:22, Bo YU wrote:
> > > Hi,
> > >
> > > First sorry without contacting here before NMU.
> >
> > Welcome!
> >
> > > I am looking for a sponsor for my package "endless-sky":
> >
> > I'm not a DD, but I gave this a look and have a couple comments.
> >
> > >  * Vcs  : https://salsa.debian.org/games-team/endless-sky
> >

>
> I have salsa account also and I think I will wait this for one or two
> days to see how happened. If there is no DD have time to upload it and
> then I will send MR to here.

Now I open MRs to submit upload to it:
https://salsa.debian.org/games-team/endless-sky/-/merge_requests

So please review it there.
Thanks.

BR,
Bo

>
> BR,
> Bo

Bug#1060388: sponsor for endless-sky

[Bo YU]

Hi!

On Wed, Jan 17, 2024 at 12:21 PM P. J. McDermott  wrote:
>
> On 2024-01-17 at 10:22, Bo YU wrote:
> > Hi,
> >
> > First sorry without contacting here before NMU.
>
> Welcome!
>
> > I am looking for a sponsor for my package "endless-sky":
>
> I'm not a DD, but I gave this a look and have a couple comments.
>
> >  * Vcs  : https://salsa.debian.org/games-team/endless-sky
>
> Do you have an account on Salsa?  You could fork the repository and
> submit an MR so that the changes are ready to merge and upload.  If not,
> that's OK; I think the changes are small enough for one of us to just
> commit in one shot.

Thanks.

I have salsa account also and I think I will wait this for one or two
days to see how happened. If there is no DD have time to upload it and
then I will send MR to here.

BR,
Bo
>
> >  endless-sky (0.10.4-0.1) UNRELEASED; urgency=medium
> >  .
> >* Non-maintainer upload.
> >* New upstream version 0.10.4. (Closes: #1059987)
> >* rebase debian/patches
>
> I see out/troff.patch and out/spelling.patch were applied upstream and
> removed from debian/patches/series, but the patch files are still under
> debian/patches/.  They should be removed.
>
> >* Change Build-Depends on 'cmake' to'cmake (>= 3.21)'.
> >  (Closes: #1054624).
>
> (Coincidentally, seeing this bug on Friday reminded me to do a similar
> cmake B-D version bump in another package.)
>
> Other than the suggestions of Git and removing patch files, this looks
> OK to me for an NMU.  But of course it needs a DD's review (ideally
> Damyan).
>
> Since the changes are apparently not in Git, here's the diff I
> reviewed:
>
>  changelog |   10 ++
>  control   |2 +-
>  patches/atomics.patch |   29 ++---
>  patches/series|2 --
>  4 files changed, 29 insertions(+), 14 deletions(-)
> ---
> diff -Naur endless-sky-0.10.2/debian/changelog 
> endless-sky-0.10.4/debian/changelog
> --- endless-sky-0.10.2/debian/changelog 2023-10-10 10:57:15.0 -0400
> +++ endless-sky-0.10.4/debian/changelog 2024-01-07 20:42:17.0 -0500
> @@ -1,3 +1,13 @@
> +endless-sky (0.10.4-0.1) UNRELEASED; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * New upstream version 0.10.4. (Closes: #1059987)
> +  * rebase debian/patches
> +  * Change Build-Depends on 'cmake' to'cmake (>= 3.21)'.
> +(Closes: #1054624).
> +
> + -- Bo YU   Mon, 08 Jan 2024 09:42:17 +0800
> +
>  endless-sky (0.10.2-6) unstable; urgency=medium
>
>[ Adrian Bunk ]
> diff -Naur endless-sky-0.10.2/debian/control endless-sky-0.10.4/debian/control
> --- endless-sky-0.10.2/debian/control   2023-10-06 09:23:26.0 -0400
> +++ endless-sky-0.10.4/debian/control   2024-01-07 20:42:17.0 -0500
> @@ -8,7 +8,7 @@
>  Vcs-Git: https://salsa.debian.org/games-team/endless-sky.git
>  Homepage: https://endless-sky.github.io
>  Build-Depends:
> - cmake,
> + cmake (>= 3.21),
>   debhelper-compat (= 13),
>   g++ (>=4.6),
>   libgl-dev,
> diff -Naur endless-sky-0.10.2/debian/patches/atomics.patch 
> endless-sky-0.10.4/debian/patches/atomics.patch
> --- endless-sky-0.10.2/debian/patches/atomics.patch 2023-10-05 
> 06:08:09.0 -0400
> +++ endless-sky-0.10.4/debian/patches/atomics.patch 2024-01-07 
> 20:42:17.0 -0500
> @@ -1,17 +1,24 @@
> -Description: link with libatomic
> - On armel and mipsel, there are a bunch of missing __atomic_load_8 symbols
> - during linking
> - .
> - These are provided by libatomic and that is even in the build-dependencies,
> - but is missing on the linker command line.
> - .
> - The right spot to add it is a bit tricky, appending it to SConstrict near
> - 'pthread' doesn't seem to have any effect, but adding to CMakeLists.txt 
> works.
> -Author: Damyan Ivanov 
> +From: Damyan Ivanov 
> +Date: Mon, 8 Jan 2024 07:21:47 +0800
> +Subject: link with libatomic
>
> +On armel and mipsel, there are a bunch of missing __atomic_load_8 symbols
> +during linking
> +
> +These are provided by libatomic and that is even in the build-dependencies,
> +but is missing on the linker command line.
> +
> +The right spot to add it is a bit tricky, appending it to SConstrict near
> +'pthread' doesn't seem to have any effect, but adding to CMakeLists.txt 
> works.
> +---
> + CMakeLists.txt | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/CMakeLists.txt b/CMakeLists.txt
> +index fa0903a..d7807e9 100644
>  --- a/CMakeLists.txt
>  +++ b/CMakeLists.txt
> -@@ -123,7 +123,7 @@ target_link_libraries(ExternalLibraries
> +@@ -125,7 +125

Bug#1001643: Bug#1060913: Re: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys

[Bo YU]

Hi!

On Tue, Jan 16, 2024 at 10:39 PM Dominik George  wrote:
>
> Hi,
>
> > Here I am not a member of DebianEdu team and told if am not a member
> > of one team there is no reason to do team upload.
> > Ideally, I should contact the team to join in or tell team I am going
> > to fix ftbfs issue.
>
> Whether the maintainer is a team doesn't matter here (it just means I am
> not responsible alone for the lack of updates on the package, haha ;)).
Ah, I just realized you are the maintainer of the package(as
uploader), many thanks for your work.
>
> In general, you always contact the maintainer for every upload before
> doing an NMU, through the address from the package meta-data or by
> sending your changes to the BTS into the bug you are fixing.

Thanks for reminding me about this.
Before submitting an NMU I basically will give it at a glance from
debian tracker to look at the care/upload frequency of this package is
used to determine if the NMU. Because for some packages that lack
care, there are bugs filed in time, but they may not be resolved for a
long time. But this is only from my experience. I should obey Debian
NMU guidance here.


>
> > But I got no response from there(not DebianEdu
> > team) in the past.
>
> Can you point me to message IDs where you requested changes to be
> uploaded?
Sorry, here I mean I asked for some help on IRC.  The package is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060388

I will ping the maintainer of the package again and will fix some
issue like `UNRELEASE` here.
>
> Ideally, you should just send the changes to the BTS bug you are fixing,
> and tag it "patch".
OKay, no problem. Sometimes the debdiff for new upstream release is
very huge and BTS will drop this.:(

Many Thanks again, TIL.

BR,
Bo
>
> -nik

Bug#1001643: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys

[Bo YU]

Hi!

On Tue, Jan 16, 2024 at 9:30 PM Dominik George  wrote:
>
> Hi,
>
> is there a reason why you are not working with the packaging team, and doing 
> NMUs without contacting the team beforehand?

Here I am not a member of DebianEdu team and told if am not a member
of one team there is no reason to do team upload.
Ideally, I should contact the team to join in or tell team I am going
to fix ftbfs issue. But I got no response from there(not DebianEdu
team) in the past.
I would like to follow your advice how to deal with the package or let
the team know the new upstream release will fix the RC problem:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001643

BR,
Bo
>
> -nik
>

Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "sdaps":

 * Package name : sdaps
   Version  : 1.9.11-0.1
   Upstream contact : Benjamin Berg 
 * URL  : https://sdaps.org
 * License  : GPL-3.0+, LPPL-1.3c
 * Vcs  : https://salsa.debian.org/debian-edu-pkg-team/sdaps
   Section  : science

The source builds the following binary packages:

  sdaps - scripts for data acquisition with paper-based surveys

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/sdaps/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sdaps/sdaps_1.9.11-0.1.dsc

Changes since the last upload:

 sdaps (1.9.11-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 1.9.11. (Closes: #1001643)
   * Use libtiff-dev instead of libtiff5-dev.
   * Set std-ver to 4.6.2.
   * Add python3-pkgconfig on B-D.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1060844: paryfor: please add support for riscv64 build

[Bo YU]

Source: paryfor
Version: 0.1-5
Severity: wishlist
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

The package fail to build on riscv64 in the past:
https://buildd.debian.org/status/logs.php?pkg=paryfor=riscv64

But now the package can be built on riscv64 from upstream support:
https://github.com/ekg/paryfor/commit/2383b62f53175950a5fcd75bdf6d68774311b496

I can built it on my local riscv64 hardware with the commit, so could
you include it on next upload?

Please let me know any issues.

-- 
Regards,
--
  Bo YU

diff -Nru paryfor-0.1/debian/changelog paryfor-0.1/debian/changelog
--- paryfor-0.1/debian/changelog2022-11-28 04:38:43.0 +0800
+++ paryfor-0.1/debian/changelog2024-01-15 15:36:05.0 +0800
@@ -1,3 +1,10 @@
+paryfor (0.1-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Support riscv64 build. (Closes: #-1)
+
+ -- Bo YU   Mon, 15 Jan 2024 15:36:05 +0800
+
 paryfor (0.1-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru paryfor-0.1/debian/patches/series paryfor-0.1/debian/patches/series
--- paryfor-0.1/debian/patches/series   2022-11-28 04:38:43.0 +0800
+++ paryfor-0.1/debian/patches/series   2024-01-15 15:32:58.0 +0800
@@ -1 +1,2 @@
 Fix-compilation-flags.patch
+support_riscv64.patch
diff -Nru paryfor-0.1/debian/patches/support_riscv64.patch 
paryfor-0.1/debian/patches/support_riscv64.patch
--- paryfor-0.1/debian/patches/support_riscv64.patch1970-01-01 
07:30:00.0 +0730
+++ paryfor-0.1/debian/patches/support_riscv64.patch2024-01-15 
15:36:05.0 +0800
@@ -0,0 +1,23 @@
+Description: support riscv64 build 
+Applied-Upstream: 
https://github.com/ekg/paryfor/commit/2383b62f53175950a5fcd75bdf6d68774311b496 
+Last-Update: 2024-01-15
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/paryfor.hpp
 b/paryfor.hpp
+@@ -51,6 +51,15 @@
+ }
+ } // namespace atomic_queue
+ } // namespace paryfor
++#elif defined(__riscv) && (__riscv_xlen == 64)
++namespace paryfor {
++namespace atomic_queue {
++constexpr int CACHE_LINE_SIZE = 64;
++static inline void spin_loop_pause() noexcept {
++asm volatile ("nop" ::: "memory");
++}
++} // namespace atomic_queue
++} // namespace paryfor
+ #else
+ #error "Unknown CPU architecture."
+ #endif


signature.asc
Description: PGP signature

Bug#1060650: RFS: zfec/1.5.7.4-0.1 [NMU] [RC] -- fast erasure codec, with Python 3 bindings

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "zfec":

 * Package name : zfec
   Version  : 1.5.7.4-0.1
   Upstream contact : https://github.com/tahoe-lafs/zfec/issues
 * URL  : http://tahoe-lafs.org/trac/zfec
 * License  : GPL-2 or TGPPL1+, GPL-2 with OpenSSL exception or TGPPL-1
 * Vcs  : https://salsa.debian.org/vasudev/zfec
   Section  : python

The source builds the following binary packages:

  python3-zfec - fast erasure codec, with Python 3 bindings

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/zfec/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/z/zfec/zfec_1.5.7.4-0.1.dsc

Changes since the last upload:

 zfec (1.5.7.4-0.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 1.5.7.4. (Closes: #1055545)
   * Drop debian/patch
   * Demove upstream-vcs-tag when use gbp
   * Ddd python3-pyutil on B-D.
   * Add python3-hypothesis and python3-twisted for test.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1060399: libbson-xs-perl: FTBFS on riscv64: double.t failures

[Bo YU]

hi,
On Wed, Jan 10, 2024 at 08:23:02PM +0200, Niko Tyni wrote:


Latest build log is at

 
https://buildd.debian.org/status/fetch.php?pkg=libbson-xs-perl=riscv64=0.8.4-2=1690811919=0


  #   Failed test 'native_to_bson(bson_to_native(cB)) = cB'
  #   at t/lib/CorpusTest.pm line 144.
  # Got:
  # 116400f87f00
  # Expected:
  # 1164001200f87f00
  # Looks like you failed 1 test of 5.

  #   Failed test 'case: NaN with payload'
  #   at t/corpus/double.t line 13.
  # Looks like you failed 1 test of 14.

  [...]

  Test Summary Report
  ---
  t/corpus/double.t  (Wstat: 256 (exited 1) Tests: 14 Failed: 1)
Failed test:  11
Non-zero exit status: 1
  t/mapping/double.t (Wstat: 768 (exited 3) Tests: 39 Failed: 3)
Failed tests:  23, 29, 35
Non-zero exit status: 3
  Files=59, Tests=1342, 97 wallclock secs ( 2.74 usr  0.35 sys + 84.38 cusr 
11.55 csys = 99.02 CPU)
  Result: FAIL


Thanks for report.

For NaN with payload, I think this is a known issue on riscv64, but now
I have a litttle understand about it and I have searched many issue
about it. Maybe I can get solution from there, like:
https://github.com/evanw/esbuild/issues/3569

Another test failed I will look into the code and feedback here.

BR,
Bo


--
Niko Tyni   nt...@debian.org



--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1060388: RFS: endless-sky/0.10.4-0.1 [NMU] [RC] -- space exploration, trading and combat game

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "endless-sky":

 * Package name : endless-sky
   Version  : 0.10.4-0.1
   Upstream contact : Michael Zahniser 
 * URL  : https://endless-sky.github.io
 * License  : GPL-2, public-domain, CC-BY-SA-4.0, CC-BY-4.0, GPL-3+, 
CC-BY-SA-3.0, CC0-1.0, CC-BY-3.0, CC-BY-2.0, boost-1.0, MIT
 * Vcs  : https://salsa.debian.org/games-team/endless-sky
   Section  : games

The source builds the following binary packages:

  endless-sky - space exploration, trading and combat game
  endless-sky-data - space exploration, trading and combat game - data files

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/endless-sky/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/e/endless-sky/endless-sky_0.10.4-0.1.dsc

Changes since the last upload:

 endless-sky (0.10.4-0.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 0.10.4. (Closes: #1059987)
   * rebase debian/patches
   * Change Build-Depends on 'cmake' to'cmake (>= 3.21)'.
 (Closes: #1054624).


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1024636: perl: add cross build support files for loongarch64

[Bo YU]

Hi,

On Wed, Jan 10, 2024 at 6:22 AM Niko Tyni  wrote:
>
> On Wed, Dec 13, 2023 at 03:47:05PM +0800, Bo YU wrote:
> > Package: perl
> > Version: 5.36.0-10
> > Followup-For: Bug #1024636
> > Tags: patch
> > X-Debbugs-Cc: rabenda...@gmail.com
> >
> > Dear Maintainer,
> >
> > I have followed the instructions from debian/cross/README to generate
> > these files which support cross build from native build on loong64 host.
> > but it is unclear to me how to verify if this binary works like you
> > comment on -1[#10]. Could you give me a little hint?
> >
> > But I think it should be no problem.
> >
> > [#10]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024636#10
>
> Hi, thanks for your efforts. I only saw your message now as you mailed
> 1024636-qu...@bugs.debian.org which is not forwarded to the maintainer.
> Please use just 1024...@bugs.debian.org in the future.
okay.:)
>
> If the files are from a native build that passed the Perl test suite
> during the build, that's totally acceptable. My concern was about the
> previous hand crafted cross config files that looked like nobody had
> ever tested them at all. For such hand crafting, I suppose a minimal
> test would be to install the cross built binary perl packages on an
> actual loong64 host and run 'perl -V' or something like that.
>
> However, I'm afraid we have missed the train here: your patch is for
> Perl 5.36 but we're now moving to 5.38 (with perl_5.38.2-2 building in
> Debian unstable right now.) It makes little sense to include the 5.36
> config files now, so unfortunately you'll have to redo the process with
> the 5.38 package.
No worried. I will test these cross configs based on 5.38 on loong64
machines again.
Yeah, when I sent the patch I realized maybe we will transit to 5.38
because it was in experimental for a long time.

>
> Apologies for the awkward process. It's all workarounds for perl upstream
> not supporting cross configuration properly due to lots of historical
> baggage.
No problem.Many thanks for your work also.

BR,
Bo
> --
> Niko Tyni   nt...@debian.org

Bug#1060274: RFS: python-acora/2.4-1.1 [NMU] [RC] -- fast multi-keyword text search engine (Python 2)

[Bo YU]

tags -1 - moreinfo


Hi,

On Tue, Jan 9, 2024 at 5:15 AM Bastian Germann  wrote:
>
> Control: tags -1 moreinfo

>
> Please check the archive before posting NMUs based on old versions.
> Also, a new upstream version needs the NMU revision -0.1, not -1.1.

Thanks for pushing updated upload to debian salsa repo. This is become
easy to update upstream release. so

Dear mentors,

I am looking for a sponsor for my package "python-acora":

 * Package name : python-acora
   Version  : 2.4-0.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://pypi.python.org/pypi/acora
 * License  : BSD-3-Clause
 * Vcs  : https://salsa.debian.org/debian/python-acora
   Section  : python

The source builds the following binary packages:

  python3-acora - fast multi-keyword text search engine (Python 3)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/python-acora/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-acora/python-acora_2.4-0.1.dsc

Changes since the last upload:

 python-acora (2.4-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   [ Bastian Germann ]
   * Remove .git suffix from Vcs-Browser
 .
   [ Bo YU ]
   * New upstream version 2.4. (Closes: #1056849, #1055707)

Please let me know any issues.

BR,
Bo

>

Bug#1060274: RFS: python-acora/2.4-1.1 [NMU] [RC] -- fast multi-keyword text search engine (Python 2)

[Bo YU]

Hi,

On Tue, Jan 9, 2024 at 5:15 AM Bastian Germann  wrote:
>
> Control: tags -1 moreinfo
>
> On Mon, 8 Jan 2024 23:13:52 +0800 Bo YU  wrote:
> >  python-acora (2.4-1.1) unstable; urgency=medium
> >  .
> >* Non-maintainer upload.
> >* New upstream version 2.4. (Closes: #1056849, #1055707).
> >* Remove python2 on B-D and pybuild.
> >* Add extend-diff-ignore to fix dpkg-source -b check issue.
>
> Please check the archive before posting NMUs based on old versions.
I guess the problem was raised by not pushing the update to the slasa
repo with before several times NMUs. I just the do NMUs based on salsa
repo.

> Also, a new upstream version needs the NMU revision -0.1, not -1.1.
Okak, thanks for reminding me.

BR,
bo
>

Bug#1060274: RFS: python-acora/2.4-1.1 [NMU] [RC] -- fast multi-keyword text search engine (Python 2)

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "python-acora":

 * Package name : python-acora
   Version  : 2.4-1.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://pypi.python.org/pypi/acora
 * License  : BSD-3-Clause
 * Vcs  : https://salsa.debian.org/debian/python-acora.git
   Section  : python

The source builds the following binary packages:

  python-acora - fast multi-keyword text search engine (Python 2)
  python3-acora - fast multi-keyword text search engine (Python 3)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/python-acora/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-acora/python-acora_2.4-1.1.dsc

Changes since the last upload:

 python-acora (2.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 2.4. (Closes: #1056849, #1055707).
   * Remove python2 on B-D and pybuild.
   * Add extend-diff-ignore to fix dpkg-source -b check issue.


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1060250: RFS: snapd-glib/1.63-5.1 [NMU] -- GLib snapd library (installed tests)

[Bo YU]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "snapd-glib":

 * Package name : snapd-glib
   Version  : 1.63-5.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://github.com/snapcore/snapd-glib
 * License  : LGPL-2 or LGPL-3
 * Vcs  : https://salsa.debian.org/debian-ayatana-team/snapd-glib
   Section  : libs

The source builds the following binary packages:

  libsnapd-glib-2-1 - GLib snapd library
  gir1.2-snapd-2 - Typelib file for libsnapd-glib1
  libsnapd-glib-dev - GLib snapd library (development files)
  libsnapd-qt-2-1 - Qt snapd library
  qml-module-snapd - Snapd QML module
  libsnapd-qt-dev - Qt snapd library (development files)
  snapd-glib-tests - GLib snapd library (installed tests)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/snapd-glib/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/s/snapd-glib/snapd-glib_1.63-5.1.dsc

Changes since the last upload:

 snapd-glib (1.63-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update libsnapd-qt-2-1.symbols to support riscv64. (Closes: #1052429)

-
The package is a key package which blocks some packages rebuild by DSAed
buildd even it never be built since riscv64 official rebootstrap. So I
do a NMU here and I am apperciated it if you sponsor this.

Please let me know any issue.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059295: RFP: gfxstream -- wrapper for graphics streams across VirtIO

[Bo YU]

Control: retitle -1 ITP: gfxstream -- wrapper for graphics streams across VirtIO

Hi，
On Fri, Dec 22, 2023 at 8:45 PM Alex Bennée  wrote:
>
> Package: wnpp
> Severity: wishlist
>
> * Package name: gfxstream
>   Version : v0.1.2
>   Upstream Author : Google
> * URL or Web page : 
> https://android.googlesource.com/platform/hardware/google/gfxstream
> * License : Apache2
>   Description : wrapper for graphics streams across VirtIO
>
> This package (and the supporting aemu and rutabagga_ffi bindings) is
> needed if we want to compile QEMU with rutabaga support - hence support
> Vulkan and Wayland over virtio-gpu.
>
> We have some notes for building in tree here in the meantime:
>
> https://linaro.atlassian.net/wiki/spaces/ORKO/pages/28985622530/Building+QEMU+with+virtio-gpu+and+rutabaga+gfx

I would like to package it. But I lack experience in packaging similar
packages so may I need some guidance from here if need.

Thanks,
Bo
>
> --
> Alex Bennée
> Virtualisation Tech Lead @ Linaro
>

Bug#1060203: RFS: dde-store/1.2.3+dfsg-2.1 [NMU] [RC] -- DDE Store for Deepin Desktop Environment

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "dde-store":

 * Package name : dde-store
   Version  : 1.2.3+dfsg-2.1
   Upstream contact : dekzi 
 * URL  : https://github.com/dekzi/dde-store
 * License  : GPL-3, GPL-3+
 * Vcs  : https://salsa.debian.org/openarun/dde-store
   Section  : utils

The source builds the following binary packages:

  dde-store - DDE Store for Deepin Desktop Environment

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/dde-store/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dde-store/dde-store_1.2.3+dfsg-2.1.dsc

Changes since the last upload:

 dde-store (1.2.3+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-pick upstream commit fix ftbfs. (Closes: #1059237)

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059511: pocl: FTBFS on many architectures: The testsuite has failed

[Bo YU]

Hi!

On Thu, Dec 28, 2023 at 6:35 AM Andreas Beckmann  wrote:
>
> Control: retitle -1 pocl: FTBFS on riscv64: testsuite fails: can't link 
> double-float modules with soft-float modules
> Control: severity -1 wishlist
>
> On 27/12/2023 09.54, Bo YU wrote:
> > The same issue happend on 5.0 also:
> > https://buildd.debian.org/status/package.php?p=pocl=experimental
> >
> > But from upstream 5.0 release note, there is support well expect 4 tests
> > failed. So what is your advice here about the issue?
>
> In the buildlog I see
>
>13% tests passed, 228 tests failed out of 263
>
> Errors seem to happen at OpenCL kernel build time:
>
>LLVM ERROR: unable to write nop sequence of 2 bytes
>
> and mostly
>
>/usr/bin/ld: /lib/riscv64-linux-gnu/libm.so: can't link double-float
>modules with soft-float modules
>
>/usr/bin/ld: failed to merge target specific data of file
>/lib/riscv64-linux-gnu/libm.so
>
...
>error: linker command failed with exit code 1 (use -v to see invocation)
>
>Final linking of kernel test_shuffle_2_2 failed.
>
>
> I'd suggest postponing further analysis until sid has pocl 5.0 and
> switched from llvm-15 to llvm-16. These two changes will *not* happen in
> a single upload.

Thanks. I did not notice these special test logs from buildd.  I will
look at this more here.

BR,
Bo
>
>
> Andreas

Bug#1059558: RFS: 389-ds-base/2.3.4+dfsg1-1.1 [NMU] [RC] -- 389 Directory Server suite - server

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "389-ds-base":

 * Package name : 389-ds-base
   Version  : 2.3.4+dfsg1-1.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://directory.fedoraproject.org
 * License  : GPL-2+ or LGPL-2.1 or MPL-1.1, GPL-3+, Apache-2.0 or MIT, 
GPL-3+ and Other, MPL-2.0
 * Vcs  : https://salsa.debian.org/freeipa-team/389-ds-base
   Section  : net

The source builds the following binary packages:

  389-ds - 389 Directory Server suite - metapackage
  389-ds-base-libs - 389 Directory Server suite - libraries
  389-ds-base-dev - 389 Directory Server suite - development files
  389-ds-base - 389 Directory Server suite - server
  python3-lib389 - Python3 module for accessing and configuring the 389 
Directory Server
  cockpit-389-ds - Cockpit user interface for 389 Directory Server

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/389-ds-base/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/3/389-ds-base/389-ds-base_2.3.4+dfsg1-1.1.dsc

Changes since the last upload:

 389-ds-base (2.3.4+dfsg1-1.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Add librust-clap-3-dev on B-D. (Closes: #1052626)

--

I can not replied the #1052626 with the debdiff file, so I do a NMU
directly.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052626

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1059138: litecoin: FTBFS: error: ‘std::map, boost::filesystem::path>::mapped_type’ {aka ‘class boost::filesystem::path’} has no member named ‘BOOST_FILESYSTEM_C_ST

[Bo YU]

Source: litecoin
Version: 0.21.2.2-1.1+b1
Followup-For: Bug #1059138

Dear Maintainer,

The upstream has fixed the issue but there are 2 test cases failed and I
have reported this to upstream:
https://github.com/litecoin-project/litecoin/issues/932

Please review the debdiff and maybe I will do a NMU one week later.


-- 
Regards,
--
  Bo YU

diff -Nru litecoin-0.21.2.2/debian/changelog litecoin-0.21.2.2/debian/changelog
--- litecoin-0.21.2.2/debian/changelog  2023-11-01 22:21:35.0 +0800
+++ litecoin-0.21.2.2/debian/changelog  2023-12-28 15:20:54.0 +0800
@@ -1,3 +1,11 @@
+litecoin (0.21.2.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix-ftbfs-on-boost1.83.patch to fix ftbfs. (Closes: #1059138)
+  * Add t-skip--wallet-init_tests.patch to skip tests failed.
+
+ -- Bo YU   Thu, 28 Dec 2023 15:20:54 +0800
+
 litecoin (0.21.2.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru litecoin-0.21.2.2/debian/patches/fix-ftbfs-on-boost1.83.patch 
litecoin-0.21.2.2/debian/patches/fix-ftbfs-on-boost1.83.patch
--- litecoin-0.21.2.2/debian/patches/fix-ftbfs-on-boost1.83.patch   
1970-01-01 07:30:00.0 +0730
+++ litecoin-0.21.2.2/debian/patches/fix-ftbfs-on-boost1.83.patch   
2023-12-28 10:46:35.0 +0800
@@ -0,0 +1,54 @@
+From acb7aad27ec8a184808aa7905887e3b2c5d54e9c Mon Sep 17 00:00:00 2001
+From: Rafael Sadowski 
+Date: Mon, 16 Aug 2021 06:34:02 +0200
+Subject: [PATCH] Fix build with Boost 1.77.0
+
+BOOST_FILESYSTEM_C_STR changed to accept the path as an argument
+---
+ src/fs.cpp| 4 
+ src/wallet/test/db_tests.cpp  | 4 
+ src/wallet/test/init_test_fixture.cpp | 4 
+ 3 files changed, 12 insertions(+)
+
+--- a/src/fs.cpp
 b/src/fs.cpp
+@@ -236,7 +236,11 @@
+ }
+ #else // __GLIBCXX__
+ 
++#if BOOST_VERSION >= 107700
++static_assert(sizeof(*BOOST_FILESYSTEM_C_STR(fs::path())) == sizeof(wchar_t),
++#else
+ static_assert(sizeof(*fs::path().BOOST_FILESYSTEM_C_STR) == sizeof(wchar_t),
++#endif // BOOST_VERSION >= 107700
+ "Warning: This build is using boost::filesystem ofstream and ifstream "
+ "implementations which will fail to open paths containing multibyte "
+ "characters. You should delete this static_assert to ignore this warning, 
"
+--- a/src/wallet/test/db_tests.cpp
 b/src/wallet/test/db_tests.cpp
+@@ -18,7 +18,11 @@
+ std::string test_name = "test_name.dat";
+ const fs::path datadir = GetDataDir();
+ fs::path file_path = datadir / test_name;
++#if BOOST_VERSION >= 107700
++std::ofstream f(BOOST_FILESYSTEM_C_STR(file_path));
++#else
+ std::ofstream f(file_path.BOOST_FILESYSTEM_C_STR);
++#endif // BOOST_VERSION >= 107700
+ f.close();
+ 
+ std::string filename;
+--- a/src/wallet/test/init_test_fixture.cpp
 b/src/wallet/test/init_test_fixture.cpp
+@@ -31,7 +31,11 @@
+ fs::create_directories(m_walletdir_path_cases["default"]);
+ fs::create_directories(m_walletdir_path_cases["custom"]);
+ fs::create_directories(m_walletdir_path_cases["relative"]);
++#if BOOST_VERSION >= 107700
++std::ofstream f(BOOST_FILESYSTEM_C_STR(m_walletdir_path_cases["file"]));
++#else
+ std::ofstream f(m_walletdir_path_cases["file"].BOOST_FILESYSTEM_C_STR);
++#endif // BOOST_VERSION >= 107700
+ f.close();
+ }
+ 
diff -Nru litecoin-0.21.2.2/debian/patches/series 
litecoin-0.21.2.2/debian/patches/series
--- litecoin-0.21.2.2/debian/patches/series 2023-11-01 22:19:24.0 
+0800
+++ litecoin-0.21.2.2/debian/patches/series 2023-12-28 11:33:11.0 
+0800
@@ -7,3 +7,5 @@
 t-skip--libmw.patch
 t-skip--secp256k1.patch
 gcc-13.patch
+fix-ftbfs-on-boost1.83.patch
+t-skip--wallet-init_tests.patch
diff -Nru litecoin-0.21.2.2/debian/patches/t-skip--wallet-init_tests.patch 
litecoin-0.21.2.2/debian/patches/t-skip--wallet-init_tests.patch
--- litecoin-0.21.2.2/debian/patches/t-skip--wallet-init_tests.patch
1970-01-01 07:30:00.0 +0730
+++ litecoin-0.21.2.2/debian/patches/t-skip--wallet-init_tests.patch
2023-12-28 15:20:20.0 +0800
@@ -0,0 +1,16 @@
+Description: skip tests failed 
+Author: Bo YU  
+Forwarded: https://github.com/litecoin-project/litecoin/issues/932 
+Last-Update: 2023-12-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/Makefile.test.include
 b/src/Makefile.test.include
+@@ -299,7 +299,6 @@
+   wallet/test/wallet_tests.cpp \
+   wallet/test/wallet_crypto_tests.cpp \
+   wallet/test/coinselector_tests.cpp \
+-  wallet/test/init_tests.cpp \
+   wallet/test/ismine_tests.cpp \
+   wallet/test/scriptpubkeyman_tests.cpp
+ 


signature.asc
Description: PGP signature

Bug#1059511: pocl: FTBFS on many architectures: The testsuite has failed

[Bo YU]

Source: pocl
Version: 4.0-3 
Severity: important

Dear Maintainer,

I am looking at the build issue from riscv64 port view but it can not be
build many arches:
https://buildd.debian.org/status/package.php?p=pocl

It seems even updated the symbols file still failed due to exist
debian/stamp-failed-testsuite file.

```
run_dh_makeshlibs:
dh_makeshlibs
delayed_check_dh_auto_test_result: run_dh_makeshlibs
@set -ex; if test -f debian/stamp-failed-testsuite ; then \
echo "* The testsuite has failed! *" ; \
exit 1 ; \
fi  
   @test -f 
obj-*/Testing/Temporary/LastTest.log && echo 'The testsuite has passed all 
tests.' || echo '*** The testsuite was *NOT* ru
n! ***'

```

The same issue happend on 5.0 also:
https://buildd.debian.org/status/package.php?p=pocl=experimental

But from upstream 5.0 release note, there is support well expect 4 tests
failed. So what is your advice here about the issue?

http://portablecl.org/docs/html/notes_5_0.html#risc-v-cpu-support-improved


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1056017: rlvm: FTBFS: boost1.83 transition

[Bo YU]

Hi！

On Tue, Dec 26, 2023 at 1:24 AM Ying-Chun Liu (PaulLiu)
 wrote:
>
> Hi Bo YU,
>
> Please NMU it and I'll sponsor it.

Thanks. please to see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059441

```

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/rlvm/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/r/rlvm/rlvm_0.14-5.2.dsc

Changes since the last upload:

 rlvm (0.14-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix ftbfs on boost1.83. (Closes: #1056017)
   * Use libboost-timer-dev instead of libboost-date-time-dev.

```

BR,
Bo
>
> Yours,
> Paul
>
>
> On 2023/12/25 19:52, Bo YU wrote:
> > Source: rlvm
> > Version: 0.14-5.1
> > Followup-For: Bug #1056017
> > Tags: patch
> >
> > Dear Maintainer,
> >
> > I cost some time to fix the issue and patch attached. Please review it.
> >
> > In order to fix the RC bug ASAP, I may do a NMU to mentor and find a
> > sponsor to upload it. Please feel free to break the process if there is
> > any issue.
> >
> >

Bug#1059441: RFS: rlvm/0.14-5.2 [NMU] [RC] -- RealLive virtual machine clone

[Bo YU]

Package: sponsorship-requests
Severity: important

I am looking for a sponsor for my package "rlvm":

 * Package name : rlvm
   Version  : 0.14-5.2
   Upstream contact : Elliot Glaysher 
 * URL  : http://rlvm.net
 * License  : BSD-3-clause-variant-2, BSD-3-clause-variant-6, 
BSD-3-clause-variant1, Expat, LGPL-2.1+, jagarl, BSD-3-clause-variant-5, 
BSD-2-clause, BSD-3-clause-variant-10, BSD-3-clause-variant-8, GPL-3+, GPL-2+, 
LGPL-2+, Expat-variant-1, BSD-3-clause-variant-4, BSD-3-clause-variant3, 
BSD-3-clause-variant-9
 * Vcs  : [fill in URL of packaging vcs]
   Section  : games

The source builds the following binary packages:

  rlvm - RealLive virtual machine clone

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/rlvm/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/r/rlvm/rlvm_0.14-5.2.dsc

Changes since the last upload:

 rlvm (0.14-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix ftbfs on boost1.83. (Closes: #1056017)
   * Use libboost-timer-dev instead of libboost-date-time-dev.


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature