I wish #SUSE/#openSUSE would just enable #dnf out of box for non-transactional variants. #zypper is comparatively slower/clunky and there's not a clearly unsolveable issue with their mutual co-existence. #Linux
@sfalken I totally get that. I'm just saying that there's no apparent harm in including both for non-transactional environments since they're using the same backends, right?
@sfalken Hmmm, I guess I can think of one thing. If I add a repo with zypper ar, then I also need to copy that file to /etc/dnf.repos.d or vice versa. I'm curious why dnf and zypper don't just share the same .repo file path on OpenSUSE?
@vwbusguy You know, I can't remember exactly, but I thought that there was something extra you needed along with dnf in order for everything to be ticketyboo. The repo definitions maybe?
I know I've seen some chatter that zypper dup vs dnf distro-sync could give some different results. (I think they're functionally equivalent commands)
@sfalken distro-sync and zypper dup aren't the same. dnf's equivalent to dup would be dnf system-upgrade (which I think is a plugin and not part of the base dnf).
Also, it looks like there is a package to make dnf aware of zypper repos: libdnf-repo-config-zypp
zypper in dnf dnf-plugins-core python3-dnf-plugins-extras-common dnf-utils libdnf-repo-config-zypp && dnf refresh
(This way, zypper repos and dnf should stay in sync. If you don't want that for some reason, replace the libdnf-repo-config-zypp with "openSUSE-repos-Leap rpm-repos-openSUSE-Leap" or Tumbleweed)
@sfalken Certainly beats spinning up a VM everytime I want to look up what version of something is currently shipped in Ubuntu or where that conf file lived on RHEL7.
@sfalken Why would you need system-upgrade or dup on Tumbleweed? (Sorry if this is a dumb question. I've never actually ran Tumbleweed outside of a container.)
@vwbusguy@sfalkenzypper has no equivalent to dnf system-upgrade. In fact, the closest analogue to zypper dist-upgrade (zypper dup) is dnf distro-sync (dnf dsync).
For Tumbleweed, dnf system-upgrade won't be particularly useful, though dnf offline-distrosync would be.
@sfalken@vwbusguy People are expected to use dnf offline-distrosync if they're running Rawhide. I actually use it when I'm running development Fedora releases too.
@vwbusguy@Conan_Kudo well, Rawhide is roughly the Factory equivalent, as I understand it, but I could be wrong, my understanding of Fedora development is very surface level
@vwbusguy@sfalken Yup. Rawhide as people normally get it is based on composes that go through gating and testing. Bypassing that by adding the Koji internal repo would get you the equivalent of Factory.
@vwbusguy dup is how you upgrade Tumbleweed. zypper up on Tumbleweed, is eventually going to get you a broken system. You quite literally update Tumbleweed to match the currently available snapshot of Tumbleweed in the repos.
Add comment