Followup-For: Bug #940012
Control: reopen -1
Control: severity -1 serious
Dropping the Conflicts does not help, since pylint3 is only available as
a cruft package nowadays.
You probably want
Breaks: pylint3
Replaces: pylint3
Provides: pylint3
any maybe even a versioned Provides ...
$ dak rm -R
Hello Sando,
>there's already a "Replaces: pylint3" in pylint the control file, but>there's
>also a "Conflicts: pylint3", which is likely causing the issue
>at hand.
>
>I'll remove the Conflict for the time being, this should prevent all
>this packages to be unbuildable/uninstallable
Problem is
On Wed, Sep 11, 2019 at 3:39 AM Gianfranco Costamagna
wrote:
>
> Source: pylint
> Version 2.2.2-3
> Severity: serious
>
> Hello, I get the pylint renaming as a good thing (yay and thanks!), but you
> currently seems to have broken quite a lot packages...
>
> Do you plan to file RC bugs for them,
Source: pylint
Version 2.2.2-3
Severity: serious
Hello, I get the pylint renaming as a good thing (yay and thanks!), but you
currently seems to have broken quite a lot packages...
Do you plan to file RC bugs for them, or will you revert the change and wait
for them to adapt?
Also, providing the
4 matches
Mail list logo