On Mon 2018-11-26 08:42:20 +0100, Werner Koch wrote:
> On Sun, 25 Nov 2018 22:22, csm...@debian.org said:
>> It seems it needs the SRV record and fails wrong without it.
>> Checking on the same system looking up that SRV record I get the
>> expected NXDOMAIN error.
>
> That seems to be a Debian
Package: terminator
Version: 1.91-1
Severity: normal
Launch terminator from another terminal emulator so that stderr is
visible.
click the upper-left-corner button to get a dropdown menu and then
click "Insert terminal number".
Nothing happens in the terminator window, but the following is
On Wed 2018-11-21 17:12:23 +0200, Adrian Bunk wrote:
> Fails:
> LC_ALL=C dpkg-buildpackage
>
> Builds:
> LC_ALL=C.UTF-8 dpkg-buildpackage
>
> Python 3.7 has a workaround for C locale.
>
> In debian/rules add:
> export LC_ALL=C.UTF-8
thank you, Adrian!
I've lost count of how many beers i owe you,
Control: tags 914269 + confirmed help
I see this error in my cowbuilder instance as well, but i don't see the
error when i build by hand on a buster/sid system.
more confusingly, this error crops up in python3.6, but not when
using python3.7 -- so i don't understand what the issue is, or how to
On Mon 2018-10-29 11:27:51 -0400, Daniel Kahn Gillmor wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Daniel Kahn Gillmor
>
> * Package name: google-i18n-address
> Version : 2.3.2
> Upstream Author : Mirumee Software
> * URL : https://g
Hi Simon--
On Mon 2018-11-12 16:48:29 +, Simon McVittie wrote:
> I recently added a new point of variation (#901473) to Debian's
> reproducible builds infrastructure: the first build is done in a
> traditional Debian system with separate /bin and /usr/bin, while the
> second is done with
-10-05 16:43:38.0 -0400
+++ gnupg2-2.1.18/debian/changelog 2018-11-18 12:20:52.0 -0500
@@ -1,3 +1,9 @@
+gnupg2 (2.1.18-8~deb9u4) stretch; urgency=medium
+
+ * Avoid crash when importing without a TTY (closes #913614)
+
+ -- Daniel Kahn Gillmor Sun, 18 Nov 2018 12:20:52 -0500
Control: tags 913614 + patch
The attached patch resolves the issue, and also introduces a test to
ensure that the problem is (and remains) fixed.
--dkg
>From 2e3b6845ea6c4762e86d281bcf83bf0e84315d8c Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Fri, 16 Nov 2018 00:38:40 -0
On Thu 2018-11-15 14:45:10 +0100, Fabian Grünbichler wrote:
> indeed, after removing any and all wireguard.ko from the usual search
> paths:
>
> # new_version=$(modinfo -F version wireguard 2>/dev/null || echo 'invalid')
> # echo $new_version
> invalid
> # cat /sys/module/wireguard/version
>
On Wed 2018-11-14 21:14:08 +0100, Fabian Grünbichler wrote:
> Maybe going with the meta package is a good idea then - especially since
> it allows us a cheap 'opt-in' for the reloading behaviour.
yep, i'm leaning in this direction too.
> I was thinking about changes to the wg-quick template unit
Package: hopenpgp-tools
Version: 0.21.2-2
Severity: normal
D368FE75E1AA92F6E49B99D26C1F1EDECC50FA53 is a signing-capable ed25519
subkey of 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9.
"hokey lint" complains "unknown pubkey algorithm type 22 unknown"
hopenpgp-tools should learn about ed25519!
This looks great and very thorough, Fabian. thank you! I'm trying to
reason about some of the details, to see how we can simplify things
further. Some questions:
* why put the module reloading in wireguard-tools.postinst and not in
wireguard.postinst ? There's no guarantee that
From 9fb2b324269af6eb1fe66e4f135611776d39b10c Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Fri, 2 Nov 2018 11:26:09 -0400
Subject: [PATCH] python: auto-generate versioned python module setup.py
---
configure.ac | 3 ++-
python/Makefile.am | 1 +
python/setup.py.in | 32
Control: tags 913582 + confirmed upstream
Control: forwarded 913582 https://dev.gnupg.org/T4251
Thanks for catching this, Simon!
On Mon 2018-11-12 16:48:29 +, Simon McVittie wrote:
> * Have two systems/chroots/containers, one with merged /usr (/bin is a
> symlink to /usr/bin) and one
On Tue 2018-11-13 21:53:12 +0100, Xavier wrote:
> Note that if there is a "git origin" that points to upstream repo, uscan
> will use it instead of creating a temporary "git clone". It is more
> efficient I think
hm, too bad. i use "upstream" as the name of my upstream git repos,
since as often
Hi Xavier--
On Tue 2018-09-25 23:45:18 +0200, Xavier wrote:
> I just implement a git-tag-signature-verify feature [1] to fix #827065:
> just to add "pgpmode=gittag" in opts.
> I think it fixes this issue too. If you agree, I'll merge it.
Thanks for this! I finally got around to testing out your
Package: devscripts
Version: 2.18.7
Severity: normal
When uscan is verifying signatures, it currently uses gpgv everywhere
except when pgpmode=self. in that case, it uses gpg, presumably in
order to extract the source tarball.
however, modern GnuPG (since 2.1.16, so including debian stretch)
I ran into the same issue on a powerpc installation.
On Mon 2018-11-12 17:16:10 +0100, Christoph Martin wrote:
> please try for me to change the value in line 271 from 65536 to a higher
> value which is high enough for your sources.list .
When i changed from 65536 to 655360, the
On Mon 2018-11-12 17:02:40 +0100, Elmar Stellnberger wrote:
> Now I have removed pcscd with apt-get remove and see it works now on my
> Debian 9 machine.
glad to hear that it's working reliably now! I'm closing this bug
report since it sounds like it's resolved, but feel free to re-open it
if
Hi Elmar--
On Sun 2018-11-11 15:54:42 +0100, Elmar Stellnberger wrote:
> The problem is that gnupg does not recognize my gpg-card if I insert it
> via the Gemalto PC-card reader; if I use the integrated reader it works.
> The problem only occurs with Debian GNU Linux 9. The USB reader still
>
On Wed 2018-10-03 17:20:02 +0200, Moritz Mühlenhoff wrote:
> This is dead upstream and broken even in ESR, let's remove it
> from the archive?
agreed, i've just filed a RM/ROM bug report (#913215) on
custom-tab-width.
--dkg
Package: ftp.debian.org
Severity: normal
Control: affects -1 src:custom-tab-width
Control: block 906843 with -1
Since Quantum made it to Firefox ESR, the custom-tab-width browser
extension is no longer useful. https://bugs.debian.org/906843 notes
that the package isn't currently useful either.
On Mon 2018-11-05 00:43:16 -0500, Scott Kitterman wrote:
> I've asked for a give back on knot-resolver for armhf. If that succeeds, I
> think it will migrate.
thanks! looks like the giveback succeeded :)
Control: tags 908755 - moreinfo
On Sun 2018-11-04 11:54:48 -0500, Scott Kitterman wrote:
> There is a rdepend that should be addressed too:
>
> Checking reverse dependencies...
> # Broken Build-Depends:
> hddemux: knot-resolver
>
> Dependency problem found.
>
> Once that's resolved, please remove
On Sun 2018-11-04 11:26:26 +1100, Dmitry Smirnov wrote:
> Package: getmail
> Version: 5.6-1
> Severity: normal
>
> getmail no longer works after dist-upgrade to Buster:
>
>
> SimplePOP3SSLRetriever:{USER}@iinet.net...@mail.iinet.net.au:995:
> {USER}@iinet.net.au: socket error ([SSL:
Control: tags 912210 + confirmed
Control: found 912210 2.7.2-2~bpo9+1
Control: found 912210 2.7.3-1
On Mon 2018-10-29 10:35:10 +, Peter Palfrader wrote:
> | Configuration file '/etc/knot/knot.conf'
> | ==> Modified (by you or by a script) since installation.
> | ==> Package distributor has
bian/ispell) does that, i think.
If someone really wants to keep sq, perhaps they could speak up here?
--dkg
>From 941518e0e8be8cf842a435f68c6ea66ec73c3264 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Wed, 31 Oct 2018 10:29:51 -0400
Subject: [PATCH] Stop shipping sq and unsq (
On Mon 2018-10-29 19:31:07 +, Adam D. Barratt wrote:
> Please go ahead.
this is now uploaded, and it's in stable-new.
--dkg
On Tue 2018-10-30 11:03:02 -0700, Sunil Mohan Adapa wrote:
> We have been setting the TMPDIR to
> /var/lib/monkeysphere/authentication/tmp/ in FreedomBox for some time
> now to work around the problem. So, I think, in general, this solution
> is fine. However, perhaps we could conservatively use
On Mon 2018-10-29 12:56:48 -0700, Sunil Mohan Adapa wrote:
> Attached the patches do this with /usr/bin/env (better to have full
> path?). I have retested all invocations again.
thanks! I've applied your patch on the master branch upstream, and then
also changed /usr/bin/env to just "env" -- no
Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor
* Package name: google-i18n-address
Version : 2.3.2
Upstream Author : Mirumee Software
* URL : https://github.com/mirumee/google-i18n-address
* License : BSD
Programming Lang: Python, JSON
On Mon 2018-10-29 14:07:33 +0100, har...@a-little-linux-box.at wrote:
> It seems the problem with the initscript is my chrooted nsd setup, if
> PIDFILE is not defined in the initscript it automatically gets set to
> /var/run/$NAME.pid (which is not true in a chrooted setup). So I guess
> adding
Hi Sunil--
thanks for all your work on this. i think we're heading for a
significant improvement here :)
On Mon 2018-10-29 00:35:53 -0700, Sunil Mohan Adapa wrote:
> runuser does not seem to depend on the user's shell. It simply runs a
> given process under that user's id (with a different PAM
On Sun 2018-10-28 21:58:55 +, Adam D. Barratt wrote:
> I don't have any objections if you want to upload already, but it won't
> get accepted into p-u from stable-new until it's had the d-i ack.
OK, it's uploaded now, in stable-new, waiting for the d-i ack.
thanks for your work on the stable
On Sun 2018-10-28 10:58:17 -0400, Daniel Kahn Gillmor wrote:
> On Sat 2018-10-27 16:47:27 +0100, Adam D. Barratt wrote:
>> Are you planning on handling the enigmail upload as well? I can't see
>> an open p-u bug for it so, given the timings, would suggest that start
>> getti
On Sat 2018-10-27 16:47:27 +0100, Adam D. Barratt wrote:
> As it turns out, that was quite a lot of noise indeed - about 1/3 of
> the ~3300 line diff, from my visual scan-and-chop. Apologies for the
> delay, but I've finally managed to carve out a block of time to handle
> this.
apologies for the
Control: retitle 890468 lintian: source-is-missing false positive when
d/missing-sources/foo has no known suffix
On Fri 2018-10-26 14:52:38 -0400, Chris Lamb wrote:
> Chris Lamb wrote:
>
>> Thanks for the bug report but unfortunately I think I'm either
>> parsing the problem incorrectly or think
Package: openssh-client
Version: 1:7.9p1-1
Severity: wishlist
/usr/lib/openssh/ssh-keysign is one of only a few setuid programs left
on a modern system. It looks like it is *probably* relatively safe --
not enabled by default due to configurations set in
/etc/ssh/ssh_config, checking that config
Is it possible that libspice-client-glib-2.0-8 should merely Recommend:
spice-client-glib-usb-acl-helper, rather than Depend: ing on it?
spice-client-glib-usb-acl-helper is one of the few setuid binaries on
debian systems, and if it isn't installed, it seems like the attack
surface would be
On Fri 2018-08-17 15:48:32 +, Harald Jenny wrote:
> the stop action of the current initscript takes a long time to stop
> the daemon, please find attached a patch which makes stopping faster.
Do you know why it takes a long time to stop? without this change, it's
using the standard
Control: tags 911907 + confirmed
Hi Sunil--
thanks for catching this, and for proposing a fix.
On Thu 2018-10-25 18:20:11 -0700, Sunil Mohan Adapa wrote:
> We faced a similar issue with quassel-core package recently and the
> maintainer fixed it by using runuser instead of su. From what I
Hi Tiziano--
thanks for following up here! I'm closing the bug report as you
recommended, but i wanted to add a little more followup in case someone
else reads this.
On Thu 2018-10-25 13:03:12 +0200, Tiziano Zito wrote:
> It has nothing to do with pinentry. Given that I have a system with
Control: affects 873499 src:gnupg2
On Mon 2017-08-28 14:36:20 +0200, Yuri D'Elia wrote:
> 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
Package: php-crypt-gpg
Version: 1.6.0-1
Severity: normal
Control: affects -1 src:gnupg2
I would like to be able to remove the gnupg2 binary package from
debian eventually, because we ship modern GnuPG as the gnupg package.
/usr/bin/gpg2 is a legacy symlink supplied by the gnupg2 dummy
package.
Package: openpgp-applet
Version: 1.1-1
Severity: normal
Control: affects -1 src:gnupg2
I would like to be able to remove the gnupg2 binary package from
debian eventually, because we ship modern GnuPG as the gnupg package.
/usr/bin/gpg2 is a legacy symlink supplied by the gnupg2 dummy
package.
Hi Tiziano--
On Wed 2018-10-24 17:24:33 +0200, Tiziano Zito wrote:
> pinentry-gnome3 (but also pinentry-gtk-2) does not open a window anymore to
> ask for a passphrase. If run from terminal it shows:
>
> No Gcr System Prompter available, falling back to curses
> OK Pleased to meet you
>
> It was
Package: apt
Version: 1.4.8
Severity: minor
Over in https://bugs.debian.org/909000,
On Mon 2018-10-22 08:28:50 -0400, Fabián Rodríguez wrote:
> This also fails in a clean Stretch install:
>
> # apt install enigmail
> Reading package lists... Done
> Building dependency tree
> Reading state
Hi Adam--
On Tue 2018-10-23 16:18:05 +0100, Adam D. Barratt wrote:
> Sure, but that's not what I said. My distinction was between including
> the gnupg update in the point release versus pushing it more urgently
> via stable-updates. I never implied the updates shouldn't be released at
> all.
On Tue 2018-10-23 20:00:06 +0100, Adam D. Barratt wrote:
> From discussions elsewhere, I understand that the "raw" upstream
> enigmail - i.e. installed via upstream's addons service - is actually
> already compatible with the new Thunderbird version, and the problem
> only affects the Debian
On Sun 2018-10-21 11:47:51 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Wed, 2018-10-17 at 11:13 -0400, Daniel Kahn Gillmor wrote:
>> Please consider an update to publicsuffix in debian stretch.
>>
>> This package reflects the state of the network
Control: clone 909000 -2
Control: retitle -2 apt: error message "apt install enigmail" failure is
misleading
Control: reassign -2 apt 1.4.8
Control: severity -2 minor
On Mon 2018-10-22 08:28:50 -0400, Fabián Rodríguez wrote:
> This also fails in a clean Stretch install:
>
> # apt install
Thanks to Adam for your ongoing work on the stable releases!
I just wanted to clarify a few points here.
On Tue 2018-10-23 08:57:08 +0100, Adam D. Barratt wrote:
> An issue is that the gnupg update itself doesn't really qualify for
> stable-updates any more than it qualifies for
Source: libgpg-error
Version: 1.32-2
Severity: normal
Control: tags -1 + help confirmed
when trying to build from source with "gbp buildpackage -A" or
"dpkg-buildpackage -A", the build fails, terminating the following
error message:
-
[…]
make[5]: Leaving directory
Package: wnpp
Severity: wishlist
Control: block 911189 by -1
Control: affects src:gpgme1.0
* Package name: node-chai
Version : 4.1.2
Upstream Author : Chai development team
* URL : https://www.chaijs.com/
* License : MIT
Programming Lang: Javascript
Source: node-webpack
Version: 3.5.6-3
Severity: wishlist
Control: affects -1 src:gpgme1.0
Control: block 911189 by -1
https://github.com/webpack/webpack/archive/v4.21.0.tar.gz is available
upstream.
The debian package for webpack has not been updated since 2018-03-08.
I'm trying to use webpack
On Tue 2018-10-09 19:15:09 +, Adam D Barratt wrote:
> The upload referenced by this bug report has been flagged for acceptance into
> the proposed-updates queue for Debian stretch.
>
> Thanks for your contribution!
>
> Upload details
> ==
>
> Package: publicsuffix
> Version:
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 publicsuffix
Please consider an update to publicsuffix in debian stretch.
This package reflects the state of the network, and keeping it current
is useful for
Package: src:gpgme1.0
Version: 1.12.0-1
Severity: wishlist
as of gpgme 1.12.0-1, GPGME ships a javascript binding that works with
so-called "Native Messaging" in both chrome and firefox.
we should ship this as a separate binary package, along with the
appropriate extension manifests.
for more
On Tue 2018-10-16 12:05:33 +0200, Carsten Schoenert wrote:
> yes, the problem here is Enigmail, not Thunderbird! But I don't see that
> this as a vulnerability per se from a security perspective.
> And you still can install the Mozilla AddOns manually into FF and TB.
> It's a loosing of comfort
Hi release team, security team:
over in #910398, i wrote:
On Fri 2018-10-05 17:48:10 -0500, Daniel Kahn Gillmor wrote:
> I'd like to update the version of GnuPG in debian stable with a series
> of targeted bugfixes (most of which are backported from upstream).
>
> There are four c
Hi Wookey--
On Mon 2017-07-24 18:58:48 +0100, Wookey wrote:
> This small patch adds support for the arm64ilp32 architecture.
I've just pushed this upstream at
https://dev.gnupg.org/rEa3f4e8838036a14e87cca811e40c9f670f152fcd
sorry for the delay, and thanks for contributing another
On Fri 2018-10-12 12:36:12 +0200, Sven Joachim wrote:
> Control: tags -1 + patch
thank you, Sven and Helmut for your attention to this kind of detail.
I'm preparing an upload with these changes.
Y'all rock!
--dkg
On Thu 2018-10-11 13:02:18 +, Georg Faerber wrote:
> Although I'm not using Thunderbird and Enigmail myself, I've rolled out
> this fix to a couple of friends on Monday. So far, they're pretty happy,
> no problems found.
thanks for this testing and feedback, Georg!
--dkg
Package: devscripts
Version: 2.18.6
Severity: normal
Control: affects -1 publicsuffix
I'd like to use a debian/watch file for the publicsuffix package like
this:
version=4
opts=mode=git,pretty=%cd,date=%Y%m%d.%H%M \
https://github.com/publicsuffix/list HEAD
however, the
0.7.8
ii svn-buildpackage 0.8.7
ii w3m0.5.3-36+b1
-- no debconf information
From 34f245c53570d9fd83dfa28db7727f314070fc11 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Wed, 10 Oct 2018 15:37:49 -0400
Subject: [PATCH
On Wed 2018-10-10 17:30:33 +0200, Narcis Garcia wrote:
> The good solution for this is to move Thunderbird 60 to
> stretch-backports instead of being at normal repository.
>
> Normal users will keep current Enigmail 2:1.9 , current Thunderbird 1:52
> and current GnuPG 2.1 and not unstable
On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real
On Mon 2018-10-08 16:05:39 +0200, W. Martin Borgert wrote:
>> In the meantime, for enigmail, i've pushed a debian/stretch branch into
>> salsa with commit id b6e978d64af1defdfed876b09c8a57acb796ad72 as
>
> Did you push? I can't find the id. I would like to test.
thanks for testing! it appears
On Sun 2018-10-07 19:46:38 +0200, Sofus Rose wrote:
> 0. systemd is set to a text startup target.
> 1. I login to a tty text console.
> 2. I run startx
I use this same workflow to start X11, and i don't have the problems
described.
> It may be worth noting that after my DE (Budgie) has started,
On Sat 2018-10-06 18:13:12 +0100, Adam D. Barratt wrote:
> On Thu, 2018-07-12 at 12:27 -0400, Daniel Kahn Gillmor wrote:
>> I've tried multiple times now to attach the debdiff to this bug
>> report,
>> and it continues to be rejected as spam by bugs.debian.org with this
>
On Sat 2018-10-06 18:13:12 +0100, Adam D. Barratt wrote:
> On Thu, 2018-07-12 at 12:27 -0400, Daniel Kahn Gillmor wrote:
>> I've tried multiple times now to attach the debdiff to this bug
>> report,
>> and it continues to be rejected as spam by bugs.debian.org with this
>
Package: cli-common-dev
Version: 0.9+nmu1
Severity: normal
Control: affects -1 src:gmime2.6
I'm trying to rebuild gmime2.6 with Rules-Requires-Root: no (see
/usr/share/doc/dpkg-dev/rootless-builds.txt.gz for more details).
When I do that, though, it yields the following error:
dh_makeclilibs
On Tue 2018-10-02 14:31:13 -0500, Daniel Kahn Gillmor wrote:
> I'm now working on figuring out what updates are needed to GnuPG in
> debian stable (stretch) to be able to get the enigmail test suite to
> pass. Hopefully they'll be minor, and comprehensible.
Turns out there were a h
Package: release.debian.org
User: release.debian@packages.debian.org
X-Debbugs-Cc: pkg-gnupg-ma...@lists.alioth.debian.org, secur...@debian.org
Usertags: pu
Tags: stretch
Severity: normal
Control: affects -1 src:gnupg2 enigmail
Control: block 909000 -1
I'd like to update the version of GnuPG
On Wed 2018-10-03 11:38:41 +0200, Jonas Meurer wrote:
> That's great news! Thanks a ton for working so hard on getting Enigmail
> 2.0 to run without OpenPGP.js. Will these changes be adapted upstream or
> will upstream keep using OpenPGP?
some of my changes are not upstreamable because i've
On Mon 2018-09-17 15:44:03 -0400, Daniel Kahn Gillmor wrote:
> * i subsequently discovered that the enigmail test suite was inadequate
>for the Autocrypt Setup Message -- i'm currently working on fixing
>that. (this is #908510)
I'm happy to report that the enigmail test su
Hi Steve--
On Fri 2018-09-28 17:28:07 -0700, Steve Langasek wrote:
> $ debsign -k01aa4a64 [...].changes
> Refusing to sign with short key ID '01aa4a64'!
> $ echo $?
> 1
> $
>
> Seriously?
Yep, seriously. Please specify the key you want to use unambiguously.
> What kind of collision attack
le to bypass the import screener by appending
> a crafted subkey to an arbitrary key:
>
>$ gpg --keyserver keyserver.ubuntu.com --recv-key
> 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9
>gpg: key CCD2ED94D21739E9: public key "Daniel Kahn Gillmor
> " imported
>gpg
Package: libreswan
Version: 3.25-2
Severity: wishlist
libreswan published version 3.26 a couple days ago. We should get it
packaged for debian.
--dkg
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The Libreswan Project has released libreswan-3.26
This is a
3 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Thu, 20 Sep 2018 01:31:58 -0400
Subject: [PATCH] irssi Provides: irssi-abi-XXX for safer plugin packaging
(Closes: #811445)
Inspired by
https://xorg-team.pages.debian.net/xorg/reference/dependencies.html,
Florian Schlichting proposed
On Sat 2018-09-15 09:09:58 +0300, Adrian Bunk wrote:
> It also needs a proper narrowly versioned dependency.
while irssi packaging doesn't release the ABI, i still want
irssi-plugin-xmpp to work for now. So I've added a (fairly brittle)
build-dep and runtime versioning limits to
Package: anbox
Version: 0.0~git20180821-1
Severity: wishlist
Tags: patch
Control: block -1 with 909156
https://bugs.debian.org/909156 is an RFP for packaging SwiftShader as
an independent library in debian.
If that was done, then i believe that something like the following
patch would enable the
happen.
Would anyone be interested in co-maintenance?
--dkg
commit b0b61117ca82e70e0c165c892a717b7f4f97a99f
Author: Daniel Kahn Gillmor
Date: Tue Sep 18 17:41:52 2018 -0400
debian has googletest
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 95766810..e8099
over in https://bugs.debian.org/909014, sergio asked for inclusion of
GnuPG's pinentry-efl in debian.
sergio wrote::
> On 17/09/2018 22:54, Daniel Kahn Gillmor wrote:
>
>> i hadn't heard from any debian users that this was desirable
>
> Hope pkg-e-de...@lists.alioth.d
Control: forcemerge 909000 909001
On Mon 2018-09-17 10:36:16 +0200, Pierre Dinh van wrote:
> Today, all my users have trouble reading their encrypted emails, because
> the last upgrade of thunderbird from security.debian.org on 16/09/2018 breaks
> enigmail (and a lot of other things).
>
> apt
Control: tags 909014 + moreinfo
On Mon 2018-09-17 15:21:06 +0300, sergio wrote:
> Please make a new binary packages with --enable-pinentry-efl for
> enlightenment.
thanks for your suggestion! I'd put off doing this because i hadn't
heard from any debian users that this was desirable.
do you
On Mon 2018-09-17 10:14:31 +0200, Jonas Meurer wrote:
> yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via
> security). This thunderbird version breaks enigmail (<< 2:2~), which
> leads to uninstallable/unusable Enigmail in Debian Stretch.
>
> May I suggest to backport Enigmail
Control: severity 772479 grave
I've got these packages installed:
ii irssi 1.1.1-1 amd64terminal based IRC client
ii irssi-plugin-xmpp 0.54-2 amd64XMPP plugin for irssi
and if i launch a new irssi installation and do:
/load xmpp
then it responds with:
Package: tracker.debian.org
Control: affects -1 src:knot-resolver
https://tracker.debian.org/pkg/knot-resolver shows:
RM: This package has been requested to be removed. normal
This package has been requested to be removed. This means that, when
this request gets
Package: ftp.debian.org
Severity: normal
Control: affects -1 knot-resolver
NOTE: this is just a request for removal of the knot-resolver binary
package on arm64. please do *not* remove the source package or any of
the other binary packages!
the knot-resolver binary fails on arm64 because of a
> Work is being done on dh_installsystemduser
> Some bits have already landed in init-system-helpers [1] and there is an
> open MR for debhelper [2].
> Once that MR lands in debhelper, picking a package like gpg-agent and
> converting it to the new helper might be a good idea to give it some
>
Package: enigmail
Version: 2:2.0.8-1
Severity: normal
Since the removal of OpenPGP.js from enigmail, the Autocrypt Setup
Message parsing and generation has been broken.
This was uncovered by upstream's improved test suite in version 2.0.8.
I'm working on fixing it.
--dkg
-- System
On Mon 2018-09-10 14:07:44 +0100, Simon McVittie wrote:
> It might be a reasonable middle ground for sockets and other
> auto-activation mechanisms to be statically enabled on the user bus, so
> that the services are not started eagerly, but are started on-demand?
For the record, this is what the
On Thu 2018-09-06 09:15:32 +0200, Sedat Dilek wrote:
> let's look at my current installed dkms kernel-modules and especially
> virtualbox-dkms and compare with wireguard-dkms.
[…]
> In my POV 'dkms status' should only show the upstream version.
> Special patched versions of *-dkms packages from
Control: tags 906019 + moreinfo
On Mon 2018-08-13 12:04:42 +0200, Sedat Dilek wrote:
> the version string for installed wireguard-dkms does not look correct to me.
> This should be "0.0.20180802" not "0.0.20180802-1".
I'm not convinced that this is correct. In the event that a
debian-specific
Package: docx2txt
Version: 1.4-1
Severity: normal
Subject: docx2txt fails on docx files which contain legitimate whitespace in
their XML
Package: docx2txt
Version: 1.4-1
Severity: normal
a .docx file is a PKZip container. each of its elements are XML files.
XML is generally allowed to have
On Fri 2018-08-31 19:53:42 -0400, Daniel Kahn Gillmor wrote:
> On the arm64 build daemons, kresd fails with the error:
>
> PANIC: unprotected error in call to Lua API (bad light userdata pointer)
>
> https://buildd.debian.org/status/fetch.php?pkg=knot-resolver=arm64=3.0.0
Package: knot-resolver
Version: 3.0.0-4
Tags: upstream, help
Control: affects -1 hddemux
On the arm64 build daemons, kresd fails with the error:
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
Package: knot-resolver
Version: 3.0.0-4
Tags: help
When running debian/tests/roundtrip on the armhf buildd arm-arm-01,
kresd fails with:
debian/tests/roundtrip: line 82: 19523 Bus error "$kresd"
"${kresd_args[@]}" "$d" 2> "$d/kresd.err"
The process doesn't even get to the
Package: src:requestpolicy
Version: 1.0.0~beta12.3+dfsg-1
Severity: wishlist
according to
https://github.com/RequestPolicyContinued/requestpolicy/releases a new
beta release has been available for nearly a year. In git
(https://github.com/RequestPolicyContinued/requestpolicy) there are
many new
901 - 1000 of 4321 matches
Mail list logo
