> What happens if the user isn't using DNF? For the workstation we have
> to support users using just the graphical tools, and we can't rely on
> command line tools for this kind of thing. I'm happy to add support
> for installing lang packs into gnome-software but need to know how the
> langpack p
On Thu, Mar 3, 2016 at 10:18 PM, linux guy wrote:
> As far as I know there are no special requirements for 0.29.x that prevent
> it from being built for F23.
The 0.29 series is the development release, we won't be updating it in
stable Fedora releases. It is already in Fedora 24+ and that is the
On Sun, Mar 6, 2016 at 10:11 AM, Hans de Goede wrote:
> Hi,
>
> I'm getting:
>
> Error: Package systemd-udev-229-5.fc24.x86_64.rpm is not signed
>
> When doing a "dnf update", I'm following the f24 branch / repo.
> This used to work with previous pushes, and AFAIK F24 pushes
> are supposed to be s
On Mon, Mar 7, 2016 at 10:04 AM, Vít Ondruch wrote:
> Not sure where should I report this issue, but I am wondering, why my
> secondary monitor is not detected after docking my Rawhide laptop (it
> works just fine after restart)? It used to work. If it didn't work right
> away, opening control pan
> Dne 7.3.2016 v 11:47 Peter Robinson napsal(a):
>> On Mon, Mar 7, 2016 at 10:04 AM, Vít Ondruch wrote:
>>> Not sure where should I report this issue, but I am wondering, why my
>>> secondary monitor is not detected after docking my Rawhide laptop (it
>>> wor
On Mon, Mar 14, 2016 at 10:56 AM, Vít Ondruch wrote:
>
>
> Dne 12.3.2016 v 15:32 Fedora Rawhide Report napsal(a):
>> = SUMMARY =
>> Added packages: 11
>> Dropped packages:0
>> Upgraded packages: 164
>> Downgraded packages: 2
>>
>
>
> Interesting, is this already 4th downgraded p
On Mon, Mar 14, 2016 at 2:15 PM, Dave Johansen wrote:
> I don't understand what happened here.
>
> Did aarch64 only recently update to gcc 6.0?
> What's the right way to fix this? Just do a rebuild for all arches?
Ignore it, it was a bug in a compose script, those email aren't meant
to go out for
On Tue, Mar 15, 2016 at 8:34 AM, Richard Hughes wrote:
> On 15 March 2016 at 08:04, Vít Ondruch wrote:
>> So will it be 3rd time in 3 months you are going to broke my
>> Rawhide?
>
> I think using the F25 packages when F24 alpha hasn't even been
> released is probably asking for trouble. Are we s
On Tue, Mar 15, 2016 at 9:24 AM, Richard Hughes wrote:
> On 15 March 2016 at 09:17, Vít Ondruch wrote:
>>> I'm somewhat confused where the problem is.
>> This is the problem:
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CI57RU5TGQZFGVTUJKM6S6WU2NU4VION/
>
On Tue, Mar 15, 2016 at 4:46 PM, Matthias Clasen wrote:
> On Tue, 2016-03-15 at 13:06 +0100, Vít Ondruch wrote:
>> So do you see any solution/improvement for this issue? I repeatedly
>> reported the breakages, I made some proposals (as simple as "send an
>> email"), which IMO should improve the si
On Tue, Mar 15, 2016 at 3:29 PM, Richard Hughes wrote:
> On 15 March 2016 at 15:09, Jared K. Smith wrote:
>> Would you be willing to at least try it for a couple of iterations
>> and see how it goes?
>
> Three questions:
>
> * Which packages should use this side tag?
> * When *exactly* would we
On Thu, Mar 17, 2016 at 1:13 AM, Xose Vazquez Perez
wrote:
> Josh Boyer wrote:
>
>> There is no need to call this ridiculous or nonsense. There have been
>> valid reasons brought up in this very thread for being somewhat
>> conservative. Please refrain from using language that makes the
>> conve
On Fri, Mar 25, 2016 at 1:26 PM, Richard W.M. Jones wrote:
>
> Example:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=13456541
>
> BuildError: Error running GIT command "git clone -n
> git://pkgs.fedoraproject.org//libguestfs
> /var/lib/mock/f25-build-5255253-593583/root/tmp/scmroot/libgu
The Fedora 24 Alpha for aarch64 is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Server
https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Alpha/Server/aarch64/
https://fedoraproject.org/wiki/Arch
The Fedora 24 Alpha for POWER is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Workstation https://getfedora.org/en/workstation/
prerelease/
- Get Fedora 24 Alpha Server https://getfedora.org/en/server/prerelease
On Tue, Apr 5, 2016 at 1:51 PM, Kaleb KEITHLEY wrote:
>
> I pushed glusterfs-3.7.9-1.fc23 to stable four days ago. It has +4 karma.
>
> It's still pending. Is it stuck? Can someone please give it a kick?
All the updates are already in process of being kicked by me, should
hopefully be moving aga
>>> I pushed glusterfs-3.7.9-1.fc23 to stable four days ago. It has +4 karma.
>>>
>>> It's still pending. Is it stuck? Can someone please give it a kick?
>>
>> All the updates are already in process of being kicked by me, should
>> hopefully be moving again shortly.
>>
>
> Thanks,
>
> I have sever
On Thu, Apr 7, 2016 at 12:18 PM, Kaleb KEITHLEY wrote:
> On 04/07/2016 06:45 AM, Peter Robinson wrote:
>>>>> I pushed glusterfs-3.7.9-1.fc23 to stable four days ago. It has +4 karma.
>>>>>
>>>>> It's still pending. Is it stuck? Can someone
On Mon, Apr 18, 2016 at 10:05 PM, Adam Williamson
wrote:
> Hi folks! Time for a first F24 Beta blocker bug status mail. Today is
> the Beta freeze date, so we need to be really focusing on getting Beta
> into shape now.
Sorry about the delayed response, I'd already gone to bed with manflu.
> tl;
On Tue, Apr 26, 2016 at 1:42 PM, Richard Shaw wrote:
> As far as I can tell it sounds like the driver is doing codec work in the
> shader code (for example h264) which is not permitted in Fedora due to
> patent issues.
Correct
> There was a mention of a package on RPM Fusion but I couldn't find
On Tue, Apr 26, 2016 at 2:24 PM, František Zatloukal
wrote:
> Yes, it's in rpmfusion
>
> Thanks everybody! It'd be great if the package can be separated so we can
> have at least free codecs HW accelerated.
Given it's all built into a single .so file it might not be that easy,
but definitely a RF
>>> As for Option 1)? I think someone with more knowledge of the individual
>>> modules
>>> in Fedora (Tom Hughes? Jared Smith?) would need to figure out how many
>>> modules
>>> would be broken if we downgraded. If it's sufficiently small, I suppose we
>>> could
>>> epoch-bump nodejs and its vi
On Wed, Apr 27, 2016 at 1:54 PM, Josh Boyer wrote:
> On Wed, Apr 27, 2016 at 7:38 AM, Denise Dumas wrote:
>> Sounds like a job for rhscl :-)
>
> Maybe?
>
> Having nodejs in an SCL (or eventually module) would certainly help
> with versioning issues going forward. However, given Fedora has
Versi
>>> The reason for not having mass rebuild during F25 development cycle is
>>> very tight schedule for F25 and we would like to avoid slips in F25 as
>>> much as possible. That is the main motivation here.
>> In other words sacrificing quality for marketing reasons - Utterly poor :(
>>
>
> It's not
> Sorry for delay for writing this. We wanted to provide latest DNF
> stack in EPEL7 which means we also need newer components like libsolv,
> hawkey, librepo, etc.
Delayed so much you've already pushed them to testing I see.I'd like
to see those unpushed until a decision is made. This isn't "push
>> Sorry for delay for writing this. We wanted to provide latest DNF
>> stack in EPEL7 which means we also need newer components like libsolv,
>> hawkey, librepo, etc.
>>
>> Some of those are in RHEL7.2 and unfortunately it's not that easy to
>> get them updated:
>> - librepo
>> - libsolv
>> - hawk
On Mon, May 9, 2016 at 3:33 PM, Florian Weimer wrote:
> I'd like to push a glibc update to Fedora 24. It does not matter if it goes
> into the release, it is just a collection of minor security fixes and
> corrections to user-reported bugs. We are currently preparing an update for
> Fedora 23 wi
The Fedora 24 Beta for aarch64 is here, on schedule for our planned June final
release. For Beta we have added Cloud and Docker base images.
Download the prerelease from our Get Fedora site:
- Get Fedora 24 Beta Server: make use of the very latest server-based
technologies available in the o
>> = Proposed System Wide Change: Use /etc/distro.repos.d as default reposdir =
>> https://fedoraproject.org/wiki/Changes/ReposInEtcDistroReposD
>>
>> Change owner(s):
>> * Neal Gompa
>> * Jan Silhan
>>
>>
>> == Detailed Description ==
>> For DNF 2.0 in Fedora 25, the DNF team would like to make
> A build failed with the -Wnarrowing error in rawhide on ARM
>
> I've got access to another ARM box where I want to reproduce the
> problem, but running gcc 6 on that box, -Wnarrowing is only a warning.
>
> I added -std=c++11 to CPPFLAGS and now it fails on the other box too,
> but are there other
The Fedora 24 Beta for Power64 is here, for our planned June final
release. For Beta we have Cloud and Docker base images.
Download the prerelease from our Get Fedora site:
- Get Fedora 24 Beta Server: make use of the very latest server-based
technologies available in the open source communi
On Tue, Oct 18, 2016 at 8:30 PM, Simone Caronni wrote:
> Hello,
>
> I've tried to push a couple of new libraries in epel-7, but the update did
> not reach the testing repository in 7 days:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e4793acdf5
>
> Is there anything wrong with it?
>> I need/want/would like to build new node 6 for EL6, but gcc is too old.
>> For that reason, I'd like to use devtoolset-4-gcc, but the build fails
>> (obviously) because the package doesn't exist.
>>
>> So, is there a way to make that work somehow?
>> I am not sure about enabling external repos d
On Fri, Oct 21, 2016 at 9:43 AM, Jan Synacek wrote:
> Why were critpath flags set on Emacs and Guile?
Because they get pulled into builds for core deliverables. In the
case of emacs I believe it's because emacs-filesystem gets pulled in
due to libidn (I've no idea why libidn needs that and I'd l
On Fri, Oct 21, 2016 at 2:21 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Oct 21, 2016 at 01:31:25PM +0200, Jan Kratochvil wrote:
>> On Fri, 21 Oct 2016 13:18:38 +0200, Peter Robinson wrote:
>> > guild would be because it's a dep of a dep of gdb-headless
>> guil
On Sun, Oct 23, 2016 at 3:09 PM, Michael Catanzaro wrote:
> On Sun, 2016-10-23 at 03:49 +, Christopher wrote:
>> 2. Should I preserve the entire changelog in the SPEC? Or should I
>> roll it
>> over when I update to the latest upstream? It seems the changelog
>> could
>> easily become the bulk
>> On Mon, Oct 24, 2016 at 05:00:21PM -0400, Josh Boyer wrote:
>> > > Please, no, don't do that. RPM is a standard, the changelog is
>> > > part of that. It would be pretty crappy to just declare we're
>> > > going to stop using RPM changelogs and bake some random new idea
>> > > into our distro's
On Wed, Oct 26, 2016 at 4:25 PM, Matthew Miller
wrote:
> On Tue, Oct 25, 2016 at 07:37:32PM -0600, Kevin Fenzi wrote:
>> Nope. We have talked about having some kind of fast track, but IMHO, we
>> should just get the normal process faster.
>
> Getting the normal process faster would help in a large
On Mon, Oct 31, 2016 at 1:25 PM, Marek Skalický wrote:
> Hi,
> current situation:
> EPEL6 - MongoDB 2.4.x
> EPEL7 - MongoDB 2.6.x
>
> Upstream supports only upgrade to next major version. So from 2.4 it is
> supported only to 2.6.
> Therefore I kept MongoDB 2.6 in EPEL7 (even two next major versio
We need Vulkan loader which is now on review. I will take care of it
ASAP.
>>>
>>>
>>> I see it[1] now. Thanks, Igor. If there is anything I can do to help with
>>> the review just let me know.
>>>
>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1308985
>>
>>
>> The vulkan loader has
On Wed, Nov 2, 2016 at 10:41 AM, Christian Stadelmann
wrote:
> 1. and 2.: Yes, it often takes at least 3 days for security critical updates
> in important packages (e.g. kernel update to 4.8.3) to land.
>
> I think the real challenge here is to continue shipping quality software
> while reducing
> $ fedpkg build --target=f26-ocaml
> Building mldonkey-3.1.5-10.fc26 for f26-ocaml
> Created task: 16300957
> Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=16300957
> Watching tasks (this may be safely interrupted)...
> 16300957 build (f26-ocaml,
> /rpms/mldonkey:8013f45d7fdb60959
On 5 Nov 2016 12:24, "Richard W.M. Jones" wrote:
>
> On Sat, Nov 05, 2016 at 12:12:37PM +, Peter Robinson wrote:
> > > $ fedpkg build --target=f26-ocaml
> > > Building mldonkey-3.1.5-10.fc26 for f26-ocaml
> > > Created task: 16300957
> >
On Mon, Nov 7, 2016 at 11:33 AM, Vít Ondruch wrote:
> What is wrong with the PPC? Is it missing dependencies on its own
> subpackages or how I should understand this?
The tagged build on F-26 was FTBFS on ppc64 so the associated build
wasn't imported for rubygem-bson. Fix the rubygem-bson failure
On Tue, Nov 8, 2016 at 9:06 AM, Richard W.M. Jones wrote:
> On Tue, Oct 18, 2016 at 02:04:22PM +0100, Richard W.M. Jones wrote:
>> OCaml 4.03 has been out for a while.
>
> Since OCaml 4.04.0 was released last Friday, we rebased to 4.04.0.
>
> This is now ready to test. If you have Rawhide + some
On Tue, Nov 8, 2016 at 12:22 PM, Hans de Goede wrote:
> Hi all,
>
> I'm getting a bunch of broken dependencies
> mails every day due to a few games I maintain
> depending on pygame (during runtime) and
> that is not available on ppc64 / ppc64le.
A fix should be landing shortly.
Peter
> Checking
On Wed, Nov 9, 2016 at 5:00 PM, Petr Pisar wrote:
> On 2016-11-09, Rex Dieter wrote:
>> I was looking at rawhide (ppc64) broken deps, and was reminded of some
>> pretty old and unmaintained (upstream) kde4/smoke-based language bindings
>> (csharp, perl, ruby), affected packages include:
>>
>> kde
On Wed, Nov 9, 2016 at 2:42 PM, Rex Dieter wrote:
> I was looking at rawhide (ppc64) broken deps, and was reminded of some
> pretty old and unmaintained (upstream) kde4/smoke-based language bindings
> (csharp, perl, ruby), affected packages include:
>
> kdebindings
> kimono
> perl-Qt
> ruby-korund
On Fri, Nov 11, 2016 at 9:08 AM, Fabio Alessandro Locati
wrote:
> On Fri, Nov 11, 2016 at 12:34:20AM -0800, Adam Williamson wrote:
>> One thing I forgot to mention in my original reply to jwb (it was
>> getting long) is that there's a conundrum that applies quite
>> specifically to Mac support, an
>> > On Fri, Nov 11, 2016 at 12:34:20AM -0800, Adam Williamson wrote:
>> >> One thing I forgot to mention in my original reply to jwb (it was
>> >> getting long) is that there's a conundrum that applies quite
>> >> specifically to Mac support, and it's this: there are quite a lot of
>> >> people wh
On Fri, Nov 11, 2016 at 12:55 PM, Josh Boyer wrote:
> On Fri, Nov 11, 2016 at 7:43 AM, Michael Catanzaro
> wrote:
>> My $0.02 is that none of the reasons we requested the blocker criterion
>> have changed. Dual boot with macOS is very important to attracting new
>> users -- we're explicitly targ
On Sat, Nov 12, 2016 at 7:32 PM, Michael Catanzaro wrote:
> On Sat, 2016-11-12 at 18:26 +0100, Ms Sanchez wrote:
>> Oh..! Now I see why the new didn't reach me, I'm not in the legal
>> list.
>> So, Fedora 25 will come with MP3 decoders by default, right? That's
>> pretty nice and should be highlig
On Mon, Nov 14, 2016 at 11:23 AM, Kalev Lember wrote:
> On 11/14/2016 11:54 AM, Igor Gnatenko wrote:
>> Hi,
>>
>> At this point, nothing uses mozjs31, so I'm going to retire it in
>> Rawhide and orphan for F24 / F25. It was used by 0 A.D. (the reason
>> why we packaged it), but nowadays upstream m
On Mon, Nov 14, 2016 at 12:58 PM, Stephen Gallagher wrote:
> On 11/11/2016 11:03 AM, Adam Williamson wrote:
>> On Fri, 2016-11-11 at 08:33 -0500, Stephen Gallagher wrote:
>>> Just to address this specifically, I am referring to Apple's penchant for
>>> stuffing their machines with hardware from ve
>>> On 11/10/2016 09:42 PM, Barry Scott wrote:
>>> In this bug
>>>
>>>https://bugzilla.redhat.com/show_bug.cgi?id=1360797
>>>
>>> It is implied that rpkg has an unspecified problem with GitPython 2.0.
>>>
>>> This is preventing the maintainer from updating to the any GitPython 2
>>> release.
>>
On Mon, Nov 14, 2016 at 1:23 PM, Peter Robinson wrote:
>>>> On 11/10/2016 09:42 PM, Barry Scott wrote:
>>>> In this bug
>>>>
>>>>https://bugzilla.redhat.com/show_bug.cgi?id=1360797
>>>>
>>>> It is implied that rpkg has
On Mon, Nov 14, 2016 at 2:15 PM, Richard W.M. Jones wrote:
> Here are three packages, none of them using %{?_isa} in their spec files:
>
> (a) libvirt
> http://pkgs.fedoraproject.org/cgit/rpms/libvirt.git/tree/libvirt.spec
> (b) libguestfs
> http://pkgs.fedoraproject.org/cgit/rpms/libguestfs.
On Mon, Nov 14, 2016 at 3:37 PM, Pavel Raiskup wrote:
> On Wednesday, September 21, 2016 12:55:48 PM CET Jason L Tibbitts III wrote:
>> First off, the guidelines have:
>> https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies
>>
>> I've been assuming that you're talk
>>> Just to address this specifically, I am referring to Apple's penchant
>>> for
>>> stuffing their machines with hardware from vendors that don't play well
>>> with
>>> open-source (for example, switching to wifi-only devices and shipping
>>> Broadcom
>>> chipsets w
>> > >> Anyone else seeing errors like this?
>> > >>
>> > >> reading sources... [ 27%]
>> > >> api/astropy.modeling.functional_models.Sersic1D reading
>> > >> sources... [ 27%]
>> > >> api/astropy.modeling.functional_models.Sersic2D Sphinx
>> > >> Documentation subprocess failed with return code -1
>
>> No I am not asking for continuous testing. I am asking that if people
>> really care about the hardware support they get in the muck and do
>> just a little of the work in an organized fashion. Put together a Mac
>> SIG that focuses on getting the best experience on the hardware. Send
>> some
On Tue, Nov 22, 2016 at 6:12 AM, Kevin Kofler wrote:
> Dennis Gilmore wrote:
>> koji authentication will be switching to Kerberos. Koji supports multiple
>> authentication mechanisms. Fedora infrastructure has set up a freeipa
>> instance internally that has credential syncing to fas. We are worki
>>> Hi,
>>>
>>> Is anybody working on fixing [1]?
>>>
>>> The exploit is a little impractical in that it only works if you have
>>> not updated any F24 base packages except GStreamer, but we should
>>> still
>>> fix it. I don't see any GStreamer updates in bodhi yet.
>>
>>
>> for gstreamer
>> https
For the release of F25, has nobody run the upgrade path violations
checker
to warn packagers about any downgrades the dist update would perform?
A missing zero day update [only available in updates-testing] for Claws
Mail has hit users. Not great. And I hear there are
>> So we already do pretty much what you outline above. I started the
>> first push to f25-updates on the Friday before the release.
>
> I think, we are talking past each other.
>
> You seem to be referring to "the freeze" in terms of the final release push,
> while I am talking about what you'd pr
>>> On 11/25/2016 05:51 PM, Peter Robinson wrote:
>>>
>>>> So we already do pretty much what you outline above. I started the
>>>> first push to f25-updates on the Friday before the release.
>>>
>>>
>>> I think, we are talking
On Wed, Dec 7, 2016 at 4:59 PM, Michael Catanzaro wrote:
> On Wed, 2016-12-07 at 10:06 -0600, Michael Cronenworth wrote:
>> While we could patch and update our
>> Fedora packages this is a perfect opportunity to retire it.
>
> I just want to add an explicit +1 in support of this proposal. Package
On Thu, Dec 8, 2016 at 4:49 AM, Michael Cronenworth wrote:
> On 12/07/2016 04:29 PM, Peter Robinson wrote:
>>
>> -1 at least for the moment. b
>
>
> Is this due to sugar? Would you accept patches?
One of the reasons, and of course, I think if we want to actively
retire p
On Thu, Dec 8, 2016 at 4:53 AM, Peter Robinson wrote:
> On Thu, Dec 8, 2016 at 4:49 AM, Michael Cronenworth wrote:
>> On 12/07/2016 04:29 PM, Peter Robinson wrote:
>>>
>>> -1 at least for the moment. b
>>
>>
>> Is this due to sugar? Would you accept p
On Tue, Dec 6, 2016 at 8:15 PM, Matthew Miller wrote:
> On Tue, Dec 06, 2016 at 09:00:35AM -0500, Kamil Paral wrote:
>> With my QA hat on, I believe using decimal releases (integers,
>> characters or anything else) is a bad idea. The reason is that people
>> don't remember it. Most people remember
On Mon, Dec 5, 2016 at 2:47 PM, Matthew Miller wrote:
> The stats I get are about a week behind, which means I now have
> information about the first week of the Fedora 25 release. See the
> graph here:
>
> https://mattdm.fedorapeople.org/stats/fedora-os-select-2016-11-22.png
>
> (and please note
On Tue, Dec 6, 2016 at 9:11 AM, Daniel P. Berrange wrote:
> On Mon, Dec 05, 2016 at 06:41:27PM -0700, Chris Murphy wrote:
>> On Mon, Dec 5, 2016 at 5:03 PM, Michael Catanzaro
>> wrote:
>> > On Mon, 2016-12-05 at 16:10 -0500, Matthew Miller wrote:
>> >> It was by design, though — for a while, whe
On Mon, Dec 5, 2016 at 9:26 PM, Matthew Miller wrote:
> On Mon, Dec 05, 2016 at 01:43:58PM -0700, Chris Murphy wrote:
>> I'm not sure it's much harder to do without modularity. Right now
>> Fedora could do a Fedora 26 release without any conventional release
>> media for server and workstation, by
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 Miller
>> wrote:
>>> The stats I get are about a week behind, which means I now have
>>> information a
On Thu, Dec 8, 2016 at 6:59 PM, Matthew Miller wrote:
> On Thu, Dec 08, 2016 at 07:41:13PM +0100, drago01 wrote:
>> Which problem are you trying to solve with those proposals?
>
> From my *other* other mail:
>
> * predictable calendar dates, to help with long-term planning
> * not being on a h
On Thu, Dec 8, 2016 at 8:13 PM, Adam Williamson
wrote:
> On Thu, 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 part
On Thu, Dec 8, 2016 at 8:38 PM, Adam Williamson
wrote:
> On Thu, 2016-12-08 at 13:33 -0700, Chris Murphy wrote:
>> I think that ignores that we're pretty much always slipping, and they
>> aren't in fact 6 month cycles.
>
> Well, since 22 we've got a lot closer to being back to May/November.
> We'v
On 9 Dec 2016 14:02, "Stephen John Smoogen" wrote:
On 8 December 2016 at 21:56, Peter Robinson wrote:
> On Thu, Dec 8, 2016 at 8:13 PM, Adam Williamson
> wrote:
>> On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote:
>>> Trying to make this idea a l
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
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 9, 2016 at 10:58 PM, Matthew Miller
wrote:
> On Fri, Dec 09, 2016 at 10:22:44PM +0000, 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
On Sun, Dec 11, 2016 at 3:10 PM, wrote:
> I would think that they are now allowed as they should work out of the box.
> Maybe we need legal to clarify, then update the guidelines.
I would think it would also depend that the actual content in the
media is redistributable but then that's the case
>> The only way it reduces the risk of releasing a botched update is
>> the
>> the updates somehow get more testing just by staying in the testing
>> channel longer.
>
> ...and actual QA, from the professionals and volunteers on the QA team,
> who are very good at finding bugs pre-release but curre
Hi All,
Just a heads up that xapian 1.4 is headed to rawhide.
Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Hi All,
>>
>> Just a heads up that xapian 1.4 is headed to rawhide.
>>
>> Peter
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>
> I tried to rebuild doxygen - fix
On Thu, Dec 22, 2016 at 10:16 AM, Vít Ondruch wrote:
>
>
> Dne 22.12.2016 v 10:12 Pavel Raiskup napsal(a):
>> On Thursday, December 22, 2016 9:50:12 AM CET Vít Ondruch wrote:
>>
>>> Wouldn't be possible to build noarch packages just on primary arch builders
>>> for example?
>> Those arches are all
>>> On Wed, 21 Dec 2016 17:06:03 +0100
>>> gil wrote:
>>>
from: Task info:
http://koji.fedoraproject.org/koji/taskinfo?taskID=17017344
https://kojipkgs.fedoraproject.org//work/tasks/7345/17017345/root.log
" Error: nothing provides libpython3.6m.so.1.0 needed by
g
On Sun, Dec 25, 2016 at 9:45 AM, Jonathan Underwood
wrote:
>
>
> On 22 Dec 2016 06:12, "Peter Robinson" wrote:
>
> Just a heads up that xapian 1.4 is headed to rawhide.
>
>
> Do you plan to rebuild dependent packages?
Should all be done now.
___
>> >>> The failure yesterday that I was thinking of was:
>> >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=17004112
>> >>>
>> >>> Re-submitting it 4 minutes later passed just fine:
>> >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=17004125
>> >> These builds were ran on different
There was a new build of java-1.8.0-openjdk-aarch32 pushed on Dec 23rd
so maybe there's some regressions there.
P
On Tue, Dec 27, 2016 at 3:46 PM, Orion Poplawski wrote:
> koschei is reporting build failures on arm for vtk now:
>
> CMake Error at /usr/share/cmake/Modules/FindJava.cmake:123 (mess
On Fri, Jan 13, 2017 at 9:03 AM, Igor Gnatenko
wrote:
> Hello,
>
> do we have tracking bug for FTBFS? I remember there was one for F24,
> but can't find something similar for F26.
It's created post mass rebuild with bugs linked for all the FTBFS as a
reasult of the mass rebuild.
_
On Sat, Jan 21, 2017 at 11:57 AM, Kai Engert wrote:
> On Fri, 2017-01-20 at 10:22 -0600, Michael Catanzaro wrote:
>>
>> Please just make sure they all get released in the same Bodhi update to
>> avoid breakage.
>
>
> The combined updates have been submitted to testing:
> F24: https://bodhi.fedorap
On Sat, Jan 21, 2017 at 2:25 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 13:20 +0100, Christian Dersch wrote:
>> > > The combined updates have been submitted to testing:
>> > > F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb320ba18
>> > > F25: https://bodhi.fedoraproject.org/updates
On Sat, Jan 21, 2017 at 3:15 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote:
>> On 01/21/2017 03:44 PM, Christian Dersch wrote:
>> >
>> > Autokarma just means the package will not be pushed automatically, but
>> > karma mechanism is still active. So once your upd
On Sun, Jan 22, 2017 at 1:05 AM, Kevin Kofler wrote:
> Adam Williamson wrote:
>> By the way, this isn't true at all. Most packages can and, these days,
>> are encouraged to ship their own SELinux policies.
>
> This is also a plague because it drags in SELinux dependencies that would
> not otherwis
> Neither of the bluetooth headsets I have here have been working for me
> for a bit, and I finally sat down to dig into it today. Unfortunately,
> I failed to track things down, so I thought I would ask the list for
> more info...
>
> The issue is that either of my headsets work fine when using th
On Mon, Jan 23, 2017 at 8:30 AM, Dave Young wrote:
> On 01/19/17 at 10:24pm, Kevin Fenzi wrote:
>> ok. After a bunch of debugging and digging today it sure looks like the
>> underlying problem was squid operating in smp mode.
>>
>> We switched the squid servers back to non smp mode around 00:00 an
On Tue, Jan 24, 2017 at 11:07 AM, Kaleb Keithley wrote:
> Hi,
>
> Trying to build latest nfs-ganesha––
>
> Yesterday (for me, 02:00 UTC, 24 Jan) I was getting (on both a fedpkg build
> and koji scratch builds):
>DEBUG util.py:435: Error: package pkgconf-pkg-config-1.2.0-1.fc26.ppc64le
> con
901 - 1000 of 1607 matches
Mail list logo
