From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 44938821632 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,943cc8ed563c421c X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.66.141.70 with SMTP id rm6mr6637988pab.37.1408782053940; Sat, 23 Aug 2014 01:20:53 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.51.17.97 with SMTP id gd1ls367946igd.22.canary; Sat, 23 Aug 2014 01:20:53 -0700 (PDT) X-Received: by 10.42.133.200 with SMTP id i8mr9233469ict.14.1408782053658; Sat, 23 Aug 2014 01:20:53 -0700 (PDT) Return-Path: Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by gmr-mx.google.com with ESMTPS id cj6si6008839qcb.1.2014.08.23.01.20.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 Aug 2014 01:20:53 -0700 (PDT) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.216.181; 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-f181.google.com with SMTP id x13so11808844qcv.26 for ; Sat, 23 Aug 2014 01:20:53 -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=ldK8yvathVMNVee5HxIJHzq1X7gs8KSlTymAWV3A2ss=; b=nE0QSijssH4aIgY6ZDcxl8YUFjv4HU1ARdBhvsCIR2Qhenrsr2Gxo5V0hRk/+tyMSP MFI4FQP9+EU5ZHoL2kkvC0M+sB9n539ABnSSUUUt43UeVTSthSning8nhdoFRbhDQosj M2fvAJ/uiYuKt9OsqP8Y4pH9p0jazrScPWPa7aBFVEsMdL1AZhLRv8yGaC7dTHyrguel bLJceu3f0wS0CnSNbCadrB+0IaLRfbLnaO0JWUvLw4l+6CZBKVWZp1Fc1Q2Eq7V2zLvY Sfa+AVGVoLP6unmlucpchC6fGItbPMTtlsCwjYMXL5aEBq2rn2fJ/UfPcJp/lofEZRg2 lm7w== X-Gm-Message-State: ALoCoQlirGpHsTc+PBUmUc7fMMvA3RLCfO2+ghdScD+vHlcXJWBQEHk8JMnkqGdne2AXVwsUicov MIME-Version: 1.0 X-Received: by 10.140.91.229 with SMTP id z92mr15033948qgd.8.1408782053030; Sat, 23 Aug 2014 01:20:53 -0700 (PDT) Received: by 10.96.88.40 with HTTP; Sat, 23 Aug 2014 01:20:52 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Aug 2014 10:20:52 +0200 Message-ID: Subject: Re: [sup] Sup being removed from Debian From: Gaute Hope To: Ian Munsie Cc: "supmua@googlegroups.com" Content-Type: text/plain; charset=UTF-8 On Sat, Aug 23, 2014 at 4:06 AM, Ian Munsie wrote: > Hi All, > > It looks like the version of Sup in Debian is slated to be removed due to a > dependency on ruby 1.9 which has been removed, and a mixup thinking Sup's > upstream had vanished after it moved away from Rubyforge. > >> Someone needs to jump on this if the want to prevent removal. It needs to >> be updated to work with ruby2.1 very soon. > > > I haven't been following upstream development but I don't want to see this > removed from Debian - has the latest version already been updated to support > Ruby 2.1, or can it easily be updated? > > The relevant Debian bug reports are here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758515 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747878 Hi, Yeah, Sup should run on ruby 2.1. The latest version is 0.19.0 which is to be got from here: http://rubygems.org/gems/sup or https://github.com/sup-heliotrope/sup/releases. Note that sup wasn't removed from Rubyforge, Rubyforge was shut down. Sup development is happening here: https://github.com/sup-heliotrope/sup Cheers, Gaute