proposal to turn dh_shlibdeps warning into an error
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Debian) |
New
|
Unknown
|
|||
| dpkg (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
| Natty |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: dpkg
is there a reason not to turn this into an error and detect these bugs early?
seen in the cwiid build:
dh_shlibdeps -plibcwiid1
dpkg-shlibdeps: warning: symbol hci_close_dev used by debian/
dpkg-shlibdeps: warning: symbol pthread_cancel used by debian/
dpkg-shlibdeps: warning: symbol hci_open_dev used by debian/
dpkg-shlibdeps: warning: symbol hci_inquiry used by debian/
dpkg-shlibdeps: warning: symbol pthread_join used by debian/
dpkg-shlibdeps: warning: symbol pthread_create used by debian/
dpkg-shlibdeps: warning: symbol clock_gettime used by debian/
dpkg-shlibdeps: warning: symbol pthread_detach used by debian/
dpkg-shlibdeps: warning: symbol hci_read_
dpkg-shlibdeps: warning: symbol hci_get_route used by debian/
seen in the protobuf build, see bug #688819
dh_shlibdeps
dpkg-shlibdeps: warning: symbol pthread_once used by debian/
dpkg-shlibdeps: warning: symbol pthread_once used by debian/
dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/
dpkg-shlibdeps: warning: symbol pthread_once used by debian/
dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/
dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/
dpkg-shlibdeps: warning: dependency on libprotobuf.so.6 could be avoided if "debian/
| Changed in dpkg (Ubuntu): | |
| importance: | Undecided → High |
| milestone: | none → natty-alpha-2 |
| Colin Watson (cjwatson) wrote | #1 |
| Changed in dpkg (Ubuntu Natty): | |
| milestone: | natty-alpha-2 → none |
| status: | New → Confirmed |
| Changed in dpkg (Ubuntu Natty): | |
| assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
| Changed in dpkg (Debian): | |
| status: | Unknown → New |
| Colin Watson (cjwatson) wrote | #2 |
| Changed in dpkg (Ubuntu Natty): | |
| status: | Confirmed → Won't Fix |
| Colin Watson (cjwatson) wrote | #3 |
| Changed in dpkg (Ubuntu): | |
| assignee: | Canonical Foundations Team (canonical-foundations) → nobody |
| importance: | High → Medium |
| Changed in dpkg (Ubuntu Natty): | |
| assignee: | Canonical Foundations Team (canonical-foundations) → nobody |
| importance: | High → Medium |
I would be sceptical about this, because it would break any library that is structured to require particular symbols from its users. This isn't hugely common practice, but there are a few examples of it in the archive: libcgic comes to mind, whose design requires applications linked against it to supply a cgiMain symbol.
I think that this should be discussed with the Debian dpkg maintainers rather than requiring any particular schedule on the Ubuntu side, so I'm removing the milestone.