Re: Ignore a dependency

[Henning Schild <henning.schild@siemens.com>]

Am Tue, 13 Sep 2022 20:59:51 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:

> 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.

You can always use dpkg-prebuilt where you download that package,
binary patch it and later installed the modified copy with isar.
However if you have a sources.list entry and that package can
potentially get updated, you will not be able to make that hack stable.

That is a pattern for a broken binary package which i had to get into
a layer.

do_binary_patch[cleandirs] += "${WORKDIR}/blabla-package"
do_binary_patch() {
	sudo dpkg-deb -R ${WORKDIR}/blabla-package.deb ${WORKDIR}/blabla-package
	# do something funny with the control file, i.e. sed -i -e ... Depends
	sudo dpkg-deb -b ${WORKDIR}/blabla-package
}
addtask binary_patch after do_unpack before do_deploy_deb

Henning

> 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-