From: svenper <svenper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] binpkg is being created, waiting for 1s...
Date: Wed, 15 Apr 2020 15:57:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21020@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2297 bytes --]
New issue by svenper on void-packages repository
https://github.com/void-linux/void-packages/issues/21020
Description:
Inspired by #2368
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.32_1 x86_64-musl GenuineIntel uptodate hold rrnFFFFFFFFF
* package:
texlive2020-exec [[WIP]](/svenper/void-packages/tree/texlive) (which package should be irrelevant but repro timing is hard)
### Expected behavior
The dviout-util subpkg packages just like the others. `.lock` files are reset when repackaging.
### Actual behavior
```text
=> WARNING: texlive2020-exec-dviout-util-2020.0_1: binpkg is being created, waiting for 1s...
=> WARNING: texlive2020-exec-dviout-util-2020.0_1: binpkg is being created, waiting for 1s...
=> WARNING: texlive2020-exec-dviout-util-2020.0_1: binpkg is being created, waiting for 1s...
...
```
```text
$ ls -lA srcpkgs/texlive2020-exec-dviout-util
lrwxrwxrwx 1 $USER $USER 16 2020-04-15 07:13 srcpkgs/texlive2020-exec-dviout-util -> texlive2020-exec
```
```text
$ file masterdir.*/upperdir/destdir/texlive2020-exec-dviout-util-2020.0/opt/texlive/2020/bin/xbps/*
masterdir.XXXXOjegIa/upperdir/destdir/texlive2020-exec-dviout-util-2020.0/opt/texlive/2020/bin/xbps/chkdvifont: ELF 64-bit LSB shared object, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, BuildID[sha1]=90500c98f88a4080a71af02d436761b77333fec3, stripped
masterdir.XXXXOjegIa/upperdir/destdir/texlive2020-exec-dviout-util-2020.0/opt/texlive/2020/bin/xbps/dvispc: ELF 64-bit LSB shared object, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, BuildID[sha1]=9149d0fb093ea6de295d49249568a7a422b98551, stripped
```
There was a `.lock` file from previous build cancelled midway through packaging. Removing it fixed the problem.
```text
rm /var/cache/xbps-src/binpkgs/texlive/texlive2020-exec-dviout-util-2020.0_1.x86_64-musl.xbps.lock
```
### Steps to reproduce the behavior
Package a package, but cancel it while packaging. Then package again.
```text
./xbps-src -H /var/cache/xbps-src pkg -t -f texlive2020-exec
```
next reply other threads:[~2020-04-15 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:57 svenper [this message]
2020-04-24 0:16 ` abenson
2020-08-10 6:02 ` Noah-Huppert
2021-01-21 14:09 ` ericonr
2021-01-21 14:10 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21020@inbox.vuxu.org \
--to=svenper@users.noreply.github.com \
--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).