On Apr 28 2020, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> Could I get you to do this:
>
> sbuild -c buster-amd64 -b -n 958989
Uhm. I feel pretty dumb, but what is the "958989" supposed to do?
$ sbuild -c buster-amd64 -b -n 958989
No distribution defined
Without that, I get:
$ git reset --hard
$ git clean -xdf
$ sbuild -c buster-amd64 -b -n
dh clean --with=autoreconf
dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building valgrind using existing
./valgrind_3.15.0.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: local changes detected, the modified files are:
valgrind/configure.ac
valgrind/coregrind/m_syswrap/priv_syswrap-linux.h
valgrind/coregrind/m_syswrap/syswrap-amd64-linux.c
valgrind/coregrind/m_syswrap/syswrap-arm64-linux.c
valgrind/coregrind/m_syswrap/syswrap-linux.c
valgrind/coregrind/m_syswrap/syswrap-ppc32-linux.c
valgrind/coregrind/m_syswrap/syswrap-ppc64-linux.c
valgrind/coregrind/m_syswrap/syswrap-s390x-linux.c
valgrind/coregrind/m_syswrap/syswrap-x86-linux.c
valgrind/memcheck/tests/linux/Makefile.am
valgrind/memcheck/tests/linux/sys-copy_file_range.c
valgrind/memcheck/tests/linux/sys-copy_file_range.stderr.exp
valgrind/memcheck/tests/linux/sys-copy_file_range.vgtest
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/valgrind_3.15.0-2~1.gbpdcc9f6.diff.VJgNrN
E: Failed to package source directory /home/nikratio/tmp/valgrind
> schroot -rc 958989 -u root
That's probably from the previous error...
$ schroot -rc 958989 -u root
E: 958989: Chroot not found
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
