New comment by the-maldridge on void-packages repository

https://github.com/void-linux/void-packages/pull/18049#issuecomment-570879418

Comment:
```
[maldridge@vm1-a-mci-us ~]$ stat /repo/current/bsdtar-3.4.1_1.i686.xbps
  File: /repo/current/bsdtar-3.4.1_1.i686.xbps
  Size: 422724    	Blocks: 832        IO Block: 4096   regular file
Device: fc04h/64516d	Inode: 43600311    Links: 1
Access: (0644/-rw-r--r--)  Uid: (  998/reposync)   Gid: (  998/reposync)
Access: 2020-01-04 03:49:15.144834208 -0600
Modify: 2020-01-04 03:39:44.285627328 -0600
Change: 2020-01-04 03:38:42.972911852 -0600
 Birth: -
[maldridge@vm1-a-mci-us ~]$ stat /repo/current/xbps-0.57.1_7.i686.xbps
  File: /repo/current/xbps-0.57.1_7.i686.xbps
  Size: 89776     	Blocks: 176        IO Block: 4096   regular file
Device: fc04h/64516d	Inode: 43600426    Links: 1
Access: (0644/-rw-r--r--)  Uid: (  998/reposync)   Gid: (  998/reposync)
Access: 2020-01-04 06:49:35.847906919 -0600
Modify: 2020-01-04 06:13:54.167068396 -0600
Change: 2020-01-04 06:14:51.221594810 -0600
 Birth: -
```

They're present on disk, and I would have assumed that after building they'd be indexed as long as xbps-rindex didn't explode.  The linked failure though looks like they didn't make it into the chroot filesystem.  This makes sense, as base-chroot doesn't depend on bsdtar so it wouldn't have been added to the container.