Skip to content
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

apt::source: configure repo only for current architecture #1527

Merged
merged 1 commit into from
Dec 20, 2022

Conversation

bastelfreak
Copy link
Member

Without this setting, we tell apt to download release information for all architectures apt knows. This includes i386 on amd64 systems. nginx doesn't publish i386 packages. because of that, it results in a warning during apt update:

N: Skipping acquire of configured file 'nginx/binary-i386/Packages' as repository 'https://nginx.org/packages/ubuntu jammy InRelease' doesn't support architecture 'i386'

This is fixed with this change.

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Without this setting, we tell apt to download release information for
all architectures apt knows. This includes i386 on amd64 systems. nginx
doesn't publish i386 packages. because of that, it results in a warning
during apt update:

N: Skipping acquire of configured file 'nginx/binary-i386/Packages' as
repository 'https://nginx.org/packages/ubuntu jammy InRelease' doesn't
support architecture 'i386'

This is fixed with this change.
@bastelfreak bastelfreak added the bug Something isn't working label Dec 20, 2022
@bastelfreak bastelfreak self-assigned this Dec 20, 2022
@puppet-community-rangefinder
Copy link

nginx::package::debian is a class

that may have no external impact to Forge modules.

This module is declared in 9 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@bastelfreak
Copy link
Member Author

This will look like:

Notice: /Stage[main]/Nginx::Package::Debian/Apt::Source[nginx]/Apt::Setting[list-nginx]/File[/etc/apt/sources.list.d/nginx.list]/content:
--- /etc/apt/sources.list.d/nginx.list	2022-12-20 10:44:43.029009469 +0100
+++ /tmp/puppet-file20221220-1147919-1fj17e7	2022-12-20 10:45:04.640920139 +0100
@@ -1,3 +1,3 @@
 # This file is managed by Puppet. DO NOT EDIT.
 # nginx
-deb https://nginx.org/packages/ubuntu jammy nginx
+deb [arch=amd64] https://nginx.org/packages/ubuntu jammy nginx

Notice: /Stage[main]/Nginx::Package::Debian/Apt::Source[nginx]/Apt::Setting[list-nginx]/File[/etc/apt/sources.list.d/nginx.list]/content: current_value '{sha256}827157dcc30574434a3993b56d28624f144469d9e55d7749aaa6aad338ee5749', should be '{sha256}bd83793d6907c903d5701add41c2f046bf70300f8d3c8590523dd6ccc6decef6' (noop)
Notice: Apt::Setting[list-nginx]: Would have triggered 'refresh' from 1 event
Notice: Apt::Source[nginx]: Would have triggered 'refresh' from 1 event

@bastelfreak bastelfreak merged commit e5f14db into voxpupuli:master Dec 20, 2022
@smortex
Copy link
Member

smortex commented Dec 20, 2022

Without this setting, we tell apt to download release information for all architectures apt knows.

"apt knows" or "apt is configured to use" 😉. I had similar "issue" at a customer running Ubuntu, and preferred to dpkg --remove-architecture i386 because that made no sense on their system.

They could not say if the added it or if Ubuntu was shipping with this by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants