• Bug#1102287: containerd: FTBFS: cannot use &instrumentedService{...}

    From Santiago Vila@21:1/5 to All on Mon Apr 7 11:50:01 2025
    Package: src:containerd
    Version: 1.7.24~ds1-4
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

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

    --------------------------------------------------------------------------------
    [...]
    github.com/containerd/continuity github.com/containerd/containerd/pkg/cri/instrument
    # github.com/containerd/containerd/pkg/cri/instrument src/github.com/containerd/containerd/pkg/cri/instrument/instrumented_service.go:68:9: cannot use &instrumentedService{…} (value of type *instrumentedService) as GRPCServices value in return statement: *instrumentedService does not implement
    GRPCServices (missing method RuntimeConfig)
    [...]
    dh_auto_build: error: cd _build && go install -trimpath -v -p 2 [...] returned exit code 1
    make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:22: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary 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/202504/

    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:containerd, 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 Debian Bug Tracking System@21:1/5 to All on Tue Apr 8 20:40:01 2025
    Processing control commands:

    tag -1 pending
    Bug #1102287 [src:containerd] containerd: FTBFS: cannot use &instrumentedService{...}
    Added tag(s) pending.

    --
    1102287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102287
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tianon Gravi@21:1/5 to All on Tue Apr 8 20:40:01 2025
    Control: tag -1 pending

    Hello,

    Bug #1102287 in containerd 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/go-team/packages/containerd/-/commit/3589a2a408f71c3394e1c5dd384cab232537bea1

    ------------------------------------------------------------------------
    Add stubs for new cri-api RuntimeConfig (Closes: #1102287) ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1102287

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

    Your message dated Tue, 08 Apr 2025 22:49:47 +0000
    with message-id <E1u2HlL-007npM-Bf@fasolo.debian.org>
    and subject line Bug#1102287: fixed in containerd 1.7.24~ds1-5
    has caused the Debian Bug report #1102287,
    regarding containerd: FTBFS: cannot use &instrumentedService{...}
    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 owner@bugs.debian.org
    immediately.)


    --
    1102287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102287
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 7 Apr 2025 09:41:08 +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.4 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,
    PP_MIME_FAKE_ASCII_TEXT,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, 13; hammy, 150; neutral, 77; 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: <sanvila@debian.org>
    Received: from mitropoulos.debian.or