Bug#705936: (no subject)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i would like to take on this wishlist item, since nobody else has yet. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/

Bug#705939: I'll do it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Let's see whether I have more luck this time :) I'd like to work on this bug! - -- GPG-Key: https://bit.ly/vwmUVA or 00B96447 on your favourite keyserver -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with

Bug#705939: fix

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 See https://github.com/dynalogin/dynalogin/pull/1 diff --git a/libdynalogin/dynalogin.c b/libdynalogin/dynalogin.c index d6b606b..f57039e 100644 - --- a/libdynalogin/dynalogin.c +++ b/libdynalogin/dynalogin.c @@ -267,8 +267,20 @@ dynalogin_result_t

Bug#702080: +1

Any news on this? Especially since Django 1.5.2 is already in wheezy-backports, which makes all versions of django-reversion currently available in debian (partially) incompatible. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#759246: calibre: new upstream version (2.0)

Package: calibre Version: 1.48.0+dfsg-1 Severity: wishlist Hello, there is a new upstream version of calibre, featuring an ebook editor as well as switching to QT5. Thanks for your work, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#669704: Suggestion: move autopsy maintenance to Debian Forensics team

Hello, since there has not been any progress on this bug for over a year (and no new versions for the package itself for over 3.5 years, despite upsteam activity), I kindly ask the Debian Forensics team to adopt the autopsy package, if resources permit. The current maintainer has stated a lack of

Bug#669704: Suggestion: move autopsy maintenance to Debian Forensics team

Hello again, after a bit more research, it seems the new 3.x branch of autopsy is windows only unfortunately. It seems the last linux version was indeed 2.24 . I will look into which modifications are necessary to get it to run with the current sleuthkit. Kind regards, Fabian -- GPG:

Bug#761994: Extra profile for /usr/sbin/useradd ,, missing access right for /etc/subuid and /etc/subgid

Package: apparmor-profiles Version: 2.8.0-6 Severity: normal Tags: patch Hello, the AppArmor profile for useradd (which is not activated by default, but located in /usr/share/doc/apparmor-profiles/extras/usr.sbin.useradd) seems to be missing a couple of lines for the files /etc/subuid ,

Bug#762014: XBMC fails to download any files (ERROR: CCurlFile::FillBuffer - Failed:, Timeout was reached)

Package: xbmc-bin Version: 2:13.1~rc1+dfsg1-1+b2 Severity: normal Hello, XBMC fails to download any file from the net using libcurl (i.e., no updating of addons, no scraping of movies/tv-shows/music, ..). The logfile repeats the following lines for every file it tries to download: 20:01:37

Bug#762014: XBMC fails to download any files (ERROR: CCurlFile::FillBuffer - Failed:, Timeout was reached)

Hello again, after downgrading libcurl3-gnutls to version 7.37.1-1, everything works as expected again. I guess the problem lies either within xbmc's usage of libcurl or within libcurl, so I am leaving the bug as is for now. Thanks, Fabian -- GPG:

Bug#766108: pinentry-gtk2 prevents pasting from the clipboard

According to the upstream bug report[0], this issue should be fixed for gtk as well in the new upstream version 9.0 (released on October 26th 2014). Since this effectively disables the combined use of password managers and gpg-agent in GUI programs like icedove/enigmail, it breaks a rather common

Bug#783922: Newest TBB does not start with provided AppArmor profile in enforce mode

Package: torbrowser-launcher Version: 0.1.9-1 Severity: normal Tags: upstream Starting the TBB using torbrowser-launcher simply exits without any error message. When run from a terminal, the following output is displayed: -snip- Tor Browser Launcher By Micah Lee,

Bug#849969: [Pkg-zfsonlinux-devel] Bug#849969: root zpool broken on Debian stretch

> Lukas Wunner hat am 28. Januar 2017 um 21:59 geschrieben: > > There are two unrelated glitches though: > > (1) systemd complains on boot: > > "systemd[2234]: zfs-share.service: Failed at step EXEC spawning > /usr/sbin/rm: No such file or directory" > > This

Bug#851512: fails to build with 4.9 kernel

Package: spl-dkms Severity: important Tags: patch since the 4.9 kernel is now available in unstable, the following upstream patches need to be cherry-picked for compatibility: aa70231f096dff572cfb1307d8f4e63dbf2b60f1 587ceae110e900da1203192336e3a14d4161b777 please find conflict-resolved

Bug#851513: Build fails with Linux kernel 4.9.0

Package: zfs-dkms Severity: important Tags: patch since the 4.9 kernel is now available in unstable, the following upstream patches need to be cherry-picked for compatibility: 8ba3f2bf6a66378b36acd70e5616a78396030984 7ca25051b6470e8471b4ed454d8c66ff21338de3

Bug#820888: cryptsetup: initramfs cryptroot zfs support

On Mon, 19 Sep 2016 00:43:28 -0500 Richard Laager wrote: > For whatever my opinion is worth... :) > > I see you are using ZFS on top of LVM on top of LUKS. (Or ZFS inside LVM > inside LUKS, if you prefer that way of looking at it.) While that's > theoretically something that

Bug#842237: zfs-share.service tries to call /usr/sbin/rm

Package: zfsutils-linux Version: 0.6.5.7-2 Severity: normal Bug #832938 changed the bindir macro to /usr/sbin in order to move the arc* python scripts there. Unfortunately, this macro is also used in the zfs-share.service.in file as the location of the "rm" binary - which is installed to /bin on

Bug#842237: zfs-share.service tries to call /usr/sbin/rm

On Thu, Oct 27, 2016 at 11:28:47AM +0200, Petter Reinholdtsen wrote: > [Fabian Grünbichler] > > The correct approach seems to be to patch the arc* script automake files > > to use the sbindir macro (although that currently gets set to /sbin , > > not /usr/sbin , so maybe

Bug#842237: zfs-share.service tries to call /usr/sbin/rm

On Thu, Oct 27, 2016 at 12:11:12PM +0200, Petter Reinholdtsen wrote: > [Fabian Grünbichler] > > IMHO, that's a step in the right direction, especially for preventing > > future misplaced files (bindir should not be set to [/usr]/sbin). But > > note that this moves the scrip

Bug#842237: [Pkg-zfsonlinux-devel] Bug#842237: zfs-share.service tries to call /usr/sbin/rm

ut setting bindir to /usr/bin should prevent future mishaps with binaries that are supposed to end up in /usr/bin (which is upstream's default for bindir) Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- debian/rules | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-)

Bug#824974: grub-pc: grub-probe fails on root-on-ZFS systems

Tags: patch, upstream this should be fixed with the attached patch included in Ubuntu yakkety's grub2 package. it uses the environment variable ZPOOL_VDEV_NAME_PATH to cause "zpool status" to generate output like "zpool status -P" would (since the latter is not available for all ZFS

Bug#820888: [pkg-cryptsetup-devel] Bug#820888: cryptsetup: initramfs cryptroot zfs support

On October 10, 2016 9:09:12 PM GMT+02:00, Guilhem Moulin <guil...@guilhem.org> wrote: >Hi Fabian, > >On Mon, 10 Oct 2016 at 20:42:00 +0200, Fabian Grünbichler wrote: >> + [ -r /conf/conf.d/cryptroot ] >> + exit 0 > >Looks like /conf/conf.d/cryptroot wasn't g

Bug#847018: zfs-dkms: fails to build against kernel version 4.8.0-2-amd64i

On 12/15/2016 10:46 PM, Achim Schaefer wrote: > Hi Petter, > > I'm not sure how to fetch the git version, so without any hint where to > start I don't know how to do this. > > Maybe you could provide a good source of informations, so I might be > able to do it. > (I've done a much simpler

Bug#806273: Patch for disabling kernel mounts when grub-mount is available

On Wed, Nov 16, 2016 at 12:30:52PM +0100, Emmanuel Kasper wrote: > On 11/15/2016 06:25 PM, Ben Hutchings wrote: > > On Tue, 2016-11-15 at 15:33 +0100, Emmanuel Kasper wrote: > >> The included patch disables read_only mounts when grub-mount is available. > > > > Why not require that grub-mount is

Bug#847018: zfs-dkms: fails to build against kernel version 4.8.0-2-amd64

On Wed, 7 Dec 2016 13:35:00 +0100 =?UTF-8?Q?Holger_Schr=c3=b6der?= wrote: > Hi. > > Does anyone have a patch for 0.6.5.8? > > > thanks > > The linked commit[1] seems to work just fine on top of the current 0.6.5.8 package in unstable / testing (and applies cleanly, like

Bug#851127: update OpenSSL 1.1.0 compat patch with upstream v2

Source: spice-gtk Version: 0.33-3.1 Severity: important Tags: patch #828554 was originally filed because of missing OpenSSL 1.1.0 compatibility for spice-gtk, and was fixed with an NMU including a proposed patch as 0.33-3.1 . this patch has been replace upstream with a patch series (current and

Bug#847018: zfs-dkms: fails to build against kernel version 4.8.0-2-amd64

This is fixed with a (clean) cherry-pick of upstream commit 3b0ba3ba99b8a3af0fb532bf264629436b1abd84 [1]. Note sure in which format patches are desired for pkg-zfsonlinux.. A local test build including the above commit works as expected.. 1:

Bug#848944: grub-common: grub-probe fails for ZFS root pool on /dev/mapper device

this is a duplicate of #824974 and thus fixed in stretch/sid's grub2/2.02~beta3-3 maybe a backport of that one for jessie-backports would help you? since ZoL is only available via -backports as well.. alternatively, you could try to build jessie with the single patch setting the environment

Bug#851512: Acknowledgement (fails to build with 4.9 kernel)

Control: merge 851352 -1 Only checked zfs-dkms for existing bugs, and thus missed this one. Merging accordingly, sorry for the additional noise!

Bug#858252: unix domain socket forwarding broken for root user

Package: openssh-server Version: 1:7.4p1-1 Severity: critical Tags: patch upstream Commit b737e4d7433577403a31cff6614f6a1b0b5e22f4 disabled unix domain socket forwarding when privsep is disabled. Unfortunately, privsep is always "disabled" for the root user, so this completely broke unix socket

Bug#842237: zfsutils-linux: 0.6.5.9-2 still fails - zfs-share.service

986c2ea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= <f.gruenbich...@proxmox.com> Date: Thu, 27 Oct 2016 10:18:55 +0200 Subject: [PATCH] fix rm path in zfs-share.service MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit S

Bug#871619: zfs-dkms: Please package ZFS 0.7.0

I started some (unofficial, not-ready-for-production-use-yet) branches for SPL and ZFS 0.7.0, available on github in case anyone wants to take a look: https://github.com/Fabian-Gruenbichler/zfs/tree/debian/wip-0.7 https://github.com/Fabian-Gruenbichler/spl/tree/debian/wip-0.7 no pre-built

Bug#871619: zfs-dkms: Please package ZFS 0.7.0

On Tue, Sep 19, 2017 at 09:35:10AM -0400, Chris Zubrzycki wrote: > Any update or possibly a mailing list for the group we can subscribe to? > ubuntu has had 0.7 for a while now… > > Thanks. > > Ubuntu is (also) still on 0.6.5.11[1]. you can subscribe to the pkg-zfsonlinux-devel list[2], but

Bug#871619: [Pkg-zfsonlinux-devel] Bug#871619: Bug#871619: Packaging

On Fri, 6 Oct 2017 08:49:51 +0200 Dmitry Galenko wrote: > I successful build deb packages from upstream repo, for kernel 4.10 > (custom) without any changes with this instruction: > > [snip] this is not a good idea for production use IMHO - those converted packages using

Bug#871619: Packaging

> Aron Xu hat am 6. Oktober 2017 um 18:19 geschrieben: > > > Hi, > > On Fri, Oct 6, 2017 at 4:59 PM, Petter Reinholdtsen wrote: > > > > [Antonio Russo] > >> How can I help out the packaging team on this? Who should I email? > > > > The best way to help is to

Bug#842237: zfsutils-linux: zfs-share.service still tries to call /usr/bin/rm on Debian stable

On Sat, 07 Oct 2017 21:20:51 +0200 dchrist wrote: > Package: zfsutils-linux > Version: 0.6.5.9-5 > Followup-For: Bug #842237 > > Dear Maintainer, > > the systemd unit zfs-share.service still tries to run /usr/bin/rm on > ExecStartPre, > which does not exist. > >

Bug#871619: [Pkg-zfsonlinux-devel] Bug#871619: Packaging

On Thu, Oct 05, 2017 at 08:10:16PM -0400, Antonio Russo wrote: > Hi! > > I forked the Alioth repository, and got the debian packaging able > to build 0.7.2 (the spl ./debian required no changes). > > The fork is available on github: > >

Bug#871619: Packaging

enbich...@proxmox.com> Date: Thu, 12 Oct 2017 08:57:48 +0200 Subject: fix install path of zpool.d scripts MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- cmd/zpool/Make

Bug#871619: Packaging

On Sat, Oct 07, 2017 at 12:19:35AM +0800, Aron Xu wrote: > Hi, > > On Fri, Oct 6, 2017 at 4:59 PM, Petter Reinholdtsen wrote: > > > > [Antonio Russo] > >> How can I help out the packaging team on this? Who should I email? > > > > The best way to help is to continue contributing

Bug#882209: [Pkg-zfsonlinux-devel] Bug#882209: zfs-linux: remove manual calls to dpkg-architecture and dpkg-parsechangelog

On Thu, Nov 23, 2017 at 09:50:40PM +0800, Aron Xu wrote: > Hi > > On Mon, Nov 20, 2017 at 5:16 PM, Fabian Grünbichler > <f.gruenbich...@proxmox.com> wrote: > > Source: zfs-linux > > Severity: wishlist > > Tags: patch > > > > please see att

Bug#879585: apparmor: Pin the AppArmor feature set in Stretch to Linux 4.9's

On Tue, Dec 05, 2017 at 11:37:51AM +0100, intrigeri wrote: > Hi Fabian! > > Fabian Grünbichler: > > is there a particular reason for not putting this into the (included by > > default) /usr/share/apparmor, but into parser.conf directly? > > Does "this&quo

Bug#879585: apparmor: Pin the AppArmor feature set in Stretch to Linux 4.9's

On Mon, Oct 23, 2017 at 08:34:58AM +0200, intrig...@debian.org wrote: > Package: apparmor > Version: 2.11.0-3 > Severity: important > > This is about supporting Stretch users who have enabled AppArmor > and run a new kernel, e.g. from stretch-backports. > > Similarly to #879584, let's pin the

Bug#884706: zfs-linux: make distclean deletes commands.cfg, which is not regenerated

On Mon, Dec 18, 2017 at 02:49:48PM +0100, Andreas Beckmann wrote: > Source: zfs-linux > Version: 0.7.3-3 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > Hi, > > zfs-linux fails to build twice in a row. The first build succeeds, the >

Bug#880709: zfsutils-linux 0.7.3 has an unlisted dependency on libuutil1linux >= 0.7.3

On Thu, Nov 16, 2017 at 10:09:45AM -0500, Rich wrote: > I'm not sure I understand what you mean by symbol files for the libraries, > here - I know what symbols are, and usually I'd expect symbol files to > refer to something like external debug symbols, but it sounds like you're > suggesting

Bug#880709: zfsutils-linux 0.7.3 has an unlisted dependency on libuutil1linux >= 0.7.3

On Sat, Nov 04, 2017 at 12:17:48AM -0400, Rich Ercolani wrote: > Package: zfsutils-linux > Version: 0.7.3-1 > Severity: important > > Dear Maintainer, > > As the subject says, if you just install > {zfsutils-linux,spl-dkms,zfs-dkms}/unstable, you can end up with > libuutil1linux from stable or

Bug#880902: [Pkg-zfsonlinux-devel] Bug#880902: zfs-test: fails to upgrade from 'testing' - trying to overwrite /usr/share/zfs/common.sh

On Sun, Nov 05, 2017 at 03:18:57PM +0100, Andreas Beckmann wrote: > Package: zfs-test > Version: 0.7.3-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed

Bug#882209: zfs-linux: remove manual calls to dpkg-architecture and dpkg-parsechangelog

enbich...@proxmox.com> Date: Mon, 20 Nov 2017 09:48:08 +0100 Subject: [PATCH 1/3] d/rules: include dpkg's default.mk MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- debian/rules

Bug#880709: Library versions

8bit to mimic upstream's current level of ABI/API stability. this is akin to "every upstream version breaks compatibility". Closes: #880709 Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- debian/rules | 12 ++-- 1 file changed, 6 insertions(+), 6 dele

Bug#883682: don't install features-file as conffile for easier overriding

On Thu, Dec 07, 2017 at 08:47:52AM +0100, intrigeri wrote: > Control: tag -1 - patch > Control: severity -1 normal > > Hi, hi (no need to CC me, I subscribe to all bugs I submit ;)) > > Fabian Grünbichler: > > see attached patch. > > Thanks! > > > I di

Bug#883682: don't install features-file as conffile for easier overriding

On Thu, Dec 07, 2017 at 10:08:54AM +0100, intrigeri wrote: > Hi, > > Fabian Grünbichler: > > On Thu, Dec 07, 2017 at 08:47:52AM +0100, intrigeri wrote: > >> > I am not sure whether we are the only derivative/downstream/.. affected > >> > by this change,

Bug#883682: don't install features-file as conffile for easier overriding

On Thu, Dec 07, 2017 at 10:45:11AM +0100, intrigeri wrote: > Fabian Grünbichler: > > sounds like a plan, I'll re-spin my patch later today. > > :) > see attached, tested on Sid with various modification scenarios. I think the messages printed by apt are enough, and there

Bug#883682: don't install features-file as conffile for easier overriding

Control: tags + patch On Wed, Dec 06, 2017 at 11:31:45AM +0100, intrigeri wrote: > Hi, > > Fabian Grünbichler: > > I am not sure whether the features file itself would really need to be a > > conf file though, if it is already pointed to by a conf file directive? > >

Bug#883682: don't install features-file as conffile for easier overriding

and actually attaching the patch this time diff --git a/debian/patches/pin-feature-set.patch b/debian/patches/pin-feature-set.patch index c12f1c4..0118aad 100644 --- a/debian/patches/pin-feature-set.patch +++ b/debian/patches/pin-feature-set.patch @@ -15,4 +15,4 @@ Author: intrigeri

Bug#882697: stretch-pu: package apparmor/2.11.0-3+deb9u1

On Sat, Dec 02, 2017 at 07:21:59PM +, Adam D. Barratt wrote: > Control: tags -1 + pending > > On Sat, 2017-12-02 at 14:37 +0100, intrigeri wrote: > > Adam D. Barratt: > > > Please go ahead, bearing in mind that the window for getting fixes > > > into > > > the 9.3 point release closes during

Bug#882697: stretch-pu: package apparmor/2.11.0-3+deb9u1

On Wed, Dec 06, 2017 at 03:28:03PM +0100, intrigeri wrote: > Hi, > > I'll first clarify because it seems to me you're using the same word > with very different meanings in a comparison: > > Fabian Grünbichler: > > TL;DR: while pinning the features prevents breakage for

Bug#899047: zfs-test: outdated B+R for files taken over from zfsutils-linux

Package: zfs-test Version: 0.7.9-2 Severity: serious commit 2c29cd95fd0e5fccc035bf7dead27a4b73708f12 moved the following files from zfsutils-linux to zfs-test, without updating zfs-test's versioned Breaks+Replaces relation accordingly: /sbin/ztest the following files are now also installed in

Bug#891890: ITP: zfs-linux-git -- zfsonlinux packaging tracking git master

(trimmed down a bit) On Fri, Jun 22, 2018 at 06:49:48PM -0400, Antonio Russo wrote: > On 6/22/18 4:17 AM, Fabian Grünbichler wrote: > > - given the different licences and thus parts of the archive, I am not > > sure whether we can merge zfs-dkms and spl-dkms inside Debian >

Bug#902449: cryptsetup-initramfs: auto-detection of zfs pool(s)

Package: cryptsetup-initramfs Version: 2:2.0.3-4 hello again! still running the same setup with a fully encrypted single vdev used as rpool. since the recent refactoring and split into cryptsetup-{run,initramfs}, I now get the following messages on every initramfs generation: cryptsetup: ERROR:

Bug#902449: cryptsetup-initramfs: auto-detection of zfs pool(s)

On Wed, Jun 27, 2018 at 12:56:04PM +0200, Guilhem Moulin wrote: > Control: severity -1 wishlist > > Hi, > > On Tue, 26 Jun 2018 at 23:34:20 +0200, Fabian Grünbichler wrote: > > cryptsetup: ERROR: Couldn't normalise device rpool/ROOT/debian > > cryptsetup: ERROR: Co

Bug#871619: Packaging

On Thu, Oct 12, 2017 at 06:51:05AM -0400, Antonio Russo wrote: > On 10/12/17 06:12, Fabian Grünbichler wrote: > > > > I would also suggest cherry-picking/backporting the following two > > upstream PRs on top of 0.7.2: > > > > #6616: send/recv compati

Bug#891890: ITP: zfs-linux-git -- zfsonlinux packaging tracking git master

On Wed, Jun 06, 2018 at 12:17:13AM -0400, Antonio Russo wrote: > I have packaging of zfsonlinux (for upstream git revisions) that > is in need of review [1]. It builds, and zfs-dkms builds as well. > I have only done very superficial testing (i.e., the zfs module > loads, you can create a pool). >

Bug#892958: Acknowledgement (deb-systemd-invoke: add support for "reload-or-restart")

Opened a MR[1] for easier review and merging, patch is a rebased version of this one. Feedback appreciated. 1: https://salsa.debian.org/debian/init-system-helpers/merge_requests/5

Bug#908290: [zfs-linux] Please package 0.7.10

On Sat, Sep 08, 2018 at 12:33:57AM -0400, Antonio Russo wrote: > Package: zfs-linux > Severity: important > Tags: patch > > --- Please enter the report below this line. --- > > The release of 0.7.10 should (I believe) supersede [2]. indeed it does! closed the MR accordingly.. > [2]

Bug#892958: deb-systemd-invoke: add support for "reload-or-restart"

emd[1], deb-systemd-invoke should support "reload-or-restart" with the same semantics as "restart". 1: https://salsa.debian.org/debian/debhelper/merge_requests/1 Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- script/deb-systemd-invoke | 6 +++---

Bug#891890: ITP: zfs-linux-git -- zfsonlinux packaging tracking git master

On Thu, Mar 01, 2018 at 10:48:57PM -0500, Antonio Russo wrote: > Package: wnpp > Severity: wishlist > X-Debbugs-CC: debian-de...@lists.debian.org > > --- Please fill out the fields below. --- > >Package name: zfs-linux-git > Version: 0.8~ > Upstream Author: Brian Behlendorf

Bug#891936: zfs-dkms: 32/64-bit detection via /proc/kallsyms is a bad idea

Package: zfs-dkms Version: 0.7.6-1 Severity: normal the zfs-dkms package tries to detect whether the (running) kernel is a 32-bit or 64-bit one with the following stanza (in zfs-dkms.config / zfs-dkms.postinst): $ head -1 /proc/kallsyms|awk '{print $1}'|wc -c and checking the length of the

Bug#913446: wireguard-tools: optionally reload module / interfaces on upgrade

Package: wireguard-tools Version: 0.0.20181018-1 Severity: wishlist Tags: patch as discussed on the WG mailing list[0], this would be nice to have - similar to what the Ubuntu PPA offers, but with debconf integration and a bit less noise on stdout. MR with a WIP implementation incoming on salsa.

Bug#913446: wireguard-tools: optionally reload module / interfaces on upgrade

On Wed, Nov 14, 2018 at 04:55:03PM -0500, Daniel Kahn Gillmor wrote: > a) is there a risk that we could somehow have the wireguard kernel > module loaded, but *not* have wireguard.ko available for finding via > modinfo -F ? If that's the case, then it looks like the postinst > script

Bug#913446: wireguard-tools: optionally reload module / interfaces on upgrade

On Wed, Nov 14, 2018 at 02:39:10AM -0500, Daniel Kahn Gillmor wrote: > Some questions: > > * why put the module reloading in wireguard-tools.postinst and not in >wireguard.postinst ? There's no guarantee that wireguard-dkms will >have been upgraded by the time wireguard-tools.postinst

Bug#919167: tmuxp FTBFS and completely broken with python-click 7.0-1

FWIW, this was reported upstream[0], and fixed[1], and released as part of 1.5.0a. Either backporting the relevant changes from PR 434 or updating to 1.5.0(a) seems like a good idea. 0: https://github.com/tmux-python/tmuxp/issues/433 1: https://github.com/tmux-python/tmuxp/pull/434 2:

Bug#892958: deb-systemd-invoke: add support for "reload-or-restart"

any feedback on this? I am waiting to rebase the debhelper MR making use of this functionality until there is some kind of indication that it might be accepted here ;)

Bug#916639: Related bugs

also see [0,1] for related discussions elsewhere. 0: https://github.com/lxc/lxc/issues/2778 1: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248

Bug#918839: systemd: LXC Container with debian buster can no longer start services after updating to systemd_240

the original reporter did not mention it explicitly (although the kernel version already indicates it ;)) - the original occurrence of this issue was on a Debian derivative (Proxmox Virtual Environment), which does not use Debian's kernel (and thus neither the same AppArmor LSM code nor AppArmor

Bug#909092: tmuxinator: missing dependency on ruby-xdg

Package: tmuxinator Version: 0.12.0-1 Severity: serious Justification: Policy 3.5 any tmuxinator command prints the following trace: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- xdg (LoadError) from

Bug#667738: libhttp-daemon-perl: HTTP::Daemon::ClientConn is IPv4 only

Hello perl maintainers :) I opened up a MR on salsa[1] to include the patches from upstream's bug tracker that enable IPv6 support by switching to IO::Socket::IP - it would be great if somebody can take a look at them and upload the -2 package ;) Kind Regards, Fabian 1:

Bug#922086: RFP: kanshi -- dynamic display configuration manager

Package: wnpp Severity: wishlist * Package name: kanshi Version : 0.2.1 Upstream Author : emersion * URL : https://github.com/emersion/kanshi * License : MIT Programming Lang: Rust Description : Dynamic display configuration manager Kanshi uses a

Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error

On September 11, 2019 3:45:45 PM UTC, Daniel Kahn Gillmor wrote: >Over on https://bugs.debian.org/939845, On Wed 2019-09-11 00:26:18 >-0400, Matthew Gabeler-Lee wrote: >> Having a system update disable a network interface and fail to >restore it is >> ... bad. Luckily I wasn't accessing the

Bug#951278: ITP: cargo-lock -- Self-contained Cargo.lock parser

Package: wnpp Severity: wishlist Owner: Fabian Grünbichler * Package name: cargo-lock Version : 4.0.1 Upstream Author : Tony Arcieri * URL : https://github.com/rustsec/cargo-lock * License : Apache-2.0 or MIT Programming Lang: Rust Description : Self

Bug#950013: [Pkg-rust-maintainers] Bug#950013: RFP: rust-tokio-sync -- rust synchronization utilities

On January 28, 2020 11:38 am, Patrick Matthäi wrote: > Package: wnpp > Severity: wishlist > > * Package name: rust-tokio-sync > Version : 0.1.7 > Upstream Author : Carl Lerche > * URL : https://crates.io/crates/tokio-sync > * License : MIT > Programming

Bug#950011: [Pkg-rust-maintainers] Bug#950011: RFP: rust-async-trait -- rust Async trait methods

On January 28, 2020 11:30 am, Patrick Matthäi wrote: > Package: wnpp > Severity: wishlist > > * Package name: rust-async-trait > Version : 0.1.22 > Upstream Author : David Tolnay > * URL : https://github.com/dtolnay/async-trait > * License : MIT OR Apache-2.0

Bug#951549: systemd-fstab-generator: zfs entries in fstab should require zfs-import-scan or zfs-import-cache

On February 18, 2020 11:06 am, Michael Biebl wrote: > Am 18.02.2020 um 01:21 schrieb Peter B: >> Package: systemd >> Version: 244-3 >> Severity: normal >> >> >> >> -- Package-specific info: >> >> ZFS filesystems can be mounted through fstab, the zpool needs to be >> imported before the mount.

