From owner-freebsd-arm@freebsd.org Tue Jan 21 23:01:46 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3E7322259E9 for ; Tue, 21 Jan 2020 23:01:46 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 482PDV0xxvz4BQW for ; Tue, 21 Jan 2020 23:01:46 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: brd/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 1A50813F10 for ; Tue, 21 Jan 2020 23:01:46 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id D2E1C21ED6 for ; Tue, 21 Jan 2020 18:01:45 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute5.internal (MEProxy); Tue, 21 Jan 2020 18:01:45 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudelucetufdoteggodetrfdotffvucfrrh hofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurh epofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdeurhgrugcuffgr vhhishdfuceosghrugeshfhrvggvuefuffdrohhrgheqnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrrgguodhmvghsmhhtphgruhhthhhp vghrshhonhgrlhhithihqdejtdejieefvdefvddqudektdeileeikeekqdgsrhgupeephf hrvggvuefuffdrohhrghesshhoudegkhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8D3E7E00A2; Tue, 21 Jan 2020 18:01:45 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-754-g09d1619-fmstable-20200113v1 Mime-Version: 1.0 Message-Id: <08b53c96-c990-40e8-89d6-fce3fca6d5e1@www.fastmail.com> In-Reply-To: <78e72ad1-4af8-f9e8-646e-1aa8c67c7621@m5p.com> References: <78e72ad1-4af8-f9e8-646e-1aa8c67c7621@m5p.com> Date: Tue, 21 Jan 2020 16:01:24 -0700 From: "Brad Davis" To: "Robert Crowston via freebsd-arm" Subject: Re: Never mind (was: cups package?) Content-Type: text/plain X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2020 23:01:46 -0000 On Tue, Jan 21, 2020, at 3:42 PM, George Mitchell wrote: > On 2020-01-21 10:02, George Mitchell wrote: > > I'm running 11.2-RELEASE on my ancient Raspberry Pi. I recently > > deleted the cups package (because I hate CUPS and it's a pain to > > type /usr/bin/lpr all the time to get the right lpr). Then I did > > a pkg upgrade which did lots of good updates with no problem -- > > including ghostscript9-agpl-base. (ghostscript9-agpl-base was > > last updated on January 17.) Unfortunately, ghostscript9-agpl-base > > as packaged depends on libcups.so.2 libcupsimage.so.2. But I > > can't reinstall cups because it is not found in the current package > > repository. Isn't it wrong that the official repo should have an > > unsatisfied dependency, other than as a transitory problem? Help! > > -- George > > > > So I bit the bullet, set ALLOW_UNSUPPORTED_SYSTEM=1, NFS-mounted a > /usr/ports tree, set up swap on a local USB disk (which ironically > was not used), and compiled ghostscript without CUPS. Much to my > surprise, it took only six hours, and my problem is now solved. > > So to update to 11.3-RELEASE, do I have to do a source upgrade? > freebsd-update appears not to work (3 mirrors found, fetching public > key failed three times). -- George Yes, freebsd-update is not really workable (i.e. would take longer than a source upgrade) on a RPi. Regards, Brad Davis