[Test-Announce] Preupgrade Test day(Mar 17) Recap

2011-03-20 Thread He Rui 
Greetings testers,

Thanks for your involvement and attention on this test event. During
that day preupgrade-1.1.9-1 was built on time for testing, for most
testers, preupgrading went on smoothly before encountering the lorax
issue[1]. The bugs filed were summarized here: 

Bug 688761 - NEW - preupgrade - 2011-03-17 Testday for Preupgrade
failure for f14->f15
Bug 684742 - ASSIGNED - lorax - glibc dynamic library loading bug causes
installs to fail
Bug 635432 - NEW - yum - UnicodeEncodeError: 'ascii' codec can't encode
character u'\xe4' in position 6: ordinal not in range(128)

The common use cases for preupgrade have been covered and the test
results of this package is positive. For detailed results, please refer
to the test day page:

https://fedoraproject.org/wiki/Test_Day:2011-03-17_Preupgrade


Thanks,
Hurry

[1] https://bugzilla.redhat.com/show_bug.cgi?id=684742
-- 
Contacts

Hurry
FAS Name: Rhe 
Timezone: UTC+8
TEL: 86-010-62608141
IRC nick: rhe #fedora-qa #fedora-zh

___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: problems at very early stage installing Fedora 15 alpha in Virtualbox 4.0.4/Mac OS X

2011-03-20 Thread Rahul Sundaram 
On 03/20/2011 11:55 PM, Sven Aluoor wrote:
> On 3/20/11 5:23 PM, Adam Huffman wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=689258
> Quote from Bug 682555
>
> The minimum memory required is 1GB, due to anaconda changes. When you 
> see "populate_rootfs" in the panic, it's caused by that.
>
> Fedora is the same fat as M$ Windows 7. Sad.

Why quote only one comment and leave out the rest?  You are welcome to
contribute

https://bugzilla.redhat.com/show_bug.cgi?id=682555#c3

Rahul



-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Bruno Wolff III 
On Sun, Mar 20, 2011 at 13:18:32 -0700,
  Antonio Olivares  wrote:
