[Bug 1735014] Re: file:// and ssh:// protocols do not allow for failed gets
Ubuntu Foundations Team Bug Bot
1735014 at bugs.launchpad.net
Wed Nov 29 00:22:33 UTC 2017
The attachment "just_get(): return exit code of scp and cp" seems to be
a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debootstrap in Ubuntu.
https://bugs.launchpad.net/bugs/1735014
Title:
file:// and ssh:// protocols do not allow for failed gets
Status in debootstrap package in Ubuntu:
Confirmed
Bug description:
A user on #ubuntu reported failure of debootstrap to fetch the Release
file; hanging whilst trying to deal with an InRelease file that
doesn't exist when using ssh:// protocol.
scp: /opt/repository/isi/archive/15.11.6/trusty/dists/trusty/InRelease: No such file or directory
mv: cannot stat '/tmp/tmp-cache/var/lib/apt/lists/partial/debootstrap.invalid_dists_trusty_InRelease': No such file or directory
sed: can't read /tmp/tmp-cache/var/lib/apt/lists/debootstrap.invalid_dists_trusty_InRelease: No such file or directory
scp: /opt/repository/isi/archive/15.11.6/trusty/dists/trusty/InRelease: No such file or directory
mv: cannot stat '/tmp/tmp-cache/var/lib/apt/lists/partial/debootstrap.invalid_dists_trusty_InRelease': No such file or directory
sed: can't read /tmp/tmp-cache/var/lib/apt/lists/debootstrap.invalid_dists_trusty_InRelease: No such file or directory
scp: /opt/repository/isi/archive/15.11.6/trusty/dists/trusty/InRelease: No such file or directory
mv: cannot stat '/tmp/tmp-cache/var/lib/apt/lists/partial/debootstrap.invalid_dists_trusty_InRelease': No such file or directory
sed: can't read /tmp/tmp-cache/var/lib/apt/lists/debootstrap.invalid_dists_trusty_InRelease: No such file or directory
This seems to be due to a problem in functions::just_get() for both
ssh:// and file:// protocols where the 'get' is assumed to have
succeeded and hard-codes a "return 0".
I think these should be returning the exit code of the scp and cp
commands respectively.
Suggested patch attached
Affects 16.04 and 17.10. Apparently doesn't affect 14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1735014/+subscriptions
More information about the foundations-bugs
mailing list