While I'm fine with this, it does create a split between where most CentOS bugs are filed and where the scl-sig ones are filed.
Perhaps an excuse to revisit unifying the bug reporting?
On Friday, November 6, 2015, Honza Horak hhorak@redhat.com wrote:
Sorry for late response, I don't think we need anything on bugs.centos.org, we already have this space: https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org
Honza
On 11/05/2015 12:37 PM, Karanbir Singh wrote:
Do we need a SCLo specific section on bugs.centos.org- and maybe get Honza setup as primary developer for that ?
regards,
-------- Forwarded Message -------- Subject: Re: [scl.org] bug reporting for slcs ? Date: Thu, 5 Nov 2015 11:38:03 +0100 From: Jarek Polok Jaroslaw.Polok@cern.ch Organisation: CERN To: sclorg@redhat.com
Since the problem is sclo-specific [ upstream package not affected ], submitted bug report here:
https://bugs.centos.org/view.php?id=9705
(as 'Project Buildsys' category 'general')
Cheers
Jarek
On 10/29/2015 04:07 PM, Jarek Polok wrote:
Hi,
Where bugs for SCLo collections are to be reported ?
bugs.centos.org does not seem to have SCLo project defined ?
We have just seen a (minor) bug in rh-ruby22 collection (wrong shebang paths in some tools)
My understanding is that that collection is a rebuilt of upstream RH one: in that case the bug is to be reported to CentOS/SCLo or to RH directly ?
Thanks
Jarek
__
_ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _
SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel