Hide Forgot
Description of problem: The current version of mozilla-adblockplus is disabled in Firefox 57, which is included in Rawhide, F27, F26, and soon F25. Version 3.0 of Adblock Plus appears to be compatible with FF57. Version-Release number of selected component (if applicable): mozilla-adblockplus-2.9.1-1.fc26.noarch (in F26) How reproducible: always
Created attachment 1353291 [details] spec for 3.0.1 I tried to update .spec. Seems it works for me. Note: to webpack nodejs package is required, I bundle it to .spec.
(In reply to Ivan Romanov from comment #1) > > I tried to update .spec. Seems it works for me. Yes, mozilla-adblockplus recompiled with attachment 1353291 [details] specs works with Firefox 57 just fine. Thanks! Any "official" movement in this matter. Koji records now the last successful activity for this package in June.
I suspect that the current assignee for this bug is no longer active. Koji shows that almost all builds back to at least early 2014 were made by either rathann (who just packaged the new mozilla-noscript) or niveusluna.
Any movement?
Sorry, I switched to uBlock Origin some time ago and don't have much interest in ABP. The review request for uBO is in bug 1518671. I may take a look at doing a new build of ABP just to make it work in FF57, but I'm pretty busy, so no promises.
Created attachment 1366460 [details] spec for 3.0.1 Update spec
Can't build with new spec in mock. It requires network connection. + npm install /builddir/build/SOURCES/webpack-3.8.1.tar.gz npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! network request to https://registry.npmjs.org/acorn failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: npm ERR! /builddir/.npm/_logs/2017-12-12T08_38_10_626Z-debug.log error: Bad exit status from /var/tmp/rpm-tmp.zKy4iv (%build) Bad exit status from /var/tmp/rpm-tmp.zKy4iv (%build)
(In reply to Dominik 'Rathann' Mierzejewski from comment #5) > I may take a look at doing a new build of ABP just to make it work in FF57, > but I'm pretty busy, so no promises. If you are unable or uninterested in maintaining this package, then please find a new (co)maintainer.
(In reply to Yaakov Selkowitz from comment #8) > (In reply to Dominik 'Rathann' Mierzejewski from comment #5) > > I may take a look at doing a new build of ABP just to make it work in FF57, > > but I'm pretty busy, so no promises. > > If you are unable or uninterested in maintaining this package, then please > find a new (co)maintainer. I'm a co-maintainer myself as you can check on https://src.fedoraproject.org/rpms/mozilla-adblockplus so I'm not sure why you're telling me this. I can remove myself from co-maintainers if that makes you happier.
(In reply to Dominik 'Rathann' Mierzejewski from comment #9) > I can remove myself from co-maintainers if that > makes you happier. Maybe, instead and for a benefit of users searching how to solve the problem, it should be noted instead that 'mozilla-ublock-origin' rpm package is available from current Fedora repos. This package does work with recent versions of Firefox and provides functionality analogous to 'mozilla-adblockplus'. I really cannot tell if making such switch "automatic" by suitable "Provides" and "Obsoletes" is a good idea or not.
(In reply to Michal Jaegermann from comment #10) > I really cannot tell if making such switch "automatic" by suitable > "Provides" and "Obsoletes" is a good idea or not. Definitely not. Adblock Plus is still maintained upstream; just our package is behind.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Not works in Fedora 29. In current state it's absolutely useless package.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.