From: Gaute Hope <eg@gaute.vetsj.com>
To: Caitlin Matos <cm.debian@gmail.com>
Cc: "supmua@googlegroups.com" <supmua@googlegroups.com>,
Per Andersson <avtobiff@gmail.com>
Subject: Re: [sup] Sup in Debian
Date: Wed, 3 Sep 2014 09:30:20 +0200 [thread overview]
Message-ID: <CABKe4MunrgNKsx5LB3Jn2ErP9C0GR11yBY2LEepsUJyOCQ5WUg@mail.gmail.com> (raw)
In-Reply-To: <5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com>
On Tue, Sep 2, 2014 at 5:05 PM, Caitlin Matos <cm.debian@gmail.com> wrote:
> 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!
As far as I can remember this is not guaranteed, I think it depends on
what combination of ruby and sup you created the configuration files
with initially.
> 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?
I think the difference will become most apparent when using Ruby <1.8
and Ruby latest with latest Sup. The structure of the YAML file
changed, I no longer remember all the details, but the following
issues and pull requests contain the work we did on it, have a look at
#258 (also listed below) on how one user got around the issue after
the script stopped working:
Deprecation of YAML migration script:
- https://github.com/sup-heliotrope/sup/pull/268
- https://github.com/sup-heliotrope/sup/issues/266
Migration after the migration script stopped working:
- https://github.com/sup-heliotrope/sup/issues/258
Issues leading to the migration script:
- https://github.com/sup-heliotrope/sup/pull/75
- https://github.com/sup-heliotrope/sup/pull/62
- https://github.com/sup-heliotrope/sup/issues/17
- https://github.com/sup-heliotrope/sup/pull/16
One important thing to remember when doing this manually is to set the
source ids to the same as they were before - that is - matching ids in
in sources.yaml before and after migration (when manually migrating,
recreating config files). This way the source id in the index will be
correct. Otherwise things will get messy. If it works for the user to
just upgrade sup and reopen that's great, but otherwise I would
suggest running through the configuration - re-add the sources, modify
source.yaml so that the ids are matching.
A lot of stuff has happened since 0.12.0 and the upgrade path is no
longer very smooth.
Hope that helped a little.
Cheers, Gaute
next prev parent reply other threads:[~2014-09-03 7:30 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
2014-09-03 7:30 ` Gaute Hope [this message]
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=CABKe4MunrgNKsx5LB3Jn2ErP9C0GR11yBY2LEepsUJyOCQ5WUg@mail.gmail.com \
--to=eg@gaute.vetsj.com \
--cc=avtobiff@gmail.com \
--cc=cm.debian@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