From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Mon, 16 Sep 2024 00:29:49 +0200 [thread overview]
Message-ID: <Zudf3UO25m5J9acr@kern> (raw)
In-Reply-To: <5ad461dd-6122-ae67-5609-0a39d5a64fe1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2756 bytes --]
Am Sat, Sep 14, 2024 at 02:46:35PM -0500 schrieb Dale:
> I was running the command again and when I was checking on it, it
> stopped with this error.
>
>
>
> File "/root/dh", line 1209, in <module>
> main()
> File "/root/dh", line 1184, in main
> directory_hash(dir_path, '', dir_files, checksums)
> File "/root/dh", line 1007, in directory_hash
> os.path.basename(old_sums[filename][1])
> ~~~~~~~~^^^^^^^^^^
> KeyError: 'Some Video.mp4'
What was the exact command with which you ran it?
Apparently the directory has a file 'Some Video.mp4', which was not listed
in an existing checksum file.
I also noticed a problem recently which happens if you give dh a directory
as argument which has no checksum file in it. Or something like it, I can’t
reproduce it from memory right now. I have been doing some refactoring
recently in order to get one-file-per-tree mode working.
> I was doing a second run because I updated some files. So, it was
> skipping some and creating new for some new ones. This is the command I
> was running, which may not be the best way.
>
>
> /root/dh -c -f -F 1Checksums.md5 -v
Yeah, using the -c option will clobber any old checksums and re-read all
files fresh. If you only changed a few files, using the -u option will
drastically increase speed because only the changed files will be read.
Use the -d option to clean up dangling entries from checksum files.
> Also, what is the best way to handle this type of situation. Let's say
> I have a set of videos. Later on I get a better set of videos, higher
> resolution or something. I copy those to a temporary directory then use
> your dmv script from a while back to replace the old files with the new
> files but with identical names. Thing is, file is different, sometimes
> a lot different. What is the best way to get it to update the checksums
> for the changed files? Is the command above correct?
dh has some smarts built-in. If you changed a file, then its modification
timestamp will get udpated. When dh runs in -u mode and it finds a file
whose timestamp is newer than its associated checksum file, that means the
file may have been altered since the creation of that checksum. So dh will
re-hash the file and replace the checksum in the checksum file.
> I'm sometimes pretty good at finding software bugs. But hey, it just
> makes your software better. ;-)
Me too, usually. If it’s not my software, anyways. ^^
But I think you may be the first other of that tool other than me.
--
Grüße | Greetings | Salut | Qapla’
Someone who eats oats for 200 years becomes very old.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-15 22:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04 0:12 ` [gentoo-user] " Grant Edwards
2024-09-04 0:39 ` Dale
2024-09-04 4:16 ` corbin bird
2024-09-06 20:15 ` Dale
2024-09-06 23:17 ` Michael
2024-09-07 3:02 ` Dale
2024-09-07 22:12 ` Wols Lists
2024-09-08 1:59 ` Dale
2024-09-08 13:32 ` Michael
2024-09-08 9:15 ` Michael
2024-09-08 20:19 ` Wol
2024-09-04 7:53 ` Raffaele Belardi
2024-09-04 4:26 ` [gentoo-user] " Eli Schwartz
2024-09-04 10:48 ` [gentoo-user] " Dale
2024-09-04 11:05 ` Frank Steinmetzger
2024-09-04 11:21 ` Dale
2024-09-04 15:57 ` Peter Humphrey
2024-09-04 19:09 ` Grant Edwards
2024-09-04 21:08 ` Frank Steinmetzger
2024-09-04 21:22 ` Grant Edwards
2024-09-04 21:53 ` Dale
2024-09-04 22:07 ` Grant Edwards
2024-09-04 22:14 ` Dale
2024-09-04 22:38 ` Michael
2024-09-05 0:11 ` Dale
2024-09-05 8:05 ` Michael
2024-09-05 8:36 ` Dale
2024-09-05 8:42 ` Michael
2024-09-05 10:53 ` Dale
2024-09-05 11:08 ` Michael
2024-09-05 11:30 ` Dale
2024-09-05 18:55 ` Frank Steinmetzger
2024-09-05 22:06 ` Michael
2024-09-06 0:43 ` Dale
2024-09-06 12:21 ` Michael
2024-09-06 21:41 ` Frank Steinmetzger
2024-09-07 9:37 ` Michael
2024-09-07 16:28 ` Frank Steinmetzger
2024-09-07 17:08 ` Mark Knecht
2024-09-14 19:46 ` Dale
2024-09-15 22:29 ` Frank Steinmetzger [this message]
2024-09-16 10:24 ` Dale
2024-09-07 22:48 ` Wols Lists
2024-09-08 9:37 ` Michael
2024-09-05 9:08 ` Frank Steinmetzger
2024-09-05 9:36 ` Michael
2024-09-05 10:01 ` Frank Steinmetzger
2024-09-05 10:59 ` Dale
2024-09-04 14:21 ` Grant Edwards
2024-09-04 11:37 ` Dale
2024-09-04 14:23 ` Grant Edwards
2024-09-04 15:58 ` Peter Humphrey
2024-09-04 19:28 ` Dale
2024-09-25 20:41 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zudf3UO25m5J9acr@kern \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox