[Ipmitool-devel] ipmitool 1.8.13 release proposal

Discussion:

Jim Mankovich

2013-07-17 16:19:23 UTC

All,

It has been almost a year since 1.8.12 was released so I think it is time to schedule
a release of 1.8.13. I would like to propose posting a release candidate for 1.8.13 in
early August with a final 1.8.13 release sometime in September if possible. If you
have any ipmitool changes you feel are needed in 1.8.13 and are not yet in the TOB
CVS repository, please speak up so we can evaluate whether or not the changes
can make it into an Aug/Sept release of 1.8.13. I would like to do the first candidate
release in the first week of August if possible.

Thanks for your support,
Jim

--
-- Jim Mankovich | ***@hp.com (US Mountain Time) --

Dan Gora

2013-07-17 18:46:50 UTC

Permalink

Hi Jim,

I posted 6 patches back on Apr 29, 2013 to fix the issues we had with
removing the -Wno-unused-result flag from CFLAGS that never got
reviewed or acked or anything. This was issue #3608759, now is issue
#65 http://sourceforge.net/p/ipmitool/patches/65/.

(What happened with the whole bug/patch tracker anyways? It was awful
before, but they managed to make it much worse...) .

I couldn't attach them to the original issue, so I just posted them to
ipmitool-devel, but maybe no one saw them.

There still does not seem to be any way to attach these new patches to
the issue tracker.. sigh...

So, anyways, I'd still like to get the last part of issue #65
resolved. The problem is that the -Wno-unused-result flag is that it
is not a valid flag for slightly older versions of gcc (I was testing
gcc 4.3.3), so it breaks the compilation, which is bad...

These patches clean up the associated warnings that were produced on
Ubuntu when I removed the flag, so that the code will continue to
compile cleanly without the flag.

If anyone would like me to repost the patches I can, but you should be
able to search them out on the mailing list by searching for ID
3608759 from April 29.

thanks
dan

Post by Jim Mankovich
All,
It has been almost a year since 1.8.12 was released so I think it is time to schedule
a release of 1.8.13. I would like to propose posting a release candidate for 1.8.13 in
early August with a final 1.8.13 release sometime in September if possible. If you
have any ipmitool changes you feel are needed in 1.8.13 and are not yet in the TOB
CVS repository, please speak up so we can evaluate whether or not the changes
can make it into an Aug/Sept release of 1.8.13. I would like to do the first candidate
release in the first week of August if possible.
Thanks for your support,
Jim
--
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Zdenek Styblik

2013-07-17 19:06:22 UTC

Permalink

Post by Dan Gora
Hi Jim,
I posted 6 patches back on Apr 29, 2013 to fix the issues we had with
removing the -Wno-unused-result flag from CFLAGS that never got
reviewed or acked or anything. This was issue #3608759, now is issue
#65 http://sourceforge.net/p/ipmitool/patches/65/.

As it says in comments - this one particular thing is on hold. Jim
will provide details, if necessary.

Post by Dan Gora
(What happened with the whole bug/patch tracker anyways? It was awful
before, but they managed to make it much worse...) .

Whole site got migrated. Compla...compliments to the SF.net crew, please.

Post by Dan Gora
I couldn't attach them to the original issue, so I just posted them to
ipmitool-devel, but maybe no one saw them.

There is a zip file attached. And if you haven't created version #2 of
it, it should have patches you're talking about.

Z.

Post by Dan Gora
There still does not seem to be any way to attach these new patches to
the issue tracker.. sigh...
So, anyways, I'd still like to get the last part of issue #65
resolved. The problem is that the -Wno-unused-result flag is that it
is not a valid flag for slightly older versions of gcc (I was testing
gcc 4.3.3), so it breaks the compilation, which is bad...
These patches clean up the associated warnings that were produced on
Ubuntu when I removed the flag, so that the code will continue to
compile cleanly without the flag.
If anyone would like me to repost the patches I can, but you should be
able to search them out on the mailing list by searching for ID
3608759 from April 29.
thanks
dan

--
Dan Gora
Software Engineer
Adax, Inc.
Av Dona Maria Alves, 1070 Casa 5
Centro
Ubatuba, SP
CEP 11680-000
Brasil
Tel: +55 (12) 3833-1021 (Brazil and outside of US)
: +1 (510) 859-4801 (Inside of US)
: dan_gora (Skype)
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Dan Gora

2013-07-17 19:11:48 UTC

Permalink

On Wed, Jul 17, 2013 at 4:06 PM, Zdenek Styblik

Post by Zdenek Styblik

Post by Dan Gora
I posted 6 patches back on Apr 29, 2013 to fix the issues we had with
removing the -Wno-unused-result flag from CFLAGS that never got
reviewed or acked or anything. This was issue #3608759, now is issue
#65 http://sourceforge.net/p/ipmitool/patches/65/.

As it says in comments - this one particular thing is on hold. Jim
will provide details, if necessary.

I read the comments. It was on hold because of the warnings generated
when the flag was removed. That's why I created the patches to fix
the warnings..

