From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 77510737920 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,f7453156d9f2b0f9 X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.182.213.105 with SMTP id nr9mr19882560obc.36.1409670319247; Tue, 02 Sep 2014 08:05:19 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.182.22.18 with SMTP id z18ls847730obe.83.gmail; Tue, 02 Sep 2014 08:05:18 -0700 (PDT) X-Received: by 10.182.225.167 with SMTP id rl7mr75008obc.13.1409670318703; Tue, 02 Sep 2014 08:05:18 -0700 (PDT) X-Google-Doc-Id: 41d2bfd7602aeb6c X-Google-Web-Client: true Date: Tue, 2 Sep 2014 08:05:17 -0700 (PDT) From: Caitlin Matos To: supmua@googlegroups.com Cc: avtobiff@gmail.com Message-Id: <5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com> In-Reply-To: References: Subject: Re: [sup] Sup in Debian MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_179_732967374.1409670317954" X-Google-Token: EK25l6AF7-Goh1ponbI0 X-Google-IP: 99.229.22.143 ------=_Part_179_732967374.1409670317954 Content-Type: multipart/alternative; boundary="----=_Part_180_1016455626.1409670317954" ------=_Part_180_1016455626.1409670317954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 > 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 > ------=_Part_180_1016455626.1409670317954 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Gaute,

A few days ago, I updated that wiki migra= tion page to better reflect what a user can do if using Ruby 2.1. I did thi= s 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 confi= g files as-is would likely suffice. If you believe this is not the case, pl= ease update what I wrote on the wiki!

I tried creating a configurati= on with both 0.12.1 and 0.19.0, and there were no obvious differences in th= e files themselves. Can you clarify what should be changed if one was to ma= nually 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.c= om> 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
------=_Part_180_1016455626.1409670317954-- ------=_Part_179_732967374.1409670317954--