| 2006-10-26 05:56:56 |
Stuart Bishop |
bug |
|
|
added bug |
| 2006-10-26 12:58:23 |
David Allouche |
bug |
|
|
added subscriber Matthew Paul Thomas |
| 2006-10-26 12:59:11 |
David Allouche |
launchpad: statusexplanation |
|
|
|
| 2006-10-30 14:58:22 |
David Allouche |
description |
The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect. |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
David thinks the source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import. |
|
| 2006-10-30 14:58:22 |
David Allouche |
title |
Python trunk reporting SVN repository as a file:// URL |
vcs impot details are not distinguished from informational vcs details |
|
| 2006-10-30 14:58:36 |
David Allouche |
launchpad-bazaar: status |
Unconfirmed |
Confirmed |
|
| 2006-10-30 14:58:36 |
David Allouche |
launchpad-bazaar: importance |
Undecided |
Medium |
|
| 2006-10-30 14:58:48 |
David Allouche |
title |
vcs impot details are not distinguished from informational vcs details |
vcs import details are not distinguished from informational vcs details |
|
| 2006-12-15 17:07:55 |
David Allouche |
launchpad-bazaar: importance |
Medium |
High |
|
| 2006-12-15 17:07:55 |
David Allouche |
launchpad-bazaar: statusexplanation |
|
Fixing this bug is a prerequisite for fixing bug 2649. Raising the importance of this bug to High. |
|
| 2007-03-16 02:59:25 |
Tim Penhey |
launchpad-bazaar: assignee |
|
ddaa |
|
| 2007-03-16 02:59:25 |
Tim Penhey |
launchpad-bazaar: statusexplanation |
Fixing this bug is a prerequisite for fixing bug 2649. Raising the importance of this bug to High. |
Some refactoring of the data model is needed, and will separate the configuration for import branches from product series |
|
| 2007-03-16 16:09:30 |
David Allouche |
description |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
David thinks the source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import. |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import. |
|
| 2007-03-23 19:52:40 |
David Allouche |
description |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import. |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import.
Related to bug 2649. |
|
| 2007-04-04 16:15:59 |
David Allouche |
launchpad-bazaar: importance |
High |
Medium |
|
| 2007-04-04 16:15:59 |
David Allouche |
launchpad-bazaar: statusexplanation |
Some refactoring of the data model is needed, and will separate the configuration for import branches from product series |
Lowering importance to medium because it will require major database schema changes. |
|
| 2007-04-04 16:21:25 |
David Allouche |
description |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import.
Related to bug 2649. |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import.
Related to bugs 2649 and 95180. |
|
| 2007-04-04 16:21:36 |
David Allouche |
description |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import.
Related to bugs 2649 and 95180. |
Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.
UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.
The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).
There should be an obvious distinction between vcs details in the registry, and vcs details for import.
Related to bug 2649 and bug 95180. |
|
| 2007-09-06 23:41:01 |
David Allouche |
launchpad-bazaar: assignee |
ddaa |
|
|
| 2008-07-08 06:33:59 |
Jonathan Lange |
launchpad-bazaar: status |
Confirmed |
Incomplete |
|
| 2008-07-08 06:33:59 |
Jonathan Lange |
launchpad-bazaar: assignee |
|
mwhudson |
|
| 2008-07-08 21:09:08 |
Michael Hudson-Doyle |
launchpad-bazaar: status |
Incomplete |
Fix Released |
|
