On Thu, 25 Oct 2012 21:56:35 -0400
Cole Robinson crobi...@redhat.com wrote:
Hi all,
I regularly pull down the F18 tree from the rsync equivalent of:
http://download.fedoraproject.org/pub/fedora/linux/development/18/x86_64/os/
note that download.fedoraproject.org is a redirect that gets
On 25/10/12 22:49, Adam Jackson wrote:
On Thu, 2012-10-25 at 22:21 +0100, Frank Murphy wrote:
I agree, but I don't need it,
Wheres the script to turn if off?
Everone else has to figure that out themselves.
accessibilty.conf has no on=0\false switch.
If the F18 install I just did is any
The list I'd come up with so far looks like this:
1. autopart empty disk
2. autopart existing empty space
3. autopart wipe entire disk
4. autopart alongside existing
5. autopart shrink
6. autopart multidisk
so for 1) you feed it an entirely empty disk and let it autopart into
it, with
Well I see your point, but it kind of cuts both ways - Josef clearly
got
confused by a few cases where we overload test cases to test several
different things, so you can argue that it's actually more
'accessible'
when we try to stick to 'one test case tests one thing'. But your
approach
- Original Message -
From: Kamil Paral kpa...@redhat.com
No, this is a game of spot five differences :-) At least one versus
all virtual consoles. This can be part of the same test case, marked
as Alpha/Beta
OK, I'll update the summary page/matrix accordingly. Also I'll try to
On Fri, Oct 26, 2012 at 1:24 AM, Robyn Bergeron rberg...@redhat.com wrote:
I am under the impression that we've been testing with/without LVM anyway,
both scenarios? In any case, it doesn't seem as earthshaking as other
developments - it's just making the default be what it's been for some
On 10/25/2012 09:16 PM, Adam Williamson wrote:
Sure, that's the reason for the potential distinction between bugs that
_can_ be fixed with updates and those that_can't_. This discussion was
prompted by a specific bug -
https://bugzilla.redhat.com/show_bug.cgi?id=868519 - which can't be
fixed
On 10/26/2012 02:53 AM, Adam Williamson wrote:
The general understanding among Storage People is that we're aiming to
go to btrfs by default for F19. Finally. That's one of the arguments
against changing the default_now_, for one release (or possibly two),
only to change it again shortly.
On Fri, Oct 26, 2012 at 6:23 AM, Jóhann B. Guðmundsson
johan...@gmail.com wrote:
On 10/26/2012 02:53 AM, Adam Williamson wrote:
The general understanding among Storage People is that we're aiming to
go to btrfs by default for F19. Finally. That's one of the arguments
against changing the
On 10/25/12 23:42, Chuck Forsberg WA7KGX N2469R wrote:
While waiting for a more functional Anaconda I have been
running 64 bit F18 with yum updates.
The Noveau driver still crashes. Fortunately Nvidia still installs.
I am able to run SCO Openserver 5.0.7 under the virtual machine.
Select
Frank Murphy frankl...@gmail.com wrote on Fri, 26 Oct 2012 08:33:25 +0100:
So you agree, it's unneccessary.
For me to need at-spi*. Point made.
I think the point was at-spi is part of GTK, but this part is not
something it is reasonable to package separately, such as a language
package or some
Cole Robinson (crobi...@redhat.com) said:
Up until recently this was a full install tree, including the images/
subdir. This makes it easy to use the tree for PXE (like using
cobbler import) or URL installs in virt-manager.
Now, though, current trees only have Packages/ repodata/ and
Hi,
I've been noticing this since at least September (but reboot really
rarely, so I always forgot to mention the problem...). My keyboard
layout of choice is swiss german, and the layout is such everywhere
except at the kdm login screen.
I've got vconsole.keymap=sg in the grub command line,
On 10/26/2012 10:20 AM, Bill Nottingham wrote:
Cole Robinson (crobi...@redhat.com) said:
Up until recently this was a full install tree, including the images/
subdir. This makes it easy to use the tree for PXE (like using
cobbler import) or URL installs in virt-manager.
Now, though, current
On Fri, 26 Oct 2012 16:34:54 +0200
Sandro Mani manisan...@gmail.com wrote:
Hi,
I've been noticing this since at least September (but reboot really
rarely, so I always forgot to mention the problem...). My keyboard
layout of choice is swiss german, and the layout is such everywhere
except
On 26/10/12 14:59, Richard Ryniker wrote:
Frank Murphy frankl...@gmail.com wrote on Fri, 26 Oct 2012 08:33:25 +0100:
So you agree, it's unneccessary.
For me to need at-spi*. Point made.
I think the point was at-spi is part of GTK, but this part is not
something it is reasonable to package
On 10/26/2012 06:21 AM, Kevin Martin wrote:
On 10/25/12 23:42, Chuck Forsberg WA7KGX N2469R wrote:
While waiting for a more functional Anaconda I have been
running 64 bit F18 with yum updates.
The Noveau driver still crashes. Fortunately Nvidia still installs.
I am able to run SCO
On 26/10/12 16:31, Adam Jackson wrote:
If the F18 install I just did is any indication, the state it ships in
is as off as it gets.
So you agree, it's unneccessary.
What a dishonest thing to say. I'd appreciate it if you didn't put
words in my mouth, thanks.
- ajax
Is it necessary for
On Fri, 26 Oct 2012 15:14:12 +
Jóhann B. Guðmundsson johan...@gmail.com wrote:
Anyone else noticing this / any idea how to fix?
Thanks,
Sandro
http://www.freedesktop.org/software/systemd/man/vconsole.conf.html
Doesn't fix it for me.
kemap=uk, can be both wrong and right.
It does
I haven't tried the vconsole thing yet (can't log out right now), but
also in my case the problem _only_ appears at the login screen.
Everywhere else, including on VTs, the layout is correct.
On Fri, Oct 26, 2012 at 6:00 PM, Frank Murphy frankl...@gmail.com wrote:
On Fri, 26 Oct 2012 15:14:12
On 10/26/12 10:44, Chuck Forsberg WA7KGX N2469R wrote:
On 10/26/2012 06:21 AM, Kevin Martin wrote:
On 10/25/12 23:42, Chuck Forsberg WA7KGX N2469R wrote:
While waiting for a more functional Anaconda I have been
running 64 bit F18 with yum updates.
The Noveau driver still crashes.
On 10/26/2012 09:22 AM, Kevin Martin wrote:
On 10/26/12 10:44, Chuck Forsberg WA7KGX N2469R wrote:
On 10/26/2012 06:21 AM, Kevin Martin wrote:
On 10/25/12 23:42, Chuck Forsberg WA7KGX N2469R wrote:
While waiting for a more functional Anaconda I have been
running 64 bit F18 with yum updates.
On Fri, 26 Oct 2012 11:22:32 -0500
Kevin Martin ktm...@gmail.com wrote:
Which kernel are you running? I can't get 304.60 to build on
3.7.0-0.rc2.git1.2.fc19.x86_64 (rawhide). It can't figure out the
kernel version so it won't even try to build.
Kevin
Chuck is running F18, may be
On 10/26/12 11:25, Chuck Forsberg WA7KGX N2469R wrote:
On 10/26/2012 09:22 AM, Kevin Martin wrote:
On 10/26/12 10:44, Chuck Forsberg WA7KGX N2469R wrote:
On 10/26/2012 06:21 AM, Kevin Martin wrote:
On 10/25/12 23:42, Chuck Forsberg WA7KGX N2469R wrote:
While waiting for a more functional
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
- lorax-18.21-1.fc18.x86_64.rpm
- pykickstart-1.99.21-1.fc18
- python-meh-0.18-1.fc18
http://dl.fedoraproject.org/pub/alt/qa/18/20121025_f18b-smoke12/
I've done a few quick
On Fri, 2012-10-26 at 11:49 -0600, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
Did you really use 18.4 or 18.5? We should be going with 18.5 I think.
--
Adam Williamson
Fedora QA Community Monkey
IRC:
On Fri, Oct 26, 2012 at 11:49 PM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-10-26 at 11:49 -0600, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
Did you really use 18.4 or 18.5? We should be
On Fri, 2012-10-26 at 09:35 +, Jóhann B. Guðmundsson wrote:
On 10/25/2012 09:16 PM, Adam Williamson wrote:
Sure, that's the reason for the potential distinction between bugs that
_can_ be fixed with updates and those that_can't_. This discussion was
prompted by a specific bug -
On Fri, 26 Oct 2012 11:19:10 -0700
Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-10-26 at 11:49 -0600, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
Did you really use 18.4 or 18.5? We should
On 10/26/2012 07:14 PM, Adam Williamson wrote:
I wanted to raise the question of whether it makes
sense in general to hold our releases for some security bugs. Right now
we have no capacity to do that.
I dont think that should be for us to decide. When we encounter
potential security issue in
On Fri, 2012-10-26 at 19:33 +, Jóhann B. Guðmundsson wrote:
On 10/26/2012 07:14 PM, Adam Williamson wrote:
I wanted to raise the question of whether it makes
sense in general to hold our releases for some security bugs. Right now
we have no capacity to do that.
I dont think that
On 10/26/2012 07:44 PM, Adam Williamson wrote:
The release must contain no known security issues of 'important' or
higher impact according to the Red Hat severity classification scale
which cannot be satisfactorily resolved by a package update (e.g. issues
during installation)
? How does that
On Fri, Oct 26, 2012 at 12:44:24 -0700,
Adam Williamson awill...@redhat.com wrote:
? How does that sound to everyone? It drops the issue entirely for Alpha
and Beta, and means we only consider bad issues that cannot be fixed
with an update for Final.
That sounds reasonable. For alpha and
On Fri, 2012-10-26 at 12:44 -0700, Adam Williamson wrote:
I think with the feedback we've seen so far that we can say the original
proposal was substantially too broad, so how about this as a revised
proposal - for now, we just add a single Final release criterion which
reads:
The release
On Fri, 2012-10-26 at 13:27 -0600, Tim Flink wrote:
On Fri, 26 Oct 2012 11:19:10 -0700
Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-10-26 at 11:49 -0600, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
-
On Fri, 2012-10-26 at 19:33 +, Jóhann B. Guðmundsson wrote:
On 10/26/2012 07:14 PM, Adam Williamson wrote:
I wanted to raise the question of whether it makes
sense in general to hold our releases for some security bugs. Right now
we have no capacity to do that.
I dont think that
Hey, folks.
So the Big LVM Autopart Controversy has been kicked upstairs to FESCo:
https://fedorahosted.org/fesco/ticket/964
If they say 'go with LVM', we'll have to do that.
I have no idea what FESCo will decide, but we should cover our bets
either way, I think, so it will do no harm to do
On Fri, 2012-10-26 at 14:06 -0700, Adam Williamson wrote:
Hey, folks.
So the Big LVM Autopart Controversy has been kicked upstairs to FESCo:
https://fedorahosted.org/fesco/ticket/964
If they say 'go with LVM', we'll have to do that.
I have no idea what FESCo will decide, but we should
On Fri, 2012-10-26 at 10:23 +, Jóhann B. Guðmundsson wrote:
On 10/26/2012 02:53 AM, Adam Williamson wrote:
The general understanding among Storage People is that we're aiming to
go to btrfs by default for F19. Finally. That's one of the arguments
against changing the default_now_, for
On Fri, 2012-10-26 at 18:16 +0200, Sandro Mani wrote:
I haven't tried the vconsole thing yet (can't log out right now), but
also in my case the problem _only_ appears at the login screen.
Everywhere else, including on VTs, the layout is correct.
It sounds like the console layout is correct and
On 10/26/2012 07:49 PM, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
- lorax-18.21-1.fc18.x86_64.rpm
- pykickstart-1.99.21-1.fc18
- python-meh-0.18-1.fc18
On Sat, 2012-10-27 at 00:14 +0200, Dennis Jacobfeuerborn wrote:
On 10/26/2012 07:49 PM, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
- lorax-18.21-1.fc18.x86_64.rpm
- pykickstart-1.99.21-1.fc18
-
On 10/27/2012 12:14 AM, Dennis Jacobfeuerborn wrote:
On 10/26/2012 07:49 PM, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
- lorax-18.21-1.fc18.x86_64.rpm
- pykickstart-1.99.21-1.fc18
-
On 10/27/2012 12:22 AM, Adam Williamson wrote:
On Sat, 2012-10-27 at 00:14 +0200, Dennis Jacobfeuerborn wrote:
On 10/26/2012 07:49 PM, Tim Flink wrote:
I've built a new smoke test image with:
- btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18
- firstboot-18.4-1.fc18
-
Just a bit of heads up about the recent changes taking place in systemd
( 195 ) for F18+...
The following sysconfig files are being deprecated /etc/sysconfig/clock,
/etc/sysconfig/i18n,/etc/sysconfig/keyboard, /etc/sysconfig/network (
Hostname only )
These changes should be transparent (
On Oct 26, 2012 7:27 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote:
Just a bit of heads up about the recent changes taking place in systemd
( 195 ) for F18+...
(snip)
https://admin.fedoraproject.org/mailman/listinfo/test
Thanks for the writeup, Jóhann. There's a lot of good info here.
On 10/27/2012 01:43 AM, Pete Travis wrote:
On Oct 26, 2012 7:27 PM, Jóhann B. Guðmundsson johan...@gmail.com
mailto:johan...@gmail.com wrote:
Just a bit of heads up about the recent changes taking place in
systemd ( 195 ) for F18+...
(snip)
On Sat, 2012-10-27 at 01:24 +, Jóhann B. Guðmundsson wrote:
I highly recommend against setting the hardware clock to localtime but
because I know some of you guys are dual booting with windows and to
lazy to fix the registry here's how you set the hardware clock to use
localtime instead..
On Oct 26, 2012 8:01 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote:
On 10/27/2012 01:43 AM, Pete Travis wrote:
On Oct 26, 2012 7:27 PM, Jóhann B. Guðmundsson johan...@gmail.com
wrote:
Just a bit of heads up about the recent changes taking place in
systemd ( 195 ) for F18+...
49 matches
Mail list logo
