Control: reassign -1 release.debian.org
Control: user release.debian@packages.debian.org
Control: usertags -1 binnmu
Control: severity -1 normal
Control: retitle -1 nmu: mariadb-10.1_10.1.21-5
On 14 Feb 2017, at 22:00, Otto Kekäläinen wrote:
>> 2017-02-14 23:58 GMT+02:00 James Clarke :
>>> On
2017-02-14 23:58 GMT+02:00 James Clarke :
>> On 14 Feb 2017, at 21:54, Otto Kekäläinen wrote:
>>
>> So you suggest I upload 10.1.21-6 and go though all the hassle of
>> filing unblocks etc? Is there no possibility to trigger a rebuild on
>> amd64 with the current source package?
>
> I don't know w
> On 14 Feb 2017, at 21:54, Otto Kekäläinen wrote:
>
> So you suggest I upload 10.1.21-6 and go though all the hassle of
> filing unblocks etc? Is there no possibility to trigger a rebuild on
> amd64 with the current source package?
I don't know which is preferred, just that both solve the probl
So you suggest I upload 10.1.21-6 and go though all the hassle of
filing unblocks etc? Is there no possibility to trigger a rebuild on
amd64 with the current source package?
Source: mariadb-10.1
Version: 10.1.21-5
Severity: serious
As can be seen in the discussion for #852709, the source+amd64 upload
for 10.1.21-5 did not include mariadb-plugin-tokudb, despite the
package's architecture being base-any-any-amd64. Either a binNMU or a
new source upload is needed (a test
5 matches
Mail list logo
