From owner-freebsd-questions@freebsd.org Tue Dec 13 14:56:16 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06999C75198 for ; Tue, 13 Dec 2016 14:56:16 +0000 (UTC) (envelope-from mfv@bway.net) Received: from smtp1.bway.net (smtp1.bway.net [216.220.96.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D9E071809 for ; Tue, 13 Dec 2016 14:56:15 +0000 (UTC) (envelope-from mfv@bway.net) Received: from gecko4 (host-216-220-115-54.dsl.bway.net [216.220.115.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: m1316v@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id 0F59E95894; Tue, 13 Dec 2016 09:56:11 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bway.net; s=mail; t=1481640971; bh=XiXe4lzTvpOxvr0dp8d5Oh+jrNk5PwJmzhvtlotgNFU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:Reply-To; b=T15IWwn9YD24ixImdgKmCo2gzTYnr0WuLlnpxCp5PbKotDZ83kUiWwQAHZAcz0QxC CQe5qdxV7F3N0ucE55gH60YxwigI8UrT/P/iVvUZOaKkW5iX2XZTvPvK81EW2Bq/Vm s+S1FcCA+J4pFS8iQIaTcNGfqDPgsGsCoqyJtyRo= Date: Tue, 13 Dec 2016 09:56:10 -0500 From: mfv To: Peter Harrison via freebsd-questions Cc: Peter Harrison Subject: Re: Chromium pkg not updated... Message-ID: <20161213095610.7736fb8a@gecko4> In-Reply-To: References: Reply-To: mfv@bway.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 14:56:16 -0000 > On Mon, 2016-12-12 at 22:52 Peter Harrison via freebsd-questions > wrote: > >Hello list. > >Anyone know why the chromium pkg doesn't seem to be being updated even >though the port is? > >Cheers, > > > >Peter Harrison. >_______________________________________________ >freebsd-questions@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to >"freebsd-questions-unsubscribe@freebsd.org" Hello, I noticed the same situation and sent the following message to freebsd-pkg yesterday: --- Infrequently, I've noticed that the pkg system seems to get constipation, that is, a build process is marked as stopped:done: but the repository is not updated. The data for the most recent incident follows: According to http://pkg.freebsd.org/freebsd:10:x86:64/latest/ the date/time of the last repository is dated 2016-Dec-06 10:16, that is, 6 days ago. However since then there have two builds as per http://beefy6.nyi.freebsd.org/jail.html?mastername=101amd64-default: Build# stopped:done: ------ ----------------- 428092 2016-12-09 08:02 428262 2016-12-11 08:10 Thus, the last build was finished more than a day ago. But a 'pkg update' results in the following message: Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Just wondering why a build status is marked as stopped:done: but the repository is not updated. In any event I'm very pleased with the pkg system. Many thanks and kudos to the developers. --- No reply so far. Cheers ... Marek