See https://github.com/brianmario/mysql2/issues/950#issuecomment-376375844
Sorry wrong ticket
See https://github.com/brianmario/mysql2/issues/950#issuecomment-376375844
Source: redmine
Severity: important
Dear Maintainer,
The aforementioned patch has:
-gem "mysql2", "~> 0.4.6", :platforms => [:mri, :mingw, :x64_mingw]
+gem "mysql2", "~> 0.4", :platforms => [:mri, :mingw, :x64_mingw]
However, this should be "~> 0.4.0" because redmine 3.x is only
I can see in the Gemfile.lock that rbpdf is still 1.19.0 where it should be
1.19.5
As a temporary workaround you should be able to run the following command
to refresh your Gemfile.lock:
sudo /var/lib/dpkg/info/redmine.postinst "triggered"
Upon discussion with redmine maintainers in #debian-ruby,
And including the Gemfile.lock would help too
On Wed, Sep 26, 2018 at 11:33 AM Hashem Nasarat wrote:
> Thanks for filling a bug report! I'll try to reproduce this later today.
> Have you done any customization to your redmine install, or are you merely
> using the plain redmine
Thanks for filling a bug report! I'll try to reproduce this later today.
Have you done any customization to your redmine install, or are you merely
using the plain redmine debian package?
In addition, can you provide the Gemfile corresponding to this redmine
install?
On Wed, Sep 26, 2018 at 8:57
I packaged a new version which fixes this bug and also addressed some other
small issues
kanashiro on irc mentioned that they'd help me with sponsorship, but just
for documentation, here's the package out for review.
https://mentors.debian.net/package/ruby-rbpdf
I made some good progress with packaging a new version of ruby-rbpdf:
https://salsa.debian.org/hnasarat-guest/ruby-rbpdf/network/master
Now to find a sponsor?
Source: libinput
Version: 1.11.2-1
Severity: normal
Dear Maintainer,
Would you consider packaging libinput 1.11.902?
I believe this is one of the RC releases before 1.12 is released.
Why:
On my own system, I didn't want to wait so I followed the instructions here
and built an updated packa
I came across this bug today and spent a little time trying to figure
out what's wrong.
I booted with Solution1 on https://wiki.debian.org/systemd#Debugging to
enable logging.
On the plymouth screen if I press a key
[OK] Started Bluetooth service.
[OK] Reached target Bluetooth.
[16] systemd[
Package: tk8.6
Version: 8.6.1-5
Severity: important
Dear Maintainer,
I noticed recently that the background branch color in gitk became hard to
read when using gitk in Debian. This color is hard to read for anyone, but
could be a serious hinderance for those with vision trouble.
gitk sets the br
Check ~/.cache/gdm/session.log for errors. I believe some part of GNOME
now tries to make calls to something in systemd. I had this problem, and
switching to systemd enabled everything to work fine.
On 09/11/2013 06:20 PM, Carlo Marchiori wrote:
> Package: gnome-shell
> Version: 3.8.4-1
> Severity
This is a known limitation of the input handling in gnome-shell < 3.8.
It's fixed in 3.8 and onward.
On 09/03/2013 09:38 AM, Andreas Glaeser wrote:
> Package: gnome-shell
> Version: 3.4.2-7+deb7u1
> Severity: wishlist
>
> Dear Maintainer,
> *** Please consider answering these questions, where appr
I had a similar problem (using a thinkpad x220). Upgrading to the 3.8
kernel (linux-image-3.8-...) fixed this issue for me.
On 04/08/2013 04:38 PM, Kees de Jong wrote:
> Please supply the following logs.
>
> ~/.xsession-errors
> /var/log/syslog
> /var/log/Xorg.0.log
>
> My best guess is that this
This may be related to one or more upstream bug reports:
https://bugzilla.gnome.org/show_bug.cgi?id=689378
https://bugzilla.gnome.org/show_bug.cgi?id=642652
or perhaps
https://bugzilla.gnome.org/show_bug.cgi?id=649477
https://bugzilla.gnome.org/show_bug.cgi?id=685513
Also, does gnome-shell in expe
16 matches
Mail list logo
