Just this afternoon around 4PM I started noticing this happen in my Docker
builds that incorporate loading the Puppet agent:
W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
component 'puppet' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
component 'puppet' (component misspelt in sources.list?)
Reading package lists...
Building dependency tree...
Reading state information...
Package puppet-agent is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'puppet-agent' has no installation candidate

same Docker build worked swimmingly earlier today and seems broken now with
NOTHING changing in the build (except to add NTP).  Any idea why this is
happening and more importantly any idea when the issue will go away?



-- 

Peter L. Berghold                       salty.cowd...@gmail.com

http://devops.berghold.net

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to