From: Caitlin Matos <cm.debian@gmail.com>
To: supmua@googlegroups.com
Cc: avtobiff@gmail.com
Subject: Re: [sup] Sup in Debian
Date: Tue, 2 Sep 2014 08:05:17 -0700 (PDT) [thread overview]
Message-ID: <5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com> (raw)
In-Reply-To: <CABKe4MsYeMSB42=MOmnN1H7Yh5bH+sWPE9Q=qrJgWVD8kumZ6g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2688 bytes --]
Hi Gaute,
A few days ago, I updated that wiki migration page to better reflect what a
user can do if using Ruby 2.1. I did this specifically with the intent of
redirecting Debian users who are updating.
However, I updated it to the best of my understanding. Having not worked
with syck, I am unfamiliar with the differences. In researching the issue
via Google, I was under the impression that simply leaving the config files
as-is would likely suffice. If you believe this is not the case, please
update what I wrote on the wiki!
I tried creating a configuration with both 0.12.1 and 0.19.0, and there
were no obvious differences in the files themselves. Can you clarify what
should be changed if one was to manually recreate the config by hand?
Thanks,
Caitlin (Debian Ruby team)
On Tuesday, August 26, 2014 4:34:15 AM UTC-4, Gaute Hope wrote:
>
> On Mon, Aug 25, 2014 at 11:34 PM, Per Andersson <avto...@gmail.com
> <javascript:>> wrote:
> > Hi!
> >
> > I am the maintainer for the Sup package in Debian, sup-mail.
> >
> > There are a few open questions which, together with lack of
> > time, have ended up in the situation where sup-mail was
> > removed from Debian.
> >
> > I want to reintroduce it of course.
>
> Yay!
>
>
> > The questions:
> >
> > I can't find if rmail and rmail-sup have merged upstream.
> > Is there any activity in 1) original rmail, 2) migration away
> > from rmail?
>
> No. I am afraid not.
>
> > What are the difference between rmail and rmail-sup?
>
> https://github.com/sup-heliotrope/rmail-sup/compare/upstream_matta...master
>
> > (I am thinking that maybe the Debian package should switch
> > upstream source from rmail to rmail-sup.)
> >
> > The last package in Debian (stable) is 0.12.1, what is the
> > migration path to current release, 0.19.0?
>
> https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14
>
> But the migration script for the config files does not work with newer
> versions of Ruby, that means you need to re-create your config set up.
>
> 0.12.1 is way out of date! It is, unfortunately, beyond the time I've
> had to maintain a clean migration path from it up to the current
> release. It is from pre ruby 1.9.
>
> Something like this should work:
>
> o. back up ~/.sup and remove the config files from ~/.sup
> o. use sup-dump to back up the index
> o. upgrade sup
> o. manually recreate the config either using sup-config or by hand
> o. set up sources.yaml to match your previous sources.yaml
> o. new sup should work with the db, make sure that _source ids_ match
> in new configs!!
> o. alternatively, re-index and sup-import the dump.
>
>
>
> Cheers, Gaute
>
[-- Attachment #1.2: Type: text/html, Size: 4314 bytes --]
next prev parent reply other threads:[~2014-09-02 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 21:34 Per Andersson
2014-08-26 8:34 ` [sup] " Gaute Hope
2014-09-02 15:05 ` Caitlin Matos [this message]
2014-09-03 7:30 ` Gaute Hope
2014-10-02 6:17 ` Per Andersson
2014-10-02 15:23 ` Gaute Hope
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com \
--to=cm.debian@gmail.com \
--cc=avtobiff@gmail.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox