| 2012-11-06 21:19:16 |
Stefano Rivera |
description |
If a package exists in ${DEVELOPMENT_RELEASE}-proposed and ${DEVELOPMENT_RELEASE}, syncpackage and requestsync give different results. Syncpackage checks against -proposed be default, while requestsync checks against proposed only if a package doesn't exist in -release. At the time I did these requests, 1.1.2-1 was in raring-proposed:
$ requestsync -d experimental shiboken
W: Target release missing - assuming raring
Consider using syncpackage(1) for syncs that do not require feature freeze exceptions.
Currently the bug report looks like:
Summary (one line):
Sync shiboken 1.1.2-2 (universe) from Debian experimental (main)
Description:
Please sync shiboken 1.1.2-2 (universe) from Debian experimental (main)
Changelog entries since current raring version 1.1.1-1:
shiboken (1.1.2-2) experimental; urgency=low
* Add python{,3}-numpy-dbg to Build-Depends to have all tests pass.
* Make dbg tests build-critical.
-- Didier Raboud <odyx@debian.org> Mon, 29 Oct 2012 10:06:19 +0100
shiboken (1.1.2-1) experimental; urgency=low
* New 1.1.2 "Alaursa" release.
- Add 6 1.1.2-specific symbols;
* Update B-Ds:
- add python{,3}-numpy to succeed all tests.
-- Didier Raboud <odyx@debian.org> Tue, 04 Sep 2012 08:47:15 +0200
Edit [y|N]? ^C
User abort.
$ syncpackage -d experimental shiboken
syncpackage: Source shiboken -> raring/Proposed: current version 1.1.2-1, new version 1.1.2-2
syncpackage: New changes:
shiboken (1.1.2-2) experimental; urgency=low
* Add python{,3}-numpy-dbg to Build-Depends to have all tests pass.
* Make dbg tests build-critical.
-- Didier Raboud <odyx@debian.org> Mon, 29 Oct 2012 10:06:19 +0100
Sync this package [y|N]? y
syncpackage: Request succeeded; you should get an e-mail once it is processed.
The syncpackage behavior is the one we want. |
== SRU ==
[IMPACT]
requestsync doesn't check proposed, and will include too many changelog entries in the bug
[TEST CASE]
Find a package like the one in the report, by running this UDD query:
SELECT rp.source, r.version, rp.version, d.release, d.version
FROM ubuntu_sources AS rp
INNER JOIN ubuntu_sources AS r
ON (rp.source = r.source
AND rp.version != r.version
AND r.release='raring')
INNER JOIN sources AS d
ON (rp.source = d.source
AND rp.version < d.version
AND r.version != d.version
AND d.release IN ('sid', 'experimental'))
WHERE rp.release='raring-proposed';
Run syncpackage and requestsync on it (without actually doing anything).
See that the changelogs differ.
== Original Report ==
If a package exists in ${DEVELOPMENT_RELEASE}-proposed and ${DEVELOPMENT_RELEASE}, syncpackage and requestsync give different results. Syncpackage checks against -proposed be default, while requestsync checks against proposed only if a package doesn't exist in -release. At the time I did these requests, 1.1.2-1 was in raring-proposed:
$ requestsync -d experimental shiboken
W: Target release missing - assuming raring
Consider using syncpackage(1) for syncs that do not require feature freeze exceptions.
Currently the bug report looks like:
Summary (one line):
Sync shiboken 1.1.2-2 (universe) from Debian experimental (main)
Description:
Please sync shiboken 1.1.2-2 (universe) from Debian experimental (main)
Changelog entries since current raring version 1.1.1-1:
shiboken (1.1.2-2) experimental; urgency=low
* Add python{,3}-numpy-dbg to Build-Depends to have all tests pass.
* Make dbg tests build-critical.
-- Didier Raboud <odyx@debian.org> Mon, 29 Oct 2012 10:06:19 +0100
shiboken (1.1.2-1) experimental; urgency=low
* New 1.1.2 "Alaursa" release.
- Add 6 1.1.2-specific symbols;
* Update B-Ds:
- add python{,3}-numpy to succeed all tests.
-- Didier Raboud <odyx@debian.org> Tue, 04 Sep 2012 08:47:15 +0200
Edit [y|N]? ^C
User abort.
$ syncpackage -d experimental shiboken
syncpackage: Source shiboken -> raring/Proposed: current version 1.1.2-1, new version 1.1.2-2
syncpackage: New changes:
shiboken (1.1.2-2) experimental; urgency=low
* Add python{,3}-numpy-dbg to Build-Depends to have all tests pass.
* Make dbg tests build-critical.
-- Didier Raboud <odyx@debian.org> Mon, 29 Oct 2012 10:06:19 +0100
Sync this package [y|N]? y
syncpackage: Request succeeded; you should get an e-mail once it is processed.
The syncpackage behavior is the one we want. |
|
