While I’m using ktorrent as an example package I’m seeking to better understand the design of these repos better.
I’m confused why the Leap 42.3 KDE Extra repo contain the newest build of ktorrent - newer than both the Tumbleweed OSS and Tumbleweed KDE Extra repo.
Tumbleweed OSS: ktorrent-5.0.1-3.2. 13-Jun3-2017
Tumbleweed Extra: ktorrent-5.0.1-36.3 15-June-2017
Leap 42.3 Extra: ktorrent-5.0.1-36.16. 5-July-2017
The tumbleweed OSS repo has the oldest build, and the tumbleweed KDE extra repo has a build version in between Leap and Tumbleweed?
It seems non-intuitive the place to find the latest build of ktorrent is in a repo for tumbleweed not mentioned on the wiki page for the KDE extras repo, and that the tumbleweed OSS repo contains the oldest of all versions.
http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/ktorrent-5.0.1-3.2.x86_64.rpm
http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.3/x86_64/ktorrent-5.0.1-36.16.x86_64.rpm
http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Tumbleweed/x86_64/ktorrent-5.0.1-36.3.x86_64.rpm
Further, why is there a KDE extra repo for tumbleweed given:
https://en.opensuse.org/SDB:KDE_repositories#Get_the_latest_KDE_3_Packages
“Tumbleweed users do not need (but can, if they want) to use it, as new releases are submitted to Tumbleweed as soon as they’re available, and are usually pushed to standard repositories in a matter of days.”
Interestingly the above page contains links for the KDE extra’s repo for LEAP, but not for Tumbleweed, though such exists.
AFAICS all the packages are -5.0.1, so the same version. The rest of the version, AFAICT this time, is no more than buildversions from OBS
Ah - thanks. The changelogs below show they are in fact the same.
What purpose does the tumbleweed KDE extras repo serve then?
Cheers
calculus:~ # rpm -qi --changelog ktorrent
Name : ktorrent
Version : 5.0.1
Release : 3.2
Architecture: x86_64
Install Date: Sat Jul 1 22:21:56 2017
Group : Productivity/Networking/File-Sharing
Size : 3496477
License : GPL-2.0+
Signature : RSA/SHA256, Tue Jun 13 13:21:46 2017, Key ID b88b2fd43dbdc284
Source RPM : ktorrent-5.0.1-3.2.src.rpm
Build Date : Tue May 23 08:00:00 2017
Build Host : lamb61
Relocations : (not relocatable)
Packager : https://bugs.opensuse.org
Vendor : openSUSE
URL : http://ktorrent.org/
Summary : KDE BitTorrent Client
Description :
KTorrent is a bittorrent application for KDE which allows you to download files
using the BitTorrent protocol. It enables you to run multiple torrents at the
same time and comes with extended features to make it a full-featured client
for BitTorrent.
Distribution: openSUSE Tumbleweed
* Tue May 23 2017 wbauer@tmo.at
- Add fix-crash-when-loading-bandwidth-scheduler-plugin.patch and
fix-crashes-in-bwscheduler-plugin.patch from upstream to fix
ktorrent crashing when the bandwidth scheduler plugin is
activated/used (kde#361863, boo#1040379)
* Wed Feb 01 2017 adam.majer@suse.de
- use individual libboost-*-devel packages instead of boost-devel
vs
calculus:~ # wget http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Tumbleweed/x86_64/ktorrent-5.0.1-36.4.x86_64.rpm
calculus:~ # rpm -qp --changelog ktorrent-5.0.1-36.4.x86_64.rpm
warning: ktorrent-5.0.1-36.4.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 0d210a40: NOKEY
* Tue May 23 2017 wbauer@tmo.at
- Add fix-crash-when-loading-bandwidth-scheduler-plugin.patch and
fix-crashes-in-bwscheduler-plugin.patch from upstream to fix
ktorrent crashing when the bandwidth scheduler plugin is
activated/used (kde#361863, boo#1040379)
* Wed Feb 01 2017 adam.majer@suse.de
- use individual libboost-*-devel packages instead of boost-devel
Good question, since it’s been added to TW, I don’t see much use of this package living in the KDE:Extra repo.
KDE:Extra is the development project for Tumbleweed.
If ktorrent wouldn’t be in KDE:Extra, it couldn’t be in Tumbleweed (or Leap) either… 
And changes have to be made in KDE:Extra first before they can be submitted to Tumbleweed.
In this case, only the rebuild count is different though, as mentioned.
The packages are in fact the same (in KDE:Extra, TW, and 42.3), there hasn’t been a change since May.
This rebuild count is absolutely meaningless if you compare different repos (or even the same repo for different distributions)…
OBS does e.g. rebuild packages automatically if one of the dependencies changes.
PS, to address another question:
KDE:Extra also contains stuff that is not part of Tumbleweed or Leap (yet).
For the standard packages that are in the distribution, there’s indeed no point in using KDE:Extra, as the updates are submitted to TW anyway.
You’d just get updates a few days earlier, before they are tested.