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.183.3.4 with SMTP id bs4mr4392870obd.47.1409042055150; Tue, 26 Aug 2014 01:34:15 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.50.41.36 with SMTP id c4ls1858133igl.44.gmail; Tue, 26 Aug 2014 01:34:14 -0700 (PDT) X-Received: by 10.68.222.194 with SMTP id qo2mr17348125pbc.6.1409042054884; Tue, 26 Aug 2014 01:34:14 -0700 (PDT) Return-Path: Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) by gmr-mx.google.com with ESMTPS id k7si583486qcm.2.2014.08.26.01.34.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 01:34:14 -0700 (PDT) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.216.52; 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-qa0-f52.google.com with SMTP id j15so13261660qaq.39 for ; Tue, 26 Aug 2014 01:34:14 -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=uwIFLfef+4I+cUA8YozPg035lThCY1z4rgs/18GWZ1Q=; b=FrHh5vaT0ubZjy2tfzAJMLCDTLfMpNkmLn/g80z1OfZJpx853pKXlpoOYoCBYvFNUV VtLUeHQEpb3P7CzfJErMqQkVR/wO912GRqWVcNdaYxpcGMpYWw/31Dw5k1kIVV7xeVyw gU9vy5j9pzCUVcY8642p9jo67ykQwPBHZJwrvtP2xwVvSjvmfOkxab/1OPRD2UGfpEZ8 +IpaLFa2dnAEkshEcoRYJVplynOqZ/lFSG8CJPue6Mnpn6EhfBGtlsehCcUvkeA9WehJ dh5AFqMTDwFV2oWGRkk1TrSlVJpnVgZpeY83U/+XOX91Ey7aO6abYrWfjw3RZ6Ny7xLW 8NsA== X-Gm-Message-State: ALoCoQnByh8d5x4I6XZOsn+BZsOtohv/Ram7f038R+l8qOBez87z5/Lj7S4CNLXzhltOiaB+EyPQ MIME-Version: 1.0 X-Received: by 10.224.115.79 with SMTP id h15mr24453228qaq.21.1409042054381; Tue, 26 Aug 2014 01:34:14 -0700 (PDT) Received: by 10.96.88.40 with HTTP; Tue, 26 Aug 2014 01:34:14 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Aug 2014 10:34:14 +0200 Message-ID: Subject: Re: [sup] Sup in Debian From: Gaute Hope To: Per Andersson Cc: "supmua@googlegroups.com" Content-Type: text/plain; charset=UTF-8 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