On Mon, Dec 13, 2010 at 06:44, Adrian Tofan wrote:
> thank you for advice. Unfortunately I didn't managed to do what I planed.
> In fact I tried using Debian pinning which allowed me to upgrade ruby gems
> using the -t option (manualy). -t was needed and I didn't managed to avoid it.
>
> Unfo
Hi everybody,
thank you for advice. Unfortunately I didn't managed to do what I planed. In
fact I tried using Debian pinning which allowed me to upgrade ruby gems using
the -t option (manualy). -t was needed and I didn't managed to avoid it.
Unfortunately Debian's runbgems is highly modified
On Dec 11, 2010, at 11:59 PM, Olivier Le Cam wrote:
> Hi -
>
> On 12/12/10 05:01, Ben wrote:
>>> Is there a way when installing a package like this :
>>>
>>> package { "rubygems":
>>> ensure => installed,
>>> }
>>>
>>> to pass -t parameter to apt-get in order to use a specific apt
>>> source ?
Hi -
On 12/12/10 05:01, Ben wrote:
Is there a way when installing a package like this :
package { "rubygems":
ensure => installed,
}
to pass -t parameter to apt-get in order to use a specific apt
source ? EG : apt-get install -t lenny-backports rubygems
Ideally I would not use exec ...
I my
On 8/12/2010 9:54 PM, Adrian wrote:
Hello everybody,
Is there a way when installing a package like this :
package { "rubygems":
ensure => installed,
}
to pass -t parameter to apt-get in order to use a specific apt
source ? EG : apt-get install -t lenny-backports rubygem
On 09/12/10 19:19, Patrick wrote:
>
> On Dec 9, 2010, at 10:07 AM, Brice Figureau wrote:
>
>> On 09/12/10 03:38, Daniel Pittman wrote:
>>> Sadly, no. I very much missed the feature. We ended up using the apt
>>> preferences file to implement that behaviour
>>>
>>> If I was doing it over I would u
On Dec 9, 2010, at 10:07 AM, Brice Figureau wrote:
> On 09/12/10 03:38, Daniel Pittman wrote:
>> Sadly, no. I very much missed the feature. We ended up using the apt
>> preferences file to implement that behaviour
>>
>> If I was doing it over I would use a define that added the package
>> resour
On 09/12/10 03:38, Daniel Pittman wrote:
> Sadly, no. I very much missed the feature. We ended up using the apt
> preferences file to implement that behaviour
>
> If I was doing it over I would use a define that added the package
> resource and also used concat to automatically build up the prefer
On 08/12/10 10:54, Adrian wrote:
> Hello everybody,
>
>
> Is there a way when installing a package like this :
>
> package { "rubygems":
> ensure => installed,
> }
>
> to pass -t parameter to apt-get in order to use a specific apt
> source ? EG : apt-get install -t lenny-backports
On Dec 8, 2010, at 11:45 PM, Felix Frank wrote:
> On 12/09/2010 05:13 AM, Patrick wrote:
>>
>> On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
>>
>>> Sadly, no. I very much missed the feature. We ended up using the apt
>>> preferences file to implement that behaviour
>>>
>>> If I was doing i
On 12/09/2010 05:13 AM, Patrick wrote:
>
> On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
>
>> Sadly, no. I very much missed the feature. We ended up using the apt
>> preferences file to implement that behaviour
>>
>> If I was doing it over I would use a define that added the package
>> resour
On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
> Sadly, no. I very much missed the feature. We ended up using the apt
> preferences file to implement that behaviour
>
> If I was doing it over I would use a define that added the package resource
> and also used concat to automatically build
Sadly, no. I very much missed the feature. We ended up using the apt
preferences file to implement that behaviour
If I was doing it over I would use a define that added the package resource
and also used concat to automatically build up the preferences entry.
Regards, Daniel.
On 09/12/2010 6:03 A
Hello everybody,
Is there a way when installing a package like this :
package { "rubygems":
ensure => installed,
}
to pass -t parameter to apt-get in order to use a specific apt
source ? EG : apt-get install -t lenny-backports rubygems
Ideally I would not use exec ...
I am
14 matches
Mail list logo
