When it rains, it pours.

by on Apr.29, 2020, under Ultimate Edition

I just lost internet after Repostorm building thousands and thousands of debs. Luckily, I did not lose network access & pulled in all those perfect deb(s) it had made. Well over 5,000+ more of them. I rebooted all my networking equipment. Deleted everything from the server over a Million files it was in the middle of processing. Re-uploading now 10 files at a time (well over 100 GB), won’t take that long at 10 Gigabit. Set me back a minute.

I will use the new list of perfect debs to delete the files that needed to be processed, no sense in doing what it has already accomplished. On a positive note. I have been expanding what Repostorm can now fix for the past 2 days as it was finding new errors & writing software to fix them as well. Probably close to 1,000 lines of code. I will upload it to the server first install it and let it resume on a whole lot less packages.

I can promise you some Errors it will never fix. I have 0 intention of downloading the source package and re-building it for them. All of those packages you see listed there for example, I will not fix. I could, but I won’t. I would almost bet money it had fixed over 100,000 errors, before I got the shaft, not even thinking about warnings.

I have adjusted Repostorm to ignore “NFO’s” an “NFO” file is written by the original programmer to say: “Yes, I know the error / warning is there. Does not apply to me, sometimes that is accurate. I am going to take their word for it. The original programmer would have had to Lintian their package to find out, they are conscience to that fact. RepoStorm will go through here forward, Repostorm will view it as a error free, warning free package as perfect. Locally initially, as soon as I install the new Repostorm on the server downstairs.

To be honest, I should not trust them. If Repostorm can fix them, why not? Well that NFO file is still in their package and will cause Lintian to throw an error (not NFO) which ultimately, I would have to write code to catch that as well. I have already written more code then I like. I am smashing Error(s) & Warning(s) at monumental per-portions. You will see.

storage@storage:/media/PCIE4/process/.debs$ ls -la | wc -l
45120 files. That is very accurate(every single package is absolutely perfect), let’s go back a folder.

storage@storage:/media/PCIE4/process$ ls -la | wc -l
17309 (probably many of them I have already fixed). I should have snatched the error logs as well. My loss, Repostorm is running analytical processing again. Less then a hour, that I do not mind (other then each and every package has at least one error /warning). It is the “Days” that bother me.

Repostorm –extract will be done in minutes. Dual (PCIE raided 4.0 NVME drives) This is alot of data we are talking about. Snap gone.

Repostorm –fix will happen in minutes. The build process is slow, does not take advantage of multiple cores or hardware, want me to re-write their software too?

You will eventually get your paws on the software I am writing, hang in there. My goal is near perfection. Do you know what a “ali” file is? I did not know until today. Lintian will actually tell you the error or warning, all I have done is reverse engineer it. Straight up fixed it. Feed me that data.

        find "${EACH}/" -name "*.ali" -type f -exec chmod 0444 {} \; 2>/dev/null

My answer? “${EACH}/” is in a loop BTW, I watched that smash 706 warnings in just one package, BTW a perfect package now.

Understand the “Error” or “Warning” first, write software to circumvent it. That is what Repostorm is doing. I started writing in 2013, good luck catching up with me. Do not forget, I am re-building the Entire Ubuntu Repository. Err RepoStorm is.


BadPermissionsForAliFile () {
cat “${FILE}.deb.errors” | while read ERRORS
FOUND=$(echo “${ERRORS}” | grep “bad-permissions-for-ali-file”)
if [[ “${FOUND}” ]]; then
FILENAME=$(echo “${ERRORS}” | cut -d “:” -f3 | sed “s/ bad-permissions-for-ali-file //g”)
Encapsulate “Setting permissions of ${FTP} to 0444.”
chmod 0444 “${FTP}”

What is an ali file, still don’t know & do not care, I do know they have to have 0444. permissions, which means you can read the file, but can not write to it.

You may think
if [[ -f “${FTP}” ]]; then
would have been a smarter approach, it has already went though 2,800 lines of code at that point & won’t fail. I did add it. I do not want any possibility for failure. How many times does || exit exist? 47 times, I just checked against it.



Leave a Reply

You must be logged in to post a comment.

Back to top ↑