Greetings all;
Does it work on debian arm?
Thanks!
Cheers, Gene Heskett.
I ran it on RPi4B RaspberryPi OS aarch64 Buster and got
:~ $ sudo dpkg -V
??5?????? c /etc/skel/.bashrc
??5?????? c /etc/elasticsearch/elasticsearch.yml
??5?????? /usr/lib/systemd/system/elasticsearch.service
??5?????? c /etc/init.d/elasticsearch
??5?????? c /etc/php/7.4/mods-available/apcu.ini
??5?????? c /etc/php/7.4/fpm/pool.d/www.conf
??5?????? c /etc/fail2ban/jail.d/defaults-debian.conf
??5?????? c /etc/apache2/apache2.conf
??5?????? c /etc/rsyslog.conf
??5?????? c /etc/sudoers.d/010_pi-nopasswd
??5?????? c /etc/redis/redis.conf
??5?????? c /etc/mail.rc
??5?????? c /etc/cron.d/certbot
??5?????? c /etc/default/useradd
??5?????? c /etc/email-addresses
??5?????? c /etc/exim4/passwd.client
??5?????? c /etc/dphys-swapfile
??5?????? c /etc/default/rpi-eeprom-update
??5?????? c /etc/login.defs
cheers
markus
On Friday 05 November 2021 10:22:11 Markus Weyermann wrote:
I ran it on RPi4B RaspberryPi OS aarch64 Buster and got
Thats exactly what I got, around 200 of them. And its quasi-random, I
ran it again on my raspian pi4b with a |wc -l and only got 87 next time.
I think the armhf and arm64 versions have a bug. The machine is otherwise fine and could be carveing steel 2 or 3 minutes after I got to it.
Takes that long to properly chuck up a workpiece.
That is not a commonly used option, but I used it because dpkg reported
an incomplete quite a few packages update this morning and I was looking
for the cause. But a sudo -E synaptic said its all fine, no errors, no fix-brokens etc.
Gene Heskett dijo [Fri, Nov 05, 2021 at 12:32:44PM -0400]:
On Friday 05 November 2021 10:22:11 Markus Weyermann wrote:Please do note that we (Debian) do not control how dpkg works on
I ran it on RPi4B RaspberryPi OS aarch64 Buster and got
RaspberryPi OS -- It is a Debian derivative, but it deviates quite a
bit from us.
I suggest you bring this issue up on the Raspberry Pi Foundation's
tracker, as it does not seem to be related to Debian.
I ran it on a clean Debian, on my Raspberry p400 (using one of the
Bullseye images from https://raspi.debian.net/), and got:
root@rpi-p400:~# dpkg -V
??5?????? c /etc/fuse.conf
??5?????? c /etc/default/raspi-firmware
root@rpi-p400:~#
I got similar results on my RockPro64, It is running
Armbain rather than pure Debian, but as far as I am
aware only the kernel comes from Armbain, and the rest
of userspace is from Debian. In other words it is probably
a Debian bug, and I don't think we can blame RaspberryPi OS
for it.
David Pottage wrote:
I got similar results on my RockPro64, It is running
Armbain rather than pure Debian, but as far as I am
aware only the kernel comes from Armbain, and the rest
of userspace is from Debian. In other words it is probably
a Debian bug, and I don't think we can blame RaspberryPi OS
for it.
No, Armbian has changes to assorted things in /etc which will
be reported by dpkg --verify. I have previously asked how to
reduce Armbian to just a custom kernel with vanilla Debian
everywhere else but didn't make much progress; the Armbian
people think their changes are improvements or bug fixes. (I
would be surprised if you see hundreds of files though.)
Here are my results for assorted ARM systems running variants
of Debian bullseye:
AWS cloud instance: 4 files in /etc, all modified by me.
QEMU vm: 1 file in /etc, modified by me.
32-bit ODROID NAS running Armbian: 19 files in /etc, about
5 modified by me, the others modified by Armbian.
ODROID C2 originally installed with "odrobian" but modified
by me to approach vanilla Debian with the odrobian kernel:
10 files in /etc, nearly all modified by me.
Nvidia Jetson Xavier NX with "Jetpack" installed over Debian:
20 files, about 3 modified by me.
I don't see any evidence that there is a problem with dpkg in
Debian; all of these derivatives make changes to configuration
files and similar which dpkg --verify correctly reports.
Cheers, Phil.
Note that I as the OP was using dpkg -V, not --verify. Might their be a difference?
Cheers, Gene Heskett.
Note that I as the OP was using dpkg -V, not --verify. Might their
be a difference?
Cheers, Gene Heskett.
Gene always check the -h vs --help or man page
dpkg --help
-V|--verify [<package>...] Verify the integrity of package(s).
package is optional and if not provided would check all packages
installed but it seems this is broken
BR
On Sunday 07 November 2021 03:19:09 deloptes wrote:
Note that I as the OP was using dpkg -V, not --verify. Might their
be a difference?
Cheers, Gene Heskett.
Gene always check the -h vs --help or man page
dpkg --help
-V|--verify [<package>...] Verify the integrity of package(s).
package is optional and if not provided would check all packages
installed but it seems this is broken
BR
well, I'm getting an almost sensible listing from the wintel boxes,
although the attributes reported are garbage in all cases of an error.
an ls -l shows the attributes correctly.
Hi,
El Sun, Nov 07, 2021 at 03:54:50PM -0500, Gene Heskett escribio:
On Sunday 07 November 2021 03:19:09 deloptes wrote:
Note that I as the OP was using dpkg -V, not --verify. Might
their be a difference?
Cheers, Gene Heskett.
Gene always check the -h vs --help or man page
dpkg --help
-V|--verify [<package>...] Verify the integrity of
package(s).
package is optional and if not provided would check all packages installed but it seems this is broken
BR
well, I'm getting an almost sensible listing from the wintel boxes, although the attributes reported are garbage in all cases of an
error. an ls -l shows the attributes correctly.
Please, read the manual.
The reported codes are not the file attributes, those are the status
of the performed checks. DPKG only has support for verifying the MD5,
so the result is always "??.??????" for a passed check and "??5??????"
for a failed check.
And the reported failed checks on Armbian are because the
"armbian-config" package modifies configuration files of other
packages.
Here, in a minimal Armbian install, I got:
??5?????? c /etc/skel/.bashrc
??5?????? c /etc/logrotate.d/apt
??5?????? c /etc/systemd/journald.conf
??5?????? c /etc/NetworkManager/NetworkManager.conf
??5?????? c /etc/default/rng-tools-debian
??5?????? c /etc/logrotate.d/alternatives
??5?????? c /etc/logrotate.d/dpkg
??5?????? c /etc/logrotate.d/aptitude
??5?????? c /etc/sysctl.conf
??5?????? c /etc/logcheck/violations.ignore.d/rng-tools
??5?????? c /etc/logcheck/ignore.d.server/rng-tools
??5?????? c /etc/default/rng-tools
??5?????? /etc/armbian-release
??5?????? /etc/default/armbian-ramlog.dpkg-dist
??5?????? /etc/default/armbian-zram-config.dpkg-dist
??5?????? c /etc/issue
??5?????? c /etc/issue.net
??5?????? c /etc/update-motd.d/10-uname
??5?????? c /etc/initramfs-tools/initramfs.conf
??5?????? c /etc/lightdm/lightdm-gtk-greeter.conf
As you see, all are configuration files modified by Armbian.
In the same hardware, a SID install reports all checks OK.
Have Fun!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 292 |
Nodes: | 16 (2 / 14) |
Uptime: | 188:49:33 |
Calls: | 6,616 |
Files: | 12,165 |
Messages: | 5,315,039 |