<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>I made some builds and this happens with Debian 11. I do git
clone Mariadb from Salsa and run 'debian/autobake-deb.sh' and it
strangely doesn't apply patch for RocksDB 'debian/patches/rocksdb-kfreebsd.patch'.
Here is log what happens:<br>
</p>
<p><span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;"></span>Incrementing
changelog and starting build scripts<br>
libdistro-info-perl is not installed, Debian release names are
not known.<br>
libdistro-info-perl is not installed, Ubuntu release names are
not known.<br>
Creating package version 1:10.6.4+maria~bullseye ... <br>
dpkg-buildpackage: info: source package mariadb-10.6<br>
dpkg-buildpackage: info: source version 1:10.6.4+maria~bullseye<br>
dpkg-buildpackage: info: source distribution bullseye<br>
dpkg-buildpackage: info: source changed by Debian MySQL
Maintainers <a class="moz-txt-link-rfc2396E" href="mailto:pkg-mysql-maint@lists.alioth.debian.org"><pkg-mysql-maint@lists.alioth.debian.org></a><br>
dpkg-source -I --before-build .<br>
dpkg-buildpackage: info: host architecture amd64<br>
dpkg-source: info: using patch list from debian/patches/series<br>
dpkg-source: info: applying mips-groonga-atomic.patch<br>
dpkg-source: info: applying mips-connect-unaligned.patch<br>
dpkg-source: info: applying c11_atomics.patch<br>
dpkg-source: info: applying
0025-Change-the-default-optimization-from-O3-to-O2-in-mys.patch<br>
dpkg-source: info: applying
mips-compilation-failure-__bss_start-symbol-miss.patch<br>
dpkg-source: info: applying rocksdb-kfreebsd.patch<br>
patching file storage/rocksdb/build_rocksdb.cmake<br>
can't find file to patch at input line 20<br>
Perhaps you used the wrong -p or --strip option?<br>
The text leading up to this was:<br>
--------------------------<br>
|--- a/storage/rocksdb/rocksdb/CMakeLists.txt<br>
|+++ b/storage/rocksdb/rocksdb/CMakeLists.txt<br>
--------------------------<br>
No file to patch. Skipping patch.<br>
2 out of 2 hunks ignored<br>
can't find file to patch at input line 40<br>
erhaps you used the wrong -p or --strip option?<br>
The text leading up to this was:<br>
--------------------------<br>
|--- a/storage/rocksdb/rocksdb/build_tools/build_detect_platform<br>
|+++ b/storage/rocksdb/rocksdb/build_tools/build_detect_platform<br>
--------------------------<br>
No file to patch. Skipping patch.<br>
1 out of 1 hunk ignored<br>
can't find file to patch at input line 60<br>
Perhaps you used the wrong -p or --strip option?<br>
The text leading up to this was:<br>
--------------------------<br>
|--- a/storage/rocksdb/rocksdb/env/env_posix.cc<br>
|+++ b/storage/rocksdb/rocksdb/env/env_posix.cc<br>
--------------------------<br>
No file to patch. Skipping patch.<br>
3 out of 3 hunks ignored<br>
can't find file to patch at input line 92<br>
Perhaps you used the wrong -p or --strip option?<br>
The text leading up to this was:<br>
--------------------------<br>
|--- a/storage/rocksdb/rocksdb/port/stack_trace.cc<br>
|+++ b/storage/rocksdb/rocksdb/port/stack_trace.cc<br>
--------------------------<br>
No file to patch. Skipping patch.<br>
1 out of 1 hunk ignored<br>
patching file storage/rocksdb/rdb_io_watchdog.h<br>
patching file storage/rocksdb/rdb_io_watchdog.cc<br>
</span><br>
<span style="font-family:monospace"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">dpkg-source:
info: the patch has fuzz which is not allowed, or is
malformed
</span><br>
dpkg-source: info: if patch 'rocksdb-kfreebsd.patch' is
correctly applied by quilt, use 'quilt refresh' to update it
<br>
dpkg-source: info: restoring quilt backup files for
rocksdb-kfreebsd.patch
<br>
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never
-E -b -B .pc/rocksdb-kfreebsd.patch/ --reject-file=- <
mariadb-s<br>
erver/debian/patches/rocksdb-kfreebsd.patch subprocess
returned exit status 1
<br>
dpkg-buildpackage: error: dpkg-source -I --before-build .
subprocess returned exit status 2</span></span></p>
<p>Tuukka<br>
</p>
<div class="moz-cite-prefix">Otto Kekäläinen kirjoitti 21.10.2021
klo 11.02:<br>
</div>
<blockquote type="cite"
cite="mid:CAOU6tABcW_cPv3OYxmzi6WfikueDNB6ZZi48dkqnFugnN2T-4A@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hello Stephen!
The package builds fine using dpkg-buildpackage, debuilder,
git-buildpackage or any of the usual Debian tools (as also shown by
the CI pipeline at
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines">https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines</a>). The
logs you sent are incomplete, they just contain the end of the log
without showing what was your starting situation or what were the
first commands you ran after cloning the repository.
Without seeing the full build log it is hard to say what failed in the
build, but I suspect you ran some commands before dpkg-buildpackage
that somehow modified the sources and therefore the build is not clean
anymore or something (but this is just speculation).
On Tue, Oct 19, 2021 at 11:32 AM Stephen <a class="moz-txt-link-rfc2396E" href="mailto:stephen@tha.net"><stephen@tha.net></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hi Otto,
I send you a build log which failed when running "dpkg-buildpackage -b". I wasnt sure what next steps to take.
The instructions you gave regarding the failed build command were not really relevant as it was just the last command shown by the build log, although I did try running it manually it also didnt work. Adding your instructions to that manually run command also did not seem to make sense as ../cmake is a directory, yet in the build statement it is the command. Sorry for not providing that further feedback.
At this point Im not sure how to make it build with "dpkg-buildpackage" or if it is simply not expected to work with this command. Should I instead simply not use this command any more to do a package build? Sorry I have not had time to read through the most current build documentation to check.
On Tue, Oct 19, 2021 at 6:42 PM Otto Kekäläinen <a class="moz-txt-link-rfc2396E" href="mailto:otto@kekalainen.net"><otto@kekalainen.net></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
I didn't get any review/feedback yet..
ma 11. lokak. 2021 klo 8.59 Otto Kekäläinen <a class="moz-txt-link-rfc2396E" href="mailto:otto@kekalainen.net"><otto@kekalainen.net></a> kirjoitti:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hello!
I recently created a new repository at
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/mariadb-team/mariadb-server">https://salsa.debian.org/mariadb-team/mariadb-server</a> that uses the
DEP-14 repository layout:
<a class="moz-txt-link-freetext" href="https://dep-team.pages.debian.net/deps/dep14/">https://dep-team.pages.debian.net/deps/dep14/</a>
First I imported the current mariadb-10.5 Salsa project on branch
debian/latest and then I imported upstream MariaDB 10.6.4 and did all
the usual QA work needed. This should now be ready for upload to
unstable.
This was a fairly big task I have been doing in steps since August and
there is a possibility that I missed something. Please review all the
recent commits at
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/latest/debian">https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/latest/debian</a>
and let me know if you spot something.
If you are not a Debian packaging or MariaDB expert, you can still
help by at least proof-reading that there are no obvious mishaps in
the commits.
If there is not much more to fix, I'll upload this the Debian unstable
in the coming days.
- Otto
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Tuukka Pasanen
Production Manager
<a class="moz-txt-link-abbreviated" href="mailto:tuukka.pasanen@ilmi.fi">tuukka.pasanen@ilmi.fi</a>
+358 40 7303 216</pre>
</body>
</html>