Bug#1019291: yarnpkg: depends on incompatible version of commander

Package: yarnpkg Version: 1.22.19+~cs24.27.18-1 Severity: normal X-Debbugs-Cc: csillag.kris...@gmail.com The current version of node-commander in Debian testing an unstable in 9.4.0. However, this version is not fully compatible with the current version of yarn. For some packages, you will

Bug#983874: gitaly: fails to install: Could not find gem 'rugged (~> 0.28)'

Package: gitaly Followup-For: Bug #983874 I am seeing the same thing. This also makes gitlab unusable. Is there any update about this? A severe error has been reported, and there is no reply for two weeks. Is this package supposed to be actually used by people? -- System Information: Debian

Bug#984680: aegisub: Aegisub often freezes when it encounters non-ASCII characters in some situations

Package: aegisub Version: 3.2.2+dfsg-6+b1 Severity: important Tags: l10n When copying data from the clipboard, if it has any non-ASCII character, I get this on the console: ../src/common/string.cpp(1185): assert "c < 0x80" failed in FromAscii(): Non-ASCII value passed to FromAscii(). ... and

Bug#924617: poppler-utils: I am also waiting for this release

Package: poppler-utils Version: 0.71.0-3 Followup-For: Bug #924617 I am also waiting for this update, because of an different bug. Thanks. -- System Information: Debian Release: 9.8 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing')

Bug#902897: virtualbox: #metoo

Package: virtualbox Version: 5.2.14-dfsg-1 Followup-For: Bug #902897 I hit this but after upgrading the kernel from 4.9 to 4.16. Before that, I think vbox 5.2.14 worked for me OK. -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500,

Bug#889652: gtk-d: Please upgrade

Source: gtk-d Followup-For: Bug #889652 Please the upgrade. A bug in the curently packaged version makes the TILIX terminal emulator unstable. (Which part of my main stack at work. I run all my editors in tilix...) Thanks. -- System Information: Debian Release: 9.3 APT prefers stable APT

Bug#883676: tilix: Please package the fixed version

Package: tilix Version: 1.7.1-2+b1 Followup-For: Bug #883676 Please update the package to the latest upstream (1.7.3), where this bug is already fixed. Until this happens, the package is basically unusable, because the terminal crashes at least once or twice every day, taking all my sessions

Bug#824956: QtQuick1 will be removed from the archive with Qt 5.6

Package: musescore Followup-For: Bug #824956 So as of now, the package is no longer installable in Debian unstable or testing. Meanwhile, there is an (unreleased) version in the package git repo that allegedly fixes this bug. Can we hope for a release? -- System Information: Debian Release:

Bug#815639: geary: Geary won't start

Package: geary Version: 0.11.1-1 Followup-For: Bug #815639 I am still having the same problem. When trying to launch geary: (geary:16053): GLib-GIO-ERROR **: Settings schema 'org.yorba.geary' does not contain a key named 'composer-pane-position' Trace/breakpoint trap . and then it

Bug#824853: tex-common: package installation fails

Package: tex-common Version: 6.05 Severity: grave Justification: renders package unusable When installing the package, I get this: *** Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... fmtutil failed.

Bug#815639: geary: Still present version 0.11.0-2

Package: geary Version: 0.11.0-2 Followup-For: Bug #815639 -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) Locale:

Bug#815731: arandr: Doesn't work with the current version of xrandr

Package: arandr Version: 0.1.8-1 Severity: grave Justification: renders package unusable Lately, xrandr has been updated to v1.5: user@host:~$ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 arandr doesn't like that at all: user@host:~$ arandr Traceback

Bug#815641: geary: please package the new fork of geary

Package: geary Severity: wishlist The package hasn't been updated for almost a year now, because upstream development has ceased. Quoting to the wikipedia page for geary, https://en.wikipedia.org/wiki/Geary_(software) > As Yorba Foundation stopped its activities and the future > of this

Bug#815639: geary: Geary won't start

Package: geary Version: 0.10.0-1 Severity: important When I try to launch geary, I get this: user@host:~$ geary (geary:17024): GLib-GIO-ERROR **: Settings schema 'org.yorba.geary' does not contain a key named 'composer-pane-position' Trace/breakpoint trap and the it exits. The same

Bug#814511: tupi: Please package new upstream version

Package: tupi Version: 0.2+git05-4 Severity: wishlist A new version of Tupi has been released. See here: http://www.maefloresta.com/portal/node/791 It would be great the the package could be updated. -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (990,

Bug#800323: i7z-gui: Segfault on launch

Package: i7z-gui Version: 0.27.2+git2013.10.12-g5023138-2 Severity: important App crashes on launch. This is what I get: i7z DEBUG: i7z version: svn-r93-(27-MAY-2013) i7z DEBUG: Found Intel Processor i7z DEBUG:Stepping 3 i7z DEBUG:Model c i7z DEBUG:Family 6 i7z DEBUG:Processor

Bug#800053: gedit-plugins: package depends on obsolete version of gedit

Package: gedit-plugins Version: 3.16.0-1 Severity: grave Justification: renders package unusable the gedit package in unstable is now at version 3.18.0-1. However gedit-plugin depends on gedit < 3.17, therefore currently it's not possible to install it with the latest version of gedit. I would

Bug#769930: me, too

I'm hit by this, too. Is there any chance we could cherry-pick the upstream fix [1] to Debian? [1]: https://github.com/pypa/pip/pull/2122 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766242: dpkg: consumes all available RAM and crashes, during configure phase

Package: dpkg Version: 1.17.19 Followup-For: Bug #766242 I am seeing this, too. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux

Bug#766322: circular dependencies causes dpkg --configure -a to go into a tight loop

Package: dpkg Version: 1.17.19 Followup-For: Bug #766322 This might be the root cause for #766242. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386

Bug#743719: 0.50 is out !

Package: gocr Version: 0.49 Followup-For: Bug #743719 -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU

Bug#762692: python-pyqt5: Package depends on obsolete qtbase-abi-5-3-1, so it can no longer be installed

Package: python-pyqt5 Severity: grave Justification: renders package unusable The virtual package qtbase-abi-5-3-1 used to be provided by the libqt5core5a package (built from the qtbase-opensource-src source), but starting of 5.3.2+dfsg-1 of said source (released on 16 Sep 2014), the qt-base abi

Bug#758210: libtext-iconv-perl: Depends on obselete perl version

Package: libtext-iconv-perl Version: 1.7-5+b1 Severity: grave Justification: renders package unusable libtext-iconv-perl still depends on perl 5.18, but the perl packages in Debian unstable have now been upgraded to 5.20. That makes this package uninstallable on sid. -- System Information:

Bug#737369: omegat: We are two years behind upstream. (Has this package been abandoned?)

Package: omegat Version: 2.3.0.1+dfsg-3 Severity: wishlist Latest package version is 2.3.0.1+dfsg-3, released on 04 Dec 2011. Latest upstream stable version is 2.6.3 update3, released on 15 January 2014. The difference is more that 2 years. Is there any chance that this package is going to be

Bug#357237: cron job brags about Insecure dependency in exec while running with -T switch

/pg_maintenance ]; then /usr/sbin/pg_maintenance --analyze /dev/null; fi Insecure dependency in exec while running with -T switch at /usr/sbin/pg_maintenance line 49. calling vacuumdb on cluster 7.4/main failed Kristof Csillag -- System Information: Debian Release: 3.1

Bug#357108: post-installatin script outputs suspicious error messages (on amd64)

not a bug, but the other messages indicate that something else is wrong, too. * * * It is of some interest that I have performed the same upgrade on other (non-AMD64) boxen as well, it went without any error messages. Please let me know how can I help you to debug this! Kristof

Bug#329732: The same version keeps upgrading again and again

. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * How can I help you to debug this? Kristof Csillag -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.12 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions