[pkg-wine-party] Bug#758291: Complete solution for update-alternatives
jre.winesim at gmail.com
Tue Sep 2 00:43:01 UTC 2014
I just pushed a few minor changes/fixes to my git repository. I changed
to use the branch "masterUnifiedPackaging" instead of "master".
As of now there is only one additional lintian complain, and this is
only for wine (stable) packages:
W: wine: latest-debian-changelog-entry-without-new-version
Otherwise I think my proposal is regression free.
[The rest of this message is only related to the unified packaging.
Although this doesn't suit this bugreport, it is still related due to my
patch proposal using the unified packaging, sorry for the noise.]
About a common changelog:
Is it ok to ship a common changelog with changes for wine-development
that are not in wine (in particular, all the upstream changes)?
In bug #597154 Russ Albery argues that this is not ok.
While I think that the changelog stays true as long as -development only
packaging changes are marked as such, I'm not sure about the upstream
This would mean to maintain two separate changelogs, which is one of the
things I wanted to avoid.
Finally a little correction for the quick&dirty use instruction (other
branch name and earlier changelog entry):
git checkout master
cp -rf debian ..
git checkout jessie #or whatever the branch is/will be called
rm -rf debian
mv ../debian .
# update changelog
./debian/rules #recreates debian/control
# build packages
More information about the pkg-wine-party