[Kernel-packages] [Bug 1568952] Comment bridged from LTC Bugzilla

2016-07-25 Thread bugproxy
--- Comment From pt...@cn.ibm.com 2016-07-25 02:41 EDT--- (In reply to comment #15) > On Mon, Jul 25, 2016 at 05:19:34AM -, bugproxy wrote: > > I don't think this bug should be fixed with makedumpfile. I think it > > should be fixed with kdump-tools. > > makedumpfile is the name of the

Re: [Kernel-packages] [Bug 1568952] Comment bridged from LTC Bugzilla

2016-07-24 Thread Steve Langasek
On Mon, Jul 25, 2016 at 05:19:34AM -, bugproxy wrote: > I don't think this bug should be fixed with makedumpfile. I think it > should be fixed with kdump-tools. makedumpfile is the name of the source package which builds kdump-tools. -- You received this bug notification because you are a

[Kernel-packages] [Bug 1568952] Comment bridged from LTC Bugzilla

2016-07-24 Thread bugproxy
--- Comment From pt...@cn.ibm.com 2016-07-25 01:18 EDT--- (In reply to comment #13) > Hello bugproxy, or anyone else affected, > > Accepted makedumpfile into xenial-proposed. The package will build now and > be available at >

[Kernel-packages] [Bug 1568952] Comment bridged from LTC Bugzilla

2016-06-09 Thread bugproxy
--- Comment From ru...@us.ibm.com 2016-06-09 12:28 EDT--- This bug has been quiet for a couple of months now. Just pinging for status. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu.

[Kernel-packages] [Bug 1568952] Comment bridged from LTC Bugzilla

2016-04-12 Thread bugproxy
--- Comment From hbath...@in.ibm.com 2016-04-12 07:47 EDT--- (In reply to comment #8) > Hello, > Hi Louis, > I am not against the modification but would like to understand better the > rationale behind this. According to the kernel doc we have : The rationale behind moving from maxcpus=1