Re: ports/ia64: klibc-utils in Sid should use static binaries
Hi Adrian,
On 06/04/2018 11:02 AM, John Paul Adrian Glaubitz wrote:
Which build dependencies are you missing? I just did a test build
with sbuild and the build dependencies install just fine without
any issues.
I tried to follow the guide on the Debian wiki ([1]) and the `apt[-get]
build-dep klibc` command fails:
```
root@rx2620:~# apt build-dep klibc
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
builddeps:klibc : Depends: debhelper (>= 9~) but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.
root@rx2620:~# apt install debhelper
Reading package lists... Done
Building dependency tree
Reading state information... Done
[...]
The following packages have unmet dependencies:
debhelper : Depends: po-debconf but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@rx2620:~# apt install po-debconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
[...]
The following packages have unmet dependencies:
po-debconf : Depends: gettext (>= 0.16) but it is not going to be
installed
Depends: intltool-debian (>= 0.34.2+20060512) but it is
not going to be installed
E: Unable to correct problems, you have held broken packages.
root@rx2620:~# apt install gettext
Reading package lists... Done
Building dependency tree
Reading state information... Done
[...]
The following packages have unmet dependencies:
gettext : Depends: libcroco3 (>= 0.6.2) but it is not going to be
installed
Depends: libxml2 (>= 2.9.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
```
[1]: https://wiki.debian.org/BuildingTutorial#The_packaging_workflow
UPDATE: I think I found the problem. I had deb lines for unstable
**and** unreleased **and** experimental (plus deb-src line for sid from
f.d.o) in my `/etc/apt/sources.list`. Using only the deb line for
"unstable" and the deb-src line allows me to install the build
dependencies for klibc:
```
root@rx2620:~# apt build-dep klibc
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
autopoint bison debhelper dh-autoreconf dh-strip-nondeterminism dwz
gettext gettext-base intltool-debian
libarchive-zip-perl libbison-dev libcroco3
libfile-stripnondeterminism-perl libfreetype6 libgraphite2-3 libharfbuzz0b
libicu-le-hb0 libicu60 libpng16-16 libxml2 po-debconf
0 upgraded, 21 newly installed, 0 to remove and 3 not upgraded.
Need to get 16.1 MB of archives.
After this operation, 60.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
[...]
```
Maybe I should use sbuild in the future.
Also, you should create an account on salsa.debian.org, fork the
klibc repository into your own salsa home, create a branch for the
ia64-fix, revert the patch and send a pull request to Ben.
I wasn't sure if code parts for an unofficial Debian arch can be
included in the official repos, but on the other hand as we did the same
thing for the GRUB patches to support GPT on sparc64, it actually makes
perfect sense to do so. What was I thinking... :-/
Please don't forget to add an entry to debian/changelog with
"dch", but I think you're familiar with that already.
Right, but still thanks for the reminder. :-)
Cheers,
Frank
Reply to: