Bug#755544: notmuch-emacs: doesn't check gpg/pgp signatures by default

2016-02-08 Thread David Edmondson
On Tue, Jul 22 2014, David Bremner wrote: > Jameson Graef Rollins writes: > >> On Mon, Jul 21 2014, David Bremner wrote: >>> notmuch folks: it seems that in vagrant's message, and several others I >>> checked, it notmuch-crypto-process-mime==nil,

Bug#759646: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

2016-02-08 Thread David Edmondson
[Raking over history...] On Sat, Nov 29 2014, David Bremner wrote: > David Edmondson <d...@dme.org> writes: > >> On Tue, Sep 02 2014, Tomi Ollila wrote: >>> On Tue, Sep 02 2014, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: >>> >>>>

Bug#810784: [Gaudenz Steinlin] Bug#810784: should match email adress case insensitive when sending encrypted mail

2016-02-08 Thread David Edmondson
On Fri, Jan 15 2016, Daniel Kahn Gillmor wrote: > So where is the case-insensitive lookup happening? Is this a bug in > mml-mode, or in notmuch-emacs? It's caused by behaviour in mml2015.el (hence upstream). `mml2015-epg-check-user-id' uses `equal' to compare the recipient from the composition

Bug#810784: [Gaudenz Steinlin] Bug#810784: should match email adress case insensitive when sending encrypted mail

2016-02-09 Thread David Edmondson
On Mon, Feb 08 2016, David Edmondson wrote: > On Mon, Feb 08 2016, David Edmondson wrote: >> On Fri, Jan 15 2016, Daniel Kahn Gillmor wrote: >>> So where is the case-insensitive lookup happening? Is this a bug in >>> mml-mode, or in notmuch-emacs? >> >>

Bug#810784: [Gaudenz Steinlin] Bug#810784: should match email adress case insensitive when sending encrypted mail

2016-02-08 Thread David Edmondson
On Mon, Feb 08 2016, David Edmondson wrote: > On Fri, Jan 15 2016, Daniel Kahn Gillmor wrote: >> So where is the case-insensitive lookup happening? Is this a bug in >> mml-mode, or in notmuch-emacs? > > It's caused by behaviour in mml2015.el (hence upstream). > > `mml2

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

2020-12-08 Thread David Edmondson
On Friday, 2020-12-04 at 08:39:55 +02, Lars Wirzenius wrote: > As it happens, David Edmonson (dme), added to cc, has been working on > adding arm64 support for the grub plugin. Part of his changes is that the > grub plugin will know the target archietecure, and choose the right grub > .deb

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

2020-11-10 Thread David Edmondson
I've sent some patches to liw for vmdb2 to improve building a UEFI based arm64 image which can be seen here: https://git.sledj.net/dme/vmdb2/src/branch/devel/arm64 These should address the general problem of vmdb2 being able to build an arm64 image when grub is used, as long as UEFI is

Bug#1068337: mblaze(7) and debian/control refer to mless(1) and msort(1), but they are actually mblaze-less(1) and mblaze-sort(1) in Debian

2024-04-03 Thread David Edmondson
Package: mblaze Version: 1.1-1 Severity: minor Tags: patch X-Debbugs-Cc: d...@dme.org Dear Maintainer, When the Debian packaging build renames mless -> mblaze-less and msort -> mblaze-sort, it does not update the references in the mblaze manual page or package description. This is confusing! --

Bug#1068337: mblaze(7) and debian/control refer to mless(1) and msort(1), but they are actually mblaze-less(1) and mblaze-sort(1) in Debian

2024-04-03 Thread David Edmondson
Proposed patches are in the debian/sid branch at https://salsa.debian.org/dme/mblaze. -- Come down, come talk to me.

Bug#1041415: details

2024-04-23 Thread David Edmondson
tag 1041415 - upstream thanks Ultimately this fails because /proc is not available in the chroot. The version of libc in use *emulates* fchmodat() using /proc/self/fd rather than using the fchmodat system call. When /proc is provided in the chroot, the fchmodat emulation works successfully and

Bug#1040690: failure in a chroot

2024-04-23 Thread David Edmondson
The failure in a chroot looks the same as that described in #1041415, and is due to the lack of /proc. It doesn't seem related to the originally described problem. -- Time is waiting to explain, why refuse?

Bug#1059101: upstream bug

2024-04-24 Thread David Edmondson
tag 1059101 + upstream thanks This is bug#70122 upstream, and Braun & Eli are converging on a fix there. -- Any social occasion, it's hello, how do you do.

Bug#1069273: ITP: gnome-shell-extension-tactile -- Tile windows on a custom grid using your keyboard

2024-04-19 Thread David Edmondson
Package: wnpp Severity: wishlist Owner: David Edmondson X-Debbugs-Cc: debian-de...@lists.debian.org, d...@dme.org * Package name: gnome-shell-extension-tactile Version : 32 Upstream Contact: Per Thomas Lundal, https://gitlab.com/lundal * URL : https://gitlab.com

Bug#1041415: details

2024-04-23 Thread David Edmondson
I was not able to reproduce this failure. Is there anything interesting about the filesystem underlying the chroot used during the install? Is root able to write files with impunity in the relevant directories? Are you able to reproduce the failure? -- Time is waiting to explain, why refuse?

Bug#1017834: analysis

2024-04-23 Thread David Edmondson
The failure to build elpa-cider is caused by: > In toplevel form: > cider.el:218:1: Error: Wrong number of arguments: (3 . 4), 2 In the source, this corresponds to: > (define-obsolete-variable-alias 'cider-default-repl-command > 'cider-jack-in-default) In recent versions of emacs, the

Bug#1041415: details

2024-04-23 Thread David Edmondson
Ah, by specifically using a chroot rather than a systemd-nspawn container, I *am* able to reproduce the failure. Off to debug... -- I'm not living in the real world, no more, no more.

Bug#1041415: details

2024-04-23 Thread David Edmondson
tag 1041415 + upstream thanks The error message: >>Error occurred processing /usr/share/emacs/site-lisp/debian-startup.el: File >>error (("Doing chmod" "Operation not supported" >>"/usr/share/emacs/site-lisp/debian-startup.elcFx8oFi")) comes from the emacs byte compiler. Tracing through the

Bug#1070189: ITP: gnome-shell-extension-happy-appy-hotkey -- Hotkey application focus / launcher for GNOME Shell

2024-05-01 Thread David Edmondson
Package: wnpp Severity: wishlist Owner: David Edmondson X-Debbugs-Cc: debian-de...@lists.debian.org, d...@dme.org * Package name: gnome-shell-extension-happy-appy-hotkey Version : 8 Upstream Contact: Jan Ouwens * URL : https://github.com/jqno/gnome-happy-appy-hotkey

Bug#693792: ITP: ocproxy -- lwip based proxy for openconnect

2012-11-20 Thread David Edmondson
Package: wnpp Severity: wishlist Owner: David Edmondson d...@dme.org * Package name: ocproxy Version : 0.9 Upstream Author : David Edmondson d...@dme.org * URL : http://dme.org/ocproxy * License : BSD Programming Lang: C Description : lwip based proxy

Bug#692413: proposed fix

2012-11-21 Thread David Edmondson
review carefully and give relevant feedback! From bc568d2e7158b27fd49e55217720c340a7532100 Mon Sep 17 00:00:00 2001 From: David Edmondson d...@dme.org Date: Tue, 20 Nov 2012 13:49:32 + Subject: [PATCH] Disconnect any active links when the daemon terminates. --- debian/changelog

Bug#692413: proposed fix

2012-11-21 Thread David Edmondson
On Wed, Nov 21 2012, David Paleino wrote: On Wed, 21 Nov 2012 13:29:59 +, David Edmondson wrote: The wicd daemon doesn't currently disconnect any active links when it terminates. Doing so results in wpa-supplicant being correctly stopped. Attached is a proposed patch (I've also uploaded

Bug#693914: RFS: ocproxy/1.20121120160713-2 ITP

2012-11-21 Thread David Edmondson
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package ocproxy. It is my first Debian package, so please review carefully. * Package name: ocproxy Version : 1.20121120160713-2 Upstream Author : David Edmondson d

Bug#702230: conkeror: xulrunner 19.0 should be found automatically

2013-03-04 Thread David Edmondson
Package: conkeror Version: 1.0~~pre+git120901-1 Severity: normal Dear Maintainer, xulrunner version 19.0 is available in the Debian experimental repository, yet the /usr/bin/conkeror script looks for versions only up to 17.0. 19.0 has some improvements over 10.0 that is included in