> 
> It is selinux that is denying the startup, system will work, but you need to 
> start with it disabled :(

Starting in permissive mode is enough. Disabling will result in needing to
do a relabel later.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

NetworkManager flaps ethernet connection when ipv6 is present.

2011-03-20 Thread Steven Haigh 
Hi all,

It seems NetworkManager has an issue with handling ipv6 and as a result 
it drops the entire network config (ipv4 & ipv6) repeatedly.

I have bugged this here:
https://bugzilla.redhat.com/show_bug.cgi?id=689291

I see hundreds of entries in /var/log/messages as such:
Mar 21 08:53:25 wopr NetworkManager[1027]:  [1300658005.596660] 
[nm-device.c:628] activation_source_schedule(): activation stage already 
scheduled
Mar 21 08:53:25 wopr NetworkManager[1027]:  Activation (em1) Stage 
4 of 5 (IP6 Configure Get) scheduled...

This will cycle forever.

Has anyone else seen this by chance?

-- 
Steven Haigh

Email: net...@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F15 Alpha will not start after my last yum update

2011-03-20 Thread Petrus de Calguarium 
cornel panceac wrote:

> can you please tell us the bug number?

https://bugzilla.redhat.com/show_bug.cgi?id=689163

Sorry about my description. My initial impressions, when I had made the report, 
were incomplete.

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Fedora 15 updates-testing report

2011-03-20 Thread updates 
The following Fedora 15 Security updates need testing:

https://admin.fedoraproject.org/updates/wordpress-3.1-1.fc15
https://admin.fedoraproject.org/updates/mailman-2.1.14-5.fc15
https://admin.fedoraproject.org/updates/krb5-1.9-6.fc15
https://admin.fedoraproject.org/updates/php-pear-1.9.2-1.fc15
https://admin.fedoraproject.org/updates/libcgroup-0.37.1-1.fc15
https://admin.fedoraproject.org/updates/openldap-2.4.24-2.fc15

https://admin.fedoraproject.org/updates/php-5.3.6-1.fc15,php-eaccelerator-0.9.6.1-6.fc15,maniadrive-1.2-29.fc15


The following Fedora 15 Critical Path updates have yet to be approved:

https://admin.fedoraproject.org/updates/gdb-7.2.50.20110320-30.fc15
https://admin.fedoraproject.org/updates/openldap-2.4.24-2.fc15
https://admin.fedoraproject.org/updates/libexif-0.6.20-1.fc15

https://admin.fedoraproject.org/updates/gpgme-1.3.0-4.fc15,kdepim-4.4.10-2.fc15
https://admin.fedoraproject.org/updates/libXfixes-5.0-1.fc15

https://admin.fedoraproject.org/updates/xorg-x11-drv-wacom-0.10.99-1.20110315.fc15
https://admin.fedoraproject.org/updates/bash-4.2.7-2.fc15

https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-22.20110303git92db2bc.fc15


The following builds have been pushed to Fedora 15 updates-testing

PyXB-1.1.2-1.fc15
bti-030-3.fc15
bzr-2.3.1-1.fc15
cclive-0.7.3.1-1.fc15
clive-2.3.0.2-1.fc15
clustershell-1.4.3-1.fc15
dtrx-7.0-3.fc15
epiphany-2.91.91.1-1.fc15
fetch-crl-3.0.6-1.fc15
gcalctool-5.91.91-1.fc15
gdb-7.2.50.20110320-30.fc15
gdcm-2.0.16-16.fc15
gmusicbrowser-1.1.7-1.fc15
gnome-games-2.91.91-1.fc15
highlight-3.3-5.fc15
htop-0.9-2.fc15
kvirc-4.0.4-1.fc15
libetpan-1.0.1-0.1.20110312cvs.fc15
libxslt-1.1.26-8.fc15
lordsawar-0.2.0-3.fc15
mfiler3-4.2.5-1.fc15
perl-Mojolicious-1.15-1.fc15
perl-Proc-Daemon-0.09-1.fc15
qbittorrent-2.7.0-1.fc15
qlandkartegt-1.1.1-1.fc15
quvi-0.2.14-1.fc15
rkward-0.5.5-1.fc15
root-5.28.00b-1.fc15
rubyripper-0.6.0-1.fc15
saphire-1.3.5-1.fc15
sox-14.3.2-1.fc15
sqliteman-1.2.2-3.fc15
telepathy-butterfly-0.5.15-3.fc15
wine-1.3.16-1.fc15

Details about builds:



 PyXB-1.1.2-1.fc15 (FEDORA-2011-3704)
 Python XML Schema Bindings

Update Information:

PyXB - Python XML Schema Bindings

References:

  [ 1 ] Bug #688663 - Review Request: PyXB - Python XML Schema Bindings
https://bugzilla.redhat.com/show_bug.cgi?id=688663




 bti-030-3.fc15 (FEDORA-2011-3584)
 Bash Twitter/Identi.ca Idiocy

Update Information:

Upstream bugfix release, and also correctly parse passwords containing the '#' 
character

ChangeLog:

* Sat Mar 19 2011 Michel Salim  - 030-3
- Improved comment marker fix, now safer and handle lines containing both
  non-marker and marker '#'s
* Fri Mar 18 2011 Michel Salim  - 030-2
- Improve detection of comment marker in configuration file
* Fri Mar 18 2011 Michel Salim  - 030-1
- Update to 0.30

References:

  [ 1 ] Bug #688872 - bti-030 is available
https://bugzilla.redhat.com/show_bug.cgi?id=688872




 bzr-2.3.1-1.fc15 (FEDORA-2011-3711)
 Friendly distributed version control system

Update Information:

Upstream 2.3.1 bugfix release

ChangeLog:

* Sun Mar 20 2011 Henrik Nordstrom  - 2.3.1-1
- Upstream 2.3.1 bugfix release




 cclive-0.7.3.1-1.fc15 (FEDORA-2011-3723)
 Command line video extraction utility

Update Information:

Update to 0.7.3.1

ChangeLog:

* Sun Mar 20 2011 Nicoleau Fabien  0.7.3.1-1
- Update to 0.7.3.1
* Sun Mar 13 2011 Nicoleau Fabien  0.7.3-1
- Update to 0.7.3
* Mon Feb 14 2011 Nicoleau Fabien  0.7.2-1
- Update to 0.7.2
--

Re: f15 no longer starts

2011-03-20 Thread Petrus de Calguarium 
Genes MailLists wrote:

> 
>  I'm curious - how does a bad rsyslog package prevent the system from
> booting ? Should it ??
> 
>   That feels too brittle to me ... I mean its only logging after all

Ask the experts, not me.

vt1 hung endlessly, with a black screen once the daemons had finally all timed 
out, and on vt2+, it was impossible to log in. After typing the password, the 
system would hang, and then a 60 second timeout would be noted, and hence, no 
login was possible. I was forced to alt-SysRq-re to kill the remaining daemons, 
I presume, and then I noticed on vt1 that graphical login was taking place, but 
on a ro system, hence config files could not be written to, hence each in turn 
generating an error. It was a total disaster and took nearly 30 minutes on an 
Intel Core 2 Duo processor.

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

F-15 Branched report: 20110320 changes

2011-03-20 Thread Branched Report 
Compose started at Sun Mar 20 13:15:48 UTC 2011

Broken deps for x86_64
--
Io-language-extras-20080330-4.fc15.x86_64 requires 
libevent-1.4.so.2()(64bit)
byzanz-0.2.2-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit)
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Ograph2way) = 
0:7442f647b0a74ed48a5c9361fc42ccc4
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Flag) = 
0:522d7f86f1236405e53271ff74923515
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Osetb) = 
0:8f21a0a4f771662673604ed92a237d79
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Oassocb) = 
0:d873c4a1eeb6fa5c5333f8658c49d1db
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Setb) = 
0:93bdb588146a13126bfad4eab6c58206
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Oassoc_buffer) = 
0:cf6fbee4fcc6644a0a90f07da8eb6c7b
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Mapb) = 
0:617c09a110cef9f040335b35078c7234
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Sexplib) = 
0:a990ea80438337d5407bbc0343c7236a
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Dumper) = 
0:76126ba149caeb2d34f12e11187a9d4e
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Oassoch) = 
0:87f7dc2635e5a7ed1ab03b7cd5380ace
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(SetPt) = 
0:b69c030e8ca717d556d3d9bd2a5d22fd
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(ANSITerminal) = 
0:3d0d1700618d8b3a4e4b2308f28cefb6
coccinelle-0.2.5-0.rc4.2.fc15.1.x86_64 requires ocaml(Oseti) = 
0:a937e7661f510c17bfd21d4372507795
conmux-0.0-12.493svn.fc15.noarch requires perl(Payload)
conmux-0.0-12.493svn.fc15.noarch requires perl(Client)
cpm-0.23-0.3.beta.fc12.x86_64 requires libdotconf-1.0.so.0()(64bit)
db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0
dbmail-3.0.0-0.3.rc1.fc15.x86_64 requires libevent-1.4.so.2()(64bit)
dbmail-auth-ldap-3.0.0-0.3.rc1.fc15.x86_64 requires 
libevent-1.4.so.2()(64bit)
dh-make-0.55-3.fc15.noarch requires debhelper
drupal6-views_bulk_operations-1.10-6.fc15.noarch requires drupal6-views
eog-plugins-2.30.0-2.fc14.x86_64 requires libgdata.so.7()(64bit)
1:fife-0.3.2-1.fc15.i686 requires libboost_regex.so.1.44.0
1:fife-0.3.2-1.fc15.i686 requires libboost_system.so.1.44.0
1:fife-0.3.2-1.fc15.i686 requires libboost_filesystem.so.1.44.0
1:fife-0.3.2-1.fc15.x86_64 requires libboost_regex.so.1.44.0()(64bit)
1:fife-0.3.2-1.fc15.x86_64 requires libboost_system.so.1.44.0()(64bit)
1:fife-0.3.2-1.fc15.x86_64 requires 
libboost_filesystem.so.1.44.0()(64bit)
file-browser-applet-0.6.6-1.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::ScrolledWindow)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Dialog)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Toolbar)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::TreeView)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MenuBar)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::VBox)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Window)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MessageDialog)
gearmand-0.14-2.fc15.x86_64 requires libevent-1.4.so.2()(64bit)
glom-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit)
glom-libs-1.16.1-2.fc15.i686 requires libgdamm-4.0.so.12
glom-libs-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit)
glunarclock-0.34.1-1.fc14.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-cpufire-1.6-3.fc14.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-music-2.5.1-5.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0
gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2)
gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
1:gnome-applets-2.32.0-3.fc15.x86_64 requires 
libpanel-applet-3.so.0()(64bit)
1:gnome-applets-2.32.0-3.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
1:gnome-applets-2.32.0-3.fc15.x86_64 requires libgweather.so.1()(64bit)
gnome-netstatus-2.28.2-1.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-python2-applet-2.32.0-1.fc14.x86_64 requires 
libpanel-applet

