package install fails.

[Jay R. Wren]

on a fresh bionic install (cloudimg)

apt install tinyproxy fails due to bad assumptions in dpkg install scripts.

```
Setting up tinyproxy (1.10.0-1) ...
chmod: cannot access '/var/log/tinyproxy/*': No such file or directory
dpkg: error processing package tinyproxy (--configure):
 installed tinyproxy package post-installation script subprocess returned error exit status 1
```

I touch a file in that directory so that glob matches and it exists, and run again:

```
Setting up tinyproxy (1.10.0-1) ...
chown: cannot access '/var/log/tinyproxy.*': No such file or directory
dpkg: error processing package tinyproxy (--configure):
 installed tinyproxy package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 tinyproxy
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

I touch a file matching that glob and try again:

```
$ sudo touch /var/log/tinyproxy.delme
...
Setting up tinyproxy (1.10.0-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/tinyproxy.service → /lib/systemd/system/t
inyproxy.service.
```

Expected: ability to install the tinyproxy package without workarounds.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Unit 193 (unit193)]

G'day.

In a "better late than never", this bug was fixed back in 2018 with commits https://salsa.debian.org/debian/tinyproxy/-/commit/f9324a7fcc9870b3fb58671dbd51d6a568e37e01 and https://salsa.debian.org/debian/tinyproxy/-/commit/635d924d866ba9fca148427d196f1416e8e800fe, which were included in 1.10.0-2 onwards.

Thanks.