Release to unstable
Simon McVittie
3 years ago
| 0 | avahi (0.8-3) unstable; urgency=medium | |
| 1 | ||
| 2 | * Team upload | |
| 3 | * Upload python3-avahi to unstable | |
| 4 | * d/control: Add comments about why some packages are Arch: any. | |
| 5 | At first glance these packages seem like they should be | |
| 6 | Architecture: all, but in fact they cannot. | |
| 7 | * d/control, d/shlibs.local: Tighten interdependencies within src:avahi. | |
| 8 | Co-installation of binary packages built from different versions of the | |
| 9 | same source package is error-prone, because parts of the same source | |
| 10 | package typically make assumptions about non-public exported symbols, | |
| 11 | implementation details or precise behaviour beyond what's in the public | |
| 12 | API. Upstream developers are also unlikely to be willing to support such | |
| 13 | installations or make promises about their behaviour. | |
| 14 | We can make partial upgrades more robust by upgrading everything from | |
| 15 | a single source package together. | |
| 16 | ||
| 17 | -- Simon McVittie <smcv@debian.org> Tue, 26 May 2020 11:33:06 +0100 | |
| 18 | ||
| 0 | 19 | avahi (0.8-2) experimental; urgency=medium |
| 1 | 20 | |
| 2 | 21 | * Team upload |