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, bec
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
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
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
> 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
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
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
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
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
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.
>
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 lo
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
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
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,
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
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
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
I had plymouth installed. Removing it avoided this bug.
--
see shy jo
signature.asc
Description: PGP signature
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
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]:
Screenshot attached
--
see shy jo
signature.asc
Description: PGP signature
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.
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
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
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:
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')
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)
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
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
(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:
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
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
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
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
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
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
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:10 -0400
Subject
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
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 flag so
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:
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
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.
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
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
/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
o
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 make it b
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
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
I don't know the version, but I'm sure this was fixed years ago.
--
see shy jo
signature.asc
Description: PGP signature
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
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
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
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
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
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:
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 [
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
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:
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
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
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
> > 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
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
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 rsync 3.2
> [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",
>
Package: openssh-server
Version: 1:9.0p1-1
Severity: normal
I upgraded libc6 on a armhf box running a rather stale version of
testing, due to installing some package that needed the new version:
2022-04-12 18:23:06 upgrade libc6:armhf 2.32-4 2.33-7
After this partial upgrade, sshing to the host
Version: 1.5.2-2.1
I'm now seeing this bug. Oddly, I did not see the bug back in 2020,
when I was successfully using arduino-mk. But now:
make do_upload
make[1]: Entering directory '/home/joey/src/arduino-copilot/Examples/Blink'
/usr/share/arduino/hardware/tools/avr/bin/avrdude -q -V -p
Colin Watson wrote:
> On Fri, Feb 04, 2022 at 09:24:25AM -0400, Joey Hess wrote:
> > -1: unknown option
> > debconf: whiptail output the above errors, giving up!
>
> Hm, I *think* this can only happen if the height or width of the dialog
> computed by Debconf::FrontEnd::
Seeing this bug after upgrade. My imap server is dovecot.
--
see shy jo
signature.asc
Description: PGP signature
Package: debconf
Version: 1.5.79
Severity: normal
-1: unknown option
debconf: whiptail output the above errors, giving up!
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture:
The simple fact is that as an upstream author who used the debian
locations because they were the ones that worked on my system, I get bug
reports from users of other systems that it's not right for wider uses
of zsh. And Debian seems to be leaving it up to me to deal with it,
which just makes me
Package: fbreader
Version: 0.12.10dfsg2-5
Severity: normal
touch foo.epub
fbreader foo.epub
This will display whatever ebook you last had open in fbreader, without
any indication that there's a problem with the file it was asked to open.
In some situations, this can be very confusing behavior.
Package: firefox
Version: 94.0.2-1
Severity: normal
I have a ~/bin/firefox wrapper script ahead of the usual firefox in PATH.
#!/bin/sh
MOZ_USE_XINPUT2=1 /usr/bin/firefox "$@"
This has a very surprising behavior, because /usr/bin/firefox contains:
FIREFOX="$(command -v firefox)"
[ -x
Package: src:linux
Version: 5.10.46-4
Severity: wishlist
I am currently having to use the out of tree Exar USB Serial Driver
(xr_usb_serial_common) to talk to a modbus communication cable.
Last year, a reimplementation of that driver finally made mainline,
as CONFIG_USB_SERIAL_XR.
Looking at the
Package: flash-kernel
Version: 3.104
Severity: normal
I have some image building scripts that installed flash-kernel in a chroot
(on unrelated hardware; user mode qemu), then configured
/etc/flash-kernel/machine, then ran flash-kernel.
That used to work (in 2018), and now fails:
Creating config
Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20210825.4ca9c75+dfsg-1
Severity: normal
ERROR: Unknown SSL protocol connecting to host 'kitenet.net' for repository
'kite'. OpenSSL responded:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed
certificate (_ssl.c:1129)
root@kite:~>sh -x /usr/lib/postfix/configure-instance.sh
+ INSTANCE=
+ SYNC_CHROOT=y
+ test -r /etc/default/postfix
+ [ X = X ]
+ POSTCONF=postconf -o inet_interfaces=
+ + tr A-Z a-z
postconf -o inet_interfaces= -hx myorigin
+ MYORIGIN=kitenet.net
+ [ Xkitenet.net != Xkitenet.net ]
+ [
Package: postfix
Version: 3.5.6-1+b1
Severity: normal
This server is following testing, and has automatic upgrades enabled. On
Sep 22, all outgoing mail ceased flowing.
I have been able to work around the problem by disabling chrooting for
smtp in master.cf.
/var/spool/postfix/etc/services
Package: git-annex
Version: 8.20210223-2
Severity: normal
There have been some two related fixes upstream since this version
to bugs that affect a sizable number of git-annex users, and make
git-annex fairly unusable. (Unable to send content to remotes, which
a crucial part of many workflows.
Package: apt
Version: 2.2.4
Severity: normal
E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed its
'Codename' value from 'buster' to 'bullseye'
N: This must be accepted explicitly before updates for this repository can be
applied. See apt-secure(8) manpage for details.
Package: bookworm
Version: 1.1.2+git20210715-1
Severity: normal
I ran
com.github.babluboy.bookworm foo.epub
and it complained:
[WARNING 22:12:14.238713] bookworm.vala:681: EBook not found at provided
location:foo.epub
[FATAL 22:12:14.244095] [GLib-GIO] g_file_query_exists: assertion
This bug affects git-annex, which runs bup split -q, possibly multiple
of them concurrently, and so gets its output messed up by the undesired
output.
Note that the output goes to stderr, so it cannot even be safely piped
to /dev/null without potentally swallowing error messages.
I'm fairly sure
that significantly confuse git.
https://git-annex.branchable.com/bugs/Importing_into_nested_directory_overwrites_files__63__/
--
see shy jo
From 4611813ef1a6ecc86fafc095a324ef0cfe7427e7 Mon Sep 17 00:00:00 2001
From: Joey Hess
Date: Fri, 26 Mar 2021 16:01:55 -0400
Subject: [PATCH] Fix bug importing from
Sudip Mukherjee wrote:
> There seems to be a version discrepancy.
>
> offlineimap3 is still old and thats the reason you still have that old stack
> trace.
> I think, for now just doing "apt-get update && apt-get install offlineimap3"
> should fix your issue.
Ah, I didn't remember there was a
Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20210225.1e7ef9e+dfsg-3
Severity: normal
Copy message UID -347 (1/347) local: -> kite:INBOX
ERROR: Copying message -347 [acc: joey]
'utf-8' codec can't decode byte 0xa0 in position 3278: invalid start byte
ERROR: while syncing [account
Package: etckeeper
Version: 1.18.16-1
Severity: normal
I have systems that would not have python installed except etckeeper
depends on it. The dependency is for brz if I understand correctly.
However, etckeeper does not use brz by default, and its dependencies
let the user choose their vcs
This is fixed in version 0.26.
http://joeyh.name/code/mpdtoys/
--
see shy jo
signature.asc
Description: PGP signature
d patch should fix this.
>
> @Joey Hess It will be great if you test the patch and confirm if it
> fixes your problem.
It does, but only after I fixed an unrelated problem:
OfflineIMAP 7.3.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v3.05, Python
Sudip Mukherjee wrote:
> I have also faced the same issue while trying to debug another issue and
> this happens when 'cert_fingerprint' is used. I had to use 'sslcacertfile'
> in my setup.
> Anyways, this has been reported upstream already at
>
Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20210105.00d395b+dfsg-2
Severity: normal
ERROR: Exceptions occurred during the run!
ERROR: Unknown SSL protocol connecting to host 'kitenet.net' for repository
'kite'. OpenSSL responded:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
Patch attached, tested lightly.
I noticed that rclone URIs are also nonstandard but since I don't have
any experience with rclone, I didn't try to fix that.
--
see shy jo
From 18f9ecfa6aa1a0ff580855e7ace87651529f64fd Mon Sep 17 00:00:00 2001
From: Joey Hess
Date: Wed, 20 Jan 2021 11:23:01
Package: git-remote-gcrypt
Version: 1.3-1
Severity: normal
rsync URIs
Note that the URI format for the rsync backend is, regretably,
non-standard.git-remote-gcrypt uses rsync://user@host:path
whereas plain rsync useseither
Upstream issue:
http://github-backup.branchable.com/todo/rate_limit_exceeded_immediately_on_first_API_request/
(Also I am no longer maintaining github-backup.)
--
see shy jo
signature.asc
Description: PGP signature
Daniel Kahn Gillmor wrote:
> thanks for the diagnosis, Joey! this looks like a change between the
> ctypes module between python 3.8 and 3.9. I'll fix it in python3-xdo,
> and hopefully that will resolve your problem.
Independent of getting this fixed, I think it's concerning that ctypes
falls
Daniel Kahn Gillmor wrote:
> I'm seeing comparable weird behavior, including the invocations of
> ldconfig and gcc, even if i don't see your particular failure. yikes.
> But, a simple file like this produces the same behavior (with ldconfig
> and gcc):
>
> ~~~
> #!/usr/bin/python3
> import xdo
>
Jameson Graef Rollins wrote:
> Hey, Joey. Sorry you're having trouble. What is the error when you try
> to execute "impass gui"? It should pop up a small context dialog
> window. That winodw is not appearing? Is there a python exception?
No gui. All I see it the output I pasted.
> What does
Daniel Kahn Gillmor wrote:
> this is odd, and it makes me think that there's some python module path
> failure happening. if it can't find the system xdo, maybe it also can't
> find the gobject introspection libraries that are used to interface with
> GTK?
>
> is it possible that this is being
Package: impass
Version: 0.12.2-1
Severity: normal
> impass gui
The xdo module is not found, so the 'xdo' paste method is not available.
Please install python3-xdo.
- exit 1
I do have that recommends installed. I did try to reinstall
it in case it was somehow broken. Real problem is that the gui
Antoine Beaupré wrote:
> --- a/etckeeper
> +++ b/etckeeper
> @@ -54,6 +54,10 @@ fi
> if [ ! -z "$AVOID_SPECIAL_FILE_WARNING" ]; then
> export AVOID_SPECIAL_FILE_WARNING
> fi
> +if [ -z "$LANG" ]; then
> + # Default to UTF8 encoding, if unset
> + export LANG=C.UTF-8
> +fi
That is
Package: etckeeper
Version: 1.18.15
Severity: normal
+if [ -z "en_GB.UTF-8" ]; then
+ # Default to UTF8 encoding, if unset
+ export LANG=C.UTF-8
+fi
I'm fairly sure it's impossible for this part of the debian patch to do
anything..
-- System Information:
Debian Release:
1 - 100 of 6094 matches
Mail list logo
