vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit d76bf40d583bfae9c230de4f8423032aaab5f576
Author: Jeremy Bicha <jbicha@ubuntu.com>
Date: Mon Sep 10 07:36:19 2018 -0400
Bump Standards-Version to 4.2.1
commit 9c35e434e689345596bacc310e8f939b906a4bc2
Author: Jeremy Bicha <jbicha@ubuntu.com>
Date: Mon Sep 10 07:34:27 2018 -0400
Run dh_auto_test instead of make check
This should be a trivial change
commit 8f11e1d67887857e9d5dd5375c82e86175516863
Author: Tim Lunn <tim@feathertop.org>
Date: Tue May 15 18:15:18 2018 +1000
releasing package gnome-keyring version 3.28.2-1
commit 52cf879b38ae0e9380065aecb397464247c3630a
Author: Tim Lunn <tim@feathertop.org>
Date: Tue May 15 17:39:59 2018 +1000
New upstream release
commit faa03418a0318f79b0a1b4a5ea3f2efda3ad1264
Merge: d3097460 d0c373da
Author: Tim Lunn <tim@feathertop.org>
Date: Tue May 15 17:39:44 2018 +1000
Update upstream source from tag 'upstream/3.28.2'
Update to upstream version '3.28.2'
with Debian dir 07d84d862550c3d4e94e46a8ab36f56666b20b5f
commit d0c373da0ceaf87e3463459fde51501c6606dab1
Merge: b2b7ed51 c2b54cdd
Author: Tim Lunn <tim@feathertop.org>
Date: Tue May 15 17:39:34 2018 +1000
New upstream version 3.28.2
commit c2b54cdd3498ca443fbcb6dc66ff2e6e7b3c44b0
Author: Daiki Ueno <dueno@src.gnome.org>
Date: Mon May 7 09:34:14 2018 +0200
Release 3.28.2
commit 02ba40403973a581d0f0fde0a7a4a62945a1efdf
Author: Daiki Ueno <dueno@src.gnome.org>
Date: Mon May 7 09:17:45 2018 +0200
ssh-agent: Don't treat packet write error as fatal
commit 65e20169b8dfc935c907ca65e54c1c6e2a365388
Author: Daiki Ueno <dueno@src.gnome.org>
Date: Mon Apr 30 18:03:19 2018 +0200
ssh-agent: Make public key parsing robuster
Previously, _gkd_ssh_agent_parse_public_key() accepted OpenSSH v1
keys, because the second component of the key line looks like a valid
base64 blob:
2048 65537 2444136...
This patch checks that the component is really base64 encoded, by
checking the length is a multiple of 4.
Note that this solution is not perfect, as there could be a key with a
public exponent whose decimal length is multiple of 4. More thorough
approach would be to call ssh-keygen -l on each public key.
https://bugzilla.gnome.org/show_bug.cgi?id=795699
commit d8b6de0c65c4206bc47942963c285d4ee76cf0c6
Author: Daniel Șerbănescu <daniel@serbanescu.dk>
Date: Wed Apr 18 18:37:29 2018 +0000
Update Romanian translation
commit d3097460197bfa99f71fc71f63b3199b2ff00900
Author: Tim Lunn <tim@feathertop.org>
Date: Thu Mar 29 19:26:47 2018 +1100
releasing package gnome-keyring version 3.28.0.2-1
commit 3759d9877232d14e0d628b7c0fd760787a7f34ca
Author: Matej Urbančič <mateju@svn.gnome.org>
Date: Tue Mar 27 18:13:59 2018 +0200
Updated Slovenian translation
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/gnome-keyring.png){kind=link}