Re: Bug in upset? [Was: Re: R: Problem [1.7]: link /bin/lzma -> xz]

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

On Sun, Mar 22, 2009 at 03:25:31PM -0400, Charles Wilson wrote:
>Ken Brown said:
>> Has this been taken care of? I'm seeing 4.32.7-2 as the current version of lzma when I run setup-1.7.exe rather than 4.32.7-3.
>
>Interesting.  I just looked at the setup.hint on sourceware (release-2
>area):
>
>category: _obsolete
>requires: xz
>sdesc: "removed package"
>ldesc: "Compatibility package to force installation of replacement"
>curr: 4.32.7-3
>prev: 4.32.7-2
>
>Which seems right, Then, in setup-2.ini:
>
>@ lzma
>sdesc: "Removed package"
>ldesc: "Compatibility package to force installation of replacement"
>category: _obsolete
>requires: xz cygwin
>[prev]
>version: 4.32.7-2
>install: release-2/lzma/lzma-4.32.7-2.tar.bz2 162142
>ffe2c623c69e07251ad8ed5560425fee
>source: release-2/lzma/lzma-4.32.7-2-src.tar.bz2 486990
>2945e37b4f6b76f3fc3895f90d2c4737
>
>So, I'm not sure if there's a bug in upset (the setup*.ini generator),
>or if it's working as it is supposed to (logically, if a package is
>_obsolete, then there is no "current" version).
>
>If the latter, then I need to figure out how to get "the right thing"
>into setup*.ini.
>
>However, an argument for the former (e.g. a bug in upset): the setup.ini
>for cygwin-1.5 has:
>
>@ lzma
>sdesc: "Removed package"
>ldesc: "Compatibility package to force installation of replacement"
>category: _obsolete
>requires: xz
>version: 4.32.7-3
>install: release/lzma/lzma-4.32.7-3.tar.bz2 14
>4059d198768f9f8dc9372dc1c54bc3c3
>source: release/lzma/lzma-4.32.7-3-src.tar.bz2 14
>4059d198768f9f8dc9372dc1c54bc3c3
>[prev]
>version: 4.32.7-2
>install: release/lzma/lzma-4.32.7-2.tar.bz2 162142
>ffe2c623c69e07251ad8ed5560425fee
>source: release/lzma/lzma-4.32.7-2-src.tar.bz2 486990
>2945e37b4f6b76f3fc3895f90d2c4737
>
>And the two lzma/setup.hints are identical.
>
>Chris, any suggestions?

I don't understand how you'd posit this as an upset bug if upset is
working correctly for the release directory.  That implies a difference
between the two directories, not an upset bug.

And, in fact, there was no lzma-4.32.7-3*tar.bz2 files in the lzma
directory.  Apparently they were deleted on March 16.  I ressurrected
them.

Since release-2 isn't supposed to have obsolete stuff in it can't we
just remove this directory entirely?

cgf

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