Hi guys,
with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package.
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
Thanks, Niels
Hi Niels,
I am not sure whether all other SIGs include debuginfo repo. Any way we will look into this.
Thanks,
--Humble
On Mon, Feb 9, 2015 at 10:39 PM, Niels de Vos ndevos@redhat.com wrote:
Hi guys,
with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package.
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
Thanks, Niels _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 02/09/2015 06:09 PM, Niels de Vos wrote:
Hi guys,
with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package.
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
Thanks, Niels
Niels,
Thanks for reporting this. Looks like it is a sepc file issue. Ideally we should have build debug packages too (similar to Fedora koji builds) . I am going look in to this. You are also welcome to send a patch for this as you are a RPM expert :)
Thanks, Lala
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Mon, Feb 09, 2015 at 06:49:13PM +0100, Lalatendu Mohanty wrote:
On 02/09/2015 06:09 PM, Niels de Vos wrote:
Hi guys,
with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package.
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
Thanks, Niels
Niels,
Thanks for reporting this. Looks like it is a sepc file issue. Ideally we should have build debug packages too (similar to Fedora koji builds) . I am going look in to this. You are also welcome to send a patch for this as you are a RPM expert :)
Hi Lala,
the -debuginfo packages get build in CBS [1], they 'only' need to get put in a debuginfo repository.
Thanks, Niels
Yeah, it just need a repo :) . As mentioned in my earlier thread, we need to check what other SIGs follows and act.
--Humble
On Mon, Feb 9, 2015 at 11:42 PM, Niels de Vos ndevos@redhat.com wrote:
On Mon, Feb 09, 2015 at 06:49:13PM +0100, Lalatendu Mohanty wrote:
On 02/09/2015 06:09 PM, Niels de Vos wrote:
Hi guys,
with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package.
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
Thanks, Niels
Niels,
Thanks for reporting this. Looks like it is a sepc file issue. Ideally
we
should have build debug packages too (similar to Fedora koji builds) . I
am
going look in to this. You are also welcome to send a patch for this as
you
are a RPM expert :)
Hi Lala,
the -debuginfo packages get build in CBS [1], they 'only' need to get put in a debuginfo repository.
Thanks, Niels
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Hi,
On 09/02/15 19:17, Humble Devassy Chirammal wrote:
Yeah, it just need a repo :) . As mentioned in my earlier thread, we need to check what other SIGs follows and act.
--Humble
For info mash does generate them already: http://cbs.centos.org/repos/storage7-testing/x86_64/debug/
Thanks Thomas!
--Humble
On Tue, Feb 10, 2015 at 1:00 AM, Thomas Oulevey thomas.oulevey@cern.ch wrote:
Hi,
On 09/02/15 19:17, Humble Devassy Chirammal wrote:
Yeah, it just need a repo :) . As mentioned in my earlier thread, we need to check what other SIGs follows and act.
--Humble
For info mash does generate them already: http://cbs.centos.org/repos/storage7-testing/x86_64/debug/
-- Thomas.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 02/09/2015 08:30 PM, Thomas Oulevey wrote:
Hi,
On 09/02/15 19:17, Humble Devassy Chirammal wrote:
Yeah, it just need a repo :) . As mentioned in my earlier thread, we need to check what other SIGs follows and act.
--Humble
For info mash does generate them already: http://cbs.centos.org/repos/storage7-testing/x86_64/debug/
Cool, I missed the debug directory in the cbs/repos. We will find a way to put them in to build logs.
Thanks, Lala
On 02/09/2015 07:17 PM, Humble Devassy Chirammal wrote:
Yeah, it just need a repo :) . As mentioned in my earlier thread, we need to check what other SIGs follows and act.
Yup, it just needs a repo. BTW as a SIG we have the freedom to put packages in to repos as along as it is inline to the SIG user story and we can choose packages which works for it :)
Thanks, Lala
On 09/02/15 17:09, Niels de Vos wrote:
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
We will need a debuginfo repo for each repo ( devel / testing / stable ) in the release file. And I believe they need to be named in a specific manner for yum and its tools to treat it as a debuginfo repo.
At the moment, the signing services do not pull in debuginfo files at all. so we can either push them unsigned ( if we really have to ) and/or I need to go away do some work to make the signing process include debugs as well ( if can wait a few days ).
As a secondary goal, we should look at pushing up a -release rpm template that other SIGs can also use, that sets a reasonable default for the various yum repo locations, docs pointers etc.
On Tue, Feb 10, 2015 at 09:20:51AM +0000, Karanbir Singh wrote:
On 09/02/15 17:09, Niels de Vos wrote:
Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well.
We will need a debuginfo repo for each repo ( devel / testing / stable ) in the release file. And I believe they need to be named in a specific manner for yum and its tools to treat it as a debuginfo repo.
At the moment, the signing services do not pull in debuginfo files at all. so we can either push them unsigned ( if we really have to ) and/or I need to go away do some work to make the signing process include debugs as well ( if can wait a few days ).
I'm not in a hurry with this, take your time. The packages are available in the CBS, and that works for me for now.
As a secondary goal, we should look at pushing up a -release rpm template that other SIGs can also use, that sets a reasonable default for the various yum repo locations, docs pointers etc.
Yes, that would be good. If other upstream projects get bug reports from CentOS SIG users, it helps to have an easy way of getting the -debuginfo packages.
Thanks, Niels