1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1100302: ros2-colcon-python-setup-py: FTBFS: ImportError: cannot im

    From Santiago Vila@21:1/5 to All on Wed Mar 12 17:40:13 2025
    Package: src:ros2-colcon-python-setup-py
    Version: 0.2.9-1
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

    During a rebuild of all packages in unstable, your package failed to build:

    --------------------------------------------------------------------------------
    [...]
    debian/rules clean
    dh clean --buildsystem pybuild
    dh_auto_clean -O--buildsystem=pybuild
    I: pybuild base:311: python3.13 setup.py clean
    Traceback (most recent call last):
    File "/<<PKGBUILDDIR>>/setup.py", line 4, in <module>
    from setuptools import setup
    ImportError: cannot import name 'setup' from 'setuptools' (unknown location)
    E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1: python3.13 setup.py clean
    dh_auto_clean: error: pybuild --clean -i python{version} -p 3.13 returned exit code 13
    make: *** [debian/rules:6: clean] Error 25
    dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/202503/

    About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:ros2-colcon-python-setup-py, so that this is still
    visible in the BTS web page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jochen Sprickerhof@21:1/5 to All on Thu Apr 3 12:00:01 2025
    Control: tag -1 pending

    Hello,

    Bug #1100302 in ros2-colcon-python-setup-py reported by you has been fixed in the
    Git repository and is awaiting an upload. You can see the commit
    message below and you can check the diff of the fix at:

    https://salsa.debian.org/robotics-team/ros2-colcon-python-setup-py/-/commit/2f753edd1f4a183e3f41e5cc14e6c7090edf6cf6

    ------------------------------------------------------------------------ Explicitly depend on python3-setuptools

    Closes: #1083751, #1100302 ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1100302

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Apr 3 12:00:01 2025
    Processing control commands:

    tag -1 pending
    Bug #1100302 [src:ros2-colcon-python-setup-py] ros2-colcon-python-setup-py: FTBFS: ImportError: cannot import name 'setup' from 'setuptools' (unknown location)
    Added tag(s) pending.

    --
    1100302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100302
    Debian Bug Tracking System
    Contact [email protected] with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Apr 3 12:10:02 2025
    This is a multi-part message in MIME format...

    Your message dated Thu, 03 Apr 2025 10:07:03 +0000
    with message-id <[email protected]>
    and subject line Bug#1100302: fixed in ros2-colcon-python-setup-py 0.2.9-2
    has caused the Debian Bug report #1100302,
    regarding ros2-colcon-python-setup-py: FTBFS: ImportError: cannot import name 'setup' from 'setuptools' (unknown location)
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected]
    immediately.)


    --
    1100302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100302
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 12 Mar 2025 16:33:54 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-120.1 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,
    RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_NONE,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 150; neutral, 80; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--H*F:U*sanvila, 0.000-+--H*rp:U*sanvila Return-path: <[email protected]>
    Received: from mitropoulos.debian.org ([2001:648:2ffc:deb:216