Re: bug #484016 not accessible without login in red hat bugzilla

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I' ve been told in next subthread, that the bug is gentoo bug and not
gluster bug. Thank you both for setting me on right direction in my search.

Petr

On 03/29/2014 08:53 PM, Lalatendu Mohanty wrote:
> On 03/30/2014 01:18 AM, Petr Sudoma wrote:
>> I've also tried to log in, to see the bug details, but after login i'm
>> told i'm not authorized to access the bug. Could you please provide
>> details of the bug or make the bug public? I'm interested in using
>> gluster with qemu and libgfapi but i want to know what problems i can
>> hit.
>>
>> I'm interested in:
>>
>> 1) what functionality is affected by the bug
>>
>> 2) whether there is some temporary workaround
>>
>> 3) glusterfs versions affected
>>
>> Petr Sudoma
>
> Hey Petr,
>
> Are you sure bz 484016 is the correct bug? I checked the bug and found
> that the bug is not related to GlusterFS as the product selected in
> the bug is "customer portals". Also I am not seeing any private
> comments in the bug.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=484016
>
> Thanks,
> Lala
>> On 03/27/2014 06:59 PM, Petr Sudoma wrote:
>>> Dear glusterfs maintainers,
>>>
>>> I'm trying to set up glusterfs+qemu (with kvm) native gfapi on Gentoo.
>>> There is a notice in gentoo package repository (in portage ebuild of
>>> qemu) that  libgfapi in qemu is temporarily disabled due to glusterfs
>>> bug #484016.
>>> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/eapi-5-files/package.use.stable.mask?revision=1.23&view=markup
>>>
>>>
>>> I want to read details of #484016 in red hat bugzilla but i'm told by
>>> https://bugzilla.redhat.com/show_bug.cgi?id=484016
>>> that i have to log on to see details of the bug.
>>> (I see no reason for bug info not being public as we are opensource and
>>> not some mad-corporate-bugs-are-our-intelectual-property ... whatever.)
>>>
>>> Could you, please, mark the bug public or post there info about the
>>> bug?
>>>
>>> I'm interested in:
>>>
>>> 1) what functionality is affected by the bug
>>>
>>> 2) whether there is some temporary workaround
>>>
>>> 3) glusterfs versions affected
>>>
>>> Thank You
>>>
>>> Petr Sudoma
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users@xxxxxxxxxxx
>>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users@xxxxxxxxxxx
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux