Bug#1074765: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed

2024-07-02 Thread Joey Hess
Package: nocache Version: 1.1-1+b1 Severity: normal joey@darkstar:~>nocache true true: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed. Aborted - exit 134 Happens every time. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable')

Bug#1074607: Error: Could not restart systemd, systemd binary not working

2024-07-01 Thread Joey Hess
Package: libc6 Version: 2.38-13 Severity: normal Seen this scary message on a few upgrades. It seems that the postinst tries to run "systemd --help", but systemd no longer provides a systemd command. ii systemd256.1-2 amd64system and service manager -- System Information: D

Bug#1074607: Error: Could not restart systemd, systemd binary not working

2024-07-01 Thread Joey Hess
Package: libc6 Version: 2.38-13 Severity: normal Seen this scary message on a few upgrades. It seems that the postinst tries to run "systemd --help", but systemd no longer provides a systemd command. ii systemd256.1-2 amd64system and service manager -- System Information: D

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2024-05-09 Thread Joey Hess
Joey Hess wrote: > with the old ref I saw on the remote. If the shas are different, I > check `git log --oneline $old..$src` -- if this outputs nothing, then > history is not advancing and it refuses to push that ref, and > reports the error to git. That's not quite right

Bug#1060224: bluetoothd started segfaulting

2024-05-01 Thread Joey Hess
Thanks, I've tried 5.73-1 and have not been able to get it to crash so far. -- see shy jo signature.asc Description: PGP signature

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2024-04-26 Thread Joey Hess
I was implementing another gitremote-helper today and ran into what I think is the same problem. Since I've worked around the problem in my gitremote-helper successfully, I wanted to share what I've learned in case it can help git-remote-gcrypt. When git push is run, for a non-forced push, it asks

Bug#1068024: revert to version that does not contain changes by bad actor

2024-04-03 Thread Joey Hess
Guillem Jover wrote: > dpkg should be able to use an old liblzma w/o multi-threaded compressor > or decompressor support Ah you're right. configure did find the library, but I'd missed updating some ifdefs. Attached updated dpkg patch which does build with the shared library and works. -- see sh

Bug#1068024: revert to version that does not contain changes by bad actor

2024-03-31 Thread Joey Hess
> The situation is being analysed by a cross-team taskforce, > please let them do the already-stressing job ☻ Sorry, didn't see that before sending my previous message. I'll leave it to you guys. -- see shy jo signature.asc Description: PGP signature

Bug#1068024: revert to version that does not contain changes by bad actor

2024-03-31 Thread Joey Hess
Since there's been some discussion about versions, the version in my xz-unscathed git repository is the same as xz 5.3.2alpha, with the addition of a fix for CVE-2022-1271 that did not make it into that version. (It was fixed in 5.2.6, but 5.3.2alpha was diverged from 5.2.5. Jia Tan was involved in

Bug#1068024: revert to version that does not contain changes by bad actor

2024-03-30 Thread Joey Hess
I have prepared a git repository that is a fork of xz from the point I identified before the attacker(s) did anything to it. In my fork, I have renamed liblzma to liblzmaunscathed. That allows it to be installed alongside current dpkg without breaking dpkg with an old version of liblzma. My git r

Bug#1068024: revert to version that does not contain changes by bad actor

2024-03-30 Thread Joey Hess
Aurelien Jarno wrote: > Note that reverted to such an old version will break packages that use > new symbols introduced since then. From a quick look, this is at least: > - dpkg > - erofs-utils > - kmod > > Having dpkg in that list means that such downgrade has to be planned > carefully. I agree

Bug#1068024: revert to version that does not contain changes by bad actor

2024-03-29 Thread Joey Hess
Package: xz-utils Version: 5.6.1+really5.4.5-1 Severity: important Tags: security I count a minimum of 750 commits or contributions to xz by Jia Tan, who backdoored it. This includes all 700 commits made after they merged a pull request in Jan 7 2023, at which point they appear to have already ha

Bug#1065072: packagekit spinning cpu

2024-03-09 Thread Joey Hess
Matthias Klumpp wrote: > either GNOME Software is wrong (I think it unconditionally has a > problem, it should never retry a cache refresh at that insane > frequency), or the APT backend in PackageKit does something wrong and > emits package changes for blocked packages when it shouldn't do so. > I

Bug#1065072: packagekit spinning cpu

2024-03-08 Thread Joey Hess
Joey Hess wrote: > It may also be relevant somehow that the topmost update was a thinkpad > AMD firmware update which "requires restart". I masked and stopped packagekit again and now in gnome-software, it displays only the thinkpad amd firmware update, and it's no longer

Bug#1065072: packagekit spinning cpu

2024-03-08 Thread Joey Hess
Below is a pkmon while the problem is occurring. Since it points at gnome-software causing the activity, I tried opening that. I noticed that the updates tab had an indicator that there were updates. Switching to it, I saw it continuously alternate between "Loading updates" with a spinner and a li

Bug#1065072: packagekit spinning cpu

2024-03-08 Thread Joey Hess
I'm confident I saw this same problem today, with packagekit repeatedly updating and spinning a CPU for 10 minutes. It only stopped at that point because I stopped and masked it. (Stopping it was not enough, something was restarting the service every time I stopped it.) See attached log. I did not

Bug#879723: can get stuck in state INSANE and stop responding

2024-02-24 Thread Joey Hess
Pali Rohár wrote: > I have looked at the whole netplugd state machine and transitions > between states. I identified more bugs than the one described in this > issue report. I have prepared fixes for all of them. > > Joey, would you be interested in testing netplugd fixes? Thanks for your work, I

Bug#1053472: starts w/o writing pid file, leading systemd to kill it

2024-01-15 Thread Joey Hess
Correction: Not the default configuration per se, just the configuration that is necessary to interoperate with the default (chrooted) configuration of postfix. -- see shy jo signature.asc Description: PGP signature

Bug#1060224: bluetoothd started segfaulting

2024-01-07 Thread Joey Hess
Package: bluez Version: 5.71-1 Severity: normal On upgrade to this version, bluetoothd started segfaulting frequently: [ 59.628624] input: Avantree SP750 (AVRCP) as /devices/virtual/input/input26 [ 97.073761] bluetoothd[838]: segfault at 561314652a23 ip 56167406a375 sp 7fffb128a200 e

Bug#1055070: /usr/share/doc/ghc-doc/html/libraries/index.html missing boot libraries

2023-10-30 Thread Joey Hess
Package: ghc-doc Version: 9.4.7-1 Severity: normal /usr/share/doc/ghc-doc/html/libraries/index.html used to include Prelude, Data.List, GHC.* etc. Now that is all missing and it only contains docs for libghc-*-doc packages. I did find the docs in /usr/share/doc/ghc-doc/html/libraries/base-4.17.2

Bug#1055070: /usr/share/doc/ghc-doc/html/libraries/index.html missing boot libraries

2023-10-30 Thread Joey Hess
Package: ghc-doc Version: 9.4.7-1 Severity: normal /usr/share/doc/ghc-doc/html/libraries/index.html used to include Prelude, Data.List, GHC.* etc. Now that is all missing and it only contains docs for libghc-*-doc packages. I did find the docs in /usr/share/doc/ghc-doc/html/libraries/base-4.17.2

Bug#1054671: Acknowledgement (gdm not starting on boot)

2023-10-27 Thread Joey Hess
I had plymouth installed. Removing it avoided this bug. -- see shy jo signature.asc Description: PGP signature

Bug#1054671: gdm not starting on boot

2023-10-27 Thread Joey Hess
Package: gdm3 Version: 45.0.1-1 Severity: normal gdm was starting on boot until an upgrade a couple weeks ago. Now the laptop boots to a getty, and I have to log in as root and systemctl start gdm3 There are no other login managers installed, although lightdm did get installed breifly around the

Bug#1053472: starts w/o writing pid file, leading systemd to kill it

2023-10-04 Thread Joey Hess
Package: sasl2-bin Version: 2.1.28+dfsg1-3 Severity: normal saslauthd was not running after an upgrade. Investigation showed this happening after systemctl start: Oct 04 14:21:21 kite systemd[1]: Failed to start saslauthd.service - SASL Authentication Daemon. Oct 04 14:21:21 kite systemd[1]: sa

Bug#1053278: Acknowledgement (embeds fasttext LLM)

2023-09-30 Thread Joey Hess
Screenshot attached -- see shy jo signature.asc Description: PGP signature

Bug#1053279: contains 100+kb minified .js file without corresponding source

2023-09-30 Thread Joey Hess
Package: firefox Version: 118.0-1 Severity: normal toolkit/components/translations/fasttext/fasttext_wasm.js is 100+ kb of minified js. There is no other source code. AFAIK this is not acceptable in a Debian package. https://firefox-source-docs.mozilla.org/toolkit/components/translations/resource

Bug#1053278: embeds fasttext LLM

2023-09-30 Thread Joey Hess
Package: firefox Version: 118.0-1 Severity: normal Firefox has a new offline translation capability in version 118. Step one of that is determining the language used in a web page. It uses https://fasttext.cc/ to acomplish that. I have experimentally verified that firefox is able to detect the l

Bug#1051987: Acknowledgement (too old for ghc)

2023-09-20 Thread Joey Hess
I've confirmed that the same build that fails with this version of cabal succeeds with cabal-install version 3.10.1.0 compiled using version 3.10.1.0 of the Cabal library -- see shy jo signature.asc Description: PGP signature

Bug#1051987: Acknowledgement (too old for ghc)

2023-09-20 Thread Joey Hess
I've confirmed that the same build that fails with this version of cabal succeeds with cabal-install version 3.10.1.0 compiled using version 3.10.1.0 of the Cabal library -- see shy jo signature.asc Description: PGP signature ___ Pkg-haskell-maintai

Bug#1051987: too old for ghc

2023-09-15 Thread Joey Hess
Package: cabal-install Version: 3.4.1.0-3 Severity: normal This version of cabal in unstable is too old to properly support ghc 9.4.6 in unstable: joey@darkstar:~/src/git-annex>cabal configure 'cabal.project.local' already exists, backing it up to 'cabal.project.local~'. Warning: Unknown/unsuppo

Bug#1051987: too old for ghc

2023-09-15 Thread Joey Hess
Package: cabal-install Version: 3.4.1.0-3 Severity: normal This version of cabal in unstable is too old to properly support ghc 9.4.6 in unstable: joey@darkstar:~/src/git-annex>cabal configure 'cabal.project.local' already exists, backing it up to 'cabal.project.local~'. Warning: Unknown/unsuppo

Bug#1050380: dhcpcd-run-hooks.8 man page missing

2023-08-23 Thread Joey Hess
Package: dhcpcd Version: 1:10.0.2-4 Severity: normal The man pages refer to this man page, but it's not included in the binary package. (It is in the source, hooks/dhcpcd-run-hooks.8.in) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Archi

Bug#1042915: please update to 0.24

2023-08-02 Thread Joey Hess
Package: libghc-aws-dev Version: 0.22.1-1+b4 Severity: wishlist Version 0.24 enables new features in git-annex, including anonymous import from a public bucket. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Fo

Bug#1042915: please update to 0.24

2023-08-02 Thread Joey Hess
Package: libghc-aws-dev Version: 0.22.1-1+b4 Severity: wishlist Version 0.24 enables new features in git-annex, including anonymous import from a public bucket. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Fo

Bug#1040674: config.txt during kernel upgrade spends time in non-bootable state

2023-07-08 Thread Joey Hess
Package: raspi-firmware Version: 1.20220830+ds-1 Severity: normal While upgrading the kernel, my raspberry pi reset and failed to come back up to a usable state. Serial console showed the last thing output was the kernel saying it was running init. Investigation of the SD card found this in config

Bug#1039050: same bug here

2023-07-03 Thread Joey Hess
I've worked around this using upstream's gtk4 branch. That runs stably though it's missing a few minor features. -- see shy jo signature.asc Description: PGP signature

Bug#1039050: same bug here

2023-07-02 Thread Joey Hess
(com.github.johnfactotum.Foliate:203690): Gjs-WARNING **: 13:14:57.747: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: main@resource:///com/git

Bug#1037310: missing space in PING line for ipv6

2023-06-10 Thread Joey Hess
Package: iputils-ping Version: 3:20221126-1 Severity: normal PING www.google.com(yi-in-f147.1e100.net (2607:f8b0:4002:c0c::93)) 56 data bytes Compare with ipv4 PING duckduckgo.com (52.149.246.39) 56(84) bytes of data. -- System Information: Debian Release: 12.0 APT prefers unstable APT poli

Bug#1036023: same problem on armhf

2023-05-28 Thread Joey Hess
I rebuilt cabal-install from source, turning off the lukko build flag, and confirmed that fixed this problem. My recommendation would be to just do that for now, until lukko gets fixed. -- see shy jo signature.asc Description: PGP signature

Bug#1036023: same problem on armhf

2023-05-28 Thread Joey Hess
I rebuilt cabal-install from source, turning off the lukko build flag, and confirmed that fixed this problem. My recommendation would be to just do that for now, until lukko gets fixed. -- see shy jo signature.asc Description: PGP signature ___ Pkg-h

