Loading...
Request History
weberho created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
dimstar_suse added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:78"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:adi:78"
dimstar accepted review
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:adi:78 got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:adi:78 got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:adi:78 got accepted.
No ticket is referenced and info is pretty sparse. So it's hard to tell which problem shall be solved by this change.
Before this gets accepted I'd like to know what "other device acceess is needed" really means.
There's no ticket for this. ProtectClock not only limits access to the clock, but apparently also to other devices. This was noticed by other packagers. If this doesn't cause issues for you then I'm fine to revoke it, as keeping ProtectClock is preferable
Yes, as stated in systemd.exec(5) ProtectClock=yes also implies DeviceAllow=char-rtc r which might cause issues for other services.
But I'm heavily using a self-hosted coturn installation based on this package. ProtectClock=yes in coturn.service works for me thus I will restore it.
Could you please revoke this submission? I'm not authorized to revoke it.