Bug#138409: PROPOSAL] Add build environment data to <package>.changes files
Randolph Chung <email@example.com> cum veritate scripsit:
> one problem is that some packages have build-dependency chains that
> when resolved completely are very deep, and sometimes contains dependency
> cycles. One could argue that these are bugs, but they seem difficult to fix
> in some cases.
Would it be too bad to include whole " dpkg -l " output ?
It sometimes may help, especially when libraries start
diverting other libraries etc.
firstname.lastname@example.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4