Accueil > Bugzilla > Do not use MySQL 5.1.31 or newer with Bugzilla 3.2 – 3.2.2

Do not use MySQL 5.1.31 or newer with Bugzilla 3.2 – 3.2.2

As described in bug 480001, MySQL 5.1.31 and newer no longer let you write ‘SET SESSION max_allowed_packet = xxxx’ (this variable is now read-only, unless set globally). As we are calling it from two different places in Bugzilla 3.2, 3.2.1 and 3.2.2, those versions won’t work together. I hope this problem will be fixed in Bugzilla 3.2.3.

Update: this bug has been fixed and will be available in Bugzilla 3.2.3, which should be released very soon now (probably next week).

About these ads
Catégories:Bugzilla
  1. fluffy
    5 mars 2009 à 4:28   | #1

    A patch is available at the bugreport…

  2. lpsolit
    11 mars 2009 à 11:49   | #2

    For all those having the same problem with Bugzilla 3.2.2, the patch is available here:

    https://bug480001.bugzilla.mozilla.org/attachment.cgi?id=364818

    Put this patch somewhere on your computer (the patch is named maxpacket-3.2.diff), and then go into your bugzilla/ root directory and type:

    patch -p0 –dry-run < /path/to/the/patch/maxpacket-3.2.diff

    If no error is thrown, run the same command again, but without –dry-run.

    The final step is to run checksetup.pl again to restore file permissions which are altered when applying the patch.

  3. Thomas Deboben
    12 mars 2009 à 2:21   | #3

    Hi,

    I have tried to install the patch on my Windows XP system.
    The patch command isn’t available.
    Is this a CVS command. I havn’t CVS on my machine.

    How could I fix it on my system.

    Many thanks,
    Thomas

    • lpsolit
      12 mars 2009 à 4:52   | #4

      No, patch.exe isn’t a CVS command. For instance, you can install it from here:

      http://unxutils.sourceforge.net/

      I don’t remember if I tested this package, but it looks good, and patch.exe is there.

  4. Thomas Deboben
    12 mars 2009 à 2:58   | #5

    Hi again,

    I’ve checked the .diff file and so I was able to patch the associated files manual, as only text files are modified.

    Now checksetup.pl is running :-)

    Cheers,
    Thomas

  5. 25 mars 2009 à 10:02   | #6

    thanks lpsolit … now I’m ruuning Bugzilla 3.2.2 with MySQL 5.1.32

  6. monty
    27 mars 2009 à 1:13   | #7

    I’m still running into an issue on this… Hopefully you can shed some light on it?

    I just checked out Bugzilla 3.2.2, on perl 5.10.0 (Build 1004).

    I am trying to setup Bugzilla on MySQL 5.1.32, however, when I try to apply the patch, as you have instructed here, I get the following error message:

    patching file ‘Bugzilla/Config/Attachment.pm’
    Assertion failed: hunk, file patch.c, line 321

    This application has requested the Runtime to terminate it in an unusual way. Please contact the application’s support team for more information.

    Any insight into this issue would be much appreciated.

    • lpsolit
      27 mars 2009 à 1:40   | #8

      @monty: this looks like a bug in your "patch" application. I have no idea what’s going on.

  7. 27 mars 2009 à 9:50   | #9

    It’s the GNU patch version for win32 that is producing this error.

    http://gnuwin32.sourceforge.net/packages/patch.htm

    patching file Bugzilla/Config/Attachment.pm
    Assertion failed: hunk, file ../patch-2.5.9-src/patch.c, line 354

    Of course it could be any number of really obscure broken MS things.
    Install cygwin to get around this and use their patch tool.

  1. 31 mars 2009 à 5:03   | #1

Laisser un commentaire

Entrez vos coordonnées ci-dessous ou cliquez sur une icône pour vous connecter:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s

Suivre

Recevez les nouvelles publications par mail.