Comments

34 Comments
User Icon thm commented & provided feedback on openvpn-2.5.7-1.fc36 a year ago
karma

Did also NOT work for me against a 2.4.9 server. Needed to do one of two things: either

  • pass --providers legacy default to allow (weak) BF-CBC, or
  • explicitly set AES-256-GCM cipher in the client.

Otherwise, connecting to that server will fail.

karma

Fixes a crash I saw with nheko-0.9.1-1.

karma

Works like charm :) Thanks!

Hi, sorry it crashes for you.

Nonetheless we usually do not update to git master in Fedora, especially not for stable Fedora branches, but follow upstream's releases. Maybe you could bug upstream to cut a release?

See https://github.com/awesomeWM/awesome/issues/1754 - seems you are trying to use a 3.5 lua.rc with 4.x.

See https://src.fedoraproject.org/rpms/lmms/blob/master/f/README.fedora. The samples are not included in the Fedora package because for many of them the copyright status is unclear.

See also this discussion several years ago: https://sourceforge.net/p/lmms/mailman/message/21407315/.

User Icon thm commented & provided feedback on firefox-57.0-2.fc25 6 years ago
karma

Works very well.

Test Case firefox browse
Test Case firefox media

Well, Shotwell was updated in F27 (by kalev) to 0.27.0 when F27 was still Rawhide.

Based on that, I think it totally makes sense to update the package to a newer release, even if it is from the unstable branch. Only other option would be to downgrade the package in F27 to 0.26.3.

Btw, as I read the Feedback Guidelines, karma should reflect this question: "Is the update generally functional?", not (dis)agreement with the update per se.

BZ#1051685 rpm doesn't read $HOME/.popt
BZ#1051685 rpm doesn't read $HOME/.popt
BZ#1051685 rpm doesn't read $HOME/.popt

@dsommers Sorry, but I tend to disagree. This is a change in behavior. The Updates Policy mandates that packages must "avoid changing the user experience if at all possible". Changing the meaning of an option (--proto in that case) is such a change.

karma

This does not work for me: There's a semantic change in --proto udp meaning IPv4 and IPv6 now. As our company's server can be reached via IPv6, but doesn't offer OpenVPN via IPv6, no connection can be established - and OpenVPN doesn't fall back to IPv4.

Now, I could use --proto udp4 instead, alas NetworkManager doesn't offer that as far as I can see.