On 12/06/2016 02:25 PM, Antonio Trande wrote:
> Hi all.
>
> This is an un-retiring request for QCad on Fedora
> (https://admin.fedoraproject.org/pkgdb/package/rpms/qcad/). Now upstream
> provides an open-source community edition version of QCad including
> files with following licenses:
>
> ## Ma
On 08/12/16 11:50 +, Jonathan Wakely wrote:
On 06/12/16 01:41 -, Joseph Stockman wrote:
Well, it continues to mean the busted version of boost::asio for those who want
to utilize any of the C++11 features (futures, etc). We've been forced to drop
all Fedora support for our products unt
Hi,
I would like to remind people about the Nomination period we have open
for FESCo and Council elections. Anyone who is interested in a seat in
FESCo and/or Council, please apply [1][2].
Let me also share some news about the upcoming FAmSCo elections: The
current FAmSCo has asked for new electi
On 09/12/16 09:47 +, Jonathan Wakely wrote:
On 08/12/16 11:50 +, Jonathan Wakely wrote:
On 06/12/16 01:41 -, Joseph Stockman wrote:
Well, it continues to mean the busted version of boost::asio for those who want
to utilize any of the C++11 features (futures, etc). We've been forced
We would like to enable hardware-assisted lock optimizations in glibc on
multiple architectures. In general, this feature works only on
production hardware with current firmware, and not on pre-production
machines some vendors provide for architecture bringup.
Are the Fedora builders using ha
On Thu, 8 Dec 2016 19:45:55 +0100, Christian Dersch wrote:
> On 12/08/2016 07:26 PM, Dennis Gilmore wrote:
> > I would like to see us stop pushing non security updates to updates from
> > updates-testing entirely and do it in monthly batches instead. we would
> > push
> > daily security fixes
On Thu, 8 Dec 2016 21:05:31 +0100, Emmanuel Seyman wrote:
> * Michael Cronenworth [08/12/2016 14:01] :
> >
> > Where did this concept originate from?
>
> This is a very old proposal that Spot made at the very first Flock
> way back in 2013.
The idea of monthly batches is much older.
__
On Fri, Dec 9, 2016 at 6:10 AM, Florian Weimer wrote:
> We would like to enable hardware-assisted lock optimizations in glibc on
> multiple architectures. In general, this feature works only on production
> hardware with current firmware, and not on pre-production machines some
> vendors provide
On 12/09/2016 01:22 PM, Josh Boyer wrote:
On Fri, Dec 9, 2016 at 6:10 AM, Florian Weimer wrote:
We would like to enable hardware-assisted lock optimizations in glibc on
multiple architectures. In general, this feature works only on production
hardware with current firmware, and not on pre-prod
On Fri, Dec 9, 2016 at 7:30 AM, Florian Weimer wrote:
> On 12/09/2016 01:22 PM, Josh Boyer wrote:
>>
>> On Fri, Dec 9, 2016 at 6:10 AM, Florian Weimer wrote:
>>>
>>> We would like to enable hardware-assisted lock optimizations in glibc on
>>> multiple architectures. In general, this feature work
On Fri, 09 Dec 2016 06:07:02 +0100, Kevin Kofler wrote:
> However, I also do not see why we cannot just do such big updates through
> the regular update process rather than in a big .1 drop. The KDE SIG has
> experience with pushing big grouped updates that look a lot like a .1
> release for Pl
On Thu, Dec 08, 2016 at 08:04:14PM -0500, Stephen John Smoogen wrote:
> On 8 December 2016 at 20:00, Peter Robinson wrote:
> > On Fri, Dec 9, 2016 at 12:39 AM, Stephen John Smoogen
> > wrote:
> >> On 8 December 2016 at 19:30, Peter Robinson wrote:
> >>> On Mon, Dec 5, 2016 at 2:47 PM, Matthew M
On 09/12/16 10:28 +, Jonathan Wakely wrote:
On 09/12/16 09:47 +, Jonathan Wakely wrote:
On 08/12/16 11:50 +, Jonathan Wakely wrote:
On 06/12/16 01:41 -, Joseph Stockman wrote:
Well, it continues to mean the busted version of boost::asio for those who want
to utilize any of the
On 9 December 2016 at 07:41, Josh Boyer wrote:
> On Fri, Dec 9, 2016 at 7:30 AM, Florian Weimer wrote:
>> On 12/09/2016 01:22 PM, Josh Boyer wrote:
>> We can't predict the future. But if Fedora builders use commercially
>> supported hardware (and not pre-production samples from one of Red Hat's
Missing expected images:
Kde live x86_64
Kde live i386
Failed openQA tests: 11/90 (x86_64), 5/16 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20161208.n.0):
ID: 50861 Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/50861
I
On Thu, Dec 08, 2016 at 12:13:59PM -0800, Adam Williamson wrote:
> Frankly, this all seems like a lot of churn and mess and process change
> for no very obvious benefit. I'm a hell of a lot more interested in
> looking at smaller and more frequent 'release' events than larger less
> frequent ones.
On Thu, Dec 8, 2016, at 09:26 PM, Colin Walters wrote:
> Anyways, in the big picture, while I don't speak for everyone on the Project
> Atomic side,
> I personally point users at CentOS first, unless I have some reason to think
> they want Fedora.
> Something like 80% of Fedora usage hitting the
On Fri, Dec 09, 2016 at 11:07:32AM -0500, Colin Walters wrote:
> > Anyways, in the big picture, while I don't speak for everyone on
> > the Project Atomic side, I personally point users at CentOS first,
> > unless I have some reason to think they want Fedora. Something like
> > 80% of Fedora usage
On Friday, 09 December 2016 at 13:41, Josh Boyer wrote:
> On Fri, Dec 9, 2016 at 7:30 AM, Florian Weimer wrote:
> > On 12/09/2016 01:22 PM, Josh Boyer wrote:
> >> On Fri, Dec 9, 2016 at 6:10 AM, Florian Weimer wrote:
[...]
> >>> What about default Fedora installations? Do they come with early bo
On Fri, Dec 9, 2016 at 11:18 AM, Dominik 'Rathann' Mierzejewski
wrote:
> On Friday, 09 December 2016 at 13:41, Josh Boyer wrote:
>> On Fri, Dec 9, 2016 at 7:30 AM, Florian Weimer wrote:
>> > On 12/09/2016 01:22 PM, Josh Boyer wrote:
>> >> On Fri, Dec 9, 2016 at 6:10 AM, Florian Weimer wrote:
> [
On 9 December 2016 at 07:58, Pierre-Yves Chibon wrote:
>>
>> No that is a separate data set.
>
> The title of the graph might need a little adjustment :)
Ah thanks. I have fixed the title and added a reverse stacked graph
https://smooge.fedorapeople.org/fedora-all-stacked-ma.png
https://smooge
On Fri, Dec 09, 2016 at 01:18:31PM +0100, Michael Schwendt wrote:
> On Thu, 8 Dec 2016 19:45:55 +0100, Christian Dersch wrote:
>
> > On 12/08/2016 07:26 PM, Dennis Gilmore wrote:
> > > I would like to see us stop pushing non security updates to updates from
> > > updates-testing entirely and do i
From 79fd51a1eafc9d52adc41f992777bd7c27c795e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?=
Date: Fri, 9 Dec 2016 17:31:00 +0100
Subject: Update to HTML-Formatter-2.16.
- Reflect upstream having switched to ExtUtils::MakeMaker.
- Spec cleanup.
---
.gitignore| 2 +-
On 9 December 2016 at 11:07, Colin Walters wrote:
> On Thu, Dec 8, 2016, at 09:26 PM, Colin Walters wrote:
>
>> Anyways, in the big picture, while I don't speak for everyone on the Project
>> Atomic side,
>> I personally point users at CentOS first, unless I have some reason to think
>> they wan
On Fri, Dec 9, 2016 at 11:30 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Dec 09, 2016 at 01:18:31PM +0100, Michael Schwendt wrote:
>> On Thu, 8 Dec 2016 19:45:55 +0100, Christian Dersch wrote:
>>
>> > On 12/08/2016 07:26 PM, Dennis Gilmore wrote:
>> > > I would like to see us stop pushing non
On Fri, 2016-12-09 at 11:17 -0500, Matthew Miller wrote:
> On Fri, Dec 09, 2016 at 11:07:32AM -0500, Colin Walters wrote:
> > > Anyways, in the big picture, while I don't speak for everyone on
> > > the Project Atomic side, I personally point users at CentOS
> > > first,
> > > unless I have some re
On Fri, 2016-12-09 at 13:18 +0100, Michael Schwendt wrote:
> The apparently random flow of poorly tested "rushed out" updates
I've had automatic updates, of all kinds, turned on on all of my
servers for at least the last four releases, and can think of maybe one
time one of them broke? This seem
On Fri, 2016-12-09 at 11:03 -0500, Matthew Miller wrote:
> So, *did* you feel that the F25 cycle felt compressed? If we're close
> enough to the theoretical-world above that we feel like we can do, say,
> four month cycles to stay on track without experiencing (particular)
> pain, maybe that's okay
On 9 December 2016 at 11:42, Nikos Mavrogiannopoulos wrote:
> On Fri, 2016-12-09 at 11:17 -0500, Matthew Miller wrote:
>> On Fri, Dec 09, 2016 at 11:07:32AM -0500, Colin Walters wrote:
>> > > Anyways, in the big picture, while I don't speak for everyone on
>> > > the Project Atomic side, I persona
===
#fedora-meeting: FESCO (2016-12-09)
===
Meeting started by maxamillion at 16:00:37 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco.2016-12-09-16.00.log.html
.
Meeting summa
On Fri, 2016-12-09 at 15:43 +, Fedora compose checker wrote:
> Missing expected images:
>
> Kde live x86_64
> Kde live i386
>
> Failed openQA tests: 11/90 (x86_64), 5/16 (i386), 1/2 (arm)
>
> New failures (same test did not fail in Rawhide-20161208.n.0):
>
> ID: 50861 Test: x86_64 Works
On Dec 9, 2016 5:18 PM, "Matthew Miller" wrote:
On Fri, Dec 09, 2016 at 11:07:32AM -0500, Colin Walters wrote:
> > Anyways, in the big picture, while I don't speak for everyone on
> > the Project Atomic side, I personally point users at CentOS first,
> > unless I have some reason to think they wa
Once upon a time, Adam Miller said:
> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
> available at
> https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco.2016-12-09-16.00.log.html
So, this is a minor request...
I read email in mutt, a terminal-based mail client.
On Fri, Dec 9, 2016 at 12:20 PM, Chris Adams wrote:
> Once upon a time, Adam Miller said:
>> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
>> available at
>> https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco.2016-12-09-16.00.log.html
>
> So, this is a minor req
On Fri, Dec 9, 2016 at 12:14 PM, Igor Gnatenko
wrote:
> On Dec 9, 2016 5:18 PM, "Matthew Miller" wrote:
>
> On Fri, Dec 09, 2016 at 11:07:32AM -0500, Colin Walters wrote:
>> > Anyways, in the big picture, while I don't speak for everyone on
>> > the Project Atomic side, I personally point users a
On Fri, 09 Dec 2016 08:44:26 -0800, Adam Williamson wrote:
> On Fri, 2016-12-09 at 13:18 +0100, Michael Schwendt wrote:
> > The apparently random flow of poorly tested "rushed out" updates
>
>
Nah, not needed at all. Basically, one can update a desktop workstation to
death, if applying update
On Fri, 2016-12-09 at 18:37 +0100, Michael Schwendt wrote:
> On Fri, 09 Dec 2016 08:44:26 -0800, Adam Williamson wrote:
>
> > On Fri, 2016-12-09 at 13:18 +0100, Michael Schwendt wrote:
> > > The apparently random flow of poorly tested "rushed out" updates
> >
> >
>
> Nah, not needed at all. B
On 12/09/2016 11:17 AM, Matthew Miller wrote:
For other software, where users would like the
version to match more closely the long lifecycle, maybe there could be
a hand-off from Fedora version to CentOS version.
Yeah, hand-offs would be a great feature for the users. Right now, it's
tricky to
On Qui, 2016-12-08 at 09:17 -0500, Matthew Miller wrote:
> Trying to make this idea a little more concrete. Here's two
> suggestions
> for how it might work. These are strawman ideas -- please provide
> alternates, poke holes, etc. And particularly from a QA and rel-eng
> point of view. Both of the
On 9 December 2016 at 12:35, Josh Boyer wrote:
> On Fri, Dec 9, 2016 at 12:20 PM, Chris Adams wrote:
>> Once upon a time, Adam Miller said:
>>> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
>>> available at
>>> https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco
On 12/09/2016 01:51 PM, Michael Schwendt wrote:
On Fri, 09 Dec 2016 06:07:02 +0100, Kevin Kofler wrote:
If as a maintainer you don't release version upgrades quickly, some users
complain everywhere they are permitted to post. Except for bugzilla. And
if you make available upgrades quickly, the
On Fri, 09 Dec 2016 09:40:08 -0800, Adam Williamson wrote:
> This is just a bunch of entirely unsupported assertions, and thus not
> worth the time to respond to.
Same applies to your usage scenario. Personal experience is just that:
personal experience.
> But I'll just note that it is not possi
On Fri, 2016-12-09 at 19:48 +0100, Michael Schwendt wrote:
> On Fri, 09 Dec 2016 09:40:08 -0800, Adam Williamson wrote:
>
> > This is just a bunch of entirely unsupported assertions, and thus not
> > worth the time to respond to.
>
> Same applies to your usage scenario. Personal experience is jus
On Fri, Dec 9, 2016 at 4:51 AM, Michael Schwendt
wrote:
> And there it is again, the rush to get out updates. Quickly! Quickly!
> What has been released before is not bug-free, and the update are not
> bug-free either, and even if no user has reported a bug, the flow of
> updates will ensure that
Once upon a time, Josh Boyer said:
> On Fri, Dec 9, 2016 at 12:20 PM, Chris Adams wrote:
> > Once upon a time, Adam Miller said:
> >> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
> >> available at
> >> https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco.2016-12
On Fri, Dec 9, 2016 at 11:00 AM, Adam Williamson wrote:
> Yes, but the burden of proof always lies with those who want to change
> stuff. I've got the easy job here: I just get to say 'look, if you want
> to change everything, provide some concrete evidence:
>
> a) that there's a problem
> b) tha
On 12/06/2016 08:25 AM, Antonio Trande wrote:
This is an un-retiring request for QCad on Fedora
(https://admin.fedoraproject.org/pkgdb/package/rpms/qcad/). Now upstream
provides an open-source community edition version of QCad
Could you comment on the current relationship of QCad to its fork
Lib
On Fri, 9 Dec 2016 19:41:28 +0100, Ralf Corsepius wrote:
> And? What*s the problem? It's part of a packagers job to balance the
> tradeoffs and find a viable compromise.
You don't need to agree. In the reply you've truncated, I've only pointed
out how I feel about the updates flood. It's my numb
On Fri, Dec 09, 2016 at 08:50:06AM -0800, Adam Williamson wrote:
> > So, *did* you feel that the F25 cycle felt compressed? If we're close
> > enough to the theoretical-world above that we feel like we can do, say,
> > four month cycles to stay on track without experiencing (particular)
> > pain, m
On Fri, 2016-12-09 at 20:46 +0100, Michael Schwendt wrote:
> On Fri, 9 Dec 2016 19:41:28 +0100, Ralf Corsepius wrote:
>
> > And? What*s the problem? It's part of a packagers job to balance the
> > tradeoffs and find a viable compromise.
>
> You don't need to agree. In the reply you've truncated,
On Fri, Dec 09, 2016 at 11:55:26AM -0800, Adam Williamson wrote:
> problem. The fact that updates default to auto-push after +3 karma is
> entirely plucked out of the air, it's just something someone made up
> one day. We could *certainly* change that. I'd be quite interested in a
> tweak where the
On Fri, 2016-12-09 at 15:05 -0500, Matthew Miller wrote:
> On Fri, Dec 09, 2016 at 11:55:26AM -0800, Adam Williamson wrote:
> > problem. The fact that updates default to auto-push after +3 karma is
> > entirely plucked out of the air, it's just something someone made up
> > one day. We could *certa
On 12/09/2016 02:52 PM, Matthew Miller wrote:
On Fri, Dec 09, 2016 at 08:50:06AM -0800, Adam Williamson wrote:
So, *did* you feel that the F25 cycle felt compressed? If we're close
enough to the theoretical-world above that we feel like we can do, say,
four month cycles to stay on track without
On Fri, Dec 9, 2016 at 1:12 PM, Adam Williamson
wrote:
> On Fri, 2016-12-09 at 15:05 -0500, Matthew Miller wrote:
>> On Fri, Dec 09, 2016 at 11:55:26AM -0800, Adam Williamson wrote:
>> > problem. The fact that updates default to auto-push after +3 karma is
>> > entirely plucked out of the air, it'
On Fri, 2016-12-09 at 13:21 -0700, Chris Murphy wrote:
> On Fri, Dec 9, 2016 at 1:12 PM, Adam Williamson
> wrote:
> > On Fri, 2016-12-09 at 15:05 -0500, Matthew Miller wrote:
> > > On Fri, Dec 09, 2016 at 11:55:26AM -0800, Adam Williamson wrote:
> > > > problem. The fact that updates default to au
On Fri, Dec 09, 2016 at 03:19:58PM -0500, langdon wrote:
> >Langdon is sitting right next to me right now and I'm going to tag him
> >in for more on Modularity.
[...]
> them. We can also decide when a "release" makes sense based on
> marketing or other considerations and just "pull the trigger" on
On Fri, 09 Dec 2016 11:00:45 -0800, Adam Williamson wrote:
> > Same applies to your usage scenario. Personal experience is just that:
> > personal experience.
>
> Yes, but the burden of proof always lies with those who want to change
> stuff. I've got the easy job here: I just get to say 'look,
On Fri, 2016-12-09 at 12:25 -0800, Adam Williamson wrote:
> Software will check for new updates at most every 48 hours, so if
> there
> happen to *be* new updates every 48 hours and your system is running
> the whole time, yeah, you can get 3-and-a-bit update notifications
> per
> week.
Not *quite
On Fri, 2016-12-09 at 21:29 +0100, Michael Schwendt wrote:
> Of course, the developers of bodhi would need to be convinced of such a
> feature, too, and it could be that there is no big kahuna to do exactly
> that. Oh well.
Well, no, you could just send a patch. Bodhi is a rather nice codebase
and
On Fri, 2016-12-09 at 14:31 -0600, Michael Catanzaro wrote:
> On Fri, 2016-12-09 at 12:25 -0800, Adam Williamson wrote:
> > Software will check for new updates at most every 48 hours, so if
> > there
> > happen to *be* new updates every 48 hours and your system is running
> > the whole time, yeah,
Hi all
Just modified the gsequencer.spec file. Now, it should be more the fedora way.
https://sourceforge.net/projects/ags/files/fedora/
Additionally, I uploaded the srpm and rpm packages built.
* gsequencer
* gsequencer-devel
* gsequencer-devel-docs
* gsequencer-debuginfo
Bests,
Joël
On Thu
On Fri, 9 Dec 2016 21:57:07 +0100, Joël Krähemann wrote:
> Hi all
>
> Just modified the gsequencer.spec file. Now, it should be more the fedora way.
>
> https://sourceforge.net/projects/ags/files/fedora/
>
> Additionally, I uploaded the srpm and rpm packages built.
>
> * gsequencer
> * gsequen
On Fri, Dec 09, 2016 at 11:29:29AM -0500, Stephen John Smoogen wrote:
> Ah thanks. I have fixed the title and added a reverse stacked graph
>
> https://smooge.fedorapeople.org/fedora-all-stacked-ma.png
What happened in late 2014?
smime.p7s
Description: S/MIME cryptographic signature
___
On 10 Dec 2016 08:06, "Scott Schmit" wrote:
On Fri, Dec 09, 2016 at 11:29:29AM -0500, Stephen John Smoogen wrote:
> Ah thanks. I have fixed the title and added a reverse stacked graph
>
> https://smooge.fedorapeople.org/fedora-all-stacked-ma.png
What happened in late 2014?
Fedora 21 which was
Hi Michael
I'm not sure of what packaging mistakes you are talking.
I just updated the spec file and removed the requires field.
But yes, I'd like to give it for review now.
Bests,
Joël
On Fri, Dec 9, 2016 at 10:04 PM, Michael Schwendt wrote:
> On Fri, 9 Dec 2016 21:57:07 +0100, Joël Kräheman
On 9 December 2016 at 16:06, Scott Schmit wrote:
> On Fri, Dec 09, 2016 at 11:29:29AM -0500, Stephen John Smoogen wrote:
>> Ah thanks. I have fixed the title and added a reverse stacked graph
>>
>> https://smooge.fedorapeople.org/fedora-all-stacked-ma.png
>
> What happened in late 2014?
We droppe
On Fri, Dec 09, 2016 at 01:19:13PM -0600, Chris Adams wrote:
> Once upon a time, Josh Boyer said:
> > On Fri, Dec 9, 2016 at 12:20 PM, Chris Adams wrote:
> > > Once upon a time, Adam Miller said:
> > >> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
> > >> available at
> > >>
On Fri, Dec 9, 2016 at 3:25 PM, Stephen John Smoogen wrote:
> On 9 December 2016 at 07:41, Josh Boyer wrote:
>> On Fri, Dec 9, 2016 at 7:30 AM, Florian Weimer wrote:
>>> On 12/09/2016 01:22 PM, Josh Boyer wrote:
>
>>> We can't predict the future. But if Fedora builders use commercially
>>> supp
On Fri, Dec 9, 2016 at 11:10 AM, Florian Weimer wrote:
> We would like to enable hardware-assisted lock optimizations in glibc on
> multiple architectures. In general, this feature works only on production
> hardware with current firmware, and not on pre-production machines some
> vendors provide
>>> > problem. The fact that updates default to auto-push after +3 karma is
>>> > entirely plucked out of the air, it's just something someone made up
>>> > one day. We could *certainly* change that. I'd be quite interested in a
>>> > tweak where there's a minimum-time-in-testing value for autopush
On Fri, Dec 09, 2016 at 04:21:27PM -0500, Stephen John Smoogen wrote:
> >> Ah thanks. I have fixed the title and added a reverse stacked graph
> >> https://smooge.fedorapeople.org/fedora-all-stacked-ma.png
> > What happened in late 2014?
> We dropped SSLv2 and SSLv3 and some TLS algorithms. This dr
On Fri, Dec 09, 2016 at 10:22:44PM +, Peter Robinson wrote:
> repo data). The full list makes up most of the 40Mb downloaded. The
> dnf developers seem to think that everyone has lots of data/bandwidth
> and don't see the problem with it.
Isn't the problem that the SAT solver used by DNF for d
On Friday, December 9, 2016, Matthew Miller
wrote:
> On Fri, Dec 09, 2016 at 03:19:58PM -0500, langdon wrote:
> > >Langdon is sitting right next to me right now and I'm going to tag him
> > >in for more on Modularity.
> [...]
> > them. We can also decide when a "release" makes sense based on
> >
On Fri, 9 Dec 2016 13:19:13 -0600
Chris Adams wrote:
> Once upon a time, Josh Boyer said:
> > On Fri, Dec 9, 2016 at 12:20 PM, Chris Adams
> > wrote:
> > > Once upon a time, Adam Miller
> > > said:
> > >> Meeting started by maxamillion at 16:00:37 UTC. The full logs are
> > >> available at
On Thu, 8 Dec 2016 12:40:49 -0500
Przemek Klosowski wrote:
> On 12/08/2016 11:10 AM, Matthew Miller wrote:
> > It's my plan to explore different ideas to continue to make Fedora
> > more successful as measured by user and contributor growth,
> > contributor return on effort, and fulfillment of ou
On 12/09/2016 03:26 PM, Matthew Miller wrote:
On Fri, Dec 09, 2016 at 03:19:58PM -0500, langdon wrote:
Langdon is sitting right next to me right now and I'm going to tag him
in for more on Modularity.
[...]
them. We can also decide when a "release" makes sense based on
marketing or other consi
Hi all
For your information
http://koji.fedoraproject.org/koji/taskinfo?taskID=16809691
https://copr.fedorainfracloud.org/coprs/jkraehemann/gsequencer/
Bests,
Joël
On Fri, Dec 9, 2016 at 10:15 PM, Joël Krähemann wrote:
> Hi Michael
>
> I'm not sure of what packaging mistakes you are talking.
>
On 8 Dec 2016, at 11:22, Dennis Gilmore wrote:
On miércoles, 7 de diciembre de 2016 1:56:32 PM CST Mike Pinkerton
wrote:
I use the Server netinstall image. Use cases include loop mounting
the netinstall .iso on boxes with Grub2 -- works on remote boxes
where there is no physical access and
On Fri, Dec 09, 2016 at 11:29:29AM -0500, Stephen John Smoogen wrote:
> On 9 December 2016 at 07:58, Pierre-Yves Chibon wrote:
>
> >>
> >> No that is a separate data set.
> >
> > The title of the graph might need a little adjustment :)
>
> Ah thanks. I have fixed the title and added a reverse st
On Fri, Dec 09, 2016 at 09:57:07PM +0100, Joël Krähemann wrote:
> Hi all
>
> Just modified the gsequencer.spec file. Now, it should be more the fedora way.
>
> https://sourceforge.net/projects/ags/files/fedora/
>
> Additionally, I uploaded the srpm and rpm packages built.
>
> * gsequencer
> * g
Well, I must say, Fedora is not making it easy! I've used Debian for a few
years and I really expect to install something and have it work.
But...there are selinux issues, I guess. I really don't know about
selinux...now I'm learning a lot. There is a folder labeled "selinux" in
/usr/share/doc/
Well, I must say, Fedora is not making it easy! I've used Debian for a few
years and I really expect to install something and have it work.
But...there are selinux issues, I guess. I really don't know about
selinux...now I'm learning a lot. There is a folder labeled "selinux" in
/usr/share/doc/
CORRECTION:
There is a folder labeled "selinux" in /usr/share/doc/dict-server/
I seem to remember installing Fedora years and years ago and being driven crazy
for a week trying to get apache working. I really think having a package named
"dictd-server" should just install that package. Well, i
83 matches
Mail list logo
