public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com,  "Schild,
	Henning" <henning.schild@siemens.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 11:31:42 +0200	[thread overview]
Message-ID: <CAJGKYO6DR+XVBu9QOkBeAHVHtRNMH1otytcih7gw6LaruKJGZw@mail.gmail.com> (raw)
In-Reply-To: <AM9PR10MB4869E983B33E008783260AB189519@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

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.

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.

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

Thanks, R-

[-- Attachment #2: Type: text/html, Size: 1110 bytes --]

  reply	other threads:[~2022-09-23  9:31 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 [this message]
2022-09-23 11:18     ` Henning Schild
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=CAJGKYO6DR+XVBu9QOkBeAHVHtRNMH1otytcih7gw6LaruKJGZw@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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