Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Santiago Vila]

On Tue, 1 Nov 2016, Ben Hutchings wrote:

> You can if you want, but all I will do then is tag it upstream and
> downgrade to wishlist.  I believe the upstream developers of overlayfs
> are well aware of limitations like this.

Ok, simple question: Could you tell if the problem I'm reporting here
is really the same as this one?:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836211

(They both happen when renaming directories).

Thanks.

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Santiago Vila]

On Tue, 1 Nov 2016, Jeremy Bicha wrote:

> On Tue, Nov 1, 2016 at 5:57 AM, Santiago Vila  wrote:
> > The original tarball does not contain any directories:
> >
> > $ tar tvf numix-icon-theme_0~20160619.217701b.orig.tar.xz | grep ^d
> > [ no output at all ]
> 
> I think your syntax is wrong because the original tarball definitely
> does contain directories: your log snippet itself shows 9 directories!

(Just try "tar tvf" without the grep to see it for yourself :-)

It contains directory/file entries, but not directory entries as such.
This is because (as I read debian/rules) it was created this way:

find [...] -type f -print | tar [...]

i.e. only files, no directories.

This is just what triggers the problem, but maybe not really "the problem",
which is probably just a problem in Linux as pointed out by Ben.

So please don't repack the tarball.

I still would like to know for sure whether or not this is buildable
in buildd.debian.org.

If you have any pending changes to make I would appreciate if you could
make the next upload in source-only form (dpkg-buildpackage -S).

Even if the package is Arch:all, it will be autobuilt and we could see
the build log here:

https://buildd.debian.org/status/package.php?p=numix-icon-theme

(I'm also going to ask sbuild maintainer for his opinion).

BTW: I would still like you to reproduce the problem. Please try
a pure Debian stretch system (which may be a virtual machine)
and a stretch chroot. If you still can't reproduce it that
way, contact me privately and I would then consider giving you
access to a virtual machine where I definitely can.

Thanks.

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Ben Hutchings]

On Wed, 2016-11-02 at 00:39 +0100, Santiago Vila wrote:
> On Tue, Nov 01, 2016 at 03:11:20PM -0600, Ben Hutchings wrote:
> 
> > 'Cloned chroot' doesn't imply that at all.  And most buildds are
> > running the kernel from stable, which doesn't include overlayfs.
> 
> 
> Well, if you are sure that this will not happen in the official
> buildds, then repacking is not necessary at all.
> 
> Would be ok for you if we just reassign this to "linux"?

You can if you want, but all I will do then is tag it upstream and
downgrade to wishlist.  I believe the upstream developers of overlayfs
are well aware of limitations like this.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special
case.



signature.asc
Description: This is a digitally signed message part

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Jeremy Bicha]

On Tue, Nov 1, 2016 at 5:57 AM, Santiago Vila  wrote:
> The original tarball does not contain any directories:
>
> $ tar tvf numix-icon-theme_0~20160619.217701b.orig.tar.xz | grep ^d
> [ no output at all ]

I think your syntax is wrong because the original tarball definitely
does contain directories: your log snippet itself shows 9 directories!
But why only 9? there's a lot more directories than that. A silly
question, but have you tried the build a second time, in case perhaps
the tarball you downloaded got corrupted or something?

I don't particularly like the code in debian/rules that's used the
create the original tarball; instead I'd prefer if uscan could gain
native git snapshot support [1] or if the numix-icon-theme developers
would actually tag releases [2]. As I commented in debian/rules, the
code is inspired by what I found other packages doing. I will replace
mine with simpler code if someone wants to submit it.

[1] https://bugs.debian.org/811565
[2] https://github.com/numixproject/numix-icon-theme/issues/1089

Thanks,
Jeremy

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Santiago Vila]

On Tue, Nov 01, 2016 at 03:11:20PM -0600, Ben Hutchings wrote:

> 'Cloned chroot' doesn't imply that at all.  And most buildds are
> running the kernel from stable, which doesn't include overlayfs.

Well, if you are sure that this will not happen in the official
buildds, then repacking is not necessary at all.

Would be ok for you if we just reassign this to "linux"?

Thanks.

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Ben Hutchings]

Control: severity -1 normal

