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.191.36 with SMTP id gv4mr174594obc.50.1409729421308; Wed, 03 Sep 2014 00:30:21 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.182.106.13 with SMTP id gq13ls918120obb.27.gmail; Wed, 03 Sep 2014 00:30:20 -0700 (PDT) X-Received: by 10.182.47.136 with SMTP id d8mr21231523obn.10.1409729420939; Wed, 03 Sep 2014 00:30:20 -0700 (PDT) Return-Path: Received: from mail-qc0-f175.google.com (mail-qc0-f175.google.com [209.85.216.175]) by gmr-mx.google.com with ESMTPS id im3si1425203qcb.1.2014.09.03.00.30.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Sep 2014 00:30:20 -0700 (PDT) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.216.175; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) smtp.mail=eg@gaute.vetsj.com Received: by mail-qc0-f175.google.com with SMTP id c9so8093801qcz.20 for ; Wed, 03 Sep 2014 00:30:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hIiQtQKS2GopkxBTHKbv4Aw2KaK4l11HIFnWw7JvIE4=; b=lKPRmFffPAhlMfq9kGOEvpOEM1f7jYWKHzSsq1n+30YgjUv42QwxxHtbhONXEx6+90 gMsH9Z9eNOXdLdAiCURgSL8AdMdwFk5qIMAYb4wJy/xaRFF0iaHQ2iI9woFHHaddl34e eipy0KNA9b2F/TuF0g6mvdGmFu2TIccmo2F2zjPyB/q/x3efc+1hpv28XjgUc36+AHR6 3n8Ey65vm7UJ9WJodjzylaiYqmq/PSqBUuE8g06zGqqrBoaBlzU5WRSKM8I/z9h037i6 QnaQGZE0mdC/9wJo3rdlt31PmWBaR1FZiN+Fom3lgH/MFA5W5+tmIVAFFMYCNIVC3+Kf oziQ== X-Gm-Message-State: ALoCoQnJfcnPHqabjKQNg+jKPUZRlOK/D28uKIwar5i8WQTerTeD1zzIxf3p8BYUeIbxaBlIA9p7 MIME-Version: 1.0 X-Received: by 10.224.60.129 with SMTP id p1mr62774165qah.99.1409729420442; Wed, 03 Sep 2014 00:30:20 -0700 (PDT) Received: by 10.96.88.40 with HTTP; Wed, 3 Sep 2014 00:30:20 -0700 (PDT) In-Reply-To: <5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com> References: <5799e92b-475e-403e-a9e4-4b5c26a7f88d@googlegroups.com> Date: Wed, 3 Sep 2014 09:30:20 +0200 Message-ID: Subject: Re: [sup] Sup in Debian From: Gaute Hope To: Caitlin Matos Cc: "supmua@googlegroups.com" , Per Andersson Content-Type: text/plain; charset=UTF-8 On Tue, Sep 2, 2014 at 5:05 PM, Caitlin Matos 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