Please remove the following email address: e.little...@gmail.com
On Sat, Sep 9, 2023 at 6:51 PM Russ Allbery wrote:
> julien.pu...@gmail.com writes:
>
> > Oh. I think I had two problems:
> > (1) thinking "Replaces" meant "replaces" ;
> > (2) thinking d/control controlled packages.
>
> > Let me
julien.pu...@gmail.com writes:
> Oh. I think I had two problems:
> (1) thinking "Replaces" meant "replaces" ;
> (2) thinking d/control controlled packages.
> Let me try to see if I'm getting at something:
> (*) Replaces doesn't really mean "can be used in place of"
> -- that would be
On Wed, Aug 23, 2023 at 09:22:41AM +0200, julien.pu...@gmail.com wrote:
> Package: debian-policy
> Version: 4.6.2.0
> Severity: normal
>
> Hi,
>
> over at bug #1050027 there is a discussion of applicable policy when
> splitting a package. I'll first explain what the bug is about and then
> why
Hi,
Le mercredi 23 août 2023 à 08:45 +0100, Simon McVittie a écrit :
> No, the central misunderstanding here is that you think Replaces will
> have the effect of instructing dpkg to remove the replaced package
> completely, which is not the case.
Oh. I think I had two problems:
(1) thinking
On Wed, 23 Aug 2023 at 09:22:41 +0200, julien.pu...@gmail.com wrote:
> In src:mathcomp-analysis 0.6.4-2, I declared that libcoq-mathcomp-
> classical Breaks libcoq-mathcomp-analysis (<< 0.6.4) and closed the
> bug. It was swiftly re-opened because I hadn't used Breaks+Replaces
> according to
Package: debian-policy
Version: 4.6.2.0
Severity: normal
Hi,
over at bug #1050027 there is a discussion of applicable policy when
splitting a package. I'll first explain what the bug is about and then
why that's a problem with the Policy.
The src:mathcomp-analysis package provided a single
6 matches
Mail list logo
