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

[Bron Gondwana]

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[1] 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[2] 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






Links:

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