[Pkg-owncloud-maintainers] Nextcloud desktop client packaging

[Sandro Knauß]

Hey,

> I am maintaining a PPA for mostly beta and alpha Ubuntu packages of the
> Nextcloud desktop client as well as ab OpenSUSE Build System repository for
> Debian packages.

Cool to actually get contact. Let's move the discussion to the maintainers 
list, as I'm not the only person that is packaging nextcloud-desktop for 
Debian.
 
> Recently it has been reported that there is a clash  between the official
> Debian/Ubuntu packages and mine due to some files placed in different
> packages. Also, the name of the main package is different
> ("nextcloud-client" vs "nextcloud-desktop").
> 
> I think it would be useful to have common Debian build control files that
> both of us work with. My files are in the upstream
> repo's admin/linux/debian directory. As you can see there are slight
> differences between the various distributions, so it is not as simple as
> having a single debian directory in the repository's root directory.
> 
> Do you think there is a way to unify the build control files that suits
> both of us? It is OK for me to use your package structure (i.e. name the
> main package "nextcloud-desktop", etc.), though of course transitional
> packages should be provided in the PPA. But the differences between the
> various distributions should be handled somehow.

Packaging data is updated after Nextcloud released a version, so having the 
files inside the upstream repo is wired. Also we often need to apply patches on 
top of the releases, as they are not perfect. What Debian is doing is having a 
parent branch, that is the master branch of upstream and the master branch is 
actually an overlay with the Debian files. see [1]. From our side, the obvious 
step would be, that you publish your packaging data to our salsa repository 
and have branches for the different distribution. 
Also I do not understand how I should interpret the data under admin/linux/
debian, as this is not standard Debian packaging style. Btw. the changelog in 
these directories refer to version 2.3.3 in the 2.6.1 release.
If we have all data at one place we can start looking into the differences and 
properly find ways to unify stuff.

hefee

[1] https://salsa.debian.org/owncloud-team/nextcloud-desktop
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-owncloud-maintainers/attachments/20200131/16248744/attachment.sig>