On Mon, 2014-06-16 at 20:37 -0400, Felix Miata wrote:
> On 2014-06-16 17:20 (GMT-0700) Adam Williamson composed:
>
> > On Mon, 2014-06-16 at 19:50 -0400, Felix Miata wrote:
>
> >> > It's in the journal, try 'sudo journalctl -b | grep Xorg' or similar.
> >>
> >> That's going to be real fun to expl
On 2014-06-16 17:20 (GMT-0700) Adam Williamson composed:
On Mon, 2014-06-16 at 19:50 -0400, Felix Miata wrote:
> It's in the journal, try 'sudo journalctl -b | grep Xorg' or similar.
That's going to be real fun to explain to people in help forums in telling
them to post the /var/log/Xorg.0.l
On Mon, 2014-06-16 at 19:50 -0400, Felix Miata wrote:
> On 2014-06-16 1:23 (GMT-0700) Adam Williamson composed:
>
> >> I discovered there was no
> >> /var/log/Xorg.0.log file. The one I have is dated April 2. Where does
> >> Xorg put its log now?
>
> > It's in the journal, try 'sudo journalctl
On 2014-06-16 1:23 (GMT-0700) Adam Williamson composed:
I discovered there was no
/var/log/Xorg.0.log file. The one I have is dated April 2. Where does
Xorg put its log now?
It's in the journal, try 'sudo journalctl -b | grep Xorg' or similar.
That's going to be real fun to explain to peo
The following Fedora 19 Security updates need testing:
Age URL
233
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
46 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19
35
https://admin.fedoraproject.org/updates/FEDORA-20
The following Fedora 20 Security updates need testing:
Age URL
54
https://admin.fedoraproject.org/updates/FEDORA-2014-5497/openstack-keystone-2013.2.3-3.fc20
46 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20
26
https://admin.fedoraproject.org/updates/FEDORA-2
On Sun, 2014-06-15 at 14:18 -0700, Stephen Sheldon wrote:
> I run Rawhide in a VMM KVM virtual machine. Since the 3.16 kernels, the
> mouse cursor is not visible when gdm starts. I can log in with the
> keyboard, and then the mouse cursor is visible in the Mate desktop. I
> still have 3.15, a
The Fedora QA devel team is proud to announce the release of Taskotron
0.3!
This is another incremental improvement and a continuation of our
new-ish timed release process. The new release is running in our
staging instance:
https://taskotron-stg.fedoraproject.org/
The major changes have been:
On Fri, 2014-06-13 at 21:36 -0400, Bob Lightfoot wrote:
> Dear Adam:
> If you could post the dnf-devs mail address or forward this that
> would be wonderful.
http://dnf.baseurl.org is probably the best thing to be following. You
could put a lot of this feedback into
http://dnf.baseurl.org/2014
On Mon, 2014-06-16 at 12:39 -0700, Adam Williamson wrote:
> Per-role functional requirements are certainly something we could add,
> and probably a good idea, but they'd have to be done as part of actually
> creating the roles. We don't have a DNS server role yet, and it's not in
> the set of two
#448: Proposed Test Day - Virtualization
---+---
Reporter: crobinso | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day |Version:
Resolution:| Keywords:
Blocked B
#448: Proposed Test Day - Virtualization
--+
Reporter: crobinso | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords:| Blocked By:
Blocking
On Mon, 2014-06-16 at 11:51 -0400, Russell Doty wrote:
> What about adding a functional test or smoke test as part of
> installation - have an automated test that validates that the server
> role is functioning correctly. For example, for a dns server verify that
> it can properly resolve addresses
On Mon, Jun 16, 2014 at 1:35 PM, Tim Lauridsen wrote:
>
>
>
> On Mon, Jun 16, 2014 at 12:39 PM, drago01 wrote:
>>
>> On Mon, Jun 16, 2014 at 12:16 PM, Tim Lauridsen
>> wrote:
>> > dnf builddep currently only work with an local .src.rpm or .spec file,
>> > that
>> > is the most common usecase.
>>
On Mon, Jun 16, 2014 at 12:39 PM, drago01 wrote:
> On Mon, Jun 16, 2014 at 12:16 PM, Tim Lauridsen
> wrote:
> > dnf builddep currently only work with an local .src.rpm or .spec file,
> that
> > is the most common usecase.
> >
> > You can create an RFE in bugzilla against dnf-plugins-core and des
On Mon, Jun 16, 2014 at 12:16 PM, Tim Lauridsen wrote:
> dnf builddep currently only work with an local .src.rpm or .spec file, that
> is the most common usecase.
>
> You can create an RFE in bugzilla against dnf-plugins-core and describe you
> usecase.
>
> normally, you need to have a locale .spe
dnf builddep currently only work with an local .src.rpm or .spec file, that
is the most common usecase.
You can create an RFE in bugzilla against dnf-plugins-core and describe you
usecase.
normally, you need to have a locale .spec or .src.rpm to build a package
locally, so this is properly why dn
17 matches
Mail list logo
