managing external apt repositories

[Eric]

Hi guys,

I have a server with some apt packages installed from 3rd repositories (mongodb from 10gen, nginx-passenger and others). Does blueprint manages those externals repositories and they're keys or should I use a script to add those repo before applying a blueprint?

Thanks in advance,

Eric

[Eric]

I think I start figuring out how to handle those repositories. Sorry if those questions are kind of "basic".

I'm using a blueprint-rule file to build my blueprint and in there I add the /etc/apt/sources.list.d/*.list to be included as file resources.

What I couldn't do yet is include the gpg files from /etc/apt/trusted.gpg.d/*.gpp in the blueprint. I tried to declare it as file (/etc/apt/trusted.gpg.d/*.gpp) and as a source package (:source:/etc/apt/trusted.gpg.d/) but neither one worked.

I really would like to avoid having to wrap-up my blueprint in shell scripts when applying it because it kind of defeats the purpose of using blueprint as management tool.

Any ideas about how could I do it?

Thanks in advance,

Eric

[Eric]

Just realized I had a type in my blueprint-rules. I typed gpp instead of gpg and that was the reason the gpg keys was not being included. It's working like a charm now!! 

once again congratulations on this awesome tool!!

On Thursday, September 20, 2012 9:23:30 PM UTC-3, Eric wrote:

I think I start figuring out how to handle those repositories. Sorry if those questions are kind of "basic".

I'm using a blueprint-rule file to build my blueprint and in there I add the /etc/apt/sources.list.d/*.list to be included as file resources.

What I couldn't do yet is include the gpg files from /etc/apt/trusted.gpg.d/*.gpg in the blueprint. I tried to declare it as file (/etc/apt/trusted.gpg.d/*.gpp) and as a source package (:source:/etc/apt/trusted.gpg.d/) but neither one worked.

[Richard Crowley]

On Thu, Sep 20, 2012 at 5:23 PM, Eric <er...@craftti.com.br> wrote:
> I think I start figuring out how to handle those repositories. Sorry if
> those questions are kind of "basic".
>
> I'm using a blueprint-rule file to build my blueprint and in there I add the
> /etc/apt/sources.list.d/*.list to be included as file resources.
>
> What I couldn't do yet is include the gpg files from
> /etc/apt/trusted.gpg.d/*.gpp in the blueprint. I tried to declare it as file
> (/etc/apt/trusted.gpg.d/*.gpp) and as a source package
> (:source:/etc/apt/trusted.gpg.d/) but neither one worked.
>
> I really would like to avoid having to wrap-up my blueprint in shell scripts
> when applying it because it kind of defeats the purpose of using blueprint
> as management tool.
>
> Any ideas about how could I do it?

One of the reasons Blueprint places files first is so that APT sources
are in place before `apt-get update` is run and packages are
installed. So you can definitely do this. Using
/etc/apt/sources.list.d and /etc/apt/trusted.gpg.d is exactly how I do
it myself.

This may be a typo but the file extension typically used in
/etc/apt/trusted.gpg.d is *.gpg not *.gpp.

Let me know if the problem persists.

Richard

[Eric]

Hi Richard that was exactly it! thanks!!