You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2012/09/21 11:03:08 UTC

[jira] [Created] (INFRA-5308) Derby svn commit notifications incorrectly sent to general@db

Kristian Waagan created INFRA-5308:
--------------------------------------

             Summary: Derby svn commit notifications incorrectly sent to general@db
                 Key: INFRA-5308
                 URL: https://issues.apache.org/jira/browse/INFRA-5308
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: CMS, Subversion
            Reporter: Kristian Waagan


Derby commit messages from Subversion have started appearing on general@db. They are not supposed to go there, only to derby-commits@db.

First seen on the 18th of September, just after the CMS was enabled for the DB site (INFRA-5215). Related?
The problem may exist for the other DB sub-projects also, I don't think there has been any commits since the problem was first observed.

Unsure which category to file this in, please correct as required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (INFRA-5308) Derby svn commit notifications incorrectly sent to general@db

Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Stevenson closed INFRA-5308.
---------------------------------

    Resolution: Fixed
    
> Derby svn commit notifications incorrectly sent to general@db
> -------------------------------------------------------------
>
>                 Key: INFRA-5308
>                 URL: https://issues.apache.org/jira/browse/INFRA-5308
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS, Subversion
>            Reporter: Kristian Waagan
>            Assignee: Joe Schaefer
>
> Derby commit messages from Subversion have started appearing on general@db. They are not supposed to go there, only to derby-commits@db.
> First seen on the 18th of September, just after the CMS was enabled for the DB site (INFRA-5215). Related?
> The problem may exist for the other DB sub-projects also, I don't think there has been any commits since the problem was first observed.
> Unsure which category to file this in, please correct as required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (INFRA-5308) Derby svn commit notifications incorrectly sent to general@db

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460380#comment-13460380 ] 

#asfinfra IRC Bot commented on INFRA-5308:
------------------------------------------

<variadic> r832375

                
> Derby svn commit notifications incorrectly sent to general@db
> -------------------------------------------------------------
>
>                 Key: INFRA-5308
>                 URL: https://issues.apache.org/jira/browse/INFRA-5308
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS, Subversion
>            Reporter: Kristian Waagan
>
> Derby commit messages from Subversion have started appearing on general@db. They are not supposed to go there, only to derby-commits@db.
> First seen on the 18th of September, just after the CMS was enabled for the DB site (INFRA-5215). Related?
> The problem may exist for the other DB sub-projects also, I don't think there has been any commits since the problem was first observed.
> Unsure which category to file this in, please correct as required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (INFRA-5308) Derby svn commit notifications incorrectly sent to general@db

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461383#comment-13461383 ] 

Kristian Waagan commented on INFRA-5308:
----------------------------------------

Thanks, Joe.
Tested by committing changes to Derby and the DB site - looking good.
                
> Derby svn commit notifications incorrectly sent to general@db
> -------------------------------------------------------------
>
>                 Key: INFRA-5308
>                 URL: https://issues.apache.org/jira/browse/INFRA-5308
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS, Subversion
>            Reporter: Kristian Waagan
>            Assignee: Joe Schaefer
>
> Derby commit messages from Subversion have started appearing on general@db. They are not supposed to go there, only to derby-commits@db.
> First seen on the 18th of September, just after the CMS was enabled for the DB site (INFRA-5215). Related?
> The problem may exist for the other DB sub-projects also, I don't think there has been any commits since the problem was first observed.
> Unsure which category to file this in, please correct as required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (INFRA-5308) Derby svn commit notifications incorrectly sent to general@db

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot updated INFRA-5308:
-------------------------------------

    Assignee: Joe Schaefer
    
> Derby svn commit notifications incorrectly sent to general@db
> -------------------------------------------------------------
>
>                 Key: INFRA-5308
>                 URL: https://issues.apache.org/jira/browse/INFRA-5308
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS, Subversion
>            Reporter: Kristian Waagan
>            Assignee: Joe Schaefer
>
> Derby commit messages from Subversion have started appearing on general@db. They are not supposed to go there, only to derby-commits@db.
> First seen on the 18th of September, just after the CMS was enabled for the DB site (INFRA-5215). Related?
> The problem may exist for the other DB sub-projects also, I don't think there has been any commits since the problem was first observed.
> Unsure which category to file this in, please correct as required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira