First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 101346
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Crypto team <crypto@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Stephan Wienczny <Stephan@Wienczny.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
gpg.patch ebuild Patch to fix this patch Rod Begbie 2005-08-04 22:25 0000 453 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 101346 depends on: Show dependency tree
Bug 101346 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-08-04 09:01 0000 
After updating to gnupg-1.4.2 the gpgkeys_* are copied to the wrong  
directory /usr/libexec/gnupg/gnupg/* . The second gnupg is not correct!  

Reproducible: Always
Steps to Reproduce:
1.emerge gnupg-1.4.2 
2.gpg --refresh-keys 
3. 
 
Actual Results:  
The helper files are not found

------- Comment #1 From Rod Begbie 2005-08-04 22:25:02 0000 ------- 
Created an attachment (id=65157) [edit]
ebuild Patch to fix this

Patrionisingly simple ebuild patch to fix this.

------- Comment #2 From Lars Strojny 2005-08-05 12:57:03 0000 ------- 
This modification leads to problem with 1.4.2. The files will be installed in
/usr/libexec/gnupg/gnupg/* there. So it should be changed again. There seems to
be strange things going on upstream.

------- Comment #3 From Daniel Black 2005-08-05 17:02:45 0000 ------- 
fixed - thank all. 
 
Rod btw I think your patch was backwards.

------- Comment #4 From Gabriel Devenyi 2005-08-05 22:10:24 0000 ------- 
*** Bug 101507 has been marked as a duplicate of this bug. ***

------- Comment #5 From Jakub Moc (RETIRED) 2005-08-10 01:45:21 0000 ------- 
*** Bug 101946 has been marked as a duplicate of this bug. ***
First Last Prev Next    No search results available      Search page      Enter new bug