-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install package on Ubuntu 19.10 and earlier due to libgcc-s1 #504
Comments
I am seeing the same on Ubuntu 19.10 on 0.5.0. Prior versions worked fine |
@mnsgs 19.10 has reached end-of-life in July 2020, hence I would suggest upgrading to 20.04-LTS or 20.10. As for 16.04 @rufusshrestha - Looks like |
Same issue here. But on Ubuntu 18.04 Edit: version 0.4.4 installs fine, but all after that fails for the same reason. |
@Kr1ss-XD Thanks Kris. If it is no longer supported for 16.04 then its fine with EOL coming up on Apr anyway. However, I still think its a regression if it does not work on 18.04 reported by @filipelbc and use of library only used in 20.04 will invalidate an LTS release that I think should be supported. As my issue is resolved, I'm not sure if I should leave this open until 18.04 issue is resolved or close it. |
I definitely agree about that. I'd suggest to leave the issue open. @dandavison mentioned he'd be off for two weeks, but maybe there's still some way to support Ubuntu's before 20.04 (probably this also hits older Debian versions as well). Maybe you could change the issue title, so that it says 'Ubuntu <20.04' or '19.10 and earlier' or something like that ? |
@Kr1ss-XD Thank you. Sure, will do as advised. No hurry there @dandavison I'm sure we can all live with older version for a while. |
NB/ Looks like this actually affects Debian 9 (oldstable) and 10 (stable) as well : The |
On Ubuntu 16.04, this can be installed by manually fetching the following packages from focal repo as a temp workaround gcc-10-base_10.2.1-6_amd64.deb |
Thanks all. Do you have a recommended action for delta to take here? |
The version linked against musl is working fine on Debian Buster. Maybe you could simply sit this problem out and refer x64 users to the musl package? |
The version linked against musl works fine in Ubuntu 18.04. |
This is basically just an informational post, no recommended course of action, but I thought I might post some related links that may be helpful. I've been affected by this as well. Running on Debian 10 (stable) with apt configuration to pull in from testing (bullseye) when necessary (but not preferentially). When installing with
on boot. In order to attempt a fix, I had to boot from a live CD, chroot (per this process), and Here's a link to a similar (if not identical) issue with Wish I had a useful recommendation, but people who are mixing apt sources need to beware. (Hi @dandavison! Awesome project you've got here.) |
Argh! Hello @jamesob and I sincerely hope that is the worst outcome that anyone will ever have as a result of using delta. I've added a warning and suggestion to use the musl-linked versions to the README. If anyone can suggest anything more we can do then please do but I'll close this as it sounds like there's not a lot. |
tl;dr if you're on an older version of Ubuntu (19.10 and earlier) or Debian (10 and earlier):
I also ran into a conflict with an existing |
Would anyone here be able to review the small change to the .deb being made in #1217? (Removes "provides") |
Have we dropped support for Ubuntu 16.04?
Cannot install due to libgcc-s1 dependency error
`Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
git-delta : Depends: libgcc-s1 (>= 4.2) but it is not installable
E: Unable to correct problems, you have held broken packages.
`
The text was updated successfully, but these errors were encountered: