See above :D

That's due to your customized guided form. The backend code doesn't expect to get these strings and so doesn't strip them.

CC: (none) => LpSolit

pinging for dmorgan as requested

pinging as requested

When you get to look at this, can the comments width also be wider?

*** Bug 10029 has been marked as a duplicate of this bug. ***

CC: (none) => fri

*** Bug 11974 has been marked as a duplicate of this bug. ***

CC: (none) => kristoffer.grundstrom1983

This is a long standing and quite annoying bug. It would be *really* nice if someone who knows his way around bugzilla could have a look at this.

Priority: Normal => High

Yes, and wider and auto wrapping comments (both viewing and entering) would be nice.

(In reply to Morgan Leijström from comment #9)
> Yes, and wider and auto wrapping comments (both viewing and entering) would
> be nice.

Comments are automatically wrapped already. About having a wider textarea, you can manually make it larger if you have a lot to type. Just click on the corner of the text field.


(In reply to Rémi Verschelde from comment #8)
> This is a long standing and quite annoying bug. It would be *really* nice if
> someone who knows his way around bugzilla could have a look at this.

The relevant code is in post_bug.cgi:

my $comment;
my $format = $template->get_format("bug/create/comment",
                                   scalar($cgi->param('format')), "txt");
$template->process($format->{'template'}, $vars, \$comment)
    || ThrowTemplateError($template->error());

You don't need this code anymore as you totally changed the guided form. You should call:

my $comment = $cgi->param('comment');

and parse it to remove the empty sections.

@Frederic:

iirc at some point way back you volunteered to maintain Mageia Bugzilla...

is this offer still valid ?

I think you wanted to use git for it back then which we didn't really like as puppet was happier with rpms...

but I think we would now be ok with a git based install much like we do for forum and other stuff

CC: (none) => tmb

(In reply to Thomas Backlund from comment #11)
> iirc at some point way back you volunteered to maintain Mageia Bugzilla...
> 
> is this offer still valid ?

If you upgrade your server from Mageia 1 to Mageia 5 first, yes. Else it's going to be a pain to maintain Bugzilla. neoclust tried to upgrade Mageia Bugzilla to 5.0 a few weeks ago and had to roll back due to too old Perl modules in Mageia 1.

Thanks, and Yes, I meant after we have rolled up infra to mga5

How far away until this is solved?

(In reply to Frédéric Buclin from comment #10)
> (In reply to Morgan Leijström from comment #9)
> > Yes, and wider and auto wrapping comments (both viewing and entering) would
> > be nice.
> 
> Comments are automatically wrapped already. About having a wider textarea,
> you can manually make it larger if you have a lot to type. Just click on the
> corner of the text field.

Yes, that only goes for the edit field where one enters the bug.

As we read comments more often than we enter them, it would be nice if the width of all comment fields would expand when we make the browser window wider, and long lines in them rewrapped.
So when someone enters a few lines of log or code that are long we can widen the window and see them in all theuir glory instead of like now have them wrapped unneccessarily.

(If also the field for entering comment would do this it need not have a handle)

@tmb: is there any ETA for the upgrade of infra to mga5? There are several reported bugs which will be automatically fixed once you upgrade to Bugzilla 5.0.

(In reply to Frédéric Buclin from comment #16)
> @tmb: is there any ETA for the upgrade of infra to mga5? There are several
> reported bugs which will be automatically fixed once you upgrade to Bugzilla
> 5.0.

I am myself waiting for bugzilla 5 for work around bugsquad tools, so am interested in the ETA as well.

@lpsolit:

There is now an empty git for new bugs.mageia.org that you can prepare new bugs.mageia.org setup on:
ssh://git@git.mageia.org/web/bugs

I guess you could set up a "testing" and a "live" branch (and "upstream" ?) or whatever layout you want... 

We'll then wire up git automatic push to new server from git according to the branches you want to use...

We still need to dump the db from bugzilla 4.4 and restore on new db server so you can test on...

@tmb: I guess you need my public SSH key to authenticate? :)

You should be able to add your key on identity.mageia.org

I see no such field, even in the "add attribute" section at the bottom of the page.

Oops, sorry, I forgot to promote your account, now try again

maybe on the new server we can go directly to bugzilla 5 but Frédéric will know better :)

Btw: welcome :)

CC: (none) => mageia

Welcome, Frédéric :-D

Reassigning this bug to you as welcome gift ;-)

CC: (none) => marja11
Assignee: dmorganec => LpSolit

(In reply to Nicolas Lécureuil from comment #23)
> maybe on the new server we can go directly to bugzilla 5

This would be the plan, yes. Doing the initial work on 4.4 to upgrade right after to 5.0 would be a waste of time, IMO.

That's weird, when I try to git clone ssh://git@git.mageia.org/web/bugs, it asks me for a password, but I use no passphrase. Could this mean that my public SSH key is not recognized by the server?

Created attachment 7479 [details]
Patch to remove useless strings from the initial comment

I'm not allowed to push changes to web/templates/bugzilla, so here is the patch. Please commit.

commit 5a60f9f2f5f070ac7d0f37ed79a3cdb7bc7b91f6
Author: Frédéric Buclin <LpSolit@...>
Date:   Sun Feb 21 21:43:46 2016 +0200

    remove useless strings from the initial comment (mga#9286)
---
 Commit Link:
   http://gitweb.mageia.org/web/templates/bugzilla/commit/?id=5a60f9f2f5f070ac7d0f37ed79a3cdb7bc7b91f6

Reopen if you can still reproduce this issue.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

FYI, I'm done with porting the Mageia extension to Bugzilla 5.0.

http://gitweb.mageia.org/web/bugs/commit/?id=9f4329cf