t; Subject: [HEADS UP] dracut-live subpackage
>
> dracut now has a new subpackage "dracut-live" which is needed to boot live
> images with dmsquash.
>
> Please add this package to your dependencies.
>
Thanks for the advance notice. Where is this planned to land? W
sn't seem very usable to me. I didn't file a bug on BZ because
I wasn't sure where exactly one does that.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
e was "hidden" because I suspect many a
mirror exclude all hidden files for the reason I had done so, namely to avoid
pulling an upstream mirror's temporary files.)
Anyway, we checked a few upstream mirrors (e.g., kernel.org) and the file isn't
there. Did something happen at the
omething happen at the top?
It's still there as far as I can see.
http://mirrors.kernel.org/fedora/releases/20/Fedora/x86_64/os/.treeinfo
Sorry folks, there was a miscomm on our end. It was .treeinfo.signed he was
missing and that was excluded by our mirroring script.
--
John
olve the issue via my
rpm directly. I've not been successful in finding any guidelines in how to
best approach that task. Do I package a bit of SEL policy or is there a way to
have my script run with the puppet_var_lib_t context?
--
John Florian
--
devel mailing list
devel@lists.fedorapro
resolve the issue via my
rpm directly. I’ve not been successful in finding any guidelines in how to
best approach that task. Do I package a bit of SEL policy or is there a way to
have my script run with the puppet_var_lib_t context?
--
John Florian
Then you should add a custom policy
Perfect! Thanks Christopher.
--
John Florian
-Original Message-
From: devel-boun...@lists.fedoraproject.org
[mailto:devel-boun...@lists.fedoraproject.org] On Behalf Of Christopher Meng
Sent: Wednesday, July 23, 2014 09:12
To: Development discussions related to Fedora
Subject: Re
h foo-server + foo-client.
Whatever you do, please do so between Fedora releases so that those of us who
use things like puppet can have a simple condition on the OS release number.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ers a lot to me since my spin is
relatively use-case agnostic; it's an generic Appliance OS and puppet makes
each node into something specific at run-time though always starting from a
common image.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproje
will *definitely* have us kicking
> ourselves in 6 months. And shipping 1.7 by default will make lots of Django
> users/devs happy.
>
> Definitely bring it up to FESCo, but it's probably riskier to be shipping
> something that will become unsupported within the release lifetime
cal,
but we use Fedora almost exclusively.)
[1] https://docs.puppetlabs.com/puppet/4.0/reference/release_notes.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1068867
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Thu, 2015-06-04 at 23:21 +0200, Haïkel wrote:
> 2015-06-04 20:21 GMT+02:00 John Florian :
> > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but
> > haven’t heard even a peep on the subject. As described[1], they’ve moved to
> > an all-in-one p
On Thu, 2015-06-04 at 20:17 -0700, Michael Stahnke wrote:
>
>
> On Thu, Jun 4, 2015 at 2:21 PM, Haïkel
> wrote:
> 2015-06-04 20:21 GMT+02:00 John Florian
> :
> > I’ve been curious how Fedora plans to tackle inclusion of
> Puppet 4, bu
On Fri, 2015-06-05 at 01:12 -0400, Nico Kadel-Garcia wrote:
> On Thu, Jun 4, 2015 at 2:21 PM, John Florian wrote:
> > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but
> > haven’t heard even a peep on the subject. As described[1], they’ve moved to
&g
rking on this.)
>
> Oh, and not to forget:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Limited_usage_of_.2Fopt.2C_.2Fetc.2Fopt.2C_and_.2Fvar.2Fopt
>
> --
> Matthew Miller
>
> Fedora Project Leader
Thanks for that info. I've always referenced
http://www.pathname.com/fhs
On 2020-07-14 13:42, Sergio Belkin wrote:
> What is the better option to to get tiled windows in Plasma?
>
> I've tried a few kwin scripts with no luck, for example:
>
> - Grid-Tiling
> - Krohnkite
> - Tiling Extension
>
> The best I've tried so far is the last one, but can be too unstable...
>
> W
se, the few hassles I encounter are so much less time demanding
than all the window management I manually did before adopting
kwin-tiling. If I could only have "focus follows eyes", I'd be quite
happy in the WM serving me rather than the other way around. :-)
John Florian
On 2020-07-16 13:59, Sergio Belkin wrote:
>
>
> El jue., 16 jul. 2020 a las 12:22, John Florian
> (mailto:jflor...@doubledog.org>>) escribió:
>
> In any case, the few hassles I encounter are so much less time
> demanding
> than all the window management
t I've used for over a decade to
un-highlight a search. That no longer works in vim or gvim. Until I'd
found that I figured something in konsole had changed. But once gvim
revealed weird issues I figured it must be more of a vim thing. Now
seeing this message, I'm becoming even m
lack of gneovim or whatever it'd be called. There
was MUCH to be liked however, I remember that much.
John Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
ants to
maintain company-private packages based on django, this affords more
flexibility. I realize it may always mean more packaging work to keep
several python-djangoXYs in the distro, but it makes for a less rigid
coupling between the OS and what framework version you need to use.
--
John
sensible, yet it does lead the "jump when we say jump" syndrome. Still,
I'd rather deal with the upgrade conflict you mention than to be pinned to
an older Fedora release. It's always a fragile balancing act choosing
between what needs to be new and what cannot yet
some tests. If he can make this work, that would
> > make our lives a lot easier. More to come, stay tuned...
> >
> >
>
> Ok, so it turns out that Python Eggs are a lot smarter than I gave
> them credit for. If you turn your attention to
> http://fedoraproj
e home. (I
did learn accidentally with btrfs I can just ignore it and I've not lost
any space on /.)
So yes, simplicity is good, unless it makes everything else harder later.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
the
host I want/need LVM because in the physical world, LVM makes life way
more easier. Yeah, I can live with it in all cases, but then I'm just as
likely to do a complete reinstall of the VM as to resize the undersized
file system. However, that's only practical because puppet is doin
wedge so much capability and effort into a narrow
> installer-only use case? Bootable raid6 and raid4??
>
I actually like that idea of decoupling them. It would be good to see
more of the *nix tradition here, do ONE thing and do it very well. Of
course we'd need th
thias
> --
> Matthias Runge
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
I'd like to see 1.6 for F20. That would let me r
le -- as reversing the
Python 3 is really undesirable at this point -- is there any reason Fedora
couldn't have two mod_wsgi packages (one for Python2 and another for
Python3)?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/lis
to Jakub Dorňák (#1035876) - I guess
> we could backport to f20 without any problems.
That would be extremely helpful here, especially given that f21 is still a
ways off.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Okay, count me in. Is there a BZ already in place for reporting issues or
should such reports
t has happened through the use of some mirror probing.
Such a 3rd message should be carefully worded to indicate that the package has
started reaching *some* mirrors and that most should have it within another day.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
http://lis
Ditto! That seems like a much simpler solution overall.
--
John Florian
> -Original Message-
> From: Petr Spacek [mailto:pspa...@redhat.com]
> Sent: Friday, December 11, 2015 03:48
> To: devel@lists.fedoraproject.org
> Subject: Re: Bodhi front page after login
>
>
sing that kernel and
report back my findings.
Anyway, I was happy just to see it boot and appear mostly operational,
especially since I was unable to do the same using F17 to build a F17 Live
spin of the same sort.
Great job so far everyone!
--
John Florian
--
devel mailing list
devel@lists.fed
te
> and report on it there?" which I REALLY don't want to do. The updates
> are a manual process, so it's already another step someone in
> Infrastructure has to do when there is an outage.
>
> Lets keep it to sites that Fedora Infrastructure directly manages.
>
27;s status being out of sync a great deal more than services we
> monitor and manage. ;)
I'm not suggesting you monitor it at all, merely to have this page state
that you don't.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t;
Exactly! Great examples BTW and I really like the order they're presented
in, starting with those everyone is likely to ask about first down to
those that some will wonder about.
--
John Florian--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> From: Kevin Fenzi
> I'd prefer to avoid a list... how about:
>
> "This site provides status only for services managed directly by Fedora
> Infrastructure"
That's short and simple and drives the point home clear enough, I think.
--
John F
epressed.
FWIW, I enabled tap-to-click -- did I just answer my own question? --
simply because my wife and I both found the mouse to be moving off target
too often when tried using these "buttons".
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
F18 Release == Gold
>
> ?
>
> My EUR 0.02, I don't really care that much about the color of the
> bikeshed but this suggestion was the most interesting to me ;-)
>
> --Stijn
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
That's the simplest, easiest to understand (without referencing a wiki for
definitions) option I've seen proposed yet.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
>
> Regards,
> Florian
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
Any ideas on the equivalent for KDM?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
gt;
> Nicola
Oh! Thanks for that info. Indeed we're running F17 on it (Samsung 5
series IIRC) without any issues at all. Fedora may work great on it, but
this old dog isn't adapting so well to the new tricks of these
touchy-clicky things. Oh well, praise be the new days where it a
ound yet --
this will save me much time. Thanks!
> I have been doing this for several years with my laptops
I'm relatively new to owning a laptop. Used them for years at work but
those were bungled with Windoze. Win7 lived all of about 5m on my Samsung
before something worthwhile (F17) was installed after which it immediately
soared in value by a factor of nearly infinity. :-)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
cks
ever. (Oh and while I'm dreaming, might as well magically change all UI
labels and documentation for mouse buttons to be 1st, 2nd, 3rd, etc.
instead of "left", "right", "middle".) I've been adapting all my life, so
I won't be
installer is the one and only place where
emulating a Fruity computer's single-button mouse makes sense. Since we
can't reduce the number of physical buttons, I propose we reduce the
logical number to just one.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
pond to the name John with one group of people, but Michael
to everyone else ... it might not be that bad if nobody else shared those
names.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
n by default.
> (I hereby include my permanent disclaimer that I'm just the idiot
> monkey, and any time someone who's not an idiot monkey comes along and
> contradicts me, you can confidently assume I'm wrong...so if ajax or
> whot or someone shows up and says I'm
File a RFE against Anaconda
>
> Done:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=858843
Awesome! Thanks for handling that. I'd been meaning to get to it myself,
but am playing firefighter at work today.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
and click-through help text of BZ's Component field
could better explain this. It might also be good to note how easy it is
to grock the src.rpm name from a "suspect" file using rpm -qif
/some/suspect/filename.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.o
gainst-attacks-1671165.html
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to boot,
login and install more atop of that, but only as needed. Anything beyond
this is some "use case", but minimal is minimal.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
as a minimal
install
> > and grow "just enough" to fit their role. I take "minimal" quite
> > literally in that I believe it should be the absolute minimum to boot,
> > login and install more atop of that, but only as needed. Anything
beyond
> > this
ed you with a dialog with the
title
> "Components to install". (I believe this even *predates anaconda*.)
>
> This is the list of those components. The "comps file".
Oh yes, of course! I remember the days ... having started with RHL 4.0.
Some acronyms are just more obvio
size: 401 M
Bill, thanks for that excellent report! It shows me that even if you
strip away some of the "conveniences", you really don't save that much
over our normal "minimal" install. Very enlightening.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ary. Seems like -a should be automatic if a pipe is
involved.
# rpm -qf $(which journalctl)
systemd-194-1.fc18.i686
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
see nothing wrong with an implied pager. I think git has nailed the
perfect combo where it allows configs of "always", "never" and "auto"
(turns off paging, color, etc. for non-tty stdout).
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
#x27;ve had a
difficult time keeping my puppet resources in shape for each Fedora
release -- six months goes by all to fast when you have many other
responsibilities -- puppet was supposed to reduce my workload, right?
Right??? If 3.0 lands in F17, that's going to hurt my plans. At the same
time, puppet in F17 "as is" is plagued with problems as already mentioned.
Argh! "Hogtied" is a very apt description.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
s a simple unavoidable fact that some systems just cannot stay as
current as they ideally should and the dependencies may run very deep and
well beyond the realm of software packages and OSes alone.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
greatly appreciate hearing of their
experiences. I don't relish the idea of making the conversion, but I
really do get the impression life would be simpler with ansible once
there. Or am I just falling for that greener grass on the other side of
the fence?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
darned
good at catching all sorts of things prior to run-time. My python code
has improved in reliability significantly thanks to PyCharm. I've never
been much of an IDE person in the past, but this tool has convinced me
that they do have their uses. I focus far more on the goal now.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
n F17, that's going to hurt my plans. At the same time, puppet in
F17 "as
> > is" is plagued with problems as already mentioned.
> >
> > Argh! "Hogtied" is a very apt description.
>
> I'm sorry if your Puppet experience isn't completely awesome. Posting
> on the Puppet users list might be more appropriate.
Been there, done that since v0.24. If I'd jumped in with 3.0, my opinions
might be different. I believe something like puppet is sorely needed and
it solves big problems, but it's been a very bumpy ride when what was once
"best practice" is now deprecated.
> In this case I am looking for packaging options/opinions on Puppet
> with regards to Fedora and EPEL.
See my next to last paragraph beginning, "As for what should be done with
Fedora and RHEL ...". Consider the rest as context.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
s a very nice compromise between (1) you should see this
and (2) not being annoying about it. I would personally like to see the
puppet folks adopt something like this as an ongoing policy for all
deprecations/obsoletions with as much as advance notice as reasonably
possible.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
gt; to support a lts release of Fedora instead since it does not take more
> then a missing sysadmin or rhel business decision to more or less render
> those community incapacitated
+1
This is exactly why I've never adopted one of them. Like the concept, but
fear such situat
u can install it after your DB has gone poopsies.
>
I've seen that happen as well. I found this by hitting the pause button
on the guest IIRC. I just always use NTP to avoid the worry, but I agree
NTP (whether ntpd or chronyd) belongs in @standard not @core.
--
John Florian
--
rr from the
cron jobs just go to the syslog, but this may be systemd's journal magic
that I've been seeing.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
)
I don't believe embedded is out of focus for Fedora, I already have
several hundred such systems, soon likely to scale into the thousands. It
works quite well for this and I don't see any reason @core can't work to
their benefit as well.
--
John Florian
--
devel mai
d in those builds. Last
time I checked, it did not appear to be so maybe this whole @core thing
really is irrelevant to me.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t I see nothing but benefit in not
having to add "| less" routinely to things that are UI in nature. These
auto-pagers get out of the way immediately if you need a pipeline, so
what's the harm? In fact, you can still "journalctl | less" or the l
#x27;m not fond of the truncation method either, but I do appreciate knowing
that I'm not seeing the whole line, nor do I much care for wrapped lines
with semi-structured output. So until my pager grows a throbbing
indicator per line to hint there's more I find it a reasonable approach.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
keep
the
> useful ones and throw away the useless ones.
I used to do something like this with vim ":g/NOISE/d" until I could see
the detail I wanted when the alternations for grep would have been
tremendously long. With journalctl's built-in filtering capabilities I'm
IT. I realize if all the fields were
thusly accessible it would result in option bloat quickly, but I'd think
filtering on _COMM is quite routine -- it is for me at least.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
x27;d
think
> > filtering on _COMM is quite routine -- it is for me at least.
>
> You can provide binary path (_EXE=) by ”journalctl /usr/sbin/sshd”.
Yes, but that's of little help with applications using interpreted
languages (e.g., python). I want to match on the name of
> From: scl...@netwolves.com
> This seems like such a specious argument. Maybe it made sense when
> we were talking about disk drives
> that were megabytes in size, but now we have 500 gigabyte drives
> usually as a minimum.
You don't ever work with embedded systems, do y
g., python). I want to match on the name of the python
> > program, not python itself.
>
> journalctl _COMM= works for me on F19.
>
As it does for me, but somewhere it got clipped that what I was
asking/wishing for was a convenient -C option (like ps) to do just this,
; The output is still authoritative, but you get more than just messages
> originating from the unit.
I just *knew* I was going to be corrected on that. Thanks for the
explanation though.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
. But maybe it would be better to make
> 'journalctl /path/to/program' smarter, so that it would look at _COMM
when
> program is not an executable. This way things would work automagically.
That would be suitable too, if not more so. Also, for whatever reason,
I&#x
#x27;t see
that happen and feel no right in complaining without a BZ, so here we go
:-)
https://bugzilla.redhat.com/show_bug.cgi?id=985548 [RFE: improve
journalctl filtering by _COMM]
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> From: zbys...@in.waw.pl
> It only does an extra stat on the file do termine its kind, and then
> adds "_EXE=..." match. There shouldn't be any speed difference.
Hmmm... I cannot reproduce it now. It must have been something else.
Please disregard and my apologies
s way if the specified server exists and responds correctly, and
> 'return false' if it doesn't. For now it is using ntpdate; I suppose we
> could switch it to ntpd, but it would make an awful lot more sense if
> chronyd could do this.
I'm on the chrony mailing list if the
o test for remote
> ntp connectivity.
I think you want to work with:
chronyc tracking
Also, this might be useful too:
chronyc waitsync
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
l extra info conveyed via color)
that it's hard to grumble about much else. :-)
I may have avoided these largely because I knew it would take time to
learn the various names. But now I know I can "journalctl _ "
and have an instant refresher. Thanks for such a well-done tool.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
n?
I'd always choose the former, regardless of the case or how convenient it
was to me.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
do. After all "import this"
says:
Explicit is better than implicit.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
have to fix up
a bunch shebang lines and learn that I need to get going on my migration
pronto than the alternative of finding one day that python2 is just gone
where one is left with either a hurried port or downloading python2 from
external sources.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
et the very blunt "head's up" and be explicit too? I have no idea when
py2 will truly go away, but I'm convinced it will eventually and I'd like
to create my works in the best possible fashion. Thus far I've relied on
the implicit py->py2 and explicit py3 invocations as that's the way I've
seen Fedora set examples, but I think this should really be more detailed
in the packaging guidelines.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Only if you want to drop VESA support.
Please don't drop that. I have a large install base of SBCs using geode
and some on savage and s3virge IIRC. I need at least the VESA fallback,
although I suspect that may not suffice in some cases.
--
John Florian
--
devel mailing list
devel@lis
cent Fedora
> releases, feel free to write me.
I would like to hear what you've worked out. We had it going back as late
as F15-16ish IIRC, but it got increasingly difficult and I lost interest,
settling for an RDP session to a Windows client.
--
John Florian
--
devel mai
Thanks Simone!
--
John Florian
From: Simone Caronni
To: Development discussions related to Fedora
Date: 03/28/2013 10:43
Subject:Re: Orphaned meanwhile package
Sent by:devel-boun...@lists.fedoraproject.org
Hello,
I'm replying here as the question was posed
ld only be used if the DB size
exceeded some threshold.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
that too. I sure hope we didn't add the efficient
method on top of the inefficient method, rather than replace it.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> From: les
>Maybe I'm wrong, but given that I won't likely be around by the time
> these newer languages have become senior, I won't see my statement
> refuted.
You needn't wait long. Ada has been around for three some decades
already. ;-)
--
John Flor
7;s the point of reviving it? Sometimes, if you don't get your
> $0.02 posted in time, it's best to just sit on it.
Agreed.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
las that Kevin proposed are the ideal replacement
for spins.
https://fedoraproject.org/wiki/Fedora_formulas
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ive spin with stateless Linux
features enabled, plus puppet (considering switching to ansible), plus a
little glue to make custom appliances where networked resources dictate
the various roles those appliances play ranging from kiosks to firewalls.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ra Project
URL : http://git.fedorahosted.org/git/livecd
Summary : Python modules for building system images
Description :
Python modules that can be used for building images for things
like live image or appliances.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
mmy account to proceed past some mandatory setup is
irritating. I've raised this concern once before already. I don't mind
hitting a skip button -- I certainly don't want to make it hard for others
to set up their accounts manually if that's their cup o' tea.
--
John Flo
tarballs
just to feed rpmbuild. It always seems such a huge waste of time,
especially for very large packages.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
sed and tarballed again.
I'd like to see it behave more the way I expected it to when I naively
first started rolling my own packages. Specifically, it would be nice if
the %Source URI was processed intelligently to automatically retrieve the
content via HTTP, FTP, GIT, FILE or whatever (within reason) happens to be
specified there.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t an in-place upgrade just
like that. (This is unbelievably useful if you have hundreds or more of
nodes running such images in an embedded hardware.) Yeah, I forced a
round peg into a very square hole, but it works beautifully. I'm both
embarrassed and proud! :-)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
accessing is not my
workstation, then it's almost always ssh (in an xterm).
Given all this, it shouldn't be hard to imagine I'd prefer the proposed change
but I have no qualms in changing the default to suit my purposes -- I've been a
deviant ever since RHL switched bash fr
s this ok [y/N]: n
Operation aborted.
Why would that be?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
1 - 100 of 236 matches
Mail list logo
