Internal conflict between python-3.7.3p0 and python-3.5.3

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Internal conflict between python-3.7.3p0 and python-3.5.3

Laurence Tratt
When I ran "pkg_add -Dsnap -u" earlier I was greeted with screen after
screen of output along the lines of:

  Can't install shared-mime-info-1.10p5 because of libraries
  |library glib-2.0.4201.2 not found
  | /usr/local/lib/libglib-2.0.so.4201.1 (glib2-2.58.3p8): minor is too small
  Direct dependencies for shared-mime-info-1.10p5->1.10p5 resolve to libxml-2.9.8p1 glib2-2.58.3p8
  Full dependency tree is sqlite3-3.27.2p0 gettext-0.19.8.1p3 glib2-2.58.3p8 libffi-3.2.1p5 python-3.6.8p0 bzip2-1.0.6p9 libxml-2.9.8p1 xz-5.2.4 pcre-8.41p2 libiconv-1.14p3
  Can't install gdk-pixbuf-2.38.1 because of libraries
  |library gio-2.0.4200.9 not found
  | /usr/local/lib/libgio-2.0.so.4200.8 (glib2-2.58.3p8): minor is too small
  |library gmodule-2.0.4200.9 not found
  | /usr/local/lib/libgmodule-2.0.so.4200.8 (glib2-2.58.3p8): minor is too small
  |library gobject-2.0.4200.9 not found
  | /usr/local/lib/libgobject-2.0.so.4200.8 (glib2-2.58.3p8): minor is too small
  Direct dependencies for gdk-pixbuf-2.38.1->2.38.1 resolve to png-1.6.37 tiff-4.0.10 glib2-2.58.3p8 jasper-2.0.14 shared-mime-info-1.10p5
  Full dependency tree is libiconv-1.14p3 python-3.6.8p0 bzip2-1.0.6p9 pcre-8.41p2 jpeg-2.0.2v0 jasper-2.0.14 glib2-2.58.3p8 shared-mime-info-1.10p5 tiff-4.0.10 png-1.6.37 libxml-2.9.8p1 xz-5.2.4 gettext-0.19.8.1p3 libffi-3.2.1p5 sqlite3-3.27.2p0
  ...

and so on. Virtually no packages appeared to update themselves. Confused, I
tried "pkg_delete -a", and reran pkg_add, but the same problem reoccurred.
Running it again I noticed a tiny line at the very beginning that seemed to
contain a clue:

  $ doas pkg_add -u -Dsnap
  quirks-3.142 signed on 2019-05-07T18:36:32Z
  [python-3.5.3]python-3.6.8p0->python-3.6.8p2+python-3.7.3p0: internal conflict between python-3.7.3p0 and python-3.5.3
  Can't install glib2-2.58.3p8->2.60.2: can't resolve python-3.7.3p0
  ...

After running "pkg_delete python-3.5.3" (upon which nothing seemed to
depend), "pkg_add -Dsnap -u" then worked fine. So it seems that the presence
of the python-3.5.3 package a) stopped pkg_add -u being able to do anything
useful b) caused it to keep trying to update packages even though it
couldn't (and obscuring the real source of the error). Unfortunately I
didn't think to save the state of my packages before this, so I can't easily
replicate my setup :/


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Remi Pointel
Le 10-05-2019 09:29, Laurence Tratt a écrit :

> When I ran "pkg_add -Dsnap -u" earlier I was greeted with screen after
> screen of output along the lines of:
>
>   Can't install shared-mime-info-1.10p5 because of libraries
>   |library glib-2.0.4201.2 not found
>   | /usr/local/lib/libglib-2.0.so.4201.1 (glib2-2.58.3p8): minor is too
> small
>   Direct dependencies for shared-mime-info-1.10p5->1.10p5 resolve to
> libxml-2.9.8p1 glib2-2.58.3p8
>   Full dependency tree is sqlite3-3.27.2p0 gettext-0.19.8.1p3
> glib2-2.58.3p8 libffi-3.2.1p5 python-3.6.8p0 bzip2-1.0.6p9
> libxml-2.9.8p1 xz-5.2.4 pcre-8.41p2 libiconv-1.14p3
>   Can't install gdk-pixbuf-2.38.1 because of libraries
>   |library gio-2.0.4200.9 not found
>   | /usr/local/lib/libgio-2.0.so.4200.8 (glib2-2.58.3p8): minor is too
> small
>   |library gmodule-2.0.4200.9 not found
>   | /usr/local/lib/libgmodule-2.0.so.4200.8 (glib2-2.58.3p8): minor is
> too small
>   |library gobject-2.0.4200.9 not found
>   | /usr/local/lib/libgobject-2.0.so.4200.8 (glib2-2.58.3p8): minor is
> too small
>   Direct dependencies for gdk-pixbuf-2.38.1->2.38.1 resolve to
> png-1.6.37 tiff-4.0.10 glib2-2.58.3p8 jasper-2.0.14
> shared-mime-info-1.10p5
>   Full dependency tree is libiconv-1.14p3 python-3.6.8p0 bzip2-1.0.6p9
> pcre-8.41p2 jpeg-2.0.2v0 jasper-2.0.14 glib2-2.58.3p8
> shared-mime-info-1.10p5 tiff-4.0.10 png-1.6.37 libxml-2.9.8p1 xz-5.2.4
> gettext-0.19.8.1p3 libffi-3.2.1p5 sqlite3-3.27.2p0
>   ...
>
> and so on. Virtually no packages appeared to update themselves.
> Confused, I
> tried "pkg_delete -a", and reran pkg_add, but the same problem
> reoccurred.
> Running it again I noticed a tiny line at the very beginning that
> seemed to
> contain a clue:
>
>   $ doas pkg_add -u -Dsnap
>   quirks-3.142 signed on 2019-05-07T18:36:32Z
>   [python-3.5.3]python-3.6.8p0->python-3.6.8p2+python-3.7.3p0:
> internal conflict between python-3.7.3p0 and python-3.5.3
>   Can't install glib2-2.58.3p8->2.60.2: can't resolve python-3.7.3p0
>   ...
>
> After running "pkg_delete python-3.5.3" (upon which nothing seemed to
> depend), "pkg_add -Dsnap -u" then worked fine. So it seems that the
> presence
> of the python-3.5.3 package a) stopped pkg_add -u being able to do
> anything
> useful b) caused it to keep trying to update packages even though it
> couldn't (and obscuring the real source of the error). Unfortunately I
> didn't think to save the state of my packages before this, so I can't
> easily
> replicate my setup :/
>

