Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

buildbot error when pushing to 2.5 branch? #55790

Closed
orsenthil opened this issue Mar 17, 2011 · 8 comments
Closed

buildbot error when pushing to 2.5 branch? #55790

orsenthil opened this issue Mar 17, 2011 · 8 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@orsenthil
Copy link
Member

BPO 11581
Nosy @loewis, @smontanaro, @orsenthil, @bitdancer
Files
  • bb-error.txt
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2011-03-18.15:57:04.695>
    created_at = <Date 2011-03-17.07:02:19.925>
    labels = ['type-bug']
    title = 'buildbot error when pushing to 2.5 branch?'
    updated_at = <Date 2011-03-18.15:57:04.693>
    user = 'https://github.com/orsenthil'

    bugs.python.org fields:

    activity = <Date 2011-03-18.15:57:04.693>
    actor = 'r.david.murray'
    assignee = 'none'
    closed = True
    closed_date = <Date 2011-03-18.15:57:04.695>
    closer = 'r.david.murray'
    components = []
    creation = <Date 2011-03-17.07:02:19.925>
    creator = 'orsenthil'
    dependencies = []
    files = ['21263']
    hgrepos = []
    issue_num = 11581
    keywords = []
    message_count = 8.0
    messages = ['131229', '131268', '131298', '131309', '131310', '131330', '131331', '131332']
    nosy_count = 5.0
    nosy_names = ['loewis', 'skip.montanaro', 'orsenthil', 'r.david.murray', 'python-dev']
    pr_nums = []
    priority = 'normal'
    resolution = 'wont fix'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue11581'
    versions = []

    @orsenthil
    Copy link
    Member Author

    When pushed a change to 2.5 branch, I got an error, which I think has
    to do with buildbot not available for 2.5 codeline.
    It asked me to notify the tracker and here it is.

    remote: state = method(*args, **kw)
    remote: File "/data/buildbot/master/master.cfg", line 87, in
    perspective_addChange
    remote: changedict['category'] =
    branch_to_category[changedict['branch']]
    remote: exceptions.KeyError: '2.5'
    remote: ]
    remote: sent email to roundup at report@bugs.python.org

    @smontanaro
    Copy link
    Contributor

    Should you be pushing anything to 2.5?

    @orsenthil
    Copy link
    Member Author

    On Thu, Mar 17, 2011 at 05:15:09PM +0000, Skip Montanaro wrote:

    Should you be pushing anything to 2.5?

    I think, there is a security release planned in 2011.
    Also, see bpo-11442 which was the specific case for pushing to 2.5.

    @smontanaro
    Copy link
    Contributor

    Yes, but this is not a security issue.

    @orsenthil
    Copy link
    Member Author

    bpo-11442 is a security issue and I pushed to 2.5 for fixing that and
    encountered this problem with buildbot. I think, we may/may not fix
    this (buildbot issue) depending upon when the 2.5 release may be
    planned.

    @bitdancer
    Copy link
    Member

    I talked to Martin. He wants the 2.5 mercurial branch to get *exactly* that set of changes that needs to be applied to the svn repository in order for him to build the security release, no more no less. Note that 2.5 goes out of security maintenance in November.

    @orsenthil
    Copy link
    Member Author

    David, from you message I understand that Martin is planning to
    release 2.5 via svn. If that is the case, whatever was pushed for
    security fix to hg can remain as such and so that those can be
    exported to svn.

    The bugs related to buildbot and svn keyword for 2.5, can then be
    ignored and closed.

    @bitdancer
    Copy link
    Member

    Yes, although there may be another answer on the compile bug.

    @bitdancer bitdancer added the type-bug An unexpected behavior, bug, or error label Mar 18, 2011
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    3 participants