bugs.mageia.org uses PostgreSQL as DB server. While MySQL silently cuts too long strings if they don't fit in a DB column, PostgreSQL crashes. Bugzilla only accepts a maximum of 255 characters for the bug summary (which is already long enough), but drakbug can report bug summaries much longer than that when it includes the backtrace in it. This happened to me a few minutes ago where the bug summary was 669 characters long, and PostgreSQL crashed with an unhelpful error message. So drakbug should really either a) skip the backtrace from the bug summary, or b) limit it to the last caller, keeping the whole backtrace for the bug comment.
Assignee: bugsquad => thierry.vignaud
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.
CC: (none) => marja11
Status: NEW => ASSIGNED
We don't put the whole call stack in the summary. You fail to show any too long bug summary
Keywords: (none) => NEEDINFO
One example of a very long bug summary is in bug 3042 comment 0. The paths to locate Perl were all included in the bug summary, making it very long. I had to cut it to submit the bug report.
Keywords: NEEDINFO => (none)
And what? That's exactly that, a comment, not a summary. As shown by this bug history, summary was fine (70 characters exactly, quite less than 255...).
Did you read what I wrote in comment 3? I had to *CUT* the bug summary! I know the difference between a comment and a bug summary...
I see, it happens about exceptions about missing files. Next time, please be clearer, I understand "The paths to locate Perl" as "path to perl" whereas what you meant was "the paths where looks for modules". Just updated summary. I'll fix it for mga2 but probably not for mga1 (not critical & rare).
Summary: drakbug must not report bugs with a summary longer than 255 characters, else Bugzilla won't accept it => drakbug mustn't report summaries longer than 255 characters, else Bugzilla won't accept it (eg: when a module is missing, exception contains %INC)
I just tested and your claim is bogus: drakbug only set the summary to "XXX crashed" or "XXX segfaulted". Nothing more. It doesn't include the actual exception message in the summary.
Version: 1 => 2
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Version: 2 => Cauldron
Closing as OLD. Please reopen if still valid in Mageia 4 or 5.
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD