From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] bugfix: isar-exclude-docs delete man folders but some packages expect that folders
Date: Fri, 23 Sep 2022 10:57:11 +0200 [thread overview]
Message-ID: <20220923105711.6bb2ca49@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO7pP-Xc_VV8-34QDxjRkZGJ=csS6OOuLEr8ARi3y3t_FQ@mail.gmail.com>
Hi,
you could simply not install "isar-exclude-docs", it is kind of a hack
which removes files that are very likely not needed. You found a case
where one file is needed after all.
Whatever we do we have to keep the postinst and the
/etc/dpkg/dpkg.conf.d/ snippet in sync. So you can not decide to keep
directories in one approach and drop them with the other.
The snippet is a one-to-one copy from ubuntu Docker containers, would
not want to fork it. So if we have to change it, we should also report
that to ubuntu.
Long story short, i think it will be a rather trivial fix in the
postinst of that java package. That very java package might show the
same problem in a ubuntu container ... which would be a nice repro to
motivate the maintainer to take a patch which deals with a file missing
... that in a plain debian would never be missing.
So i would say someone has to open an issue on salsa, maybe an MR.
Mention isar-exclude-docs and ubuntu docker images as examples where
the files and folders can be missing.
In the meantime you can not install isar-exlcude-docs, or install the
java package before it, or patch that postinst locally by rebuilding
the java package, or write a dummy package that does an "mkdir" in
postinst and install it after exclude and before java ... i think just
installing the docs is the easiest and will not cost you too much space.
Henning
Am Thu, 22 Sep 2022 22:36:22 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> Hi all,
>
> bugfix: isar-exclude-docs delete man folders but some packages expect
> that folders.
> solution: adopts the same approach used for the doc folder.
>
> https://github.com/robang74/isar/commit/c656e6df63aa76701e34d7ee3f99c81e96312b9d
>
> diff --git a/meta/recipes-support/isar-exclude-docs/files/postinst
> b/meta/recipes-support/isar-exclude-docs/files/postinst
> index d34c04e..581cdc1 100644
> --- a/meta/recipes-support/isar-exclude-docs/files/postinst
> +++ b/meta/recipes-support/isar-exclude-docs/files/postinst
> @@ -3,5 +3,5 @@
> # time and do not need to be "the first" package
> # what we delete needs to be in sync with the dpkg configuration we
> ship
>
> -rm -rf /usr/share/man/*
> +find /usr/share/man/ -type f -exec rm -rf {} \;
> find /usr/share/doc/ -type f ! -name "copyright" ! -name
> "changelog.*" -exec rm -rf {} \;
>
> Here you are the error during the configuration of the package:
>
> Setting up openjdk-11-jre-headless:amd64 (11.0.16+8-1~deb11u1) ...
> update-alternatives: using
> /usr/lib/jvm/java-11-openjdk-amd64/bin/java to provide /usr/bin/java
> (java) in auto mode update-alternatives: error: error creating
> symbolic link '/usr/share/man/man1/java.1.gz.dpkg-tmp': No such file
> or directory dpkg: error processing package
> openjdk-11-jre-headless:amd64 (--configure): installed
> openjdk-11-jre-headless:amd64 package post-installation script
> subprocess returned error exit status 2 dpkg: dependency problems
> prevent configuration of openjdk-11-jre:amd64: openjdk-11-jre:amd64
> depends on openjdk-11-jre-headless (= 11.0.16+8-1~deb11u1); however:
> Package openjdk-11-jre-headless:amd64 is not configured yet.
>
> Cheers, R-
>
next prev parent reply other threads:[~2022-09-23 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:36 Roberto A. Foglietta
2022-09-22 21:31 ` Roberto A. Foglietta
2022-09-23 12:01 ` Henning Schild
2022-09-23 14:18 ` Roberto A. Foglietta
2022-09-23 14:39 ` Henning Schild
2022-09-23 8:06 ` Moessbauer, Felix
2022-09-23 9:31 ` Roberto A. Foglietta
2022-09-23 11:18 ` Henning Schild
2022-09-23 8:57 ` Henning Schild [this message]
2022-09-23 9:25 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220923105711.6bb2ca49@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox