unknown-section varnish-6.0/web
  Section: @SECTION@/web -> Section: web
  Section: @SECTION/libdevel -> libdevel
  The substitution line in the package-deb script got removed:
  sed -i -e "s|@SECTION@|varnish-$MAJOR|" "$DIST_DIR/debian/control

copyright-without-copyright-notice:
  The copyright file expected a certain 3 line header:
      Copyright YYYY Firstname Lastname <address@example.com>
      Copr. YYYY-YYYY Firstname Lastname <address@example.com>
      © YYYY,YYYY Firstname Lastname <address@example.com>

Added debian/source/format file with content "1.0"

READMEs:
 - Installing again the once-installed README.rst and README.packaging

VCLs:
- A non-commented version of builtin.vcl is not installed into
/usr/share/doc/varnish/examples anymore.

Fixes #104

While ultimately the goal is to automate virtual provides and requires
to the extent of out-of-tree modules, considering that for now package
maintainers would have to manually adjust their requirements, they
couldn't easily manage either 32bit or 64bit dependencies in a single
Requires tag. While we don't ship 32bit packages, distributions like
Fedora do.

Now a user can easily target the right architecture on a multilib system
with a single dependency:

    Requires: varnishd(abi)%{?_isa} = sha1

This is already part of the upgrade notes I'm redacting and I will amend
the wiki accordingly.

In other words on 64bit systems:

    Provides: varnishd(abi)(64bit) = sha1
    Provides: varnishd(vrt)(64bit) = x.y

Same as VMOD virtual provides.

Although this one wasn't handled before so I'm not certain it makes any
difference to just say sections "web" and "libdev" even for our repos.

And simplify its neighbor.

We can already deduce the name expected by DPKG or RPM from what we
have.

With more comments this time!

As per discussion, to better facilitate alternate init-
systems and re-packaging efforts, we want to keep in the
sysv versions of the packaging files.

In other words, we get that part of the release tag from upstream
already.

Same as traditional shared objects, it now looks like this:

    varnish = x.y.z-r
    varnish(x86-64) = x.y.z-r
    libvarnishapi.so.1()(64bit)
    libvarnishapi.so.1(LIBVARNISHAPI_2.0)(64bit)
    varnishd(abi) = sha1
    varnishd(vrt) = a.b
    vmod(blob)(64bit) = x.y.z-r
    vmod(directors)(64bit) = x.y.z-r
    vmod(purge)(64bit) = x.y.z-r
    vmod(std)(64bit) = x.y.z-r
    vmod(vtc)(64bit) = x.y.z-r

Maybe varnishd(*) provides should be ISA-bits-aware too.

Since we wrap calls to the original find-provides it loses the ability
to do that so it becomes our responsibility.

A bit fragile when it comes to grabbing the version.

This change aligns DPKG provides to their RPM counterparts with one
notable exception: the ABI being a hash, it may start with a letter
and go against DPKG's policy. Since it's only used for strict equality
this is not a problem.

The new provides look like this:

    Provides:
     libvarnishapi1,
     varnish,
     varnishd-abi-sha1
     varnishd-vrt (= x.y)

Partially fixes #8 because in order to make this useful for VMODs
without forcing package maintainers to manually require either the
exact ABI or a given VRT version, a means for automatic requires
for VMOD builds is missing. This doesn't address the NOGIT case,
but we don't support packaging not originating from a git commit.

Unlike RPM packaging, this does not list installed VMODs, as I'm
not certain it can be done in the first place (probably though).

Refs c6d66785
Closes #92

Maybe we should rename common/ to systemd/ as well.

While at it, add some polish to the overall script and simplify the
different cases.