public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com, jan.kiszka@siemens.com
Subject: Re: [PATCH 1/1] bugfix: isar-exclude-docs delete man folders but some packages expect that folders
Date: Fri, 23 Sep 2022 13:18:25 +0200	[thread overview]
Message-ID: <20220923131825.517f4d50@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO6DR+XVBu9QOkBeAHVHtRNMH1otytcih7gw6LaruKJGZw@mail.gmail.com>

Am Fri, 23 Sep 2022 11:31:42 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:

> Dear Felix and Henning,
> 
>  - I confirm that there is a bug into the openjdk-11-jre-headless
> package
> 
>  - I confirm that I can avoid to use isar-exclude-doc or doing it in
> my way
> 
>  - I did not changed the openjdk-11-jre-headless package but it is
> buggy by itself
> 
> With these premises, every ISAR user can fall in my same condition:
> use the ISAR doc exclusion and include a buggy package.

Which would rather speak for making it more clear that the package can
cause trouble and by installing it one is leaving the "good debian
path".

> IMHO, the ISAR should be fault tollerant and should not break the
> building just because someone took the assumption that nobody out
> there makes mistakes or the generic ISAR user can solve in a minute
> any fault.

Including work arounds for bugs in other components is something that
can be done if really needed. But certainly not the first thing to do,
especially if the work-around can be done in a layer instead of the
core.

Such things are tricky and we try to help here when users come and ask.

> Thus, please consider to apply the patch and possible also the one
> about depmod -a in a for loop. :-)

The patch is wrong and only does half, if you turn the install order
around and call that update-alternative you will see the problem again.
Sorry ... no.

And i do not remember that depmod loop patch, but also a bug of another
component that can be worked around and does not need core support.

Thanks for pointing out the problems you found, but i am afraid those
two are not to be solved in Isar itself.

Please go ahead and patch that openjdk thingy in salsa, i bet they
might merge faster than we can discuss here. And the problem will be
solved in the right place.
If you can quickly point out 5 prominent packages that really need
their man-pages to function ... or wait no ... empty directories ... we
can think about patching the core.

Henning


> Thanks, R-


  reply	other threads:[~2022-09-23 11:18 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 [this message]
2022-09-23  8:57 ` Henning Schild
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=20220923131825.517f4d50@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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