Hello,
do we have tracking bug for FTBFS? I remember there was one for F24,
but can't find something similar for F26.
--
-Igor Gnatenko
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproje
> On Thu, Jan 12, 2017 at 1:11 PM, Chris Murphy
> wrote:
> >If you
> > pick Server or Cloud Edition using Everything netinstall, you get ext4
> > on LVM with a massive /home volume rather unsuitable for servers, and
> > no free space in the VG for docker-storage-setup to configure for
> > itself.
Dne 13.1.2017 v 10:03 Igor Gnatenko napsal(a):
> Hello,
>
> do we have tracking bug for FTBFS? I remember there was one for F24,
> but can't find something similar for F26.
If I am not mistaken, such tracking bug is typically created after mass
rebuild, which have not happened yet.
Vít
Dne 12.1.2017 v 20:48 Jan Kurik napsal(a):
> [1] https://admin.fedoraproject.org/voting/vote/council-january-2017
> [2] https://admin.fedoraproject.org/voting/vote/famsco-jauary-2017
> [3] https://admin.fedoraproject.org/voting/vote/fesco-january-2017
These links are behaving really strange. Whe
On Fri, 13 Jan 2017 12:27:31 +0100
Vít Ondruch wrote:
>
>
> Dne 12.1.2017 v 20:48 Jan Kurik napsal(a):
> > [1] https://admin.fedoraproject.org/voting/vote/council-january-2017
> > [2] https://admin.fedoraproject.org/voting/vote/famsco-jauary-2017
> > [3] https://admin.fedoraproject.org/voting/v
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.
_
Hi,
I have two packages up for review that could use some attention please:
https://bugzilla.redhat.com/show_bug.cgi?id=1411875
and
https://bugzilla.redhat.com/show_bug.cgi?id=1411947
Thanks,
--
Kaleb
___
devel mailing list -- devel@lists.fedorapr
Hi everybody,
The sidetag with Ruby 2.4 and all the rebuilt packages is undergoing
merge into F26 right now [1]. Since the update of Ruby involved soname
bump, we managed to rebuild most of the depending packages. But there is
still about 10 packages which are broken for various reasons (you can
s
Hello,
Readline-7.0 was released few months ago and I have rebased it in rawhide to
version 7.0. I have created a compatibility package compat-readline6 to avoid
breaking any existing applications.
Update to readline-7.0 caused a build failure with gdb that was fixed by this
commit [1].
I am
On 01/11/2017 10:52 AM, Adam Jackson wrote:
On a benchmark that doesn't reflect real usage very well, but sure.
Can you drill down on this a bit? Which subtests get most worse?
Unfortunately the state of benchmarking in Linux is extremely poor. I'm not here to
discuss the non-existent ecosyste
On 01/12/2017 06:42 AM, Dominik 'Rathann' Mierzejewski wrote:
Which package contains this benchmark? I can't find it in Fedora repos.
GtkPerf was retired in Fedora a few versions ago. I should revive it and update it
to use Gtk3 and include "real-world" cases, but my time is limited. :(
The
Hi,
On 01/12/2017 11:24 PM, Nicolas Chauvet wrote:
2017-01-12 19:04 GMT+01:00 Hans de Goede :
Hi All,
I've just submitted a pkg review request for libglvnd:
https://bugzilla.redhat.com/show_bug.cgi?id=1412764
This is the last building block needed to allow full
parallel installation of the n
Easy access to debug information is very well done in Fedora, and is one
of its most empowering features. It's very easy to trace problems: 'gdb
program' even prints out the 'dnf debuginfo-install' command required to
load symbol tables and source for everything on the system. Thanks to
that, w
On Fri, Jan 13, 2017 at 09:51:32AM -0600, Michael Cronenworth wrote:
> Unfortunately the state of benchmarking in Linux is extremely poor.
> I'm not here to discuss the non-existent ecosystem of performance
> testing, but I appreciate that you are willing to look at the test
> results.
Is the stuf
On 01/13/2017 10:51 AM, Michael Cronenworth wrote:
On 01/11/2017 10:52 AM, Adam Jackson wrote:
On a benchmark that doesn't reflect real usage very well, but sure.
Can you drill down on this a bit? Which subtests get most worse?
I have compiled the results into a spreadsheet. There is not one
su
On Thu, 12 Jan 2017 21:26:03 -0800
Adam Williamson wrote:
> On Sat, 2017-01-07 at 13:00 +0100, Igor Gnatenko wrote:
> > python-gensim
>
> Our version of this is very old. The current upstream version looks
> closer to being buildable, but requires the 'smart_open' library,
> which isn't packag
Przemek Klosowski:
> Easy access to debug information is very well done in Fedora, and is
> one of its most empowering features. It's very easy to trace
...
> Once the debuginfo is installed, however, we have a little bit of a
> stalemate, because the regular updates do not update the debuginfo
> f
On 01/13/2017 10:19 AM, Matthew Miller wrote:
Is the stuff from Phoronix's openbenchmarking.org helpful at all?
http://openbenchmarking.org/suites/pts
It does not implement any benchmarks itself and relies on the same tests that are
not accepted by most people you show the results. It only pro
Doh I missed this. This is now approved due to "bootstrapping issue". So the
way to use "old" pkgconfig is (in case of FTBFS)?
Pavel
On Thursday, January 5, 2017 11:53:38 AM CET Owen Taylor wrote:
> On Wed, 2017-01-04 at 09:20 +0100, Jan Kurik wrote:
> > = System Wide Change: pkgconf as system
On 01/13/2017 11:30 AM, Michael Mraka wrote:
Przemek Klosowski:
Easy access to debug information is very well done in Fedora, and is
one of its most empowering features. It's very easy to trace
...
Once the debuginfo is installed, however, we have a little bit of a
stalemate, because the regul
On 01/13/2017 12:03 PM, Przemek Klosowski wrote:
> On 01/13/2017 11:30 AM, Michael Mraka wrote:
>> Przemek Klosowski:
>>> Easy access to debug information is very well done in Fedora, and is
>>> one of its most empowering features. It's very easy to trace
>> ...
>>> Once the debuginfo is installed,
===
#fedora-meeting: FESCO (2017-01-13)
===
Meeting started by dgilmore at 16:06:54 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2017-01-13/fesco.
2017-01-13-16.06.log.html
.
Meeting summary
On Friday, January 13, 2017 5:54:41 PM CET Pavel Raiskup wrote:
> Doh I missed this. This is now approved due to "bootstrapping issue". So the
> way to use "old" pkgconfig is (in case of FTBFS)?
Reading again the proposal, there's compatibility layer -- but the old
implementation nowhere (Obsole
2017-01-13 16:56 GMT+01:00 Hans de Goede :
> Hi,
>
> On 01/12/2017 11:24 PM, Nicolas Chauvet wrote:
>>
>> 2017-01-12 19:04 GMT+01:00 Hans de Goede :
>>>
>>> Hi All,
>>>
>>> I've just submitted a pkg review request for libglvnd:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1412764
>>>
>>> Thi
On Fri, 2017-01-13 at 10:30 -0500, Siteshwar Vashisht wrote:
> Hello,
>
> Readline-7.0 was released few months ago and I have rebased it in
> rawhide to version 7.0. I have created a compatibility package
> compat-readline6 to avoid breaking any existing applications.
>
> Update to readline-7.0 c
On 01/13/2017 12:16 PM, Stephen Gallagher wrote:
On 01/13/2017 12:03 PM, Przemek Klosowski wrote:
On 01/13/2017 11:30 AM, Michael Mraka wrote:
/etc/dnf/plugins/debuginfo-install.conf
..
autoupdate
A boolean option which controls updates of debuginfo packages. If
options is enabled an
On Fri, 13 Jan 2017 18:16:18 +0100, Stephen Gallagher wrote:
> Probably because debuginfo files are very large and you might not want to
> waste
> bandwidth keeping them updated. (Just guessing here)
Also the repos are commonly out of sync so some packages have N+1 binary rpm
while other packages
On Fri, 2017-01-13 at 11:10 -0500, Przemek Klosowski wrote:
> Once the debuginfo is installed, however, we have a little bit of a
> stalemate, because the regular updates do not update the debuginfo
> files, so the symbols and sources get out of synch with the actual
> installed software. It's not
On Fri, Jan 13, 2017 at 12:20 PM, Pavel Raiskup wrote:
> On Friday, January 13, 2017 5:54:41 PM CET Pavel Raiskup wrote:
>> Doh I missed this. This is now approved due to "bootstrapping issue". So
>> the
>> way to use "old" pkgconfig is (in case of FTBFS)?
>
> Reading again the proposal, there'
On 01/13/2017 12:43 PM, Jan Kratochvil wrote:
Also the repos are commonly out of sync so some packages have N+1 binary rpm
while other packages have N+1 debuginfo rpm.
I think it's reasonable to expect the 'debuginfo-install' plugin to keep
them in synch by NOT installing the debuginfo N+1 with
On Fri, 13 Jan 2017 19:26:16 +0100, Przemek Klosowski wrote:
> Are you saying that currently it updates them completely independently?
Yes.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
On Wed, 2017-01-11 at 09:54 -0500, Neal Gompa wrote:
> On Wed, Jan 11, 2017 at 9:53 AM, Mark Wielaard wrote:
> > Shall we work on a separate change proposal (on top of this one) that
> > introduces debugsource and debuginfo subpackages? I think that could
> > still make it for F26. But it would be
On Fri, Jan 13, 2017 at 1:38 PM, Mark Wielaard wrote:
> On Wed, 2017-01-11 at 09:54 -0500, Neal Gompa wrote:
>> On Wed, Jan 11, 2017 at 9:53 AM, Mark Wielaard wrote:
>> > Shall we work on a separate change proposal (on top of this one) that
>> > introduces debugsource and debuginfo subpackages? I
On 01/10/2017 08:16 AM, Laura Abbott wrote:
> On 12/12/2016 09:14 AM, Laura Abbott wrote:
>> Hi,
>>
>> Kernel 4.9 was officially released yesterday, December 11. This kernel is
>> being built for rawhide today. The plan for bringing this kernel into
>> F24/F25 is going to follow roughly the same s
Here is an attempt at building YafaRay using scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=17274673
An issue is somehow OpenCV will not meet a requirement due to this error
below:
-- Found opencv, version 3.1.0
CMake Error at CMakeModules/FindOpenCV.cmake:120 (string):
On Tue, 2017-01-10 at 15:22 +0100, Hans de Goede wrote:
> Hi,
>
> A while back Debian has switched to using the modesetting Xorg driver
> rather then the intel Xorg driver for Intel GPUs.
>
> There are several good reasons for this, rather then repeating them
> I'm just going to point to the Debi
36 matches
Mail list logo
