Package: libqt5core5a
Version: 5.12.5+dfsg-8
Severity: normal
The latest version of libqt5core5a breaks libqtcore4 (<
4:4.8.7+dfsg-20~), which is any libqtcore4 version currently available
in unstable.
Is this intentional?
This makes libqt5core5a uninstallable for me. I have several programs
Package: pstoedit
Version: 3.74-1+b1
Severity: important
Tried pstoedit for the first time today, but I couldn't get it to work.
After a few tests, I noticed it would fail to run even when converting a
dummy pdf (saved with inkscape) to a ps.
The following command:
$ pstoedit lay1.pdf lay1.ps
Package: python-sympy-doc
Version: 1.4-1
Severity: normal
Processing 3 changed doc-base files...
Error in `/usr/share/doc-base/sympy', line 8: all `Format' sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details about
the above error.
-- System Information:
Package: python3-seaborn
Version: 0.9.0-1
Followup-For: Bug #910613
Still true as of 0.9.0-2.
seaborn does *not* need tk.
On Thu, Oct 17 2019, Jason Crain wrote:
> On 2019-10-17, Yuri D'Elia wrote:
>> This has been fixed in libexiv2-27. Would it be possible to rebuild
>> against the newer version? Thanks.
>
> exiv2 0.27 is only in experimental. Are you asking me to upload a new
> version o
Package: libgexiv2-2
Version: 0.10.9-1
Severity: normal
libgexiv2 links against libexiv2-14 which has several bugs handling
temporary files (see #932627). This is indirectly causing gimp's
"export" to leave stray temporary files around
(https://gitlab.gnome.org/GNOME/gimp/issues/3662).
This has
Package: zathura
Version: 0.4.4-1
Followup-For: Bug #940815
I also find the zoom direction to be inverted.
I tried to remap Button4/Button5, but no maps involving Button4/5 have
effect:
map Button4 zoom in
map zoom in
It seems that the mouse wheel behavior cannot be overridden.
On Sun, Sep 22 2019, Klaumi Klingsporn wrote:
> This bug-message I get on the console too, so it may be
> related to the problems but doesn't seem to cause them.
Ok -- wow, I think I've found the issue.
I ran under a different system, and it seems that setting:
export GTK_IM_MODULE=xim
is
On Sun, Sep 22 2019, Klaumi Klingsporn wrote:
> But I remember that I had similar problems with a
> self-compiled earlier 2.3-version of audacity. I had to
> move the configuration-directory (~/.audacity-data) out of
> the way and to choose the classic-theme to make it work.
>
> Maybe this helps?
Package: audacity
Version: 2.3.2-2
Followup-For: Bug #935173
"Very difficult" is an understatement.
audacity 2.3.2 is basically unusable as it is :(
Package: iwd
Version: 0.21-1
Severity: normal
iwd includes /usr/lib/modules-load.d/pkcs8.conf to load pkcs8_key_parser
when available. This however causes an error message during startup in
my case, which I'd like to silence.
I would recommend moving the file to /etc/modules-load.d, possibly
Package: libopencv-imgcodecs4.1
Severity: normal
libopencv-imgcodecs4.1 on experimental probably needs a rebuild.
It currently depends on libopenexr23, which is unavaiable.
The current version on sid is libopenexr24.
Package: python3-pyqtgraph
Version: 0.10.0-4
Severity: important
Version 0.10.0-4 fails to import:
import pyqtgraph
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pyqtgraph/__init__.py", line 210, in
from .graphicsItems.GraphicsLayout
Package: libzip4
Version: 1.5.1-4
Severity: normal
Upstream released 1.5.2 in 2019-03-12 which fixes a bug with encryption.
It would be nice if the package would be updated.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
Package: nodejs-doc
Version: 12.7.0~dfsg-1
Severity: normal
Processing 2 changed doc-base files...
Error in `/usr/share/doc-base/nodejs-api', line 9: all `Format' sections are
invalid.
Note: `install-docs --verbose --check file_name' may give more details about
the above error.
Package: libexiv2-14
Version: 0.25-4
Severity: normal
There's a bug in libexiv2-14 that leaves stray temporary files in the
dirctory where files are saved. This can be reproduced with Gimp 2.10.8
which uses libexiv2 indirectly though libgexiv by doing an export to any
file with Exif data
Package: smbclient
Version: 2:4.9.11+dfsg-1
Followup-For: Bug #931717
Here's the thing: if you replace /usr/lib/cups/backend/smb with a shell
script that simply calls smbspool:
#!/bin/sh
exec /usr/bin/smbspool "$@"
it works. I wanted to debug if DEVICE_URI was set correctly, and it is.
The
Package: gimp
Version: 2.10.8-2
Severity: wishlist
Dear maintainer, GIMP 2.10.12 is available (two minor releases above the
current package).
Thanks
On Fri, Jun 07 2019, Otto Kekäläinen wrote:
> Hello!
>
> Sorry for the long delay in replying.
This one completely slipped under by radar.
Thanks Otto for pinging me.
> i looked at the patch but I am not sure if I understand it fully.
>
> Upstream is very responsive so I suggest you send a pull
Package: vpnc-scripts
Version: 0.1~git20180227-1
Severity: normal
When using openconnect 8.02-1 and network connection is lost, the
reconnection attempt shows this error:
CSTP Dead Peer Detection detected dead peer!
unknown reason 'attempt-reconnect'. Maybe vpnc-script is out of date
Script
Package: wx-common
Version: 3.0.4+dfsg-8
Severity: wishlist
It would be helpful to have a package for the 3.1.* release (currently
3.1.2) of wxWidgets for development purposes, even if that just targets
experimental.
Although still considered "development" and not 100% compatible with
3.0, wx
On Thu, Jan 03 2019, Matteo F. Vescovi wrote:
>> Nothing else is displayed/shown.
>> Admittedly, I never cared enough to report.
>
> It works just fine here. See attached image.
> Please, provide more context to address the issue.
I really have no idea here of any possible cause.
Is iv qt or gtk?
Package: openimageio-tools
Version: 2.0.3~dfsg0-3
Severity: normal
I used "iv" a couple of times in the past, mostly out of curiosity.
I tried again today since I saw upstream' bug #318 should be fixed (bad
gamma handling).
However, in the last several releases (afaik, since at least 6 months)
Package: libopenmpi-dev
Version: 3.1.3-4
Severity: normal
I feel libopenmpi-dev shouldn't depend on a compiler directly.
libopenmpi-dev, specifically, doesn't require gfortran8 to be usable.
After discussion with the maintainer, it seems that the package ships
with version-specific precompiled
On Thu, Nov 29 2018, Gürkan Myczko wrote:
> Does this also happen with 3.5?
> Or the 3.6 available at: http://phd-sid.ethz.ch/debian/colmap/cm36/ ?
I didn't explicitly try your build, but I've rebuilt colmap 3.6 from
source a while ago (since I've also reported the bug upstream) and it
doesn't
On Mon, Nov 26 2018, Bill Allombert wrote:
> On my laptop with 49 days uptime (w/ lot of suspend-to-disk),
> consolation only used 30m and I always use the console.
Random question: could it be that it's due to the fact that I barely use
the console at all?
> What kind of pointing devices do you
Package: consolation
Severity: normal
Version: 0.0.6-2
I've been running consolation for quite a while but I noticed recently
it accumulates a considerable amount of CPU time over the course of a
day.
On a system with a ~2 hours uptime, sorting by cpu time, I have Xorg
(40m), pulseaudio (20m)
Package: ripgrep
Version: 0.9.0-6
Severity: wishlist
Dear maintainer, there's a newer upstream version available: 0.10.0
It would be nice to have an updated package, thanks!
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
Package: libopencv-dev
Version: 3.3.0+dfsg-1~exp0+b4
Severity: normal
Dear maintainer, the newest available upstream is at version 3.4.3.
The current version available on unstable is 3.2.0 which is two years
old. 3.3.0 on experimental is one year old. There are multiple
vulnerabilities published
Package: members
Version: 20080128-5+nmu1+b1
Severity: minor
Running "members" without parameters shows a spourious blank line before
"Usage:".
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
On Mon, Oct 29 2018, Michael Biebl wrote:
>> TBH, I'm not quite sure what your particular problem is.
I wanted to prevent systemd-rfkill to restore the state on boot without
a kernel parameter.
I ended-up masking the systemd-rfkill.service, which essentially does
what I want. We can close this.
Package: python-configparser
Version: 3.5.0b2-1
Severity: normal
I guess python-configparser depends on libjs-sphinxdoc because the
documentation makes use of it. I cound understand a direct dependency if
this would be done in a -doc package, but in this case I feel the
dependency should be
On Tue, Oct 23 2018, Scott Kitterman wrote:
>>I had to install the "spfquery" package to actually debug some domain
>>rules.
>
> There is also an spfquery provided by spf-tools-python.
Thanks for pointing this out, but it doesn't seem to allow tweaking as
much as "spfquery" (from
On Mon, Oct 22 2018, gregor herrmann wrote:
> You can easily sub-class Mail::SPF::Server and the
> Mail::SPF::Result class collection in order to extend or modify
> their behavior. The hypothetical Mail::SPF::BlackMagic package was
> once supposed to make use of this.
>
> also doesn't
Package: wpasupplicant
Version: 2:2.7~git20181004+1dd66fc-1
Followup-For: Bug #907518
wpasupplicant should accept a tls MinVersion parameter to be specified
per-network. Nobody wants to adjust the global setting just to connect
to an outdated system.
As pointed out, I also spotted this while
Package: smbnetfs
Version: 0.6.1-1
Followup-For: Bug #892841
The patch provided by Alexander fixes the issue in my case.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64
Package: python3-seaborn
Version: 0.8.0-1
Severity: normal
NMU version 0.8.0-1.1 add a Depends: python3-tk, however this dependency
shouldn't be there.
I fought hard to remove it in the first place.
If you follow the bug report in #896401 and #896003, the dependency is
triggered when using
Package: screenkey
Severity: minor
python-xlib is not required by screenkey.
You must depend on libx11-6 explicitly.
On Sun, Sep 30 2018, Jonas Smedegaard wrote:
> Quoting wavexx (2018-07-12 11:32:38)
>> This is still true for 2.0.17. uwsgi-plugin-python3 cannot be
>> gracefully shutdown:
>
> I cherry-picked some upstream improvements for python3 module:
> Could you please test if still an issue with uwsgi
Source: slurm-llnl
Severity: wishlist
Dear maintaner, it would be nice to have the new slurm 18 version
available in Debian.
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Package: libscotch-6.0
Version: 6.0.6-1
Severity: normal
Since the latest update, I have the following warning from ldconfig:
Processing triggers for libc-bin (2.27-6) ...
ldconfig: /usr/lib/x86_64-linux-gnu/libesmumps-6.so is not a symbolic link
-- System Information:
Debian Release:
On Thu, Sep 20 2018, Aron Xu wrote:
> It's still possible to happen when upgrading both of the packages,
> pre-depends only avoids the problem on fresh installation. Let's think
> about an alternative way to solve incompatible kernel problem.
Do the dkms triggers actually run concurrently?
I
Package: zfs-dkms
Version: 0.7.9-3
Followup-For: Bug #903112
After reading through config/kernel.m4, I encourage the debian package
of zfs-dkms to add:
--with-spl-timeout=0
to the configure invocation. Concurrent build of spl and dkms is *not*
possible in debian, as spl is listed as a
On Tue, Sep 18 2018, Axel Beckert wrote:
> Reason seems that pcre2 and pcre3 are not exchangable without code
> changes at all as it initially sounded in that LP bug report:
>
> https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/8
>
Package: zsh
Version: 5.6.2-2
Severity: normal
In the last release, the pcre module does not seem to be built anymore.
This causes "setopt rematch_pcre" to fail:
failed to load module `zsh/pcre':
/usr/lib/x86_64-linux-gnu/zsh/5.6.2/zsh/pcre.so: cannot open shared object
file: No such file or
Package: slic3r-prusa
Version: 1.39.2+dfsg-1
Severity: wishlist
Dear mantainer, Slic3r-PE has just released a new upstream version: 1.41.0.
Package: libsane
Version: 1.0.25-4.1
Followup-For: Bug #905913
The upload of 1.0.27-1~experimental6 makes libsane currently
uninstallable on sid.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500,
Package: glslang-dev
Version: 7.8.2853-1
Severity: wishlist
I think it would make sense if glslang-dev would Suggest: glslang-tools
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Package: wnpp
Severity: wishlist
* Package name: openmvs
Version : 0.8
Upstream Author : OpenMVS authors
* URL : https://cdcseacave.github.io/openMVS/
* License : AGPL3+
Programming Lang: C++
Description : open Multi-View Stereo reconstruction library
Package: colmap
Version: 3.4-2
Severity: normal
I'm using an integrated Intel UHD Graphics 620 (Kabylake GT2). I just
tried "colmap gui" -> "automatic reconstruction" and left the default
options (which sets GPU to enabled).
colmap crashes at the following spot:
#0 0x74c98f3b in
Package: apt
Version: 1.6.3
Followup-For: Bug #879786
I second that apt-secure should mention the use of "apt" and, in detail,
"apt-get --allow-releaseinfo-change" as well (pointing to apt-get for
more details on the various finger-graned flags) since the manpage of
apt(1) doesn't include any
On Sun, Jul 22 2018, Michael Biebl wrote:
> Reading the upstream bug report, this seems to be an issue related to
> s2idle and CLOCK_MONOTONIC. I'm thus inclined to close this bug report
Agreed.
> (or reassign to src:linux, depending on what you prefer).
> This really should be raised at the
On Sun, Jul 22 2018, Sean Whitton wrote:
> The argument for including the recommendation is that a changelog is
> not very useful in a binary package, except as a fallback when no
> release notes are available. If you're going to dig into an upstream
> changelog you will do so alongside a
Package: grub-common
Version: 2.02+dfsg1-4
Severity: wishlist
The git version of grub2 and specifically the new grub-mkconfig tool
supports two new directives: GRUB_EARLY_INITRD_LINUX_{STOCK,CUSTOM} (see
commit a698240df0c43278b2d1d7259c8e7a6926c63112)
These allow grub to load extra initrd
Package: python3-dateutil
Version: 2.6.1-1
Severity: normal
Dear maintainer, there's a newer upstream version of dateutil (2.7.3)
which fixes some important issues for radicale 2.x
It would be nice if the package would be updated.
Thanks
-- System Information:
Debian Release: buster/sid
APT
Package: cura
Version: 3.3.1-1
Severity: important
With a fresh installation, cura does not start:
2018-07-10 12:05:02,830 - DEBUG - [MainThread]
PostProcessingPlugin.PostProcessingPlugin.loadScripts [155]: Begin loading of
script: Stretch
QQmlComponent: Component is not ready
2018-07-10
FIY, this is not only related to Intel, and has been fixed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=106715
I tested manually the patch and it fixes the issue for me as well.
Would it be possible to backport the fix into the current package?
After further debugging I figured this seems to be related to the
internal watchdog. I filed a bug report upstream:
https://github.com/systemd/systemd/issues/9538
Package: systemd
Version: 239-5
Severity: important
I noticed journald dumped core several times on this system.
Unfortunately, I didn't notice earlier as these are obviously not logged
on the journal and coredumpctl fails to report them. Nice.
[ 6840.048179] systemd-coredump[7546]:
Package: zfs-dkms
Version: 0.7.9-3
Severity: normal
If the spl module builds fails, the zfs configure scripts does a
pointless wait loop during "configure":
...
configure:14082: checking spl source directory
configure:14140: result: /usr/src/spl-0.7.9
configure:14154: checking spl build
Package: grub-efi-amd64
Version: 2.02+dfsg1-4
Severity: important
I was using grub-pc until recently, where I migrated to grub-efi-amd64.
It's the same hardware (lenovo yoga x1).
My grub configuration is unchanged, and consists of:
GRUB_TIMEOUT=0
GRUB_TIMEOUT_STYLE=hidden
I was used to hold
Package: python3-pygments
Version: 2.2.0+dfsg-1
Severity: wishlist
It would be nice if pygments suggested it's own documentation
(python-pygments-doc) in both the python and python3 flavours.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'),
Package: dput-ng
Version: 1.21
Severity: wishlist
Since an additional documentation package is available, it would be nice
if dput-ng would Suggest: dput-ng-doc
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'),
Package: libdbus-1-dev
Version: 1.12.8-3
Severity: wishlist
It would be nice if libdbus-1-dev suggested it's own documentation.
Curreently, dbus-1-doc suggests libdbus-1-dev, but it should be the
other way around: if you have the development headers installed you
probably want the documentation
Package: vdirsyncer
Version: 0.16.2-4
Severity: wishlist
Since vdirsyncer-doc is available, it would be nice to see it suggested
in the vdirsyncer package.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500,
Package: openjdk-11-jdk
Version: 11~19-1
Severity: important
Unpacking openjdk-11-jre-headless:amd64 (11~19-1) over (11~18-1) ...
dpkg: error processing archive
/var/cache/apt/archives/openjdk-11-jre-headless_11~19-1_amd64.deb (--unpack):
trying to overwrite
Package: mlterm
Version: 3.8.4-1+b1
Severity: wishlist
Dear maintainer, there's a newer version of mlterm available: 3.8.6
(released 2018-06-12), fixing a couple of upstream bugs.
It would be nice to update the package.
Thanks!
-- System Information:
Debian Release: buster/sid
APT prefers
Source: pycollada
Severity: wishlist
Dear maintainer, there's a newer version of pycollada available: v0.6
from November 2017.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture:
Package: xserver-xorg-core
Version: 2:1.20.0-2
Severity: normal
After updating to 2:1.20.0-2 from 2:1.19.99.901-1, the ability to rotate the
display via xrandr's --rotate stopped working.
I'm using an Intel Corporation HD Graphics 520 [8086:1916] (rev 07) from a
Lenovo Yoga 1st Gen, kms driver.
Package: ipset
Version: 6.34-1
Severity: wishlist
Dear maintainer, there's a new upstream source for the userland utilities of
ipset (6.38) which fixes a parsing bug.
It would be nice to update the package.
Thanks!
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT
Package: gmic
Version: 1.7.9+zart-4.1
Severity: wishlist
Dear maintainer, the current upstream version of gmic is at 2.2.2.
The current packaged release is more than one year old.
Package: pypy
Version: 6.0.0+dfsg-1
Followup-For: Bug #825970
pypy 6 is officially a dual 2.7/3.5 release.
It would be very nice to have a pypy3 package. I have to keep a custom build,
since I no longer develop on 2.7 since quite some time now.
-- System Information:
Debian Release: buster/sid
Package: libncurses-dev
Version: 6.1+20180210-2
Severity: minor
The old libncurses5-dev packages suggested the development documentation in
ncurses-doc.
It would be nice do the same in the new package.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900,
Package: zathura
Version: 0.3.9-1
Severity: normal
The latest update of libsynctex1 broke the ABI, resulting in:
zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result
There is already a bug filed against libsynctex1, but I believe a rebuild of
zathura might be an easier
Package: slic3r-prusa
Version: 1.39.1+dfsg-2
Severity: important
FIY, the latest update of wxWindows packages broke the current version of
slic3r and slic3r-prusa.
I'm not sure where to file this (maybe wx should have put some Breaks), but
maybe a simple rebuild could fix the issue.
-- System
Package: openssh-server
Version: 1:7.7p1-1
Severity: normal
DebianBanner does not seem to work correctly anymore. Upon upgrade to 7.7, the
following is shown, sshd rejects the existing configuration file:
/etc/ssh/sshd_config line 111: integer value invalid.
The affected line is:
DebianBanner
Package: python3-pywt
Version: 0.5.1-1.1+b2
Severity: wishlist
Since developer documentation is available, it would be nice if python[3]-pywt
would Suggest: python-pywt-doc
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
On Thu, Mar 15 2018, Jeremy Bicha wrote:
> On Thu, Mar 15, 2018 at 7:21 AM, Yuri D'Elia <wav...@thregr.org> wrote:
>> I had a look at /usr/share/icons/HighContrast/index.theme and the file
>> seems incomplete. The Directories= entry is truncated, and all the
>>
On Wed, Feb 21 2018, Yuri D'Elia wrote:
> On Tue, Feb 20 2018, Jeremy Bicha wrote:
>> On Tue, Feb 20, 2018 at 5:46 AM, Yuri D'Elia <wav...@thregr.org> wrote:
>>> On Mon, Feb 19 2018, Jeremy Bicha wrote:
>>>> How are you setting the HighContrast icon theme?
&
Package: smbnetfs
Version: 0.6.1-1
Severity: important
At least since 0.6.0, any attempt to use open(2) with O_CREAT on a mounted smb
filesystem fails with EIO (Input/output error). The file is created, with has a
size of 0.
This is a call caused by "cp" traced with strace:
openat(AT_FDCWD,
Package: smbnetfs
Version: 0.6.1-1
Severity: minor
I wanted to supress the ServiceUnknown secret service warning I get every time
I start smbnetfs.
On my system I don't have gnome keyring or a "libsecret" compatible service. As
such, I've put
use_libsecret "false"
in the config file, but
On Tue, Feb 20 2018, Jeremy Bicha wrote:
> On Tue, Feb 20, 2018 at 5:46 AM, Yuri D'Elia <wav...@thregr.org> wrote:
>> On Mon, Feb 19 2018, Jeremy Bicha wrote:
>>> How are you setting the HighContrast icon theme?
>>
>> I set this using lxappearance, which b
On Mon, Feb 19 2018, Jeremy Bicha wrote:
> Ok, I looked closer and this doesn't appear to be a Tweaks bug. And I
> can't reproduce the issue at all.
>
> On Mon, Feb 19, 2018 at 4:01 PM, Yuri D'Elia <wav...@thregr.org> wrote:
>> Since the last update, the "HighCo
Package: gnome-accessibility-themes
Version: 3.27.90.1-1
Severity: normal
Since the last update, the "HighContrast" icon theme only works for GTK2
programs.
GTK3 programs seem stuck with the default (tango?) theme.
My GTK3 config hasn't changed (.config/gtk-3.0/settings.ini has
Package: libglfw3-dev
Version: 3.2.1-1
Severity: wishlist
Since documentation is available, it would be nice if libglfw3-dev itself would
Suggest: libglfw3-doc.
Thanks!
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
Package: nasm
Version: 2.13.02-0.1
Severity: minor
During doc-base setup:
Setting up doc-base (0.10.8) ...
Unregistering 234 doc-base files, re-registering 236 doc-base files...
Error in `/usr/share/doc-base/nasm-manual', line 14: all `Format' sections are
invalid.
-- System Information:
Package: cura
Version: 3.0.3-2
Severity: wishlist
Cura 3.1 is the latest available stable release.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/4
Package: systemd-cron
Version: 1.5.12-2
Severity: normal
Found this in the wild: zfsutils-linux package has the following cron.d entry:
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] &&
/usr/lib/zfs-linux/scrub
On Sat, Dec 30 2017, Bill Allombert wrote:
> I have uploaded consolation_0.0.6~pre1 with the --no-daemon option.
> Could you write a patch to fix debian/init.d ?
> I could do it but then I am not in a good position to test the result.
Sorry for the delay. Attaching:
consolation.path: diff for
On Fri, Dec 29 2017, Bill Allombert wrote:
>> It would be nice to have a non-forking mode though.
>
> So you would like a command line option that prevent forking ?
> What should be the name ? --no-daemon ?
I've seen and like "-f" for "foreground" personally, but --no-daemon is
just as good: your
Package: consolation
Version: 0.0.5-1
Followup-For: Bug #883087
I noticed my system took too long to shutdown and tracked it down to
consolation (which is awesome btw!).
As mentioned by Jakub, consolation forks without writing a pid file, so
start-stop-daemon just timeouts.
I wrote a simple
Package: libevdev-dev
Version: 1.5.7+dfsg-1
Severity: wishlist
Since developer documentation is available, it would be nice if libevdev-dev
would Suggest: libevdev-doc
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
FYI, this also has implications for systemd.
See the following bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878965
and the related upstream:
https://github.com/systemd/systemd/issues/7054
Package: ess
Version: 17.11-1
Followup-For: Bug #882042
Looks like ess doesn't play well with emacsen-common.
ess-lisp-directory is initialized to /usr/share/emacs25/site-lisp/ess/
in ess-utils.el:46. The ess-etc-directory-list expects to find the etc
directory somewhere relative to this path,
Package: libunwind-dev
Version: 1.2.1-2
Severity: important
This is from libunwind-common.h:
#define UNW_VERSION_MAJOR 1
#define UNW_VERSION_MINOR 2.1
#define UNW_VERSION_EXTRA
Notice how .1 was not spilled to UNW_VERSION_EXTRA.
This breaks the UNW_VERSION_CODE macro, which expects
Package: apitrace
Version: 7.1+git20170623.d38a69d6+repack-2
Severity: normal
Dear maintainer, apitrace-tracers has an explicit version restriction on
libc6<2.25, which now cannot be satisfied on unstable.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy:
Package: libjs-jed
Severity: normal
libjs-jed shouldn't depend on javascript-common directly, unless a web
server is actually required (which isn't).
The dependency should be changed to a recommends.
Thanks.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy:
Package: python3-sqlalchemy
Version: 1.1.11+ds1-1
Severity: normal
python3-sqlalchemy should Recommend: python3-sqlalchemy-ext, as
python-sqlalchemy is already doing.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental')
Package: python3-pandas
Version: 0.20.3-10
Severity: normal
Loading of various Excel documents depends on python3-openpyxl and
python3-xlrd.
Both were already Recommended in python-pandas, but the same is
not true for python3-pandas.
-- System Information:
Debian Release: buster/sid
APT
Package: dracut
Version: 045+132-1
Severity: normal
I briefly tried dracut on a minimal system with cryptosetup+luks
root filesystem. Everything works as expected.
I discovered a minor issue with the password prompt.
During boot, the prompt to unlock the root fs has a timeout. If
the timeout
101 - 200 of 765 matches
Mail list logo