Bug#716777: acpi-support: acpi-support depends on acpi-fakekey on all archs, but acpi-fakekey is not built for all archs

2013-07-12 Thread David Edmondson
Package: acpi-support Severity: normal Dear Maintainer, * What led up to the situation? I want my ARM Chromebook to suspend on lid close, hence want to install acpi-support so that I can enable suspend on lid close in /etc/default/acpi-support. * What exactly did you do

Bug#716902: flash-kernel: [RFC PATCH] samsung arm chromebook support

2013-07-15 Thread David Edmondson
On Sun, Jul 14 2013, Shawn Landden wrote: I am working on getting the Samsung ARM Chromebook supported by the Debian installer. Excellent! I'm curious about: +Part-Kernel: /dev/mmcblk0p6 On my Chromebook partition 6 is KERN-C, but it is only a single sector: : wowbagger; sudo cgpt show

Bug#716902: flash-kernel: [RFC PATCH] samsung arm chromebook support

2013-07-16 Thread David Edmondson
On Mon, Jul 15 2013, Shawn wrote: On Mon, Jul 15, 2013 at 5:41 AM, David Edmondson d...@dme.org wrote: On Sun, Jul 14 2013, Shawn Landden wrote: I am working on getting the Samsung ARM Chromebook supported by the Debian installer. +Part-Kernel: /dev/mmcblk0p6 On my Chromebook partition

Bug#716902: flash-kernel: [RFC PATCH] samsung arm chromebook support

2013-07-16 Thread David Edmondson
On Tue, Jul 16 2013, Shawn wrote: Are you aware of any restrictions in how the internal flash may be partitioned? If, for example, I was happy to dedicate the internal flash to Debian, is there any reason not to simply have three partitions: - nv-uboot - /boot - root ? I think

Bug#716902: flash-kernel: [RFC PATCH] samsung arm chromebook support

2013-07-18 Thread David Edmondson
On Thu, Jul 18 2013, Ian Campbell wrote: On Sun, 2013-07-14 at 05:35 -0700, Shawn Landden wrote: +# /proc/cpuinfo contains Hardware : SAMSUNG EXYNOS5 (Flattened Device Tree) and therefore this: +Machine: Google Snow Comes from /proc/device-tree/model I guess/hope? That's

Bug#716902: flash-kernel: [RFC PATCH] samsung arm chromebook support

2013-07-18 Thread David Edmondson
On Thu, Jul 18 2013, Ian Campbell wrote: On Thu, 2013-07-18 at 10:10 +0100, David Edmondson wrote: On Thu, Jul 18 2013, Ian Campbell wrote: On Sun, 2013-07-14 at 05:35 -0700, Shawn Landden wrote: +# /proc/cpuinfo contains Hardware : SAMSUNG EXYNOS5 (Flattened Device Tree

Bug#716777: acpi-support: acpi-support depends on acpi-fakekey on all archs, but acpi-fakekey is not built for all archs

2014-06-18 Thread David Edmondson
On 18 Jun 2014, at 14:45, Michael Meskes mes...@debian.org wrote: The next version of the package will not depend on acpi-fakekey but only recommend it. Would that be good enough for you as a solution? Yes, thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#764501: wmctrl: add a 'minimize' option

2014-10-08 Thread David Edmondson
Package: wmctrl Version: 1.07-7 Severity: wishlist Dear Maintainer, It would be wonderful to have a minimize option to wmctrl. This would toggle the iconified state of the indicated window. A patch to implement iconify is available in a git repository at git://make-linux.org/tools/wmctrl.git

Bug#759646: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

2014-11-30 Thread David Edmondson
On Sat, Nov 29 2014, David Bremner wrote: David Edmondson d...@dme.org writes: On Tue, Sep 02 2014, Tomi Ollila wrote: On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 08/30/2014 03:37 AM, Jani Nikula wrote: I'm inclined to think this is a bug in message-mode. I

Bug#759646: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

2014-11-30 Thread David Edmondson
On Mon, Dec 01 2014, David Bremner wrote: David Edmondson d...@dme.org writes: I'm a little torn what to do here. On the one hand the upstream change fixes the bug as reported. On the other hand, if something corrupts the #secure tag (e.g., by deleting a letter), then the message is still