Re: BEWARE: a problematic glibc made it to stable (F16)

2011-10-20 Thread Rahul Sundaram
On 10/20/2011 06:05 AM, Josh Boyer wrote: > > Except that Fedora _has_ been glibc's development platform for as long > as I can remember. The Fedora project might not think so, but it's > exactly what upstream glibc does. I am aware of this but our policies have changed and either they need to

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Lennart Poettering
On Thu, 20.10.11 07:46, Matthew Miller (mat...@mattdm.org) wrote: > > On Mon, Oct 17, 2011 at 07:10:04PM +0200, Lennart Poettering wrote: > > In general doing something like this is a bit backwards since networks > > come and go and come and go in todays world, and we also don't want to > > This

Re: yubikey

2011-10-20 Thread Paul Wouters
On Thu, 20 Oct 2011, Nathan O. wrote: > slot 1: fedora OTP configured with fedora-burn-yubikey -u > slot 2: yubico OTP. Using the command line tool shipped with fedora > gave me some problems, so I used the one from yubico > > (http://wiki.yubico.com/files/YubiKey%20Person

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Bruno Wolff III
On Mon, Oct 17, 2011 at 19:10:04 +0200, Lennart Poettering wrote: > > So, while my first response to this would be the suggestion to improve > the sw in question to make it more robust to today's dynamic networking > I do acknowledge that this is not always feasible. So > here's what you can do

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Jef Spaleta
On Thu, Oct 20, 2011 at 1:03 PM, Nicolas Mailhot wrote: > The problem is mostly integration with networked apps, which are either > of the 'network can be up or not, if it's up always do foo' kind, or the > 'can manage multiple networks, but expects all of them to exist at > startup'. There is a d

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Nicolas Mailhot
Le jeudi 20 octobre 2011 à 12:40 -0800, Jef Spaleta a écrit : > And NM's dispatcher.d capability doesn't allow you to define and > remember per connection rules of the complexity you need? The problem is mostly integration with networked apps, which are either of the 'network can be up or not, if

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Jef Spaleta
On Thu, Oct 20, 2011 at 12:26 PM, Nicolas Mailhot wrote: > On anything more complex a new connexion will usually be established in > addition to the existing ones, and will have a specific pre-set > configuration. For example, a port can be dedicated to guest systems, or > communication with speci

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Nicolas Mailhot
Le jeudi 20 octobre 2011 à 11:59 -0800, Jef Spaleta a écrit : > On Thu, Oct 20, 2011 at 11:51 AM, Nicolas Mailhot > wrote: > > No, it's an attempt to explain a general concept and not to point the > > finger at anyone. Because as soon as you provide specifics, someone will > > feel offended, get d

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Jef Spaleta
On Thu, Oct 20, 2011 at 11:51 AM, Nicolas Mailhot wrote: > No, it's an attempt to explain a general concept and not to point the > finger at anyone. Because as soon as you provide specifics, someone will > feel offended, get defensive, and refuse to listen to the general > message. I'd honestly l

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Nicolas Mailhot
Le jeudi 20 octobre 2011 à 12:27 -0700, Adam Williamson a écrit : > On Thu, 2011-10-20 at 21:22 +0200, Nicolas Mailhot wrote: > > Le jeudi 20 octobre 2011 à 13:08 -0500, Dan Williams a écrit : > > > > > If you architect a system that accounts for networking changing states, > > > then it works for

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Adam Williamson
On Thu, 2011-10-20 at 21:22 +0200, Nicolas Mailhot wrote: > Le jeudi 20 octobre 2011 à 13:08 -0500, Dan Williams a écrit : > > > If you architect a system that accounts for networking changing states, > > then it works for *everyone*. If you depend on networking always being > > there, then it on

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Nicolas Mailhot
Le jeudi 20 octobre 2011 à 13:08 -0500, Dan Williams a écrit : > If you architect a system that accounts for networking changing states, > then it works for *everyone*. If you depend on networking always being > there, then it only works for some subset of users that have one type of > installati

Self-Introduction

2011-10-20 Thread Solomon Peachy
Howdy, folks! My name is Solomon Peachy, and I've been using the handle 'pizza' since before my PFY days. I've been doing this Linux thing for quite some time now -- My home directory dates back to Red Hat Linux 4.2, and I've been using Linux as my primary desktop for more than a decade, but i

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Dan Williams
On Thu, 2011-10-20 at 07:46 -0400, Matthew Miller wrote: > On Mon, Oct 17, 2011 at 07:10:04PM +0200, Lennart Poettering wrote: > > In general doing something like this is a bit backwards since networks > > come and go and come and go in todays world, and we also don't want to > > This seems like a

[Test-Announce] 2011-10-21 @ 17:00 UTC - F16 Final Blocker Bug Review #4

2011-10-20 Thread Tim Flink
# F16 Final Blocker Review meeting #4 # Date: 2011-10-21 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) # Location: #fedora-bugzappers on irc.freenode.net The fourth Fedora 16 final blocker bug review meeting will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the final

[Test-Announce] Fedora 16 Final Test Compose 2 (TC2) Available Now!

2011-10-20 Thread Andre Robatino
As per the Fedora 16 schedule [1], Fedora 16 Final Test Compose 2 (TC2) is now available for testing. Please see the following pages for download links (including delta ISOs) and testing instructions. Serverbeach1 is still available as a mirror (but with approximately a 1 hour lag behind dl), so if

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Adam Williamson
On Thu, 2011-10-20 at 07:46 -0400, Matthew Miller wrote: > On Mon, Oct 17, 2011 at 07:10:04PM +0200, Lennart Poettering wrote: > > In general doing something like this is a bit backwards since networks > > come and go and come and go in todays world, and we also don't want to > > This seems like a

[perl-Object-InsideOut] update to 3.84

2011-10-20 Thread Iain Arnell
commit 3b15d48d9c3210390d72be080bd0f9d9a7894a9f Author: Iain Arnell Date: Thu Oct 20 17:21:51 2011 +0200 update to 3.84 .gitignore |1 + perl-Object-InsideOut.spec | 34 -- sources|2 +- 3 files changed, 22 inse

File Object-InsideOut-3.84.tar.gz uploaded to lookaside cache by iarnell

2011-10-20 Thread Iain Arnell
A file has been added to the lookaside cache for perl-Object-InsideOut: 3676732d8b31fd9c6a0094e0a8a0254d Object-InsideOut-3.84.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject

[perl-Any-Moose/f16] update to 0.17

2011-10-20 Thread Iain Arnell
Summary of changes: 89d0396... update to 0.17 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mail

[perl-Wx] 0.9902

2011-10-20 Thread Tom Callaway
commit 7be4852caf5bbdd71ee194852a920bba6fe3927f Author: Tom "spot" Callaway Date: Thu Oct 20 11:01:39 2011 -0400 0.9902 .gitignore |1 + perl-Wx.spec |7 +-- sources |2 +- 3 files changed, 7 insertions(+), 3 deletions(-) --- diff --git a/.gitignore b/.gitignore ind

File Wx-0.9902.tar.gz uploaded to lookaside cache by spot

2011-10-20 Thread Tom Callaway
A file has been added to the lookaside cache for perl-Wx: df4c9098cdaa37716dca37919c026bc0 Wx-0.9902.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl

[perl-Moose/f16] add virtual provides for perl-Any-Moose

2011-10-20 Thread Iain Arnell
Summary of changes: 5a14075... add virtual provides for perl-Any-Moose (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://adm

[perl-Mouse/f16] (3 commits) ...update to 0.97

2011-10-20 Thread Iain Arnell
Summary of changes: 51548d8... update to 0.95 (*) fbe0167... clean up some rpmlint warnings (*) b19f5ce... update to 0.97 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mail

Re: yubikey

2011-10-20 Thread Nathan O.
Thanks for the help, I will put this email in Saved so I will have it later. :-) On Wed, Oct 19, 2011 at 1:54 PM, Mario Ceresa wrote: > Hello all! > > I'm an happy possessor of a yubikey and I use it both for FAS > authentication and for ssh access. > > The configuration is the following: > > slo

Re: Systemd unit file: Can/Should ExecStart and ExecStop run a script?

2011-10-20 Thread Richard Shaw
2011/10/20 "Jóhann B. Guðmundsson" : > On 10/19/2011 08:29 PM, Lennart Poettering wrote: >> The After=syslog.target is unnecessary these days and should be removed >> to keep things simple. > > If you expect upstream to ship unit files then you must realize  that > upstream needs to ship a unit fil

rawhide report: 20111020 changes

2011-10-20 Thread Rawhide Report
Compose started at Thu Oct 20 08:15:05 UTC 2011 Broken deps for x86_64 -- 389-admin-1.1.23-1.fc17.i686 requires libicuuc.so.46 389-admin-1.1.23-1.fc17.i686 requires libicui18n.so.46 389-admin-1.1.23-1.fc17.i686 require

Broken dependencies: perl-Pugs-Compiler-Rule

2011-10-20 Thread buildsys
perl-Pugs-Compiler-Rule has broken dependencies in the rawhide tree: On x86_64: perl-Pugs-Compiler-Rule-0.37-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.3) On i386: perl-Pugs-Compiler-Rule-0.37-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.3) Please resolve this as soon as

