3:17 p.m.
OK. Got a minor bug with system-config-selinux.py or that is what the
about reports for the dialog.
Thing is this component is not included in the list of components, oh
this is on FC10.
Simply put, you cannot drag the dialog around if your screen size is
800x480 (on my ASUS 701). Neither grabbing it on the title line nor
using <alt-leftmouse> can move it. No problems if the screen size is
larger than the dialog box. No problem dragging other 'oversized'
dialogs (like system-config-services) around either way.
So how do I report this bug if the component is not in the component list?
3:24 p.m.
On Thu, 26 Feb 2009 16:17:25 -0500, Robert wrote:
OK. Got a minor bug with system-config-selinux.py or that is what
the
about reports for the dialog.
Thing is this component is not included in the list of components, oh
this is on FC10.
Simply put, you cannot drag the dialog around if your screen size is
800x480 (on my ASUS 701). Neither grabbing it on the title line nor
using <alt-leftmouse> can move it. No problems if the screen size is
larger than the dialog box. No problem dragging other 'oversized'
dialogs (like system-config-services) around either way.
So how do I report this bug if the component is not in the component list?
http://bugz.fedoraproject.org/APPEND-SRC-RPM-NAME-HERE
then click on "Report".
3:36 p.m.
On Thu, 2009-02-26 at 16:17 -0500, Robert Moskowitz wrote:
OK. Got a minor bug with system-config-selinux.py or that is what
the
about reports for the dialog.
Thing is this component is not included in the list of components, oh
this is on FC10.
Simply put, you cannot drag the dialog around if your screen size is
800x480 (on my ASUS 701). Neither grabbing it on the title line nor
using <alt-leftmouse> can move it. No problems if the screen size is
larger than the dialog box. No problem dragging other 'oversized'
dialogs (like system-config-services) around either way.
So how do I report this bug if the component is not in the component list?
Find out what package it's in:
[adamw@adam ~]$ locate system-config-selinux.py
/usr/share/system-config-selinux/system-config-selinux.py
/usr/share/system-config-selinux/system-config-selinux.pyc
/usr/share/system-config-selinux/system-config-selinux.pyo
[adamw@adam ~]$ rpm
-qf /usr/share/system-config-selinux/system-config-selinux.py
policycoreutils-gui-2.0.62-2.fc11.x86_64
[adamw@adam ~]$
Find out what .src.rpm that binary RPM comes from:
[adamw@adam ~]$ rpm -qi policycoreutils-gui-2.0.62-2.fc11.x86_64 | grep Source
Group : System Environment/Base Source RPM:
policycoreutils-2.0.62-2.fc11.src.rpm
[adamw@adam ~]$
So, 'policycoreutils' is the component.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
4:06 p.m.
Adam Williamson wrote:
On Thu, 2009-02-26 at 16:17 -0500, Robert Moskowitz wrote:
> OK. Got a minor bug with system-config-selinux.py or that is what the
> about reports for the dialog.
>
> Thing is this component is not included in the list of components, oh
> this is on FC10.
>
> Simply put, you cannot drag the dialog around if your screen size is
> 800x480 (on my ASUS 701). Neither grabbing it on the title line nor
> using <alt-leftmouse> can move it. No problems if the screen size is
> larger than the dialog box. No problem dragging other 'oversized'
> dialogs (like system-config-services) around either way.
>
> So how do I report this bug if the component is not in the component list?
>
Find out what package it's in:
[adamw@adam ~]$ locate system-config-selinux.py
/usr/share/system-config-selinux/system-config-selinux.py
/usr/share/system-config-selinux/system-config-selinux.pyc
/usr/share/system-config-selinux/system-config-selinux.pyo
[adamw@adam ~]$ rpm
-qf /usr/share/system-config-selinux/system-config-selinux.py
policycoreutils-gui-2.0.62-2.fc11.x86_64
[adamw@adam ~]$
Find out what .src.rpm that binary RPM comes from:
[adamw@adam ~]$ rpm -qi policycoreutils-gui-2.0.62-2.fc11.x86_64 | grep Source
Group : System Environment/Base Source RPM:
policycoreutils-2.0.62-2.fc11.src.rpm
[adamw@adam ~]$
So, 'policycoreutils' is the component.
Thanks. I will attempt to note this method for future use.
4:22 p.m.
A note to all testers: we have extensive documentation on submitting
bugs at:
http://fedoraproject.org/wiki/BugsAndFeatureRequests
For example, this has a section called "Finding the Right Component"
with links explaining the techniques people have described.
Hopefully this will be useful in answering other questions people may
have; please let us know if there is anything missing!
-B.
4:36 p.m.
On Thu, 2009-02-26 at 17:06 -0500, Robert Moskowitz wrote:
Thanks. I will attempt to note this method for future use.
Neat shortcut if you know what the binary is but don't know what package
it's in:
rpm -qf `which somebinary`
e.g.:
[adamw@adam ~]$ rpm -qf `which glxgears`
glx-utils-7.3-5.fc11.x86_64
[adamw@adam ~]$
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
7:28 p.m.
On Thu, Feb 26, 2009 at 4:36 PM, Adam Williamson <awilliam(a)redhat.com> wrote:
On Thu, 2009-02-26 at 17:06 -0500, Robert Moskowitz wrote:
> Thanks. I will attempt to note this method for future use.
Neat shortcut if you know what the binary is but don't know what package
it's in:
rpm -qf `which somebinary`
e.g.:
[adamw@adam ~]$ rpm -qf `which glxgears`
glx-utils-7.3-5.fc11.x86_64
However, the BZ components (I just recently learned myself) are src
rpms, so something like this can give the final answer:
rpm -qf --qf '%{SOURCERPM}\n' `which glxgears`
or
rpm -qf --qf '%{SOURCERPM}\n'
/usr/share/system-config-selinux/system-config-selinux.py
jerry
7:39 p.m.
On Thu, 2009-02-26 at 19:28 -0600, Jerry Amundson wrote:
On Thu, Feb 26, 2009 at 4:36 PM, Adam Williamson
<awilliam(a)redhat.com> wrote:
> On Thu, 2009-02-26 at 17:06 -0500, Robert Moskowitz wrote:
>
>> Thanks. I will attempt to note this method for future use.
>
> Neat shortcut if you know what the binary is but don't know what package
> it's in:
>
> rpm -qf `which somebinary`
>
> e.g.:
>
> [adamw@adam ~]$ rpm -qf `which glxgears`
> glx-utils-7.3-5.fc11.x86_64
However, the BZ components (I just recently learned myself) are src
rpms,
Er, I explained that bit in my previous mail. So there was no need to do
it again here.
so something like this can give the final answer:
rpm -qf --qf '%{SOURCERPM}\n' `which glxgears`
or
rpm -qf --qf '%{SOURCERPM}\n'
/usr/share/system-config-selinux/system-config-selinux.py
Nice shortcut, though. Thanks.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
1:53 a.m.
On Thu, 26 Feb 2009 17:39:46 -0800, Adam wrote:
On Thu, 2009-02-26 at 19:28 -0600, Jerry Amundson wrote:
> On Thu, Feb 26, 2009 at 4:36 PM, Adam Williamson awilliam redhat com wrote:
> > On Thu, 2009-02-26 at 17:06 -0500, Robert Moskowitz wrote:
> >
> >> Thanks. I will attempt to note this method for future use.
> >
> > Neat shortcut if you know what the binary is but don't know what package
> > it's in:
> >
> > rpm -qf `which somebinary`
> >
> > e.g.:
> >
> > [adamw@adam ~]$ rpm -qf `which glxgears`
> > glx-utils-7.3-5.fc11.x86_64
>
> However, the BZ components (I just recently learned myself) are src
> rpms,
Er, I explained that bit in my previous mail. So there was no need to do
it again here.
So, where is the "neat shortcut" then? In your previous mail you had also
used "rpm -qf ...", so _this_ mail did not contain anything new.
4:12 a.m.
On Friday 27 February 2009 07:53:13 Michael Schwendt wrote:
So, where is the "neat shortcut" then? In your previous
mail you had also
used "rpm -qf ...", so this mail did not contain anything new.
The improvement this time was the use of %{SOURCERPM} in the query format, it
was not used in the previous rpm call.
--
José Abílio
4:34 a.m.
On Fri, 27 Feb 2009 10:12:13 +0000, José wrote:
On Friday 27 February 2009 07:53:13 Michael Schwendt wrote:
> So, where is the "neat shortcut" then? In your previous mail you had also
> used "rpm -qf ...", so this mail did not contain anything new.
The improvement this time was the use of %{SOURCERPM} in the query format, it
was not used in the previous rpm call.
No, Jerry Amundson added that. Apparently Adam was excited about the
"`which glxgears`", but he only used it to determine the binary rpm
name with rpm -qf.
12:12 p.m.
On Fri, 2009-02-27 at 11:34 +0100, Michael Schwendt wrote:
On Fri, 27 Feb 2009 10:12:13 +0000, José wrote:
> On Friday 27 February 2009 07:53:13 Michael Schwendt wrote:
> > So, where is the "neat shortcut" then? In your previous mail you had
also
> > used "rpm -qf ...", so this mail did not contain anything new.
>
> The improvement this time was the use of %{SOURCERPM} in the query format, it
> was not used in the previous rpm call.
No, Jerry Amundson added that. Apparently Adam was excited about the
"`which glxgears`", but he only used it to determine the binary rpm
name with rpm -qf.
No, Jose is right. It was the %{SOURCERPM} which I hadn't thought to
use.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12:43 p.m.
On Fri, 27 Feb 2009 10:12:07 -0800, Adam wrote:
> > > So, where is the "neat shortcut" then? In
your previous mail you had also
> > > used "rpm -qf ...", so this mail did not contain anything new.
> >
> > The improvement this time was the use of %{SOURCERPM} in the query format, it
> > was not used in the previous rpm call.
>
> No, Jerry Amundson added that. Apparently Adam was excited about the
> "`which glxgears`", but he only used it to determine the binary rpm
> name with rpm -qf.
No, Jose is right. It was the %{SOURCERPM} which I hadn't thought to
use.
No :), see:
https://www.redhat.com/archives/fedora-test-list/2009-February/msg01117.html
I even quoted you from it ("neat shortcut"), a reply which not only
confused me as one can see in the archives.
4:13 p.m.
On Fri, 2009-02-27 at 19:43 +0100, Michael Schwendt wrote:
> No, Jose is right. It was the %{SOURCERPM} which I hadn't
thought to
> use.
No :), see:
https://www.redhat.com/archives/fedora-test-list/2009-February/msg01117.html
I even quoted you from it ("neat shortcut"), a reply which not only
confused me as one can see in the archives.
You're getting confused between two separate uses of similar terms. :)
In that mail, I was referring to the use of an embedded `which foobar`
as a 'neat shortcut'. In this other, later, mail:
https://www.redhat.com/archives/fedora-test-list/2009-February/msg01130.html
I refer to Jerry's use of %{SOURCERPM} as a "nice shortcut".
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
2:28 a.m.
On Fri, 27 Feb 2009 14:13:05 -0800, Adam wrote:
On Fri, 2009-02-27 at 19:43 +0100, Michael Schwendt wrote:
> > No, Jose is right. It was the %{SOURCERPM} which I hadn't thought to
> > use.
>
> No :), see:
>
> https://www.redhat.com/archives/fedora-test-list/2009-February/msg01117.html
>
> I even quoted you from it ("neat shortcut"), a reply which not only
> confused me as one can see in the archives.
You're getting confused between two separate uses of similar terms. :)
Dunno what your problem is, but certainly I'm not confused by "two
separate uses of similar terms".
In that mail, I was referring to the use of an embedded `which
foobar`
as a 'neat shortcut'. In this other, later, mail:
That is what I referred to. Look at what I quoted, particularly if you've
forgotten already what you've written. Not only did I quote the right
sentences, I explicitly wrote "neat shortcut" in double-quotes in my
reply, which is the term you've used. I did *not* refer to your later
reply where you commented on the %SOURCERPM query as "nice shortcut".
This thread is about "Determining the component for a bug submission",
and when skimming over new message, for a moment I thought maybe recent
development in RPM added a shortcut for querying the src.rpm name. Else
I would have skipped the entire thread, because I know these queries.
What confused me is the strange 1st half of your reply to Jerry, who had
pointed out that your query using `which ...` is insufficient, since we
need the src.rpm.
So, actually, you were just excited about the `which ...` part, because
you called it "Neat shortcut" (see archives! msg 01117), although it is
incompatible with the file locations from the start of the thread. And
then Jerry told you about the proper src.rpm query (which would benefit
from getting a _real_ shortcut in future RPM releases).
https://www.redhat.com/archives/fedora-test-list/2009-February/msg01130.html
I refer to Jerry's use of %{SOURCERPM} as a "nice shortcut".
And I refer to the different query you called "neat shortcut".
In hope that you won't add any more confusion now. :)
4:41 p.m.
On Sat, 2009-02-28 at 09:28 +0100, Michael Schwendt wrote:
So, actually, you were just excited about the `which ...` part,
because
you called it "Neat shortcut" (see archives! msg 01117),
Thank you for telling me what was actually happening in *my own brain*,
when I was so foolish as to think it was something else.
I am the person who wrote this stuff. I know why I wrote it. I told you
why. For some bizarre reason you think you know this better than me, I
can't begin to imagine why.
This is the most ridiculous thread I've ever been involved in (and trust
me, there's some competition), so I'm going to stop now.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
2:54 a.m.
Adam Williamson wrote:
Neat shortcut if you know what the binary is but don't know what package
it's in:
rpm -qf `which somebinary`
e.g.:
[adamw@adam ~]$ rpm -qf `which glxgears`
glx-utils-7.3-5.fc11.x86_64
[adamw@adam ~]$
Here's one.
Because I just don't know.
After the latest (to me) rawhide updates.
The log viewer (from within gnome)
the various logs have different dates.
messages has correct dates,
secure has Sat 28th, as Tues 28th, but it also has Mon as the 28th.
Stuff like that
Where would that puppy go.
Frank
5534
days inactive
5538
days old
16 comments
7 participants
participants (7)
-
Adam Williamson -
Christopher Beland -
Frank Murphy -
Jerry Amundson -
José Abílio Matos -
Michael Schwendt -
Robert Moskowitz