News | About | Get Frugalware | Packages | Documentation | Discussion Forums | Bug Tracker | Wiki | Community | Development

Bugs

From FrugalWiki

Jump to: navigation, search

Contents

Warning

This howto now has been moved to the official documentation. If you modify this page, please send a patch to keep the official text in sync. Thanks.

Introduction

The aim of this HOWTO is to explain how to choose a task name and what to include in a feature request/bugreport to help Frugalware developers speed up the process of fixing a bug or fulfilling a feature request.

Where

The URL of our Bug tracking system is:

http://bugs.frugalware.org/

General

Before opening a task, use the search function, maybe there is a task for your bug/feature. In that case just add a comment about "I can reproduce this, too." or "I would enjoy this feature, too."

If you'd like to report outdated package make sure that it isn't listed on this site: http://frugalware.org/~vmiklos/stats/chkworld.html When your package is listed please do *not* report it as we know there is a new version and we will update it as soon as possible.

Bugreport

Please include the following things, unless you know what you are doing:

  1. Description of Problem - never say "does not work", quote the error message
  2. Steps to reproduce the problem
  3. Actual Results
  4. Expected Results
  5. How often does this happen?
  6. Additional Information

The default arch is i686 and the default version is -current. If these are not true, don't forget to change them!

If you report a -current installer bug, then maybe -current is not enough, please specify the snapshot date.

If you found a security bug, then use the [SEC] prefix in the task name.

Feature Requests

Please don't request more than one package in a feature request. Open a task for every package. (Of course you don't have to open task for dependencies if they are also missing from out packages.)

If you request a package, please include:

  1. The name of the application (yes, "more games" is not enough!)
  2. The URL of the application
  3. Optionally a short note about why do you think this package would be interesting for others, too

If you have a FrugalBuild for the package already, then after opening the task, upload it as an attachment. In this case, please prefix your task name with [FB], because this way it'll be reviewed sooner.

Pacman-g2 problems

If you get a crash from our package manager then we need a backtrace from gdb. Here are the instructions to get a backtrace:

  • Find the command line that triggers the crash. For example:
pacman-g2 -Sy
  • Get the pacman-g2 darcs repo and compile it with debug symbols enabled:
darcs get --partial http://darcs.frugalware.org/repos/pacman-g2
cd pacman-g2
sh autogen.sh
./configure --enable-debug
make
  • Then run pacman-g2 in gdb and get the trace:
cd src/pacman-g2
sudo libtool gdb ./pacman-g2
run -Sy
  • When pacman-g2 crashed, get the trace by typing 'bt'. Here is an example:
Program received signal SIGSEGV, Segmentation fault.
0x0805035e in pacman_sync (targets=0x0) at sync.c:354
354             *p = 1;
(gdb) bt
#0  0x0805035e in pacman_sync (targets=0x0) at sync.c:354
#1  0x08054594 in main (argc=2, argv=0xbfee1844) at pacman.c:609
(gdb)
  • Attach the output of 'bt' to your bugreport.

Fixed in darcs

Your feature request / bugreport may be closed with a "Fixed in darcs ..." message. Darcs is our source control management software (just like CVS). If your task is not considered to be important, then it will be fixed/implemented only in darcs, without increasing the package release. This means that it will be automatically included in the next release.

Personal tools
Namespaces
Variants
Actions