The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Mailman breaks with stable upcp due to Python upgrade.

Discussion in 'E-mail Discussions' started by beddo, Aug 1, 2009.

  1. beddo

    beddo Well-Known Member

    Joined:
    Jan 19, 2007
    Messages:
    157
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    England
    cPanel Access Level:
    DataCenter Provider
    cPanel 11.24.4-S36281 - WHM 11.24.2 - X 3.9
    FREEBSD 7.0 i386 standard

    Upcp last night must have updated Python from python25-2.5.4_2 to python26-2.6.2_1. Actually looking from the logs it installed 2.6.2 as well as 2.5.4 and set the system default to 2.6. Now I get emails from the mailman cron jobs telling me:

    Code:
    /usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py:32: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
    
    From what I understand that means that the version of mailman in cpanel stable does not support python 2.6 so I've rolled back to 2.5 manually and it works again.

    Does someone need to add something to block python from being updated or roll in a mailman update to stable to stop this from hitting other people?
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    That message just seems to be a warning that the code in Mailman is relying on functionality that will eventually be removed from Python. However, this could indicate that Mailman is not fully compatible with Python 2.6. Preventing an upgrade to Python 2.6 seems to be a practical measure to take until we can propagate an updated version of Mailman to STABLE.
     
  3. beddo

    beddo Well-Known Member

    Joined:
    Jan 19, 2007
    Messages:
    157
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    England
    cPanel Access Level:
    DataCenter Provider
    Thanks for the reply, I must admit I didn't check whether it was just a warning or not and I don't even know if anyone uses mailman on the server in question - I just got several messages from different cron jobs about it.

    I did see some hits on google where people said mailman isn't compatible with 2.6 though. Is blocking the 2.6 upgrade something that we do our end or is it a change to upcp from your end? If we do it our end, is there a changelog type thing that we can keep an eye on to check for changes in mailman?

    I didn't catch one when looking for versions but may have missed it..
     
  4. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    You would handle that on your end at this time. We maintain a changelog at cPanel - The Leading Control Panel - Change Log and will make an entry when we propagate a newer version of Mailman.
     
  5. SageBrian

    SageBrian Well-Known Member

    Joined:
    Jun 1, 2002
    Messages:
    415
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    NY/CT (US)
    cPanel Access Level:
    Root Administrator
    David,
    I'm not complaining.... but.
    That changelog is not really updated as much as cPanel thinks. It can sometimes take a week for the changes to show up. Meanwhile, anyone doing automatic updates has no idea what changes were made.

    Perhaps the changelog could actually be updated at the same time the updates are made available? :)

    Consider what is available currently, and that nothing is noted about these.

    CURRENT
    11.24.5-CURRENT_37946
    (Mon Aug 3 17:42:29 2009)

    EDGE
    11.24.7-EDGE_37011
    (Fri Jul 3 00:25:04 2009) <----- (I like this one)

    Brian

    again, not complaining. just pointing out the deficiency.
     
  6. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Changelogs are updated after the builds are released because they must be manually done after the build is released. If you want to know what the changes are before updating your server, feel welcome to move your server to manual updates instead. You can do this by going to WHM -> Server Configuration -> Update config. Whenever you are ready to update, you can go to WHM -> cPanel -> Update to Latest Version.
     
  7. SageBrian

    SageBrian Well-Known Member

    Joined:
    Jun 1, 2002
    Messages:
    415
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    NY/CT (US)
    cPanel Access Level:
    Root Administrator
    Yes, I am on Manual. But, I believe you sort of proved my point.

    Here is the latest from the ChangeLog:

    Release 37629
    2009-07-27 08:18:41

    Fixes
    Fixed issue with setting CPAN mirrors during CPAN module installation
    Initialize CPAN configuration when it is missing or corrupt
    Prevent redirect loops
    Update makecpphp to handle PHP 5.2.10


    Yet, according to the releases, were are at:
    RELEASE
    11.24.5-RELEASE_37946
    (Mon Aug 3 17:57:31 2009)


    So, what changes are in the latest #37946?
    :)

    Even though 37946 is available, I don't know what it might update. I accept it as 'usual' and don't worry about it as the changelog will 'eventually' get updated. But, I'm not sure cPanel notices the delay.

    Again, this is not a complaint, just an observation. And things are sooooo much better than they were a few years ago when we had few changelog updates.
     
Loading...

Share This Page