Do note, by the way, that the idea appears to be that the Apt module
automatically handles for you what you are trying to do manually: that is,
to ensure that "apt-get update" is automatically run, once, after all Apt
sources are managed, so that your packages can safely express relationships
d
On Friday, May 10, 2013 1:13:32 PM UTC-5, James Kyle wrote:
>
> Wait, this is at the bottom of the modules/apt/manifests/source.pp:
>
> # Need anchor to provide containment for dependencies.
> anchor { "apt::source::${name}":
> require => Class['apt::update'],
> }
>
> Could that do it?
On 10.05.2013 18:13, James Kyle wrote:
I'm sure this has to do with getting updates to run after adding sources
because if I hop on the host and do this:
/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install
libvirt-bin
It reproduces the error. But if I then run 'apt-get update' and
That's what I'm seeing as well, but no idea where it's coming from (tips on
how to run something like that down welcome).
I only have a very few modules I've written myself and like 3 nodes. I've
removed all dependencies declared there except the one above. And I've
grepped the modules directory f
On Friday, May 10, 2013 11:13:03 AM UTC-5, James Kyle wrote:
>
> This is what I get with the above, slightly adapted to take care of an
> edge case:
>
> Apt::Source<| |> -> Exec['apt_update'] -> Package<| title !=
> 'ubuntu-cloud-keyring' |>
>
> The ubuntu-cloud-keyring is a prerequisite for ad
This is what I get with the above, slightly adapted to take care of an edge
case:
Apt::Source<| |> -> Exec['apt_update'] -> Package<| title !=
'ubuntu-cloud-keyring' |>
The ubuntu-cloud-keyring is a prerequisite for adding the ubuntu cloud
archive (for openstack debs). Without this exception, it
This can be achieved without stages if you put the relationship inside
site.pp outside any class scope.
On Friday, May 10, 2013 8:25:58 AM UTC-6, jcbollinger wrote:
>
>
>
> On Thursday, May 9, 2013 10:23:25 PM UTC-5, Nan Liu wrote:
>>
>> On Thu, May 9, 2013 at 11:52 AM, James Kyle wrote:
>>
>>>
On Thursday, May 9, 2013 10:23:25 PM UTC-5, Nan Liu wrote:
>
> On Thu, May 9, 2013 at 11:52 AM, James Kyle
> > wrote:
>
>> I've run into several incidences where a module attempts to install a
>> package before the apt::source is added or an update is run. Result is a
>> bunch apt errors and e
On Thu, May 9, 2013 at 11:52 AM, James Kyle wrote:
> I've run into several incidences where a module attempts to install a
> package before the apt::source is added or an update is run. Result is a
> bunch apt errors and explosions.
>
> Basically what should be done is all the apt::sources are ad
I've run into several incidences where a module attempts to install a
package before the apt::source is added or an update is run. Result is a
bunch apt errors and explosions.
Basically what should be done is all the apt::sources are added and and an
update run _before_ any packages are install
10 matches
Mail list logo
