You are not logged in.
Pages: 1
I saw on https://buildmaster.archlinux32.org/bro … kages.html there is a nice feature showing a link to the upstream
Flyspray bug.
How are those made and managed? How can I report or add on, for instance for byacc: https://bugs.archlinux.org/task/55333?
Offline
There is a "state file" for each blocked package named "$pkgname.$git_revision.$git_mod_revision.$repository.blocked" whose content is shown on the website.
Literal content "wait for FS#12345" will be transformed to the respective link to flyspray (also the "wait for other-package and yet-another-package" will be transformed to links or marked red if the respective package(s) is/are not on the build-list).
So far, I created these files by hand via ssh.
Now, I wrote an email-interface:
Once your gpg-key is listed with the necessary permissions on the build master, you can send a gpg-encrypted, gpg-signed, hashcash-stamped email to "buildmaster (at) archlinux32 (dt) org" with content like
block: byacc.419eb1948f338676cf9fa99d261b34631612a782.4120aefd67048ed2e5bce7caf43e83d88a8165f1.community wait for FS#55331to get the respective package blocked for the respective reason.
Other possible actions, implemented so far are to "unblock" a package and to "stabilize" a package (e.g. move it from testing to its stable repository).
Comments/complaints welcome.
If you give me your gpg-key, I can enable for you blocking of packages (unblocking is needed fairly seldom, since the block only refers to a specific version of the package).
Cheers,
deepthought
Offline
This is a nice feature, really.
I'll send you my key via the email channel..
Offline
Ok, tried a block for python-redis, sent an email, hope it's ok.
I made an upstream bugreport and added a
https://github.com/andymccurdy/redis-py/issues/899">upstream</a>Offline
BTW: how often is the buildmaster udating the broken package page? And do I get an error message back from the mailserver or
a confirmation for the block?
Offline
fetchmail: every 3 minutes
website-update: every 2 minutes
removal of old files: every 10 minutes (then the broken packages which got fixed will vanish)
package updates: every 10 minutes
update of dependency-graphs: every 30 minutes
And no, you don't get confirmation or error messages, because I couldn't figure out how to do this without replying to spammers - I'm open for suggestions.
btw: Thanks for your contributions :-)
Cheers,
deep42thought
Offline
There is now an email-log available on the build master. It's somewhat spartanic, but it should do the job :-)
This log is updated directly by fetchmail, so there might be logged something successfully which is not apparent on other web-diagnostics yet.
Regards,
deep42thought
Offline
Ah. This is brilliant. Finally I can see my failed blocking attempts. :-)
Offline
Pages: 1