On Fri, Apr 28, 2023 at 08:42:07PM +0100, Peter Green wrote:
> On 28/04/2023 18:58, Fabian Grünbichler wrote:
> > I see no practical issue with 2 meaning we can't have multiple semver
> > suffix packages variants of a single crate installed - having the
> > unversioned and one semver suffix
On Fri, Apr 28, 2023 at 07:58:35PM +0200, Fabian Grünbichler wrote:
> 2) if the "fork point" corresponds to the version in the soon-to-be-old
> stable release, and the semver suffix package is still in testing when
> that becomes the stable release (as then the unversioned package in
> (old)stable
as reference, the (simplified) problematic combination:
rust-foobar in version X.Y.Z-A
ships librust-foobar-dev which provides librust-foobar-X-dev,
librust-foobar-X.Y-dev and librust-foobar-X.Y.Z-dev (all in version
X.Y.Z-A)
is what I call the "unversioned" package in the rest of this mail (it
On 28/04/2023 06:05, Helmut Grohne wrote:
Can you go into more detail as to what you mean with "don't support
version ranges"?
You can place a lower bound on the version, place an upper bound
on the version or constrain to a precise version. But you can't
constrain to a range of versions.
Hi Peter,
On Fri, Apr 28, 2023 at 01:24:16AM +0100, Peter Green wrote:
> Summarising a number of bug reports by Helmut Ghrone:
>
> > Please ensure that librust---dev has sufficient Breaks and
> > Replaces declarations.
>
> The issue specifically appears to be that the breaks+replaces are
Summarising a number of bug reports by Helmut Ghrone:
Please ensure that librust---dev has sufficient Breaks and
Replaces declarations.
The issue specifically appears to be that the breaks+replaces are declared
against a virtual package, it seems dpkg is honoring the breaks against the
6 matches
Mail list logo