[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#693197: marked as done (RFS: mozilla-gnome-keyring/0.6.6-1)



Your message dated Sat, 15 Dec 2012 05:00:25 +0100
with message-id <50CBF5D9.10202@debian.org>
and subject line Re: Bug#693197: RFS: mozilla-gnome-keyring/0.6.5-1
has caused the Debian Bug report #693197,
regarding RFS: mozilla-gnome-keyring/0.6.6-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
693197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693197
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "mozilla-gnome-keyring"

* Package name    : mozilla-gnome-keyring
  Version         : 0.6.5-1

This is an update to an already existing package:

  http://packages.debian.org/source/experimental/mozilla-gnome-keyring

It builds those binary packages:

  xul-ext-gnome-keyring - Store mozilla passwords in GNOME Keyring.

To access further information about this package, please visit the following URL:

http://mentors.debian.net/package/mozilla-gnome-keyring


Alternatively, one can download the package with dget using this command:

  dget -x http://mentors.debian.net/debian/pool/main/m/mozilla-gnome-keyring/mozilla-gnome-keyring_0.6.5-1.dsc

Changes since the last upload:

 * Upload to unstable.
 * Fix FTBFS where the platform name contains a /. (Closes: #689189)
 * Fix Vcs-* entries in debian/contol to point to the correct branch.
   (Closes: #689165)

Regards,
 Ximin Luo

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On 15.12.2012 04:56, Michael Biebl wrote:
> On 15.12.2012 04:06, Michael Biebl wrote:
> 
>> How does this exactly work? How does the iceweasel extension know that
>> it should load libgnomekeyring.so whereas the icedove extension should
>> load libgnomekeyring-icedove.so?
> 
> nvm, found it in the mean time: the chrome.manifest maps the libraries
> to the corresponding apps by using the app-id.
> 

Uploaded in the mean time, so closing the bug


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply to: