Hi,
I think with the removal of the transitional libmariadbclient18 from
testing we can consider this transition as finished. The corresponding
manual tracker should be archived as well, there are only a few sid-only
packages left depending on cruft.
Andreas
Hi,
On 3/23/19 2:26 AM, Andreas Beckmann wrote:
On 2019-03-20 12:28, Emilio Pozuelo Monfort wrote:
On 20/03/2019 00:49, Andreas Beckmann wrote:
please give-back qt4-x11. A build has succeeded today in my pbuilder sid
Scheduled.
That worked. What needs to be done to make the three late bin
Hi,
On 2019-03-20 12:28, Emilio Pozuelo Monfort wrote:
> On 20/03/2019 00:49, Andreas Beckmann wrote:
>> please give-back qt4-x11. A build has succeeded today in my pbuilder sid
> Scheduled.
That worked. What needs to be done to make the three late binNMUs
migrate to testing? Does not seem to ha
On 20/03/2019 00:49, Andreas Beckmann wrote:
> Hi,
>
> please give-back qt4-x11. A build has succeeded today in my pbuilder sid
> amd64 and i386 chroot, so this was probably a compiler realted issue, it
> was failing previously nowhere near mysql/mariadb touching code.
>
> gb qt4-x11_4:4.8.7+dfsg
Hi,
please give-back qt4-x11. A build has succeeded today in my pbuilder sid
amd64 and i386 chroot, so this was probably a compiler realted issue, it
was failing previously nowhere near mysql/mariadb touching code.
gb qt4-x11_4:4.8.7+dfsg-17 . ANY
Andreas
On 08/03/2019 12:48, Andreas Beckmann wrote:
> On 2019-01-31 13:55, Andreas Beckmann wrote:
>> There is one package not covered by the tracker since it only
>> indirectly depends on default-libmysqlclient-dev.
>>
>> nmu kannel-sqlbox_0.7.2-5 . ANY . unstable . -m "Rebuild against libmariadb3"
>
>
On 08/03/2019 12:48, Andreas Beckmann wrote:
> On 2019-01-31 13:55, Andreas Beckmann wrote:
>> There is one package not covered by the tracker since it only
>> indirectly depends on default-libmysqlclient-dev.
>>
>> nmu kannel-sqlbox_0.7.2-5 . ANY . unstable . -m "Rebuild against libmariadb3"
>
>
On 2019-01-31 13:55, Andreas Beckmann wrote:
> There is one package not covered by the tracker since it only
> indirectly depends on default-libmysqlclient-dev.
>
> nmu kannel-sqlbox_0.7.2-5 . ANY . unstable . -m "Rebuild against libmariadb3"
Ping?
And please give-back lua-sql, the FTBFS is fix
On 2019-01-28 15:45, Emilio Pozuelo Monfort wrote:
>> Please schedule the remaining binNMUs s.t. the packages drop the
>> dependency on the transitional libmariadbclient18 package.
>
> I have scheduled level 1. Will do level 2 later.
There is one package not covered by the tracker since it only
On 27/01/2019 15:18, Andreas Beckmann wrote:
> Hi,
>
> mariadb-10.3 finally migrated to testing and mariadb-10.1 was just
> removed from unstable, so it should leave testing soon as well.
>
> Please schedule the remaining binNMUs s.t. the packages drop the
> dependency on the transitional libmari
Hi,
mariadb-10.3 finally migrated to testing and mariadb-10.1 was just
removed from unstable, so it should leave testing soon as well.
Please schedule the remaining binNMUs s.t. the packages drop the
dependency on the transitional libmariadbclient18 package.
Thanks
Andreas
On 2019-01-20 12:04, Otto Kekäläinen wrote:
> Is there some way for me to test this transition manually? I have
> tested many times upgrading systems with Stretch/MariaDB 10.1 to
> Sid/MariaDB 10.3 but did not bump into any issues.
I tried this manually in pbuilder/buster to understand what proble
su 20. tammik. 2019 klo 1.44 Andreas Beckmann (a...@debian.org) kirjoitti:
>
> On 2019-01-19 21:14, Andreas Beckmann wrote:
> > Getting back to the current case: I assume this is caused by
> > libmariadbclient-dev being turned into a virtual package provided by
> > libmariadb-dev. I'll test whether
On 2019-01-19 21:14, Andreas Beckmann wrote:
> Getting back to the current case: I assume this is caused by
> libmariadbclient-dev being turned into a virtual package provided by
> libmariadb-dev. I'll test whether reintroducing a transitional package
> would improve the situation. Might require a
[ changed recients to #919395 (transition bug) + pkg-mysql-maint,
dropping upstream developers ]
On 2019-01-18 11:44, Emilio Pozuelo Monfort wrote:
> The problem was that the old libdbd-mariadb-perl didn't work with the new
> mariadb-10.3, so without a Breaks relationship in mariadb-10.3, there
On 18/01/2019 10:59, Olaf van der Spek wrote:
> On Thu, Jan 17, 2019 at 3:37 PM Emilio Pozuelo Monfort
> wrote:
>> That was with the old libdbd-mariadb-perl, and the new one (which was fine)
>> wasn't migrating due to a build-dep on the new mysql-defaults, which was
>> blocked
>> on mariadb-10.3
On Thu, Jan 17, 2019 at 3:37 PM Emilio Pozuelo Monfort wrote:
> That was with the old libdbd-mariadb-perl, and the new one (which was fine)
> wasn't migrating due to a build-dep on the new mysql-defaults, which was
> blocked
> on mariadb-10.3, blocked on libdbd-mariadb-perl... I cheated a bit and
On 12/01/2019 19:50, Otto Kekäläinen wrote:
>> Go ahead with that upload.
>
> Done yesterday and builds went OK:
> https://tracker.debian.org/pkg/mariadb-10.3
>
> Ironically we have a new regression now in the Perl module designed
> for MariaDB (ibdbd-mariadb-perl/1.10-1): autopkgtests now fail
>
> Go ahead with that upload.
Done yesterday and builds went OK:
https://tracker.debian.org/pkg/mariadb-10.3
Ironically we have a new regression now in the Perl module designed
for MariaDB (ibdbd-mariadb-perl/1.10-1): autopkgtests now fail
apparently because there is a ' character wrong in the tes
On 11/01/2019 10:07, Otto Kekäläinen wrote:
> Hello!
>
> ma 7. tammik. 2019 klo 10.38 Otto Kekäläinen (o...@debian.org) kirjoitti:
>>
>> ma 7. tammik. 2019 klo 11.20 Emilio Pozuelo Monfort (po...@debian.org)
>> kirjoitti:
>> ..
>>> https://packages.qa.debian.org/m/mariadb-10.3.html points to an au
Hello!
ma 7. tammik. 2019 klo 10.38 Otto Kekäläinen (o...@debian.org) kirjoitti:
>
> ma 7. tammik. 2019 klo 11.20 Emilio Pozuelo Monfort (po...@debian.org)
> kirjoitti:
> ..
> > https://packages.qa.debian.org/m/mariadb-10.3.html points to an autopkgtest
> > failure on pam-mysql too, though that on
ma 7. tammik. 2019 klo 11.20 Emilio Pozuelo Monfort (po...@debian.org)
kirjoitti:
..
> https://packages.qa.debian.org/m/mariadb-10.3.html points to an autopkgtest
> failure on pam-mysql too, though that one doesn't seem to have a corresponding
> bug report yet.
That's right, there is no bug report
Hi Otto,
On 06/01/2019 16:08, Otto Kekäläinen wrote:
> Hello!
>
> I just realized that the upload of mariadb-10.3 into Debian includes
> the following transitions:
> - libmariadbd18 -> libmariadbd19
> - libmariadbclient18 becomes deprecated and fully replaced by the
> libmariadb3 library already
Hello!
I just realized that the upload of mariadb-10.3 into Debian includes
the following transitions:
- libmariadbd18 -> libmariadbd19
- libmariadbclient18 becomes deprecated and fully replaced by the
libmariadb3 library already in Debian for a longer time (source
package mariadb-connector-c)
Te
24 matches
Mail list logo
