Source: picotool
Version: 1.1.2-1
Severity: serious
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear picotool Maintainer,
The picotool package build failed on many archs caused by detecting debian/
picotool.1.in diff.The crucial buildd log below:
```
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /<<PKGBUILDDIR>>/debian/picotool/usr/bin/picotool
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-riscv64-linux-gnu'
dh_install -a
dh_installdocs -a
dh_installchangelogs -a
debian/rules execute_before_dh_installman
make[1]: Entering directory '/<<PKGBUILDDIR>>'
# native build
# verify that the contents of debian/picotool.1.in is up-to-date
help2man -n "interact with RP2040 devices or binaries" --no-info
--help-option=help --output=picotool.1
./obj-riscv64-linux-gnu/picotool
{ \
awk 'NR == 1 && /DO NOT MODIFY THIS FILE! It was generated by
help2man/ { print }' picotool.1; \
sed 's/@@DATE@@/April 2024/' debian/picotool.1.in; \
} | diff -u - picotool.1
--- - 2024-06-04 18:21:26.747621999 +0000
+++ picotool.1 2024-06-04 18:21:26.722708927 +0000
@@ -10,11 +10,17 @@
.IP
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-\-bus <bus>]
[\-\-address <addr>] [\-f] [\-F]
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] <filename> [\-t <type>]
-picotool load [\-n] [\-N] [\-u] [\-v] [\-x] <filename> [\-t <type>]
[\-o <offset>] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
+picotool load [\-n] [\-N] [\-u] [\-v] [\-x] <filename> [\-t <type>]
[\-o <offset>] [\-\-bus <bus>]
+.IP
+[\-\-address <addr>] [\-f] [\-F]
+.IP
picotool save [\-p] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>]
picotool save \fB\-a\fR [\-\-bus <bus>] [\-\-address <addr>] [\-f]
[\-F] <filename> [\-t <type>]
picotool save \fB\-r\fR <from> <to> [\-\-bus <bus>] [\-\-address
<addr>] [\-f] [\-F] <filename> [\-t <type>]
-picotool verify [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>] [\-r <from> <to>] [\-o <offset>]
+picotool verify [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>] [\-r <from>
+.IP
+<to>] [\-o <offset>]
+.IP
picotool reboot [\-a] [\-u] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
picotool version [\-s]
picotool help [<cmd>]
@@ -22,7 +28,8 @@
.TP
info
Display information from the target device(s) or file.
-Without any arguments, this will display basic information for all
connected RP2040 devices in BOOTSEL mode
+Without any arguments, this will display basic information for all
connected RP2040
+devices in BOOTSEL mode
.TP
load
Load the program / memory range stored in a file onto the device.
@@ -49,11 +56,17 @@
.IP
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-\-bus <bus>]
[\-\-address <addr>] [\-f] [\-F]
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] <filename> [\-t <type>]
-picotool load [\-n] [\-N] [\-u] [\-v] [\-x] <filename> [\-t <type>]
[\-o <offset>] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
+picotool load [\-n] [\-N] [\-u] [\-v] [\-x] <filename> [\-t <type>]
[\-o <offset>] [\-\-bus <bus>]
+.IP
+[\-\-address <addr>] [\-f] [\-F]
+.IP
picotool save [\-p] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>]
picotool save \fB\-a\fR [\-\-bus <bus>] [\-\-address <addr>] [\-f]
[\-F] <filename> [\-t <type>]
picotool save \fB\-r\fR <from> <to> [\-\-bus <bus>] [\-\-address
<addr>] [\-f] [\-F] <filename> [\-t <type>]
-picotool verify [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>] [\-r <from> <to>] [\-o <offset>]
+picotool verify [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
<filename> [\-t <type>] [\-r <from>
+.IP
+<to>] [\-o <offset>]
+.IP
picotool reboot [\-a] [\-u] [\-\-bus <bus>] [\-\-address <addr>] [\-f] [\-F]
picotool version [\-s]
picotool help [<cmd>]
@@ -61,7 +74,8 @@
.TP
info
Display information from the target device(s) or file.
-Without any arguments, this will display basic information for all
connected RP2040 devices in BOOTSEL mode
+Without any arguments, this will display basic information for all
connected RP2040
+devices in BOOTSEL mode
.TP
load
Load the program / memory range stored in a file onto the device.
make[1]: *** [debian/rules:23: execute_before_dh_installman] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=picotool&arch=riscv64&ver=1.1.2-1&stamp=1717525294&raw=0
I believe this issue has been solved in the latest version on
https://salsa.debian.org/debian/picotool, and I have tested it; it works
well. However, the debian/changelog has not been modified. Maybe you should
update the changelog to trigger a rebuild.
Gui-Yue
Best Regards
