On Tue, 2020-11-24 at 22:17 +0200, Otto Kekäläinen wrote:
> > Well, my point was more that we already have buster > unstable, and
> > that I was assuming you'd fix that by uploading a package to
> > unstable, rather than an even newer package to buster. :-)
>
> As MariaDB 10.5 is already in unstab
> Well, my point was more that we already have buster > unstable, and
> that I was assuming you'd fix that by uploading a package to unstable,
> rather than an even newer package to buster. :-)
As MariaDB 10.5 is already in unstable, it is in practice impossible
to do any 10.3 uploads to unstable
Hello!
On Tue, 24 Nov 2020 at 21:08, Adam D. Barratt wrote:
..
> I see there's a mariadb-10.3 update in experimental (for 10.3.27).
> Based on the above, I assume that an upload to unstable is also
> planned?
No, that was an experiment which turned out to be a very stupid one
and I will no pursu
On Tue, 2020-11-24 at 22:02 +0200, Otto Kekäläinen wrote:
> Hello!
>
> On Tue, 24 Nov 2020 at 21:08, Adam D. Barratt <
> a...@adam-barratt.org.uk> wrote:
> mariadb-10.3 is one of the packages that I was looking at in
> > relation to the upcoming stable point release (in a week and a
> > bit's time
On Sun, 2020-11-22 at 16:48 +0200, Otto Kekäläinen wrote:
> > If you want to keep src:mariadb-10.3 around, one or the other. Or
> > you could upload a new version of mariadb-10.3 which drops the
> > package.
>
> Ok, I will upload a new 10.3. I want it to stay around for a bit more
> until the tran
> If you want to keep src:mariadb-10.3 around, one or the other. Or you
> could upload a new version of mariadb-10.3 which drops the package.
Ok, I will upload a new 10.3. I want it to stay around for a bit more
until the transition of 10.5 is fully completed and verified to
replace 10.3 in full.
Hi Otto,
On 22-11-2020 14:41, Otto Kekäläinen wrote:
> This is a temporary transitional package that does not exist in 10.5
> anymore: https://packages.debian.org/unstable/libmariadbclient-dev
This is a binary from mariadb-10.3. We discussed before, it shouldn't be
part of bullseye, right? What y
> https://release.debian.org/britney/update_output.txt.gz says this;
>
> trying: mariadb-10.5
> skipped: mariadb-10.5 (1, 0, 30)
> got: 31+0: a-1:a-27:a-1:a-0:i-0:m-0:m-0:p-0:s-2
> * s390x: libmariadbclient-dev
>
> So, migrating mariadb-10.5 to testing would make libmariadbclient-dev
> non-
Hi Otto,
On 22-11-2020 14:11, Otto Kekäläinen wrote:
>> Could you please add some whitelist/override for debci so that at
>> least the issue of "autopkgtest for mariadb-10.3/1:10.3.24-2" failing
>> would go away [...]
>
> I see you did this in https://release.debian.org/britney/hints/elbrus, than
Hello!
> Could you please add some whitelist/override for debci so that at
> least the issue of "autopkgtest for mariadb-10.3/1:10.3.24-2" failing
> would go away [...]
I see you did this in https://release.debian.org/britney/hints/elbrus, thanks!
We also found a hack to get around the amrhf bui
Hello!
> To start with item 2:
>
> > 2) autopkgtest for mariadb-10.3/1:10.3.24-2 fail on i386 (and armhf
> > when it build earlier this month). The test is installing
> > "mariadb-server" which in unstable pulls in mariadb-10.5. I silenced
> > this false positive (or indifferent failure of access
On 2020-10-29 20:29:34 +0200, Otto Kekäläinen wrote:
> Hello!
>
> > > 1) Builds on armhf stopped working earlier this month due to compiler
> > > bug #972564, perhaps in cmake or gcc. Upstream gcc has confirmed at
> > > least one issue. There is no schedule on when it will be fixed and
> > > there
Hello!
> > 1) Builds on armhf stopped working earlier this month due to compiler
> > bug #972564, perhaps in cmake or gcc. Upstream gcc has confirmed at
> > least one issue. There is no schedule on when it will be fixed and
> > there is nothing to my knowledge that I could reasonably do about
> >
Hi Otto,
On 29-10-2020 16:28, Otto Kekäläinen wrote:
> I kindly ask assistance from the Debian release team what to do about
> MariaDB 10.5.
I think it's good that you reach out.
> I have been working on MariaDB 10.5 packaging since August[1] and I've
> had it in unstable since early September[2
Hello!
I kindly ask assistance from the Debian release team what to do about
MariaDB 10.5.
I have been working on MariaDB 10.5 packaging since August[1] and I've
had it in unstable since early September[2]. It is currently however
stuck on two migration excuses:
1) Builds on armhf stopped workin
15 matches
Mail list logo