Re: [Fedora QA] #170: Request for F15 Power Management test day

2011-03-20 Thread Fedora QA 
#170: Request for F15 Power Management test day
---+
  Reporter:  jskarvad  |   Owner: 
  Type:  defect|  Status:  new
  Priority:  major |   Milestone: 
 Component:  Test Day  | Version: 
Resolution:|Keywords: 
---+
Comment (by jskarvad):

 Thanks, test cases should be finalized now. We will test them intensively
 during Monday. Feel free to change/improve anything (especially wording -
 I am not native speaker :). Any feedback is welcome. I will also try to
 create the live CD (on Monday).

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F15 Alpha will not start after my last yum update

2011-03-20 Thread Vamsi Krishna Brahmajosyula 
The boot stops at "Enabling user sessions" (not the exact words) on my
machine.

When i tried rebooting with selinux=0, I am able to boot.

Looks like the issue is with SELinux context some where.

On Mon, Mar 21, 2011 at 12:23 AM, cornel panceac  wrote:

>
>
> 2011/3/20 Petrus de Calguarium 
>
>> Ian Pilcher wrote:
>>
>> > Has this problem been bugzilla'ed, BTW?
>>
>> Yes, I did a couple of hours ago.
>>
>
> can you please tell us the bug number?
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>

-
vamsi
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Rawhide startup strangeness

2011-03-20 Thread Michał Piotrowski 
Hi,

2011/3/20 Steven I Usdansky :
> Not sure if this is probably related to the F15 not starting problem,
> but thought I'd report my experience. Upgraded my Rawhide installation
> earlier this morning (9:24 AM CDT). Shut down the computer and attempted
> to reboot into Rawhide. Boot process hung for at least three minutes,
> at which point I got impatient and rebooted with init=/sbin/upstart,
> which worked. Shut down the computer, went to lunch, came back, and
> turned on the computer, booting into Rawhide without init=/sbin/upstart.
> Boot process completed at expected.

To fix it you can downgrade rsyslog or disable selinux.


-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Fedora 13 updates-testing report

2011-03-20 Thread updates 
The following Fedora 13 Security updates need testing:

https://admin.fedoraproject.org/updates/libvirt-0.8.2-3.fc13
https://admin.fedoraproject.org/updates/dbus-1.2.24-2.fc13
https://admin.fedoraproject.org/updates/krb5-1.7.1-18.fc13
https://admin.fedoraproject.org/updates/tor-0.2.1.29-1300.fc13
https://admin.fedoraproject.org/updates/php-pear-1.9.2-1.fc13
https://admin.fedoraproject.org/updates/libxml2-2.7.7-2.fc13
https://admin.fedoraproject.org/updates/dhcp-4.1.2-2.ESV.R1.fc13
https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13
https://admin.fedoraproject.org/updates/mailman-2.1.12-17.fc13

https://admin.fedoraproject.org/updates/php-5.3.6-1.fc13,maniadrive-1.2-27.fc13,php-eaccelerator-0.9.6.1-6.fc13
https://admin.fedoraproject.org/updates/libtiff-3.9.4-3.fc13
https://admin.fedoraproject.org/updates/389-admin-1.1.15-1.fc13
https://admin.fedoraproject.org/updates/gnash-0.8.9-1.fc13
https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13
https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc13
https://admin.fedoraproject.org/updates/postfix-2.7.3-1.fc13
https://admin.fedoraproject.org/updates/mhonarc-2.6.18-3.fc13


The following Fedora 13 Critical Path updates have yet to be approved:

https://admin.fedoraproject.org/updates/selinux-policy-3.7.19-101.fc13
https://admin.fedoraproject.org/updates/policycoreutils-2.0.83-33.4.fc13
https://admin.fedoraproject.org/updates/tzdata-2011d-1.fc13
https://admin.fedoraproject.org/updates/tzdata-2011b-3.fc13

https://admin.fedoraproject.org/updates/perl-ExtUtils-XSpp-0.15-2.fc13,perl-5.10.1-122.fc13,perl-Wx-0.98-5.fc13
https://admin.fedoraproject.org/updates/libxml2-2.7.7-2.fc13
https://admin.fedoraproject.org/updates/fuse-2.8.5-5.fc13
https://admin.fedoraproject.org/updates/NetworkManager-0.8.3.997-1.fc13
https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13
https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13
https://admin.fedoraproject.org/updates/livecd-tools-13.2-1.fc13
https://admin.fedoraproject.org/updates/lua-5.1.4-7.fc13
https://admin.fedoraproject.org/updates/librsvg2-2.26.3-3.fc13

https://admin.fedoraproject.org/updates/mobile-broadband-provider-info-1.20110218-1.fc13
https://admin.fedoraproject.org/updates/dosfstools-3.0.9-4.fc13
https://admin.fedoraproject.org/updates/file-5.04-7.fc13
https://admin.fedoraproject.org/updates/system-config-users-1.2.107-1.fc13
https://admin.fedoraproject.org/updates/python-ethtool-0.6-1.fc13
https://admin.fedoraproject.org/updates/libical-0.46-2.fc13
https://admin.fedoraproject.org/updates/mash-0.5.20-1.fc13
https://admin.fedoraproject.org/updates/libfprint-0.3.0-1.fc13

https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-7.fc13
https://admin.fedoraproject.org/updates/lldpad-0.9.26-2.fc13


The following builds have been pushed to Fedora 13 updates-testing

clustershell-1.4.3-1.fc13
colossus-0.12.1-1.fc13
dtrx-7.0-3.fc13
kvirc-4.0.4-1.fc13
mercurial-1.8.1-2.fc13
rawtherapee-3.0-0.28.a1.fc13
root-5.28.00b-1.fc13
rubyripper-0.6.0-1.fc13
sox-14.3.2-1.fc13
sqliteman-1.2.2-3.fc13
tortoisehg-1.1.10-1.fc13
wine-1.3.16-1.fc13

Details about builds:



 clustershell-1.4.3-1.fc13 (FEDORA-2011-3669)
 Python framework for efficient cluster administration

Update Information:

* clush: fixed clush -bL traceback
* nodeset: fixed issue with stdin '-' keyword
CLI tools enhancement: improved clush, clubak and nodeset commands options
CLI tools enhancement: improved clush, clubak and nodeset commands options
CLI tools enhancement: improved clush, clubak and nodeset commands options
CLI tools enhancement: improved clush, clubak and nodeset commands options

ChangeLog:

* Sat Mar 19 2011 Stephane Thiell  1.4.3-1
- update to 1.4.3
* Tue Mar 15 2011 Stephane Thiell  1.4.2-1
- update to 1.4.2




 colossus-0.12.1-1.fc13 (FEDORA-2011-3670)
 Allows people to play Titan against each other or AIs

Update Information:

Upstream is looking at dropping support for < 0.12 on the server for online 
games.

ChangeLog:

* Sat Mar  5 2011 Bruno Wolff III  - 0.12.1-1
- Upstream 0.12.1 release with a few minor bug fixes.
- Release notes at 
http://colossus.sourceforge.net/docs/RecentChangesDetails.html
* Tue Feb 15 2011 Bruno Wolff III  - 0.12

Fedora 14 updates-testing report

2011-03-20 Thread updates 
The following Fedora 14 Security updates need testing:

https://admin.fedoraproject.org/updates/libcgroup-0.36.2-6.fc14
https://admin.fedoraproject.org/updates/libvirt-0.8.3-6.fc14
https://admin.fedoraproject.org/updates/krb5-1.8.2-9.fc14
https://admin.fedoraproject.org/updates/couchdb-1.0.2-1.fc14
https://admin.fedoraproject.org/updates/mailman-2.1.13-7.fc14
https://admin.fedoraproject.org/updates/php-pear-1.9.2-1.fc14

https://admin.fedoraproject.org/updates/mono-addins-0.5-2.fc14,mono-2.6.7-4.fc14
https://admin.fedoraproject.org/updates/389-admin-1.1.15-1.fc14
https://admin.fedoraproject.org/updates/tor-0.2.1.29-1400.fc14
https://admin.fedoraproject.org/updates/gnash-0.8.9-1.fc14
https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14

https://admin.fedoraproject.org/updates/php-5.3.6-1.fc14,php-eaccelerator-0.9.6.1-6.fc14,maniadrive-1.2-27.fc14
https://admin.fedoraproject.org/updates/exim-4.72-2.fc14
https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc14
https://admin.fedoraproject.org/updates/postfix-2.7.3-1.fc14
https://admin.fedoraproject.org/updates/avahi-0.6.27-6.fc14
https://admin.fedoraproject.org/updates/pure-ftpd-1.0.30-1.fc14
https://admin.fedoraproject.org/updates/mhonarc-2.6.18-3.fc14


The following Fedora 14 Critical Path updates have yet to be approved:

https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14
https://admin.fedoraproject.org/updates/gdb-7.2-48.fc14
https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-35.fc14
https://admin.fedoraproject.org/updates/cronie-1.4.7-1.fc14
https://admin.fedoraproject.org/updates/tzdata-2011d-1.fc14
https://admin.fedoraproject.org/updates/tzdata-2011b-3.fc14

https://admin.fedoraproject.org/updates/perl-ExtUtils-XSpp-0.15-2.fc14,perl-5.12.3-142.fc14,perl-Wx-0.98-5.fc14
https://admin.fedoraproject.org/updates/avahi-0.6.27-6.fc14
https://admin.fedoraproject.org/updates/libconfig-1.4.6-1.fc14
https://admin.fedoraproject.org/updates/lua-5.1.4-7.fc14

https://admin.fedoraproject.org/updates/mobile-broadband-provider-info-1.20110218-1.fc14
https://admin.fedoraproject.org/updates/xorg-x11-drv-geode-2.11.11-4.fc14


The following builds have been pushed to Fedora 14 updates-testing

PyXB-1.1.2-1.fc14
cclive-0.7.3.1-1.fc14
clive-2.3.0.2-1.fc14
clustershell-1.4.3-1.fc14
colossus-0.12.1-1.fc14
dtrx-7.0-3.fc14
gdcm-2.0.16-14.fc14
kvirc-4.0.4-1.fc14
mercurial-1.8.1-2.fc14
quvi-0.2.14-1.fc14
rawtherapee-3.0-0.28.a1.fc14
rkward-0.5.5-1.fc14
root-5.28.00b-1.fc14
rubyripper-0.6.0-1.fc14
sdcc-3.0.0-0.fc14
sox-14.3.2-1.fc14
sqliteman-1.2.2-3.fc14
tortoisehg-1.1.10-1.fc14
wine-1.3.16-1.fc14

Details about builds:



 PyXB-1.1.2-1.fc14 (FEDORA-2011-3688)
 Python XML Schema Bindings

Update Information:

PyXB - Python XML Schema Bindings

References:

  [ 1 ] Bug #688663 - Review Request: PyXB - Python XML Schema Bindings
https://bugzilla.redhat.com/show_bug.cgi?id=688663




 cclive-0.7.3.1-1.fc14 (FEDORA-2011-3698)
 Command line video extraction utility

Update Information:

Update to 0.7.3.1

ChangeLog:

* Sun Mar 20 2011 Nicoleau Fabien  0.7.3.1-1
- Update to 0.7.3.1
* Sun Mar 13 2011 Nicoleau Fabien  0.7.3-1
- Update to 0.7.3
* Mon Feb 14 2011 Nicoleau Fabien  0.7.2-1
- Update to 0.7.2
* Sun Feb 13 2011 Nicoleau Fabien  0.6.5-3
- Add an include to compile with new GCC
* Tue Feb  8 2011 Fedora Release Engineering  
- 0.6.5-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild




 clive-2.3.0.2-1.fc14 (FEDORA-2011-3692)
 Video extraction tool for user-uploaded video hosts

Update Information:

Update to 2.3.0.2

ChangeLog:

* Sun Mar 20 2011 Nicoleau Fabien  2.3.0.2-1
- Update to 2.3.0.2




 clustershell-1.4.3-1.fc14 (FEDORA-2011-3672)
 Python framework for efficient cluster administration
--

Rawhide startup strangeness

