Merge lp:~ubuntu-branches/ubuntu/oneiric/libgnome-keyring/oneiric-201109060911 into lp:ubuntu/oneiric/libgnome-keyring

Proposed by Ubuntu Package Importer
Status: Rejected
Rejected by: Colin Watson
Proposed branch: lp:~ubuntu-branches/ubuntu/oneiric/libgnome-keyring/oneiric-201109060911
Merge into: lp:ubuntu/oneiric/libgnome-keyring
Diff against target: 93 lines (+82/-0) (has conflicts)
1 file modified
debian/control (+82/-0)
Text conflict in debian/control
To merge this branch: bzr merge lp:~ubuntu-branches/ubuntu/oneiric/libgnome-keyring/oneiric-201109060911
Reviewer Review Type Date Requested Status
Colin Watson Disapprove
Review via email: mp+74185@code.launchpad.net

Description of the change

The package importer has detected a possible inconsistency between the package history in the archve and the history in bzr. As the archive is authoritative the importer has made lp:ubuntu/oneiric/libgnome-keyring reflect what is in the archive and the old bzr branch has been pushed to lp:~ubuntu-branches/ubuntu/oneiric/libgnome-keyring/oneiric-201109060911. This merge proposal was created so that an Ubuntu developer can review the situations and perform a merge/upload if necessary. There are three typical cases where this can happen.
  1. Where someone pushes a change to bzr and someone else uploads the package without that change. This is the reason that this check is done by the importer. If this appears to be the case then a merge/upload should be done if the changes that were in bzr are still desirable.
  2. The importer incorrectly detected the above situation when someone made a change in bzr and then uploaded it.
  3. The importer incorrectly detected the above situation when someone just uploaded a package and didn't touch bzr.

If this case doesn't appear to be the first situation then set the status of the merge proposal to "Rejected" and help avoid the problem in future by filing a bug at https://bugs.launchpad.net/udd linking to this merge proposal.

(this is an automatically generated message)

To post a comment you must log in.
Revision history for this message
Colin Watson (cjwatson) wrote :

'bzr merge' shows no conflicts, and in fact no content changes; and there's no significant extra history here either. Rejecting.

review: Disapprove

Unmerged revisions

25. By Martin Pitt

releasing version 3.1.90-0ubuntu1

24. By Martin Pitt

import upstream release 3.1.90

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/control'
2--- debian/control 2011-09-06 10:25:05 +0000
3+++ debian/control 2011-09-06 09:15:36 +0000
4@@ -1,3 +1,4 @@
5+<<<<<<< TREE
6 # This file is autogenerated. DO NOT EDIT!
7 #
8 # Modifications should be made to debian/control.in instead.
9@@ -77,3 +78,84 @@
10 libraries.
11 .
12 Most people should not need this package.
13+=======
14+# This file is autogenerated. DO NOT EDIT!
15+#
16+# Modifications should be made to debian/control.in instead.
17+# This file is regenerated automatically in the clean target.
18+
19+Source: libgnome-keyring
20+Section: gnome
21+Priority: optional
22+Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
23+XSBC-Original-Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
24+Uploaders: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>, Jordi Mallach <jordi@debian.org>, Josselin Mouette <joss@debian.org>, Michael Biebl <biebl@debian.org>, Sebastian Dröge <slomo@debian.org>
25+Build-Depends: debhelper (>= 5),
26+ cdbs,
27+ gnome-pkg-tools (>= 0.10),
28+ intltool (>= 0.35.0),
29+ libglib2.0-dev (>= 2.16.0),
30+ gtk-doc-tools (>= 1.9),
31+ docbook-xml,
32+ libdbus-1-dev (>= 1.0),
33+ libgcrypt11-dev (>= 1.2.2),
34+ libglib2.0-doc,
35+ gnome-keyring
36+Standards-Version: 3.9.2
37+Vcs-Browser: http://svn.debian.org/wsvn/pkg-gnome/desktop/unstable/libgnome-keyring/
38+Vcs-Svn: svn://svn.debian.org/svn/pkg-gnome/desktop/unstable/libgnome-keyring/
39+Homepage: http://live.gnome.org/GnomeKeyring
40+
41+Package: libgnome-keyring-dev
42+Section: libdevel
43+Architecture: any
44+Depends: ${misc:Depends},
45+ libgnome-keyring0 (= ${binary:Version}),
46+ libglib2.0-dev (>= 2.16)
47+Description: Development files for GNOME keyring service
48+ gnome-keyring is a daemon in the session, similar to ssh-agent,
49+ and other applications can use it to store passwords and other
50+ sensitive information.
51+ .
52+ The program can manage several keyrings, each with its own master
53+ password, and there is also a session keyring which is never stored to
54+ disk, but forgotten when the session ends.
55+ .
56+ This package contains development files for GNOME.
57+
58+Package: libgnome-keyring0
59+Section: libs
60+Architecture: any
61+Depends: ${misc:Depends},
62+ ${shlibs:Depends}
63+Breaks: gnome-keyring (<< 3.0)
64+Suggests: gnome-keyring
65+Description: GNOME keyring services library
66+ gnome-keyring is a daemon in the session, similar to ssh-agent,
67+ and other applications can use it to store passwords and other
68+ sensitive information.
69+ .
70+ The program can manage several keyrings, each with its own master
71+ password, and there is also a session keyring which is never stored to
72+ disk, but forgotten when the session ends.
73+ .
74+ This package contains shared libraries for GNOME.
75+
76+Package: libgnome-keyring0-dbg
77+Section: debug
78+Architecture: any
79+Depends: libgnome-keyring0 (= ${binary:Version})
80+Description: GNOME keyring services library (debugging symbols)
81+ gnome-keyring is a daemon in the session, similar to ssh-agent,
82+ and other applications can use it to store passwords and other
83+ sensitive information.
84+ .
85+ The program can manage several keyrings, each with its own master
86+ password, and there is also a session keyring which is never stored to
87+ disk, but forgotten when the session ends.
88+ .
89+ This package contains detached debugging symbols for the shared
90+ libraries.
91+ .
92+ Most people should not need this package.
93+>>>>>>> MERGE-SOURCE

Subscribers

People subscribed via source and target branches

to all changes: