Date: Mon, 15 Dec 2014 10:39:21 -0600 From: Rusty Nejdl <rnejdl@ringofsaturn.com> To: Guido Falsi <madpilot@freebsd.org> Cc: ports@freebsd.org Subject: Re: Giving Up Maintainership Message-ID: <assp.0426874822.a12afa6839a6fa87a1d439fa545fd357@ringofsaturn.com> In-Reply-To: <548EF8D5.8090005@FreeBSD.org> References: <f8d1a4f608dd7e845dd07fce240ca7a9@ringofsaturn.com> <548EF8D5.8090005@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-12-15 09:05, Guido Falsi wrote: > On 12/15/14 15:09, Rusty Nejdl wrote: > >> Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance. > >> CALIBRE [2] Ebook management application > > I'll take this one since I use it. I'll commit the maintainer change > later today. > > Unluckily upgrading it will be a problem since new version depends on > Python QT5 libraries. > > So I take a chance to ask: > > Is there any active work on creating ports for these? > > Who should I talk about this to? I had to completely stop on Calibre because of the dependency on QT5. I did start on 2.1.0 and can send you the pieces if that will help. Rusty From owner-freebsd-ports@FreeBSD.ORG Mon Dec 15 17:12:44 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E81FD142 for <freebsd-ports@freebsd.org>; Mon, 15 Dec 2014 17:12:44 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78CC6AC3 for <freebsd-ports@freebsd.org>; Mon, 15 Dec 2014 17:12:43 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id bs8so11177884wib.5 for <freebsd-ports@freebsd.org>; Mon, 15 Dec 2014 09:12:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bgBam6sIFJx2OJIopUxthfhlOK1ChumyTL3yZktzFXg=; b=AP1f754L1pwZ6qs/fZs42yrpAIElrVkyF162WHT0uSsqUgL/CB/nLvavJdoH1HZe+L AmiQ0BvYGA5LO6k4/1hYQ0BsbyqpCblzHBMwKz0rGzRfeTr90BksTL6aBsPrg5iSaVUs YLBNfGcI5doQoL2gfVtoa8kHZPpBFU4tqVxyKuBsVECj6iSM3SmmLCMThVdKczq/4Lrj /CWmJfgW5D0R+yyzL/3upqfX0rI6SSTv01c4xavhRp7IuEoGTeItQNsP7SX+Q0BiiDvQ jKtCZZRUevIVxW5OvWQtPZw7B3tr9w7EmaX5MITTDxqeVTFwIuVdqTA2whRz5nLf73n1 ElGA== X-Gm-Message-State: ALoCoQkCELdfHFQc5WPI9LilxtZN2T2FYo/BCAfECzUMZnMRrSQuOa1ogk4+QAfl4jYuk4J/OcFk X-Received: by 10.194.5.227 with SMTP id v3mr54666834wjv.63.1418660037021; Mon, 15 Dec 2014 08:13:57 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id h8sm13776858wiy.17.2014.12.15.08.13.56 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Dec 2014 08:13:56 -0800 (PST) Message-ID: <548F0852.2050605@multiplay.co.uk> Date: Mon, 15 Dec 2014 16:12:02 +0000 From: Steven Hartland <killing@multiplay.co.uk> User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Jeffrey Bouquet <jeffreybouquet@yahoo.com>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: Another pkg showstopper-- more information References: <1418408422.13975.YahooMailBasic@web140904.mail.bf1.yahoo.com> <548B332F.3000502@multiplay.co.uk> <548B4092.9000605@yahoo.com> <548EF83C.2060909@multiplay.co.uk> <548EFBF2.4040003@yahoo.com> In-Reply-To: <548EFBF2.4040003@yahoo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 15 Dec 2014 17:12:45 -0000 On 15/12/2014 15:19, Jeffrey Bouquet wrote: > On 12/15/14 07:03, Steven Hartland wrote: >> On 12/12/2014 19:22, Jeffrey Bouquet wrote: >>> On 12/12/14 10:25, Steven Hartland wrote: >>>> Unless I'm missing something you don't actually provide any >>>> information about the issue your actually seeing? >>>> >>>> I personally have already updated 10 or so boxes with a wide range of >>>> packages to pkg 1.4 and apart from a change with the handling of pkg >>>> upgrade -f <pkg>, which was an intended fix, I didn't have any >>>> problems. >>>> >>>> So not sure what your "show stopper" is or what you think could be >>>> tested more thoroughly (don't forget the call for testing did go out >>>> the other week, so looks like there was quite a bit of opportunity to >>>> get involved. >>>> >>>> Regards >>>> Steve >>>> >>>> On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote: >>>>> Reverted to pkg, by build, and FORCE PKG REGISTER. >>>>> >>>>> pkgs still cannot be installed. >>>>> >>>>> Still stuck with ports ( however portupgrade -- non-packages -- seems >>>>> to be >>>>> working with this pkg << pkg-devel downgrade ) >>>>> >>>>> (/ portmaster? == no, cannot get >>>>> handle, lock on database) only. >>>>> >>>>> ..............###########...............##################........... >>>>> >>>>> Should pkg and/or pkg-devel be more thoroughly tested before >>>>> release into the tree? No other pkg usually hints at similar pkg >>>>> system(s) breakage without a proven recovery/rollback procedure >>>>> already documented... similar to what portupgrade does with its >>>>> saving of shared libraries prior to upgrade of a port. >>>>> _______________________________________________ >>>>> To unsubscribe, send any mail to >>>>> "freebsd-ports-unsubscribe@freebsd.org" >> Bringing the list back into this, as its not my area: >> >>> pkg install wants to install extra ports and abort traps >> You'll want to post details about, OS version, pkg version, and the >> exact error with any stack trace >>> pkg add a "pkg fetched" file, cannot install it by package, wrong >>> architecture >>> (freebsd >> FreeBSD or vice versa, setting somewhere, etc) >> This doesn't make any sense to me, to others it may do but, always >> best to include proper steps and the output of the commands so people >> know exactly what your doing and the issue your seeing. >>> portupgrade works on some ports still, but machine > machine broken >>> because of pkg issues >>> and portupgrade -P broken similarly >>> >>> portmaster cannot install, convoluted error (lock on database and/or >>> already installed error(s)) >>> >>> So the /var/db/pkg build machine functionality also the portmaster -P >>> portupgrade -P >>> are broken. Here. Maybe these could be tested on all architectures >>> before each new package >>> upgrade? Another layer of machines, so to speak, "just because NOT " >> Again you don't provide any real details of the issues, you might of >> well have said "its broken" >>>>> of SQlite.. ... one >>> used to not have to post to the list or even subscribe to have reliable >>> LAN build set. >>> > I just updated 195471 bugzilla with a two week update. Fixed > (temporarily?) the wrong > architecture error with a missing pkg.conf file or reversion of one of > them which was not > missing, and have a workaround for the errors that remain, but it is > tedious and > worrisome, to say the least. Compared to how it could be with more SQL > coders on > board... maybe. Cant say I've ever had any issues, its always just worked, so worth posting your customizations. > > Made a post in a thread on the forums with the same information as the > update in > the PR above. > > For what it is worth... > Just read the digest of Freebsd-STABLE that arrived today, others are also > disillusioned with the priority given to pkg(ng) fixes for what was > once a not-exact but > very reliable packaging system across releases. > > > > Thanks for forwarding to the list. Unsure with each email sent > precisely the number of > recipients, but the fewer, the more likelihood the sometimes "could not > be sent" appears... > > Mostly wishing for a procedure to fix it before needing to upgrade to > v10 !! Never had to > reinstall since v5.0x AFAIK... Copying to the list again. You might want to see if you have a reply to list or reply to all option in your mail client there Jeffrey, as I said this not my area but the pkgng are very good, so given the right information I'm sure someone will be able to help. Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?assp.0426874822.a12afa6839a6fa87a1d439fa545fd357>