On Tue, 2013-12-17 at 21:47 -0800, Adam Williamson wrote:
> On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote:
> > I have a tendency to upgrade to a new Fedora release as soon as it's
> > final, and I sometimes upgrade even sooner. ISTM that the official
> > upgrade process is almost alwa
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2013-12-18 18:00 UTC'
Links to all tickets belo
On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote:
> I have a tendency to upgrade to a new Fedora release as soon as it's
> final, and I sometimes upgrade even sooner. ISTM that the official
> upgrade process is almost always broken, often for known reasons.
> Should one of the criteria f
On 12/17/2013 07:55 AM, Stephen Herr wrote:
On 12/16/2013 03:48 PM, Orion Poplawski wrote:
On 12/16/2013 12:22 PM, Stephen Herr wrote:
On 12/13/2013 03:19 PM, Orion Poplawski wrote:
On 12/13/2013 12:49 PM, Stephen Herr wrote:
Hi everyone, I'm Stephen Herr (sherr).
I noticed that the koan pac
On Tue, Dec 17, 2013 at 6:47 PM, Michael Catanzaro wrote:
> On Tue, 2013-12-17 at 18:33 -0800, Andrew Lutomirski wrote:
>> I don't think Fedora is doing its users any favors by declaring F20 to
>> be released when upgrading from F19 using 'fedup --source network 20'
>> is known to be broken. The
On Dec 17, 2013, at 5:40 PM, Kevin Kofler wrote:
> Miloslav Trmač wrote:
>> a) Do we all agree that we need to solve this?
>
> No.
>
> We should not compromise our design principles (and, e.g., endorse an
> abominable hack like SCLs) just to allow obsolete applications to run on
> current ve
On Tue, 2013-12-17 at 18:33 -0800, Andrew Lutomirski wrote:
> I don't think Fedora is doing its users any favors by declaring F20 to
> be released when upgrading from F19 using 'fedup --source network 20'
> is known to be broken. The bleeding-edge types can already upgrade to
> the beta.
I'm atte
On Tue, Dec 17, 2013 at 4:52 PM, Emmanuel Seyman wrote:
> * Andrew Lutomirski [17/12/2013 15:22] :
>>
>> I propose changing that to something like "Install fedup. The version
>> of fedup used must be the most recent stable release.)
>
> Given that you yourself report that the most recent stable r
Swap with https://bugzilla.redhat.com/show_bug.cgi?id=1033433 if you like.
I need to handle these remaining bugs now.
Thanks.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduc
* Andrew Lutomirski [17/12/2013 15:22] :
>
> I propose changing that to something like "Install fedup. The version
> of fedup used must be the most recent stable release.)
Given that you yourself report that the most recent stable release of fedup
does not work, I'm not sure why you would want t
Andrew Lutomirski wrote:
> I have a tendency to upgrade to a new Fedora release as soon as it's
> final, and I sometimes upgrade even sooner.
[snip]
> ends up downloading all rpms *twice* a sucking up a correspondingly
> immense amount of disk space.
That's the punishment for your impatience. :-p
Miloslav Trmač wrote:
> a) Do we all agree that we need to solve this?
No.
We should not compromise our design principles (and, e.g., endorse an
abominable hack like SCLs) just to allow obsolete applications to run on
current versions of Fedora or the other way round. Current applications need
On þri 17.des 2013 22:24, Miloslav Trmač wrote:
Hello,
Looking at the current WG outputs, it seems that nobody is taking on
the problem of stable application runtimes:
Probably because no maintainer has been asked for how long release cycle
they considered they could/would maintain their comp
On Tue, 2013-12-17 at 15:27 -0800, Andrew Lutomirski wrote:
> there are
> lots of libraries where, for example, .so.6 would be a perfectly fine
> replacement for .so.7, but the system doesn't know that.
I think the authors of these libraries screwed up. Namely, libudev and
libffi were both mista
On Tue, Dec 17, 2013 at 3:19 PM, Colin Walters wrote:
> Hi Andrew,
>
> On Tue, 2013-12-17 at 15:05 -0800, Andrew Lutomirski wrote:
>
>> There will be a similar problem in the docker images, unless you're
>> suggesting that everyone use Ubuntu-in-docker-on-Fedora/RHEL.
>
> True, but it becomes the
On Tue, Dec 17, 2013 at 3:41 AM, Lukas Zapletal wrote:
> On Mon, Dec 16, 2013 at 03:10:08AM -0700, T.C. Hollingsworth wrote:
>> > I do commit locally
>> > although I probably don't want push the snapshot sources, because I update
>> > them later, when time comes.
>
> +1
The more I think about thi
On Tue, Dec 17, 2013 at 3:16 PM, Andrew Lutomirski wrote:
> I have a tendency to upgrade to a new Fedora release as soon as it's
> final, and I sometimes upgrade even sooner. ISTM that the official
> upgrade process is almost always broken, often for known reasons.
> Should one of the criteria fo
Hi Andrew,
On Tue, 2013-12-17 at 15:05 -0800, Andrew Lutomirski wrote:
> There will be a similar problem in the docker images, unless you're
> suggesting that everyone use Ubuntu-in-docker-on-Fedora/RHEL.
True, but it becomes the responsibility of the container creator, not
"Fedora".
Anyways, I
I have a tendency to upgrade to a new Fedora release as soon as it's
final, and I sometimes upgrade even sooner. ISTM that the official
upgrade process is almost always broken, often for known reasons.
Should one of the criteria for releasing Fedora N+1 be that a
fully-updated Fedora N must be abl
On Tue, Dec 17, 2013 at 3:01 PM, Colin Walters wrote:
> On Tue, 2013-12-17 at 23:24 +0100, Miloslav Trmač wrote:
>
>> b) Which WG will take on the task of solving this? We shouldn't end
>> up with everybody agreeing that this needs to be solved, but no PRD
>> proposing to solve this. Is it the B
On Tue, 2013-12-17 at 23:24 +0100, Miloslav Trmač wrote:
> b) Which WG will take on the task of solving this? We shouldn't end
> up with everybody agreeing that this needs to be solved, but no PRD
> proposing to solve this. Is it the Base WG or the Env and Stacks WG?
> Or is it up to Server and
Hello, I have this review
https://bugzilla.redhat.com/show_bug.cgi?id=1014738
and I'll be happy to review other package in return
Thanks, Sergio
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraprojec
Hello,
Looking at the current WG outputs, it seems that nobody is taking on
the problem of stable application runtimes:
Primary requirement
===
If all Fedora Products are released at a fairly fast cadence, and with
a fairly short support cycle, how do I write, deploy and run an
app
Hi
On Tue, Dec 17, 2013 at 4:34 PM, Tomas Hozza wrote:
> Publishing scan results for all Fedora packages might not be very good
> idea,
> since the static analysis can find issues with possible security impact.
>
Sure and if someone wants to understand that security impact inorder to
exploit t
- Original Message -
> Hi
>
>
> On Tue, Dec 17, 2013 at 12:47 PM, Daniel P. Berrange wrote:
>
>
> The issues reported against libvirt all appear to be false positives.
> Not entirely surprising since we already have coverity run against
> libvirt code nightly.
>
> Thanks for the quick
On Tue, Dec 17, 2013 at 01:17:14PM -0500, Rahul Sundaram wrote:
> Hi
>
>
> On Tue, Dec 17, 2013 at 12:47 PM, Daniel P. Berrange wrote:
>
>
> > The issues reported against libvirt all appear to be false positives.
> > Not entirely surprising since we already have coverity run against
> > libvirt
Hi
On Tue, Dec 17, 2013 at 12:47 PM, Daniel P. Berrange wrote:
> The issues reported against libvirt all appear to be false positives.
> Not entirely surprising since we already have coverity run against
> libvirt code nightly.
>
Thanks for the quick response.Does Red Hat run it only for p
On Tue, Dec 17, 2013 at 12:17:00PM -0500, Rahul Sundaram wrote:
> Hi
>
> In the last few days, I have been running cppcheck on quite a few programs
> including systemd, transmission, libvirt, ndjbdns etc and cppcheck has
> found real and potential bugs (null pointer dereferences, uninitialized
>
Hi
On Tue, Dec 17, 2013 at 12:36 PM, Dan Williams wrote:
> On Tue, 2013-12-17 at 12:17 -0500, Rahul Sundaram wrote:
> > Hi
> >
> > In the last few days, I have been running cppcheck on quite a few
> programs
> > including systemd, transmission, libvirt, ndjbdns etc and cppcheck has
> > found r
On Tuesday, December 17, 2013 11:36:26 AM Dan Williams wrote:
> > In the last few days, I have been running cppcheck on quite a few programs
> > including systemd, transmission, libvirt, ndjbdns etc and cppcheck has
> > found real and potential bugs (null pointer dereferences, uninitialized
> > va
On Tue, 2013-12-17 at 12:17 -0500, Rahul Sundaram wrote:
> Hi
>
> In the last few days, I have been running cppcheck on quite a few programs
> including systemd, transmission, libvirt, ndjbdns etc and cppcheck has
> found real and potential bugs (null pointer dereferences, uninitialized
> variabl
Hi
In the last few days, I have been running cppcheck on quite a few programs
including systemd, transmission, libvirt, ndjbdns etc and cppcheck has
found real and potential bugs (null pointer dereferences, uninitialized
variables, memory & resource leaks etc) in each of them. I have reported
th
> == First-Class Cloud Images ==
>
> The Fedora Cloud SIG has been working hard to provide images that are
> well-suited for running as guests in public and private clouds like Amazon
> Web Services (AWS) and OpenStack.
>
> If you're using public or private cloud, you should grab one of the
> do
#fedora-meeting: env and stacks (2013-12-17)
Meeting started by mmaslano at 16:01:35 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-12-17/env_and_stacks.2013-12-17-
Am 17.12.2013 16:02, schrieb Robyn Bergeron:
> We can say with great certainty the Fedora Project is pleased to announce the
> release of Fedora 20 ("Heisenbug"), which coincides with the 10th anniversary
> of the creation of the Fedora Project.
>
> Download this leading-edge, free and open so
Greetings!
We can say with great certainty the Fedora Project is pleased to announce the
release of Fedora 20 ("Heisenbug"), which coincides with the 10th anniversary
of the creation of the Fedora Project.
Download this leading-edge, free and open source operating system now:
http://fedorapro
On 12/16/2013 03:48 PM, Orion Poplawski wrote:
On 12/16/2013 12:22 PM, Stephen Herr wrote:
On 12/13/2013 03:19 PM, Orion Poplawski wrote:
On 12/13/2013 12:49 PM, Stephen Herr wrote:
Hi everyone, I'm Stephen Herr (sherr).
I noticed that the koan package is orphaned in Fedora and that it
has o
On Mon, Dec 16, 2013 at 09:04:21 +, Richard W.M. Jones wrote:
> Patches welcome. It's only 905 lines of code.
Probably not from me; most of my packages are on the small side (or are
Haskell which cabal-rpm handles the dependencies for).
> In the original case in this thread, we're interested
On Tue, Dec 17, 2013 at 2:36 PM, Miro Hrončok wrote:
> Út 17. prosinec 2013, 14:13:30 CET, Dridi Boukelmoune napsal:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=python-webcolors
>> https://bugzilla.redhat.com/show_bug.cgi?id=python-funcparserlib
>
> So I take them and you ow me two, ok?
Dea
Út 17. prosinec 2013, 14:13:30 CET, Dridi Boukelmoune napsal:
https://bugzilla.redhat.com/show_bug.cgi?id=python-webcolors
https://bugzilla.redhat.com/show_bug.cgi?id=python-funcparserlib
So I take them and you ow me two, ok?
Good news, those packages are already python3-ready, as are blockdia
Hello,
I've recently solved problems *easily* thanks to python (I'm not yet a
python person) so I thought I would give it some love and pick a
python package from the wish list.
I've chosen blockdiag, which I actually might start using (along with
its friends seqdiag, actdiag and nwdiag) so first
On Tue, Dec 17, 2013 at 12:00 PM, Stanislav Ochotnicky
wrote:
> Quoting Lukas Zapletal (2013-12-17 11:41:29)
>> On Mon, Dec 16, 2013 at 03:10:08AM -0700, T.C. Hollingsworth wrote:
>> > > I do commit locally
>> > > although I probably don't want push the snapshot sources, because I
>> > > update
>
Quoting Lukas Zapletal (2013-12-17 11:41:29)
> On Mon, Dec 16, 2013 at 03:10:08AM -0700, T.C. Hollingsworth wrote:
> > > I do commit locally
> > > although I probably don't want push the snapshot sources, because I update
> > > them later, when time comes.
>
> +1
>
> > This should happen rarely e
On Mon, Dec 16, 2013 at 03:10:08AM -0700, T.C. Hollingsworth wrote:
> > I do commit locally
> > although I probably don't want push the snapshot sources, because I update
> > them later, when time comes.
+1
> This should happen rarely enough that having to use `git commit
> --no-verify` to bypass
44 matches
Mail list logo