On Tue, 2016-11-01 at 19:17 +0100, Santiago Vila wrote:
> On Tue, Nov 01, 2016 at 12:13:00PM -0600, Ben Hutchings wrote:
> > Do Debian buildds use overlayfs?
> 
> 
> Yes, I think so. Just look at any build log in buildd.debian.org and
> you will see this:
> 
> Not cleaning session: cloned chroot in use
> 
> This is what happens when sbuild is used with union-type=overlay.
> (When not, you would see at that point how installed packages are
> deinstalled).

'Cloned chroot' doesn't imply that at all.  And most buildds are
running the kernel from stable, which doesn't include overlayfs.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special
case.



signature.asc
Description: This is a digitally signed message part

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Jeremy Bicha]

On Tue, Nov 1, 2016 at 2:13 PM, Ben Hutchings  wrote:
> Do Debian buildds use overlayfs?  If not then I don't see how this can
> be serious.

Also, it builds fine here. Ubuntu 16.10 host using sbuild
0.71.0-2ubuntu1 with Debian sid guest with union-type=overlay

I'd attach a build log as proof but somehow my build log is 7MB(!).

Thanks,
Jeremy Bicha

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Santiago Vila]

On Tue, Nov 01, 2016 at 12:13:00PM -0600, Ben Hutchings wrote:
> Do Debian buildds use overlayfs?

Yes, I think so. Just look at any build log in buildd.debian.org and
you will see this:

Not cleaning session: cloned chroot in use

This is what happens when sbuild is used with union-type=overlay.
(When not, you would see at that point how installed packages are deinstalled).

Thanks.

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Ben Hutchings]

Do Debian buildds use overlayfs?  If not then I don't see how this can
be serious.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special
case.



signature.asc
Description: This is a digitally signed message part

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

[Santiago Vila]

Package: src:numix-icon-theme
Severity: serious

Dear maintainer:

I tried to build "numix-icon-theme" in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:

+--+
| Build environment|
+--+

Kernel: Linux 4.7.0-1-amd64 amd64 (x86_64)
Toolchain package versions: binutils_2.27-9+b1 dpkg-dev_1.18.10 g++-6_6.2.0-9 
gcc-6_6.2.0-9 libc6-dev_2.24-5 libstdc++-6-dev_6.2.0-9 libstdc++6_6.2.0-9 
linux-libc-dev_4.7.8-1
Package versions: adduser_3.115 apt_1.3.1 autoconf_2.69-10 automake_1:1.15-4 
autopoint_0.19.8.1-1 autotools-dev_20160430.1 base-files_9.6 base-passwd_3.5.40 
bash_4.4-1 binutils_2.27-9+b1 bsdmainutils_9.0.12 bsdutils_1:2.28.2-1 
build-essential_12.2 bzip2_1.0.6-8 coreutils_8.25-2 cpp_4:6.1.1-1 cpp-6_6.2.0-9 
dash_0.5.8-2.3 debconf_1.5.59 debhelper_10.2.2 debian-archive-keyring_2014.3 
debianutils_4.8 dh-autoreconf_12 dh-strip-nondeterminism_0.028-1 
diffutils_1:3.5-1 dpkg_1.18.10 dpkg-dev_1.18.10 e2fslibs_1.43.3-1 
e2fsprogs_1.43.3-1 eatmydata_105-5 fakeroot_1.21-2 file_1:5.29-1 
findutils_4.6.0+git+20160703-2 g++_4:6.1.1-1 g++-6_6.2.0-9 gcc_4:6.1.1-1 
gcc-5-base_5.4.1-3 gcc-6_6.2.0-9 gcc-6-base_6.2.0-9 gettext_0.19.8.1-1 
gettext-base_0.19.8.1-1 gpgv_2.1.15-4 grep_2.26-1 groff-base_1.22.3-8 
gzip_1.6-5 hostname_3.18 init-system-helpers_1.45 insserv_1.14.0-5.4 
intltool-debian_0.35.0+20060710.4 less_481-2.1 libacl1_2.2.52-3 
libapt-pkg5.0_1.3.1 libarchive-zip-perl_1.59-1 libasan3_6.2.0-9 libatom
 ic1_6.2.0-9 libattr1_1:2.4.47-2 libaudit-common_1:2.6.7-1 libaudit1_1:2.6.7-1 
libblkid1_2.28.2-1 libbsd0_0.8.3-1 libbz2-1.0_1.0.6-8 libc-bin_2.24-5 
libc-dev-bin_2.24-5 libc-l10n_2.24-5 libc6_2.24-5 libc6-dev_2.24-5 
libcap-ng0_0.7.7-3 libcc1-0_6.2.0-9 libcilkrts5_6.2.0-9 libcomerr2_1.43.3-1 
libcroco3_0.6.11-2 libdb5.3_5.3.28-12 libdebconfclient0_0.218 
libdpkg-perl_1.18.10 libeatmydata1_105-5 libfakeroot_1.21-2 libfdisk1_2.28.2-1 
libffi6_3.2.1-6 libfile-stripnondeterminism-perl_0.028-1 libgcc-6-dev_6.2.0-9 
libgcc1_1:6.2.0-9 libgcrypt20_1.7.3-2 libgdbm3_1.8.3-14 libglib2.0-0_2.50.1-1 
libgmp10_2:6.1.1+dfsg-1 libgomp1_6.2.0-9 libgpg-error0_1.24-1 libicu57_57.1-4 
libisl15_0.17.1-1 libitm1_6.2.0-9 liblsan0_6.2.0-9 liblz4-1_0.0~r131-2 
liblzma5_5.2.2-1.2 libmagic-mgc_1:5.29-1 libmagic1_1:5.29-1 libmount1_2.28.2-1 
libmpc3_1.0.3-1 libmpfr4_3.1.5-1 libmpx2_6.2.0-9 libncurses5_6.0+20160917-1 
libncursesw5_6.0+20160917-1 libpam-modules_1.1.8-3.3 
libpam-modules-bin_1.1.8-3.3 libpam-runtime_1.1.8-3.
 3 libpam0g_1.1.8-3.3 libpcre3_2:8.39-2 libperl5.24_5.24.1~rc3-3 
libpipeline1_1.4.1-2 libquadmath0_6.2.0-9 libselinux1_2.5-3 
libsemanage-common_2.5-1 libsemanage1_2.5-1 libsepol1_2.5-1 libsigsegv2_2.10-5 
libsmartcols1_2.28.2-1 libss2_1.43.3-1 libstdc++-6-dev_6.2.0-9 
libstdc++6_6.2.0-9 libsystemd0_231-9 libtimedate-perl_2.3000-2 
libtinfo5_6.0+20160917-1 libtool_2.4.6-2 libtsan0_6.2.0-9 libubsan0_6.2.0-9 
libudev1_231-9 libunistring0_0.9.6+really0.9.3-0.1 libustr-1.0-1_1.0.4-5 
libuuid1_2.28.2-1 libxml2_2.9.4+dfsg1-2 linux-libc-dev_4.7.8-1 locales_2.24-5 
login_1:4.2-3.2 m4_1.4.17-5 make_4.1-9 man-db_2.7.5-1 mawk_1.3.3-17 
mount_2.28.2-1 multiarch-support_2.24-5 nano_2.7.0-1 
ncurses-base_6.0+20160917-1 ncurses-bin_6.0+20160917-1 passwd_1:4.2-3.2 
patch_2.7.5-1 perl_5.24.1~rc3-3 perl-base_5.24.1~rc3-3 
perl-modules-5.24_5.24.1~rc3-3 po-debconf_1.0.20 
sbuild-build-depends-core-dummy_0.invalid.0 
sbuild-build-depends-numix-icon-theme-dummy_0.invalid.0 sed_4.2.2-8 
sensible-utils_0.0.9 startpar_0.
 59-3.1 sysv-rc_2.88dsf-59.8 sysvinit-utils_2.88dsf-59.8 tar_1.29b-1 
tzdata_2016h-1 util-linux_2.28.2-1 xz-utils_5.2.2-1.2 zlib1g_1:1.2.8.dfsg-2+b1

+--+
| Build|
+--+


Unpack source
-

gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/sbuild-nonexistent/.gnupg/trustedkeys.kbx': General 
error
gpgv: Signature made Wed Jun 22 07:20:20 2016 CEST
gpgv:using RSA key 9AF46B3025771B31
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
./numix-icon-theme_0~20160619.217701b-1.dsc
dpkg-source: info: extracting numix-icon-theme in /<>
dpkg-source: info: unpacking numix-icon-theme_0~20160619.217701b.orig.tar.xz
tar: numix-icon-theme-0~20160619.217701b/Numix/128/devices: Directory renamed 
before its status could be extracted
tar: numix-icon-theme-0~20160619.217701b/Numix/128/categories: Directory 
renamed before its status could be extracted
tar: numix-icon-theme-0~20160619.217701b/Numix/128/actions: Directory renamed 
before its status could