View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007516 | Kali Linux | Kali Package Bug | public | 2021-12-28 14:39 | 2021-12-31 01:43 |
Reporter | linuxkd | Assigned To | arnaudr | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 2021.4 | ||||
Summary | 0007516: bind9-libs causes dpkg errors that prevent installation of other packages, causes apt failures afterwards | ||||
Description | Installing bind9-libs either directly or as a dependency causes issues with dpkg and the apt database. | ||||
Steps To Reproduce | 1) Setup minimal base OS (I used debian 11 minimal as a starting point, I have my reasons). 3) Install bind9-libs | ||||
Additional Information | root@ip-172-31-0-223:/home/admin# apt install bind9-libs Subsequent installs become broken The only working method of removing the blocker that I have found that works every time this packages is a dependency for dnsutils (nslookup, dig, etc) | ||||
This section was slightly wrong in my original post, there should not be a period in the first line, this is the corrected version The only working method of removing the blocker that I have found that works every time |
|
Dug a little further, here is some more relevant information. dpkg version info root@ip-172-31-0-223:~/work1# dpkg --version I extracted the bind9-libs package to look at the triggers file, here is the contents along with checksum Triggers added by dh_makeshlibs/13.5.2activate-noawait ldconfig root@ip-172-31-0-223:~/work1# sha1sum triggers |
|
Hello. I can't reproduce this issue when I build a Kali OS from scratch. It seems that the issue is really due to your setup, ie. starting from a Debian OS and then transforming it into Kali. It would be better to NOT do that !! This is not supported, and it's a recipe for tears and sorrow. Out of curiosity, why not just starting from a minimal Kali OS (it's easy with debootstrap) ? Otherwise, if you insist on doing that, you can have a look here: https://gitlab.com/kalilinux/tools/kali-ci-autopkgtest-lxc/-/blob/master/.gitlab-ci.yml#L53-75 This is a place where we do that, ie. start from a Debian min OS and transform it into Kali afterward. In short:
From this point, I guess it should fix your problem. But there might be more issues down the road waiting for you, because this is just NOT the right way to bootstrap a Kali image. |
|
(also for this kind of questions, please consider going through https://forums.kali.org/ rather than the bugtracker, as this is definitely not a bug) |
|
Thank you very much for the detailed response, and noted on the forums bit. |
|
No worries, I'm closing this issue then. Have a nice day and happy new year! |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2021-12-28 14:39 | linuxkd | New Issue | |
2021-12-28 14:52 | linuxkd | Note Added: 0015574 | |
2021-12-28 15:22 | linuxkd | Note Added: 0015576 | |
2021-12-30 07:53 | arnaudr | Note Added: 0015583 | |
2021-12-30 07:55 | arnaudr | Note Added: 0015584 | |
2021-12-30 14:10 | linuxkd | Note Added: 0015587 | |
2021-12-31 01:43 | arnaudr | Note Added: 0015590 | |
2021-12-31 01:43 | arnaudr | Assigned To | => arnaudr |
2021-12-31 01:43 | arnaudr | Status | new => closed |
2021-12-31 01:43 | arnaudr | Resolution | open => unable to reproduce |