Bug#939074: RM: python-raven -- ROM; NPOASR; RC-buggy

Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl1q7HsSHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5FlAP/34wIc24kphH0em5pjgmOyaoR9KCFfJK

Bug#932763: haproxy: `haproxy.cfg` contains an outdated URL and cipher choices

❦ 22 juillet 2019 15:19 -05, April King : > I would also strongly suggest bundling the RFC 7919 2048-bit > Diffie-Hellman parameters file in the haproxy debian package as well. For this part, I remember that in the past, it was better to have custom DH parameters than widely used one. I don't

Bug#932763: haproxy: `haproxy.cfg` contains an outdated URL and cipher choices

❦ 22 juillet 2019 15:19 -05, April King : > The existing `haproxy.cfg`, from `debian/haproxy.cfg` contains this URL: > https://mozilla.github.io/server-side-tls/ssl-config-generator/?server=haproxy > > > However, it

Bug#570998: lintian: Please check that commands in /{usr/,}sbin do not use section 1 manpages

❦ 19 juillet 2019 13:02 +00, Dmitry Bogatov : > Unless it is false-positive, it constitutes violation of FHS, so it > warrants "warning" severity. As stated earlier, there is a large gap on language between manual section definitions and definition for sbin/bin: hier(7) says: /sbin

Bug#570998: lintian: Please check that commands in /{usr/,}sbin do not use section 1 manpages

❦ 18 juillet 2019 10:50 +01, "Adam D. Barratt" : >> Are you sure? This is not about the alternative init but about manual >> page section. It doesn't seem Dmitry is involved at all. > > Apparently people can be interested in more than one thing. :-p > > See the MR submitter on >

Bug#570998: lintian: Please check that commands in /{usr/,}sbin do not use section 1 manpages

❦ 17 juillet 2019 23:04 -03, "Chris Lamb" : >> - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348864 >> - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253011 >> >> There is no consensus. > > Dmitry (added to CC), as you were the one championing this change, can > you please comment

Bug#570998: lintian: Please check that commands in /{usr/,}sbin do not use section 1 manpages

Package: lintian Followup-For: Bug #570998 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 *sigh* See: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348864 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253011 There is no consensus. hier(7) says: /sbin Like /bin, this

Bug#883393: jool Debian packaging

❦ 13 juillet 2019 12:29 -05, Alberto Leiva : >> - d/changelog: do you have any contact with Bjoern Buerger, the >> original author of the ITP? > > We talked up to 2018-05-10. > > I sent him another email on 2018-05-28, and then another one two days > ago. Both of them have gone unanswered as

Bug#931960: RFS: jool/4.0.2-1 [ITP] -- IP/ICMP Translators

❦ 12 juillet 2019 18:48 -05, Alberto Leiva Popper : > I am looking for a sponsor for my package "jool" I have posted a review in #883393 (before seeing this RFS). -- Debian package sponsoring guidelines: https://vincent.bernat.ch/en/debian-package-sponsoring signature.asc Description: PGP

Bug#883393: jool Debian packaging

Hey! - d/changelog: do you have any contact with Bjoern Buerger, the original author of the ITP? - d/control: the list in Maintainers will receive bug reports and stuff related to the lifecycle of the package. Is that your intent? - d/control: remove comments. - d/control: Vcs-*

Bug#883393: ITP: jool -- Open Source SIIT and NAT64 Translator for Linux

Package: wnpp Followup-For: Bug #883393 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Any progress on this? Do you need help packaging? -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl0mDQYSHGJlcm5hdEBk

Bug#931617: Scripts are not executed with /bin/sh when they should

Package: keepalived Version: 1:2.0.10-1 Severity: important Tags: patch upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! With a configuration like this: vrrp_script check_vpn1 { script "/usr/sbin/birdc -v show proto vpn1 | grep -q '^1002-.* up .*'" interval 1 } The script is

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

❦ 15 juin 2019 20:39 +02, Nicola Di Lieto : >>Look at https://mentors.debian.net/sponsors. Notably, there is a "Let's >>Encrypt" team (team+letsencrypt@tracker.debian). > > Hello Vincent, > > many thanks for your reply. I already emailed > team+letsencr...@tracker.debian.org at the end of

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

❦ 15 juin 2019 07:14 +02, Nicola Di Lieto : > I have tentatively packaged this already in the git repository, using > the DEP-14 branch layout at http://dep.debian.net/deps/dep14 - look at > the debian/master branch. Not sure what to do now to get it into > debian. Look at

Bug#929830: syslog shows netlink error

❦ 13 juin 2019 09:03 +02, michael-dev : >> Is there anything special on your setup? Lots of interface running or >> interfaces cycling (VM)? > > This has happened both in virtual and non-virtual machines, some of > them only have one interface, others have two or three. > I also do not see

Bug#929830: syslog shows netlink error

❦ 11 juin 2019 11:36 +02, michael-dev : > the problem occured on multiple machines. Directly after restart, > lldpd memory usage seems fine, but eventually memory usage starts > exploding again. > The started happening within weeks after upgrading to stretch. All > machines were restartet after

Bug#926032: [chromium] Buggy / Solarized videos

Package: chromium Version: 75.0.3770.80-1 Followup-For: Bug #926032 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I am also hit by this bug and it's still present in 75. It seems to be known upstream: https://bugs.freedesktop.org/show_bug.cgi?id=109548

Bug#929830: syslog shows netlink error

❦ 1 juin 2019 13:14 +02, michael-dev : > while memory usage was increasing, syslog showed (few) lldpd[1264]: > unable to receive netlink answer: No buffer space available messages. I think this may be more a consequence than a cause. The code around this message seems to correctly handle

Bug#925203: unblock: bpftrace/0.9-1

❦ 9 mai 2019 10:28 +02, Paul Gevers : > I fear you're not going to like my mail, sorry. No problem! >> Please unblock package bpftrace >> >> Upstream told me 0.9 is the first release where the API (to write >> bpftrace code snippets) has been stabilized, so scripts and docs will >> stop

Bug#928461: unblock: haproxy/1.8.20-1 (pre-approval)

hecks: segfault during tcpcheck_main +- BUG/MAJOR: http_fetch: Get the channel depending on the keyword used +- BUG/MAJOR: listener: Make sure the listener exist before using it. +- BUG/MAJOR: spoe: Fix initialization of thread-dependent fields +- BUG/MAJOR: stats: Fix how huge POST data are

Bug#926798: RFP: elpa-magit-forge -- Work with Git forges from the comfort of Magit

❦ 10 avril 2019 10:50 -04, Antoine Beaupre : > I keep on coming back to this package. I think it's installable > through MELPA but because of the poor connexion here, I'm having > trouble testing it. From my understanding, it doesn't work with the current version of magit. See:

Bug#570623: reprepro: please add multiple version management

Package: reprepro Version: 5.3.0-1 Followup-For: Bug #570623 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! What is the status of this feature? The merge request is not available anymore and the GitHub repository of the fork is not up-to-date with 5.3.0. - -- System Information: Debian

Bug#858837: Bug#888743: Debian vs Linux namespaces, NMU lsb-base

❦ 24 mars 2019 14:40 +01, Didier 'OdyX' Raboud : >> Wouldn't it break chrooted processes? But mostly, as the whole pattern >> is broken, it seems to be a low-effort solution. > > Vincent: what scenario did you have in mind? For the first part, any daemon chrooting (like HAProxy, lldpd). For the

Bug#858837: Debian vs Linux namespaces, NMU lsb-base

❦ 24 mars 2019 09:42 +01, Geert Stappers : > What would be the harm to the Buster release > if lsb-base got NMU > with > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=888743;filename=init-functions.diff;msg=37 > ? Wouldn't it break chrooted processes? But mostly, as the whole

Bug#925203: unblock: bpftrace/0.9-1

-22 15:10:27.0 +0100 +++ bpftrace-0.9/debian/changelog 2019-03-16 19:07:56.0 +0100 @@ -1,3 +1,10 @@ +bpftrace (0.9-1) unstable; urgency=medium + + * New upstream release. + * d/patches: drop all patches, applied upstream. + + -- Vincent Bernat Sat, 16 Mar 2019 19:0

Bug#923782: Relax dependency on faraday to allow updating ruby-faraday

Package: ruby-puppet-forge Followup-For: Bug #923782 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! With the provided patch, I am able to use librarian-puppet without any issue. Unless someone protests, I'll do a NMU next week to fix this bug. - -- System Information: Debian Release:

Bug#921981: haproxy: Workers segmentation fault if unique-id-header is used

❦ 10 février 2019 20:53 +00, Tim Duesterhus : > please see this issue I already filed upstream: > > https://github.com/haproxy/haproxy/issues/40 > > I'm including a short summary below: > > If I run haproxy with the attached reproducer configuration and > direct concurrent requests to it then

Bug#922085: curlftpfs: provide patch to fix file creation on pure-ftp

❦ 11 février 2019 21:35 +01, Stéphane Chauveau : > My provider is using Pure-Ftp (I do not know which version) and on > that server the chmod command does not work on non-existing files. > Unfortunately, curlftpfs is using chmod to create new files which > causes a systematic 'No such file of

Bug#921484: Origin of background.js and manifest.json not documented?

Package: webext-browserpass Version: 2.0.22-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! I am curious to know why there is a debian/background.js as well as a debian/manifest.json? They are not documented in debian/copyright. The manifest seems to have a bogus

Bug#921188: closed by Ritesh Raj Sarraf (Bug#921188: fixed in bpfcc 0.8.0-2)

❦ 4 février 2019 11:48 +0530, Ritesh Raj Sarraf : >> The .so should go in the -dev package, while the .so.0 and .so.0.8.0 >> should go to the non -dev package. Currently, the opposite is true. > > Hi Vincent, > > So many things I must be missing something very obvious. Does this look > good to

Bug#921188: closed by Ritesh Raj Sarraf (Bug#921188: fixed in bpfcc 0.8.0-2)

❦ 3 février 2019 10:09 +00, "Debian Bug Tracking System" : > This is an automatic notification regarding your Bug report > which was filed against the libbpfcc-dev package: > > #921188: Include pkgconfig file > > It has been closed by Ritesh Raj Sarraf . The .so should go in the -dev package,

Bug#918120: ITP: bpftrace -- high-level tracing language for Linux eBPF

❦ 25 janvier 2019 22:54 +01, Michael Prokop : >> * Package name: bpftrace >> Version : git >> Upstream Author : IO Visor Project >> * URL : https://github.com/iovisor/bpftrace >> * License : Apache 2 >> Programming Lang: C++ >> Description : high-level

Bug#921188: Include pkgconfig file

Package: libbpfcc-dev Version: 0.8.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Could you please include the .pc file which is provided upstream? It would help to build projects depending on libbcc (like bpftrace). Also, the -dev is missing the .so which is shipped

Bug#918120: ITP: bpftrace -- high-level tracing language for Linux eBPF

❦ 25 janvier 2019 22:54 +01, Michael Prokop : >> * Package name: bpftrace >> Version : git >> Upstream Author : IO Visor Project >> * URL : https://github.com/iovisor/bpftrace >> * License : Apache 2 >> Programming Lang: C++ >> Description : high-level

Bug#918120: ITP: bpftrace -- high-level tracing language for Linux eBPF

Package: wnpp Severity: wishlist Owner: Vincent Bernat -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: bpftrace Version : git Upstream Author : IO Visor Project * URL : https://github.com/iovisor/bpftrace * License : Apache 2 Programming

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

❦ 29 décembre 2018 18:33 +00, Dmitry Bogatov : > Probably not. Violations of FHS is violation of policy, and to get > authorization to policy violation is long road, starting with discussion > on debian-devel@. > > But, can't we just configure Nix to store it under /var/nix? This would break

Bug#915636: python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0

❦ 13 décembre 2018 11:54 +0100, Vincent Bernat : >> find attached my NMU .debian.tar using the updated 16.1.0 version. >> As I found no documentation what you +ds version removed from the >> upstream TAR ball, I'm using the pristine upstream TAR ball. >> >> Upstre

Bug#915636: python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0

❦ 5 décembre 2018 15:12 +0100, Philipp Hahn : > find attached my NMU .debian.tar using the updated 16.1.0 version. > As I found no documentation what you +ds version removed from the > upstream TAR ball, I'm using the pristine upstream TAR ball. > > Upstream moved most files to the src/

Bug#915043: nikto: missing build on all

❦ 29 novembre 2018 16:51 -0200, Eriberto Mota : > I've prepared an NMU for nikto (versioned as 1:2.1.5-3.1) and > uploaded it to DELAYED/10. Please feel free to tell me if I > should delay it longer. Thanks. You can upload it right now if you want. -- What I tell you three times is true.

Bug#877792: visualvm: Can't start (possible due to java 9)

❦ 5 octobre 2017 16:30 -0300, "Nelson A. de Oliveira" : > I am unsure if it's happening because I am using openjdk 9, but I can't > start visualvm: > > = > $ visualvm > Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on > WARNING: Unknown module: jdk.jvmstat specified to

Bug#911867: RFS: frr/6.0.1-1 [ITP]

❦ 27 octobre 2018 14:54 +0200, David Lamparter : > The lib is an integral part of a FRRouting version; the daemons and the > .so must match up. As noted above on the symbols file, the .so version > is not currently used since the ABI is not stable. The "0" does not > convey any useful

Bug#861500: graphite-api: broken symlinks: /usr/share/doc/graphite-api/html/_static/*/* -> ../../../../../sphinx_rtd_theme/static/*/*

❦ 15 octobre 2018 16:14 +0200, Andreas Beckmann : > Followup-For: Bug #861500 > > As Dmitry Shachnev mentioned in #911069: > >> These symlinks are generated by dh_sphinxdoc, so better to depend on >> ${sphinxdoc:Depends}. Thanks. I am uploading a fixed version. -- "You have been in

Bug#910269: pysnmp4 source is inconsistent

❦ 4 octobre 2018 12:08 +0200, Michal Arbet : > Yes , diff looks big , just for sure , ls -la INSTALLED_PATH of pysnmp4 > > root@sid-builder-pbuilder:/build/python-pysnmp4# ls -la > /usr/lib/python3/dist-packages/pysnmp/hlapi/ > total 32 > drwxr-xr-x 5 root root 4096 Oct 4 09:56 . > drwxr-xr-x

Bug#910269: pysnmp4 source is inconsistent

❦ 4 octobre 2018 11:39 +0200, Michal Arbet : > I found the issue with pysnmp4 packages in debian. > Package's source is totally different with source hosted on github > repository. > > What happened with your last upload to salsa repository ? >

Bug#902025: emacs25: Emacs 26.1 released

❦ 30 juin 2018 17:18 -0500, Rob Browning : >> Emacs 26.1 has been released, and should be packaged for Debian. > > Indeed. > > But we have a few things we need to finish up first. > > We're in the process of unversioning the emacs packages[1], and the > first set (emacs, emacs-non-dfsg, and

Bug#906978: Bug is in pysnmp4

❦ 10 septembre 2018 14:32 +0200, Thomas Goirand : > Upstream updated the issue and write it's an problem with pysnmp4: > > https://github.com/etingof/pysnmp/issues/193 > > The issue is fixed in the master branch of pysnmp, but there's no > release for it yet. > > Should we reasign the bug? I'll

Bug#908413: haproxy: HAProxy can't load more than one multicert bundle.

❦ 9 septembre 2018 18:32 +0200, "Francisco Blas Izquierdo Riera (klondike)" : > I have wrotten, compiled and tested the attached patch. I would be > very thankful if it could be included on your next backports build. > I have also submitted the patch to upstream for consideration. Let's see

Bug#907807: After upgrading to OpenSSL 1.1.1, many sites are unreachable

❦ 5 septembre 2018 09:30 -0400, Antoine Beaupré : > So I've forwarded the bug upstream to see if we can get a hint there. I > originally thought this was a 1.1 transition problem, but as it turns > out, linkchecker loads those sites fine in buster, which still has > 1.1.0. It's 1.1.1 which

Bug#907886: sshpubkeys: Please package the newest upstream release

❦ 3 septembre 2018 17:07 +0200, Nicolas Braud-Santoni : > Hi Vincent ! > > Upstream released a new (major) version, that is stricter on which SSH keys > it will accept, in February. I think this will eventually cause issues if > we keep shipping sshpubkeys 2.x when people might expect 3.x > >

Bug#907807: After upgrading to OpenSSL 1.1.1, many sites are unreachable

❦ 3 septembre 2018 09:49 -0400, Antoine Beaupré : >> Since the upgrade to OpenSSL 1.1.1pre9 in sid, linkchecker is unable >> to check many sites including: >> >> - ones without SNI Don't remember for this one. >> - ones with DH parameters too small Result: SSLError:

Bug#907807: After upgrading to OpenSSL 1.1.1, many sites are unreachable

Package: linkchecker Version: 9.4.0-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since the upgrade to OpenSSL 1.1.1pre9 in sid, linkchecker is unable to check many sites including: - ones without SNI - ones with DH parameters too small - ones using TLS 1.0 - ones

Bug#753464: firewalld: Upon startup, no rules are setup

❦ 31 août 2018 04:16 +0200, Michael Biebl : >> Upon startup, firewalld is running but nor rules are setup. >> >> firewalld.service - firewalld - dynamic firewall daemon >>Loaded: loaded (/lib/systemd/system/firewalld.service; enabled) >>Active: active (running) since mer. 2014-07-02

Bug#906955: isync: can't verify some ssl certificate(e.g. imap.gmail.com)

Package: isync Version: 1.3.0-1 Followup-For: Bug #906955 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! I run into the same problem. Here is a patch fixing the issue for me: https://sourceforge.net/p/isync/isync/merge-requests/2/ I don't know why it worked with OpenSSL 1.1.0. I didn't

Bug#886291: pycryptodome naming

❦ 13 août 2018 22:05 +0200, Alexis Murzeau : > Currently, packages which depends on python3-pycryptodome are: > - python3-httpsig > - python3-pysnmp4 > > python3-httpsig exists only in unstable. > python3-pysnmp4 exists in stable but depends on python3-crypto and the > version in

Bug#905403: graphite-api ftbfs

❦ 4 août 2018 07:33 +0200, Matthias Klose : > Package: src:graphite-api > Version: 1.1.3-3 > Severity: serious > Tags: sid buster > > missing build dependencies? > > running build_ext > tests (unittest.loader._FailedTest) ... ERROR > >

Bug#903663: python3-numpy: Should not depend on python3.7

Package: python3-numpy Followup-For: Bug #903663 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Why does python3-numpy depend on Python 3.7? It should work with any Python 3.x package. As a number of packages are uninstalled when python3.7 is installed, it would be convenient to not have

Bug#904977: Compile with GTK3

Package: gpicview Version: 0.2.5-2+b1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Would it be possible to compile GPicView with GTK3 instead of (or in addition to) GTK2? This would bring HiDPI support. With GTK2, the icons are tiny. A quick test by using

Bug#904976: Build with GTK3

Package: geeqie Version: 1:1.4-6 Severity: wishlist Hey! GTK3 support in Geeqie package is disabled because of #762718. However, we are almost 4 years later. It's likely the situation has been improved and Geeqie should be able to be compiled with GTK3. I did a quick test by removing the

Bug#900724: js2-mode: diff for NMU version 0~20170116-1.1

❦ 23 juillet 2018 18:00 +0800, Sean Whitton  : > I've prepared an NMU for js2-mode (versioned as 0~20170116-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I should delay > it longer. No problem. You can even skip the delay. -- Seeing that death, a necessary end, Will come

Bug#902999: fail with Python3.7: module 'uuid' has no attribute '_uuid_generate_time'

Package: python3-freezegun Version: 0.3.9-1 Severity: normal Tags: upstream patch fixed-upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! With Python 3.7, we get: ERROR collecting .pybuild/cpython3_3.7_cookiecutter/build/tests/test_default_extensions.py

Bug#902869: cookiecutter binary: Should depend on python-cookiecutter | python3-cookiecutter

❦ 2 juillet 2018 16:36 +0100, Joel Cross  : > Thanks for building a Python 3 version of this package. However, when > attempting to install the cookiecutter binary, I noticed it still depends on > the Python 2 library. > If memory serves correctly, it is possible to change the 'Depends' line to

Bug#900869: segfault when updating list of wireless networks

Package: network-manager-gnome Version: 1.8.12-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since the last update of nm-applet, it crashes for me when displaying the regular menu (left-click). Here is a backtrace of the problem: gdb$ bt full #0

Bug#888810: transmission-daemon: New rpc-host-whitelist does not persist

❦ 21 avril 2018 20:45 -0400, Sandro Tosi  : >> The new rpc-host-whitelist setting does not persist accross restart. >> Transmission likes to rewrite its configuration file. When it happens >> (on stop notably), the rpc-host-whitelist is written with an empty value >> instead of

Bug#872413: kpatch: Please package new upstream version

❦ 15 avril 2018 09:58 +0200, Simon Ruderich  : >> As the package is not currently usable with our kernel, or even the >> one in stable, I am bumping the severity. Since you already worked a >> lot on this, would you be interested to prepare an upload for 0.5.0? If >> yes, we

Bug#872413: kpatch: Please package new upstream version

severity 872413 serious thanks ❦ 17 août 2017 10:21 +0200, Simon Ruderich  : > Package: kpatch > Version: 0.3.2-3.1 > Severity: normal > Tags: patch > > Hello, > > The version of kpatch in Sid is quite old and doesn't work with > the current kernel. Please consider updating

Bug#895276: lldpd.service: mkdir fails if directory already exists

❦ 9 avril 2018 11:01 +0200, Laurent Bigonville  : > The .systemd file does a mkdir that fails if the directory already > exists. > > I would suggest to use RuntimeDirectory= instead (in conjunction with > RuntimeDirectoryPreserve= if the data need to survive the restart of the

Bug#894533: cookiecutter: please drop catchlog dependency

❦ 5 avril 2018 09:25 +0200, Gianfranco Costamagna  : > I uploaded the package in deferred/5, as Team upload. > > Unfortunately I can't push because the 1.6.0-1 upload hasn't been > pushed yet, so I'll attach the debdiff between the current package in > unstable and the

Bug#892914: reload hangs with systemd

Source: unbound Version: 1.6.7-1 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! The systemd integration is a bit buggy with reload. On reload, unbound will send STOPPING=1 then READY=1. After STOPPING=1 is sent, the unbound-control process terminates. When

Bug#890562: Provide an emoji-less version of DejaVu Sans

❦ 15 février 2018 23:40 +0100, Vincent Bernat <ber...@debian.org> : > As an alternative, Arch Linux provides an emoji-less DejaVu Sans. This > would also work for Debian. Would it be possible to follow the same > path? > > https://aur.archlinux.org/packages/ttf-dejavu-emo

Bug#890562: Provide an emoji-less version of DejaVu Sans

Package: src:fonts-dejavu Version: 2.37-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! DejaVu Sans provides some emojis in B In Debian, we have Noto Color Emoji which can be used for emojis. Unfortunately, when the base font is DejaVu Sans, the fallback doesn't happen.

Bug#851639: ITP: alacritty -- A cross-platform, GPU-accelerated terminal emulator

❦ 17 janvier 2017 01:00 -0500, Eric Dorland  : > * Package name: alacritty > Upstream Author : Joe Wilm > * URL : https://github.com/jwilm/alacritty > * License : Apache 2.0 > Programming Lang: Rust > Description : A

Bug#888810: transmission-daemon: New rpc-host-whitelist does not persist

Package: transmission-daemon Version: 2.92-2+deb9u1 Severity: normal Hey! The new rpc-host-whitelist setting does not persist accross restart. Transmission likes to rewrite its configuration file. When it happens (on stop notably), the rpc-host-whitelist is written with an empty value instead of

Bug#887423: [Pkg-net-snmp-devel] Bug#887423: snmptrapd: Systemd service unit definition of snmptrapd ignoring settings in /etc/default/snmptrapd

❦ 16 janvier 2018 11:01 +0100, Ingo Rauschenberg  : > I have to use the snmptrapd with some special mib-files from the > vendors of my hardware suppliers (like Dell, Brocate, Enterasys, Sun, > Rittal, ...). > Therefor I defined the MIBSDIR environment

Bug#887345: BIRD should be part of "network.target"

❦ 15 janvier 2018 17:03 +0100, Ondrej Zajicek  : >> A better solution (for me) would be: >> >> [Unit] >> Description=BIRD Internet Routing Daemon (IPv4) >> After=network-pre.target systemd-sysctl.service systemd-udevd.service >> Before=network.target multi-user.target

Bug#887345: BIRD should be part of "network.target"

❦ 15 janvier 2018 12:12 +0100, Vincent Bernat <ber...@debian.org> : >> On shutdown, BIRD is stopped early due to "After=network.target". This >> is troublesome when other services need the network to correctly >> stop. I am unsure of the right fix. Maybe: >

Bug#887345: BIRD should be part of "network.target"

❦ 15 janvier 2018 11:28 +0100, Vincent Bernat <ber...@debian.org> : > On shutdown, BIRD is stopped early due to "After=network.target". This > is troublesome when other services need the network to correctly > stop. I am unsure of the right fix. Maybe: [...] A bette

Bug#887345: BIRD should be part of "network.target"

Package: bird Version: 1.6.3-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! On shutdown, BIRD is stopped early due to "After=network.target". This is troublesome when other services need the network to correctly stop. I am unsure of the right fix. Maybe: [Unit]

Bug#886223: ITP: workalendar -- Worldwide holidays and working days helper and toolkit

Package: wnpp Severity: wishlist Owner: Vincent Bernat <ber...@debian.org> * Package name: workalendar Version : 2.3.1 Upstream Author : Bruno Bord <bruno.b...@people-doc.com> * URL : https://github.com/novafloss/workalendar * License : Expat Prog

Bug#885042: Check inclusion of Apache 2.0 NOTICE files

❦ 2 janvier 2018 12:04 -0800, Russ Allbery  : >>> We currently allow distribution of a binary-package-only Debian image >>> along with a written offer of source or, for non-commercial >>> distribution, a simple pointer to the Debian source archives. This >>> complies with the

Bug#885042: Check inclusion of Apache 2.0 NOTICE files

❦ 2 janvier 2018 10:42 -0800, Russ Allbery  : >>> Apache 2.0 requires distributing any NOTICE file along with derivative >>> works, but this is easy to forget. In many cases, we have effectively >>> the same information in debian/copyright, but even if this is the case >>> for

Bug#885042: Check inclusion of Apache 2.0 NOTICE files

❦ 22 décembre 2017 19:58 -0800, Russ Allbery  : > Apache 2.0 requires distributing any NOTICE file along with derivative > works, but this is easy to forget. In many cases, we have effectively > the same information in debian/copyright, but even if this is the case > for a

Bug#868408: xnee: Please drop the (build-)dependency against gnome-vfs

❦ 2 janvier 2018 02:02 +0100, Andreas Henriksson  : >> I have removed deps to gnomeui (gconf had already been removed) from Xnee >> sources. > > Vincent, please see the attached debdiff that incorporates Henriks > change as a patch in debian/patches/ for your convenience. >

Bug#885863: ITP: pysmi -- SNMP SMI/MIB Parser

Package: wnpp Severity: wishlist Owner: Vincent Bernat <ber...@debian.org> * Package name: pysmi Version : 0.2.2 Upstream Author : Ilya Etingof <etin...@gmail.com> <etin...@gmail.com> * URL : https://github.com/etingof/pysmi * License

Bug#872724: pyasn1

❦ 26 décembre 2017 21:08 +0200, Timo Aaltonen  : Do you expect one of us to upload or did you want to do that yourself (both are fine for me)? >>> >>> I didn't read the bug history. I'll upload a new version shortly, >>> without doing a transition because we don't

Bug#872724: pyasn1

❦ 26 décembre 2017 07:23 +0100, Vincent Bernat <ber...@debian.org> : >> Do you expect one of us to upload or did you want to do that yourself >> (both are fine for me)? > > I didn't read the bug history. I'll upload a new version shortly, > without doing a transition

Bug#872724: pyasn1

❦ 26 décembre 2017 07:21 +0100, Vincent Bernat <ber...@debian.org> : > Do you expect one of us to upload or did you want to do that yourself > (both are fine for me)? I didn't read the bug history. I'll upload a new version shortly, without doing a transition because we don'

Bug#872724: pyasn1

❦ 24 décembre 2017 22:25 +0200, Timo Aaltonen  : > On PyPy, though, it always raises TypeError. Before looking for > alternatives, please take a moment to read the following explanation as > to why it is the case. What you are looking for may not be possible. > > A memory

Bug#884517: Grab option should be reverted as enabled by default

Package: gpg-agent Version: 2.2.3-1 Severity: normal File: /usr/bin/gpg-agent -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! For some reason, upstream enabled the --no-grab option when asking for passphrase by default. I didn't find any rationale behind this change. See:

Bug#883771: ITP: openbmp -- BGP Monitoring Protocol (BMP) collector

Package: wnpp Severity: wishlist Owner: Vincent Bernat <ber...@debian.org> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: openbmp Version : 0.13.0 Upstream Author : Cisco Systems, Inc. and others * URL : https://github.com/OpenBMP/openbmp * L

Bug#883704: ImportError No module named contextlib2

❦ 6 décembre 2017 18:18 +0100, Philippe Pepiot  : import raven > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/raven/__init__.py", line 54, in > > from raven.base import * # NOQA > File

Bug#883607: ITP: golang-github-dgryski-go-farm -- go-farm: a pure-Go farmhash implementation

Package: wnpp Severity: wishlist Owner: Vincent Bernat <ber...@debian.org> * Package name: golang-github-dgryski-go-farm Version : 0.0~git20171119.ac7624ea8da3-1 Upstream Author : Damian Gryski * URL : https://github.com/dgryski/go-farm * License :

Bug#882688: use uaccess instead or in addition to plugdev

Package: android-sdk-platform-tools-common Version: 24.0.0+5 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! The udev rules shipped with the package gives access to Android stuff only for users in group plugdev. It would be convenient if non-privileged local users were

Bug#882676: [Pkg-net-snmp-devel] Bug#882676: Missing modules?

❦ 25 novembre 2017 16:12 +0100, Laurent Bigonville  : > If I'm installing snmp-mibs-downloader, the messages are going away Dunno what xsane is trying to do, but MIBs are non-free, so it's not possible to add a dependency. -- Harp not on that string. --

Bug#882568: RFS: nq/0.2.1-1 [ITP]

❦ 24 novembre 2017 21:25 +0100, Nicolas Braud-Santoni  : >> Any MBF should be discussed first on debian-devel@ first. For me, >> this seems a small violation and it would be preferable to stick with >> severity normal to not appear too agressive. > > Only 8 source

Bug#882568: RFS: nq/0.2.1-1 [ITP]

❦ 24 novembre 2017 17:48 +0100, Nicolas Braud-Santoni  : >> In d/copyright: you need to include the complete CC0 license. > > OK; I did so based on what other packages were doing, according to > codesearch.d.n [0]. If that's an acceptable solution, I will > - include

Bug#882568: RFS: nq/0.2.1-1 [ITP]

❦ 24 novembre 2017 02:44 +0100, Nicolas Braud-Santoni  : > I am looking for a sponsor for my package "nq" > > * Package name: nq >Version : 0.2.1-1 >Upstream Author : Leah Neukirchen > * URL :

Bug#882488: ITP: sshpubkeys -- SSH public key parser for Python

Package: wnpp Severity: wishlist Owner: Vincent Bernat <ber...@debian.org> * Package name: sshpubkeys Version : 2.2.0 Upstream Author : Olli Jarva <o...@jarva.fi> * URL : https://github.com/ojarva/python-sshpubkeys * License : BSD-3-clause Prog

Bug#882125: incompatible with pidgin apparmor profile

Package: pidgin-sipe Version: 1.23.0-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! AppArmor is now enabled by default in Debian and pidgin comes with an AppArmor profile. When pidgin-sipe is installed, we get this error: /usr/bin/pidgin: line 7:

Bug#842980: ITP: jtextfsm -- template based state machine for parsing semi-formatted text

❦ 2 novembre 2016 19:28 +0100, Vincent Bernat <ber...@debian.org> : > * Package name: jtextfsm > Version : 0.3.1 > Upstream Author : Google; Jonathan Slenders <textfsm-...@googlegroups.com> > * URL : https://github.com/jonathanslen

Bug#880701: lintian: Please update the Debian archive sections

❦ 4 novembre 2017 09:11 GMT, Chris Lamb  : > tags 880701 + pending > thanks > > Thanks! Applied in Git: > > > https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=a01ed6cd1520ad16d0c0cc3a47b8c264ca49f8b9 This is too soon. The section doesn't exist yet. The

<    1   2   3   4   5   6   7   8   9   10   >