User story #3172
closed
Technique Rug / YaST Pakcage Manager Configuration (ZMD) can't register services with signed RPM
Description
- Repository URL (with a "\$" inside the URL) containing signed RPM like Rudder repository
- Repository local name
and with the "Add the following repository(ies) ticked.
The reporting on the node when using cf-agent desesperatly say "Could not register the source"
Files
Updated by Nicolas PERRON about 12 years ago
- Status changed from New to In progress
It seems that the problem come from the fact that the repository added (Rudder repository) contains signed packages. Rug asks if we want to trust the key but doesn't obtain answer.
Updated by Nicolas PERRON about 12 years ago
I will have to add possibility to specify the add of Public Key for each repository.
Problem: It is not possible to check existence of an unique key, the command rug kl only display all the keys. I will need to create a perl module, like the module used to check the repositories.
Updated by Nicolas PERRON about 12 years ago
- File check_zmd_keys.pl check_zmd_keys.pl added
- % Done changed from 0 to 90
Here is the file which check key presence with rug
Updated by Nicolas PERRON about 12 years ago
- Tracker changed from Bug to User story
- Subject changed from Technique Rug / YaST Pakcage Manager Configuration (ZMD) doesn't register services, especially with special character like "$" to Technique Rug / YaST Pakcage Manager Configuration (ZMD) can't register services with signed RPM
- Description updated (diff)
Change title and type of ticket
Updated by Matthieu CERDA 
Updated by Jonathan CLARKE
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.4.13 to 2.6.11
Retargeted to 2.6, since 2.4 is not maintained anymore.
Updated by
Updated by François ARMAND almost 10 years ago
- Status changed from In progress to 8
Can't be in progress since nobody assigned.
Updated by Alexis Mousset almost 6 years ago
- Status changed from New to Rejected
Deprecated technique