Tiny Core Base > Corepure64
tcz shipping delay
Vaguiner:
Hello, I have sent to tcesubmit@gmail.com two packages; fuse-zip and archivemount. I tried to correctly follow all the tips for sending the package, as well as the proper verification of dependencies, licenses, strip, binaries source code and etc, but I never got an email response.
I believe it was sent to the spam folder.
I've also noticed other different people complaining that packet submissions are never answered. If there is some undocumented and unclear reason (eg the package is 1kb heavier so I won't accept it. or I won't accept it because it was submitted by an unknown person who may be sending viruses) it would be good to explain so we can work on this answer, yeah It's simply impossible to resolve a question you don't know the reason for.
Rich:
Hi CardealRusso
It may take a week or two for your submission to be processed.
From the link you posted:
--- Quote --- ... Submit extension:
- tar all necessary and optional files, example:
tar cvzf rogue.tar.gz rogue/
- attach and email to tcesubmit@gmail.com
- note: encryption of the extension attachment is not required ...
--- End quote ---
I recommend encrypting the extension to prevent email providers from
flagging/blocking extensions because they looked inside the attachment
and saw something they did not like.
You can encrypt your extension like this:
--- Code: ---bcrypt extension.tar.gz
--- End code ---
Then enter tinycore at the Encryption key: prompt.
Or you can use this one liner:
--- Code: ---yes tinycore | bcrypt extension.tar.gz
--- End code ---
Juanito:
I checked tcesubmit 2 days ago, I’ll check the spam tomorrow - if the submission wasn’t bcrypted it’s possible it didn’t even make the spam.
Vaguiner:
--- Quote from: Rich on June 17, 2023, 09:16:27 AM ---flagging/blocking extensions because they looked inside the attachment
--- End quote ---
--- Quote from: Juanito on June 17, 2023, 12:15:56 PM ---...if the submission wasn’t bcrypted it’s possible it didn’t even make the spam.
--- End quote ---
yes i indeed forgot to bcrypt the files
however the files were not detected by google's anti-virus, since, if it were, I myself would be warned that the email I sent contained a virus, however the message sent only states that the file was scanned.
https://support.google.com/mail/answer/25760?hl=en#zippy=%2Cvirus-in-an-email-sent-to-you%2Cvirus-in-an-email-youre-sending
So I assume it went to the spam box or was never read.
In fact, according to the google article mentioned, the file is scanned before the email is sent, when it is attached in the draft, so it would never be supposedly sent if it found any problems.
aus9:
Hi Rich wrote
--- Quote ---I recommend encrypting the extension to prevent email providers from flagging/blocking extensions because they looked inside the attachment and saw something they did not like.
--- End quote ---
I am guilty of that...but I think I can remember someone like bmarkus or similar statue saying no longer required.
Another way to submit is upload your tarball to a host site and email the link?
This is sometimes useful as gmail has an attachment limit of sending of 25Mb
https://emailanalytics.com/gmail-attachment-size-limit/
Navigation
[0] Message Index
[#] Next page
Go to full version