RPI submitqc and zsync

[aus9]

I was tempted to try an inport of submitqc to RPi to use it to generate .zsync files for planned submissions.

Naturally my coding skills get in the way (lack thereof)

On TC64 I have this

Code: [Select]

cat /usr/local/bin/submitqc  | grep zsync
    tce-load -i zsync
    [ $? != 0 ] && echo "Need zsync!" && exit 1
      DEPLIST="$DEPLIST zsync"
      # make zsync
      zsyncmake -u ${SCRIPT}.tcz ${SCRIPT}.tcz
  [ ! "$ARCH" = "armv7" ] && DEPLIST="$DEPLIST zsync binutils"
# make zsync file
makezsync() {
  LOG=/tmp/submitqc/zsync.$F
    echo "${YELLOW}$SCRIPT: skipping zsync creation - zsync support uncertain on armv7. Please \
submit zsync availability (script patches?) to maintainer."
    echo "$SCRIPT: $F.zsync not created; unknown whether armv7 has zsync support. Please report." \
  echo -n "${BLUE}$SCRIPT: $F creating new $F.zsync ${NORMAL}"
  rm -f ${F}.zsync
  zsyncmake -u ${F} ${F}
    echo -e "\n\t${RED}$SCRIPT: unknown error creating $F.zsync. Re-make manually.${NORMAL}"
    echo "${RED}Do NOT submit without zsync file.${NORMAL}"
    echo "$SCRIPT: unknown error creating $F.zsync. Re-make manually." > $LOG
    makezsync # create new zsync file, jic
It looks like it is a known issue zsync....but what is the most simplest solution without submitqc in Arm repos?

IE what command do I run to generate the file?

2) Based on above......should arm zsync have binutils as a dep?

thanks for reading

[aus9]

@Paul_123 or Juanito, if you agree, then the command I will use in my build script based on test below will be of the form

Code: [Select]

zsynmake TCE-name.tcz
Below I used the EXACT file below but re-generated a zync file. IMHO the diff is seeing a diff purely due to diff in the time generated. Its a TC64 file that will not be submitted to RPi. The original zsync file is under dir test/

Code: [Select]

tc@rpi:/tmp$ diff *zsync test/*zsync
Files lxterminal-doc.tcz.zsync and test/lxterminal-doc.tcz.zsync differ
tc@rpi:/tmp$ cat *zsync
zsync: 0.6.2
Filename: lxterminal-doc.tcz
MTime: Mon, 13 Apr 2020 02:52:26 +0000
Blocksize: 2048
Length: 12288
Hash-Lengths: 2,2,3
URL: lxterminal-doc.tcz
SHA-1: 0186431bd62989ad4e7fd8de3b6925107c54429c
####################################################
tc@rpi:/tmp$ cat test/*zsync
zsync: 0.6.2
Filename: lxterminal-doc.tcz
MTime: Mon, 13 Apr 2020 02:44:13 +0000
Blocksize: 2048
Length: 12288
Hash-Lengths: 2,2,3
URL: lxterminal-doc.tcz
SHA-1: 0186431bd62989ad4e7fd8de3b6925107c54429c
I can only spot ....MTime: Mon, 13 Apr 2020 02:52:26 +0000 as the diff
but I am impatient to proceed to submissions.

2) I ran that command without binutils loaded

so loaded binutils deleted tmp file and regenerated with no changes of merit

Code: [Select]

tc@rpi:/tmp$ rm -rf *zsync
tc@rpi:/tmp$ zsyncmake lxterminal-doc.tcz
No URL given, so I am including a relative URL in the .zsync file -
you must keep the file being served and the .zsync in the same public directory.
Use -u lxterminal-doc.tcz to get this same result without this warning.
tc@rpi:/tmp$ diff *zsync test/*zsync
Files lxterminal-doc.tcz.zsync and test/lxterminal-doc.tcz.zsync differ
3) attempting to put -u after zsyncmake causes command to hang!

[aus9]

unable to remove last post. There was something wrong with the time for fresh zsync file.
so I downloaded RPi zsync for aterm using my web browser, this is looking better

Code: [Select]

cat *zsync
zsync: 0.6.2
Filename: aterm.tcz
MTime: Mon, 06 Jan 2020 05:44:23 +0000
Blocksize: 2048
Length: 65536
Hash-Lengths: 2,2,4
URL: aterm.tcz
SHA-1: 65cb3c968e4c54740913ad85b283ce983edc7212

��X�L;gݺ���M�>��Ċ
                 <���޹rY��G�KO&�d�?� b�n�Ib��[��a���GO{������M��KT[�2����S�+�����D�V�Vw�&^�=x���y�mIf��+��&D��g�����4ޅ�AVQ�]��'kd�}�Fr����n��Ⱦ@����tc@rpi:/tmp$
#######################################################################################
tc@rpi:/tmp$ cd 2
tc@rpi:/tmp/2$ zsyncmake aterm.tcz
No URL given, so I am including a relative URL in the .zsync file - you must keep the file being served and the .zsync in the same public directory. Use -u aterm.tcz to get this same result without this warning.
tc@rpi:/tmp/2$ cat *zsync
zsync: 0.6.2
Filename: aterm.tcz
MTime: Sat, 22 Aug 2020 03:30:22 +0000
Blocksize: 2048
Length: 65536
Hash-Lengths: 2,2,4
URL: aterm.tcz
SHA-1: 65cb3c968e4c54740913ad85b283ce983edc7212

[dentonlt]

Hey, @aus9 - what become of this? Any word received from others?

Currently doing so submitqc updates, and I'll merge this in if it's required/working on ARM.

I think that bmarkus has said that the zsync files are auto-generated on the TC servers, however - we may not need the zsync code at all in the end. I'm digging for his post, and will cross-post here if I can find it.

[bmarkus]

Correct, zsync is generated at the server side, no need to upload it.

[dentonlt]

Correct, zsync is generated at the server side, no need to upload it.

Thanks for re-confirming, Bela.

Cheers ~