From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id INnvObM5Y2QyJwAASxT56A (envelope-from ) for ; Tue, 16 May 2023 10:07:16 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 6FcNOrM5Y2SjhgAA9RJhRA (envelope-from ) for ; Tue, 16 May 2023 10:07:15 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 9799E811F for ; Tue, 16 May 2023 10:07:15 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pypi5-0001Y1-7z; Tue, 16 May 2023 04:07:05 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pypi2-0001Xp-Ct for bug-guix@gnu.org; Tue, 16 May 2023 04:07:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pypi2-00086d-23 for bug-guix@gnu.org; Tue, 16 May 2023 04:07:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pypi1-0000sJ-N1 for bug-guix@gnu.org; Tue, 16 May 2023 04:07:01 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#63530: Missing library in package procps Resent-From: Gabriel Wicki Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Tue, 16 May 2023 08:07:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63530 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: 63530@debbugs.gnu.org Received: via spool by 63530-submit@debbugs.gnu.org id=B63530.16842243713300 (code B ref 63530); Tue, 16 May 2023 08:07:01 +0000 Received: (at 63530) by debbugs.gnu.org; 16 May 2023 08:06:11 +0000 Received: from localhost ([127.0.0.1]:45111 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pyphD-0000rA-2j for submit@debbugs.gnu.org; Tue, 16 May 2023 04:06:11 -0400 Received: from chimborazo.ee.ethz.ch ([129.132.2.15]:50529) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pyph8-0000qY-OL for 63530@debbugs.gnu.org; Tue, 16 May 2023 04:06:09 -0400 Received: from localhost (antispam.ee.ethz.ch [129.132.2.16]) by chimborazo.ee.ethz.ch (Postfix) with ESMTP id 91D4A400ED for <63530@debbugs.gnu.org>; Tue, 16 May 2023 10:05:59 +0200 (CEST) X-Virus-Scanned: by amavisd at antispam.ee.ethz.ch Received: from chimborazo.ee.ethz.ch ([129.132.2.15]) by localhost (antispam.ee.ethz.ch [129.132.2.16]) (amavisd-new, port 10026) with ESMTP id IU2qCUxDGoAn for <63530@debbugs.gnu.org>; Tue, 16 May 2023 10:05:58 +0200 (CEST) Received: from blackbox (212-51-128-25.fiber7.init7.net [212.51.128.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gabriel) by chimborazo.ee.ethz.ch (Postfix) with ESMTPSA for <63530@debbugs.gnu.org>; Tue, 16 May 2023 10:05:58 +0200 (CEST) From: Gabriel Wicki References: <87wn192qh8.fsf@erlikon.ch> <87o7mlkyq8.fsf@riseup.net> Date: Tue, 16 May 2023 10:05:54 +0200 In-Reply-To: <87o7mlkyq8.fsf@riseup.net> (Csepp's message of "Tue, 16 May 2023 00:36:37 +0200") Message-ID: <87mt243dlp.fsf@erlikon.ch> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1684224435; a=rsa-sha256; cv=none; b=AvdWNbiQ9RCO6W38C6Doq4QQZpYZys8GpeyRG1nL0PDGu98in9tUfpdOqmHP3njInC9daW XXR5anVv74xIe01V8QhmnOMDB4+4Phjk7oIxIdsDIj816yjSu8YqnptpEOhUlgv/Dc7JId Jx3TsMY68vwo5kWN2l7ofBMX4wUewZnctU8It5mzpDgzn5Veblm8EI3R5HwDMCVeAufi+2 chF6R4bF4hyYIbpbXK7hAIs5x0YvHatEs6I19ErxwE+TJzcYlqdoyc3cwTeanszMBMod/u aMz24p+i36h7ivwDxYSAbVuG0IASpkvHN1QPi0D6oqYMmCbRNqgtePOJh+Dhvg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1684224435; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post; bh=XeJ+UKcuvJfg6qyF3GZkJMlE5LT1sMvfIgSDjpWJD/s=; b=djAGbw3nHg13+Dw1AavOIbLGwWLrYie4+KFcjw1VDxePvSlL8gljMmpPH6rxDdwQnxBFFy Jg2/tzFcppVNifuOHI1/orRhWfxcWK2XYYHwYS8axlhegauLHdyyci3+rAQgXnTBGlA++i ifCwc21QlUxJha9VQh/fbmR/P858koEi4zi6mNGKyU+5JPouroJ1F8+oc84/cW6zQoKryY CcmKqY9LgZXQEJz+gonEMzNElUjw7+gEHpNnKSLXMy2l73lagBtT6Bbo8ngmDE+W9XJ61I nvETCTQaf4Pl295jLDQQ6bv/57vHxhxtHeaD5Ko+fdFceSu8ALukauisrxs9Ow== X-Migadu-Spam-Score: -3.69 X-Spam-Score: -3.69 X-Migadu-Queue-Id: 9799E811F X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" X-TUID: EL6/DI4dUqNX A little more hacking leads me to the conclusion that (probably with version 4 but it's not exactly clear from the changelog) procps has made some significant changes to it's API. So, unless igt-gpu-tools (and probably others) are fixed upstream they remain broken. Fixes through simple regex-magic in our build-phases might be possible, but I am not confident enough in the matter to guarantee that the package would not just build but be broken in a more specific manner. Is there an easy way to check which dependents of procps are actually broken currently? Or is it really just igt-gpu-tools? There's two ways to go (I'd be happy for some input and volunteer to do the actual leg-work): 1. Add an additional procps-3 package with the older API to fix the broken packages. 2. Leave it as-is and wait for an upstream change of the currently broken packages.