Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Jun 2024 20:30:10 -0700
From:      Yuri <yuri@FreeBSD.org>
To:        Tatsuki Makino <tatsuki_makino@hotmail.com>, "ports@freebsd.org" <ports@freebsd.org>
Subject:   Re: After following the advise from UPDATING about pythoin-3.11, 'pkg add' now says: pkg: "Cannot solve problem using SAT solver" and attempts to install and then offers to remove py39- packages
Message-ID:  <187dec33-ae28-435b-9dce-04968da0a45d@FreeBSD.org>
In-Reply-To: <SI2PR01MB50369A901B50909246BC3AADFAC42@SI2PR01MB5036.apcprd01.prod.exchangelabs.com>
References:  <b9d28cb8-4071-4d16-9e5b-54b833fe65e8@FreeBSD.org> <SI2PR01MB50369A901B50909246BC3AADFAC42@SI2PR01MB5036.apcprd01.prod.exchangelabs.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------U7fiEDLlMl382xu51vb0Vk2n
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello,


On 6/8/24 14:24, Tatsuki Makino wrote:
> I feel that there is a slight possibility that this upgrade may 
> include the following issues. ( echo py39-foo ; echo py311-foo ) | sort


You are right. Package DB contains both py39- and py311- packages:
$ pkg search py311- | wc
    4477   33240  346412
$ pkg search py39- | wc
    3506   25946  270059

Since pkg has no awareness of the current python version - it attempts 
to install all found candidates for each particular PKGORIGIN.


Anybody knows what caused this regression in the package database?


Thanks,
Yuri
--------------U7fiEDLlMl382xu51vb0Vk2n
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix"><font face="monospace">Hello,</font></div>
    <div class="moz-cite-prefix"><font face="monospace"><br>
      </font></div>
    <div class="moz-cite-prefix"><font face="monospace"><br>
      </font></div>
    <div class="moz-cite-prefix"><font face="monospace">On 6/8/24 14:24,
        Tatsuki Makino wrote:<br>
      </font></div>
    <blockquote type="cite"
cite="mid:SI2PR01MB50369A901B50909246BC3AADFAC42@SI2PR01MB5036.apcprd01.prod.exchangelabs.com">I
      feel that there is a slight possibility that this upgrade may
      include the following issues.
      ( echo py39-foo ; echo py311-foo ) | sort</blockquote>
    <font face="monospace"><br>
    </font><br>
    <font face="monospace">You are right. Package DB contains both py39-
      and py311- packages:</font><br>
    <font face="monospace"><span
        style="color:#000000;background-color:#ffffff;">$ pkg search
        py311- | wc
      </span><br>
         4477   33240  346412
      <br>
      $ pkg search py39- | wc
      <br>
         3506   25946  270059<br>
    </font>
    <font face="monospace"><br>
      Since pkg has no awareness of the current python version - it
      attempts to install all found candidates for each particular
      PKGORIGIN.</font><br>
    <font face="monospace"><br>
    </font><br>
    <font face="monospace">Anybody knows what caused this regression in
      the package database?</font><br>
    <font face="monospace"><br>
    </font><br>
    <font face="monospace">Thanks,</font><br>
    <font face="monospace">Yuri<br>
    </font>
  </body>
</html>

--------------U7fiEDLlMl382xu51vb0Vk2n--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?187dec33-ae28-435b-9dce-04968da0a45d>