Update vino to 3.6.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vino (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[IMPACT]
Vino 3.6.1 is a translation and bugfix release. The one bug fixed is a FTBFS bug if building with libsecret support. I'm not sure why vino wasn't automatically building with libsecret support since we did add the build dependencies. In my update, I'm explicitly adding --with-secret to debian/rules to make sure we do build with libsecret support like we intended.
Vino 3.6.1
==========
Alexandre Rostovtsev (1):
Consistently use SECRET_DEPS, not LIBSECRET_DEPS
David King (2):
Update NEWS for 3.6.1 release
Post-release version bump to 3.6.1
Ihar Hrachyshka (1):
Updated Belarusian translation.
Khoem Sokhem (1):
[l10n] Added Khmer translation
Rūdolfs Mazurs (1):
Updated Latvian translation
[TESTCASE]
* Just make sure vino continues to work.
[Regression Potential]
* The code diff is pretty small but it does change the build. I don't know much about libsecret but I'm guessing it would improve security.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: vino 3.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu4
Architecture: amd64
Date: Tue Oct 23 20:33:01 2012
MarkForUpload: True
SourcePackage: vino
UpgradeStatus: No upgrade log present (probably fresh install)
Because vino was previously not building with libsecret support (for whatever reason), this amounts to the introduction of a new feature in the SRU. I think an explicit test case is needed for libsecret if it's going to be enabled in SRU, as well as some explicit analysis of the possible sources of regression due to libsecret enablement.
If this information is not available, I recommend doing this SRU with libsecret explicitly *disabled* instead, for consistency with the current build.