jadonk / jadonk/bonescript

Dependancy issue when install bonescript Debian package

Open
#188 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
510
Forks
153
PR merge metrics
No merged PRs in 30d

Description

When installing bonescript (using `apt install bonescript`) on a BeagleBone Blue using a Debian command line image I get the following problem.

```text
Setting up bonescript (0.7.3-git20190822.0-0rcnee2~buster+20190903) ...
bonescript:nodejs:[v10.15.2]
bonescript:installing:[bonescript-0.7.3-26c5522-v10.15.2-20190903.tar.xz]
bonescript:updating:[/usr/local/lib/node_modules/bonescript/]
tar (child): xz: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
dpkg: error processing package bonescript (--configure):
installed bonescript package post-installation script subprocess returned error exit status 2
Setting up libevent-2.1-6:armhf (2.1.8-stable-4) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
bonescript
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

Installing `xz-utils` fixes this issue. It would be good to add `xz-utils` as a dependency to the Debian bonescript package.

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the Debian package metadata and post-installation script responsible for configuring bonescript, then inspect how package dependencies are declared. Verify that the script requires xz and that the package installs xz-utils as a dependency. Reproduce installation on the Debian command-line image and confirm dpkg configures bonescript successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, javascript
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.