python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

Bug #1862928 reported by Rafael David Tinoco on 2020-02-12
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-crypto (Ubuntu)
Medium
Rafael David Tinoco

Bug Description

If you try:

(c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed
                        Depends: python3:amd64 (>= 3.7~) but it is not going to be installed
                        Depends: libgmp10:amd64 but it is not going to be installed
 python3-samba : Depends: python3-crypto but it is not installable

You won't be able to install python3-crypto.

With a simple rebuild problem goes away.

NOTE: This is needed to fix:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316
(Where I'm getting back winbind to samba on i386)

Changed in python-crypto (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Rafael David Tinoco (rafaeldtinoco)
lotuspsychje (lotuspsychje) wrote :

mine installs on 20.04 devel
but with other warnings:

/usr/lib/python3/dist-packages/Crypto/Random/Fortuna/FortunaGenerator.py:28: Syn
taxWarning: "is" with a literal. Did you mean "=="?
  if sys.version_info[0] is 2 and sys.version_info[1] is 1:
/usr/lib/python3/dist-packages/Crypto/Random/Fortuna/FortunaGenerator.py:28: Syn
taxWarning: "is" with a literal. Did you mean "=="?
  if sys.version_info[0] is 2 and sys.version_info[1] is 1:
/usr/lib/python3/dist-packages/Crypto/SelfTest/Random/test_random.py:107: Syntax
Warning: "is" with a literal. Did you mean "=="?
  if sys.version_info[0] is 3:

Yep, I had those as well, thought it was my dev environmnet. But, if you say yours install fine there is no need for a rebuild.. weird.. I'll re-check here, thank you!

Ah okay, perhaps your environment is amd64 ? I'm testing this in an i386 environmnet (LXD container) only. Still getting:

 python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed
                        Depends: python3:amd64 (>= 3.7~) but it is not going to be installed

I think this relates to having i386 in amd64 installed OSes only currently. Since I'm using a i386 only container, it can't figure out the correct python dependency (asking for amd64). If I build python3-crypto in an i386 container dependencies are correctly figured out.

summary: - python-crypto needs rebuild in Focal (python 3.7 -> python 3.8
+ python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8
dependency refresh)

Steve,

Looks like python3-crypto package is not in the i386 archive.

Judging by:

https://launchpad.net/ubuntu/+source/python-crypto
https://launchpad.net/ubuntu/+source/python-crypto/+publishinghistory
https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2
https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2/+build/17949247

And based on other similar tests (python3-pam also failing in i386 only environment, but some other python3-XXX packages having i386 binary packages available) I would say we need the i386 binary package python3-crypto back in archive to satisfy the needs for:

https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316
(MERGE: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/samba/+git/samba/+merge/378664)

FYI
The ones working seem to be those building as:
  Architecture: all
While the ones you report as failing are:
  Architecture: any

09:43 <cpaelzer> you see that python3-crypto has per-arch deb files
09:43 <rafaeldtinoco> I added a comment in the case and subscribed steve
09:43 <cpaelzer> while your conter-xample of ansi just has one called ..._all.deb
09:43 — rafaeldtinoco checks
09:43 <cpaelzer> AFAICS python3-crypto contains no arch dependent files
09:44 <cpaelzer> so it could be Architecture:all, rebuilt and then it should work
09:44 <cpaelzer> but as I said this is always confusing having an expert like vorlon comment on it sounds the right path forward before we'd do anything wrong
09:46 <rafaeldtinoco> cpaelzer: dh $@ --with=python2,python3 --buildsystem=pybuild
09:46 <cpaelzer> ?
09:46 <rafaeldtinoco> and I could remove python2 from rules also
09:46 <rafaeldtinoco> together with the rebuild
09:47 <rafaeldtinoco> and change Architecture: all
09:47 <cpaelzer> sure, but I thought we only remove those python2 that are blocking anything
09:47 <cpaelzer> we only want to demote to universe or did it change and we want to drop things entriely?
09:48 <cpaelzer> anyway - agreed, it feels almost always right to drop py2 - just sometimes you might cause more work than you solve
09:48 <cpaelzer> think of other dependencies on that and the chain that you need to resolve then for example
09:52 <rafaeldtinoco> yep, i think that is the last one
09:52 <rafaeldtinoco> as I rebuilt it locally and was able to re-enable all needed samba pkgs
09:53 <cpaelzer> your rebuilt gave you an :i386 package
09:53 <rafaeldtinoco> yep
09:53 <cpaelzer> I'd expect that an :all package is even more generic
09:53 <rafaeldtinoco> which the :all might do
09:53 <cpaelzer> I see no need this needs to be per-arch

Steve Langasek (vorlon) wrote :

Does not need a rebuild (which wouldn't have worked anyway), it only needed the i386 binaries resuscitated which is now done.

Changed in python-crypto (Ubuntu):
status: In Progress → Invalid

Thanks Steve!! Package is back to archive, moving on with what needed this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers