Spec URL: http://raveit65.fedorapeople.org/Mate-Desktop/fc17/SPECS/mate-keyring.spec SRPM URL: http://raveit65.fedorapeople.org/Mate-Desktop/fc17/SRPM/mate-keyring-1.4.0-5.fc17.src.rpm Description: The mate-keyring session daemon manages passwords and other types of secrets for the user, storing them encrypted with a main password. Applications can use the mate-keyring library to integrate with the keyring. Fedora Account System Username: raveit65
new starting point koji scratch build for f18 http://koji.fedoraproject.org/koji/taskinfo?taskID=4358613 SPEC: http://raveit65.fedorapeople.org/Mate-Desktop/fc18/SPECS/mate-keyring.spec SRPM: http://raveit65.fedorapeople.org/Mate-Desktop/fc18/SRPM/mate-keyring-1.4.0-6.fc18.src.rpm
new starting point koji scratch build for f18 http://koji.fedoraproject.org/koji/taskinfo?taskID=4360721 * Sun Aug 05 2012 Wolfgang Ulbrich <chat-to-me> - 1.4.0-7 - fix mixed use of $RPM_BUILD_ROOT & %%{buildroot} - rename patch to mate - fix requires in -devel - fix scriplet sections * Sat Aug 04 2012 Wolfgang Ulbrich <chat-to-me> - 1.4.0-6 - initial build for fedora - edit start-gnome-keyring-in-mate sources SPEC: http://raveit65.fedorapeople.org/Mate-Desktop/fc18/SPECS/mate-keyring.spec SRPM: http://raveit65.fedorapeople.org/Mate-Desktop/fc18/SRPM/mate-keyring-1.4.0-7.fc18.src.rpm
Ok, I'm not happy with the auto provides on the mate-keyring package Provides -------- mate-keyring-pam-1.4.0-7.fc18.x86_64.rpm: mate-keyring-pam = 1.4.0-7.fc18 mate-keyring-pam(x86-64) = 1.4.0-7.fc18 pam_mate_keyring.so()(64bit) mate-keyring-1.4.0-7.fc18.x86_64.rpm: config(mate-keyring) = 1.4.0-7.fc18 gkm-mate2-store-standalone.so()(64bit) gkm-roots-store-standalone.so()(64bit) gkm-secret-store-standalone.so()(64bit) gkm-ssh-store-standalone.so()(64bit) gkm-xdg-store-standalone.so()(64bit) libmategck.so.0()(64bit) libmategcr.so.0()(64bit) mate-keyring = 1.4.0-7.fc18 mate-keyring(x86-64) = 1.4.0-7.fc18 mate-keyring-pkcs11.so()(64bit) All these below are provide by gnome-keyring gkm-roots-store-standalone.so()(64bit) gkm-secret-store-standalone.so()(64bit) gkm-ssh-store-standalone.so()(64bit) gkm-xdg-store-standalone.so()(64bit gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and other : secrets Repo : fedora Matched from: Filename : /usr/lib64/gnome-keyring/devel/gkm-xdg-store-standalone.so gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and other : secrets Repo : @koji-override-0/$releasever Matched from: Filename : /usr/lib64/gnome-keyring/devel/gkm-ssh-store-standalone.so gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and other : secrets Repo : @koji-override-0/$releasever Matched from: Filename : /usr/lib64/gnome-keyring/devel/gkm-secret-store-standalone.so gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and other : secrets Repo : @koji-override-0/$releasever Matched from: Filename : /usr/lib64/gnome-keyring/devel/gkm-roots-store-standalone.so It is possible to filter them, could you try and get Rex or some else with the experience to confirm the need to do this.
(In reply to comment #3) > Ok, I'm not happy with the auto provides on the mate-keyring package > > > Provides > -------- > mate-keyring-pam-1.4.0-7.fc18.x86_64.rpm: > > mate-keyring-pam = 1.4.0-7.fc18 > mate-keyring-pam(x86-64) = 1.4.0-7.fc18 > pam_mate_keyring.so()(64bit) > > mate-keyring-1.4.0-7.fc18.x86_64.rpm: > > config(mate-keyring) = 1.4.0-7.fc18 > gkm-mate2-store-standalone.so()(64bit) > gkm-roots-store-standalone.so()(64bit) > gkm-secret-store-standalone.so()(64bit) > gkm-ssh-store-standalone.so()(64bit) > gkm-xdg-store-standalone.so()(64bit) > libmategck.so.0()(64bit) > libmategcr.so.0()(64bit) > mate-keyring = 1.4.0-7.fc18 > mate-keyring(x86-64) = 1.4.0-7.fc18 > mate-keyring-pkcs11.so()(64bit) > > > > > All these below are provide by gnome-keyring > > > gkm-roots-store-standalone.so()(64bit) > gkm-secret-store-standalone.so()(64bit) > gkm-ssh-store-standalone.so()(64bit) > gkm-xdg-store-standalone.so()(64bit > > > gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and > other > : secrets > Repo : fedora > Matched from: > Filename : /usr/lib64/gnome-keyring/devel/gkm-xdg-store-standalone.so > > gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and > other > : secrets > Repo : @koji-override-0/$releasever > Matched from: > Filename : /usr/lib64/gnome-keyring/devel/gkm-ssh-store-standalone.so > > gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and > other > : secrets > Repo : @koji-override-0/$releasever > Matched from: > Filename : /usr/lib64/gnome-keyring/devel/gkm-secret-store-standalone.so > > gnome-keyring-3.4.1-2.fc17.x86_64 : Framework for managing passwords and > other > : secrets > Repo : @koji-override-0/$releasever > Matched from: > Filename : /usr/lib64/gnome-keyring/devel/gkm-roots-store-standalone.so > > > It is possible to filter them, could you try and get Rex or some else with > the experience to confirm the need to do this. I could be wrong but it's better to be sure.
Thx for your hints. I will ask Rex Dieter for knowledge. In general it is a problem that mate-keyring wasn't complete renamed. I'm shure i can write a patch for renaming 'gkm' in mate-keyring, but there are other packages which expect the therm 'gkm' in there code. Shure, i can remove gkm-roots-store-standalone.so()(64bit) gkm-secret-store-standalone.so()(64bit) gkm-ssh-store-standalone.so()(64bit) gkm-xdg-store-standalone.so()(64bit , but won't this step break make-keyring from working? Unfortunately I can't estimate the consequences. Not all packages which need a keyring framework are installed on my desktop. And i don't know all. I will notice Steve Zech (mate dev) about this, and build a test rpm for me.
(In reply to comment #5) > Thx for your hints. > I will ask Rex Dieter for knowledge. > Thanks, I would welcome feedback as I haven't dealt with this type of issue before. > but there are other packages which expect the therm 'gkm' in there code. > > Shure, i can remove I didn't ask you to remove them only hide them from yum if needed. > > gkm-roots-store-standalone.so()(64bit) > gkm-secret-store-standalone.so()(64bit) > gkm-ssh-store-standalone.so()(64bit) > gkm-xdg-store-standalone.so()(64bit , > > but won't this step break make-keyring from working? > Unfortunately I can't estimate the consequences. > Not all packages which need a keyring framework are installed on my desktop. > And i don't know all. Here's a list $ repoquery --whatrequires gnome-keyring NetworkManager-gnome-1:0.9.4.0-7.git20120403.fc17.x86_64 NetworkManager-gnome-1:0.9.4.0-9.git20120521.fc17.x86_64 NetworkManager-openswan-0:0.9.3.995-1.git20120302.fc17.x86_64 NetworkManager-openvpn-1:0.9.3.997-1.fc17.x86_64 NetworkManager-pptp-1:0.9.3.997-1.fc17.x86_64 NetworkManager-vpnc-1:0.9.3.997-1.fc17.x86_64 gnome-keyring-pam-0:3.4.1-2.fc17.i686 gnome-keyring-pam-0:3.4.1-2.fc17.x86_64 gnome-python2-gnomekeyring-0:2.32.0-9.fc17.x86_64 mysql-workbench-0:5.2.38-2.fc17.x86_64 mysql-workbench-0:5.2.40-1.fc17.x86_64 virt-manager-0:0.9.1-3.fc17.noarch virt-manager-0:0.9.1-4.fc17.noarch
(In reply to comment #6) > (In reply to comment #5) > > but there are other packages which expect the therm 'gkm' in there code. > > > > Shure, i can remove > > I didn't ask you to remove them only hide them from yum if needed. But in fact, we speak about duplicates of already present system files, don't we? I think it's a task for upstream to make them distinguishable from the gnome-keyring ones.
Re: comment #3 Those duplicated Provides aren't anything to consider a review-blocker, and shouldn't cause any practical problems. However, it is possible to filter them out if you really want to (preferably implemented post-review, imo)
I have both gnome-keyring and mate-keyring installed without conflicts. There shouldn't be any problems.
Created attachment 915480 [details] Comment (This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Thank you Leigh for approving the package. rpmlint error is fixed in version 1.4.0.8 %changelog * Sun Aug 05 2012 Wolfgang Ulbrich <chat-to-me> - 1.4.0-8 - fix rpmlint error unused-direct-shlib-dependency * Sun Aug 05 2012 Wolfgang Ulbrich <chat-to-me> - 1.4.0-7 - fix mixed use of $RPM_BUILD_ROOT & %%{buildroot} - rename patch to mate - fix requires in -devel - fix scriplet sections * Sat Aug 04 2012 Wolfgang Ulbrich <chat-to-me> - 1.4.0-6 - initial build for fedora - edit start-gnome-keyring-in-mate sources * Sun Dec 25 2011 Wolfgang Ulbrich <chat-to-me> - 1.1.0-1 - mate-file-manager.spec based on gnome-keyring-2.32.0-1.fc14 spec SPEC: http://raveit65.fedorapeople.org/Mate-Desktop/fc18/SPECS/mate-keyring.spec
New Package SCM Request ======================= Package Name: mate-keyring Short Description: Framework for managing passwords and other secrets Owners: raveit65 rdieter Branches: f16 f17 InitialCC:
Make that, New Package SCM Request ======================= Package Name: mate-keyring Short Description: Framework for managing passwords and other secrets Owners: raveit65 rdieter vicodin Branches: f16 f17 InitialCC:
I'm not agree with comment 13
Git done (by process-git-requests). Implemented #12.
mate-keyring-1.4.0-8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mate-keyring-1.4.0-8.fc17
mate-keyring-1.4.0-8.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mate-keyring-1.4.0-8.fc16
mate-keyring-1.4.0-8.fc16 has been pushed to the Fedora 16 testing repository.
I don't work for the Mate-Desktop project anymore, because i see no basic for working together with Dan Mashal.
mate-keyring-1.4.0-8.fc17 has been pushed to the Fedora 17 stable repository.