Bug#951368: ITP: cargo-deny -- Cargo plugin to help you manage large dependency graphs

Package: wnpp Severity: wishlist Owner: Fabian Grünbichler * Package name: cargo-deny Version : 0.6.4 Upstream Author : Jake Shadle * URL : https://github.com/EmbarkStudios/cargo-deny * License : MIT or Apache-2.0 Programming Lang: Rust Description

Bug#953668: [Pkg-rust-maintainers] Bug#953668: cargo fails to find default X.509 certificates to validate https on powerpc

On March 12, 2020 12:06 am, Daniel Kahn Gillmor wrote: > Package: cargo > Version: 0.40.0-3 > > Starting from an empty ~/.cargo, by default on the powerpc platform, > cargo fails to find the right X.509 certificates to validate an https > connection to github.com. > > But if i explicitly point

Bug#927889: libgit2: Specify certificate locations

On April 24, 2019 6:27 pm, Dan Nicholson wrote: > Source: libgit2 > Version: 0.27.7+dfsg.1-0.1 > Severity: important > Tags: patch > > When libgit2 is built with mbedTLS, it tries to determine the trusted > certificate location at build time. Unless openssl and ca-certificates are > installed,

Bug#953668: [Pkg-rust-maintainers] Bug#953668: cargo fails to find default X.509 certificates to validate https on powerpc

