Re: keep getting this error emailed to me on fez upload of module: Error reading META from your last upload
On 8/12/23 18:08, Bruce Gray wrote:
I tested your META6.json file with:
(cd t && raku -MTest -MTest::META -e 'plan 1; meta-ok();')
, and it looked good.
There is an open issue matching your problem.
There is mention of a fix; if I am reading it correctly, it is to
archive with `git archive` and upload with "fez's --file option",
instead of letting `fez` create the archive itself.
(If you try this, remember to advance your version number before
uploading!)
Whether or not that fix works for you, we would all benefit from you
noting your results on the ticket itself:
https://github.com/tony-o/raku-fez/issues/105
--
Hope this helps,
Bruce Gray (Util of PerlMonks)
yes this works bit of a pain but it's a workaround cool 😎bananas 😎
On Dec 8, 2023, at 00:00, Francis Grizzly Smit
wrote:
Ooops sorry my bad
On 8/12/23 16:55, Francis Grizzly Smit wrote:
Hi
keep getting this error emailed to me on fez upload of module: Error
reading META from your last upload, I have this
deployed
use v6;
use lib 'lib';
use Test;
use Gzz::Text::Utils;
plan 1;
constant AUTHOR = ?%*ENV;
if AUTHOR {
   require Test::META <&meta-ok>;
   meta-ok;
   done-testing;
}
else {
skip-rest "Skipping author test";
exit;
}
and it passes after a few corrections, but still on fez upload it
appears to pass but I get that email and it never updates what is
wrong??
my MEATA6.json is:
{
   "name" : "Gzz::Text::Utils",
   "description" : "A Raku module to provide text formatting
services to Raku programs. Including a \"sprintf\" alike function
\"Sprintf\" that copes better with Ansi highlighted text ...",
   "perl" : "6.d",
   "license" : "LGPL-3.0-or-later",
   "authors" : [
   "Francis Grizzly Smit "
   ],
   "depends": [
   "Terminal::Width",
   "Terminal::WCWidth"
   ],
   "provides" : {
   "Gzz::Text::Utils" : "lib/Gzz/Text/Utils.rakumod"
   },
   "source-url" : "https://github.com/grizzlysmit/Gzz-Text-Utils.git";,
   "support" : {
   "source" : "https://github.com/grizzlysmit/Gzz-Text-Utils.git";,
   "email" : "griz...@smit.id.au",
   "bugtracker":
"https://github.com/grizzlysmit/Gzz-Text-Utils/issues";
   },
   "auth": "zef:grizzlysmit",
   "version" : "0.1.13",
   "tags" : [ "text", "formatting", "sprintf clone", "ANSI",
"highlighted" ],
 "test-depends": [
 ]
}
--
.~. There are many things that I love
/V\ but God Comes way above all else
/( )\Francis (Grizzly) Smit
^^-^^http://www.smit.id.au/
--
.~. There are many things that I love
/V\ but God Comes way above all else
/( )\Francis (Grizzly) Smit
^^-^^http://www.smit.id.au/
Your idea on how to detect random directory names
Hi All, I am writing a clean up routine to relive my spot back ups of junk in Blink browser directories that are meaningless to a backup and that take up a lot of space. These directories are long and have random characters for files names, such as "adcocjohghhfpidemphmcmlmhnfgikei" How who you go about figuring out who was random and who was not. I am thinking first the length and then the absence of capitol letters and spaces and underscores. Your take? Many thanks, -T $ ls ~/.config/BraveSoftware/Brave-Browser adcocjohghhfpidemphmcmlmhnfgikei GrShaderCache afalakplffnnnlkncjhbmahjfjhmlkal hyphen-data aoojcmojmmcbpfgoecoadbdpnagfchel iblokdlgekdjophgeonmanpnjihcjkjj apfggiafobakjahnkchiecbomjgigkkn InterventionPolicyDatabase AutofillRegex iodkpdagapdfkphljnddpjlldadblomo AutofillStates'Last Version' bfpgedeaaibpoidldhjcknekahbikncb 'Local State' biahpgbdmdkfgndcmfiipgcebobojjkp MEIPreload BraveWalletmfddibmblmbccpadfndgakiopmmhebop BrowserMetrics-spare.pma NativeMessagingHosts cdbbhgbmjhfnhnmgeddbliobbofkgdhe OnDeviceHeadSuggestModel CertificateRevocation oofiananboodjbbmdelgdommihjbkfag CertificateTransparencyOptimizationHints cffkpbalmllkdoenhmdmpbkajipdjfam OriginTrials chrome_shutdown_ms.txt persisted_first_party_sets.json ClientSidePhishing PKIMetadata component_crx_cache 'Safe Browsing' CrashpadMetrics-active.pma'Safe Browsing Cookies' 'Crash Reports''Safe Browsing Cookies-journal' 'Crowd Deny'SafetyTips Defaultsegmentation_platform Dictionaries ShaderCache ECSerivceProvidersConfig SSLErrorAssistant extensions_crx_cache 'Subresource Filter' FileTypePolicies TLSDeprecationConfig 'First Run' tor Floc TpcdMetadata gccbbckogglekeggclmmekihdgdpdgoe Variations gkboaolpopklhgplhaaiboijnklogmbc 'Webstore Downloads' GraphiteDawnCache WidevineCdm Greaselion ZxcvbnData } -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
Re: Your idea on how to detect random directory names
> On Dec 9, 2023, at 00:37, ToddAndMargo via perl6-users > wrote: > > Hi All, > > I am writing a clean up routine to relive my spot back ups > of junk in Blink browser directories that are meaningless to > a backup and that take up a lot of space. > > These directories are long and have random characters > for files names, such as "adcocjohghhfpidemphmcmlmhnfgikei" > > How who you go about figuring out who was random and > who was not. I am thinking first the length and then > the absence of capitol letters and spaces and underscores. > > Your take? --snip-- # Brave Browser temp directories: exactly 32 contiguous lowercase alpha characters. my $brave_junk_directories_re = / ^ <[a..z]> ** 32 $ /; my %to_skip = @filenames.grep($brave_junk_directories_re).Set; -- Hope this helps, Bruce Gray (Util of PerlMonks)
Re: Your idea on how to detect random directory names
On Sat, Dec 9, 2023 at 2:06 AM Bruce Gray
wrote:
>
>
> > On Dec 9, 2023, at 00:37, ToddAndMargo via perl6-users <
> perl6-us...@perl.org> wrote:
> >
> > Hi All,
> >
> > I am writing a clean up routine to relive my spot back ups
> > of junk in Blink browser directories that are meaningless to
> > a backup and that take up a lot of space.
> >
> > These directories are long and have random characters
> > for files names, such as "adcocjohghhfpidemphmcmlmhnfgikei"
> >
> > How who you go about figuring out who was random and
> > who was not. I am thinking first the length and then
> > the absence of capitol letters and spaces and underscores.
> >
> > Your take?
>
>
> --snip--
>
> # Brave Browser temp directories: exactly 32 contiguous lowercase alpha
> characters.
> my $brave_junk_directories_re = / ^ <[a..z]> ** 32 $ /;
> my %to_skip = @filenames.grep($brave_junk_directories_re).Set;
>
>
I know this really wasn't mentioned clearly, but as a precaution you might
also want to consider filtering on whether the inode is referencing a file
or not:
my @to_skip = dir(".", test => { .IO.d && / ^ <[a..z]> ** 32 $ / } ) ;
If that possibility doesn't exist, then I personally would use:
my @to_skip = dir(".", test => { / ^ <[a..z]> ** 32 $ / } ) ;
As always, there's more than one way to skin a cat.
~Paul
--
__
:(){ :|:& };:
