bzip2 is not available in the snap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git-ubuntu |
Fix Released
|
Undecided
|
Robie Basak |
Bug Description
[Affects the edge snap and git master only]
I've realized that postgresql-13 isn't imported yet into git ubuntu.
I wanted to locally import it to work with that repository until it is officially imported.
But I've found it to crash
$ cd /tmp/
$ mkdir postgresql-13
$ cd postgresql-13
$ git ubuntu import postgresql-13 -d postgresql-13 --no-push --no-fetch
05/18/2021 12:00:03 - INFO:Ubuntu Server Team importer v1.0
05/18/2021 12:00:07 - INFO:Importing patches-unapplied 13~beta2-1 to debian/experimental
05/18/2021 12:00:09 - INFO:Downloading postgresql-
05/18/2021 12:00:17 - INFO:Downloading postgresql-
05/18/2021 12:00:19 - ERROR:Command exited 1: gbp import-orig --no-merge --upstream-branch do-not-push --pristine-tar --no-interactive --no-symlink-orig '--upstream-
05/18/2021 12:00:19 - ERROR:stdout:
05/18/2021 12:00:19 - ERROR:stderr: tar (child): lbzip2: 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
gbp:error: Couldn't unpack '/tmp/postgresq
05/18/2021 12:00:19 - WARNING:Unable to pristine-tar import orig tarball for 13~beta2-1
05/18/2021 12:00:19 - ERROR:Command exited 29: dpkg-source -x --skip-patches /tmp/postgresql
05/18/2021 12:00:19 - ERROR:stdout: dpkg-source: info: extracting postgresql-13 in /tmp/tmptyu3ehe8/x
dpkg-source: info: unpacking postgresql-
05/18/2021 12:00:19 - ERROR:stderr: Can't exec "bunzip2": No such file or directory at /snap/git-
dpkg-source: error: unable to execute bunzip2: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
dpkg-source: error: tar -xf - --no-same-
Traceback (most recent call last):
File "/snap/
import_func(
File "/snap/
import_
File "/snap/
unapplied_
File "/snap/
run(cmd)
File "/snap/
raise e
File "/snap/
cp = subprocess.run(
File "/snap/
raise CalledProcessEr
subprocess.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/snap/
load_
File "/snap/
sys.
File "/snap/
return main(
File "/snap/
_main_
File "/snap/
history_found = import_publishes(
File "/snap/
raise GitUbuntuImport
gitubuntu.
Related branches
- Bryce Harrington: Approve
- Server Team CI bot: Approve (continuous-integration)
- Christian Ehrhardt : Needs Fixing
-
Diff: 273 lines (+213/-2)5 files modifieddebian/control (+1/-0)
gitubuntu/integration_test.py (+208/-0)
gitubuntu/source_builder.py (+1/-1)
snap-wrappers/wrappers/reconstruct-changelog (+1/-1)
snap/snapcraft.yaml (+2/-0)
summary: |
- postgresql-13 fails to import - lbzip2: Cannot exec: No such file or - directory + bzip2 is not available in the snap |
description: | updated |
Changed in usd-importer: | |
status: | New → Triaged |
assignee: | nobody → Robie Basak (racb) |
tags: | added: snap |
Changed in usd-importer: | |
status: | Triaged → In Progress |
Changed in usd-importer: | |
status: | In Progress → Fix Committed |
It is imported, but isn't the default repository in Launchpad. git-ubuntu can't do that as it doesn't have the privileges.
We have three separate issues here:
1) git-ubuntu has no automated mechanism to automatically make newly imported repositories the default repositories for the Ubuntu package target in Launchpad, which means that "git ubuntu clone <package>" doesn't work straight away. Manual intervention (by any core dev) is required.
2) bzip2 is broken in the snap as you discovered, but this is only in the edge snap and I have a card on it. The importer service instance isn't affected as it runs beta.
3) [not sure you hit this] packages in main are assessed when the poller is started, and not updated afterwards. Restarting the poller is necessary after a component change. The latest refactoring in edge now makes it easier to fix this, but this might not be worth worrying because we intend to import all packages anyway.
Which issue (if any) would you like to track with this bug?