Bug#1036023: same problem on armhf

2023-05-28 Thread Joey Hess
I'm experiencing the same bug on armhf with cabal-install 3.4.1.0-3. My workaround was to downgrade it to 3.0.0.0-3+b1. This may be a relevant upstream issue: https://github.com/haskellari/lukko/issues/15 -- see shy jo signature.asc Description: PGP signature

Bug#1036023: same problem on armhf

2023-05-28 Thread Joey Hess
I'm experiencing the same bug on armhf with cabal-install 3.4.1.0-3. My workaround was to downgrade it to 3.0.0.0-3+b1. This may be a relevant upstream issue: https://github.com/haskellari/lukko/issues/15 -- see shy jo signature.asc Description: PGP signature _

Bug#1034648: postinst runs linux-update-symlinks before initrd exists

2023-04-24 Thread Joey Hess
Ben Hutchings wrote: > This behaviour is intentional. The expectation is that these symlinks > are used by programs that update the boot loader configuration later > on, and those will be run only after the initramfs has been generated. > What do you think will go wrong here? Ok, I am probably wr

Bug#1034648: postinst runs linux-update-symlinks before initrd exists

2023-04-24 Thread Joey Hess
Ben Hutchings wrote: > This behaviour is intentional. The expectation is that these symlinks > are used by programs that update the boot loader configuration later > on, and those will be run only after the initramfs has been generated. > What do you think will go wrong here? Ok, I am probably wr

Bug#1034648: postinst runs linux-update-symlinks before initrd exists

2023-04-20 Thread Joey Hess
Source: linux Version: 6.1.20-2 Severity: normal I was upgrading a slow arm board and noticed this: Setting up linux-image-6.1.0-7-armmp-lpae (6.1.20-2) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.18.0-4-armmp-lpae I: /initrd.img.old is now a symlink to boot/initrd.img-5.18.0-4-armmp-l

Bug#1034648: postinst runs linux-update-symlinks before initrd exists

2023-04-20 Thread Joey Hess
Source: linux Version: 6.1.20-2 Severity: normal I was upgrading a slow arm board and noticed this: Setting up linux-image-6.1.0-7-armmp-lpae (6.1.20-2) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.18.0-4-armmp-lpae I: /initrd.img.old is now a symlink to boot/initrd.img-5.18.0-4-armmp-l

Bug#1034319: debootstrap of foreign arch fails w/o recommended binfmt-support

2023-04-12 Thread Joey Hess
Package: qemu-user-static Version: 1:7.2+dfsg-5 Severity: normal I got a new arm64 host at Hetzner, and needed an amd64 chroot in it. Of course that's easy, since debootstrap --arch just works for foreign arches with qemu-user-static installed. root@sparrow:/tmp>apt-get install debootstrap qemu-u

Bug#1033627: exporttree=yes data loss

2023-03-28 Thread Joey Hess
nd including it. (The patches are lightly trimmed versions of upstream commits 02662f52920e84cd9464641ada84f6c3bbe3f86a and 18d326cb6f27912542f41fbb9525eefdbd553d09) -- see shy jo From 02662f52920e84cd9464641ada84f6c3bbe3f86a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Mar 2023 15:21:1

Bug#1033627: exporttree=yes data loss

2023-03-28 Thread Joey Hess
nd including it. (The patches are lightly trimmed versions of upstream commits 02662f52920e84cd9464641ada84f6c3bbe3f86a and 18d326cb6f27912542f41fbb9525eefdbd553d09) -- see shy jo From 02662f52920e84cd9464641ada84f6c3bbe3f86a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Mar 2023 15:21:1

Bug#1032531: dh_installchangelogs puts incorrect comment at the end of trimmed changelogs

2023-03-08 Thread Joey Hess
Package: debhelper Version: 13.11.4 Severity: normal I wanted to see the earlier changelog for debconf, and saw its changelog ends with: -- Colin Watson Sat, 03 Aug 2019 11:51:13 +0100 # Older entries have been removed from this changelog. # To read the complete changelog use `apt changelog d

Re: Licensing of old Debconf::Gettext module in dpkg

2023-03-07 Thread Joey Hess
Guillem Jover wrote: > Hi Joey and Nicolas! > > Long time ago the Debconf::Gettext [O] module got imported into the dpkg > code base [I] with some modifications from Nicolas. The current module > in the dpkg code base is [C], which has seen substantial modifications > by me since its import. > >

Bug#1031647: git-annex: Bogus build dependency whitelist results in FTBFS on m68k

2023-02-23 Thread Joey Hess
e of git-annex. -- see shy jo From f24f96e0186a61ef5940ce97de2713413989b63c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 23 Feb 2023 10:35:19 -0400 Subject: [PATCH] move webapp build deps under Assistant build flag git-annex.cabal: Move webapp build deps under the Assistant build fla

Bug#1031647: git-annex: Bogus build dependency whitelist results in FTBFS on m68k

2023-02-23 Thread Joey Hess
e of git-annex. -- see shy jo From f24f96e0186a61ef5940ce97de2713413989b63c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 23 Feb 2023 10:35:19 -0400 Subject: [PATCH] move webapp build deps under Assistant build flag git-annex.cabal: Move webapp build deps under the Assistant build fla

Re: Bug#1031647: git-annex: Bogus build dependency whitelist results in FTBFS on m68k

2023-02-23 Thread Joey Hess
e of git-annex. -- see shy jo From f24f96e0186a61ef5940ce97de2713413989b63c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 23 Feb 2023 10:35:19 -0400 Subject: [PATCH] move webapp build deps under Assistant build flag git-annex.cabal: Move webapp build deps under the Assistant build fla

Bug#1030317: youtube-dl replacement by yt-dlp prevents git-annex frm using it

2023-02-02 Thread Joey Hess
Package: git-annex Version: 10.20221003-3 Severity: normal Now when youtube-dl is installed, there is no youtube-dl in path, so git-annex cannot use it. Newer versions of git-annex have been changed to support yt-dlp. This could be fixed by upgrading it, or cherry picking these commits: 5256be61c

Bug#1030317: youtube-dl replacement by yt-dlp prevents git-annex frm using it

2023-02-02 Thread Joey Hess
Package: git-annex Version: 10.20221003-3 Severity: normal Now when youtube-dl is installed, there is no youtube-dl in path, so git-annex cannot use it. Newer versions of git-annex have been changed to support yt-dlp. This could be fixed by upgrading it, or cherry picking these commits: 5256be61c

Bug#1030037: fsck.repair=yes is not documented

2023-01-30 Thread Joey Hess
Package: initramfs-tools Version: 0.142 Severity: wishlist I wanted automatic fsck for problems on the root filesystem, and it was difficult to disconver that fsck.repair=yes on the kernel cmdline is the way to configure that. initramfs-tools was made to support the same configuration used by sys

Bug#1030037: fsck.repair=yes is not documented

2023-01-30 Thread Joey Hess
Package: initramfs-tools Version: 0.142 Severity: wishlist I wanted automatic fsck for problems on the root filesystem, and it was difficult to disconver that fsck.repair=yes on the kernel cmdline is the way to configure that. initramfs-tools was made to support the same configuration used by sys

Bug#848578: [PATCH] ts: Enable UTF-8 binary mode for input and output processing (Closes: #848578)

2023-01-02 Thread Joey Hess
Nicolas Schier wrote: > Are there chances that you still apply such patches? After your call > for adoption: Is there some new maintainer for moreutils already > available? I'm still maintaining moreutils until I find someone else. I am not considering new additions of tools to it any longer.

Bug#848578: [PATCH] ts: Enable UTF-8 binary mode for input and output processing (Closes: #848578)

2023-01-02 Thread Joey Hess
Nicolas Schier wrote: > Enable UTF-8 compatible processing of input and output to correctly output > e.g. > timestamps containing non-latin letters (cp. [1]). > +# Ensure that text read or printed are converted from/to UTF-8. > +binmode STDIN, ':utf8'; > +binmode STDOUT, ':utf8'; > +binmode STDER

Bug#1027038: QR code support

2022-12-26 Thread Joey Hess
Package: impass Version: 0.12.2-1 Severity: wishlist The "pass" password manager has a show QR code option, which makes it easy to transfer a single password to a phone. On the phone, you just copy and paste the password into whatever program. This is perfect for me, since I don't want my phone to

Bug#1025967: intermittent hang

2022-12-12 Thread Joey Hess
/bugs/git_annex_test_never_exits__63__/ The attached patch fixes the bug. This is also being released in git-annex version 10.20221212. -- see shy jo From 65f9e7a3c73626f17f6f49d0c8266041fd333e93 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 8 Dec 2022 14:18:54 -0400 Subject: [PATCH 1/8

Bug#1025967: intermittent hang

2022-12-12 Thread Joey Hess
/bugs/git_annex_test_never_exits__63__/ The attached patch fixes the bug. This is also being released in git-annex version 10.20221212. -- see shy jo From 65f9e7a3c73626f17f6f49d0c8266041fd333e93 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 8 Dec 2022 14:18:54 -0400 Subject: [PATCH 1/8

Bug#1024226: git-annex: please replace youtube-dl suggests with yt-dlp

2022-11-21 Thread Joey Hess
see shy jo From 5256be61c12fb030fe2eebe2751ee1601a5e7514 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Nov 2022 14:39:26 -0400 Subject: [PATCH] When youtube-dl is not available in PATH, use yt-dlp instead Debian is going to drop youtube-dl which is not active upstream, and yt-dlp is the replacement. This will

Bug#1024226: git-annex: please replace youtube-dl suggests with yt-dlp

2022-11-21 Thread Joey Hess
see shy jo From 5256be61c12fb030fe2eebe2751ee1601a5e7514 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Nov 2022 14:39:26 -0400 Subject: [PATCH] When youtube-dl is not available in PATH, use yt-dlp instead Debian is going to drop youtube-dl which is not active upstream, and yt-dlp is the replacement. This will

Bug#1021840: mention borg compact in NEWS.Debian

2022-10-15 Thread Joey Hess
Package: borgbackup Version: 1.2.2-2 Severity: wishlist borg compact is needed to actually free up pruned space, which was not the case with the version in stable. I noticed this only after my backup disk overflowed, and I think that having a mention of it in NEWS.Debian might have made me aware o

Bug#728024: rejected upstream

2022-10-03 Thread Joey Hess
I have rejected this idea in upstream commit 28ec94ee7fb080ec31a29fe121f2e94bc68e6fba: > I think this is out of scope for git-annex. It's not its place to change > what files git allows to be version controlled. I will not change my mind regarding this. Of course, Debian can patch git-annex to b

Bug#728024: rejected upstream

2022-10-03 Thread Joey Hess
I have rejected this idea in upstream commit 28ec94ee7fb080ec31a29fe121f2e94bc68e6fba: > I think this is out of scope for git-annex. It's not its place to change > what files git allows to be version controlled. I will not change my mind regarding this. Of course, Debian can patch git-annex to b

Bug#789225: seems fixed?

2022-10-03 Thread Joey Hess
I don't know the version, but I'm sure this was fixed years ago. -- see shy jo signature.asc Description: PGP signature

Bug#789225: seems fixed?

2022-10-03 Thread Joey Hess
I don't know the version, but I'm sure this was fixed years ago. -- see shy jo signature.asc Description: PGP signature ___ Pkg-haskell-maintainers mailing list Pkg-haskell-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/ma

Bug#1004043: seems fixed

2022-10-03 Thread Joey Hess
I was able to reproduce this using version 8.20210128. It seems to be fixed in version 10.20220526. I think this was fixed by commit 1cacfd1b199b1a9a093716e04afd7e5ef4bd26a5. While that commit was fixing problems caused by test suite parallization that happened well after this bug was filed, so c

Bug#1004043: seems fixed

2022-10-03 Thread Joey Hess
I was able to reproduce this using version 8.20210128. It seems to be fixed in version 10.20220526. I think this was fixed by commit 1cacfd1b199b1a9a093716e04afd7e5ef4bd26a5. While that commit was fixing problems caused by test suite parallization that happened well after this bug was filed, so c

Bug#1021206: new upstream release fixes numerous reversions and bugs

2022-10-03 Thread Joey Hess
Package: git-annex Version: 10.20220724-1 Severity: normal The current git-annex release is 10.20221003, and it fixes a number of reversions and bugs that are present in the version in Debian. I've gathered the main ones here, although if you chose to cherry-pick these commits, you would need to

Bug#1021206: new upstream release fixes numerous reversions and bugs

2022-10-03 Thread Joey Hess
Package: git-annex Version: 10.20220724-1 Severity: normal The current git-annex release is 10.20221003, and it fixes a number of reversions and bugs that are present in the version in Debian. I've gathered the main ones here, although if you chose to cherry-pick these commits, you would need to

Bug#900173: probably fixed

2022-10-03 Thread Joey Hess
commit 947d2a10bcf80e74758f65b3cc3fd5ac1bff3fa8 Author: Joey Hess Date: Wed May 12 15:08:03 2021 -0400 assistant: Fix a crash on startup by avoiding using forkProcess ghc 8.8.4 seems to have changed something that broke code that has been successfully using forkProcess since 2012

Bug#900173: probably fixed

2022-10-03 Thread Joey Hess
commit 947d2a10bcf80e74758f65b3cc3fd5ac1bff3fa8 Author: Joey Hess Date: Wed May 12 15:08:03 2021 -0400 assistant: Fix a crash on startup by avoiding using forkProcess ghc 8.8.4 seems to have changed something that broke code that has been successfully using forkProcess since 2012

Bug#965135: probably fixed in 8.20201007

2022-10-03 Thread Joey Hess
This bug seems very similar to a known fixed git-annex bug. commit 922621301ae750e9ee86807ae21709e2e5b2d352 Author: Joey Hess Date: Thu Sep 17 17:27:42 2020 -0400 Serialize use of C magic library, which is not thread safe. This fixes failures uploading to S3 when using -J. -- see

Bug#965135: probably fixed in 8.20201007

2022-10-03 Thread Joey Hess
This bug seems very similar to a known fixed git-annex bug. commit 922621301ae750e9ee86807ae21709e2e5b2d352 Author: Joey Hess Date: Thu Sep 17 17:27:42 2020 -0400 Serialize use of C magic library, which is not thread safe. This fixes failures uploading to S3 when using -J. -- see

Bug#1014628: FWD: Re: git-annex arm 32-bit builds

2022-09-18 Thread Joey Hess
I was looking at this bug the other day trying to determine why git-annex was not in testing, and did not realize it was due to this dbus issue. My mail below digs into it, if the issue is still happening. - Forwarded message from Joey Hess - Date: Mon, 23 May 2022 12:48:21 -0400 From

Bug#1014628: FWD: Re: git-annex arm 32-bit builds

2022-09-18 Thread Joey Hess
I was looking at this bug the other day trying to determine why git-annex was not in testing, and did not realize it was due to this dbus issue. My mail below digs into it, if the issue is still happening. - Forwarded message from Joey Hess - Date: Mon, 23 May 2022 12:48:21 -0400 From

Bug#1014628: FWD: Re: git-annex arm 32-bit builds

2022-09-18 Thread Joey Hess
I was looking at this bug the other day trying to determine why git-annex was not in testing, and did not realize it was due to this dbus issue. My mail below digs into it, if the issue is still happening. - Forwarded message from Joey Hess - Date: Mon, 23 May 2022 12:48:21 -0400 From

Bug#1019462: started checking for mail in the middle of tab completion

2022-09-09 Thread Joey Hess
Package: bash Version: 5.2~rc2-2 Severity: normal For example, here I entered "cd sr" joey@darkstar:~>cd srYou have mail in /home/joey/Maildir c/ I think this behavior started on this upgrade: 2022-09-07 15:08:53 upgrade bash:amd64 5.1-6.1 5.2~rc2-2 -- System Information: Debia

Re: Substitute for archivemail

2022-09-05 Thread Joey Hess
chewmail is probably the best substitute. It has a very similar usage, I only had to change the -o option and replace -u with -R. -- see shy jo signature.asc Description: PGP signature

Bug#1019215: "AGE" in man page is unclear

2022-09-05 Thread Joey Hess
Package: mail-expire Version: 0.9.1 Severity: normal mail-expire AGE FILES... What is this "AGE"? I am not going to run a program that messes with my email to find out. The rest of the man page does not say. I found the answer in mail-expire --help Usage: /usr/bin/mail-expire [

Bug#992995: mail-expire: Add support to skip new or unread marked mails

2022-09-05 Thread Joey Hess
I agree, I would also need this in order to replace my useage of archivemail with mail-expire. I'm probably not unusual in having certian mailboxes full of messages that need to remain in there despite being old or unread. -- see shy jo signature.asc Description: PGP signature

Bug#1014007: too old for current ghc

2022-06-28 Thread Joey Hess
Package: cabal-install Version: 3.0.0.0-3+b1 Severity: normal cabal build now complains about an unsupported ghc version Warning: Unknown/unsupported 'ghc' version detected (Cabal 3.0.1.0 supports 'ghc' version < 8.10): /usr/bin/ghc is version 9.0.2 -- System Information: Debian Release: bookwor

Bug#1014007: too old for current ghc

2022-06-28 Thread Joey Hess
Package: cabal-install Version: 3.0.0.0-3+b1 Severity: normal cabal build now complains about an unsupported ghc version Warning: Unknown/unsupported 'ghc' version detected (Cabal 3.0.1.0 supports 'ghc' version < 8.10): /usr/bin/ghc is version 9.0.2 -- System Information: Debian Release: bookwor

Bug#1013898: significantly slower than 3.0.17.4-3

2022-06-26 Thread Joey Hess
Package: vlc Version: 3.0.17.4-4 Severity: normal I'm seeing only a few frames per second with -4 on 1080p H264 video. After downgrading to -3, it's back to ~60 FPS. This is the last part of the output of -4. The VA-API stuff seems relevant somehow since the changelog says that was disabled in th

Bug#1013898: significantly slower than 3.0.17.4-3

2022-06-26 Thread Joey Hess
Package: vlc Version: 3.0.17.4-4 Severity: normal I'm seeing only a few frames per second with -4 on 1080p H264 video. After downgrading to -3, it's back to ~60 FPS. This is the last part of the output of -4. The VA-API stuff seems relevant somehow since the changelog says that was disabled in th

Re: use of Recommends by vlc to force users to use pipewire

2022-05-31 Thread Joey Hess
Vincent Lefevre wrote: > So there's something contradictory. If the pipewire service alone > doesn't take control of audio over pulseaudio, then the only culprit > would be pipewire-media-session. Or what? A bug in pipewire, which > would actually take control of audio even without pipewire-pulse?

Bug#1010278: xterm_set_titles is broken

2022-05-03 Thread Joey Hess
I have the same problem, which causes a broken display when eg, deleting messages. I can confirm that setting TERM=xterm-p370 avoids the problem. -- see shy jo signature.asc Description: PGP signature

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-03 Thread Joey Hess
Fixed with attached patch. -- see shy jo From 43701759a32e38613c61de6dc923c24069f435d6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 3 May 2022 12:12:25 -0400 Subject: [PATCH] disable shellescape for rsync 3.2.4 rsync 3.2.4 broke backwards-compatability by preventing exposing filenames

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-03 Thread Joey Hess
Fixed with attached patch. -- see shy jo From 43701759a32e38613c61de6dc923c24069f435d6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 3 May 2022 12:12:25 -0400 Subject: [PATCH] disable shellescape for rsync 3.2.4 rsync 3.2.4 broke backwards-compatability by preventing exposing filenames

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-03 Thread Joey Hess
> > git-annex enableremote foo shellescape=no I've confirmed that this workaround works. Also, the client's version of rsync is what matters. 3.2.3 client and 3.2.4 server does not have the problem. -- see shy jo signature.asc Description: PGP signature

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-03 Thread Joey Hess
> > git-annex enableremote foo shellescape=no I've confirmed that this workaround works. Also, the client's version of rsync is what matters. 3.2.3 client and 3.2.4 server does not have the problem. -- see shy jo signature.asc Description: PGP signature ___

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-02 Thread Joey Hess
Sean Whitton wrote: > > git-annex can be configured to not do its own shell escaping when accessing > > a rsync special remote. If your remote is named "foo", you can configure it > > that way as follows: > > > > git-annex enableremote foo shellescape=no > > Thanks for looking into it. Do you

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-02 Thread Joey Hess
Sean Whitton wrote: > > git-annex can be configured to not do its own shell escaping when accessing > > a rsync special remote. If your remote is named "foo", you can configure it > > that way as follows: > > > > git-annex enableremote foo shellescape=no > > Thanks for looking into it. Do you

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-02 Thread Joey Hess
Joey Hess wrote: > The rsync command that git-annex runs has a trailing close quote, as > seen in the first excerpt above. But rsync then complains about the path > with that close quote removed. > > I'm having a hard time not seeing this as a bug in rsync. # NEWS for rsyn

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-02 Thread Joey Hess
Joey Hess wrote: > The rsync command that git-annex runs has a trailing close quote, as > seen in the first excerpt above. But rsync then complains about the path > with that close quote removed. > > I'm having a hard time not seeing this as a bug in rsync. # NEWS for rsyn

Bug#1010397: Fwd: Bug#1010397: git-annex sync fails in rsync remotes with rsync 3.2.4-1

2022-05-02 Thread Joey Hess
> [2022-04-30 13:00:20.39881781] (Utility.Process) process [1635096] read: > rsync ["-e","'ssh' '-S' '../.git/annex/ssh/user@host-key' '-o' > 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-l' 'user' > '-T'","--progress","--inplace", > "user@host-key:/backup/dspace/repositories/repository.git

  1   2   3   4   5   6   7   8   9   10   >