On November 28, 2020 12:41 pm, Jan Niehusmann wrote: > Hi, > > On Thu, Mar 12, 2020 at 11:07:08AM +0100, Fabian Grünbichler wrote: >> I am not sure whether we want to work around it in cargo (by defaulting >> to that location, for example), but this is related to >>

Bug#981153: [Pkg-rust-maintainers] Bug#981153: cargo: Please package new upstream (blocks Firefox 85)

On January 27, 2021 2:22 pm, Amy Kos wrote: > Hi, > > raising severity, due to several high impact security vulnerabilities fixed > in Firefox 85. > > https://www.mozilla.org/en-US/security/advisories/mfsa2021-03/ IMHO we'd need a freeze exception from the RT to update cargo at this point in

Bug#988729: [Pkg-rust-maintainers] Bug#988729: CVE-2021-21299

On May 18, 2021 8:42 pm, Moritz Muehlenhoff wrote: > Source: rust-hyper > Severity: grave > Tags: security > X-Debbugs-Cc: Debian Security Team > > CVE-2021-21299: > https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf > https://rustsec.org/advisories/RUSTSEC-2021-0020.html

Bug#975191: [Pkg-rust-maintainers] Bug#975191: Bug#975191: re: rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

On August 31, 2021 9:16 pm, Wolfgang Silbermayr wrote: > On 8/31/21 4:25 PM, Bastian Germann wrote: >> On Wed, 2 Dec 2020 02:46:36 + peter green wrote: >>>  > This will impact quite some other modules. >>> >>> I agree that the current autoremoval list looks pretty scary, so I decided >>> to

