Build deps problem when building aptly deb packages using standard Debian tools

[syominsergey]

Hi!

I tried to build aptly debian packages and ran into problem with build deps.
Now I will show howto reproduce this problem.

Assumed, that we have already cloned aptly git repository somewhere on host machine in clear state, just after git clone https://github.com/aptly-dev/aptly.git. Let's say that we have env var APTLY_PROJ_PATH poiting to folder where aptly git repo cloned on host machine. It is important to make sure that the folder ${APTLY_PROJ_PATH}/.go is missing before doing next steps.

Start new Debian Trixie container:

podman run --pull=always -it --rm -v "${APTLY_PROJ_PATH}":/root/aptly debian:trixie bash

Update apt cache:

apt update

Goto into folder with aptly sources:

cd ~/aptly/

Install build-deps using apt:

apt build-dep . |& tee ~/apt_build-dep.log

You can see full log here: apt_build-dep.log.

Try to build deb packages:

dpkg-buildpackage -b -uc |& tee ../dpkg-buildpackage.log

Build finished with a lot of error messages with text tls: failed to verify certificate: x509: certificate signed by unknown authority.

You can see full log here: dpkg-buildpackage.log.

It is possible to solve problem by installing package ca-certificates:

apt install ca-certificates

After installation of ca-certificates it is possible to build aptly deb packages with dpkg-buildpackage -b -uc successfully.

Maybe it is necessary to add ca-certificates as Build-Depends in debian/control file?

p.s. I tested project in state after commit a65f79e.

[alexmyczko]

can you use the debian source package and retry?

refer to

https://metadata.ftp-master.debian.org/changelogs//main/a/aptly/aptly_1.6.1+ds1-3_copyright

the point is upstream packages should not ship debian/ if they do they get repackaged usually (upstream=debian being native is the exception)

if you really want the git checkout of this repo go ahead, drop debian/ and get debian/ from debian...

[syominsergey]

@alexmyczko, thank you for your comment.
So, you think that behaviour I described is not a problem?
I won't insist.
I thought existance of debian folder in aptly project denotes that it is possible to build aptly with standard debian tools.
But if it wasn't meant that way, then I was wrong.

[alexmyczko]

@syominsergey 6.9.8.2 at https://www.debian.org/doc/manuals/developers-reference/developers-reference.en.html#document-best-pkging-practices can't find the part about debian/ by upstream though right now. the problem is with non debian people doing debian/ packaging, it didn't went through debian qa (new queue, and some other testing). the point is upstream source code should be without distro specific parts, the distro adds the debian/ (or for other distros other things).

having a debian/ might make it possible to build it with debian tools. indeed, but it does not mean it will work, as in this case :)