Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

Package: chromium Version: 61.0.3163.100-2 Followup-For: Bug #871542 I was also hit by this bug with Chromium 61. At 2560x1440 the UI is just overblown. Using an 1.5 scale factor fixes the size to something acceptable, but only when I'm using the laptop's screen. When booting with an external

Bug#876841: Depends on python3-mock

Package: python3-tables Version: 3.4.2-1 Severity: normal Hi, in the newer release of the package, python3-tables is added as a build dependency, however the package itself depends on python3-mock. After checking though, it seems that python3-mock is only used in tests/test_utils.py (the test

Bug#729956: Python 3 Statsmodels & Pandas

On Sat, Sep 16 2017, Diane Trout wrote: > I was assuming it's because there's a cyclic dependency between pandas > and statsmodels (needed for pandas unit tests), and statsmodels was > also broken by the fpectl problem. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875805 > > My solution

Bug#729956: Python 3 Statsmodels & Pandas

On Sat, Sep 16 2017, Diane Trout wrote: > python3-pandas: Pandas is not installable > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723 I would have expected the rebuild of python packages affected by the fpectl extension with a transition, but it doesn't seem to be the case?

Bug#873499: GnuPG package split and interlocking dependencies [was: Re: Bug#873499: Should depend on "gnupg | gnupg2 | gpg"]

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: >> I'd recommend gpg-agent, and suggest gnupg instead. > > why? upstream recommends shipping all the binaries in a single package > as the standard deployment. I'm trying to meet them halfway here. <...> > I'm willing to keep the split in debian to

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: > On Mon 2017-09-11 14:28:29 +0200, Yuri D'Elia wrote: >> I'd rather go for this route, and recommend gpg-agent from gpg, > > gpg already Recommends: gnupg, which itself Depends: gpg-agent. I'd recommend gpg-agent, and sugges

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: > gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory > gpg: can't connect to the agent: No such file or directory > gpg: agent_genkey failed: No agent running > Key generation failed: No agent running > 2 dkg@sid:~$ Since I

Bug#875303: Troublesome systemd-networkd-wait-online.service

Package: systemd Version: 234-3 Severity: normal The systemd-networkd-wait-online.service is causing tlp.service (among others) to break in my setup. The issue is caused by the rule Also=systemd-networkd-wait-online.service present in systemd-network.service. Several services include include

Bug#875298: New upstream version available

Source: mlmmj Severity: wishlist A new upstream version of mlmmj is available: 1.3.0 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)

Bug#729956: git-dpm (was Re: Bug#729956: Forwarded upstream)

On Wed, Sep 06 2017, Andreas Tille wrote: >> But just to confirm, I see that statsmodels is just using >> git-buildpackage? > > Yes. Ok, that's reassuring. I'll have a look at the packaging, since I'm already on alioth. But since DPMT is CC-ed (I normally follow via gmane), I take the occasion

Bug#729956: Forwarded upstream

On Wed, Sep 06 2017, Andreas Tille wrote: > Great. What about sending a patch with your changes to the bug > report? I've added a branch debian-python3 to I always built from source, not with the debian packaging. >https://anonscm.debian.org/git/debian-science/packages/statsmodels.git > >

Bug#729956: Forwarded upstream

On Wed, Sep 06 2017, Andreas Tille wrote: > I opened an issue on Github > > https://github.com/statsmodels/statsmodels/issues/3909 > > requesting Python3 support. I concur with what was said in the issue. This is only an issue with debian's packaging. I've been using a custom build of

Bug#741613: Switch to RFP

Control: retitle -1 RFP: glslang -- OpenGL / OpenGL ES Shading Language Reference Compiler Switch to RFP, as it's unlikely I can work on the packaging in the near future.

Bug#874258: Requires rebuild due to pyfpe ABI change

Package: python3-scipy Version: 0.18.1-2+b2 Severity: important python3 stopped building the fpectl module, requiring a rebuild of the affected modules. scipy.linalg is affected: import scipy import scipy.linalg Traceback (most recent call last): File "", line 1, in File

Bug#874253: Needs rebuild due to PyFPE

Package: python3-pandas-lib Version: 0.20.3-1 Severity: important python stopped building the fpectl extension, which results in this: ImportError: C extension: /usr/lib/python3/dist-packages/pandas/_libs/tslib.cpython-35m-x86_64-linux-gnu.so: undefined symbol: PyFPE_jbuf not built. If you

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Tue, Aug 29 2017, Colin Watson wrote: > This package contains /usr/bin/gpg itself, and is useful on its own > only for public key operations (encryption, signature verification, > listing OpenPGP certificates, etc). If you want full capabilities > (including secret key operations, network

Bug#873498: Should depend on "gnupg | gnupg2 | gpg"

On Tue, Aug 29 2017, Sean Whitton wrote: >> binary itself. To avoid extra dependencies, it would be nice to update >> the dependency to "gnupg | gnupg2 | gpg". > > Well, gnupg2 is a transitional package, so no point in having that. > > Would 'gpg' be enough? The package description says it can't

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

Package: pass Version: 1.7.1-3 Severity: normal The gnupg2 package in unstable has been renamed again and split into several components. The "gnupg" package is now the full suite, while "gpg" contains the binary itself. To avoid extra dependencies, it would be nice to update the dependency to

Bug#873498: Should depend on "gnupg | gnupg2 | gpg"

Package: git-remote-gcrypt Version: 1.0.1-1 Severity: normal The gnupg2 package in unstable has been renamed again and split into several components. The "gnupg" package is now the full suite, while "gpg" contains the binary itself. To avoid extra dependencies, it would be nice to update the

Bug#872983: Do not depend on openbox-menu

Package: openbox Version: 3.6.1-4.1 Severity: wishlist I'm using openbox without a desktop menu entirely. Openbox 3.6.1-5 switched from Suggests: openbox-menu to Depends: openbox-menu. Can we push it back to a Suggests or a Recommends for those that don't need it? -- System Information: Debian

Bug#871774: Broken dependencies

Package: bogofilter-bdb Severity: normal Version: 1.2.4+dfsg1-9+b1 Probably as a result of a rebuild, bogofilter-bdb 1.2.4+dfsg1-9+b1 depends on both: --- bogofilter-common (= 1.2.4+dfsg1-9) --- bogofilter-common (= 1.2.4+dfsg1-9+b1) (UNAVAILABLE) -- System Information: Debian Release:

Bug#868433: Needs rebuild for gdal-abi-2.2

Package: libopencv-imgcodecs3.2 Version: 3.2.0+dfsg-1~exp1 Severity: normal On unstable, gdal has been upgraded to 2.2, which makes imgcodecs3.2 uninstallable.

Bug#868429: 1.12.2 uninstallable

Package: gstreamer1.0-vaapi Version: 1.12.2-1 Severity: serious The dependencies for libgstreamer-plugins-bad1.0-0 listed in the current 1.12.2 version of the package make it uninstallable. *-vaapi depends on both: libgstreamer-plugins-bad1.0-0 (< 1.12.2) libgstreamer-plugins-bad1.0-0 (>=

Bug#866598: 1.10.0+dfsg-5+b2 uninstallable: conflicts with debconf

Package: python3-cairo Version: 1.10.0+dfsg-5+b1 Severity: serious Preparing to unpack .../python3-cairo_1.10.0+dfsg-5+b2_amd64.deb ... Unpacking python3-cairo (1.10.0+dfsg-5+b2) over (1.10.0+dfsg-5+b1) ... dpkg: error processing archive

Bug#864905: New upstream 4.0.6 available

Package: kicad Version: 4.0.5+dfsg1-4 Severity: wishlist Upstream released a new stable version of kicad (4.0.6). Notably, it chances some paths that should fix #860093 as well.

Bug#864601: Missing 'HuC' firmware on Intel Kabylake/Skylake/Broxton

Package: firmware-misc-nonfree Version: 20161130-3 Severity: normal The HuC firmware is currently missing for the i915 module: W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for

Bug#864197: Allow to match packages by their source name in apt_preferences

On Mon, Jun 05 2017, Julian Andres Klode wrote: >> In apt_preferences, would it possible to pin packages by their source name? > > That is planned. We already have a almost 15 year old wishlist > bug for that, so I'm merging this one into that. Missed that. Mmmh, I guess I shouldn't sweat on

Bug#864197: Allow to match packages by their source name in apt_preferences

Package: apt Version: 1.4.6 Severity: wishlist In apt_preferences, would it possible to pin packages by their source name? I'm a developer and I'm using pinning for several development packages. I currently list the binary packages by hand, by really I'd like to match packages by their source

Bug#823110: cups-filters: Versioned dependency on imagemagick makes using graphicsmagick harder

On Wed, May 31 2017, Samuel Thibault wrote: > Hello, > > Versioned Provides are now supported, so graphicsmagick can just Provide > the appropriate version of imagemagick. I'll ask, but maybe they don't already because graphicsmagick-imagemagick-compat does not guarantee 100% feature parity. I'm

Bug#823110: cups-filters: Versioned dependency on imagemagick makes using graphicsmagick harder

Package: cups-filters Version: 1.11.6-3 Followup-For: Bug #823110 I second this, and push it further. cups-filters depends on imagemagik for "convert" alone, and it's used only in: /var/lib/cups/filter/imagetobrf /var/lib/cups/filter/texttobrf Both usage of convert are absolutely trivial,

Bug#860763: imagemagick: /etc/imagemagick-6/policy.xml useless limits settings

Package: imagemagick-6-common Version: 8:6.9.7.4+dfsg-9 Followup-For: Bug #860763 I agree with the original reporter here. The policy includes arbitrary limits which cannot easily be modified by invoking the commands. If we want to ensure the "resource" limits do not get exceeded in order to

Bug#860188: v40 interpreter in 2.7

On Thu, May 18 2017, Laurent Bigonville wrote: > 2.7.1 is currently in experimental and AFAIKS the v40 interpreter is enabled > by > default in that version, see: > https://www.freetype.org/freetype2/docs/subpixel-hinting.html > > Where you thinking about something else? After rechecking with

Bug#862671: Pressure wrap-around in qt4 programs

Package: xserver-xorg-input-wacom Version: 0.34.0-1 Severity: normal I'm using a wacom bamboo tablet, and noticed that starting with xserver-xorg-input-wacom 0.34.0-1 the pressure reported by the stylus in Qt4 programs wraps around at 0.5 (going back to -0.5 instead), thus never reaching 1. This

Bug#861813: Should Suggest: khal-doc

Package: khal Version: 0.9.5-2 Severity: wishlist Since a khal-doc package is available, it would be nice if khal suggested it. Thanks. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel:

Bug#860188: v40 interpreter in 2.7

Package: libfreetype6 Version: 2.7.1-0 Severity: wishlist Freetype 2.7 introduces a new v40 truetype interpreter mode, which is not currently enabled. I've been using a custom-built freetype with the v40 interpreter enabled for the past 6 months, and I wouldn't go back. v40 has some

Bug#859006: fontconfig alias issue

Package: xfonts-terminus Version: 4.40-2 Severity: normal I'm not sure this is related to #843982 so I'm filing it as a new report. With the upgrade to fontconfig 2.12, using 'Terminus' as a font family stopped working. xlsfonts lists the various fonts and aliases, but fc-list shows 'xos4

Bug#470417: fail2ban: please support ipv6 addresses (and ipv6tables)

Package: fail2ban Followup-For: Bug #470417 Any progress on packaging the experimental version? On a dual-stack server, the current fail2ban is useless.

Bug#858637: Acknowledgement (Downgrade dependency on python3-tk)

And after re-reading #858576, I'd say the dependency should be dropped entirely. The import error is in matplotlib itself. Seaborn shouldn't depend indirectly on matplotlib backends. python3-matplotlib recommends python3-tk already, as it should.

Bug#858637: Downgrade dependency on python3-tk

Package: python3-seaborn Version: 0.7.1-3 Severity: normal seaborn 0.7.1-3 now depends on tk, but it's not directly required for seaborn. It's only used when the tkagg backend is selected in matplotlib. For other backends, tk is not required. Please downgrade the dependency to a Recommends.

Bug#858617: Fails to load certain JPEG files

Package: inkscape Version: 0.92.1-1 Severity: normal inkscape fails to load (or import) the following 1.4Mb image file: https://gemex.eurac.edu/dl/?t=ada658ec062a8ff67c9360852058c3f1 This is a (seemingly) standard JPEG image produced by OpenCamera on Android. Interestingly, it fails to load

Bug#858292: New upstream 1.2 available

Package: goaccess Severity: wishlist Upstream is now at 1.2, but the current version in debian is only at 0.9.4.

Bug#858106: Should Suggest: python-cvxopt-doc

Package: python3-cvxopt Version: 1.1.8+dfsg-1 Severity: wishlist It would be nice if both python-cvxopt and python3-cvxopt suggested their own documentation since it is available in a separate package. Thanks! -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900,

Bug#857139: Should Suggest: libwayland-doc

Package: libwayland-dev Version: 1.12.0-1 Severity: wishlist It would be nice if libwayland-dev suggested it's reference documentation. Thanks! -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64)

Bug#856966: Uninstallable on sid

Package: libcore-ocaml-dev Severity: normal I was trying to install libcore-ocaml-dev, but multiple dependencies are currently unavailable, making the package uninstallable: https://packages.debian.org/sid/libcore-ocaml-dev -- System Information: Debian Release: 9.0 APT prefers unstable APT

Bug#856958: Should Suggest: tar-doc

Package: tar Version: 1.29b-1.1 Severity: wishlist It would be nice if tar suggested it's own full documentation package, even if it's not fully DFSG compatible.

Bug#856956: Should Suggest: flex-doc

Package: flex Version: 2.6.1-1.3 Severity: wishlist It would be nice if flex suggested it's own documentation. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

On Sat, Feb 11 2017, Michael Biebl wrote: >> I cannot explain why given the exact same partition/volume scheme by >> lvm/cryptsetup, in one case I can shutdown cleanly, and in the other it >> breaks. > > While I can reproduce the error messages on shutdown, it does *not* > cause a dirty file

Bug#855607: Error during installation

Package: mmm-mode Version: 0.5.4-1 Severity: normal This is shown during install: Setting up mmm-mode (0.5.4-1) ... ERROR: mmm-mode is broken - called emacs-package-install as a new-style add-on, but has no compat file. Install mmm-mode for emacs install/mmm-mode: Handling install of emacsen

Bug#804552: API reference mostly empty

On Mon, 09 Nov 2015 15:35:57 +0100 Yuri D'Elia <wav...@thregr.org> wrote: The "API reference" (/usr/share/doc/python-pandas-doc/html/api.html) in the current package is mostly empty. For example, "General functions" contains no links at all except for section titles.

Bug#571234: Missing dependency on xbitmaps

This seems to be due that vlines2 is a bitmap in the package xbitmaps, which I didn't have installed at the time of the bug report (the only hard dependency that forced install is xterm on my current system). Maybe x11-utils should Recommend: xbitmaps, the same way x11-apps does.

Bug#824506: Issues with GTK

Please close this, I'm reporting it upstream.

Bug#848913: libeigen3-doc

Sorry, never got this message since I wasn't cc-ed. Got around it now as I'm re-checking my reports. Yes, I'm sorry about this. It was an issue with my mirror. The package is clearly fine. You can close, Thanks!

Bug#826581: Issues on broadwell

Starting with 4.8 kernels, booting with i915.enable_rc6=0 fixes this issue for me, including several other random crashes that were occurring without apparent reason. I guess it would be proper to move this report against one of the current kernel images, since the problem still persists on

Bug#836458: [pkg-gnupg-maint] Bug#836458: Cannot edit key stored with an empty passphrase

On Sat, Sep 03 2016, Werner Koch wrote: > I just tried this: > > gpg --edit-key some_key_with_no_passphrase > > At the prompt, I set a new passphrase using the "passwd" command. A bit > annoying is that you need to repeat it for the subkey. Next I used > "passwd" again and entered an empty

Bug#855313: Invalid option -l

Source: aide Severity: normal It seems that the short form of --limit: "-l", does not work: # aide.wrapper -l test /usr/bin/aide: invalid option -- 'l' Unknown option given. Exiting although it's clearly documented in the manual, man page and in the --help. -- System Information: Debian

Bug#855029: doc-base error while installing python-matplotlib-doc

Package: python-matplotlib-doc Version: 2.0.0+dfsg1-1 Severity: normal Noticed this error during installation: Processing 4 changed doc-base files... Error in `/usr/share/doc-base/python-matplotlib-doc', line 13: all `Format' sections are invalid. Note: `install-docs --verbose --check

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

On Sat, Feb 11 2017, Michael Biebl wrote: >> reached? If I cannot get a clean journal out, there's nothing much I can >> debug. > > You could try to attach a serial device to your VM and log the output to > that device [1]. This will get us a more complete log. > Attach the complete file. But for

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

On Sat, Feb 11 2017, Michael Biebl wrote: > While I can reproduce the error messages on shutdown, it does *not* > cause a dirty file system (in particular /var) here. > I do have persistent journal enabled on the test VM, but the filing > killing/unmount spree in systemd-shutdown properly unmounts

Bug#854814: Fails to start systemd-resolved

Package: systemd Version: 232-17 Severity: normal With the update to 232-17, systemd-resolved fails to start with the following error: Feb 10 17:46:31 test systemd[1]: Starting Network Name Resolution... -- Subject: Unit systemd-resolved.service has begun start-up -- Defined-By: systemd --

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

On Fri, Feb 10 2017, Michael Biebl wrote: > Looks similar to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like > https://github.com/systemd/systemd/issues/1620 Uhm, it does. Aside from the fact that it's not at all harmless as mentioned, since the root fs is not unmounted.

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

Package: systemd Version: 232-15 Severity: normal I've setup a VM using kvm with a virtio block device, running debian unstable and an encrypted root filesystem (automatically setup during installation as lvm+encrypted volume). Somehow, systemd tries to stop the lvm/crypto block devices way too

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Mon, Feb 06 2017, Daniel Kahn Gillmor wrote: >> gpg --batch -qe -r keyid "$@" > > sure, but what's the "$@" ? Is it guaranteed to be a simple file name? > or could it be more gpg options? I left that out in a copy-paste, but it's empty. There are no extra args to given to gpg that I didn't

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Mon, Feb 06 2017, Michael Biebl wrote: >> These are all single processes just waiting. >> So for gpg purposes, the agent is working as intended. >> However, I'm perplexed as of why I have so many running. > > I guess all of this could be solved if gnupg-agent was using > exit-on-idle (with some

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: > Can you give me the exact invocation? If the agent is being > queried/auto-launched when it doesn't need to be, that'd be something > worth asking GnuPG upstream to take a look at. Nothing fancy. The command line is: gpg --batch -qe -r keyid

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: > What are you doing with gpg? if whatever you're doing needs the secret > keyring, the agent will be launched. if it doesn't need the secret > keyring, the agent will not be launched. In one instance, I have a couple of gpg --batch processes that

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Fri, Feb 03 2017, Michael Biebl wrote: >> When gpg is used via command line, the agent is started automatically >> and then it's left sitting there. But for a system without seats, the >> agent doesn't make sense. It shouldn't be running. > > That doesn't make sense. Even if you stop the

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Fri, Feb 03 2017, Michael Biebl wrote: >> I'm quite happy about the listening sockets by default on desktop, but >> on servers it's exactly the opposite. And masking is currently > > What's the problem with having them started on servers? Those are UNIX > sockets, not something which is

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

On Fri, Feb 03 2017, Michael Biebl wrote: >> I wouldn't change anything for stretch and keep the status quo. > > And as already said, once we have support for user services in i-s-h, > this can be revisited post stretch. i-s-h? So the reasoning here is that dh-systemd doesn't support presetting

Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

Package: gnupg-agent Version: 2.1.18-3 Severity: normal According to upstream, it's incorrect to ship user/sockets.target.wants/* files directly, as those cannot be disabled by the administrator. Quote: ... should instead ship this with an [install] section and enable it at package install

Bug#850982: closed by Daniel Kahn Gillmor <d...@fifthhorseman.net> (Bug#850982: fixed in gnupg2 2.1.17-6)

On Wed, Jan 18 2017, Debian Bug Tracking System wrote: > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Daniel Kahn Gillmor >

Bug#851593: Should Recommend: slop

Package: maim Severity: normal Since slop is debian as well, maim should definitely recommend (or *at least* suggest) it, as maim's -s depend on slop to be installed.

Bug#850982: [pkg-gnupg-maint] Bug#850982: Add instructions to disable gpg-agent user service in README.Debian

On Thu, Jan 12 2017, Yuri D'Elia wrote: > I'm also not entirely sure on the best way to disable the socket. > Should you mask it? Just to clarify, you can mask them per-user, but placing a symlink to /dev/null in /etc/systemd/user/ has no effect. Ideas?

Bug#851138: logrotate dummy_* fails

On Thu, Jan 12 2017, Marc Haber wrote: > On Thu, Jan 12, 2017 at 12:25:14PM +0100, Yuri D'Elia wrote: >> The fix for #833982 is not enough. The current logrotate scripts for atop >> cause >> logrotate to exit with non-zero status, and run-parts to fail as a result. >

Bug#851138: logrotate dummy_* fails

Package: atop Version: 2.2.6-2 Severity: normal The fix for #833982 is not enough. The current logrotate scripts for atop cause logrotate to exit with non-zero status, and run-parts to fail as a result. Adding nomail is not enough: Jan 12 11:52:50 eab16011nb run-parts[661]:

Bug#850982: [pkg-gnupg-maint] Bug#850982: Add instructions to disable gpg-agent user service in README.Debian

On Wed, Jan 11 2017, Daniel Kahn Gillmor wrote: >> I do not want to auto-start these services for the root user. I also want to >> disable auto-start completely in servers I'm logging into. I think both are >> pretty common scenarios and deserve special mention, as systemctl --user >> disable

Bug#850982: Add instructions to disable gpg-agent user service in README.Debian

Package: gnupg-agent Version: 2.1.17-4 Severity: normal The gpg-agent and dirmngr services are now auto-enabled for user sessions, which is actually a nice improvement. Can we tweak the instructions present in the README.Debian to include the commands required to disable this for a single user,

Bug#459427: changelog vs. NEWS handling

On Mon, Jan 02 2017, Russ Allbery wrote: > No matter what we do here, we're going to make a bunch of packages buggy, > because the archive is very divided on current best practice. :( Buggy in the sense that existing packages wouldn't comply with the new rules? I don't see this as "buggyness",

Bug#459427: changelog vs. NEWS handling

On Sun, Jan 01 2017, Andreas Henriksson wrote: > My personal opinion is that a changelog is something where every change > is guaranteed to be logged. (And that guarantee is basically just saying > that if it's ever noticed that a change was not logged, that's indeed a > bug.) > A NEWS file is

Bug#848692: Acknowledgement (reportbug fails with apostrophe in full name)

Should have written "single quote" to make it more obvious.

Bug#848582: atopacctd cannot start

On Mon, Dec 19 2016, Marc Haber wrote: > This is related to #833997. You're caught by one of the two kernel > issues mentioned in this bug. The fact that atopacctd 2.2.4 starts > correctly is that it doesn't check for this kernel issue. It starts, > but never receives process accounting messages.

Bug#848582: atopacctd cannot start

Just some extra info to report that 2.2.4 (the version I upgraded from) starts correctly.

Bug#848582: atopacctd cannot start

Package: atop Version: 2.2.5-1~exp1 Severity: normal I just upgraded to 2.2.5 to test the new logging, but atopacctd.service does not start: Dec 18 16:45:47 eab16011nb atopacctd[4018]: Version: 2.2.5 - 2016/12/15 10:12:34 Dec 18 16:45:47 eab16011nb

Bug#848494: Inconsistent status of active tasks

Package: taskwarrior Version: 2.5.1+dfsg-2 Severity: whishlist I'd expect that active tasks could be filtered using status:active, but only the +ACTIVE pseudo-tag is available. I see this as an inconsistency. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy:

Bug#817922: [Pkg-roundcube-maintainers] Bug#817922: Bug#817922: PEAR issues

On Fri, Dec 16 2016, Sandro Knauß wrote: > now transistion of Php7 is through and we are in freeze. Is it still an issue? Not anymore, thanks!

Bug#848161: muttrc(5) doesn't mention "bright" color prefix

Package: mutt Version: 1.7.1-5 Severity: minor I was reading muttrc(5) and the mutt manual at the same time for the "color" keyword. muttrc(5) lists conveniently all the color aliases, but fails to mention that colors can be prefixed with "bright" to make the face bold. It would be nice if this

Bug#844067: opencv: Uninstallable package libopencv-dev after binNMU

Package: libopencv-dev Version: 3.1.0+dfsg-1~exp2 Followup-For: Bug #844067 Any news on this?

Bug#845209: Switch to clang-3.9

Package: clang-defaults Severity: wishlist Clang 3.9 is the latest release of clang, which is already available on unstable. Is there any reason to keep depending on 3.8 as the default? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'),

Bug#834402: aptitude: search loses column format when redirected or piped

Package: aptitude Version: 0.8.3-1+b2 Followup-For: Bug #834402 I also consider this a regression. For instance, see this example: aptitude -s search -F '%c%M %p' '~i' > status.txt The width doesn't matter, I'm logging the output for archival. I actually *want* infinite width. But %M is now

Bug#843897: Should allow pyqt5

Package: python-pyqtgraph Version: 0.9.10-5 Severity: normal pyqtgraph 0.10 can now also work with pyqt5. I'd suggest adjusting the dependencies to allow this. python-pyqtgraph should depend on python-qt4 | python-pyqt5 | python-pyside python3-pyqtgraph should depend on python3-pyqt4 |

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

On Mon, Nov 07 2016, Michael Biebl wrote: >> Kernel: Linux 3.4.112-kvm-i386-20161024 > > I suspect your kernel is too old and/or doesn't have all necessary > features enabled. Have you checked As written, this is 3.4. > See /usr/share/doc/systemd/README.gz > It explicitly mentions 3.12 as

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

Package: systemd Version: 232-1 Severity: serious Upgrading systemd from 231-10 to either 232-1 or 232-2 breaks systemd-resolved and dovecot on my system, with the following error when the units are started: Nov 7 15:26:03 e systemd[18963]: systemd-resolved.service: Failed at step NAMESPACE

Bug#843536: Setting a package on hold resets the auto flag

Package: aptitude Version: 0.8.3-1+b1 Severity: normal Setting a package in "iA" state on hold clears the automatic flag, but there's no reason it should. The auto state should be preserved when putting a package on hold, as forbid currently does. -- Package-specific info: Terminal:

Bug#843257: No GTK style

Package: qt5-style-plugins Severity: important Dear maintainer, Qt 5.7 doesn't support the GTK style anymore. The qt5-gtk-themeplatform is next to useless (what I care about is consistency between widgets!). It looks like the qt5ct package (ITP #822246) could still make use of use the gtk2

Bug#836734: Considerable I/O performance regression on Lenovo Carbon X1 with 4.7.0

On Wed, Nov 02 2016, Salvatore Bonaccorso wrote: >> I'm unsure at what exactly look for, as it could also be related to many >> subsystems (I'm using an ext4 fs in an encrypted volume). > > I was seeing similar issues with a X1 laptop after the update of 4.6.x > to 4.7.x, and seem dissapeared with

Bug#807125: Should Suggest: ipython-doc

Package: ipython3 Version: 5.1.0-2 Followup-For: Bug #807125 With the update to 5.1, the package now builds python-ipython-doc, but it's still not suggested by ipython[3] or python[3]-ipython. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900,

Bug#832010: Please enable LZ4 compression

On Sat, Oct 22 2016, Michael Biebl wrote: > Is it possible to enable lz4 for coredumps only? Not according to upstream. > Felipe's argument about apt already pulling in libz4 makes me less > concerned, fwiw, as we wouldn't introduce yet another new dependency in > the "base"

Bug#838979: Suggests non-existent hevea-doc

Package: hevea Version: 2.29-1 Severity: normal Looks like that since 2.29-1 the hevea-doc package is no longer built. It would be nice if the package would be built again, or in the worst case, drop the suggests. -- System Information: Debian Release: stretch/sid APT prefers unstable APT

Bug#838279: Depends on libopencv-video-dev

Package: libopencv-shape3.0 Severity: normal Version: 3.0.0+dfsg-1~exp7 I wanted to give opencv3 a try from the experimental packaging. I noticed libopencv-shape3.0 depends on both libopencv-video-dev and libopencv-video3.0 at the same time. I suppose libopencv-video-dev is undeeded. -- System

Bug#836739: Issues with the latest gtk3 update

Package: darktable Version: 2.0.5-2+b1 Severity: normal The new gtk3 update broke darktable's internal skin. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64

Bug#836734: Considerable I/O performance regression on Lenovo Carbon X1 with 4.7.0

Package: src:linux Version: 4.7.2-1 Severity: normal I'm using a Carbon X1 (3rd gen). Compared to the latest 4.6 kernel, this image has a significant performance regression in all I/O related operations. Just as a ballpark, 4.6.0-1 can boot in generally less than 3 seconds after the grub

<    1   2   3   4   5   6   7   8   >