After installing this update, "su -" in gnome-terminal suffers from a 15 seconds delay. Downgrading to 0.7.0-4.fc27 fixes it.

Would be enough for a -1, but maybe I'm missing something.

Also fixes the currently crashing 3.15.0 in F27:

folder.c:3967 Condition path != NULL failed
folder.c:3991 Condition path != NULL failed
msgcache.c:586 Condition cache_file != NULL failed
(claws-mail:21030): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 'folder_path != NULL' failed
Segmentation fault (core dumped)

LAME works for MP3 encoding in Audacious' filewriter output plugin.

yum-deprecated showing different behaviour is a start. Good. See bug 1439690 I've assigned to "dnf".

Of course, users with update problems have got 3rd party packages installed. a52dec has not been offered by Fedora before! Those are the packages you try to handle in your %changelog, btw.

The fundamental problem is that you're replacing a52dec with liba52, replacing executables with only libraries. Whether the various package tools, such as DNF, show warnings or errors, is implementation dependent. All replace a52dec because of your Obsoletes tags and remove executables from users' installations accidentally.

That is reproducible by you, too, with pkcon or dnf or other tools, provided that you do start with the older package releases such as -21.fc25, regardless of whether single-arch or multilib. That doesn't matter.

The reason why dnf runs into broken deps or conflicts may be your circular Obsoletes as pointed out before. You can't update a52dec with a new releases, because the new a52dec requires liba52, which in turn obsoletes a52dec. No, the versions in the tags don't do what you possibly hope they would do. You lose a52dec and only get liba52.

Notice the topic on users@ list. Update problems with older a52dec updates affects various dist releases.

I've given you a clear test-case for F25 and pointed out several mistakes in your update. I don't have the time to provide you with many more details, if you are not willing to test your own updates painstakingly.

You cannot assume that any user has already applied a previous update. Your -26.fc25 update also failed to replace -21.fc25 correctly, flags a52dec as broken and removes it because of the obsoletes. The entire upgrade path for these updates is broken.

Oh, there's also multiple Obsoletes tags for a52dec in different packages, and both cover -21.fc25. That won't work, since only either one would be chosen.

Also, since a52dec-0.7.4-21.fc25 contains libs and executables, letting liba52 replace it isn't correct. User would get only the lib, not the executables.

You've introduced a circular Requires/Obsoletes pair. a52dec requires liba52, which obsoletes a52dec.

zdenek : Please investigate further. That smells like some conflict in wxGTK compat packages, but isn't reproducible here. I've come from "dnf install audacity" to "dnf --enablerepo=updates-testing update audacity" without any such problems.

rpm -qa|grep -i wx

wxBase3-3.0.2-26.fc25.x86_64 compat-wxBase3-gtk2-3.0.2-7.fc24.x86_64 wxGTK3-3.0.2-26.fc25.x86_64 compat-wxGTK3-gtk2-3.0.2-7.fc24.x86_64

In case anyone is annoyed by the 'next_on_delete' change, the hidden preference setting can be changed with the "clawsker" tool. Its latest version can be found in updates-testing on its way into stable updates.

Been using this for some time, and the only interruption is the changed passphrase storage method, which requires re-entering passphrases for accounts once.

Unfortunately, you need another release, because now you've put both files into the runtime package, which is exactly the opposite of the previous bug. With this new version you've packaged, there is a new versioned runtime library, and you need to ship the .so symlink in the -devel package and the versioned .so.1 in the runtime package: https://fedoraproject.org/wiki/Packaging:Guidelines#Devel_Packages

Unfortunately, you need another release, because now you've put both files into the runtime package, which is exactly the opposite of the previous bug. With this new version you've packaged, there is a new versioned runtime library, and you need to ship the .so symlink in the -devel package and the versioned .so.1 in the runtime package: https://fedoraproject.org/wiki/Packaging:Guidelines#Devel_Packages

It fixes #1291903 -- and is an interesting case, since priority-based detection of file formats really is problematic if the implemented signatures aren't 100%.

No vote, because since approx. two days, when logging in into GNOME Shell, I receive a notification about failed network connection. dhclient reports "Network is down" and fails to send packets. NetworkManager reports "Activation: failed for connection 'Wired connection 1'", but that's the last activity in the logs, and the connection is up. I only click away the notification and need not do anything else.

First thing I will try is a downgrade to 1.0.6.