Where did old Tasks go? [was Re: git.cyrus.foundation deprecated]

Wed Dec 21 18:34:19 EST 2016

https://web.archive.org/web/20150406213645/https://git.cyrus.foundation/T16

When upgrading a Cyrus IMAP Murder (discrete), 2.4 backends do not
advertise the MOVE capability, but 2.5 frontends will -- and happily
proxy the UID MOVE command despite the fact that the backends do not
support RFC 6851[1]

So the fix is to disable MOVE on the frontend by suppressing the
capability.

Bron.

On Thu, 22 Dec 2016, at 09:34, Nic Bernstein wrote:

> Bron,

>  Darn!  The only reference I'm able to find to T16 is in commit
>  a412ffd97b26, which is about as unrelated to the issue as can be:
>
>> $ git show a412ffd97b26 commit
>> a412ffd97b2678f8bf5da967116b8759f0ebbfa1 Author: Jeroen van Meeuwen
>> (Kolab Systems) <vanmeeuwen at kolabsys.com> Date:   Tue Mar 3 02:03:21
>> 2015 +0100  Add a note on Cyrus IMAP Murder Topologies that upgrade
>> to 2.5.0  Fixes T16  diff --git
>> a/doc/source/imap/features/namespaces.rst
>> b/doc/source/imap/features/namespaces.rst index 8be8d3f..7c37603
>> 100644 --- a/doc/source/imap/features/namespaces.rst +++
>> b/doc/source/imap/features/namespaces.rst @@ -25,6 +25,8 @@ By
>> default, up to versions prior to Cyrus IMAP version *netnews*
>> namespace convention -- a ``.`` (dot) character is used as the
>> hierarchy separator.  +Further implications and limitations of this
>> convention include: + *   Mailbox names are case-sensitive, *   A
>> mailbox name may not start with a ``.`` (dot) character, *   A
>> mailbox name may not contain two ``.`` (dot) characters in a row,
>>
> This obviously has nothing to do with Murder and is just an editorial
> comment in the documentation.
> 

>  Anyone else know what T16 might have been about? :-[

>      -nic

> 

> 

> On 12/21/2016 03:19 PM, Bron Gondwana wrote:

>> Hi Nic,

>> 

>> My understanding is that Kolab had a disk failure and lost
>> git.cyrus.foundation, so I have been unable to get anything out of
>> Phabricator.
>> 

>> Unfortunately before that time I didn't have the correct
>> administrative access to be able to extract all the tasks and
>> information, so I'm going to assume everything that we did on that
>> system that wasn't in the git repositories and synced out is now
>> lost.  I'm quite annoyed with myself that I didn't at least save HTML
>> dumps of the pages that I had access to see, but I assumed I could
>> get the data out cleanly at some point in the future, so I didn't
>> push as hard as I should.
>> 

>> Regards,

>> 

>> Bron.

>> 

>> 

>> On Thu, 22 Dec 2016, at 04:15, Nic Bernstein wrote:

>>> Friends,

>>> Where did the Maniphest Tasks go when the move to github was made?

>>> 

>>> I ask because the release notes for 2.5.X say:

>>> 

>>>> Make sure to read the Upgrading to Cyrus IMAP 2.5.0[2] notes (all
>>>> of them).
>>> and those notes contain this:

>>> 

>>>> Cyrus IMAP Murder Topologies

>>>> Environments that run a Cyrus IMAP Murder topology will want to
>>>> upgrade their backends before they upgrade their frontends. See
>>>> Task #16[3] for details.
>>> But the link for Task #16 is dead, still pointing to
>>> git.cyrus.foundation:
>>> 

>>>> glop:master$ grep -iR foundation cyrus-imapd/docsrc/

>>>> cyrus-imapd/docsrc/imap/download/release-
>>>> notes/2.5/x/2.5.0.rst:Please see https://git.cyrus.foundation/.
>>>> cyrus-imapd/docsrc/conf.py:        'task':('
>>>> https://git.cyrus.foundation/T%s', 'Task #'),
>>> I'd be happy to fix that, but am unclear as to where this
>>> information now lives.
>>> 

>>> Cheers,

>>>     -nic

>>> 

>>> 

>>> On 06/23/2016 06:37 PM, Bron Gondwana via Cyrus-devel wrote:
>>>> Hi all,  Phabricator is being deprecated.  The project is moving to
>>>> github at:

>>>> https://github.com/cyrusimap/  I'm working on migrating all the
>>>> bugs from bugzilla and phabricator to be github issues.  For now
>>>> the website is still hosted at CMU.  One thing I'm doing is
>>>> applying a "kill commit" to the top of the git repositories at the
>>>> other locations.  This doesn't lose any history, you can just reset
>>>> --hard HEAD^ to get back to the latest master commit - but it does
>>>> discourage any further pushes of commits that get lost, because
>>>> they won't merge or rebase very happily on top of the kill commit!
>>>> The kill commit contains a small README.txt which tells you how to
>>>> update your git repository to point to the new location.  Cheers,
>>>> Bron.

>>>>
>>>
>>> -- Nic Bernstein                             nic at onlight.com
>>> Onlight, Inc.                             www.onlight.com 6525 W
>>> Bluemound Road, Suite 24           v. 414.272.4477 Milwaukee,
>>> Wisconsin  53213-4073

>>>
>>> Email had 1 attachment:

>>>  * nic.vcf
>>>   1k (text/x-vcard)

>> 

>> --

>>   Bron Gondwana

>>   brong at fastmail.fm

>> 

>> 

>
> -- Nic Bernstein                             nic at onlight.com
> Onlight, Inc.                             www.onlight.com 6525 W
> Bluemound Road, Suite 24           v. 414.272.4477 Milwaukee,
> Wisconsin  53213-4073
>
> Email had 1 attachment:

>  * nic.vcf
>   1k (text/x-vcard)

--

  Bron Gondwana

  brong at fastmail.fm

Links:

  1. https://web.archive.org/web/20150406213645/
     https://tools.ietf.org/html/rfc6851
  2. https://cyrusimap.org/imap/release-notes/2.5/x/2.5.0.html#imap-relnotes-2-5-0-upgrading
  3. https://git.cyrus.foundation/T16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andrew.cmu.edu/pipermail/cyrus-devel/attachments/20161222/36f2f99c/attachment.html>