On Tue, Sep 18, 2018 at 10:45:45AM +0200, Ondrej Novy wrote:
> Hi,
>
> út 18. 9. 2018 v 10:30 odesílatel Lars Wirzenius napsal:
>
> Would Conflicts work here?
>
>
> Conflicts is just more strict Breaks,
Eh, no.
> for example when files are overwritten. This is not case and Breaks
> "is e
On Wed, 2018-09-19 at 10:07 +0200, Wouter Verhelst wrote:
> On Tue, Sep 18, 2018 at 10:45:45AM +0200, Ondrej Novy wrote:
> > for example when files are overwritten. This is not case and Breaks
> > "is enough".
>
> "Breaks" means "will cause the other package to fail". That isn't the
> case here. A
Hi,
st 19. 9. 2018 v 13:21 odesílatel Ansgar Burchardt
napsal:
> Policy specifically says to use Breaks in this case: "Breaks should be
> used [...] when the breaking package exposes a bug in or interacts
> badly with particular versions of the broken package." (same section as
> above)
>
accor
Hi,
st 19. 9. 2018 v 10:07 odesílatel Wouter Verhelst
napsal:
> > Conflicts is just more strict Breaks,
>
> Eh, no.
>
ehm, yes: 7.4: Conflicts ... This is a stronger restriction than Breaks
You're claiming that the systemd support of your package won't work
> correctly unless you have a partic
Package: wnpp
Severity: wishlist
Owner: Jochen Sprickerhof
* Package name: python-pcl
Version : 0.3.0rc1
Upstream Author : John Stowers
* URL : https://strawlab.github.io/python-pcl/
* License : BSD-3-Clause
Programming Lang: Python
Description : Pytho
On Wed, Sep 19, 2018 at 9:12 AM Ondrej Novy wrote:
> but I want my package to work without init systems, for example inside
> Docker. But if systemd is installed, I need >= version.
I think I had a much simpler situation with chrome-gnome-shell.
According to upstream, Firefox older than 56 is no
6 matches
Mail list logo
