pending approval... #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
you may find it easier to use when debugging. it also doesn't scroll the output and instead logs all of it, just printing to terminal the step it's on.
> now i need to:
-figure out how to increment each "rel" and check for a 200 on that url on the highest rel value
-find a sane loop limit for the above (5? 10? 20? more or less depending on whether it's a maj/min/patch we're testing against?)
-fetch the new source and REPLACE the old source, or mv it to an archive. theoretically we would just need to copy in the urls.txt
and pur_src.$RELEASE.tar.xz (and optionally .sha256) somewhere, since it contains the sources inside. ask project lead on how she wants
archival of old releases done.
--extract each tarball- this won't be fun since they use different compressions upstream- anyways, extract to a working dir,
maybe build a sha256 of every file for a sort of manifest, and delete the upstream's tarball. also, for better compatibility
with the purbuild.sh script, rename package-1.2.3/ dirs to package/ (and modify the build script to reference that).
---snippet for checksums. NOTE: *BSD prefers the "tagged" format:
(SHA256 (test) = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855)
as opposed to the "GNU" format:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 test
but common convention is to use GNU notation (*BSD can generate GNU with sha256 -r, whereas GNU
can generate *BSD with sha256sum --tag).
import hashlib
file = 'file.bin'
infile = open(file,'rb')
hash = hashlib.sha256(infile.read()).hexdigest()
BSDhash = (('SHA256 ({0}) = {1}').format(file,hash))
GNUhash = (('{0} {1}').format(hash,file))
11:15:06 <@rainbowhash> r00t^2, dont touch chrootboot. the uh...half the point of this was me figuring out this crap. work on the release checker 11:15:19 < r00t^2> oh 11:15:21 < r00t^2> heh sorry 11:15:44 <@rainbowhash> i really appreciate your help but yeah... I'd still like to be the primary force here :P this is supposed to be a learning experience for me x3 11:15:55 <@rainbowhash> I'll shoot the script over to you once I"m done fumbling my way through WHOOPS. switching focus to the release checker.
still has weird behaviour with only two revision levels, but i think i'll figure it out. pretty sure it's the regex substitution- need a $ in there. i bet GNU's mirrors hate me for testing this shit.
RainbowHackerHorse
added a commit
that referenced
this pull request
Mar 14, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR for convenience pending @RainbowHackerHorse approval on issue #5