[debian-mysql] MariaDB 10.6 for Debian packaged

Thu Oct 28 08:35:16 BST 2021

Hello,

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:

Incrementing changelog and starting build scripts
libdistro-info-perl is not installed, Debian release names are not known.
libdistro-info-perl is not installed, Ubuntu release names are not known.
Creating package version 1:10.6.4+maria~bullseye ...
dpkg-buildpackage: info: source package mariadb-10.6
dpkg-buildpackage: info: source version 1:10.6.4+maria~bullseye
dpkg-buildpackage: info: source distribution bullseye
dpkg-buildpackage: info: source changed by Debian MySQL Maintainers 
<pkg-mysql-maint at lists.alioth.debian.org>
  dpkg-source -I --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying mips-groonga-atomic.patch
dpkg-source: info: applying mips-connect-unaligned.patch
dpkg-source: info: applying c11_atomics.patch
dpkg-source: info: applying 
0025-Change-the-default-optimization-from-O3-to-O2-in-mys.patch
dpkg-source: info: applying 
mips-compilation-failure-__bss_start-symbol-miss.patch
dpkg-source: info: applying rocksdb-kfreebsd.patch
patching file storage/rocksdb/build_rocksdb.cmake
can't find file to patch at input line 20
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/storage/rocksdb/rocksdb/CMakeLists.txt
|+++ b/storage/rocksdb/rocksdb/CMakeLists.txt
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 40
erhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/storage/rocksdb/rocksdb/build_tools/build_detect_platform
|+++ b/storage/rocksdb/rocksdb/build_tools/build_detect_platform
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/storage/rocksdb/rocksdb/env/env_posix.cc
|+++ b/storage/rocksdb/rocksdb/env/env_posix.cc
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/storage/rocksdb/rocksdb/port/stack_trace.cc
|+++ b/storage/rocksdb/rocksdb/port/stack_trace.cc
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
patching file storage/rocksdb/rdb_io_watchdog.h
patching file storage/rocksdb/rdb_io_watchdog.cc

dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch 'rocksdb-kfreebsd.patch' is correctly 
applied by quilt, use 'quilt refresh' to update it
dpkg-source: info: restoring quilt backup files for rocksdb-kfreebsd.patch
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
erver/debian/patches/rocksdb-kfreebsd.patch subprocess returned exit 
status 1
dpkg-buildpackage: error: dpkg-source -I --before-build . subprocess 
returned exit status 2

Tuukka

Otto Kekäläinen kirjoitti 21.10.2021 klo 11.02:
> 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
> https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines). 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<stephen at tha.net>  wrote:
>> 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<otto at kekalainen.net>  wrote:
>>> I didn't get any review/feedback yet..
>>>
>>> ma 11. lokak. 2021 klo 8.59 Otto Kekäläinen<otto at kekalainen.net>  kirjoitti:
>>>> Hello!
>>>>
>>>> I recently created a new repository at
>>>> https://salsa.debian.org/mariadb-team/mariadb-server  that uses the
>>>> DEP-14 repository layout:
>>>> https://dep-team.pages.debian.net/deps/dep14/
>>>>
>>>> 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
>>>> https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/latest/debian
>>>> 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

-- 
Tuukka Pasanen
Production Manager
tuukka.pasanen at ilmi.fi
+358 40 7303 216
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20211028/3b39d32b/attachment.htm>