Hi,
On 1/21/24 21:35, Matthias Urlichs wrote:
Now … does that apply to crossing release boundaries? Specifically, if
foo/testing requires bar >=1.1 to work but just states "Depends: bar
>=1", and bar/stable is 1.0.42 … is that a bug? If so which severity?
I'd say yes, with normal severity.
Hi,
On 21-01-2024 16:08, Matthias Urlichs wrote:
However according to our release notes we only support upgrading from
release x to x+1, skipping releases is not allowed.
I'm not talking about skipping releases but about partial upgrades.
Thus …
> foo/testing requires bar >=1.1 to work but
On 2024-01-21 Matthias Urlichs wrote:
> On 21.01.24 15:34, Andreas Metzler wrote:
> > However according to our release notes we only support upgrading from
> > release x to x+1, skipping releases is not allowed.
> I'm not talking about skipping releases but about partial upgrades.
eah, but it
On 21.01.24 15:34, Andreas Metzler wrote:
However according to our release notes we only support upgrading from
release x to x+1, skipping releases is not allowed.
I'm not talking about skipping releases but about partial upgrades.
Thus …
> foo/testing requires bar >=1.1 to work but just
Quoting Matthias Urlichs (2024-01-21 13:35:05)
> question: policy 3.5 states, rather unequivocally,
>
> Every package must specify the dependency information about other
> packages that are required for the first to work correctly.
>
> Now … does that apply to crossing release
On 2024-01-21 Matthias Urlichs wrote:
> question: policy 3.5 states, rather unequivocally,
>Every package must specify the dependency information about other
>packages that are required for the first to work correctly.
> Now … does that apply to crossing release boundaries?
Hi,
question: policy 3.5 states, rather unequivocally,
Every package must specify the dependency information about other
packages that are required for the first to work correctly.
Now … does that apply to crossing release boundaries? Specifically, if
foo/testing requires bar >=1.1 to
7 matches
Mail list logo
