Hi,
Can you please improve on the systemd service by adding
EnvironmentFile=-/etc/environment
I have to manually add them back each time after the rpm updated as my servers are behind a proxy.
Or should a request be logged on the snapd github?
Hi,
Can you please improve on the systemd service by adding
EnvironmentFile=-/etc/environment
I have to manually add them back each time after the rpm updated as my servers are behind a proxy.
Or should a request be logged on the snapd github?
The packages use /etc/sysconfig/snapd which is what is expected of any package coming from Fedora/EPEL. The packages provided in the repository are a rebuild of what is available in EPEL, but with SELinux disabled (as Amazon’s own repositories provide outdated versions of selinux policy). I intend to keep them as close as possible to what is in EPEL.
As an admin you can drop a *.conf
override file in /etc/systemd/system/snapd.service.d/
directory with the following content:
[Service]
Environment=-/etc/environment
Which also means you don’t have to edit anything after updating the packages.
Thank you! This works great!
@mborzecki Is the repo for AMZN2 being continuously updated? Last updated was in November last year.
Yes, I’ll be pushing the update to 2.54.3 soon.
Sorry for the delay. The 2.54.3 packages have been uploaded.
Hi,
I am using Amazon Linux 2 (aarch64) on Amazon EC2, and have downloaded the latest SRPM from the repository here:
And then I tried to install dependencies with:
sudo yum-builddep snapd-2.54.3-1.amzn2.1.src.rpm
After that, I tried building with:
rpmbuild --rebuild snapd-2.54.3-1.amzn2.1.src.rpm
But it failed with:
Installing snapd-2.54.3-1.amzn2.1.src.rpm
error: Failed build dependencies:
compiler(go-compiler) is needed by snapd-2.54.3-1.amzn2.1.aarch64
Before installing dependencies, there were much more lines than this. After installing dependencies, there is still one line. It seems that yum-builddep
cannot solve this dependency automatically.
What can I do?
Hello I tried to add the repo to the repo list and I got this below error:
(people.canonical.com)|185.125.188.97|:443… connected. HTTP request sent, awaiting response… 404 Not Found 2022-07-22 16:43:21 ERROR 404: Not Found.
Is this being updated anymore since @mborzeki is no longer working for Canonical? Recent Amazon Linux updates have broken snap…
I can try an take a look, but most likely over the weekend.
I’m having trouble following all the jargon and short descriptions. I am new to Linux. I wanted to use tesseract to get some text from my pdf and so I got a Amazon Workspaces account. Running Linux 2 like people here I think. I needed Snap to get tesseract because of other issues. Now I’m here.
I get the same error that everyone is talking about but can’t keep up with the solution. Can I get a simple step by step of what I need to put in Linux terminal to be able to get snapd?
Hi @mborzecki1,
Did you have any luck with this, I’m also receiving that annoying error and I need it for the Amazon Workspaces:
error: Failed build dependencies: compiler(go-compiler) is needed by snapd-2.36.3-0.amzn2.x86_64
Thanks!
Hi @mborzecki1,
Seems https://people.canonical.com is down for repos.
https://people.canonical.com/%7Emvo/snapd/amazon-linux2/repo/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Was the repo deprecated or moved?
@faramirza I’m no longer with Canonical, and AFAIK @mvo under whose account the repository was published has also left.
I think @Igor @pedronis are still around and maybe they can move the repository to a different location such that the packages are publicly available and not tied to any particular account at p.c.c.
Just to be clear, if your business depends on having snapd available, it’s best to reach out to Amazon and request package inclusion into a separate extras library.
Looks like someone attempted to submit a request to add it to Amazon Linux 2022. Looks like they won’t be adding it to Amazon Linux 2023 either…
https://github.com/amazonlinux/amazon-linux-2023/issues/248#issuecomment-1740119321
It’s a nice to have, but at least for me it’s not a mission critical item. Then again, it would be nice to have the build process/code available on Github so someone can continue building it…
I’m not sure I understand your comment. The specs have always been there, it’s not like the packages were built from some secret source tree. Everything’s is in this repository: https://github.com/bboozzoo/snapd-amazon-linux.
Never said it was secret. Just wanted to confirm the patches and build process were out there. That’s all.
The package repository is available at a new location, please see the following topic for details: