On 14.07.2018 22:01, Andreas Beckmann wrote:
Followup-For: Bug #901001
Hi,
are there known upgrade problems related to this bug when upgrading
from jessie to stretch (python 3.4 -> 3.5) or could we tag this bug
as 'sid buster'?
It's the same, but maybe not seen that frequently as the populari
Followup-For: Bug #901001
Hi,
are there known upgrade problems related to this bug when upgrading
from jessie to stretch (python 3.4 -> 3.5) or could we tag this bug
as 'sid buster'?
Andreas
On Sat, Jun 09, 2018 at 06:39:19PM +0200, Matthias Klose wrote:
> On 09.06.2018 18:31, Matthias Klose wrote:
> > On 09.06.2018 11:55, Philipp Kern wrote:
> > > On 6/9/18 7:20 AM, Steve Langasek wrote:
> > > > - the package is being upgraded; it is in the common case (when no
> > > > python
> > > >
On 09.06.2018 18:31, Matthias Klose wrote:
On 09.06.2018 11:55, Philipp Kern wrote:
On 6/9/18 7:20 AM, Steve Langasek wrote:
- the package is being upgraded; it is in the common case (when no python
module names have been dropped from within the package) less important to
run py3clean bec
On 09.06.2018 11:55, Philipp Kern wrote:
On 6/9/18 7:20 AM, Steve Langasek wrote:
- the package is being upgraded; it is in the common case (when no python
module names have been dropped from within the package) less important to
run py3clean because the same files will be recreated shortl
On 6/9/18 7:20 AM, Steve Langasek wrote:
> - the package is being upgraded; it is in the common case (when no python
> module names have been dropped from within the package) less important to
> run py3clean because the same files will be recreated shortly afterwards
> by py3compile from the
On Thu, Jun 07, 2018 at 03:00:46PM -0700, Julian Andres Klode wrote:
> Package: python3-default
> Severity: serious
> When python3 default version changes, and a new python3-minimal is
> unpacked before its python3.N-minimal, we end up with a system without a
> working python3 symlink. This break
Control: reassign -1 src:python3-defaults,src:dh-python
I'm not sure, if the pre-dependency is the correct solution (or the only
solution). To run py3clean/py3compile, you need any python3.X package unpacked.
So a possible solution could be to make py3clean/py3compile shell scripts,
which tr
Package: python3-default
Severity: serious
When python3 default version changes, and a new python3-minimal is unpacked
before its
python3.N-minimal, we end up with a system without a working python3 symlink.
This breaks
upgrades because prerm scripts of python3 packages use:
if which py3clean >
9 matches
Mail list logo
