Guessing this is related to the archiving of the puppet 4 & older packages?

I note that the yum archive still functions as a repo, but the apt one 
doesn't have any release files (or a dists folder), in spite of otherwise 
being structured appropriately.. Is this going to be fixed? 
(release-archives.puppet.com/apt/)

On Wednesday, May 15, 2019 at 10:06:23 PM UTC+1, Morgan Rhodes wrote:
>
> The bionic repo should be working again. Let us know if you have any more 
> issues.
>
> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes <[email protected] 
> <javascript:>> wrote:
>
>> Hi Peter,
>>
>> Apologies, we've been having some repo issues today. I'm getting the 
>> bionic repository updated now and it should be done within the hour. I will 
>> send another update here when it completes.
>>
>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold <[email protected] 
>> <javascript:>> wrote:
>>
>>> 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                       [email protected] 
>>> <javascript:>
>>>
>>> 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 [email protected] <javascript:>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> Morgan Rhodes
>> Release Engineering
>> [email protected] <javascript:>
>>
>
>
> -- 
> Morgan Rhodes
> Release Engineering
> [email protected] <javascript:>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to