There is an additional reason to use Origins-Pattern, which is that some package repos cannot be expressed with an Allowed-Origin: in particular, any repo which has a colon in its Origin field, for example the archive at www.openprinting.org, which has the origin field:
It is impossible to escape the colon to satisfy unattended-upgrade as an Allowed-Origin pattern, so rather than add another hack to unattended-upgrade, it would seem better to switch to using the Origins-Pattern setting instead.
There is an additional reason to use Origins-Pattern, which is that some package repos cannot be expressed with an Allowed-Origin: in particular, any repo which has a colon in its Origin field, for example the archive at www.openprintin g.org, which has the origin field:
\http:// www.openprintin g.org/download/ printdriver/ debian/\
It is impossible to escape the colon to satisfy unattended-upgrade as an Allowed-Origin pattern, so rather than add another hack to unattended-upgrade, it would seem better to switch to using the Origins-Pattern setting instead.