Package: g++-13
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Would it be possible to provide GCC 13 for Bookworm, perhaps via backports?
Olaf
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Package: httping
Version: 2.5-5.2+b1
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Hi,
A new version has been released upstream:
https://github.com/folkertvanheusden/HTTPing/releases
Olaf
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500,
Op wo 19 apr 2023 om 06:04 schreef Anton Gladky :
>
> Hi,
>
> boost-defaults_1.81.0 is in experimental. But boost1.81
> is also available in the Debian Bookworm [1].
>
> [1] https://packages.debian.org/source/testing/boost1.81
Hi Anton,
Ah, it's even available in bpo, thanks a lot!
--
Olaf
Package: cmake
Followup-For: Bug #1024294
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Nevermind, it seems to be an unrelated issue:
# apt install cmake
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed.
Package: cmake
Version: 3.24.3-1
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Maybe not a bug, but why does cmake conflict with this kernel image?
Greetings,
Olaf
# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state
Op ma 26 sep. 2022 om 15:19 schreef Marc Haber
:
>
> On Mon, Sep 26, 2022 at 03:18:39PM +0200, Marc Haber wrote:
> > Thanks for spotting this. Fixed in git. MR 65 created.
>
> In the mean time, find the information on salsa:
>
> https://salsa.debian.org/debian/adduser/-/blob/master/debian/README
Package: adduser
Version: 3.129
Severity: normal
X-Debbugs-Cc: olafvds...@gmail.com
Hi,
> See /usr/share/doc/adduser/README.Debian for detailed reasoning.
$ cat /usr/share/doc/adduser/README.Debian
cat: /usr/share/doc/adduser/README.Debian: No such file or directory
$ l /usr/share/doc/adduser
Package: libc6
Version: 2.31-13
Followup-For: Bug #990069
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
The original issue of not being able to open a new SSH connection during the
upgrade still seems to be present.
Greetings,
Olaf
-- System Information:
Debian Release: 11.0
APT
Op di 6 jul. 2021 om 22:21 schreef Debian Bug Tracking System
:
> Changes:
> glibc (2.31-13) unstable; urgency=medium
> .
>[ Colin Watson ]
>* debian/debhelper.in/libc.postinst, script.in/nsscheck.sh: Look for
> openssh-server package rather than ssh. Closes: #990069
Hi,
I tried
On Tue, Jul 6, 2021 at 1:19 AM Otto Kekäläinen wrote:
>
> On Mon, Jul 5, 2021 at 1:12 PM Olaf van der Spek wrote:
> >
> > On Mon, Jul 5, 2021 at 9:24 PM Otto Kekäläinen wrote:
> > > I wish somebody could contribute with exact steps on how to reproduce
> > >
On Mon, Jul 5, 2021 at 9:24 PM Otto Kekäläinen wrote:
> I wish somebody could contribute with exact steps on how to reproduce
> the issue. So far I've gotten some half attempts at that but they
> haven't been actionable for me.
Hi Otto,
I'd point to
Op zo 4 jul. 2021 om 00:42 schreef Colin Watson :
> Sorry for my delay - it took me a while to spot the problem. libc6's
> postinst does arrange to restart services where needed, but in this case
> it doesn't realize that you have the ssh service installed because you
> only have the
Op zo 20 jun. 2021 om 10:38 schreef Olaf van der Spek :
>
> So I think it's not accepting new connections from the start of the
> upgrade run until the end:
> Setting up openssh-sftp-server (1:8.4p1-5) ...
> Setting up console-setup (1.203) ...
> Setting up mime-support (3.66
So I think it's not accepting new connections from the start of the
upgrade run until the end:
Setting up openssh-sftp-server (1:8.4p1-5) ...
Setting up console-setup (1.203) ...
Setting up mime-support (3.66) ...
Setting up openssh-server (1:8.4p1-5) ...
Installing new version of config file
Op za 19 jun. 2021 om 13:13 schreef Colin Watson :
>
> On Sat, Jun 19, 2021 at 12:53:48PM +0200, Olaf van der Spek wrote:
> > During a Debian 10 -> 11 upgrade, the SSH server doesn't appear to be
> > accepting new connections. IMO this is less than optimal, and not sure if
Package: openssh-server
Version: 1:8.4p1-5
Severity: normal
Dear Maintainer,
During a Debian 10 -> 11 upgrade, the SSH server doesn't appear to be accepting
new connections. IMO this is less than optimal, and not sure if this was always
the case.
Would it be possible to keep accepting
> Op za 22 mei 2021 om 23:30 schreef Otto Kekäläinen :
> > Would somebody like to review/test it?
Doesn't seem to be working for me:
# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following
Op za 22 mei 2021 om 23:30 schreef Otto Kekäläinen :
>
> Hello!
>
> On Sun, May 16, 2021 at 4:18 PM Otto Kekäläinen wrote:
> >
> >
> >> > But as said, the bug #988089 can only be fixed by a change in galera-4
> >> > debian/control. Changing the mariadb-10.5 debian/control to
> >> >
Op za 22 mei 2021 om 23:54 schreef Trevor Cordes :
> So now mariadb should allow sane ^W settings now matter how it is
> compiled:
> - with readline: always worked
> - with libedit that comes with maria-db: always worked
> - with your system libedit: now works once you add settings to .editrc
>
Op vr 14 mei 2021 om 09:53 schreef Otto Kekäläinen :
> Investigating (0) galera-4:amd64 < none -> 26.4.7-3 @un uN Ib >
> Broken galera-4:amd64 Conflicts on galera-3:amd64 < 25.3.25-2 ->
> 25.3.31-2+b1 @ii umU Ib >
> Considering galera-3:amd64 0 as a solution to galera-4:amd64 0
> Holding Back
Op za 22 mei 2021 om 04:27 schreef Trevor Cordes :
>
> On Thu, 26 Nov 2020 12:50:26 -0500 The Wanderer
> wrote:
> Which means at one time this was fixed. That's why this used to work
> for us. But something must have regressed in the source, and the fix
MariaDB 10.3 uses libreadline-gplv2
Op za 15 mei 2021 om 18:10 schreef David Kalnischkies :
> So upgrading mariadb will bring you galera-4 which conflicts with
> galera-3. Package removals are not allowed in 'upgrade' so this mariadb
> upgrade will be reverted and you will get it in the next step with
> a full-upgrade – which will
Hi,
Another interesting observation. After upgrading galera-3 from buster
to bullseye first, apt will install 10.5..
# apt full-upgrade
The following packages will be REMOVED:
libpython-stdlib mariadb-client-10.3 mariadb-client-core-10.3
mariadb-server mariadb-server-10.3
Package: apt
Version: 2.2.3
Severity: minor
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Upgrading galera-3 appears to be possible without troubles according to the
second invocation, so shouldn't the first invocation just do that upgrade?
# apt upgrade
The following packages have been
Op vr 14 mei 2021 om 09:53 schreef Otto Kekäläinen :
> As Faustin pointed out, Bullseye has both galera-3 and galera-4. This
> is so the distro is compatible with running whatever version of
> MariaDB you want. Galera-3 will be in Debian (and Ubuntu) repositories
> for as long as somebody is still
Op vr 14 mei 2021 om 08:21 schreef Olaf van der Spek :
> > - why installing galera-4 removes mariadb-server-10.3, see bellow:
galera-4 conflicts with galera-3
mariadb-server-10.3 depends on galera-3
Op wo 12 mei 2021 om 13:03 schreef Faustin Lammler :
> Here are some questions regarding galera (because I believe the problem
> might come from it):
> - why bullseye/sid provide both galera-3 and galera-4?
> - why installing galera-4 removes mariadb-server-10.3, see bellow:
On that topic,
Op zo 9 mei 2021 om 08:40 schreef Otto Kekäläinen :
> Here is a debian-devel thread where I learnt new ways to run apt in
> debug mode to better see why it chooses to upgrade/remove certain
> packages, it might be helpful here too:
> https://lists.debian.org/debian-devel/2021/03/msg00139.html
>
> So in summary everything else goes OK and upgrade passes
It would be kinda nice to end up with mariadb-server-10.5 too... ;)
Op do 6 mei 2021 om 21:43 schreef Otto Kekäläinen :
>
> So in summary everything else goes OK and upgrade passes, but there is
> one 'mariadb-server' metapackage removed
Op do 6 mei 2021 om 04:29 schreef Otto Kekäläinen :
>
> Thanks for reporting!
>
> We constantly test updates from older distros and MariaDB versions in
> our Salsa-CI pipeline, and it does not show the symptoms your system
> had.
>
> Would it be possible for you to provide exact steps on how to
>
Package: mariadb-server
Version: 1:10.5.9-1
Severity: normal
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Installed Debian 10, installed mariadb-server and some other stuff.
Updated sources.list to reference bullseye.
Did apt update
Did apt upgrade
# apt dist-upgrade
Reading package
On Mon, Mar 15, 2021 at 2:33 PM wrote:
> Speaking of environment, AFAIK on modern systems it can be read only by
> sufficiently privileged user, so I don't see how it is less secure than
> a file (which will have to have the same permissions as
> /proc//environ). Could you elaborate how is it
Hi,
> There are no libedit related customizations in the Debian packaging, so I
> suggest you report this
upstream at jira.mariadb.org, where upstream devs might have some input
into this.
Could this be related to:
> Installation of all MariaDB packages on Debian Sid is currently broken, as
Package: apt
Version: 2.1.20
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Hi,
This is a request for advice for dependencies of PHP packages. See the related
issue @ https://github.com/oerdnj/deb.sury.org/issues/1533
The goal is to avoid a situation where apt wants to install a second
Package: php-fpm
Version: 2:7.4+76
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Thanks a lot for packaging 8.0!
Is the plan to ship it in Bullseye?
Greetings,
Olaf
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500,
Package: libboost-dev
Version: 1.74.0.3
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Could Boost 1.75 be packaged?
Greetings,
Olaf
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Op vr 11 dec. 2020 om 17:31 schreef Otto Kekäläinen :
>
> We test the Debian 10 -> Debian 11 upgrade in
> https://salsa.debian.org/mariadb-team/mariadb-10.5/-/jobs/1222976
>
> Source:
> https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/master/debian/salsa-ci.yml#L201-226
>
> Would you
Hi,
10.5 and the upstream versions seem affected too.
# grep mariadb syslog
Dec 13 10:10:28 debian mariadbd[535]: 2020-12-13 10:10:28 0 [Note]
/usr/sbin/mariadbd (mysqld 10.5.8-MariaDB-1:10.5.8+maria~sid) starting
as process 535 ...
Dec 13 10:10:28 debian mariadbd[535]: 2020-12-13 10:10:28 0
Hi Otto,
Note this is on apt upgrade. On apt dist-upgrade it works fine. But
most others packages are fine with just upgrade.
I installed Debian 10, changed buster to testing in sources.list and
ran apt upgrade.
Grtz,
Olaf
Op vr 11 dec. 2020 om 16:28 schreef Otto Kekäläinen :
>
> Hello!
>
>
Op vr 11 dec. 2020 om 16:26 schreef Faustin Lammler :
>
> Hi Olaf!
>
> Yes I can confirm this behavior on sid.
>
> My understanding from
> https://lists.debian.org/debian-release/2020/11/msg00305.html is that
> 10.3 will be fully removed from sid and replaced by 10.5.
>
Hi Faustin,
I understand,
Package: mariadb-server
Version: 1:10.3.27-0+deb10u1
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
I thought / hoped with the correct dependencies (replaces?) apt upgrade could
do this upgrade without holding back. Is some dep missing or can't apt upgrade
do this yet?
Hi,
https://mariadb.com/kb/en/server-system-variables/#open_files_limit
> If set to 0, then MariaDB will calculate a limit based on the following:
> MAX(max_connections*5, max_connections +table_open_cache*2)
max_connections: 151
table_open_cache: 2000
This doesn't add up to 32186.
Package: mariadb-server-10.3
Version: 1:10.3.27-0+deb10u1
Followup-For: Bug #976652
Dear Maintainer,
Fresh Debian 10 install, fresh mariadb-server install:
# zgrep max_open_files syslog*
Dec 11 13:08:46 xyz mysqld[1695]: 2020-12-11 13:08:46 0 [Warning] Could not
increase number of
Package: mariadb-server-10.3
Version: 1:10.3.27-0+deb10u1
Followup-For: Bug #976652
Dear Maintainer,
Debian 10 server @ Linode:
$ zgrep max_open_files syslog*
syslog:Dec 11 12:36:58 ln0 mysqld[699]: 2020-12-11 12:36:58 0 [Warning] Could
not increase number of max_open_files to more than 16384
Package: mariadb-server-10.3
Version: 1:10.3.27-0+deb10u1
Followup-For: Bug #976652
Hi Faustin,
Debian 10 server @ Linode:
$ zgrep max_open_files syslog*
syslog:Dec 11 12:36:58 ln0 mysqld[699]: 2020-12-11 12:36:58 0
[Warning] Could not increase number of max_open_files to more than
16384
Op vr 11 dec. 2020 om 12:22 schreef Faustin Lammler :
>
> > > syslog.6.gz:Dec 5 18:56:49 dev mysqld[694]: 2020-12-05 18:56:49 0
> > > [Warning] Could not increase number of max_open_files to more than 16384
> > > (request: 32183)
> Are you having this message too?
Yes, aren't you? ;)
> >
Package: mariadb-server-10.3
Version: 1:10.3.27-0+deb10u1
Followup-For: Bug #976652
Dear Maintainer,
> syslog.6.gz:Dec 5 18:56:49 dev mysqld[694]: 2020-12-05 18:56:49 0 [Warning]
> Could not increase number of max_open_files to more than 16384 (request:
> 32183)
Where does the 32183 come
Op zo 11 okt. 2020 om 16:30 schreef Giovanni Mascellani :
>
> Hi,
>
> Il 10/10/20 07:28, Olaf van der Spek ha scritto:
> > Hi,
> >
> > What's the plan for Bullseye?
> > It'd be nice if Boost 1.75, expected December 9, could be included.
>
> I agree. On the
Hi,
What's the plan for Bullseye?
It'd be nice if Boost 1.75, expected December 9, could be included.
Greetings,
--
Olaf
Op vr 2 okt. 2020 om 08:28 schreef Otto Kekäläinen :
>
> Did you notice my question?
>
> > Olaf: what commands did you run to compile your example program? Any
> > pkg-config or mariadb_config involved?
No, I used: g++ b933063.cpp -l mysqlclient
join@dev:~$ cat /etc/debian_version
10.6
Op wo 30 sep. 2020 om 17:05 schreef Faustin Lammler :
> I see that you opened a jira issue about this, remember to forward bug
> reports to upstream issue so we can track them better.
>
> What about Sergei last message, do you have any further comments?
Hi Faustin,
I think this issue can be
Op ma 28 sep. 2020 om 19:27 schreef Otto Kekäläinen :
> If you Olaf want to contribute by improving this, I suggest you
> research upstream docs and configs and try to figure out if we
> actually need a full charset row of only utf8mb4 or if current
> situation is sufficient and the 'client' and
On Tue, Jun 16, 2020 at 1:33 PM Toni Mueller wrote:
>
>
> Hi Otto,
>
> On Tue, Jun 16, 2020 at 12:27:53PM +0300, Otto Kekäläinen wrote:
> > Can you provide us enough information about your environment so we
> > could try to reproduce this error?
>
> I'm not sure what you are after. The machine in
Op wo 13 mei 2020 om 11:09 schreef Olaf van der Spek :
>
> Dear maintainers,
>
> How's progress on Boost packaging?
Thanks for the update!
--
Olaf
Op wo 13 mei 2020 om 11:28 schreef Giovanni Mascellani :
> Il 13/05/20 11:09, Olaf van der Spek ha scritto:
> > How's progress on Boost packaging?
>
> Version 1.71 has been in unstable for quite some time now. It is not the
> default yet, but bugs are filed against packages
Dear maintainers,
How's progress on Boost packaging?
Greetings,
--
Olaf
Op do 27 feb. 2020 om 06:54 schreef László Böszörményi :
> Are you going to rename it to abseil-cpp (as Google has abseil-python
> as well, make a disparity between the two)?
Python libraries use a "python3-" prefix while C/C++ libraries use a
"lib" prefix, so I don't think it makes sense to
What about the C++ std version? Abseil / C++14 isn't the same as Abseil / C++17.
This applies to other C++ libraries as well.
Package: mariadb-10.3
Severity: wishlist
Dear Maintainer,
10.4 was released some time ago, what's the plan for 10.4?
Greetings,
Olaf
-- System Information:
Debian Release: 9.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64
Op wo 11 sep. 2019 om 15:27 schreef Faustin Lammler :
>
> Hi Olaf,
> did you finally managed to setup the TLS between client and server?
>
> Let me know if you want me to test something based on
> https://mariadb.com/kb/en/library/securing-connections-for-client-and-server/
> and
>
Package: libmariadb-dev-compat
Version: 1:10.3.15-1
Severity: normal
Dear Maintainer,
I expected character_set_client to be utf8mb4, but it's latin1. Isn't it
supposed to be utf8mb4?
Greetings,
Olaf
/etc/mysql/mariadb.conf.d/50-client.cnf :
[client]
# Default is Latin1, if you need UTF-8 set
Package: npm
Version: 5.8.0+ds6-4
Severity: normal
Hi,
Doesn't happen all the time.. the log is 5000+ lines, would you like me to
include the full log?
> npm install --ignore-scripts --no-package-lock
5412 silly extract stylelint@^10.0.1 extracted to
On Wed, Jun 12, 2019 at 10:44 PM Faustin Lammler wrote:
> do you still have the build log, if not, can you give me your build
> steps and environment so I can try to reproduce the error?
No, however I think it should be reproducible in all environments.
It's too late for Buster isn't it?
It
On Wed, Jun 12, 2019 at 1:12 PM Faustin Lammler wrote:
>
> Hi Olaf,
> do you think that
> https://salsa.debian.org/mariadb-team/mariadb-10.3/merge_requests/12
> resolves the bug or is there anything more you want me to test in order
> to double check?
>
> Thanks!
> Faustin
MR 12 is (kinda)
Op di 21 mei 2019 om 09:03 schreef Helmut Grohne :
> I cannot reproduce the issue with version 1.4.53-4. The manual page
> clearly documents the -tt option. This was fixed upstream in commit
> c4edd356.
You're right, I'm sorry, I looked at an out-of-date version of the man page.
--
Olaf
Package: lighttpd
Version: 1.4.53-4
Severity: wishlist
Dear Maintainer,
-h includes the option but the man page doesn't.
Greetings,
Olaf
# lighttpd -help
lighttpd/1.4.53 (ssl) - a light and fast webserver
usage:
-f filename of the config-file
-m module directory (default:
Package: lighttpd
Version: 1.4.53-4
Severity: normal
Dear Maintainer,
May 19 10:56:32 buster systemd[1]: /lib/systemd/system/lighttpd.service:6:
PIDFile= references path below legacy directory /var/run/, updating
/var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file
Source: lighttpd
Version: 1.4.53-4
Severity: normal
Dear Maintainer,
> (response.c.344) invalid character in URI -> 400 /?a=%7F
%7F looks fine to me..
Greetings,
Olaf
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64
On Sat, Apr 27, 2019 at 5:27 PM Michael Farmbauer
wrote:
> in the latest update the pid and socket files have been moved from
> /var/run/mysqld to /run/mysqld.
>
> The directory /run/mysqld must be created in the init files:
>
> /etc/init.d/mysql
> /var/lib/systemd/system/mariadb*
>
> Those file
Package: lighttpd
Version: 1.4.53-4
Severity: wishlist
Hi,
Lighttpd.conf appears to use a mix of tabs and spaces for indentation. Could
spaces (2 ;)) be used consistently?
Greetings,
Olaf
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable')
Package: lighttpd
Version: 1.4.53-4
Severity: normal
Hi,
server.modules = ( "mod_setenv" ) was removed from lighttpd.conf but no setenv
conf file appears to be available in the conf-available dir.
Greetings,
Olaf
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT
Op wo 17 apr. 2019 om 19:45 schreef Otto Kekäläinen :
>
> > > Try making the overly broad permissions of
> > > /etc/mysql/ssl/server-key.pem -rwxr-xr-x
> > > to something less world-readable.
> >
> > # chmod 700 server-cert.pem
> > # service mysql restart
> >
> > error.log:
> > SSL error: Unable
Op wo 17 apr. 2019 om 16:40 schreef Otto Kekäläinen :
>
> Try making the overly broad permissions of
> /etc/mysql/ssl/server-key.pem -rwxr-xr-x
> to something less world-readable.
# chmod 700 server-cert.pem
# service mysql restart
error.log:
SSL error: Unable to get certificate from
Op wo 17 apr. 2019 om 15:09 schreef Otto Kekäläinen :
>
> What does this print?
>
> find /etc/mysql/ -ls
# find /etc/mysql/ -ls
137133 4 drwxr-xr-x 5 root root 4096 Apr 17
12:14 /etc/mysql/
132729 0 lrwxrwxrwx 1 root root 24 Apr 17
06:56
Package: mariadb-server-10.3
Version: 1:10.3.13-2
Severity: normal
Dear Maintainer,
I followed
https://www.cyberciti.biz/faq/how-to-setup-mariadb-ssl-and-secure-connections-from-clients/
but something went wrong:
2019-04-17 12:24:55 0 [Note] InnoDB: Loading buffer pool(s) from
Op wo 17 apr. 2019 om 10:06 schreef Debian Bug Tracking System
:
> Ernesto confirmed that it was lack of entropy in his case, so I am closing
> the bug.
So, what is the solution?
On Wed, Apr 3, 2019 at 11:12 PM Graham Cobb wrote:
> I'm not sure what the "MariaDB error log" is but I have found the following
> entries in syslog:
It's /var/log/mysql/error.log
Should it be in unstable?
--
Olaf
Package: mariadb-server-10.3
Version: 1:10.3.13-1
Severity: wishlist
Dear Maintainer,
To utf8_unicode_ci or not to utf8_unicode_ci, that's the question. ;)
AFAIK utf8_unicode_ci is recommended, but the current default is
utf8_general_ci.
Ideally this would be fixed upstream but upstream seems
Op di 12 feb. 2019 om 18:13 schreef Faustin Lammler :
>
> Olaf,
> It seems that in this case, the error log should indeed be in the
> datadir ($ldata -> /var/lib/mysql).
>
> I have double checked and this behavior is the same since 10.1 (Debian
> or upstream).
>
> See:
>
Op di 12 feb. 2019 om 11:15 schreef Pirate Praveen :
> npm was not updated for over 3 years and was removed from stretch. See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870460
>
> My motivation for updating it was for gitlab (I'd have been happy with
> even npm 1.4 as I only wanted 'npm
Op di 12 feb. 2019 om 10:25 schreef Pirate Praveen :
> > npm 6 has been available for some time..
> >
>
> If that introduce any rc bugs, there won't be enough time to fix it and
> I don't want to risk it at this point.
Makes sense. 6 has been available since May though, right? Why wasn't
it
Op di 12 feb. 2019 om 10:13 schreef Pirate Praveen :
> On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf van
> der Spek wrote:
> > Could npm 6 be packaged?
>
> We won't be able to get it into buster (soft freeze starting today),
> 2019-02-12 Soft freeze (no new packages, no re-en
Hi,
Could npm 6 be packaged?
Greetings,
--
Olaf
Op ma 11 feb. 2019 om 16:06 schreef Faustin Lammler :
> I have just checked and this seems to be the default directory
> for the error log:
> https://mariadb.com/kb/en/library/overview-of-mariadb-logs/
Debian has log_error = /var/log/mysql/error.log
--
Olaf
Op ma 11 feb. 2019 om 16:02 schreef Faustin Lammler :
> Can I ask you what steps leads to this?
apt upgrade I think, from 10.1 to 10.3, with enable-large-prefix in a conf file.
Note it's not about the failure itself, it's about the text being
wrong about the location of logs.
--
Olaf
Package: mariadb-server-10.3
Version: 1:10.3.12-2
Severity: normal
Dear Maintainer,
Feb 11 10:13:29 ln0 mariadb-server-10.3.postinst[14792]:
Feb 11 10:13:29 ln0 mariadb-server-10.3.postinst[14792]: Installation of system
tables failed! Examine the logs in
Feb 11 10:13:29 ln0
On Mon, Feb 4, 2019 at 12:30 PM Otto Kekäläinen wrote:
> > Great. Do you know what's missing from
> > https://salsa.debian.org/olafvdspek-guest/mariadb-10.3/commit/55d06886f5a81c10a00822078aac3ea0090c1b7f
> > to split mytop?
>
> hmm, no comments comes to my mind.
Just to be clear, the build
u be willing to continue maintaining mytop if the conflict
with mariadb was resolved?
Greetings,
--
Olaf van der Spek
Op vr 1 feb. 2019 om 11:09 schreef Otto Kekäläinen :
>
> I agree that having mytop (or mariadbtop) in a separate package would
> make sense. I am not even fully familiar what the original upstream
> story is and who is maintaining the "most upstream" version of it
> currently.
Great. Do you know
Giovanni Mascellani:
> Of course I will eventually update Boost, but probably not before
> stretch is released. Version 1.67 is going in stretch.
https://www.debian.org/releases/stretch/ ;)
> I have no idea why either meson or mpd think Boost 1.67 is buggy,
On Sat, Dec 29, 2018 at 4:27 PM Otto Kekäläinen wrote:
> > What about moving mytop (matop?) into it's own package? That'd keep
> > issues separated as well.
>
> That would solve the issue filed in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863968
>
> Maintaining MariaDB in Debian
Package: apt
Version: 1.8.0~beta1
Severity: wishlist
Hi,
> 2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Could you just tell me which packages, especially when it's just a few?
If it's 100+, the number makes sense. If it's 10, I'd like to know which.
Greetings,
Olaf
--
Op ma 28 jan. 2019 om 17:57 schreef Marko Mäkelä :
> > Wow that was quick, thanks a lot! Got a link to the changes?
>
> https://github.com/MariaDB/server/commit/36be0a5aef0376c526d68007da1c11ac440f0d8b
>
> The cost is not that big. Unfortunately we do not have any common
That's much more than I
Op ma 28 jan. 2019 om 17:17 schreef Marko Mäkelä :
>
> I filed and fixed the following ticket in the upcoming MariaDB 10.3.13
> release:
> https://jira.mariadb.org/browse/MDEV-18399
> MDEV-18399 Recognize the deprecated parameters innodb_file_format,
> innodb_large_prefix
Wow that was quick,
Op ma 28 jan. 2019 om 13:23 schreef Marko Mäkelä :
> > > The parameters innodb_large_prefix and innodb_file_format were
> > > deprecated in MySQL 5.7 and MariaDB 10.2, and removed in MySQL 8.0 and
> > > MariaDB 10.3.
> >
> > What's the deprecation policy?
> > I think the time between deprecation
Op ma 28 jan. 2019 om 12:33 schreef Marko Mäkelä :
> there would be no issue when upgrading. Would it be thinkable to add
> the loose_ prefix to unknown options in configuration files? Or to
We can't rewrite history.
> ship a new version of the default configuration file, commenting out
> the
Op zo 27 jan. 2019 om 19:22 schreef Otto Kekäläinen :
> Yes, I guess it would be ideal if the upstream binary ignored unknown
> configs instead of stopping on them. Maybe Marko has some comments on
> this.
>
> In packaging we could have some preinstall script that simply added a
> comment to all
Op zo 27 jan. 2019 om 19:15 schreef Otto Kekäläinen :
> Can you reproduce this issue? What are the steps to reproduce?
1. Install stretch
2. apt install mariadb-server
3. Replace stretch by buster in sources.list
4. apt install mariadb-server
Preparing to unpack
Package: mariadb-server-10.3
Version: 1:10.3.12-2
Severity: normal
Hi,
When upgrading from 10.1 to 10.3 and not using the new 10.3 conf files..
2019-01-27 11:13:12 0 [ERROR] /usr/sbin/mysqld: unknown variable
'innodb-large-prefix=on'
2019-01-27 11:13:12 0 [ERROR] Aborting
This is kinda ugly,
1 - 100 of 1469 matches
Mail list logo
