embug_report

Langue: en

Version: Sun 11 Jan 2009 19:55:45 GMT (debian - 07/07/09)

Section: 1 (Commandes utilisateur)

NAME

embug_report - Wrapper for reportbug that understands Emdebian bugs

SYNOPSIS

embug_report [[-a] | [--arch] ARCHITECTURE] [[-n] | [--dry-run]] [[--closes] BUGNUMBER]
embug_report [[-?] | [-h] | [--help] | [--version]]

DESCRIPTION

embug_report

simplifies the process of handling bugs in Emdebian - specifically, bugs filed against buildd.emdebian.org

embug_report needs to be run from the Debian package directory - i.e. ./debian/changelog must exist.

The main purpose is to make it easier to file bugs with appropriate build log extracts and also creating typical "closure" messages for bugs filed against buildd.emdebian.org so that these can be closed when uploading to Emdebian with the same kind of message as would be created when uploading a fixed package to Debian.

Bugs filed and closed using embug_report are intended for a variety of Emdebian-specific issues:

1. Emdebian patches failed to apply - these issues need to be resolved quickly so sometimes it is better to seek updated patches via the mailing list or IRC.
2. Emdebian packages failed to cross-build - the autobuilder report only shows this message if the patches applied correctly. The bug report should detail whether the package built natively on the specified architecture and include details of any likely fixes.
3. Emdebian packages cannot be uploaded due to dependency issues - where possible, these dependency issues can be overridden but sometimes a bug report is needed due to a new dependency being added to a package.
4. Emdebian packages contain unwanted changes without renaming packages - this is the newest section and these bugs need careful handling so that Emdebian Grip can be functionally equivalent to Debian and Emdebian Crush can support functional changes necessary to achieve the extra reduction in installation sizes and dependency tree changes.
5. Problems with the legality of Emdebian packages - missing copyright files, etc., where the equivalent Debian package is unaffected.
6. Other issues that arise within Emdebian packages but do not affect the equivalent Debian package.

CLOSING BUGS

Normally, the debian/changelog entry made by emdebuild is left untouched as it is not recorded within Emdebian and replaced when the next version arrives in Debian.

However, embug_report allows at least some kind of normal usage of the changelog because debchange and dch can be used to send closure messages and this support will be added to emrecent, using embug_report to automatically send the closure message with full details of the .changes file, to the bug report.

Closure messages are sent using /usr/bin/mail or a message is printed if the command cannot be executed.

Use the -n|--dry-run option to generate the closure message without sending it.

PACKAGES

embug_report only handles bugs assigned to the buildd.emdebian.org pseudo-package.

embug_report uses reportbug when filing new bugs.

COMMANDS

-a|--arch ARCHITECTURE

Override the default cross-build architecture (from dpkg-cross).

--closes BUGNUMBER

The bug number to close (if not already specified in the changelog itself).

AUTHOR

embug_report was written by Neil Williams codehelp@debian.org.

This manual page was written by Neil Williams codehelp@debian.org

SEE ALSO

See also emdebuild (1), empdebuild (1), emsource (1), embug (1), dpkg-cross (1), emdebian-tools (1).

m[blue]General Introductionm[][1] to crossbuilding Debian.

AUTHOR

Emdebian

Neil Williams

Debian and Emdebian developer.

NOTES

1.
General Introduction
http://www.emdebian.org/emdebian/intro.html