git-pbuilder builds in a chroot, containing build-essential and the
build dependencies. (One reason for doing this is to have _only_ those
packages available, and not anything else you happen to have installed,
as a check that the declared build dependencies do include everything
needed.)
H
I am trying to build the postfix Debian package from the stretch sources.
I downloaded the .dsc, .orig.tar.gz, and ..debian.tar.xz files and did a
"gbp import-dsc *.dsc".
When I run "gbp buildpackage --git-dist=stretch" I get this:
test -f debian/rules
dh_clean build
dh_clean: Compatibility l
Andrey Rahmatullin writes:
> On Fri, Dec 06, 2019 at 05:37:25PM +0100, Ole Streicher wrote:
>> for the "casacore" package (written in C++), we wanted to introduce
>> symbols files for the shared libraries it produces. However, this
>> somehow does not work, as they seem to depend on the architectu
Am 06.12.2019 um 17:37 schrieb Ole Streicher:
How should one handle this?
Best regards
Ole
Arch dependend symbols are a pain in the ... :D
there are some approaches to handle it - one could have a look into the
KDE packaging tools and packaging how the KDE team handle this. I use a
differe
On Fri, Dec 06, 2019 at 05:37:25PM +0100, Ole Streicher wrote:
> Hi,
>
> for the "casacore" package (written in C++), we wanted to introduce
> symbols files for the shared libraries it produces. However, this
> somehow does not work, as they seem to depend on the architecture and/or
> the C++ comp
Hi,
for the "casacore" package (written in C++), we wanted to introduce
symbols files for the shared libraries it produces. However, this
somehow does not work, as they seem to depend on the architecture and/or
the C++ compiler version:
https://buildd.debian.org/status/logs.php?pkg=casacore&ver=3
6 matches
Mail list logo
