#764983 reportbug --template aptitude misses vital configuration details

Package:
aptitude
Source:
aptitude
Description:
terminal-based package manager
Submitter:
積丹尼 Dan Jacobson
Date:
2015-11-11 23:06:03 UTC
Severity:
minor
#764983#5
Date:
2014-10-12 19:01:35 UTC
From:
To:
reportbug --template aptitude misses vital configuration details.

Here I am e.g., preparing a bug report about config files remaining:

# set libapt-pkg4.13
# aptitude purge $@
The following packages will be REMOVED:
  libapt-pkg4.13{p}
0 packages upgraded, 0 newly installed, 1 to remove and 5 not upgraded.
Need to get 0 B of archives. After unpacking 2,698 kB will be freed.
The following packages have unmet dependencies:
 libapt-inst1.5 : Depends: libapt-pkg4.13 (>= 1.1~exp1) but it is not going to be installed.
The following actions will resolve these dependencies:

     Remove the following packages:
1)     libapt-inst1.5
2)     python-apt

Accept this solution? [Y/n/q/?]
The following packages will be REMOVED:
  libapt-inst1.5{a} (D: libapt-pkg4.13)  libapt-pkg4.13{p}  python-apt{a} (D: libapt-inst1.5)
0 packages upgraded, 0 newly installed, 3 to remove and 5 not upgraded.
Need to get 0 B of archives. After unpacking 4,027 kB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 115036 files and directories currently installed.)
Removing python-apt (0.9.3.10) ...
Removing libapt-inst1.5:i386 (1.1~exp1) ...
Processing triggers for libc-bin (2.19-11) ...
(Reading database ... 114958 files and directories currently installed.)
Removing libapt-pkg4.13:i386 (1.1~exp3) ...
Purging configuration files for libapt-pkg4.13:i386 (1.1~exp3) ...
Processing triggers for libc-bin (2.19-11) ...

Current status: 3891 new [-1].
# aptitude search ~c
c   libapt-inst1.5                                                - deb package format runtime library

And reportbug --template aptitude has this
#764983#10
Date:
2014-10-13 01:20:23 UTC
From:
To:
Hi Dan,

積丹尼 Dan Jacobson wrote:

But you don't list _what_ you are missing, just what you got -- which
looks quite a lot to me, hence it's not obvious what you miss.

		Regards, Axel
#764983#17
Date:
2014-10-14 03:14:24 UTC
From:
To:
E.g., in my bug example there was a something probably affected by
one of them, but I had to remember to append them by hand to the bug report!
#764983#24
Date:
2015-11-11 17:46:51 UTC
From:
To:
Hi,

2014-10-14 04:14 積丹尼 Dan Jacobson:

One of the problems to solve this is that reportbug should not be used
as root, while aptitude's Aptitude:: config values often come from
~root/.aptitude/config, and sometimes people launch aptitude as regular
user and then become root as part of running aptitude, or run through
sudo, etc.

So if the person uses reportbug as normal user, it cannot read the
root's config, and if one uses root (which reportbug doesn't recomment)
then it's not known which user's config should be appended as well.

I don't know if the problem can be solvable in general.  Unless we only
capture the reporting user's config, I don't know if we can do much
better.


Cheers.
#764983#33
Date:
2015-11-11 23:02:32 UTC
From:
To:
vital supplementary information.