[aur-general] mantisbt blacklisted?
Helloes everyone, I was just trying to push a new version of mantisbt (1.3.1), which I adopted from alucryd. However, I get this odd message: remote: error: package is blacklisted: mantisbt remote: error: hook declined to update refs/heads/master To aur.archlinux.org:mantisbt ! [remote rejected] master -> master (hook declined) error: failed to push some refs to 'aur@aur.archlinux.org:mantisbt' Does anyone know, why this is happening, and why mantisbt would be blacklisted? Cheerios, David -- https://sleepmap.de
On 09/08/2016 10:26 AM, David Runge wrote:
Helloes everyone,
I was just trying to push a new version of mantisbt (1.3.1), which I adopted from alucryd.
However, I get this odd message:
remote: error: package is blacklisted: mantisbt remote: error: hook declined to update refs/heads/master To aur.archlinux.org:mantisbt ! [remote rejected] master -> master (hook declined) error: failed to push some refs to 'aur@aur.archlinux.org:mantisbt'
Does anyone know, why this is happening, and why mantisbt would be blacklisted?
Cheerios, David
Did it used to be in community? Because it isn't in the repos, but it is in the svntogit archive. (And if it was dropped from the repos, I thought the branch was supposed to be dropped.) -- Eli Schwartz
Did it used to be in community? Because it isn't in the repos, but it is Yes. in the svntogit archive. (And if it was dropped from the repos, I thought the branch was supposed to be dropped.) I see. Alucryd moved it to the AUR: https://bugs.archlinux.org/task/50206 I adopted it afterwards (also wrote the bug report).
-- Eli Schwartz
Cheerios, David -- https://sleepmap.de
On 2016-09-08 16:52:21 (+0200), David Runge wrote:
in the svntogit archive. (And if it was dropped from the repos, I thought the branch was supposed to be dropped.) I see. So... is there any way to get the package updated now?
Best, David -- https://sleepmap.de
On 09/08/2016 04:15 PM, David Runge wrote:
So... is there any way to get the package updated now?
I have no idea, I was just speculating as to the causes. And I speculate that the package was not properly purged from community, and the AUR configuration thinks it is still there and thus should not be allowed to be updated by a non-TU. You *will* need a TU to un-blacklist the package, whyever it happened. -- Eli Schwartz
On 08/09, Eli Schwartz via aur-general wrote:
On 09/08/2016 04:15 PM, David Runge wrote:
So... is there any way to get the package updated now?
I have no idea, I was just speculating as to the causes.
And I speculate that the package was not properly purged from community, and the AUR configuration thinks it is still there and thus should not be allowed to be updated by a non-TU.
You *will* need a TU to un-blacklist the package, whyever it happened.
Either the script that updates the blacklist hasn't been run yet, or the server it's run on hasn't been updated recently, but no TU can really help with this, alas. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
On 09/09/2016 06:05 PM, Johannes Löthberg via aur-general wrote:
Either the script that updates the blacklist hasn't been run yet, or the server it's run on hasn't been updated recently, but no TU can really help with this, alas.
Well, I don't know the exact implementation. :o But I assume e.g. lfleischer or bluewind can do it? Or at least investigate. ... It looked like it was deleted from the repos a while ago though! -- Eli Schwartz
Hey, On 08/09, David Runge wrote:
I was just trying to push a new version of mantisbt (1.3.1), which I adopted from alucryd.
However, I get this odd message:
remote: error: package is blacklisted: mantisbt remote: error: hook declined to update refs/heads/master To aur.archlinux.org:mantisbt ! [remote rejected] master -> master (hook declined) error: failed to push some refs to 'aur@aur.archlinux.org:mantisbt'
Does anyone know, why this is happening, and why mantisbt would be blacklisted?
Some mishaps meant that the old blacklist was still in effect even though it was no longer updated, it should work now! -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
Helloes, On 2016-09-10 23:27:59 (+0200), Johannes Löthberg wrote:
Some mishaps meant that the old blacklist was still in effect even though it was no longer updated, it should work now! It does! Thank you!
Best, David -- https://sleepmap.de
participants (3)
-
David Runge
-
Eli Schwartz
-
Johannes Löthberg