public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: Ignore a dependency
Date: Tue, 13 Sep 2022 20:59:51 +0200	[thread overview]
Message-ID: <CAJGKYO5Tm3qwWgCcwBS1pFQ4+67a3ZAEaU8zBMct7PkNr=23_Q@mail.gmail.com> (raw)
In-Reply-To: <20220913155324.1425d13a@md1za8fc.ad001.siemens.net>

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

Dear Uladzimir and Henning,

First of all thanks for your answers.

I confirm that I did not found a straight forward way to do it. After all,
it is not necessary also. Mainly because two reasons: 1. debian packages
dependencies are sane and do not require any bypass; 2. the dpkg database
is left with a unsatisfied dependency and this get bothering forever.

Unfortunately, it is about a thirty party proprietary deb packages source.

I am testing a fake .deb in which the postinst unpack the target .deb and
it uses install to deploy the content in the rootfs. I hate to use this
trick but I need just one file from that package.

In brief, it does such a thing:

set the resolv.conf
apt update
apt download
dpkg -x
install
rm all

Every suggestion will be appreciated.

Best regards, R-

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

  reply	other threads:[~2022-09-13 19:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 11:55 Roberto A. Foglietta
2022-09-13 12:53 ` Uladzimir Bely
2022-09-13 12:58   ` Roberto A. Foglietta
2022-09-13 13:09     ` Baurzhan Ismagulov
2022-09-13 13:09     ` Uladzimir Bely
2022-09-13 13:53     ` Henning Schild
2022-09-13 18:59       ` Roberto A. Foglietta [this message]
2022-09-14  8:34         ` Henning Schild
2022-09-14 18:42           ` Roberto A. Foglietta
2022-09-15  9:35             ` Henning Schild
2022-10-01 22:14           ` Roberto A. Foglietta
2022-10-01 23:10             ` Roberto A. Foglietta

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='CAJGKYO5Tm3qwWgCcwBS1pFQ4+67a3ZAEaU8zBMct7PkNr=23_Q@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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