WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: extension audit script  (Read 19162 times)

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7126
Re: extension audit script
« Reply #60 on: February 11, 2012, 04:25:24 PM »
Thanks, I have not tended to the script in quite a while, but I will give it some attention soon.

Online coreplayer2

  • Hero Member
  • *****
  • Posts: 1629
Re: extension audit script
« Reply #61 on: February 12, 2012, 10:47:40 AM »
Thanks for the extension, I use it as a extension check whether submitted or not.     Are you making one for scm's? 

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7126
Re: extension audit script
« Reply #62 on: February 12, 2012, 12:00:37 PM »
Actually, with scms the checks would be fewer and simpler.  I will surely make a script for it soon.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7126
Re: extension audit script
« Reply #63 on: February 12, 2012, 04:47:22 PM »
I have not actually announced it, but I have let Robert Schumann, aka gutmensch, handle the main part of the tcz repo since I am occupied with the scms.  And the best help I can give overall is not to meddle and let him tend to it unless my help is solicited.

But I will update the audit script, I plan to simplify it a little, since it really does not need to try to verify .desktop files for one, as it is always giving false negatives on that.  I am considering adding in the 'check for library breakage' routine, but as it is now the data for that is made on my own mirror at home, and is not real time with ibiblio.  Which means it can do as much harm as good if someone has a good extension that will not break the repo but the data is old and falsely states that breakage would occur.  It is good for my personal use, and perhaps to run against existing stuff knowing that the data used may not be current.   But if not in real time with the repo, it doesn't need to be in the audit routine.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7126
Re: extension audit script
« Reply #64 on: February 12, 2012, 05:41:18 PM »
Updated, simplified dep check, removed suspicious directory perms check as there are many different dir perms for different apps expected - cannot check for them all, removed desktop file check as again unexpected entries are admissible.

Offline jls_legalize

  • Hero Member
  • *****
  • Posts: 1387
    • Core17
Re: extension audit script
« Reply #65 on: May 29, 2012, 05:02:08 PM »
The script doesn't recognizes me as package maintainer, maybe because there are spaces in my name?
legalize them                                     ThisIsNotlYnuCsfrOmscR-Etch

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7126
Re: extension audit script
« Reply #66 on: May 29, 2012, 05:59:55 PM »
It seems to work fine here, with the spaces

Code: [Select]

root@box:/home/tc# submitqc4
There are extensions without md5.txt files : mldonkey.tcz. Do you want to proceed and create md5.txt files for these and check the existing ones?  y/n  y
 
mldonkey.tcz is maintained by  jls_legalize <unsenepopiu at tin dot it>. You are  jls_legalize <unsenepopiu at tin dot it>.  Make sure the maintainer is aware you are updating his extension.
 
mldonkey.tcz  has some similarly named extensions in the repo.  Make sure yours does not    collide with these:
 
mldonkey.tcz
 
The following errors are found in mldonkey.tcz.info. No news is good news:
mldonkey.tcz is a valid tcz file.  Creating MD5 for mldonkey.tcz:
 
#######