From: jirib <jirib@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] libguestfs broken - destdir missing for update-libguestfs-appliance
Date: Mon, 22 Mar 2021 20:52:55 +0100 [thread overview]
Message-ID: <20210322195255.-xPe7IeIayo_hVc2h3OtgdHVrbVpYDY3HDutbhvYMFI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29059@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2707 bytes --]
Closed issue by jirib on void-packages repository
https://github.com/void-linux/void-packages/issues/29059
Description:
<!-- 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.10.17_1 x86_64 GenuineIntel uptodate rrFFF`
* package:
`libguestfs-1.44.0_1`
### Expected behavior
`update-libguestfs-appliance` should work out of the box, it should download binary applicance and extract it for libguestfs use.
### Actual behavior
`update-libguestfs-appliance` fails as it does NOT have directory where to extract data
```
# update-libguestfs-appliance
Downloading binary appliance v1.40.1 for libguestfs ...
--2021-02-25 20:36:51-- http://libguestfs.org/download/binaries/appliance/appliance-1.40.1.tar.xz
Resolving libguestfs.org (libguestfs.org)... 46.43.9.215, 2001:41c9:1:422::215
Connecting to libguestfs.org (libguestfs.org)|46.43.9.215|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://download.libguestfs.org/binaries/appliance/appliance-1.40.1.tar.xz [following]
--2021-02-25 20:36:52-- http://download.libguestfs.org/binaries/appliance/appliance-1.40.1.tar.xz
Resolving download.libguestfs.org (download.libguestfs.org)... 46.43.9.215, 2001:41c9:1:422::215
Reusing existing connection to libguestfs.org:80.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://download.libguestfs.org/binaries/appliance/appliance-1.40.1.tar.xz [following]
--2021-02-25 20:36:52-- https://download.libguestfs.org/binaries/appliance/appliance-1.40.1.tar.xz
Connecting to download.libguestfs.org (download.libguestfs.org)|46.43.9.215|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 111566640 (106M) [application/x-xz]
Saving to: ‘appliance-1.40.1.tar.xz’
appliance-1.40.1.tar.xz 100%[====================================>] 106.40M 2.34MB/s in 46s
2021-02-25 20:37:38 (2.33 MB/s) - ‘appliance-1.40.1.tar.xz’ saved [111566640/111566640]
Checking checksum ... appliance-1.40.1.tar.xz: OK
Extracting binary appliance files to /usr/lib/guestfs:
tar: /usr/lib/guestfs: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
```
```
# grep /usr/lib `which update-libguestfs-appliance `
echo "Extracting binary appliance files to /usr/lib/guestfs:" >&2
tar -xvf appliance-${VERSION}.tar.xz -C /usr/lib/guestfs \
chmod -v 644 "/usr/lib/guestfs/"{kernel,initrd,root,README.fixed}
```
### Steps to reproduce the behavior
* update-libguestfs-appliance # as root
prev parent reply other threads:[~2021-03-22 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 20:00 [ISSUE] " jirib
2021-02-25 20:07 ` ericonr
2021-02-25 21:13 ` thypon
2021-03-22 19:52 ` jirib
2021-03-22 19:52 ` jirib [this message]
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=20210322195255.-xPe7IeIayo_hVc2h3OtgdHVrbVpYDY3HDutbhvYMFI@z \
--to=jirib@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).