bleh that's a detail that I did not know (and since we don't have pdk
yet we can only check manually wrt online documentation :S)

bumping the version in the metadata.json file too so that it corresponds
to the tag that'll go on this commit

name should be $user-$project (as in $user in terms of puppet forge..
but it can be whatever we want if we don't publish)

the licnse was specified in metadata.json but it's clearer if we have
the actual license text available in the repository

I can't fix the warning about cross-namespace (cross-module)
inheritance. This class should probably be removed entirely but I won't
call this shot now without talking a bit more about it with others.

Support an $ensure parameter in the base class.

See merge request !3

Make multi-repository handling actually usable.

See merge request !1

https://gitlab.com/shared-puppet-modules-group/reprepro/merge_requests/1#note_12894797

It previously could not be used because of non-unique resources, such as
File[/etc/init.d/reprepro].

This commit makes all such resources I could spot per-repository.

This reverts commit 28b9219c.

Conflicts:
	manifests/repository.pp

Conflicts:
	manifests/repository.pp

This makes it impossible to apply a catalog on a VM with 512MB of RAM (that has
1.5k files in pool/, and 10k files in dists/).

Apparently, the change is only needed when "we change the owner of
a repository", which looks rare enough to me not to deserve such implications.
A better way to support this usecase should be found.

This reverts commit 4f8da394.

Conflicts:
	manifests/repository.pp

This reverts commit c301116d.

After quickly discussing this on IRC, I see no convincing reason for this move.
(For the record, my /var/log/incoming.log is owned by reprepro:root and has
stuff in it.) Unless we have a pretty good reason, let's respect the FHS.

/var/log/reprepro/$repository/incoming.log + log rotation would probably be even
better, but well.

Conflicts:
	manifests/repository.pp

Conflicts:
	manifests/repository.pp

Conflicts:
	manifests/repository.pp

Conflicts:
	manifests/repository.pp

Conflicts:
	manifests/repository.pp

this is necessary when we change the owner of a repository. if we do
not change otherwise permissions will not update