Bug#973644: mes should be Architecture: amd64 armel armhf i386

2020-11-18 Thread Vagrant Cascadian
Control: tag 973644 pending On 2020-11-03, Adrian Bunk wrote: > On Mon, Nov 02, 2020 at 01:56:03PM -0800, Vagrant Cascadian wrote: >> On 2020-11-02, Adrian Bunk wrote: >> > "amd64 armel armhf i386" are the architectures supported upstream >> > (32bit arm needs some files that are in upsteam but

Bug#973644: mes should be Architecture: amd64 armel armhf i386

2020-11-02 Thread Adrian Bunk
On Mon, Nov 02, 2020 at 01:56:03PM -0800, Vagrant Cascadian wrote: > On 2020-11-02, Adrian Bunk wrote: > > Source: mes > > Version: 0.22-4 > > Severity: important > > Tags: ftbfs > > > > "amd64 armel armhf i386" are the architectures supported upstream > > (32bit arm needs some files that are in

Bug#973644: mes should be Architecture: amd64 armel armhf i386

2020-11-02 Thread Vagrant Cascadian
On 2020-11-02, Adrian Bunk wrote: > Source: mes > Version: 0.22-4 > Severity: important > Tags: ftbfs > > "amd64 armel armhf i386" are the architectures supported upstream > (32bit arm needs some files that are in upsteam but missing in the > 0.22 release tarball). There is work on adding more

Bug#973644: mes should be Architecture: amd64 armel armhf i386

2020-11-02 Thread Adrian Bunk
Source: mes Version: 0.22-4 Severity: important Tags: ftbfs "amd64 armel armhf i386" are the architectures supported upstream (32bit arm needs some files that are in upsteam but missing in the 0.22 release tarball).