[Build-common-hackers] Bug#725950: Bug#725950: Bug#725950: cdbs: allow version ranges in DEB_AUTO_UPDATE_foo

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2013-11-30 07:09, Vasudev Kamath wrote:
> IOhannes m zmölnig <zmoelnig at iem.at> writes:
> 
> Hi IOhannes,

hi.

sorry, it seems that i never replied to this.
could have saved some brain power...

> 
>> On 2013-10-10 17:19, Jonas Smedegaard wrote:
>>> Great approach!
>>> 
>>> I've wanted to deal with this for some time but wanted and 
>>> approach that was backporting-friendly, which this could be.
>>> 
>>> I am pretty bogged down currently - will you try implement it?
>> 
>> attached is an attempt. i don't dare to push that directly to 
>> cdbs-git.
> 
> I just checked the patch but I'm not clear how this new feature 
> should be used commit message says semicolon but eg shows usage of 
> comma instead.

yes, i mixed up the two. it should have read comma.

> I installed the patched version and did following
> 
> DEB_AUTO_UPDATE_AUTOMAKE = ,12
> 
> I was expecting it to generate automake (>= 1:1.12) but instead 
> generated version was automake (<= 12)

the idea is, that the comma delimits the lower (left-side) and the
upper (right-side) version of the b-d.

so "5,9" can be read as "at least version 5, but no more than version
9" so it would result in a versioned B-D "automake (>= 5), automake (<=9)"
otoh ",12" can be read as "i don't care about the lower version
boundary, but the version must not be higher than '12'", resulting in
"automake (<= 12)".



> which seems to me as wrong because there is no such version in 
> archive.

currently, no checks are performed whether the requested versions are
actually in the archive.
i don't think that this is necessarily false: if a package requires an
(say) automake version between 1.3 and 1.7 and none of these are
currently packaged, then the package correctly won't be able to build.



but i guess you figured that out already...

fgamsd
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJS1rmIAAoJELZQGcR/ejb4LkgP/0L21KFDHo6d2uD865tTDlxn
2XGh06V6hhibkVVXVOLduXl9LpA8Y7H4PbMzmN1JwXisw+hTfvEHfL43ztic2r7+
4JrD6zzXBJp/NvWm6EGAyHUMG0IVcnxKpYrH6N3Hd4YwwLOfgtIpjpwydq50PrAk
AcYWpVru5NXSUa1KGbXYIwratZJP/hgGDNB41NcpB5Yh5b97G7ULeSfZn4BEssSk
dZnrOWMI30shZthxTWfQwbKbUBQRIC/gvCEu68JqSlCFuF6x0Oi/RL5RfHdpLSfe
0i8HSHnSE2ogblfGUd8kLqNAo6LSNSc3NZvKYB3vXgnVImV+zSRvGrjCTxOpNpGc
7PYOlLl9Sbvjedz/82FVb9Dvyc/fw5ju/53C4gbSFD1djw/8jJFdny5UQSt5RxRM
yK4KibzNlu/wSf3TdNtSsCPcjbh35/hQKuLJrEkD5DY2fkZdJDfZLePHLxC+r++z
rT+jo0DXUfXp6a0gsplIzFlM8l4q+Vp08JbdpYpfy6VhS/aNsufEqQq0BSI08nPz
NScOpIrykPpLfzgcFEuCSHDrkn/pTra2JrHpL8DtF2t0Odt6xYDLxDKE3yDDsEHf
ao2hVSN/oRBSZd0qzmgShGYgoCS75h8T4hPZznsgTydEnNitzYyGQDVUzddUnHlN
OmrOPw9AKD5d3P+R4wNI
=0MOC
-----END PGP SIGNATURE-----