On Mon 01 Jul 2019 at 13:45:30 (+), Fabian peter Hammerle wrote:
> > Presumably by employing the same method that linux-image uses:
> > by moving/copying the version number into the packages' names,
> > foo-1 and foo-2.
>
> Thanks for your suggestion
>
> We are using CI/CD pipelines that depl
Hi David,
> Presumably by employing the same method that linux-image uses:
> by moving/copying the version number into the packages' names,
> foo-1 and foo-2.
Thanks for your suggestion
We are using CI/CD pipelines that deploy multiple versions / debian packages
per day.
So appending version s
On Mon 01 Jul 2019 at 07:32:20 (+), Fabian peter Hammerle wrote:
> I set up an APT repository containing 2 packages: foo and bar
>
> The repository contains 2 versions of foo: 1.0.0 and 2.0.0
> and 2 versions of bar: 3.0.0 and 4.0.0
>
> foo 1.0.0 depends on bar 3.0.0
> foo 2.0.0 depends on ba
Hi Tomás,
Thank you very much for suggesting `--allow-downgrades` and your additional
explanations.
Unfortunately, I get the same error as before:
```
$ sudo apt-get install --allow-downgrades foo=1.0.0
Reading package lists... Done
Building dependency tree
Reading state information... Do
On Mon, Jul 01, 2019 at 07:32:20AM +, Fabian peter Hammerle wrote:
> Dear Debian Users,
>
> I set up an APT repository containing 2 packages: foo and bar
>
> The repository contains 2 versions of foo: 1.0.0 and 2.0.0
> and 2 versions of bar: 3.0.0 and 4.0.0
[...]
> I get the same result whe
Dear Debian Users,
I set up an APT repository containing 2 packages: foo and bar
The repository contains 2 versions of foo: 1.0.0 and 2.0.0
and 2 versions of bar: 3.0.0 and 4.0.0
foo 1.0.0 depends on bar 3.0.0
foo 2.0.0 depends on bar 4.0.0
I can easily install the latest version of foo via
```
6 matches
Mail list logo
