| View previous topic :: View next topic |
| Author |
Message |
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20419
|
 Posted: Fri Dec 20, 2019 6:48 am Post subject: buildpkg, downgrade-backup & unmerge-backup conflict? |
 |
|
It appears to me that either or both features downgrade-backup and unmerge-backup may overwrite packages created by buildpkg.
When installing binary packages on a client, I have seen some configuration files with the following contents: | Code: | | # empty file because --include-config=n when `quickpkg` was used |
I wasn't using quickpkg, so as a test, I removed the link /usr/bin/quickpkg. Sure enough, during an emerge: | Code: | >>> Installing (1 of 3) dev-python/bz2file-0.98::gentoo
* checking 5 files for package collisions
quickpkg: command not found!!! FAILED preinst: quickpkg: 127 |
Which lead to the discovery that buildpkg appeared to use quickpkg. Although after noticing downgrade-backup and unmerge-backup, those two seem to more likely be the culprit. Which would mean the package created by buildpkg is overwritten.
Is proper use / use case of downgrade-backup and unmerge-backup documented somewhere? I didn't see anything in the Binary package guide.
Seemingly relevant bugs:
Bug 464662 - quickpkg --include-config=y breaks config file protection·
Bug 643872 - sys-apps/portage: quickpkg could automatically prevent creation of duplicate packages
Bug 687862 - sys-apps/portage: FEATURES=unmerge-backup || downgrade-backup should use quickpkg --include-config=y
Description of features:
| man make.conf wrote: | buildpkg
Binary packages will be created for all packages that are merged. Also see quickpkg(1) and emerge(1) --buildpkg and
--buildpkgonly options.
downgrade-backup
When a package is downgraded to a lower version, call quickpkg(1) in order to create a backup of the installed version
before it is unmerged (if a binary package of the same version does not already exist). Also see the related
unmerge-backup feature.
unmerge-backup
Call quickpkg(1) to create a backup of each package before it is unmerged (if a binary package of the same version does
not already exist). Also see the related downgrade-backup feature. |
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
 |
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Fri Dec 20, 2019 2:04 pm Post subject: |
|
|
indeed there's something strange there, because both options doesn't produce the same package in real
| Code: | # rm bz2file-0.98.tbz2
# emerge -1 --usepkg=n --buildpkgonly bz2file
# mv bz2file-0.98.tbz2 bz2file-0.98.tbz2.buildpkg
# quickpkg --include-config=y bz2file
# mv bz2file-0.98.tbz2 bz2file-0.98.tbz2-withconfig
# quickpkg --include-config=n bz2file
# md5sum bz2file-0.98.tbz2*
afcc623166d0dd19fda579286052c7c5 bz2file-0.98.tbz2
afcc623166d0dd19fda579286052c7c5 bz2file-0.98.tbz2-withconfig
a4ade32ff5dd220d9a57ca4827a0e435 bz2file-0.98.tbz2.buildpkg |
|
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20419
|
| Posted: Tue Dec 24, 2019 7:41 pm Post subject: |
|
|
Interesting. I hadn't even considered whether or not quickpkg was capable of producing correct results. :)
I guess I'll just consider it a currently incomplete set of features. At least now I have a new project to find out which packages lack proper config files in them.
Thanks.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
|
Portage & Programming
