New adminer version

[lamby]

I just noticed on my developer dashboard that there is a new version of adminer:

https://qa.debian.org/cgi-bin/watch?pkg=adminer

Should I go ahead and package it with a backport?

[JedMeister]

Leave it with me if you don't mind. My inclination is to say yes, but my head is pretty busy right now! 😂

[lamby]

I went ahead with uploading the new version (https://tracker.debian.org/news/927911) which has now migrated to testing (https://tracker.debian.org/news/928890). It can thus now be backported to stetch-backports.

[lamby]

There is now another version, 4.6.1. Short changelog is:

Sticky position of table actions
Speed up rendering of long tables (regression from 4.4.0)
Display notification about performing action after relogin
Add system tables help links
MySQL: Support non-utf8 charset in search in column
MySQL: Support geometry in MySQL 8 (bug #574)
MariaDB: Links to documentation
SQLite: Allow deleting PRIMARY KEY from tables with auto increment
PostgreSQL: Support binary files in bytea fields
PostgreSQL: Don't treat interval type as number (bug #474)
PostgreSQL: Cast to string when searching using LIKE (bug #325)
PostgreSQL: Fix condition for selecting no rows
PostgreSQL: Support TRUNCATE+INSERT export
Customization: Support connecting to MySQL via SSL
Customization: Allow specifying server name displayed in breadcrumbs

[lamby]

4.6.1 uploaded

This also resulted in an improvement to @debian's lintian... https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=88df93d6bd9deefdf52437aeeaa694adc5bd0ed6

[lamby]

4.6.1-1 hit testing, so could be backported. Let me know :)

[lamby]

4.6.2-1 uploaded to unstable FYI :)

[lamby]

4.6.2-1 hit testing so can be backported

[JedMeister]

@lamby - how long does it take to prepare and upload a backport before it's available to apt?

I.e. If I asked you to upload a backport today, when could I install it (from stretch-backports)?

PS just to make it completely clear; I don't want this done yet, I'm just wondering how long it would take - so I can factor it in to our release cycle.

[lamby]

Once it's in testing, about 6/12 hours?

[JedMeister]

Once it's in testing, about 6/12 hours?

Perfect! :smile:

So my inclination would be to wait until a few days before we are ready for release and get you to do it then. That way we can include the latest version (that you've packaged). If things go according to plan, that will probably be this particular version. But seeing as things rarely seem to go to plan around here, if there is an update in the meantime, we can increase the chances of getting that included in the release.

Obviously there is the wait (5 days minimum IIRC?) in 'unstable' before a new version migrates to 'testing' (and it can only be backported once it's in 'testing'). So I think odds are that we'll be including 4.6.2-1 but it's nice to keep the options open.

Thanks again mate! You rock!

[lamby]

So my inclination would be to wait until a few days before we are ready for release and get you to do it then. […]

Makes sense. Just let me know :)