** Also affects: mariadb-5.5 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: mariadb-5.5 (Ubuntu Xenial)
** No longer affects: mariadb-5.5 (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Terminal log says:
* Stopping MariaDB database server mysqld [176G
[170G[[31mfail[39;49m]
invoke-rc.d: initscript mysql, action "stop" failed.
151029 17:23:17 [Note] /usr/sbin/mysqld (mysqld
5.5.44-MariaDB-1ubuntu0.14.04.1) starting as process 10523 ...
* Starting MariaDB database ser
The terminal log shows that mysqld failed to start/stop:
invoke-rc.d: initscript mysql, action "stop" failed
Please provide more information about why the daemon does not start or stop.
What did 'ps uax' show, was there a mysqld process? Is there anything in syslog
from mysql or something i
The title is still misleading. The problem can be fixed by changing the
mysql package code. The part that the mariadb package does is not
anything new, it is exactly the same code as in the mysql packages and
originates from there.
** Summary changed:
- MariaDB writes to /var/lib/mysql after cros
The latest Oracle security notices and CVEs were about issues that have
been fixed in MariaDB 10.0.17 to .22
See latest changelogs and prevous changelogs updated in retrospect in
commit: http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-10.0.git/commit/?h=ubuntu-15.04&id=bbb953f102e98d1a7141a621a1
@TylerHicks: sorry, I didn't realize that syncing from Debian has
stopped in 15.04 and later releases. So 15.10 went unpatched..
Anyway, I've now opened #1512241 for a new security issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I've done extensive testing and I recommend pulling in the latest
package form Debian git master to Ubuntu as it will include fixes for
this and no regressions:
https://lists.alioth.debian.org/pipermail/pkg-mysql-
maint/2015-April/007707.html
--
You received this bug notification because you are
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464895
Title:
CVE-2015-3152: MySQL SSL/TLS downgrade vulnerability
To manage notifications
When the systems is slow again, could you please run in a terminal "top"
and copy-paste the first 15 lines or so here that we can see what it
shows?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924684
Public bug reported:
I've noticed that sometimes when I'm running on battery and then insert
the power cord, the system slows down significantly. When I remove the
power cord, it runs fine again, and when I reattach the power cord the
system slows down again.
I'm running the latest Ubuntu 12.04 w
** Attachment added: "perf-output.txt.gz"
https://bugs.launchpad.net/bugs/998204/+attachment/3141783/+files/perf-output.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998204
Title:
Intel c
Second attachment I referred to in original report.
** Attachment added: "pid-16287-stack.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998204/+attachment/3141805/+files/pid-16287-stack.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This is now fixed in Ubuntu 12.04. Both kernel 3.2 and usb_modeswitch
have support for Huawei E392.
Hoever it does not still work. When the USB dongle is inserted, network
manager recognizes it properly, runs the mobile broadband wizard etc but
when it finally is time to connect, it just keeps con
** Summary changed:
- Huawei E392 is not recognized as Mobile Broadband
+ Huawei E392 is not register to mobile broadband network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948153
Title:
Huawei
Running 12.04 with all updates 2012-04-18 and this error comes up while
just browsing and searching for apps. The error comes up multiple times
and is really annoying.
The software center itself does not crash, but an apport window pops up
saying software center crashed with errors, but it is impo
Interesting. So 'mysqladmin --defaults-file=/etc/mysql/debian.cnf' fails
but 'mysql --defaults-file=/etc/mysql/debian.cnf' works? Or both of
those fail but manually passing username and password as thei are in
/etc/mysql/debian.cnf via 'mysql -u debian-sys-maint -p' works?
--
You received this bu
Sorry for the long delay in replying. Anyway, I don't think the case is
this.
Please run 'sudo netstat -pant' send copy-paste the output here for
analysis. Also you could try 'telnet 127.0.0.1 3306' and confirm that it
works, and then 'telnet x.x.x.x 3306' with the host's external IP to see
if it
This bug should be agains the C connector library, not main mariadb-10.0
pacakge.
Anyway, the issue was fixed by creating a symlink in:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-client-
lgpl.git/commit/debian/libmariadb-dev-
compat.links?id=08ea0bbeab4a6ebb1e62b92c1ca347061be4
** Packa
Hello!
2016-02-25 2:30 GMT+02:00 Matthias Klose :
> failed, down to 5 test failures:
>
> Completed: Failed 5/3689 tests, 99.86% were successful.
>
> Looks like the testsuite is not safe to run in parallel. s390x default
> to -fPIE, so maybe mariadb has issues with option.
Thanks for the informati
The relevant part in your log is:
Job for mysql.service failed because the control process exited with error
code. See "systemctl status mysql.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error al procesar el paquete mariadb-server-10.0 (--
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461737
Title:
package mariadb-server-core-5.5 (not installed) failed to
install/
** Summary changed:
- package mariadb-server-5.5 (not installed) failed to install/upgrade: le
sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
+ package mariadb-server-5.5 (not installed) failed to install/upgrade:
/home/marie-_j/mysql/aria_log_control
*** This bug is a duplicate of bug 1511432 ***
https://bugs.launchpad.net/bugs/1511432
Hello!
Your teminal log shows lines like 'invoke-rc.d: initscript mysql, action
"stop" failed.'
Can you run manually 'sudo service mysql stop' and then see in syslog
and /var/log/mysql/* logs why the serve
*** This bug is a duplicate of bug 1511432 ***
https://bugs.launchpad.net/bugs/1511432
Relevant part from terminal log:
Selecting previously unselected package mariadb-server.
Preparing to unpack .../mariadb-server_5.5.46-1ubuntu0.14.04.2_all.deb ...
Unpacking mariadb-server (5.5.46-1ubuntu0
** Summary changed:
- package mariadb-hostname-5.5 5.5.44-1ubuntu0.14.04.1 failed to
install/upgrade: subprocess installed post-installation script returned error
exit status 1
+ failed to install/upgrade: service stop/start did not work
--
You received this bug notification because you are a
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513862
Title:
package mariadb-client-5.5 5.5.44-1ubuntu0.14.04.1 failed to
insta
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512947
Title:
package mariadb-server-5.5 5.5.44-1ubuntu0.14.04.1 failed to
insta
2015-12-14 18:57 GMT+02:00 Seth Arnold <1524...@bugs.launchpad.net>:
> Just as an aside, the last time I tried to use uscan to download a new
> tarball from upstream MariaDB it performed a lot of non-obvious actions
> besides just downloading the tarball. How should uscan be called so that
> it per
> 2015-12-14 18:57 GMT+02:00 Seth Arnold <1524...@bugs.launchpad.net>:
>> Just as an aside, the last time I tried to use uscan to download a new
>> tarball from upstream MariaDB it performed a lot of non-obvious actions
>> besides just downloading the tarball. How should uscan be called so that
>>
Vivid won't get any updates anymore, but the version in Debian and
current development version of Ubuntu 16.04 now has the latest version.
** Changed in: entr (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
The package is auto-synced. Closing this issue.
** Changed in: mariadb-10.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502009
Title:
Sync 10.0.20-3 f
Thanks for the report. The actual error is this:
intentando sobreescribir `/usr/share/mysql/errmsg-utf8.txt', que está
también en el paquete mysql-common 5.6.27-1ubuntu15.04
Can you please run 'dpkg -L mysql-common' on your system? Where did you
install this mysql-common package from?
According
http://packages.ubuntu.com/search?suite=vivid&arch=any&mode=exactfilename&searchon=contents&keywords=errmsg-utf8.txt
=> /usr/share/mysql/errmsg-utf8.txt mariadb-server-10.0, mysql-server-5.6,
percona-server-server-5.6, percona-xtradb-cluster-server-5.6
Are you using mysql-common that is insta
@Matthias Klose:
I have test builds at
https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all
but those don't include s390x, as I don't have permissions to enable
that arch for the repository. Can you do it?
--
You received this bug notification beca
The version 10.0.23-1 uploaded to Debian and soon synced to Ubuntu has
now a reworked auth_socket configuration, where auth_socket is used by
default only on new installs and on upgrades the existing mysqld root
accounts are kept as-is.
Therefore marking 'fix committed'.
** Changed in: mariadb-10
I am not an expert on how systemd invokes legacy init.d/mysql files.
Please presenting a reproducable case I can repeat and/or analyze what
systemd exactly does and send a patch for http://git.debian.org/?p=pkg-
mysql/mariadb-10.0.git (or mirror at
https://github.com/ottok/mariadb-10.0)
For auth_s
Marking 'fix committed' as Ubuntu will soon sync latest version from
Debian repos.
** Changed in: mariadb-10.0 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
If you are using third party repositories (mariadb.org), please disable
then first before installing the same software from official
Ubuntu/Debian repositories. This problem does not exists when using only
Ubuntu repositories.
--
You received this bug notification because you are a member of Ubun
Related commit:
https://github.com/ottok/mariadb-10.0/commit/cf2f7d436bb264c419960d7dda5072450031a545
Changing
Replaces: mariadb-client-10.0 (<< ${source:Version})
to
Replaces: mariadb-client-10.0
..maybe could solve it, but might introduce regressions for normal
upgrades (package replacing a
Apt-get output ended with:
160107 18:54:20 [Note] /usr/sbin/mysqld (mysqld
10.0.22-MariaDB-0ubuntu0.15.10.1) starting as process 4686 ...
Job for mysql.service failed because the control process exited with error
code. See "systemctl status mysql.service"
and "journalctl -xe" for det
** Patch added: "5.5.46-1ubuntu0.14.04.2..5.5.47-1ubuntu0.14.04.2.diff"
https://bugs.launchpad.net/ubuntu/+source/mariadb-5.5/+bug/1524704/+attachment/4532380/+files/5.5.46-1ubuntu0.14.04.2..5.5.47-1ubuntu0.14.04.2.diff
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
A new upstream microrelease is available.
MRE status for MariaDB was granted by the Ubuntu technical board on May
15th, 2014.
I am now submitting this release as a stable update. All previous
microrelases have been submitted as security updates, so please advice
me on the pr
Tip: use uscan to get the latest upstream release tarball, and use the
attached debdiff to apply on the debian/ folder contents from the
previous released package version in Ubuntu 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the problem:
++ /usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf shutdown
+ shutdown_out='/usr/bin/mysqladmin: connect to server at '\''localhost'\''
failed
error: '\''Access denied for user '\''debian-sys-maint'\''@'\''localhost'\''
(using password: YES)'\'''
What does /etc/my
What if you manually run 'mysql -u debian-sys-maint -p' and use the password in
that file?
Have you changed the mysql.users table so that debian-sys-maint userpassword is
no longer same as in the config file?
What does 'select * from mysql.users where user='debian-sys-maint' show?
Is the user th
Relevant lines:
160217 16:10:09 [Note] /usr/sbin/mysqld (mysqld
10.0.23-MariaDB-0ubuntu0.15.10.1) starting as process 15582 ...
Job for mysql.service failed because the control process exited with error
code. See "systemctl status mysql.service" and "journalctl -xe" for details.
invoke-rc.d: ini
http://www.ubuntu.com/usn/usn-2881-1/ paritally applies for MariaDB too,
and fixes are in this 5.5.47 release that has been waiting for sponsor
to upload for about 1,5 months.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Also this CVE applies: http://www.openwall.com/lists/oss-
security/2016/01/26/3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524704
Title:
New upstream microrelease available: 5.5.47
To manage no
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538315
Title:
USN-2881-1: MySQL vulnerabilities also apply to MariaDB
To manage n
Note that http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-10.0.git/?h=ubuntu-15.04 is maintained with git-
buildpackage and the repository includes the pristine-tar data, so you
can also extract both the upstream and debian packaging from this one
single repository if you want. It would be maybe
Note that http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-10.0.git/?h=ubuntu-15.04 is maintained with git-
buildpackage and the repository includes the pristine-tar data, so you
can also extract both the upstream and debian packaging from this one
single repository if you want. It would be maybe
I noticed on a 12.04 system that something had created in the user home
directory a directory called .xinput.d/ which contained the file
(symbolic link) en_US -> /etc/X11/xinit/xinput.d/ibus. I wonder what
created this? Ibus? Why is it en_US despite the user keyboard locale in
setxkb and other plac
Thanks @Julien!
What did you have installed before you upgraded into mariadb 5.5.41? Did
you migrate from mysql 5.5 or from an older version of mariadb? Was the
previous version installed from the official Ubuntu repositories or
somewhere else?
When you were asked the migration question in the gr
I am not sure if downgrading from MySQL 5.6 or MariaDB 10.0 to a lower
version 5.5 is possible. Try re-installing MySQL 5.6, then dump the
databases into a sql file, purge everything of mysql-5.6 away, install
MariaDB 5.5 cleanly and import the data from the sql dump file.
Or you could perhaps try
MariaDB 10.0 will be available starting from Ubuntu 15.04 Vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424633
Title:
Unable to set password for the MariaDB "root" user in postinstall
scri
Hello!
I just started getting feedback from users who's updates fail - it seems
I screwed up in a bugfix and introduced a new bug. The new bug was fixed
in 10.0 but somehow I missed thinking about backporting it.
What shall we do? Upload directly a 5.5.41-1ubuntu packages?
Here are the debdiffs:
Thanks for reporting this. Somehow this issue slipped in 5.5 though it was a
known thing. Fixes committed at
https://github.com/ottok/mariadb-5.5/compare/ubuntu/5.5.41-0ubuntu0.14.04.1...ubuntu-14.04
https://github.com/ottok/mariadb-5.5/compare/ubuntu/5.5.41-0ubuntu0.14.10.1...ubuntu-14.10
** Cha
*** This bug is a duplicate of bug 1417917 ***
https://bugs.launchpad.net/bugs/1417917
** This bug has been marked a duplicate of bug 1417917
package mariadb-server-5.5 install returned error exit status 1 due bug in
mysql flags removal
--
You received this bug notification because you a
You can fix this manually temporary by running:
sudo touch /var/lib/mysql/debian-5.5.flag
** Summary changed:
- package mariadb-server-5.5 install returned error exit status 1 due to
missing /var/run/mysqld
+ package mariadb-server-5.5 install returned error exit status 1 due bug in
mysql flag
** Changed in: mariadb-5.5 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318163
Title:
package mariadb-server-5.5 install/upgrade/remove return
Updated tags:
https://github.com/ottok/mariadb-5.5/compare/ubuntu/5.5.41-0ubuntu0.14.04.2...ubuntu-14.04
https://github.com/ottok/mariadb-5.5/compare/ubuntu/5.5.41-0ubuntu0.14.10.2...ubuntu-14.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Good.
I just wish that I had integrated piuparts testing into my build scripts
(http://labs.seravo.fi/~otto/mariadb-repo/build.sh), as I already have
chroots for each distro version. But so far setting up piuparts has been
too difficult. If I had piuparts automation somewhere, errors like this
wou
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391676
Title:
USN-2384-1: MySQL vulnerabilities partia
contents&keywords=errmsg.sys
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No replies from reporter. I will not spend time on this bug unless
reported gives more information.
Also, the issue seems invalid, since the file mysql.m4 in Ubuntu is
always in the libclient package and never in mysql-common, as the report
indicates. See
http://packages.ubuntu.com/search?suite=tr
No replies from reported, marking as invalid.
** Changed in: mariadb-5.5 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289925
Title:
package libmariad
)
Status: New => Confirmed
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401252
Title:
package m
I got a proper bug report in upstream Debian and was able to pinpoint
the issue. A fix is possible to produce now.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770177
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
** Changed in: mariadb-
The init file has got some fixes in upstream Debian and I believe they
fix this issue as well.
** Changed in: mariadb-5.5 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 1417917 ***
https://bugs.launchpad.net/bugs/1417917
The error is not that you have your statedir in /srv, but because of a
missing '-f' in the rm command.
Regarding new directory: you would be safest if you create a link like:
ln -s /srv/mysql /var/lib/mys
The relevant part from the logs is:
**
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Setting up libmagic1:i386 (1:5.14-2ubuntu3.3) ...
Setting up file (1:5.14-2ubuntu3.3) ...
Setting up libmariadbclient18:i386 (5.5.41-1ubuntu0.14.04.
*** This bug is a duplicate of bug 1418862 ***
https://bugs.launchpad.net/bugs/1418862
** This bug has been marked a duplicate of bug 1418862
mariadb 5.5.41-1ubuntu0.14.04.1 failed to install/upgrade with output
"mysqld [80G [74G[ OK ]"
--
You received this bug notification because you
Can somebody please tell me how to reproduce this error? Apport logs
alone does not contain enough information to solve a bug.
https://developer.mozilla.org/en-
US/docs/Mozilla/QA/Bug_writing_guidelines#Writing_precise_steps_to_reproduce
--
You received this bug notification because you are a me
This bug is because in mysql the innochecksum binary and man page are
shipped in different packages (client vs server). In MariaDB the
innochecksum binary and manpage are both part of the client package.
We need to either fix MySQL packaging or add mysql-server-5.6 into the
breaks/replaces of mari
2015-02-13 15:13 GMT+02:00 Robie Basak <1421...@bugs.launchpad.net>:
> Can we agree on the right place for innochecksum to live first, and then
> we can make sure that all variants do the same thing? How do you feel
> about moving it to the mariadb server package?
OK, let's do that
--
You receiv
Downgrades from 5.6 to 5.5 are not supported as dpkg told you. Please
read what is on the screen. Closing this as invalid.
** Changed in: mariadb-5.5 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1368124 ***
https://bugs.launchpad.net/bugs/1368124
** This bug has been marked a duplicate of bug 1368124
package mariadb-client-5.5 5.5.38-1 failed to install/upgrade: trying to
overwrite '/usr/share/man/man1/innochecksum.1.gz', which is also in package
dpkg seems to output lines like:
***
Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized va
This is fixed for 5.5 in http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-5.5.git/commit/?id=52ceea23d59849801cd6359cac31804cab8153cb
but it's waiting to get to Ubuntu via the stable updates path.
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
This was fixed in http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-5.5.git/commit/?id=f8035cbf and will enter Ubuntu 14.04
and 14.10 via the stable release update path of 5.5.41.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
For the record: this was fixed in http://anonscm.debian.org/cgit/pkg-
mysql/mariadb-5.5.git/commit/?id=19cda85f117d914626ad77d3027327b7803dfa98
and will flow back to Ubuntu 14.04 and 14.10 wehn 5.5.40 enters via the
stable updates channel.
--
You received this bug notification because you are a m
I have noticed the same problem when using gnome-terminal + mosh = mouse
scroll goes trough command history (like pressing keys up and down)
instead of scrolling the (as would be correct in that situation and what
e.g. xterm does).
--
You received this bug notification because you are a member of
Ok, the patch is now applied in gnome-terminal and I disabled in the
profile the option 'Whether to send keystrokes for alternate screen
scrolling' to fix this annoying behaviour for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I used a USB stick downloaded on a Ubuntu machine and installed using
the default Ubuntu tool (usb-creator-gtk).
There are no I/O errors in the log, but the base-installer / in-target
components fail to run and exit with errors. But if you cannot repeat
this by selecting the LVM options, then I gu
This is a valid bug. The media was error free and the installation was
successful using home folder partitioning (eCryptfs). To me it seems
that something in the partman/dmcrypt selection deployment was faulty.
** Description changed:
- When installing Lubuntu 14.04 I chosein the partitioning scr
I now used the process outlined by Seth above to produce yet another
Ubuntu security backport of 5.5.37. Instead of attaching the 21 MB
debdiff file, I have now attached a diff that only has the debian/*
contents.
Steps for you to apply this patch:
- apt-get source mariadb-server - on Trusty will
Added additional patch that makes the same change as in
https://github.com/ottok/mariadb-5.5/commit/d0ba739a0 to reformat diff
headers as requested.
** Patch added: "dpatch-to-quilt-format.diff"
https://bugs.launchpad.net/ubuntu/+source/mariadb-5.5/+bug/1313187/+attachment/4103841/+files/dpatc
The Debian MySQL team decision is documented at
https://wiki.debian.org/Teams/MySQL/virtual-mysql-server
The mariadb-5.5 package in Trusty and Utopic already follows this
policy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
What is the other package on your system that had
libmariadbclient18:i386? If you now installed MariaDB package
5.5.35-1ubuntu1, what was the older MariaDB package you had?
What steps should I take to reproduce the error?
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => O
** Changed in: ubuntu
Assignee: (unassigned) => Otto Kekäläinen (otto)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/519478
Title:
[needs-packaging] mariadb-server
To manage notificati
Patch for Utopic attached. Here are the steps to deploy this patch:
1. apt-get source mariadb-server - on Utopic will download and unpack
mariadb-5.5_5.5.39-2.debian.tar.xz
2. Download mariadb-5.5.40.tar.gz from
https://downloads.mariadb.org/mariadb/5.5.40/#os_group=source and rename
it to mariad
*** This bug is a duplicate of bug 1368124 ***
https://bugs.launchpad.net/bugs/1368124
** This bug has been marked a duplicate of bug 1368124
package mariadb-client-5.5 5.5.38-1 failed to install/upgrade: trying to
overwrite '/usr/share/man/man1/innochecksum.1.gz', which is also in package
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363438
Title:
package libmariadbclient-dev (not installed) failed to
install/upg
The current init file works just fine. If any new init file is needed,
then a systemd file would be nice to have.
** Changed in: mariadb-5.5 (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Does utopic need a separate patch?
Will vivid automatically sync with Debian to get the MariaDB 10.0 in
there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391676
Title:
USN-2384-1: MySQL vulnera
Yes, the patch for 5.5.39 in Trusty cannot be applied on 5.5.39 in
Utopic, because Utopic 5.5.39 is based on 5.5.39 as it was in Debian
recently, while Trusty is based on a older branch of Debian.
I think I'll import the upstream 5.5.40 on Debian 5.5.39 and prepare
that result to you so you can re
Hello!
This kind of by design how the mysql and mariadb packages work. If there
is an issue with the /var/lib/mysql/*.flag file or data migration, the
dpkg process simply stops and an unwanted upgrade is not performed.
Unfortunately the exit code is not handled very well and Apport thinks
this is
Here is a diff on what the differences are for 5.5.39 in Trusty and
Utopic. Utopic has a never version from Debian which has multiple
packaging bug fixed and no new features added. I think if would be safe
to but also in Trusty. I wonder what the correct process here is?
It would be nice to have s
** Patch added: "mariadb-5.5.39-diff-trusty-utopic.diff"
https://bugs.launchpad.net/ubuntu/+source/mariadb-5.5/+bug/1391676/+attachment/4260729/+files/mariadb-5.5.39-diff-trusty-utopic.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Sorry Seth for being unclear and wasting your time trying to patch and
build something unusable. The file mariadb-5.5.39-diff-trusty-
utopic.diff is a visualization of the differences on 5.5.30 in Trusty
and Utopic and not intended to be used as a patch on anything.
I was just thinking on the long
401 - 500 of 664 matches
Mail list logo