2011-03-20 Thread Steven I Usdansky 
Not sure if this is probably related to the F15 not starting problem,
but thought I'd report my experience. Upgraded my Rawhide installation
earlier this morning (9:24 AM CDT). Shut down the computer and attempted
to reboot into Rawhide. Boot process hung for at least three minutes,
at which point I got impatient and rebooted with init=/sbin/upstart,
which worked. Shut down the computer, went to lunch, came back, and
turned on the computer, booting into Rawhide without init=/sbin/upstart.
Boot process completed at expected. 


  
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Mismatch between FC15 kernel and kernel-devel

2011-03-20 Thread Chuck Forsberg WA7KGX N2469R 
This mismatch causes the Nvidia run file installer to abend.
Please get the versions right.

Better yet, include kernel-devel files in the live CD.

I sure do miss being able to rsync the repository and
then do a quick local network install with pxeboot.

-- 
Chuck Forsberg WA7KGX N2469R c...@omen.com   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
   Omen Technology Inc  "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
W dniu 20 marca 2011 21:28 użytkownik Genes MailLists
 napisał:
> On 03/20/2011 04:20 PM, Michał Piotrowski wrote:
>
>>>
>>> what happens if you replace After= with Wants= ?
>>
>> After is used to define order in which services should be started.
>> Wants is used to define required dependencies.
>>
>>
>>
>
> so replace it with:
>
>  Prefers.foo
>  Prefers.foo.DontWaitMoreThan
>
> perhaps ...

Maybe something like
After=network.target
AfterNotAbsolutelyRequired=syslog.target

But the solution depends on Lennart. He knows systemd best and it's up
to him how things works.

-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Genes MailLists 
On 03/20/2011 04:20 PM, Michał Piotrowski wrote:

>>
>> what happens if you replace After= with Wants= ?
> 
> After is used to define order in which services should be started.
> Wants is used to define required dependencies.
> 
> 
> 

so replace it with:

  Prefers.foo
  Prefers.foo.DontWaitMoreThan

perhaps ...

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
W dniu 20 marca 2011 21:06 użytkownik cornel panceac
 napisał:
>
>
> 2011/3/20 Michał Piotrowski 
>>
>> W dniu 20 marca 2011 20:54 użytkownik cornel panceac
>>  napisał:
>> >
>> >
>> > 2011/3/20 Genes MailLists 
>> >>
>> >> On 03/20/2011 03:43 PM, Michał Piotrowski wrote:
>> >>
>> >> >
>> >> > In a stable distribution such situation would not be possible because
>> >> > of the whole testing procedures etc.
>> >> >
>> >> > But of course there should be a way to avoid such situation. I hope
>> >> > that Lennart will find a good way to solve this problem soon.
>> >> >
>> >> >
>> >> >
>> >>
>> >>  Then make the variable timeout default to 30 secs - so worst case
>> >> services get started and system runs ... individual services which
>> >> actually require the pre-requisite - can change the timeout variable to
>> >> demand pre-req is satisfied - of course even these will presumably fail
>> >> (hopeflly gracefully).
>> >>
>> >>  So the answer seems to be implement a timeout for pre-requisites and
>> >> default it to something sensible - ... fixup any upstart files as
>> >> needed
>> >> - since the systemd unit files are all new anyway - we should be fine
>> >> with this.
>> >>
>> > although i understand the general idea about systemd, i believe that in
>> > fedora's case there has to be a plan which says who starts when, and
>> > what
>> > requires what. then, if thngs don't go that well, as it happened with
>> > this
>> > rsyslog update, the plan can be imporved.
>> > --
>> > test mailing list
>> > test@lists.fedoraproject.org
>> > To unsubscribe:
>> > https://admin.fedoraproject.org/mailman/listinfo/test
>> >
>>
>> Unfortunately it is not so simple. For example we have a service
>> After=syslog.target network.target
>> and for some reason network configuration takes longer than 30 seconds
>> so the service does not start when default timeout will be short and
>> will cover all dependences.
>
> what happens if you replace After= with Wants= ?

After is used to define order in which services should be started.
Wants is used to define required dependencies.



-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Antonio Olivares 


--- On Sun, 3/20/11, Genes MailLists  wrote:

> From: Genes MailLists 
> Subject: Re: optimizing systemd, was: f15 no longer starts
> To: "For testers of Fedora development releases" 
> 
> Date: Sunday, March 20, 2011, 11:04 AM
> On 03/20/2011 01:57 AM, cornel
> panceac wrote:
> > 
> > 
> 
> > 
> > indeed, yum downgrade rsyslog fixed it. can systemd be
> configured in
> > such a way that not so important services are not
> preventing the system
> > to work properly?
> > 
> > 
> 
>   Agreed - logging failure probably should not prevent
> the system from
> starting .. that sounds not right to me.
> -- 

It is selinux that is denying the startup, system will work, but you need to 
start with it disabled :(

I downgraded rsyslog package to get a working desktop in the meantime there is 
a bugzilla already:

https://bugzilla.redhat.com/show_bug.cgi?id=689089

Regards,

Antonio 


  
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread cornel panceac 
2011/3/20 Michał Piotrowski 

> W dniu 20 marca 2011 20:54 użytkownik cornel panceac
>  napisał:
> >
> >
> > 2011/3/20 Genes MailLists 
> >>
> >> On 03/20/2011 03:43 PM, Michał Piotrowski wrote:
> >>
> >> >
> >> > In a stable distribution such situation would not be possible because
> >> > of the whole testing procedures etc.
> >> >
> >> > But of course there should be a way to avoid such situation. I hope
> >> > that Lennart will find a good way to solve this problem soon.
> >> >
> >> >
> >> >
> >>
> >>  Then make the variable timeout default to 30 secs - so worst case
> >> services get started and system runs ... individual services which
> >> actually require the pre-requisite - can change the timeout variable to
> >> demand pre-req is satisfied - of course even these will presumably fail
> >> (hopeflly gracefully).
> >>
> >>  So the answer seems to be implement a timeout for pre-requisites and
> >> default it to something sensible - ... fixup any upstart files as needed
> >> - since the systemd unit files are all new anyway - we should be fine
> >> with this.
> >>
> > although i understand the general idea about systemd, i believe that in
> > fedora's case there has to be a plan which says who starts when, and what
> > requires what. then, if thngs don't go that well, as it happened with
> this
> > rsyslog update, the plan can be imporved.
> > --
> > test mailing list
> > test@lists.fedoraproject.org
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/test
> >
>
> Unfortunately it is not so simple. For example we have a service
> After=syslog.target network.target
> and for some reason network configuration takes longer than 30 seconds
> so the service does not start when default timeout will be short and
> will cover all dependences.
>

what happens if you replace After= with Wants= ?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
W dniu 20 marca 2011 20:54 użytkownik cornel panceac
 napisał:
>
>
> 2011/3/20 Genes MailLists 
>>
>> On 03/20/2011 03:43 PM, Michał Piotrowski wrote:
>>
>> >
>> > In a stable distribution such situation would not be possible because
>> > of the whole testing procedures etc.
>> >
>> > But of course there should be a way to avoid such situation. I hope
>> > that Lennart will find a good way to solve this problem soon.
>> >
>> >
>> >
>>
>>  Then make the variable timeout default to 30 secs - so worst case
>> services get started and system runs ... individual services which
>> actually require the pre-requisite - can change the timeout variable to
>> demand pre-req is satisfied - of course even these will presumably fail
>> (hopeflly gracefully).
>>
>>  So the answer seems to be implement a timeout for pre-requisites and
>> default it to something sensible - ... fixup any upstart files as needed
>> - since the systemd unit files are all new anyway - we should be fine
>> with this.
>>
> although i understand the general idea about systemd, i believe that in
> fedora's case there has to be a plan which says who starts when, and what
> requires what. then, if thngs don't go that well, as it happened with this
> rsyslog update, the plan can be imporved.
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>

Unfortunately it is not so simple. For example we have a service
After=syslog.target network.target
and for some reason network configuration takes longer than 30 seconds
so the service does not start when default timeout will be short and
will cover all dependences.

-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread cornel panceac 
2011/3/20 Genes MailLists 

> On 03/20/2011 03:43 PM, Michał Piotrowski wrote:
>
> >
> > In a stable distribution such situation would not be possible because
> > of the whole testing procedures etc.
> >
> > But of course there should be a way to avoid such situation. I hope
> > that Lennart will find a good way to solve this problem soon.
> >
> >
> >
>
>  Then make the variable timeout default to 30 secs - so worst case
> services get started and system runs ... individual services which
> actually require the pre-requisite - can change the timeout variable to
> demand pre-req is satisfied - of course even these will presumably fail
> (hopeflly gracefully).
>
>  So the answer seems to be implement a timeout for pre-requisites and
> default it to something sensible - ... fixup any upstart files as needed
> - since the systemd unit files are all new anyway - we should be fine
> with this.
>
> although i understand the general idea about systemd, i believe that in
fedora's case there has to be a plan which says who starts when, and what
requires what. then, if thngs don't go that well, as it happened with this
rsyslog update, the plan can be imporved.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20110320 changes

2011-03-20 Thread Rawhide Report 
Compose started at Sun Mar 20 08:15:20 UTC 2011

Broken deps for x86_64
--
audacious-plugin-xmp-3.3.0-6.fc15.x86_64 requires audacious(plugin-api) 
= 0:17
byzanz-0.2.2-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit)
castor-0.9.5-6.fc15.1.x86_64 requires oro
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Oassocb) = 
0:d873c4a1eeb6fa5c5333f8658c49d1db
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Ograph2way) = 
0:7442f647b0a74ed48a5c9361fc42ccc4
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Flag) = 
0:522d7f86f1236405e53271ff74923515
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Osetb) = 
0:8f21a0a4f771662673604ed92a237d79
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Oseti) = 
0:a937e7661f510c17bfd21d4372507795
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Sexplib) = 
0:a990ea80438337d5407bbc0343c7236a
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Setb) = 
0:93bdb588146a13126bfad4eab6c58206
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Oassoc_buffer) = 
0:cf6fbee4fcc6644a0a90f07da8eb6c7b
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Mapb) = 
0:617c09a110cef9f040335b35078c7234
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Oassoch) = 
0:87f7dc2635e5a7ed1ab03b7cd5380ace
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(Dumper) = 
0:76126ba149caeb2d34f12e11187a9d4e
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(SetPt) = 
0:b69c030e8ca717d556d3d9bd2a5d22fd
coccinelle-0.2.5-0.rc4.3.fc16.x86_64 requires ocaml(ANSITerminal) = 
0:3d0d1700618d8b3a4e4b2308f28cefb6
conmux-0.0-12.493svn.fc15.noarch requires perl(Payload)
conmux-0.0-12.493svn.fc15.noarch requires perl(Client)
cpm-0.23-0.3.beta.fc12.x86_64 requires libdotconf-1.0.so.0()(64bit)
db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0
dbmail-3.0.0-0.3.rc1.fc15.x86_64 requires libevent-1.4.so.2()(64bit)
dbmail-auth-ldap-3.0.0-0.3.rc1.fc15.x86_64 requires 
libevent-1.4.so.2()(64bit)
dh-make-0.55-3.fc15.noarch requires debhelper
eog-plugins-2.30.0-2.fc14.x86_64 requires libgdata.so.7()(64bit)
1:fife-0.3.2-1.fc15.i686 requires libboost_regex.so.1.44.0
1:fife-0.3.2-1.fc15.i686 requires libboost_system.so.1.44.0
1:fife-0.3.2-1.fc15.i686 requires libboost_filesystem.so.1.44.0
1:fife-0.3.2-1.fc15.x86_64 requires libboost_regex.so.1.44.0()(64bit)
1:fife-0.3.2-1.fc15.x86_64 requires libboost_system.so.1.44.0()(64bit)
1:fife-0.3.2-1.fc15.x86_64 requires 
libboost_filesystem.so.1.44.0()(64bit)
file-browser-applet-0.6.6-1.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gambas2-gb-pdf-2.22.0-3.fc15.x86_64 requires libpoppler.so.12()(64bit)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::ScrolledWindow)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MessageDialog)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Dialog)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Toolbar)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::TreeView)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MenuBar)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::VBox)
gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Window)
gdal-1.7.3-2.fc15.i686 requires libxerces-c-3.0.so
gdal-1.7.3-2.fc15.x86_64 requires libxerces-c-3.0.so()(64bit)
gdal-java-1.7.3-2.fc15.i686 requires libxerces-c-3.0.so
gdal-java-1.7.3-2.fc15.x86_64 requires libxerces-c-3.0.so()(64bit)
gdal-perl-1.7.3-2.fc15.x86_64 requires libxerces-c-3.0.so()(64bit)
gdal-ruby-1.7.3-2.fc15.x86_64 requires libxerces-c-3.0.so()(64bit)
gedit-valencia-0.3.0-4.fc14.x86_64 requires libvala-0.10.so.0()(64bit)
glom-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit)
glom-libs-1.16.1-2.fc15.i686 requires libgdamm-4.0.so.12
glom-libs-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit)
glunarclock-0.34.1-1.fc14.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-cpufire-1.6-3.fc14.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-music-2.5.1-5.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0
gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires 
libpanel-applet-2.so.0()(64bit)
gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2)
gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Genes MailLists 
On 03/20/2011 03:43 PM, Michał Piotrowski wrote:

> 
> In a stable distribution such situation would not be possible because
> of the whole testing procedures etc.
> 
> But of course there should be a way to avoid such situation. I hope
> that Lennart will find a good way to solve this problem soon.
> 
> 
> 

 Then make the variable timeout default to 30 secs - so worst case
services get started and system runs ... individual services which
actually require the pre-requisite - can change the timeout variable to
demand pre-req is satisfied - of course even these will presumably fail
(hopeflly gracefully).

 So the answer seems to be implement a timeout for pre-requisites and
default it to something sensible - ... fixup any upstart files as needed
- since the systemd unit files are all new anyway - we should be fine
with this.

g
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
W dniu 20 marca 2011 20:30 użytkownik Petrus de Calguarium
 napisał:
> Michał Piotrowski wrote:
>
>> Hmm... I'm not sure if it's reasonable - this will require
>> modification of many systemd services.
>
> I don't know whether modifying services is reasonable

It's _really_ difficult to add systemd service to Fedora and I suspect
that changing existing services also will be difficult.

>, but what is not
> reasonable is for a user no longer to be able to boot his system and not to be
> able to log in after an update. For the less experienced user, this particular
> problem required a reinstallation of the system. For me, a somewhat more savvy
> user, this required using all the skills I had just to avoid reinstallation,
> and only a tip on this list from another affected user to get me out of an
> unsolvable situation.
>
> A possible solution would be to have both updates and updates-testing repos 
> for
> all fedoras, even the not yet released branched fedora. I would prefer not to
> run updates-testing, but I do want to run Fedora-alpha as soon as it is
> available. As it stands at present, updates-testing is automatically enabled,
> whether a user wants it or not, and there is no other way to get updates 
> except
> to keep updates-testing enabled. As I said, I like running the experimental
> system, but updates-testing is a bit to racey for me.
>

In a stable distribution such situation would not be possible because
of the whole testing procedures etc.

But of course there should be a way to avoid such situation. I hope
that Lennart will find a good way to solve this problem soon.



-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Petrus de Calguarium 
Michał Piotrowski wrote:

> Hmm... I'm not sure if it's reasonable - this will require
> modification of many systemd services.

I don't know whether modifying services is reasonable, but what is not 
reasonable is for a user no longer to be able to boot his system and not to be 
able to log in after an update. For the less experienced user, this particular 
problem required a reinstallation of the system. For me, a somewhat more savvy 
user, this required using all the skills I had just to avoid reinstallation, 
and only a tip on this list from another affected user to get me out of an 
unsolvable situation.

A possible solution would be to have both updates and updates-testing repos for 
all fedoras, even the not yet released branched fedora. I would prefer not to 
run updates-testing, but I do want to run Fedora-alpha as soon as it is 
available. As it stands at present, updates-testing is automatically enabled, 
whether a user wants it or not, and there is no other way to get updates except 
to keep updates-testing enabled. As I said, I like running the experimental 
system, but updates-testing is a bit to racey for me.

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
W dniu 20 marca 2011 19:48 użytkownik Genes MailLists
 napisał:
> On 03/20/2011 02:41 PM, Michał Piotrowski wrote:
>
>>
>> Perhaps the problem is that most systemd services requires to start
>> them when rsyslog is running
>> After=syslog.target
>>
>> This should be fixed somehow - there should be a way to tell systemd
>> that service B isn't critical to start service A and service A can be
>> started after some time if service B refuses to start.
>>
>
>  This sounds reasonable ..

Hmm... I'm not sure if it's reasonable - this will require
modification of many systemd services.

> and I imagine pretty simple to implement - I
> suspect LP has already implemented it :-) yes ?

-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread cornel panceac 
2011/3/20 Rahul Sundaram 

> On 03/20/2011 11:34 PM, Genes MailLists wrote:
> > On 03/20/2011 01:57 AM, cornel panceac wrote:
> > indeed, yum downgrade rsyslog fixed it. can systemd be configured in
> > such a way that not so important services are not preventing the system
> > to work properly?
> >
> >
> >   Agreed - logging failure probably should not prevent the system from
> > starting .. that sounds not right to me.
>
> Glad we have consensus.  Now would someone file a bug report please?
>
> Rahul
>
>
i've found this:
https://bugzilla.redhat.com/show_bug.cgi?id=689163
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F15 Alpha will not start after my last yum update

2011-03-20 Thread cornel panceac 
2011/3/20 Petrus de Calguarium 

> Ian Pilcher wrote:
>
> > Has this problem been bugzilla'ed, BTW?
>
> Yes, I did a couple of hours ago.
>

can you please tell us the bug number?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Rahul Sundaram 
On 03/20/2011 11:34 PM, Genes MailLists wrote:
> On 03/20/2011 01:57 AM, cornel panceac wrote:
> indeed, yum downgrade rsyslog fixed it. can systemd be configured in
> such a way that not so important services are not preventing the system
> to work properly?
>
>
>   Agreed - logging failure probably should not prevent the system from
> starting .. that sounds not right to me.

Glad we have consensus.  Now would someone file a bug report please?

Rahul

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Genes MailLists 
On 03/20/2011 02:41 PM, Michał Piotrowski wrote:

> 
> Perhaps the problem is that most systemd services requires to start
> them when rsyslog is running
> After=syslog.target
> 
> This should be fixed somehow - there should be a way to tell systemd
> that service B isn't critical to start service A and service A can be
> started after some time if service B refuses to start.
> 

  This sounds reasonable .. and I imagine pretty simple to implement - I
suspect LP has already implemented it :-) yes ?


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Michał Piotrowski 
Hi,

2011/3/20 Genes MailLists :
> On 03/20/2011 01:57 AM, cornel panceac wrote:
>>
>>
>
>>
>> indeed, yum downgrade rsyslog fixed it. can systemd be configured in
>> such a way that not so important services are not preventing the system
>> to work properly?
>>
>>
>
>  Agreed - logging failure probably should not prevent the system from
> starting .. that sounds not right to me.

