Re: Git commit in all available branches

not do that, but applications should be pushed back unless there is some system level constraint preventing it. So I too would like a commit to all branches or sync all branches to this one command. Cheers, Jeff. -- Jeff Fearn jfe...@redhat.com Software Engineer Engineering Operations Red Hat, Inc

Re: Bugzilla email address sync

On 2/06/2016 08:37, Kevin Fenzi wrote: > On Wed, 01 Jun 2016 22:30:14 + > Christopher wrote: > >> Thanks. I opened: >> https://fedorahosted.org/fedora-infrastructure/ticket/5333 to address >> the issue more broadly (I figure this would be useful to others, and >>

Re: Bugzilla email address sync

On 2/06/2016 09:08, Bruno Wolff III wrote: > On Thu, Jun 02, 2016 at 09:05:55 +1000, > Jeff Fearn <jfe...@redhat.com> wrote: >> >> Hi, we expect to have SAML authentication working in Bugzilla 5, I'm >> implimenting it for Red Hat customer accounts ATM and also testi

Re: Removing aliases on bugzilla

On 15/08/16 03:38, Igor Gnatenko wrote: > Actually there is bug in bugzilla which prevents searching by text > which is written in some bug's alias. Is there a bug open for this? Cheers, Jeff. -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Hat Asia Pacific Pty Lt

Re: Injecting perl-devel and perl-generators build-requires

On 29/06/16 12:08, Kevin Kofler wrote: > Petr Pisar wrote: >> per Build Root Without Perl Fedora 25 change >> , I'm >> ready to implement the most visible part of this change. > > That change completely fails to account for the

Re: Injecting perl-devel and perl-generators build-requires

On 29/06/16 23:27, Petr Pisar wrote: > On 2016-06-29, Jeff Fearn <jfe...@redhat.com> wrote: >> I would like the perl team to consider taking this opportunity to remove >> non-standard behavior instead of adding more. The whole perl/perl-devel >> split was to make

Re: fedorahosted.org sunset is next week!

Is there a facility to redirect URLs to new sites? e.g. I'd like https://fedorahosted.org/publican/ to redirect to https://sourceware.org/publican/ Cheers, Jeff. signature.asc Description: OpenPGP digital signature ___ devel mailing list --

Re: fedorahosted.org sunset is next week!

On 23/02/2017 10:35 AM, Kevin Fenzi wrote: > On Thu, 23 Feb 2017 10:10:27 +1000 > Jeff Fearn <jfe...@redhat.com> wrote: > >> Is there a facility to redirect URLs to new sites? >> >> e.g. I'd like https://fedorahosted.org/publican/ to redirect to >> https://so

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 5/10/2016 12:36, Sam Varshavchik wrote: > Adam Williamson writes: > >> All dnf's 'nice features' aren't really there for a system update, are >> they? > > Well what are they there for, then? > >> You can use all of its nice features for doing other things. > > Like what? I thought

Re: Triaging RH Bugzilla and forwarding bugs upstream (Was: F24, small backward steps)

like our approach so far. Fedora is our biggest user community, so we can certainly make some Fedora specific changes to RH Bugzilla should it be required. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Hat Asia Pacific Pty Ltd http://dilbert.com/fast/200

Re: Triaging RH Bugzilla and forwarding bugs upstream (Was: F24, small backward steps)

ically is infeasible. It could probably be made light weight though. Say a button you click that copies in the OP from the bug, pops up a box for the clicker to enter some useful text in, includes a back link to RH BZ, and creates a bug upstream with that information. Cheers, J

Re: Triaging RH Bugzilla and forwarding bugs upstream (Was: F24, small backward steps)

On 19/09/16 20:27, Jóhann B. Guðmundsson wrote: > On 09/18/2016 10:16 PM, Jeff Fearn wrote: > >> Hi, we might be able to extend the External Trackers extension in RH >> Bugzilla to be able to create as >> well as sync bugs. > > Between which issue trackers

Re: Private Bugzilla bugs

On 25/10/16 22:49, den...@ausil.us wrote: > There has never been any policy against private bugs, and it's been > encouraged for security sensitive bugs from day 1. There is a lot of Red Hat > employees who default to private bugs FYI The warn on public create customization has been dropped

Re: Private Bugzilla bugs

t;less interesting" pre-release work. We would love to receive a well structured RFE from someone who has expertise in this area. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Hat Asia Pacific Pty Ltd http://dilbert.com/fast/2004-08-17/ PGP Fing

Re: Private Bugzilla bugs

On 22/10/2016 4:54 AM, Florian Weimer wrote: > On 10/21/2016 08:42 PM, Stephen John Smoogen wrote: >> We don't run the Bugzilla so the capability of who has it and who does >> not is not set by us. > > Bugzilla's group-based restrictions can be configured per product, so > it's easy to ask for

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On 14/10/2016 11:07 AM, Adam Williamson wrote: > On Thu, 2016-10-13 at 19:33 +1000, Jeff Fearn wrote: >>> That's not the intent of the fields as I understand them. 'severity' is >>> supposed to represent how bad the bug is, whereas 'priority' is >>> supposed to repres

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On 13/10/2016 4:56 PM, Adam Williamson wrote: > On Thu, 2016-10-13 at 14:40 +1000, Jeff Fearn wrote: >> On 13/10/16 14:02, Adam Williamson wrote: >>> On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote: >>>> On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson >>&

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

to get time allocated for this kind of stuff without a list of bugs to put in front of management. Every performance bug we have open will give us more leverage to spend some time optimizing the query engine. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Ha

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

e for priority but not true for severity. Severity is the external, i.e. reporters, weighting of the bug and you do not need to be in editbugs to set it. Cheers, Jeff. -- Jeff Fearn Senior Software Engineer PnT - DevOps - Development Red Hat Asia Pacific Pty L

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On 13/10/16 13:59, Adam Williamson wrote: > On Thu, 2016-10-13 at 10:45 +1000, Jeff Fearn wrote: >> On 13/10/16 10:37, Adam Williamson wrote:> 3. Bugzilla queries are (still) >> slow as hell (though not >> quite as bad >>> as when we wrote blockerbugs). >

Re: Announcing Bugzilla 5 Public Beta!

Hi Garret, On 02/05/17 15:10, Garrett Holmstrom wrote: > A couple minor web UI issues: > > Logging in with a FAS account redirects to > https://beta-bugzilla.redhat.com/None, which yields a 404 error. I've contacted Patrick about this and opened [1]. > Several of the custom fields on the

Re: bugzilla-requests recipient rejected

On 10/12/18 06:53, Florian Weimer wrote: > * Georg Sauthoff: > >> On Thu, Nov 01, 2018 at 05:10:37PM +, Alasdair G Kergon wrote: >>> If anyone spots any more, please open a ticket by emailing bugzilla-requests >>> @redhat.com and one of us will clean it up. >> >> I just tried that but my

Re: Bugzilla outage/upgrade delayed until 9 December 2018

On 1/12/18 01:45, Neal Gompa wrote: > On Fri, Nov 30, 2018 at 10:14 AM Ben Cotton wrote: >> >> The upgrade of bugzilla.redhat.com has been delayed a week. It will >> now be done on 9 December 2018 from 0:00 to 12:00 UTC. >> > > Aww, anyone know why? The release pipe line was unexpectedly

Re: Bugzilla outage/upgrade on 2 December 2018

On 27/11/18 19:45, Miroslav Suchý wrote: > Dne 26. 11. 18 v 16:57 Ben Cotton napsal(a): >> Bugzilla 5.0 introduces a new REST endpoint to replace XML-RPC and >> JSON-RPC. The XML-RPC and JSON-RPC APIs will remain available. > > Before someone jumps into porting their code to the new REST API (my

Re: Bugzilla outage/upgrade on 2 December 2018

On 27/11/18 12:13, Neal Gompa wrote: > On Mon, Nov 26, 2018 at 5:08 PM Jeff Fearn wrote: >> >> On 27/11/18 02:06, Emmanuel Seyman wrote: >>> * Neal Gompa [26/11/2018 11:01] : >>>> >>>> Out of curiosity, does anyone know where the source code for Re

Re: Bugzilla outage/upgrade on 2 December 2018

On 27/11/18 02:06, Emmanuel Seyman wrote: > * Neal Gompa [26/11/2018 11:01] : >> >> Out of curiosity, does anyone know where the source code for Red Hat >> Bugzilla actually is? I tried to find it a while ago, and even tried >> to send an email asking about it (with no response...). This variant

Re: Bug filing/triage/ownership policy for modules

On 20/12/19 06:22, Kevin Fenzi wrote: > On Thu, Dec 19, 2019 at 09:29:36AM +1000, Jeff Fearn wrote: >> On 19/12/19 01:00, David Cantrell wrote: >>> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote: >>>> Just FTR, for Red Hat Software Collections, we are (ab

Re: Bug filing/triage/ownership policy for modules

On 19/12/19 01:00, David Cantrell wrote: > On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote: >> Just FTR, for Red Hat Software Collections, we are (ab)using "Version" >> BZ field to track the SCL version (e.g. [1]), which in module >> terminology resembles stream. Maybe we could reuse

Re: Bug filing/triage/ownership policy for modules

On 19/12/2019 6:31 pm, Vít Ondruch wrote: > > Dne 19. 12. 19 v 0:29 Jeff Fearn napsal(a): >> On 19/12/19 01:00, David Cantrell wrote: >>> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote: >>>> Just FTR, for Red Hat Software Collections, we are (ab)using

Re: Spam on closed bugzilla reports

On 25/2/20 20:54, Richard W.M. Jones wrote: > On Mon, Feb 24, 2020 at 10:07:15PM -0800, Luya Tshimbalanga wrote: >> Hello team, >> >> It looks like spammers use closed bug report for their ads as seen >> in this one: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1644013 >> >> Can someone

Re: Fedora pagure confusion wrt EPEL

On 31/1/20 08:57, Fabio Valentini wrote: >> With pkgdb I could see who maintains which "branches" and which branches >> exist. With this new web UI, I don't find where I could take a look at >> who maintains which branch. For some packages I see socalled "members", a >> "main admin", an "admin",

Re: CPE Git Forge Decision

On 1/4/20 21:11, Bruno Wolff III wrote: > On Wed, Apr 01, 2020 at 12:39:21 +0200, >  Florian Weimer wrote: >> * Bruno Wolff, III: >> >>> RHEL is a special case, as CENTOS provides a free drop in replacement >>> and switching from CENTOS to Fedora shouldn't be much work. Is there >>> other

Re: Can a bugzilla issue be locked because of spam?

On 31/8/20 12:51, Christopher wrote: > This old issue (https://bugzilla.redhat.com/show_bug.cgi?id=1177202) > keeps receiving spam every couple of weeks from a different account. > I've been trying to flag the spam comments as spam, and remove the > flags they keep setting, and remove their CC as

Re: Can a bugzilla issue be locked because of spam?

On 1/9/20 05:28, Andy Mender wrote: > On Mon, 31 Aug 2020 at 14:22, Qiyu Yan wrote: > >> Fabio Valentini 于2020年8月31日周一 下午7:54写道： >>> I'm getting *pretty annoyed* with a similar (but way worse) issue as >> well: >>> https://bugzilla.redhat.com/show_bug.cgi?id=810049 >>> >>> It's worse because

Re: Can a bugzilla issue be locked because of spam?

On 31/8/20 21:54, Fabio Valentini wrote: > On Mon, Aug 31, 2020 at 4:51 AM Christopher > wrote: >> >> This old issue (https://bugzilla.redhat.com/show_bug.cgi?id=1177202) >> keeps receiving spam every couple of weeks from a different account. >> I've been trying to flag the spam comments as

Re: BZ + Firefox: browser freezes when choosing close reason?

On 6/9/20 00:09, Till Hofmann wrote: > > > On 9/5/20 3:17 PM, Zbigniew Jędrzejewski-Szmek wrote: >> On Sat, Sep 05, 2020 at 02:50:28PM +0200, Till Hofmann wrote: >>> Hi all, >>> >>> I'm having a weird problem with Bugzilla: Whenever I want to close an >>> issue and I click on the reason menu

Re: maybe a path forward for java and modules? [was Re: The Future of the Java Stack (also regarding ELN and RHEL)]

On 18/9/20 03:43, Matthew Miller wrote: > On Thu, Sep 17, 2020 at 01:30:26PM -0400, Stephen John Smoogen wrote: >> 'its broke' >> 'yes I know its broke.. I just need the header files' >> 'well I need it to work' 'well fix it yourself' >> 'no that is your job.. it says you OWN THE PACKAGE'. >> 'I

File XML-TreeBuilder-4.0.tar.gz uploaded to lookaside cache by jfearn

A file has been added to the lookaside cache for perl-XML-TreeBuilder: b1190367133fbf2807c488c2704588c4 XML-TreeBuilder-4.0.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org

[perl-XML-TreeBuilder] update to latest upstream

commit 1ccaacfd6806dbe9c3624c5434a8d52af7ace028 Author: Jeff Fearn jfe...@redhat.com Date: Thu Dec 2 14:10:05 2010 +1000 update to latest upstream .gitignore |1 + XML-TreeBuilder-NoExpand.patch | 267 perl-XML

RFC: cpanspec recursive building of deps & using docker

I have been working on modifications to cpanspec to support using --build and --follow at the same time [1][2]. Basically it creates a yum repo and builds and adds packages to that then installs them to make sure they work properly. Now that’s fine if you don’t mind installing everything on your