Bug#994204: dh_installsystemd: --no-stop-on-upgrade has no effect, seemingly broken in 6067bc2f

On September 13, 2021 7:39 pm, Arnaud Rebillout wrote: > Package: debhelper > Version: 13.5.1 > Severity: normal > X-Debbugs-Cc: ni...@thykier.net > > Dear Maintainer, > > First let me give a bit of context: > > I was putting some work on the docker.io package. Right now docker.io > depends on

Bug#998716: linux-image-5.14.0-2-amd64: The package size has grown a lot compared to 5.8/5.10 releases

On Tue, Nov 30, 2021 at 08:18:56PM +0100, Ben Hutchings wrote: > On Tue, 2021-11-30 at 11:01 +0100, Fabian Grünbichler wrote: > [...] > > possibly interesting in that context (I asked/posted the link in > > #debian-kernel a few days ago as well) - these BTF sections now actua

Bug#974606: [Pkg-rust-maintainers] Bug#974606: should rust-tokio-process be removed?

On November 12, 2021 6:47 am, peter green wrote: > In addition to the (build-)dependency on an old version of > rust-crossbeam-queue, > rust-tokio-process (build-)depends on version 0.1 of rust-futures. Upstream > seems to > have abandoned the crate, there was an alpha release supporting futures

Bug#999507: [Pkg-rust-maintainers] Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.

On November 12, 2021 6:38 am, Peter Green wrote: > Package: rust-tokio-signal > Version: 0.2.7-2 > Severity: serious > > rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream > seems to > have abandoned the project, there was an alpha release supporting futures > 0.2, but >

Bug#999507: [Pkg-rust-maintainers] Bug#999507: Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.

On November 12, 2021 1:11 pm, Henry-Nicolas Tourneur wrote: > > > Le ven 12 nov 2021 à 10:18, Fabian Grünbichler > a écrit : >> On November 12, 2021 6:38 am, Peter Green wrote: >>> Package: rust-tokio-signal >>> Version: 0.2.7-2 >>> Severit

Bug#998716: linux-image-5.14.0-2-amd64: The package size has grown a lot compared to 5.8/5.10 releases

On November 30, 2021 12:57 am, Ben Hutchings wrote: > On Sun, 07 Nov 2021 03:52:13 +0200 Bohdan Horbeshko > wrote: >> Package: linux-image-5.14.0-2-amd64 >> Severity: minor >> >> Dear Maintainer, >> >> the Installed-Size of the package has occasionally grown up to 375 MB, >> which is about 30%

Bug#1003210: Linux kernel module loading failing with "failed to validate module" error

On Thu, Jan 06, 2022 at 10:18:23AM +, Ben Dooks wrote: > Package: linux-image-5.15.0-2-amd64 > Version: 5.15.5-2 > > Dmesg output when mmc card is inserted: > > > [137854.880467] mmc0: cannot verify signal voltage switch > [137855.004774] mmc0: new ultra high speed SDR104 SDHC card at

Bug#1007797: [Pkg-rust-maintainers] Bug#1007797: debcargo: Cannot represent prerelease part of dependency: iso7816

it should work if you explicitly allow it, see debcargo.conf.toml.example[0]: # Whether to allow prerelease deps, by rewriting these to the released version. # This should only be enabled for certain crates if really necessary, and first # you should check that they can actually build when

Bug#1005203: [Pkg-rust-maintainers] Bug#1005203: rustc: Please package at least version 1.57

On February 9, 2022 12:54 am, Mike Hommey wrote: > Package: rustc > Version: 1.56.0+dfsg1-2 > Severity: important > > Dear Maintainer, > > Firefox 97 requires rustc 1.57 (released 2 months ago), which is not yet > available in unstable. see

Bug#912717: possible upstream fix

according to one of our downstream users (https://bugzilla.proxmox.com/show_bug.cgi?id=2333) > the problem is fixed by git commit > https://github.com/samba-team/samba/commit/47466691ccb9f73677dc43de3206e365f2daf611. > samba release 4.10.13+ should contain this fix so bullseye should already

Bug#1004430: tar: `numeric-owner` not honored for ACLs

Package: tar Version: 1.34+dfsg-1 Severity: normal Tags: patch X-Debbugs-Cc: f.gruenbich...@proxmox.com filed upstream (with similar patch): http://savannah.gnu.org/bugs/?61934 ACL entries store references to numeric uids/gids. on platforms that have libacl, use `acl_to_any_text` to generate ACL

Bug#1051318: ITP: rust-xtr -- Gettext helper for Rust crates

Package: wnpp Severity: wishlist Owner: Fabian Grünbichler X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org, debian@fabian.gruenbichler.email * Package name: rust-xtr * Version : 0.1.9 * Upstream Contact: Olivier Goffart * URL : https

  1   2   >