Hi,

On which version of OpenBSD are you trying to update your packages?

Have you read this page to understand how to follow -current
http://www.openbsd.org/faq/current.html?

Cheers,

Remi.

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Laurence Tratt
On Fri, May 10, 2019 at 10:56:43AM +0200, Remi Pointel wrote:

Hello Remi,

> On which version of OpenBSD are you trying to update your packages?

Apologies for not being clear. This was on the May 9th snapshot.


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Remi Pointel
Le 10-05-2019 11:44, Laurence Tratt a écrit :
> On Fri, May 10, 2019 at 10:56:43AM +0200, Remi Pointel wrote:
>
> Hello Remi,
>
>> On which version of OpenBSD are you trying to update your packages?
>
> Apologies for not being clear. This was on the May 9th snapshot.
>

Python-3.5.x has been removed since OpenBSD 6.1, I think you are trying
to update a very old OpenBSD-current.

You could test this after reading
https://www.openbsd.org/faq/faq15.html:

- list all packages installed in a file "list"
$ pkg_info -mz | tee list

- remove all packages installed:
$ doas pkg_delete -X

- install all packages from the first step:
$ doas pkg_add -l list

Cheers,

Remi.

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Stuart Henderson
On 2019/05/10 13:49, Remi Pointel wrote:

> Le 10-05-2019 11:44, Laurence Tratt a écrit :
> > On Fri, May 10, 2019 at 10:56:43AM +0200, Remi Pointel wrote:
> >
> > Hello Remi,
> >
> > > On which version of OpenBSD are you trying to update your packages?
> >
> > Apologies for not being clear. This was on the May 9th snapshot.
> >
>
> Python-3.5.x has been removed since OpenBSD 6.1, I think you are trying to
> update a very old OpenBSD-current.
>
> You could test this after reading https://www.openbsd.org/faq/faq15.html:
>
> - list all packages installed in a file "list"
> $ pkg_info -mz | tee list
>
> - remove all packages installed:
> $ doas pkg_delete -X
>
> - install all packages from the first step:
> $ doas pkg_add -l list
>
> Cheers,
>
> Remi.
>

This was because @pkgpath markers were wrong in the ports, 3.5 should
have been merged into a newer version when it was removed, but that
wasn't done so old packages would stick around.

I've fixed the ports now but the simple fix if you don't want to wait
for a new pkg snapshot is "pkg_delete /var/db/pkg/python*3.5.*"

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Remi Pointel
Le 10-05-2019 14:03, Stuart Henderson a écrit :

> On 2019/05/10 13:49, Remi Pointel wrote:
>> Le 10-05-2019 11:44, Laurence Tratt a écrit :
>> > On Fri, May 10, 2019 at 10:56:43AM +0200, Remi Pointel wrote:
>> >
>> > Hello Remi,
>> >
>> > > On which version of OpenBSD are you trying to update your packages?
>> >
>> > Apologies for not being clear. This was on the May 9th snapshot.
>> >
>>
>> Python-3.5.x has been removed since OpenBSD 6.1, I think you are
>> trying to
>> update a very old OpenBSD-current.
>>
>> You could test this after reading
>> https://www.openbsd.org/faq/faq15.html:
>>
>> - list all packages installed in a file "list"
>> $ pkg_info -mz | tee list
>>
>> - remove all packages installed:
>> $ doas pkg_delete -X
>>
>> - install all packages from the first step:
>> $ doas pkg_add -l list
>>
>> Cheers,
>>
>> Remi.
>>
>
> This was because @pkgpath markers were wrong in the ports, 3.5 should
> have been merged into a newer version when it was removed, but that
> wasn't done so old packages would stick around.
>
> I've fixed the ports now but the simple fix if you don't want to wait
> for a new pkg snapshot is "pkg_delete /var/db/pkg/python*3.5.*"

Good catch, thank you.

Remi.

Reply | Threaded
Open this post in threaded view
|

Re: Internal conflict between python-3.7.3p0 and python-3.5.3

Laurence Tratt
In reply to this post by Stuart Henderson
On Fri, May 10, 2019 at 01:03:47PM +0100, Stuart Henderson wrote:

> This was because @pkgpath markers were wrong in the ports, 3.5 should have
> been merged into a newer version when it was removed, but that wasn't done
> so old packages would stick around.

Thanks Stuart!


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt