toremove' cleaned up further. I finally could upgrade the still marked
for hold package python3-chardet, which removed the python-chardet
package, could let follow another 'apt autoremove", and the original
problem of this thread "package python3-chardet breaks package
p
On Jo, 14 mai 20, 11:40:51, Marco Möller wrote:
> On 14.05.20 08:36, Andrei POPESCU wrote:
> > On Mi, 13 mai 20, 17:40:45, Marco Möller wrote:
> > > Unfortunately I now see that there are already many packages from /sid
> > > residing in my supposed to be /testing installation. FrankenDebian
> > >
On 14.05.20 08:36, Andrei POPESCU wrote:
On Mi, 13 mai 20, 17:40:45, Marco Möller wrote:
Unfortunately I now see that there are already many packages from /sid
residing in my supposed to be /testing installation. FrankenDebian detected.
This might happen if the package has the same version in
On Mi, 13 mai 20, 17:40:45, Marco Möller wrote:
> Unfortunately I now see that there are already many packages from /sid
> residing in my supposed to be /testing installation. FrankenDebian detected.
This might happen if the package has the same version in testing as in
unstable. 'apt list ' is c
On 13.05.20 16:23, Marco Möller wrote:
As package python3-chardet defines to break package python-chardet, I
cannot upgrade python3-chardet because I am still very satisfied using
software "cherrytree" which depends on python-chardet. My finding is,
that I would have to remove python-chardet, w
As package python3-chardet defines to break package python-chardet, I
cannot upgrade python3-chardet because I am still very satisfied using
software "cherrytree" which depends on python-chardet. My finding is,
that I would have to remove python-chardet, which subsequently would
also remove che
6 matches
Mail list logo