From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6948863191726161920 X-Received: by 2002:a05:600c:48a6:: with SMTP id j38mr6028131wmp.99.1618045038756; Sat, 10 Apr 2021 01:57:18 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:285:: with SMTP id 5ls5350851wmk.3.gmail; Sat, 10 Apr 2021 01:57:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxnF9fROvZKrQ15LNhq0YwieBhhrkEUAwk1EGih03oXSN/TCTj3oM0svxn0/UlrF6Nn5IFF X-Received: by 2002:a05:600c:19d2:: with SMTP id u18mr17546244wmq.147.1618045037886; Sat, 10 Apr 2021 01:57:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618045037; cv=none; d=google.com; s=arc-20160816; b=Mao/h00MALGCYrUJAE1lxrgk+w0QLXo1QFyqb1cEe3FaKtmH2VQTIxxpHQox68ru5y ddhUIK3SIYpg4a9la5qbMcnlUEdgxU/zBge3vFWsVNpCqpNDEnNUB/lkJHWYo1g91Ovh zJPKZI+kZ+p4DQe1wTalK2RA1MV9J48GjbKTR4dfTU/zHcBjKRZMoprMOT8+3yMoFWzt 36iX9sl7bEeegIY5nJyL+XtnfJ3mpnrXopiW6L+GWKlI5JIGiR383RDk/zKCv/JEYagW Gznv3AbI1/A5XyVCPPOb29BXyWckgusfi9ey7TQ1SZGyN2iB0vb2bkY4ZPUnb6e9qgzc RMUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=HmFYF8oSA9S/dKqY7fSaYOZXu24p7m/2Yxwu+kVpsOE=; b=dPdeCcCTrpU5Qh9OnoJj0FRX7c/yiUbEo0urZu/HQQpmJ0enAx6fEvEK6PBAJwTvDU pfXeP9KcyEOYfv5+rWRjKV0aeLBZ6BxtpAbF2NsxLE8pbQqK8Ov5kDTlYyQNXSljp1nu DzEBKeMus83ovEmisaiVE62idhaqjeNrynFnOtwg6EDzN1t0Zqfb8y3SZGLrvITO7XTP XoYDm0eQMmKlFfxdCQdua5Ozon54muMhDCli4hfnX8cdrnpDu4K5LIIasqYiNINbvhhs XRgNwVPwwdb3aGzinltBRjAbPNuYxkKSRW0PDZMcTKT1NJA6OH72bwl3bIGFPb0NVJTT Y3dg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id f8si1002498wmj.1.2021.04.10.01.57.17 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Apr 2021 01:57:17 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id 13A8vHjl012575 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 10 Apr 2021 10:57:17 +0200 Received: from md1za8fc.ad001.siemens.net ([139.22.114.252]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 13A8kKcJ029199; Sat, 10 Apr 2021 10:46:20 +0200 Date: Sat, 10 Apr 2021 10:46:18 +0200 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: isar-exclude-docs vs. openjdk et al. Message-ID: <20210410104618.790f06b3@md1za8fc.ad001.siemens.net> In-Reply-To: <265b98fc-524f-7f7e-164c-0215f5e9d494@siemens.com> References: <51fed86f-7579-3f42-4780-c84e18bf4117@siemens.com> <20210409103005.0d904d99@md1za8fc.ad001.siemens.net> <265b98fc-524f-7f7e-164c-0215f5e9d494@siemens.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: GJ8maeRrNO47 Am Fri, 9 Apr 2021 15:01:48 +0200 schrieb Jan Kiszka : > On 09.04.21 10:30, Henning Schild wrote: > > Hi, > > > > not sure that doc purging is really allowed or whether we are > > messing with stuff we better should not mess with. > > > > Am Thu, 8 Apr 2021 20:54:28 +0200 > > schrieb Jan Kiszka : > > > >> Hi all, > >> > >> there seems to be a conceptual issue with isar-exclude-docs purging > >> documents in its postinst hook: If other packages are configured > >> after isar-exclude-docs and those packages expects certain doc > >> paths to be still there, see openjdk [1], they will fail. > >> > >> How to solve that? > >> - maintain a list of conflicting packages in that recipe? > > > > This is going to be cumbersome but when having a packet that needs > > its docs, we probably should not install that cleaner. > > > >> - convert the package to a post-process hook? > > > > would still break apt-get update of packages that need their docs > > > >> - find a way to ensure a compatible ordering when running our > >> postinst? > > > > again going to break apt-get > > > > Looking at this one example it does not really need its docs, it > > just expects them in "its own hack". My guess is that the problem > > can be reproduced in a ubuntu container (where the no-docs stuff is > > coming from), and can be used to report an issue so that the > > update-alternatives script looks for the files conditionally. Or > > maybe write a patch for that package and MR it on salsa directly. > > > > If you are installing java you probably can store a few MB of docs > > ;) > > Yeah, the case that triggered that is a bug, not a real scenario. I'm > lacking a feeling how common that combination is and if there might be > realistic combinations as well. My guess is that it would be best to try and mainline that package right into debian. They could use it for their containers, offer it for their users and will maintain the list of conflicts or detect such bugs. As far as i remember the configs came from ubuntu, not sure they have it packaged or just smuggle it into their containers. That said, i bet there are packages that have runtime deps on (their) docs. Doc readers or applications that opt for cat ing a file on --help, probably not made up ... Henning > Jan > > > Henning > > > >> > >> Jan > >> > >> [1] > >> https://groups.google.com/g/isar-users/c/uIHgzvCGLwU/m/tuOchY6BAgAJ > >> > > > >