Re: BEWARE: a problematic glibc made it to stable (F16)

2011-10-20 Thread Adam Jackson
On Wed, 2011-10-19 at 20:35 -0400, Josh Boyer wrote: > Except that Fedora _has_ been glibc's development platform for as long > as I can remember. The Fedora project might not think so, but it's > exactly what upstream glibc does. Indeed, this has been the case since it was still called Red Hat

F-16 Branched report: 20111020 changes

2011-10-20 Thread Branched Report
Compose started at Thu Oct 20 08:15:18 UTC 2011 Broken deps for x86_64 -- aeolus-all-0.4.0-1.fc16.noarch requires rubygem(aeolus-cli) aeolus-conductor-0.4.0-1.fc16.noarch requires rubygem(oauth) aeolus-conductor-devel-

Re: systemd - standard place to run stuff after the network is up?

2011-10-20 Thread Matthew Miller
On Mon, Oct 17, 2011 at 07:10:04PM +0200, Lennart Poettering wrote: > In general doing something like this is a bit backwards since networks > come and go and come and go in todays world, and we also don't want to This seems like a very desktop-focused view of things. I appreciate that that's impo

Bluetooth problem that is affecting a few people

2011-10-20 Thread Steven James Drinnan
hi all I submitted a bug some time ago but there has been no response to the bug. see https://bugzilla.redhat.com/show_bug.cgi?id=735319 The bug is that after the upgrade to 2.6.40 bluetooth stopped connecting correctly to my phone (says connection refused) reverting to 2.38 fixes the problem.

Re: Systemd unit file: Can/Should ExecStart and ExecStop run a script?

2011-10-20 Thread Jóhann B. Guðmundsson
On 10/19/2011 08:29 PM, Lennart Poettering wrote: > The After=syslog.target is unnecessary these days and should be removed > to keep things simple. If you expect upstream to ship unit files then you must realize that upstream needs to ship a unit file that works across distribution on what eve

Re: Systemd unit file: Can/Should ExecStart and ExecStop run a script?

2011-10-20 Thread Jóhann B. Guðmundsson
On 10/19/2011 09:48 PM, Richard Shaw wrote: > That will work for the user, however, I was also going to allow for > additional options from the sysconfig file, but $OPTIONS wasn't being > expand either. sysconfig files for daemons kinda is obsolete these days either write the daemon to parse a co