On 2024-03-05 16:01:10 +0100, Sebastian Ramacher wrote: > Hi > > On 2024-03-05 15:42:49 +0100, Pierre-Elliott Bécue wrote: > > Hello, > > > > Sebastian Ramacher <sramac...@debian.org> wrote on 05/03/2024 at > > 09:38:13+0100: > > > > > Source: owncloud-client > > > Version: 4.2.0.11670+dfsg-1.1 > > > Severity: serious > > > Tags: ftbfs > > > X-Debbugs-Cc: sramac...@debian.org > > > > > > Version check failed: > > > Your upload included the binary package dolphin-owncloud, version > > > 4.2.0.11670+dfsg-1.1, for amd64, > > > however unstable already has version 5.0.0-1+b1. > > > Uploads to unstable must have a higher version than present in unstable. > > > > > > Cheers > > > > owncloud-client has been uploaded far before in the past, and was > > shipping dolphin-owncloud, nautilus-owncloud, et al. > > > > In client v5, upstream removed these packages from the owncloud-client > > source, and therefore they're now packaged through dedicated source > > packages. > > > > These ones are the latest uploads. > > > > I'll upload the v5 version of owncloud-client source package which won't > > ship dolphin-owncloud et al anymore. > > > > It's what's been suggested to me, and therefore I can't see a bug here. > > > > Could you give me a bit more intel aobut why this would be a serious > > bug? > > The uploads by the buidds fail to be included in the archive since the > constraints are not satisfied. You can check the reject files for the > changes files from owncloud-client on coccia.d.o. > > You can also see on > https://buildd.debian.org/status/package.php?p=owncloud-client&suite=sid > that the package is stuck in Uploaded state due to this issue.
FWIW, the dolphin-owncloud binary package is provided with a higher version number by owncloud-client-desktop-shell-integration-dolphin. I suppose the dolphin-owncloud package can just be dropped from owncloud-client. Cheers -- Sebastian Ramacher
