Re: strange behavior with i2c on raspberry pi 4

Supposedly the i2c bus you found is one of the HDMI lines, they use i2c for EDID and other information. My real time clock is on /dev/i2c-3. alex@aws:~:(13)> i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -

strange behavior with i2c on raspberry pi 4

Hello, i have a raspi 4 with a RTC. Since some days I have a problem with the i2c. The RTC is not found anymore. So i disconnect the RTC and do a i2cdetect -y 1 and it looks like: 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00: 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12

Bug#1066847: openssh: please consider disabling ssh-askpass-gnome on 32-bit during the time_t transition

Source: openssh Severity: wishlist Tags: patch X-Debbugs-Cc: debian-arm@lists.debian.org On the architectures affected by the 64-bit time_t transition, there is at least one cyclic build-dependency involving this package: openssh-server, gtk+3.0, at-spi2-core, dbus-broker, systemd, cryptsetup, lib

Bug#1066844: at-spi2-core: needs re-bootstrapping on armel, armhf for 64-bit time_t transition

Package: at-spi2-core Version: 2.51.90-3 Severity: important X-Debbugs-Cc: debian-arm@lists.debian.org Tags: patch at-spi2-core has a circular build-dependency on itself when tests are enabled, which makes its build-dependencies unsatisfiable (libglib2.0-dev depends on libglib2.0-0t64, but at-spi2

Re: python-cryptography vs. stainless steel ports

On 3/14/24 06:53, Thorsten Glaser wrote: Dixi quod… Is there a chance your team could fork the old python-cryptography source package (3.4.8-2) and do something like: Apparently, pyopenssl needs to also be forked as it wraps the above and, between 21.0.0-1 and 22.1.0-1, it began requiring the