Apport

provide a framework to blacklist on the basis of packages

Bug #1078819 reported by Ritesh Raj Sarraf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apport
Confirmed
Low
Unassigned

Bug Description

In its current form, blacklisting in apport is done using full file path, per file.
This is good enough to cover crashes that will occur in the specific binary/library.

I have users requesting to provide an option to completely opt-out of apport bug reports. This would mean report related to packaing - debconf/postinst/preinst and also from tools like dkms etc.

This is a feature request to provide a blacklisting mechanism on the basis of package names.

Revision history for this message
Martin Pitt (pitti) wrote :

Actually /etc/default/apport is meant to provide this globally, with "enabled = 0". At least signal and Python crashes respect this. Other things like apt are supposed to call /usr/share/apport/is-enabled or check /etc/default/apport before they write a report.

On a per-package basis this could be implemented with a new set of blacklist files, but it might actually be easier to implement it as a global hook. How do you want the blacklist to look like? For Debian I suppose it should be something that a package maintainer can change, such as a tag in debian/control, a debtag, or a collab-maint repo?

Revision history for this message
Ritesh Raj Sarraf (rrs) wrote : Re: [Bug 1078819] Re: provide a framework to blacklist on the basis of packages

On Thursday 15 November 2012 11:28 AM, Martin Pitt wrote:
> Actually /etc/default/apport is meant to provide this globally, with
> "enabled = 0". At least signal and Python crashes respect this. Other
> things like apt are supposed to call /usr/share/apport/is-enabled or
> check /etc/default/apport before they write a report.
>
> On a per-package basis this could be implemented with a new set of
> blacklist files, but it might actually be easier to implement it as a
> global hook. How do you want the blacklist to look like? For Debian I
> suppose it should be something that a package maintainer can change,
> such as a tag in debian/control, a debtag, or a collab-maint repo?

debian/control could be our last option to do it. THis was something
that was present in the initial hack that I shared with you.
But this still will need all the packages to add this change.

How about the blacklist files? We could just add a pkgnames.d/ folder
there. This approach does not need too many changes elsewhere.

--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

Evan (ev)
Changed in apport:
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.