[KORG] Bugzilla Upgrade / Server move

[KORG] Bugzilla Upgrade / Server move

[J.H.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Evening Everyone,

Just a quick heads up to everyone http://bugzilla.kernel.org was taken
down for about an hour this evening to perform an upgrade that was
precipitated by a possible security vulnerability that we wanted to
squash quickly and avoid it going forward.

The code base has had a rather extensive upgrade, migrating custom
fields over to Bugzilla's 3.x custom field support, and dealing with
kernel.org specific changes.

Along with this upgrade http://bugzilla.kernel.org has moved onto the
kernel.org dynamic hosting machine, joining patchwork and our wikis on
this dedicated piece of hardware.

If you have any issues, problems, concerns, please don't hesitate to get
a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org

- - John 'Warthog9' Hawley
Chief Kernel.org Administrator
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAknJ2Z0ACgkQ/E3kyWU9didIjQCfcIkjMhbc1TvqlMPAjgwDFk8p
orEAnAtJWGMfZJNuawlxSuRTBDbcGFcD
=0IE9
-----END PGP SIGNATURE-----

Re: [KORG] Bugzilla Upgrade / Server move

[Alan Cox]

> The code base has had a rather extensive upgrade, migrating custom
> fields over to Bugzilla's 3.x custom field support, and dealing with
> kernel.org specific changes.

That has been needed for soooo long - thanks a lot.

> If you have any issues, problems, concerns, please don't hesitate to get
> a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org

Looks basically sound on a quick test. I've closed a lot of the bugs in
our bugzilla against our bugzilla as they are now fixed.

Only glitch so far is formatting (needed a shift-reload to clear the old
style sheet) but then still has problems because the version some people
enter is very very long and that field doesn't have a sensible width
forced in the list format.

There are some other things that need sorting once its settled - a lot of
the owner data and auto-assignment stuff is stale (eg reiser is still
assigned to namesys!) perhaps they should all be assigned to a mailing
list of the form bugzilla-category-subcat so that it becomes entirely
mailman "self service" ?

Re: [KORG] Bugzilla Upgrade / Server move

[Martin Bligh]

> There are some other things that need sorting once its settled - a lot of
> the owner data and auto-assignment stuff is stale (eg reiser is still
> assigned to namesys!) perhaps they should all be assigned to a mailing
> list of the form bugzilla-category-subcat so that it becomes entirely
> mailman "self service" ?

Yup, I'll try to finalize that conversion soon, we've been moving that way
for a long time.

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Pierre Ossman]

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

On Wed, 25 Mar 2009 00:13:33 -0700
"J.H." <warthog19@eaglescrag.net> wrote:

> 
> If you have any issues, problems, concerns, please don't hesitate to get
> a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org
> 

One small misfeature in the new bugzilla is that you can no longer view
attachments directly in the browser. For text/plain stuff this is
particularly annoying. If it could be fixed I'd be a much happier
camper. :)

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Dave Airlie]

> On Wed, 25 Mar 2009 00:13:33 -0700
> "J.H." <warthog19@eaglescrag.net> wrote:
> 
> > 
> > If you have any issues, problems, concerns, please don't hesitate to get
> > a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org
> > 
> 
> One small misfeature in the new bugzilla is that you can no longer view
> attachments directly in the browser. For text/plain stuff this is
> particularly annoying. If it could be fixed I'd be a much happier
> camper. :)

I think upstream bugzilla stopped this due to a potential security problem
with feeding things to the browser.

Dave.

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Pierre Ossman]

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Thu, 26 Mar 2009 01:12:33 +0000 (GMT)
Dave Airlie <airlied@csn.ul.ie> wrote:

> > 
> > One small misfeature in the new bugzilla is that you can no longer view
> > attachments directly in the browser. For text/plain stuff this is
> > particularly annoying. If it could be fixed I'd be a much happier
> > camper. :)
> 
> I think upstream bugzilla stopped this due to a potential security problem
> with feeding things to the browser.
> 

If we cannot trust the browser to safely handle most data, then I
suppose we'll all have to start using wget and browsing our pages via
less.

I hope this feature can be reconfigured, even if upstream happens to
think out browsers are too insecure to be on the net.

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Tejun Heo]

Hello,

Is there anyway to put the comment input area at the bottom of the
page?  Trying to reply at the top just messes up my head in weird
ways.

Thanks.

-- 
tejun

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Stefan Richter]

Tejun Heo wrote:
> Is there anyway to put the comment input area at the bottom of the
> page?  Trying to reply at the top just messes up my head in weird
> ways.

Here is a patch:
https://bugzilla.redhat.com/show_bug.cgi?id=457022#c19
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[Stefan Richter]

Stefan Richter wrote:
> Tejun Heo wrote:
>> Is there anyway to put the comment input area at the bottom of the
>> page?  Trying to reply at the top just messes up my head in weird
>> ways.
> 
> Here is a patch:
> https://bugzilla.redhat.com/show_bug.cgi?id=457022#c19

PS:
Here is a 'me too' to Tejun's comment.  Top-posting in bugzilla is OK if
one doesn't have to re-read the history of the bug because it's all
fresh in one's mind.  This is almost only the case when one follows the
bug by mail --- but then one can also reply by mail and doesn't have a
problem with the web interface anyway.  So, whenever one uses the web
interface of bugzilla.kernel.org, it is quite likely that one skims
through previous comments before adding a new one.  Hence comment box
after existing comments makes much more sense, IMO.  At least if
comments are shown in chronological order ( = site default).
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move

[J.H.]

Ok this change is in now.  The additional comments section should be 
below the comments now.

- John 'Warthog9' Hawley

Stefan Richter wrote:
> Stefan Richter wrote:
>> Tejun Heo wrote:
>>> Is there anyway to put the comment input area at the bottom of the
>>> page?  Trying to reply at the top just messes up my head in weird
>>> ways.
>> Here is a patch:
>> https://bugzilla.redhat.com/show_bug.cgi?id=457022#c19
> 
> PS:
> Here is a 'me too' to Tejun's comment.  Top-posting in bugzilla is OK if
> one doesn't have to re-read the history of the bug because it's all
> fresh in one's mind.  This is almost only the case when one follows the
> bug by mail --- but then one can also reply by mail and doesn't have a
> problem with the web interface anyway.  So, whenever one uses the web
> interface of bugzilla.kernel.org, it is quite likely that one skims
> through previous comments before adding a new one.  Hence comment box
> after existing comments makes much more sense, IMO.  At least if
> comments are shown in chronological order ( = site default).