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.

Sign up for GitHub

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

Jump to bottom

apt::setting expects priority to be an integer, set defaults accordingly #602

Merged
merged 1 commit into from
Apr 19, 2016
Merged

apt::setting expects priority to be an integer, set defaults accordingly #602

merged 1 commit into from
Apr 19, 2016

Conversation

madddi
Copy link

@madddi madddi commented Apr 19, 2016

Using apt::pin without specifying order results in:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: apt::setting priority must be an integer or a zero-padded integer on node

The same thing happens when using apt::conf with the default priority.

@madddi
apt::setting expects priority to be an integer, set defaults accordingly
e5d5123 
Signed-off-by: Mathias Merscher <Mathias.Merscher@dg-i.net>
@daenney daenney mentioned this pull request Apr 19, 2016
Closed
@DavidS DavidS merged commit e992538 into puppetlabs:master Apr 19, 2016
@DavidS
Copy link

DavidS commented Apr 19, 2016

Thanks!

@LukasAud LukasAud added the bugfix label Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bugfix
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@madddi @DavidS @LukasAud