Bug#1067303: trash-cli in Debian: test problems again

ook and prepare a new release into Sid recently? If not, > would you mind a NMU into DELAYED/15 with the fix included? I'll take a look Today. I'm otherwise happy for NMUs, I'm on the Low Threshold NMU list. Best wishes, --  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#1067303: trash-cli in Debian: test problems again

ll as the same for the Debian packaging layer (we've had several Debian/Python build integrations over the years too). Best wishes, --  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#1004693: vfs_fruit module is in the binary package samba-vfs-modules

.  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#855837: golang-petname: Do not include in stretch at request of maintainer

orphaning. Best wishes, --  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#969901: torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed

Package: torbrowser-launcher Version: 0.3.2-11~bpo10+1 Severity: serious Justification: Policy 3.5 There's a few things going on in this session, but this bug report is about the last backtrace in particular: $ torbrowser-launcher Tor Browser Launcher By Micah Lee, licensed under MIT version

Bug#936146: archivemail - Python 3 porting

I use it. Thanks, --  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#855837: closing 855837

# stetch shipped ages ago close 855837 thanks -- 👱🏻Jonathan Dowland ✎ j...@dow.land 🔗https://jmtd.net

Bug#936146: archivemail - Python 3 porting

the older of two different APIs provided by the python "mailbox" library, and only the newer one was carried forward to Python 3. So moving away from that older API is a big part of the work. --  Jonathan Dowland ✎j...@debian.org  https://jmtd.net

Bug#950926: ember: Using packages to install "snap" packages is not a correct use of the packaging system

installing into flatpaks, rather than consuming from them) --  Jonathan Dowland  https://jmtd.net

Bug#950791: neomutt: missing debian/copyright entries for autosetup/*

Some initial work on this:

Bug#950791: neomutt: missing debian/copyright entries for autosetup/*

ULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages neomutt is related to: ii neomutt 20180716+dfsg.1-1 -- no debconf info

Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop

nal Debian conservative, when-its-ready approach would be the distribution status quo (Xorg), but I recognise the concerns about the proposed patch, further work needed, lack of testing etc.; and those are not issues I think I can resolve alone. -- Jonathan Dowland

Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop

Hi Andrew So far as I am aware there is still radio silence from active GNOME packaging team members regarding this issue. No comment yet on the patch I adapted, positive or negative; this bug (#927667) remains at an RC severity. I've not yet read all the thread that Samuel linked to[1] but it

Bug#903635: This is RC; breaks unrelated software

cessary chain DOCKER-USER creation, which I can reproduce). I should have filed a separate issue really, sorry. I've cloned now. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄

Bug#903635: docker.io: use of iptables-legacy is incompatible with nftables-based iptables

this week. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop

reassign 927667 gdm3 tags 927667 +patch thanks On Fri, May 10, 2019 at 10:26:07AM +0100, Jonathan Dowland wrote: Two ways of resolving this are: Either the default GNOME3 session in Debian switched back to Xorg, or the default desktop session is switched away from GNOME; but I would much prefer

Bug#903635: docker.io: use of iptables-legacy is incompatible with nftables-based iptables

. Will the patch in #2339 address the specific issue of what happens on package install? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄

Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop

, that the people doing the work should decide. Mostly agree :-) -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄

Bug#903635: This is RC; breaks unrelated software

On Wed, Apr 24, 2019 at 08:04:43PM +0100, Jonathan Dowland wrote: Installing docker.io changed my FORWARD chain policy to DROP, breaking networking for unrelated virsh-based VMs that I had installed on the machine at the time. This matches exactly the text for severity: serious. Sorry

Bug#818366: synaptic: fails to start under Wayland

. If the new display technology for Buster doesn't work with long-established and popular packages in the archive, shouldn't the default display technology for Buster be reverted back to the current one? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄

Bug#924473: Corrected path

On Sun, Mar 17, 2019 at 07:09:52PM +0100, Bruno Kleinert wrote: Hi Jonathan, please find attached a debdiff that updates the path to the manpage. Thanks for this, I will endeavour to apply and upload Tomorrow (hit a snag locally, my sbuild environment hath borken)

Bug#911762: trash-cli: FTBFS - segmentation fault during test phase

Source: trash-cli Version: 0.12.9.14-2.1 Severity: serious FTBFS as per attached. sbuild fails too I'm hoping this is cured by the new upstream version and/or tightening a python version, and I'm going to attempt to fix it. -- System Information: Debian Release: 9.5 APT prefers stable APT

Bug#870635: mutt package is not using the official mutt tarball

.org/cgi-bin/bugreport.cgi?bug=866366 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866366#24 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Bug#870635: mutt package is not using the official mutt tarball

t;vanilla" mutt if they wanted to. -- Jonathan Dowland

Bug#855837: golang-petname: Do not include in stretch at request of maintainer

should include this library in Stretch. -- Jonathan Dowland signature.asc Description: Digital signature

Bug#839486: lhasa: FTBFS: Tests failures

On Tue, Oct 11, 2016 at 12:46:46PM +0100, James Cowgill wrote: > Control: tags -1 patch Thanks for looking at this! -- Jonathan Dowland signature.asc Description: Digital signature

Bug#706909: fixed in smartmontools 6.1+svn3812-1

On Sat, Oct 03, 2015 at 06:57:31PM +0200, Paul Wise wrote: > This isn't the way to fix this issue, the current mechanisms still lead to > drivedb.h from the package being overwritten by downloaded data. Thedrivedb.h > file should be shipped in the deb in /usr not /var. At package install/update >

Bug#785122: chocolate-doom: includes licence-incompatible GPLv3 code

Package: chocolate-doom Version: 2.1.0-1 Severity: serious Justification: license issue Chocolate-doom includes code taken from GnuPG, which is GPLv3, whereas chocolate-doom is GPLv2 (or later). Upstream have fixed this by replacing the AES implementation with one from the kernel. See

Bug#724043: archivemail: FTBFS: Test failure

Hi Nikolaus, On Sun, Nov 24, 2013 at 09:35:12PM +0100, Nikolaus Schulz wrote: But yes, it's a bug, and the fix is in fact trivial, it's just that my coding infrastructure was broken until today. Did you manage to write up a fix for this? If not I'll work on one. Thanks -- Jonathan Dowland

Bug#750382: ~ Bug#750382: works for me on mips

=lhasaarch=i386ver=0.2.0%2Bgit-2stamp=1403473868 [2] mips - https://buildd.debian.org/status/fetch.php?pkg=lhasaarch=mipsver=0.2.0%2Bgit-2stamp=1403477942 -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#750382: thanks for the prod

Thanks for pointing this out; I think I noticed back when they failed but forgot. Today I dusted off some build environments but can't reproduce on i386 or amd64 yet. I'll keep looking. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#724551: squishyball: FTBFS: syntax error near unexpected token `vorbisfile,'

Hi, On Tue, Sep 24, 2013 at 09:42:30PM -0400, Aaron M. Ucko wrote: Please declare a build dependency on pkg-config and confirm via pbuilder or the like that you haven't missed any others. Thanks for catching. How embarrassing. I see that -1 failed too, but as an experimental package nobody

Bug#722438: qtscrob: FTBFS - manpage compression race in parallel builds

On 11 Sep 2013, at 03:47, Aaron M. Ucko u...@debian.org wrote: Given that all three builds ran in parallel (with -j6 or -j8), I suspect a race condition. Could you please take a look? Urgh. I hit this in the middle of preparing the package but it went away towards the end so I forgot about

Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning

On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam In my case I don't think so- it's built into the frame of my laptop screen. -- To UNSUBSCRIBE, email to

Bug#696727: cheese does not start with Gtk-Warning

On Thu, Mar 28, 2013 at 11:13:34AM +0100, John Paul Adrian Glaubitz wrote: How about unloading the kernel module then? I guess it's probably an UVC camera, so modprobe -r uvcvideo should do the trick for most cameras (as most of them are UVC). Thanks for the tip. It is indeed uvcvideo, and

Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)

I've just noticed that cheese is busy looping and mallocing whilst it's seemingly doing nothing: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 18958 jon 20 0 7513m 6.2g 3236 R 92.1 80.0 20:03.57 cheese -- To UNSUBSCRIBE, email to

Bug#696727: cheese does not start with Gtk-Warning

On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote: UI (No device found). Interesting stuff. I'm going to try splicing some debug statements into the code to see at what point it reaches and whether that helps get any further. I've poked around a little, attached is a backtrace

Bug#696727: cheese does not start with Gtk-Warning

severity 696727 important thanks (Downgrading since no evidence that it fails for the majority) On 28 Mar 2013, at 18:56, Emilio Pozuelo Monfort po...@debian.org wrote: After that I'd try with another tool that doesn't use gstreamer, then we can pinpoint whether this is a gstreamer bug or

Bug#696727: cheese does not start with Gtk-Warning

useful. -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

On Wed, Mar 27, 2013 at 07:38:45PM +0100, Michael Biebl wrote: I do get those warnings, but afaics they are a red herring. Indeed, I've fixed the warnings using the tip at https://bugzilla.gnome.org/show_bug.cgi?id=671912 and I still have the same behaviour, process runs, remains running, but

Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)

Just FWIW I've installed camorama which works fine - just to confirm that my webcam is OK. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

On Wed, Mar 27, 2013 at 09:16:17PM +, Jonathan Dowland wrote: You are perhaps correct that those errors are a red herring. Nevertheless I have a bt with G_DEBUG=fatal-warnings, attached in case it's useful. Actually attached. $ gdb ./.libs/cheese GNU gdb (GDB) 7.4.1-debian Copyright (C

Bug#702769: bup_0.25~git2011.11.04-5.1_amd64.changes ACCEPTED into unstable

, or tried to reach me via other means… None-the-less, thanks for fixing the bug. -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694570: installation failures with d-i beta4 relating to EFI

Package: installation-reports Severity: critical Justification: makes baby jesus cry Hi, I just tried d-i beta4 amd64 netinst on my lenovo thinkpad x121e laptop. The Laptop's firmware has boot mode set to 'either/both' for legacy BIOS/EFI. The storage device was a totally blank SSD, no prior OS.