Perhaps the problem is that most systemd services requires to start
them when rsyslog is running
After=syslog.target

This should be fixed somehow - there should be a way to tell systemd
that service B isn't critical to start service A and service A can be
started after some time if service B refuses to start.

Maybe it is possible, but I can not find anything like this in
http://0pointer.de/public/systemd-man/systemd.unit.html

-- 
Best regards,
Michal

http://eventhorizon.pl/
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: problems at very early stage installing Fedora 15 alpha in Virtualbox 4.0.4/Mac OS X

2011-03-20 Thread Sven Aluoor 
On 3/20/11 5:23 PM, Adam Huffman wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=689258

Quote from Bug 682555

The minimum memory required is 1GB, due to anaconda changes. When you 
see "populate_rootfs" in the panic, it's caused by that.

Fedora is the same fat as M$ Windows 7. Sad.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: optimizing systemd, was: f15 no longer starts

2011-03-20 Thread Genes MailLists 
On 03/20/2011 01:57 AM, cornel panceac wrote:
> 
> 

> 
> indeed, yum downgrade rsyslog fixed it. can systemd be configured in
> such a way that not so important services are not preventing the system
> to work properly?
> 
> 

  Agreed - logging failure probably should not prevent the system from
starting .. that sounds not right to me.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: f15 no longer starts

2011-03-20 Thread Genes MailLists 
On 03/19/2011 11:10 PM, Petrus de Calguarium wrote:
> Vaclav Misek wrote:
> 
>> it was the rsyslog package.
> 
> Thanks a million!
> 
> yum downgrade rsyslog
> 
> cured it. I am back using F15 again.
> 

 I'm curious - how does a bad rsyslog package prevent the system from
booting ? Should it ??

  That feels too brittle to me ... I mean its only logging after all
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: problems at very early stage installing Fedora 15 alpha in Virtualbox 4.0.4/Mac OS X

2011-03-20 Thread Adam Huffman 
On Sun, Mar 20, 2011 at 4:02 PM, Rahul Sundaram  wrote:
> On 03/20/2011 06:03 PM, Adam Huffman wrote:
>> On Sun, Mar 20, 2011 at 6:02 AM, Rahul Sundaram  wrote:
>>> On 03/20/2011 01:58 AM, Sven Aluoor wrote:
 Hi

 I tried the install option "Install system with basic video driver"
 and the normal one. The problems accur before normal installer. See
 screen shot http://i.imgur.com/4GBKW.png
>>> Please report bugs to Red Hat Bugzilla
>>>
>>> http://fedoraproject.org/wiki/How_to_file_a_bug_report
>>>
>>> Rahu
>>>
>> I'm seeing something similar with KVM/libvirt - which is the correct
>> component for this?  Anaconda?
>
> File it there.  Can be reassigned if necessary
>

Done:

https://bugzilla.redhat.com/show_bug.cgi?id=689258
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: problems at very early stage installing Fedora 15 alpha in Virtualbox 4.0.4/Mac OS X

2011-03-20 Thread Rahul Sundaram 
On 03/20/2011 06:03 PM, Adam Huffman wrote:
> On Sun, Mar 20, 2011 at 6:02 AM, Rahul Sundaram  wrote:
>> On 03/20/2011 01:58 AM, Sven Aluoor wrote:
>>> Hi
>>>
>>> I tried the install option "Install system with basic video driver"
>>> and the normal one. The problems accur before normal installer. See
>>> screen shot http://i.imgur.com/4GBKW.png
>> Please report bugs to Red Hat Bugzilla
>>
>> http://fedoraproject.org/wiki/How_to_file_a_bug_report
>>
>> Rahu
>>
> I'm seeing something similar with KVM/libvirt - which is the correct
> component for this?  Anaconda?

File it there.  Can be reassigned if necessary

Rahul

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Problems with "system-config-printer" after todays morning updates

2011-03-20 Thread Tim Waugh 
On Sun, 2011-03-20 at 07:36 +0100, Joachim Backes wrote:
> Option 'printer-resolution' has value '(unknown IPP tag)' and cannot be 
> edited.

Should be addressed by:
  https://admin.fedoraproject.org/updates/python-cups-1.9.55-1.fc15

...which I've just submitted for testing.

Tim.
*/



signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: problems at very early stage installing Fedora 15 alpha in Virtualbox 4.0.4/Mac OS X

2011-03-20 Thread Adam Huffman 
On Sun, Mar 20, 2011 at 6:02 AM, Rahul Sundaram  wrote:
> On 03/20/2011 01:58 AM, Sven Aluoor wrote:
>> Hi
>>
>> I tried the install option "Install system with basic video driver"
>> and the normal one. The problems accur before normal installer. See
>> screen shot http://i.imgur.com/4GBKW.png
>
> Please report bugs to Red Hat Bugzilla
>
> http://fedoraproject.org/wiki/How_to_file_a_bug_report
>
> Rahu
>

I'm seeing something similar with KVM/libvirt - which is the correct
component for this?  Anaconda?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Install to Hard Drive option in User Switch Panel not responding + issues with tty1 tty3 and tty5

2011-03-20 Thread Pratyush Sahay 
Hello all,

Tried the Nightly Compose of 18-3-2011 (i686 Live Media)
The "Install To Hard Drive" option in the User Switch Panel doesnt respond.
But, the "Install To Hard Drive" option in Favourites Menu works fine and
initiates Anaconda.

Also, in Live user mode:
tty1 (ctrl+Alt+F1) is showing a gray colored box around the text till the
log-in prompt ;
tty3 (ctrl+Alt+F3) and tty5 (ctrl+Alt+F5) is showing lots of text till the
log-in prompt.
However, this issue doesnt show up in fallback mode (tried in Virtualbox)

--
Regards,

Pratyush Sahay
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Sometimes nothing happens if pressing the Activities button in gnome-shell

2011-03-20 Thread Joachim Backes 

dear testers,

I see it *rather often* that if pressing the Activities button on the 
gnome-shell desktop, nothing happens (no favorites bar). But if I press 
the windows key, the favorites bar appears immediately.


Additionally, if pressing *sometimes* the Activities->Applications 
button, nothing happens.


But in most other cases, pressing these buttons has the desired effect.

Somebody has seen this too?

Kind regards

Joachim Backes 

http://www.rhrk.uni-kl.de/~backes



smime.p7s
Description: S/MIME Cryptographic Signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test