DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=D3Ox/6694XVnr4r+
	7OaynDpBLRnI+vxnyok3Ak1fD5Lxbzk6jHheMdzuLtvvuCHnmayzGnGjK24xpWv7
	Z4x/wP/hYeqHBxAK9yxI0HZcc1oXxETpnsKiVn4Rp/gAtpNn0CX2E0y6Xi8oultp
	xKXckcVQMnU02ZLTX8yQ8wvzOkM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Setup-x86_64 and Cygwin 64 Latest Updates - Packages NOT Upgraded
To: cygwin AT cygwin DOT com
References: <832845fb-1518-8c64-2aeb-b2afe951f023 AT SystematicSw DOT ab DOT ca>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <462498a0-9a77-8d24-49e4-ed04cf171f01@gmail.com>
Date: Fri, 31 Mar 2017 23:18:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <832845fb-1518-8c64-2aeb-b2afe951f023@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 31/03/2017 23:03, Brian Inglis wrote:
> Just updated to latest Setup-x86_64 and Cygwin 64 packages.
>
> Cross-checking setup and installed releases I find installed:
>
> $ egrep '^(libproj9|libslang2|perl-Carp)\s' /etc/setup/installed.db
> libproj9 libproj9-4.9.3-1.tar.bz2 0
> libslang2 libslang2-2.3.1pre17-1.tar.bz2 0
> perl-Carp perl-Carp-1.3301-2.tar.bz2 0
>
> but setup.ini shows:
>
> $ awk '/^@ (libproj9|libslang2|perl-Carp)$/,/^version:\s/' \
> 	`apt cache`/mirror/$HOSTTYPE/setup.ini | \
> 	egrep '^(@|version:)\s'
> @ libproj9
> version: 4.9.2-1
> @ libslang2
> version: 2.3.1a-1
> @ perl-Carp
> version: 1.38-1

on 64 bit libproj9 version seems only 4.9.2-1 for X86_64.
I will look whats happened.

for libslang2 you need to force update as
libslang2-2.3.1pre17-1 > 2.3.1a-1

An improvement on revision (0.x instead of 1)
was done to avoid this pitfall, but in this case
it was too late.

>
> Are dependencies only auto-updated when the manually
> picked packages that depend on them are?
>
> Could these packages now be orphans if their original manually
> picked parent packages changed their dependencies?
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple