<hannes>
it is while topkg tries to upload the tarball to mirage/charrua-core... by trying to authenticate user mirage to github -- which does not work.. if you have the cookie, it will use it instead.
<haesbaert>
hmm ok I'm looking for it
<haesbaert>
topkg docs don't mention it
<haesbaert>
oh foudn something on delegate
<haesbaert>
ack found it
<haesbaert>
1. opam-publish token stealing.
<haesbaert>
$(user) and the corresponding token will be used for
<haesbaert>
root)/plugins/opam-publish/$(user).token. If such a file exists,
<haesbaert>
generated for it that is keept in $(opam config
<haesbaert>
If you have already used opam-publish, an authorization token was
<haesbaert>
authentication.
contrapumpkin has joined #mirage
<haesbaert>
hannes: it's something else, I tried using a token now
<hannes>
haesbaert: in case you want to make it not possible for others to install 0.4*+, you can add something like available: false (or available: ocaml-version = 0) in these opam files.. imho it is worth doing
<haesbaert>
I think I don't have permissions to cut a release on github
<haesbaert>
since it is on the mirage repository
* hannes
does not know much about GitHub permissions
<hannes>
but: 14 seconds from now
<hannes>
haesbaert released teste at mirage/charrua-core
<haesbaert>
yeah I did that manually
<haesbaert>
so it seems I can cut a release
<haesbaert>
topkg says that if I don't have an opam token, and TOPKG auth env, it asks me for the password
<haesbaert>
I created a token and set env, same thing happened
<hannes>
did you try to pass some -v -v flags to your invocation of topkg?
<haesbaert>
hmm no, I can try now
<haesbaert>
nothing new
<haesbaert>
I mean nothing helpful
mort___ has quit [Quit: Leaving.]
<hannes>
haesbaert: still the same output?
mort___ has joined #mirage
<hannes>
from the topkg-delegate, I mean
<hannes>
increasing verbosity should give you some idea what it actually tried to do.. (I've no clue from the response you posted in which stage it is, and what it tried to achieve)
<haesbaert>
hannes: it outputs more stuff, but nothing extra for that stage
<haesbaert>
I've generated a token via opam publish now
<haesbaert>
leme try
argent_smith has quit [Quit: Leaving.]
<haesbaert>
fuck me it worked
<haesbaert>
THIS IS SO FREAKIN COOL
<hannes>
I told you hours ago ;) congrats!
<haesbaert>
release ALL THE TIME
<haesbaert>
hannes: you did, but there is no setup command anymore
<haesbaert>
you have to try to publish it the first time
<haesbaert>
so it's a chicken and egg
<haesbaert>
so I've made a dummy opam publish to generate the token
<hannes>
I had to tell it username + repository during some init stage
<hannes>
ic
<haesbaert>
yep, but there is no init stage anymore
<haesbaert>
opam-publish setup is no more
<haesbaert>
I tried TOPKG_TOPEN=haesbaert:tokencrap
<hannes>
pin an older version :)
<haesbaert>
?
<haesbaert>
I mean this is fucking brilliant
<hannes>
but hey, this is good that you did it... safe your token, you'll need it in the future :)