On 2020-08-07 14:08 +0200, Harald Dunkel wrote:
> On 8/5/20 6:29 PM, Sven Joachim wrote:
>> I am not sure I understand what you actually want to do, though.
>>
>
> I am maintaining a set of meta packages, referencing the packages
> to install on my hosts. To avoid having separate meta packages
On 8/5/20 6:29 PM, Sven Joachim wrote:
I am not sure I understand what you actually want to do, though.
I am maintaining a set of meta packages, referencing the packages
to install on my hosts. To avoid having separate meta packages for
each new Debian version I have to use conditional
Hello,
perhaps options described here could help you:
https://www.debian.org/doc/manuals/aptitude/ch02s05s05.en.html
On 2020-08-05 12:33 +0200, Harald Dunkel wrote:
> On 8/5/20 11:03 AM, Sven Joachim wrote:
>> I am surprised to read that, considering that your installed lxc
>> version
>> does not actually fulfill the dependency. Note the epoch.
>> $ dpkg --compare-versions 1:2.0.11-1~xgo90+1 lt 3 || echo 'Got
On 8/5/20 11:03 AM, Sven Joachim wrote:
I am surprised to read that, considering that your installed lxc version
does not actually fulfill the dependency. Note the epoch.
$ dpkg --compare-versions 1:2.0.11-1~xgo90+1 lt 3 || echo 'Got it!'
Got it!
Maintaining the sample-lxc package I have
On 2020-08-05 09:42 +0200, Harald Dunkel wrote:
> I've got a problem with upgrading a private package in Stretch. The control
> file says:
>
> Package: sample-lxc
> Architecture: all
> Depends: ${misc:Depends}
> , cgmanager | systemd
> , debootstrap
>
6 matches
Mail list logo
