On 2/24/12 12:10 PM, Ville Skyttä wrote:
On 2012-02-23 20:06, Jesse Keating wrote:
Could you help me figure out why path completion with ~/ isn't working
in fedpkg, but with full paths it is? I assume there is something wrong
in the (contributed) bash completion file.
On 02/21/2012 06:31 PM, Doug Ledford wrote:
it honors all the LSB dependency tags in the SysV init scripts, and
my experience is that this is specifically where a number of the
emulation startup bugs exists.
What do you mean? That the LSB headers are incorrect too often?
It's a problem, but
On 2/19/12 3:43 AM, Ville Skyttä wrote:
On 2012-02-18 20:26, Rahul Sundaram wrote:
On 02/18/2012 11:05 PM, Ville Skyttä wrote:
You can get the completion to work according to that preference with for
example yum install ./fooTAB - anything that looks like a filesystem
path triggers
- Original Message -
On 02/10/2012 06:32 PM, Adam Williamson wrote:
systemd was explicitly written to be 100% sysv-compatible
Mostly compatible, but not 100%.
http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
You're both joking, right? That isn't 100% compatible,
On Tue, 2012-02-21 at 12:31 -0500, Doug Ledford wrote:
- Original Message -
On 02/10/2012 06:32 PM, Adam Williamson wrote:
systemd was explicitly written to be 100% sysv-compatible
Mostly compatible, but not 100%.
On 2012-02-18 20:26, Rahul Sundaram wrote:
On 02/18/2012 11:05 PM, Ville Skyttä wrote:
You can get the completion to work according to that preference with for
example yum install ./fooTAB - anything that looks like a filesystem
path triggers filename-only completion, otherwise we do both
On 2012-02-16 05:34, Stephen John Smoogen wrote:
2) The bash-completions add-on. Which does all kinds of wonderful
things which when they work is really nice.. it will autocomplete
hostnames if you type ssh ftab, it will autocomplete depending on
the command you typed the most obvious
On Fri, 2012-02-17 at 16:23 +, John5342 wrote:
On Fri, Feb 17, 2012 at 13:54, Nils Philippsen n...@redhat.com wrote:
This disables normal non-programmable tab-completion for me.
Also, if you want the (other) default settings, you need to
$include /etc/inputrc on the first line of
On 02/18/2012 02:27 PM, Ville Skyttä wrote:
People tend to bring this up every now and then but fail to be specific
exactly what happened so it's quite difficult for anyone to fix things.
I just installed it for sometime and found that yum install footab
looks up the online repositories
On 2012-02-18 18:27, Rahul Sundaram wrote:
On 02/18/2012 02:27 PM, Ville Skyttä wrote:
People tend to bring this up every now and then but fail to be specific
exactly what happened so it's quite difficult for anyone to fix things.
I just installed it for sometime and found that yum
On 02/18/2012 11:05 PM, Ville Skyttä wrote:
You can get the completion to work according to that preference with for
example yum install ./fooTAB - anything that looks like a filesystem
path triggers filename-only completion, otherwise we do both filenames
and repos.
That's atleast
On Thu, 2012-02-16 at 17:49 +, Jóhann B. Guðmundsson wrote:
On 02/16/2012 05:33 PM, Jóhann B. Guðmundsson wrote:
complete -r if memory serves me correct then again I'm getting old and
fragile...
set disable-completion on into /etc/inputrc or ~/.inputr to disable it
across
On Fri, Feb 17, 2012 at 13:54, Nils Philippsen n...@redhat.com wrote:
This disables normal non-programmable tab-completion for me.
Also, if you want the (other) default settings, you need to
$include /etc/inputrc on the first line of ~/.inputrc. It would really
help if we shipped
Matthew Garrett wrote:
On Wed, Feb 15, 2012 at 07:23:24PM -0500, Steve Clark wrote:
On 02/15/2012 05:19 PM, mike cloaked wrote:
I use bash completion all the time every single day - I guess I have
become a corner case!
No you haven't. All the developers I have worked with since the
early
- Original Message -
From: Steve Clark scl...@netwolves.com
To: Development discussions related to Fedora
devel@lists.fedoraproject.org
Sent: Thursday, February 16, 2012 6:47:03 AM
Subject: Re: /usrmove? - about the future
On 02/15/2012 10:34 PM, Matthew Garrett wrote:
On Wed
On 02/16/2012 08:12 AM, Steve Gordon wrote:
- Original Message -
From: Steve Clarkscl...@netwolves.com
To: Development discussions related to Fedoradevel@lists.fedoraproject.org
Sent: Thursday, February 16, 2012 6:47:03 AM
Subject: Re: /usrmove? - about the future
On 02/15/2012 10:34
On Thu, Feb 16, 2012 at 03:34, Stephen John Smoogen smo...@gmail.com wrote:
A bad autocomplete can cause you to sit 3-4 minutes
as DNS or other things time out.
Ctrl+C will cancel the command and the completion with it. It's not
ideal if you are typing a long command but it certainly avoids
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2012 09:59 AM, John5342 wrote:
On Thu, Feb 16, 2012 at 03:34, Stephen John Smoogen
smo...@gmail.com wrote:
A bad autocomplete can cause you to sit 3-4 minutes as DNS or
other things time out.
Ctrl+C will cancel the command and the
On 02/16/2012 05:26 PM, Daniel J Walsh wrote:
Is there a way to disable this. Basically i don't want any bash
completion to use the network.
complete -r if memory serves me correct then again I'm getting old and
fragile...
JBG
--
devel mailing list
devel@lists.fedoraproject.org
On 02/16/2012 05:33 PM, Jóhann B. Guðmundsson wrote:
complete -r if memory serves me correct then again I'm getting old and
fragile...
set disable-completion on into /etc/inputrc or ~/.inputr to disable it
across logout/reboots
JBG
--
devel mailing list
devel@lists.fedoraproject.org
Am 14.02.2012 19:16, schrieb Jóhann B. Guðmundsson:
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the systemd maintainers ever read bug reports BTW?
Why do you think otherwise?
Not only read them but fix them as well.
To give you some stats
There are currently 96 Open bugs
On 02/15/2012 10:47 AM, Reindl Harald wrote:
Am 14.02.2012 19:16, schrieb Jóhann B. Guðmundsson:
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the systemd maintainers ever read bug reports BTW?
Why do you think otherwise?
Not only read them but fix them as well.
To give you some
Am 15.02.2012 10:53, schrieb Brendan Jones:
On 02/15/2012 10:47 AM, Reindl Harald wrote:
Am 14.02.2012 19:16, schrieb Jóhann B. Guðmundsson:
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the systemd maintainers ever read bug reports BTW?
Why do you think otherwise?
Not only read
On 02/15/2012 11:55 AM, Reindl Harald wrote:
Am 15.02.2012 10:53, schrieb Brendan Jones:
On 02/15/2012 10:47 AM, Reindl Harald wrote:
Am 14.02.2012 19:16, schrieb Jóhann B. Guðmundsson:
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the systemd maintainers ever read bug reports BTW?
On Mon, 2012-02-13 at 09:28 -0800, Adam Williamson wrote:
On Mon, 2012-02-13 at 14:47 +0100, Nils Philippsen wrote:
On Fri, 2012-02-10 at 11:08 -0800, Adam Williamson wrote:
Let me put it this way, then: Fedora is released on a six month cycle,
which is far faster than is usually
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
On 02/15/2012 11:55 AM, Reindl Harald wrote:
Am 15.02.2012 10:53, schrieb Brendan Jones:
On 02/15/2012 10:47 AM, Reindl Harald wrote:
Am 14.02.2012 19:16, schrieb Jóhann B. Guðmundsson:
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a shocking revelation to you but not everybody uses or
relies their world on bash autocompletion.
- Panu -
What world are you living in?
bash-completion is not a default package.
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a shocking revelation to you but not everybody uses or
relies their world on bash autocompletion.
- Panu -
What world are you living
Once upon a time, Rahul Sundaram methe...@gmail.com said:
bash-completion is not a default package.
Wrong since F16 - it is default in the Base group in comps.
--
Chris Adams cmad...@hiwaay.net
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself -
On 02/15/2012 10:40 PM, Reindl Harald wrote:
it is used by all professional users using mostly a terminal
it should not installed as deafult because desktop users do
not need it at all, but this does not change the fact that
systemd developers which i still call professional users
should
On 02/15/2012 10:48 PM, Chris Adams wrote:
Once upon a time, Rahul Sundaram methe...@gmail.com said:
bash-completion is not a default package.
Wrong since F16 - it is default in the Base group in comps.
Ah. didn't notice that. I haven't done a fresh installation since
Fedora 11 or so.
On Wed, Feb 15, 2012 at 11:19:18PM +0530, Rahul Sundaram wrote:
On 02/15/2012 10:48 PM, Chris Adams wrote:
Once upon a time, Rahul Sundaram methe...@gmail.com said:
bash-completion is not a default package.
Wrong since F16 - it is default in the Base group in comps.
Ah. didn't notice
Am 15.02.2012 18:40, schrieb Rahul Sundaram:
On 02/15/2012 10:40 PM, Reindl Harald wrote:
it is used by all professional users using mostly a terminal
it should not installed as deafult because desktop users do
not need it at all, but this does not change the fact that
systemd developers
Am 15.02.2012 18:53, schrieb Tomasz Torcz:
On Wed, Feb 15, 2012 at 11:19:18PM +0530, Rahul Sundaram wrote:
On 02/15/2012 10:48 PM, Chris Adams wrote:
Once upon a time, Rahul Sundaram methe...@gmail.com said:
bash-completion is not a default package.
Wrong since F16 - it is default in the
On 02/15/2012 07:10 PM, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a shocking revelation to you but not everybody uses or
relies their world on bash
On 02/16/2012 12:13 AM, Reindl Harald wrote:
i SURELY have made a notice in one of many
bug-reports belonging to systemd last year
I don't recall seeing it and I am cc'ed in all systemd bug reports and
also, individual bugs require individual bug reports. Not merely a note
in another bug
On Wed, Feb 15, 2012 at 07:45:41PM +0100, Reindl Harald wrote:
does not matter because bash is the default shell and
transitions have to be targeted for defaults and any
developer of core-components has to use system defaults
for his testings
I'm sorry, it's clear at this point that you have
On Wed, 2012-02-15 at 18:10 +0100, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a shocking revelation to you but not everybody uses or
relies their world on
On Wed, Feb 15, 2012 at 8:30 PM, Adam Williamson awill...@redhat.com wrote:
On Wed, 2012-02-15 at 18:10 +0100, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a
On 02/15/2012 05:19 PM, mike cloaked wrote:
On Wed, Feb 15, 2012 at 8:30 PM, Adam Williamsonawill...@redhat.com wrote:
On Wed, 2012-02-15 at 18:10 +0100, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu
On 15/02/12 01:30 PM, Adam Williamson wrote:
On Wed, 2012-02-15 at 18:10 +0100, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On 02/15/2012 05:06 PM, Steve Clark wrote:
On 02/15/2012 05:49 AM, Panu Matilainen wrote:
It might be a shocking revelation to you but not
On 02/16/2012 07:46 AM, Dariusz J. Garbowski wrote:
Right. And thanks to this thread I just learned what broke bash
completion for me after fresh install of F16: 'rpm -e bash-completion'
fixed bash for me :-)
As a quick note; you should probably use yum remove instead of rpm -e
because
On 15 February 2012 17:23, Steve Clark scl...@netwolves.com wrote:
On 02/15/2012 05:19 PM, mike cloaked wrote:
On Wed, Feb 15, 2012 at 8:30 PM, Adam Williamson awill...@redhat.com
wrote:
On Wed, 2012-02-15 at 18:10 +0100, Reindl Harald wrote:
Am 15.02.2012 17:59, schrieb Rahul Sundaram:
On Wed, Feb 15, 2012 at 07:23:24PM -0500, Steve Clark wrote:
On 02/15/2012 05:19 PM, mike cloaked wrote:
I use bash completion all the time every single day - I guess I have
become a corner case!
No you haven't. All the developers I have worked with since the early
nineties use it all the
https://bugzilla.redhat.com/show_bug.cgi?id=753339
... and reboot is still not working on Fedora 16 on several machines...
do the systemd maintainers ever read bug reports BTW?
++
| Alfredo Ferrari
https://bugzilla.redhat.com/show_bug.cgi?id=753339
... with clean install and on Fedora 16, two duifferent machines
++
| Alfredo Ferrari || Tel.: +41.22.767.6119 |
| C.E.R.N.
Alfredo Ferrari wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=753339
... and reboot is still not working on Fedora 16 on several
machines...
It's not obvious whether systemd is to blame for this bug.
do the systemd maintainers ever read bug reports BTW?
Of course. You have comments
On 02/14/2012 10:23 AM, Alfredo Ferrari wrote:
Do the systemd maintainers ever read bug reports BTW?
Why do you think otherwise?
Not only read them but fix them as well.
To give you some stats
There are currently 96 Open bugs against systemd and 536 that have been
closed at the time of
On 02/10/2012 07:12 PM, Jon Ciesla wrote:
Given all that, it seems only logical to conclude that Fedora really
_isn't_ primarily intended for use as a production server.
Bingo, which is why it's important for people like me who do it to
realize what they're getting into and take some
On Fri, 2012-02-10 at 11:08 -0800, Adam Williamson wrote:
Let me put it this way, then: Fedora is released on a six month cycle,
which is far faster than is usually considered desirable for server
usage. It has a 13 month lifetime, which is far shorter than is usually
considered desirable for
On Mon, 2012-02-13 at 14:47 +0100, Nils Philippsen wrote:
On Fri, 2012-02-10 at 11:08 -0800, Adam Williamson wrote:
Let me put it this way, then: Fedora is released on a six month cycle,
which is far faster than is usually considered desirable for server
usage. It has a 13 month lifetime,
Am 10.02.2012 12:59, schrieb Miloslav Trmač:
On Fri, Feb 10, 2012 at 12:42 PM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 10.02.2012 10:06, schrieb Jóhann B. Guðmundsson:
The state of overall migration to systemd is depended on each package
maintainer(s)
and at current rate that
On Fri, Feb 10, 2012 at 1:13 PM, Reindl Harald h.rei...@thelounge.net wrote:
[..]
POSSIBLE SOLUTION:
each second release does not introduzce those big changes and
only optimize existing things and bringing only new versions
of packages require a simple mass
Am 10.02.2012 15:09, schrieb drago01:
On Fri, Feb 10, 2012 at 1:13 PM, Reindl Harald h.rei...@thelounge.net wrote:
[..]
POSSIBLE SOLUTION:
each second release does not introduzce those big changes and
only optimize existing things and bringing only new
On Fri, Feb 10, 2012 at 01:13:13PM +0100, Reindl Harald wrote:
POSSIBLE SOLUTION:
each second release does not introduzce those big changes and
only optimize existing things and bringing only new versions
of packages require a simple mass rebuild for so-changes
you can call it F17, F17.5
Am 10.02.2012 16:06, schrieb Peter Hutterer:
On Fri, Feb 10, 2012 at 01:13:13PM +0100, Reindl Harald wrote:
POSSIBLE SOLUTION:
each second release does not introduzce those big changes and
only optimize existing things and bringing only new versions
of packages require a simple mass
- Original Message -
From: Reindl Harald h.rei...@thelounge.net
To: devel@lists.fedoraproject.org
Sent: Friday, February 10, 2012 10:43:07 AM
Subject: Re: /usrmove? - about the future
Am 10.02.2012 16:06, schrieb Peter Hutterer:
On Fri, Feb 10, 2012 at 01:13:13PM +0100
Am 10.02.2012 16:49, schrieb Steve Gordon:
- Original Message -
From: Reindl Harald h.rei...@thelounge.net
So the likely effect is that these features will be called ready
whenever
they need to be (according to the process) with the rest simply
called
optimizing.
if people do
On Fri, Feb 10, 2012 at 16:57:18 +0100,
Reindl Harald h.rei...@thelounge.net wrote:
so if the releases would be more well thought i would have
time to write such things, but then there would be no need for it
Consider running for FESCO this spring and emphasize your views on features in
On Fri, 2012-02-10 at 13:13 +0100, Reindl Harald wrote:
I quite agree this is (becoming?) a problem - but can you suggest a
workable solution?
calm down new features because you see now what happended
On a point of fact: what _is_ it that you are suggesting happened
exactly?
Everyone on
Am 10.02.2012 18:05, schrieb Adam Williamson:
On Fri, 2012-02-10 at 13:13 +0100, Reindl Harald wrote:
Everyone on this list is well aware of the fact that you consider
systemd a terrible failure because not every package in Fedora yet has
systemd-native init scripts, but by the same token,
On Fri, Feb 10, 2012 at 8:21 AM, Reindl Harald h.rei...@thelounge.net wrote:
F15 was the first Linux i saw where reboot did not
work until you typed kill 1 while praying!
Can you point me to a bug report from you or anyone else that has been
confirmed by at least one other person?
I personally
On Fri, 2012-02-10 at 18:21 +0100, Reindl Harald wrote:
Am 10.02.2012 18:05, schrieb Adam Williamson:
On Fri, 2012-02-10 at 13:13 +0100, Reindl Harald wrote:
Everyone on this list is well aware of the fact that you consider
systemd a terrible failure because not every package in Fedora
On Fri, Feb 10, 2012 at 04:57:18PM +0100, Reindl Harald wrote:
Am 10.02.2012 16:49, schrieb Steve Gordon:
- Original Message -
From: Reindl Harald h.rei...@thelounge.net
So the likely effect is that these features will be called ready
whenever
they need to be (according to
On Fri, 2012-02-10 at 08:28 -0900, Jef Spaleta wrote:
On Fri, Feb 10, 2012 at 8:21 AM, Reindl Harald h.rei...@thelounge.net wrote:
F15 was the first Linux i saw where reboot did not
work until you typed kill 1 while praying!
Can you point me to a bug report from you or anyone else that has
On Fri, Feb 10, 2012 at 08:28:28 -0900,
Jef Spaleta jspal...@gmail.com wrote:
I personally didn't experience that with the F15 systems I had. But
maybe I got lucked and dodged a bullet.
It seems pretty common that updating systemd causes problems with the next
shutdown. I don't know why and
On 02/10/2012 06:33 PM, Bruno Wolff III wrote:
It seems pretty common that updating systemd causes problems with the next
shutdown. I don't know why and it is a pain to reproduce since it doesn't
happen again on the next reboot.
Did you see the problem with updates within a stable Fedora
Am 10.02.2012 18:28, schrieb Jef Spaleta:
On Fri, Feb 10, 2012 at 8:21 AM, Reindl Harald h.rei...@thelounge.net wrote:
F15 was the first Linux i saw where reboot did not
work until you typed kill 1 while praying!
Can you point me to a bug report from you or anyone else that has been
On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams d...@redhat.com wrote:
In any case, badmouthing systemd for an upgrade bug where it actually
works fine *when you're really running F15* doesn't seem right. I
wouldn't have had this problem if it'd installed off the Live CD or done
a fresh
Am 10.02.2012 18:32, schrieb Adam Williamson:
On Fri, 2012-02-10 at 18:21 +0100, Reindl Harald wrote:
Am 10.02.2012 18:05, schrieb Adam Williamson:
On Fri, 2012-02-10 at 13:13 +0100, Reindl Harald wrote:
Everyone on this list is well aware of the fact that you consider
systemd a terrible
On Fri, Feb 10, 2012 at 8:41 AM, Reindl Harald h.rei...@thelounge.net wrote:
no i can not because it is a one-shot thing to do yum distro-sync and so i
had no time for a bugrport while other more important things like mysqld were
horrible broken
Let me strongly suggest, that unfiled problems
On Fri, Feb 10, 2012 at 11:42 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams d...@redhat.com wrote:
In any case, badmouthing systemd for an upgrade bug where it actually
works fine *when you're really running F15* doesn't seem right. I
wouldn't have
On 02/10/2012 11:11 PM, Reindl Harald wrote:
no i can not because it is a one-shot thing to do yum distro-sync and so i
had no time for a bugrport while other more important things like mysqld were
horrible broken
Considering the number of mails in this list where you have repeated the
On Fri, Feb 10, 2012 at 8:49 AM, Jon Ciesla limburg...@gmail.com wrote:
I've been yum upgrading since FC1. I didn't see that. I was also
running a mysql server.
Maybe you should file a bug report noting that yum upgrade worked for
you. I personally think that is a bug. unsupported workflows
On 02/10/2012 06:32 PM, Adam Williamson wrote:
systemd was explicitly written to be 100% sysv-compatible
Mostly compatible, but not 100%.
http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
Michal
--
devel mailing list
devel@lists.fedoraproject.org
Am 10.02.2012 18:49, schrieb Jef Spaleta:
On Fri, Feb 10, 2012 at 8:41 AM, Reindl Harald h.rei...@thelounge.net wrote:
no i can not because it is a one-shot thing to do yum distro-sync and so i
had no time for a bugrport while other more important things like mysqld were
horrible broken
Am 10.02.2012 18:49, schrieb Jon Ciesla:
On Fri, Feb 10, 2012 at 11:42 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams d...@redhat.com wrote:
In any case, badmouthing systemd for an upgrade bug where it actually
works fine *when you're really running
On Fri, Feb 10, 2012 at 11:52 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Feb 10, 2012 at 8:49 AM, Jon Ciesla limburg...@gmail.com wrote:
I've been yum upgrading since FC1. I didn't see that. I was also
running a mysql server.
Maybe you should file a bug report noting that yum upgrade
Am 10.02.2012 18:49, schrieb Rahul Sundaram:
On 02/10/2012 11:11 PM, Reindl Harald wrote:
no i can not because it is a one-shot thing to do yum distro-sync and so i
had no time for a bugrport while other more important things like mysqld were
horrible broken
Considering the number of
Am 10.02.2012 18:52, schrieb Jef Spaleta:
On Fri, Feb 10, 2012 at 8:49 AM, Jon Ciesla limburg...@gmail.com wrote:
I've been yum upgrading since FC1. I didn't see that. I was also
running a mysql server.
Maybe you should file a bug report noting that yum upgrade worked for
you. I
On Fri, Feb 10, 2012 at 8:56 AM, Jon Ciesla limburg...@gmail.com wrote:
Dammit. I knew I was doing something wrong. I'd better set those
machines on fire.
youtube video or it didnt happen.
-jef
--
devel mailing list
devel@lists.fedoraproject.org
On Fri, 2012-02-10 at 18:39 +0100, Michal Schmidt wrote:
On 02/10/2012 06:33 PM, Bruno Wolff III wrote:
It seems pretty common that updating systemd causes problems with the next
shutdown. I don't know why and it is a pain to reproduce since it doesn't
happen again on the next reboot.
On 02/10/2012 11:27 PM, Reindl Harald wrote:
jesus christ we are talking about the future and what did go wrong
in the past - why should anybody file a bugrpeort for yum-upgrade
from F14 to F15 this time where F14 is EOL and you become as answer
yum upgrade is not supported (due dumb pilicies
On 02/10/2012 06:55 PM, Reindl Harald wrote:
mysqld in F15 worked only on baby-systems where nothing
other relies on mysqld but not on machines having tons
of services rely in a init-process who fires them up
after mysqld id reday for connections
I am aware of this mysqld-related bugreport of
On Fri, 2012-02-10 at 08:42 -0900, Jef Spaleta wrote:
I noticed it wasn't list as a common gotcha on the F15 commons bug
page that is maintained to handle these sorts of quibbles. Do we allow
for recognition of the not supported upgrade dance in the common
bugs information as a policy
Yes.
On Fri, Feb 10, 2012 at 11:55 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 10.02.2012 18:49, schrieb Jon Ciesla:
On Fri, Feb 10, 2012 at 11:42 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams d...@redhat.com wrote:
In any case, badmouthing systemd
On 02/10/2012 07:00 PM, Adam Williamson wrote:
The one-time case - 'the first time you go from systemd X to systemd Y,
the system won't shut down cleanly' - does seem to affect stable release
upgrades, yeah.
If anyone knows the values of X and Y where it's reproducible, please
let us know.
On Fri, Feb 10, 2012 at 11:59 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Feb 10, 2012 at 8:56 AM, Jon Ciesla limburg...@gmail.com wrote:
Dammit. I knew I was doing something wrong. I'd better set those
machines on fire.
youtube video or it didnt happen.
No video camera. But I have
On Fri, 2012-02-10 at 18:54 +0100, Reindl Harald wrote:
Am 10.02.2012 18:49, schrieb Jef Spaleta:
On Fri, Feb 10, 2012 at 8:41 AM, Reindl Harald h.rei...@thelounge.net
wrote:
no i can not because it is a one-shot thing to do yum distro-sync and so
i
had no time for a bugrport while
On Fri, Feb 10, 2012 at 08:42:08AM -0900, Jef Spaleta wrote:
On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams d...@redhat.com wrote:
In any case, badmouthing systemd for an upgrade bug where it actually
works fine *when you're really running F15* doesn't seem right. I
wouldn't have had this
Am 10.02.2012 19:00, schrieb Rahul Sundaram:
On 02/10/2012 11:27 PM, Reindl Harald wrote:
I suggest you change your tone if you want your points to be heard. If
you can't be polite, please stop posting till you can. My point is
that, you continue to bring up past issues but you have not
On Fri, 2012-02-10 at 19:02 +0100, Michal Schmidt wrote:
On 02/10/2012 07:00 PM, Adam Williamson wrote:
The one-time case - 'the first time you go from systemd X to systemd Y,
the system won't shut down cleanly' - does seem to affect stable release
upgrades, yeah.
If anyone knows the
On Fri, Feb 10, 2012 at 9:07 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-02-10 at 19:02 +0100, Michal Schmidt wrote:
On 02/10/2012 07:00 PM, Adam Williamson wrote:
The one-time case - 'the first time you go from systemd X to systemd Y,
the system won't shut down cleanly' -
Am 10.02.2012 19:01, schrieb Michal Schmidt:
On 02/10/2012 06:55 PM, Reindl Harald wrote:
mysqld in F15 worked only on baby-systems where nothing
other relies on mysqld but not on machines having tons
of services rely in a init-process who fires them up
after mysqld id reday for connections
On 02/10/2012 11:37 PM, Reindl Harald wrote:
and you think my tone is the problem?
Yes, I think your tone is a severe problem that needs to be corrected if
you want to anyone to take your points seriously. There are several
problems which you continue to talk about where you haven't filed a
Am 10.02.2012 19:15, schrieb Jef Spaleta:
On Fri, Feb 10, 2012 at 9:07 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-02-10 at 19:02 +0100, Michal Schmidt wrote:
On 02/10/2012 07:00 PM, Adam Williamson wrote:
The one-time case - 'the first time you go from systemd X to systemd
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
i have rpeorted A TON of bugs where services was not converted to systemd
many of them are also not converted until now
Are you doing this because there is a functionality problem? Systemd is
explicitly (mostly) backwards compatible
On 02/10/2012 05:57 PM, Reindl Harald wrote:
yum upgrade is not supported (due dumb pilicies away from real life)
With my QA hat on I can say with confidence that this will never be
officially supported.
There is no way in hell that QA can test every possible upgrade path
with every
Am 10.02.2012 19:18, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
i have rpeorted A TON of bugs where services was not converted to systemd
many of them are also not converted until now
Are you doing this because there is a functionality problem?
On 02/10/2012 10:05 AM, Adam Williamson wrote:
You're not supposed to be running Fedora on production servers. That is
not what it's for.
Sez who?
http://fedoraproject.org/wiki/SIGs/Server
-Scott
--
devel mailing list
devel@lists.fedoraproject.org
1 - 100 of 122 matches
Mail list logo
