On 02/14/2016 12:16 PM, Brendan Simon (eTRIX) wrote:
> The thing is when you are deploying something to lots of sites (e.g. an
> embedded data logger in many remote locations), it's important to know
> exactly what versions you have created and installed, and more
> importantly be able to rebuild t
On 14/02/2016 12:49 AM, Christian Seiler wrote:
> On 02/13/2016 12:12 PM, Brendan Simon wrote:
>> Is there a way to restrict apt to a **specific release** of Jessie.
>> e.g. 8.1, 8.2, 8.3, ... ??
>>
>> I build root filesystems for embedded systems. The sources.list is set
>> to Jessie, but the co
On 14/02/2016 12:07 AM, Andrew M.A. Cater wrote:
> On Sat, Feb 13, 2016 at 10:12:15PM +1100, Brendan Simon wrote:
>> Is there a way to restrict apt to a **specific release** of Jessie.
>> e.g. 8.1, 8.2, 8.3, ... ??
>>
>> I build root filesystems for embedded systems. The sources.list is set
>> to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/02/16 00:12, Brendan Simon wrote:
> Hi,
>
> Is there a way to restrict apt to a **specific release** of Jessie.
> e.g. 8.1, 8.2, 8.3, ... ??
>
> I build root filesystems for embedded systems. The sources.list is
> set to Jessie, but the con
Hi,
On 02/13/2016 12:12 PM, Brendan Simon wrote:
> Is there a way to restrict apt to a **specific release** of Jessie.
> e.g. 8.1, 8.2, 8.3, ... ??
>
> I build root filesystems for embedded systems. The sources.list is set
> to Jessie, but the contents of the generated rootfs can change from on
Hi,
Is there a way to restrict apt to a **specific release** of Jessie.
e.g. 8.1, 8.2, 8.3, ... ??
I build root filesystems for embedded systems. The sources.list is set
to Jessie, but the contents of the generated rootfs can change from one
day to the next if there have been updates. I want t
6 matches
Mail list logo
