HP bugs database

[Srimalik]

Is there any way that anybody can see the description of a bug raised on a HP product ( say HPUX).

In the details of any patch we can see some numbers like "JAGXXXXXX" and a headline, can we find the full description of the problem.

I know making the solution public will not be possible but at least the full problem description and reproduction scenarios should be made public

[Robert-Jan Goossens_1]

Hi,

Try searching the Techinical Database.

US
http://www2.itrc.hp.com/service/cki/enterService.do?admit

Europe
http://www4.itrc.hp.com/service/cki/enterService.do?admit

Regards,
Robert-Jan

[Srimalik]

I searched for JAGac40498 in the link mentioned it gave me the patch in which this was delivered.

I want to know the full problem description and the reproduction steps to check whether the problem exists on my machine or not

[Dennis Handly]

I thought if you had a support contract you can look at the knowledge database and the individual bugs.

I can take a look at it for you Monday.

[Srimalik]

Do you mean that not everybody can view the bugs database? You need to have a support contract for that and link you itrc user id with the contract.

[Dennis Handly]

>Do you mean that not everybody can view the bugs database?

Yes.

[Srimalik]

:-(

[Dennis Handly]

It turns out CR JAGac40498 is not visible to any customer. PHCO_20869 was for obsolete 11.00:
mkboot fails on a whole-disk HFS system with large-files enabled

It appears all that was done was to add an error message.

[Patrick Wallek · Accepted solution]

>>but at least the full problem description and reproduction scenarios should be made public

So you want all the problems in HP-UX to be made available to all the hackers and unscrupulous types on the Internet?

I must say that I disagree. Having general problem descriptions as in the patches is fine. I do NOT think the steps to reproduce a problem should be made public, even if you have a support contract.

[Srimalik]

yeah, they should not be available to the world, thanks for your comments