Unfortunately there was/is no way to attach these patches to the original issue.

Post by Zdenek Styblik

Post by Dan Gora
(What happened with the whole bug/patch tracker anyways? It was awful
before, but they managed to make it much worse...) .

Whole site got migrated. Compla...compliments to the SF.net crew, please.

lol.. compliments are not exactly what I have in mind for them...

Post by Zdenek Styblik
There is a zip file attached. And if you haven't created version #2 of
it, it should have patches you're talking about.

That's the whole problem. After creating an issue and attaching the
patch, there's no way to attach additional patches. I cannot touch
the issue at all, even though I was the one that created it!

d

Zdenek Styblik

2013-07-17 19:21:24 UTC

Permalink

Post by Dan Gora
On Wed, Jul 17, 2013 at 4:06 PM, Zdenek Styblik

Post by Zdenek Styblik

As it says in comments - this one particular thing is on hold. Jim
will provide details, if necessary.

I read the comments. It was on hold because of the warnings generated
when the flag was removed. That's why I created the patches to fix
the warnings..

I see. But everything that was on tracker, s1-s9, is committed now. If
these patches weren't attached to any ticket, then yes, they've got
skipped for sure.

Post by Dan Gora
Unfortunately there was/is no way to attach these patches to the original issue.

Strange since you're the one whom created the ticket in the first
place. But SF.net acts in very strange ways.

[...]

Post by Dan Gora

Post by Zdenek Styblik
There is a zip file attached. And if you haven't created version #2 of
it, it should have patches you're talking about.

That's the whole problem. After creating an issue and attaching the
patch, there's no way to attach additional patches. I cannot touch
the issue at all, even though I was the one that created it!
d

Hm. Well, you can send it again to me and I'll see if I have it. But
as I said. If it wasn't attached to any ticket, then I'm sure they've
got skipped. In such case, please create a new ticket and attach these
patches.
No guarantees (at least from me) on commit prior 1.8.13 release
though, as there are still some issues that have to be fixed prior
1.8.13 and they're, well, planned. This, sort of, isn't.

Thanks,
Z.

Dan Gora

2013-07-17 19:28:30 UTC

Permalink

On Wed, Jul 17, 2013 at 4:21 PM, Zdenek Styblik

Post by Zdenek Styblik

Post by Dan Gora
On Wed, Jul 17, 2013 at 4:06 PM, Zdenek Styblik

Post by Zdenek Styblik

As it says in comments - this one particular thing is on hold. Jim
will provide details, if necessary.

I read the comments. It was on hold because of the warnings generated
when the flag was removed. That's why I created the patches to fix
the warnings..

I see. But everything that was on tracker, s1-s9, is committed now. If
these patches weren't attached to any ticket, then yes, they've got
skipped for sure.

yeah I saw that my last patches finally got merged.. thank you..

Post by Zdenek Styblik
Strange since you're the one whom created the ticket in the first
place. But SF.net acts in very strange ways.

I think that you can change tickets because you're an Admin. Since
I'm a nobody, I cannot do anything, even touch my own tickets...
sigh...

Post by Zdenek Styblik
Hm. Well, you can send it again to me and I'll see if I have it. But
as I said. If it wasn't attached to any ticket, then I'm sure they've
got skipped. In such case, please create a new ticket and attach these
patches.

ok, I'll send them again.

Post by Zdenek Styblik
No guarantees (at least from me) on commit prior 1.8.13 release
though, as there are still some issues that have to be fixed prior
1.8.13 and they're, well, planned. This, sort of, isn't.

Well it's all part of patch #65... and they were submitted back in
Apr.. and they are fairly simple.

Either way.. It fixes a fairly major regression that breaks builds,
but it's up to you, I guess.

d

Dan Gora

2013-07-17 19:42:08 UTC

Permalink

Post by Dan Gora

Post by Zdenek Styblik
Strange since you're the one whom created the ticket in the first
place. But SF.net acts in very strange ways.

I think that you can change tickets because you're an Admin. Since
I'm a nobody, I cannot do anything, even touch my own tickets...
sigh...

eesh.. total boner on my part.. I just wasn't logged into SF.net.. I
guess you can update the tickets now. So I did that.. I added the
patches to patch #65.

https://sourceforge.net/p/ipmitool/patches/65/

thanks
dan

Zdenek Styblik

2013-07-17 19:45:06 UTC

Permalink

Post by Dan Gora

Post by Zdenek Styblik
Strange since you're the one whom created the ticket in the first
place. But SF.net acts in very strange ways.

I think that you can change tickets because you're an Admin. Since
I'm a nobody, I cannot do anything, even touch my own tickets...
sigh...

eesh.. total boner on my part.. I just wasn't logged into SF.net.. I
guess you can update the tickets now. So I did that.. I added the
patches to patch #65.
https://sourceforge.net/p/ipmitool/patches/65/
thanks
dan

Got it. Disregard some things I've said in other thread then.

Z.