From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: .travis.yml: update masterdirs
Date: Sun, 05 Jan 2020 08:01:29 +0100 [thread overview]
Message-ID: <20200105070129.CL2sFtfhMD34_96boKYmBD2kinoGqYgEO5U16auM170@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18049@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
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.
next prev parent reply other threads:[~2020-01-05 7:01 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 5:59 [PR PATCH] " voidlinux-github
2020-01-05 6:41 ` voidlinux-github
2020-01-05 6:42 ` voidlinux-github
2020-01-05 6:43 ` voidlinux-github
2020-01-05 6:56 ` voidlinux-github
2020-01-05 7:01 ` voidlinux-github [this message]
2020-01-05 7:02 ` voidlinux-github
2020-01-05 7:03 ` voidlinux-github
2020-01-05 7:04 ` voidlinux-github
2020-01-05 7:05 ` voidlinux-github
2020-01-05 7:06 ` voidlinux-github
2020-01-05 7:06 ` voidlinux-github
2020-01-05 7:07 ` voidlinux-github
2020-01-05 7:08 ` voidlinux-github
2020-01-05 7:31 ` voidlinux-github
2020-01-05 7:34 ` voidlinux-github
2020-01-05 7:35 ` voidlinux-github
2020-01-05 7:37 ` voidlinux-github
2020-01-05 7:38 ` voidlinux-github
2020-01-05 7:58 ` voidlinux-github
2020-01-05 8:00 ` voidlinux-github
2020-01-05 8:01 ` voidlinux-github
2020-01-05 8:02 ` voidlinux-github
2020-01-05 8:03 ` voidlinux-github
2020-01-05 8:04 ` voidlinux-github
2020-01-05 8:04 ` voidlinux-github
2020-01-05 8:05 ` voidlinux-github
2020-01-05 8:06 ` voidlinux-github
2020-01-05 8:06 ` voidlinux-github
2020-01-05 8:09 ` voidlinux-github
2020-01-05 8:11 ` voidlinux-github
2020-01-05 8:12 ` voidlinux-github
2020-01-05 8:13 ` voidlinux-github
2020-01-05 8:13 ` voidlinux-github
2020-01-05 8:14 ` voidlinux-github
2020-01-05 8:15 ` voidlinux-github
2020-01-05 8:15 ` voidlinux-github
2020-01-05 8:16 ` voidlinux-github
2020-01-05 8:18 ` voidlinux-github
2020-01-05 8:22 ` voidlinux-github
2020-01-05 8:27 ` voidlinux-github
2020-01-05 8:28 ` voidlinux-github
2020-01-05 8:29 ` voidlinux-github
2020-01-05 8:37 ` voidlinux-github
2020-01-05 8:37 ` voidlinux-github
2020-01-05 8:39 ` voidlinux-github
2020-01-05 8:41 ` voidlinux-github
2020-01-05 8:41 ` voidlinux-github
2020-01-05 8:42 ` voidlinux-github
2020-01-05 9:45 ` [PR PATCH] [Closed]: " voidlinux-github
2020-01-05 9:45 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200105070129.CL2sFtfhMD34_96boKYmBD2kinoGqYgEO5U16auM170@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).