Hi folks! I'm proposing we cancel the QA meeting tomorrow (today?),
as no-one seemed to have anything urgent for the agenda in response to
my other mail. So, I get to sleep in!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
On Sun, Aug 5, 2018 at 10:44 PM, Asavaseri Natnaree
wrote:
> Dear contributors,
>
> I am happy to announce that we are ready to release preliminary results of
> the "Developer Perception to Microsoft's acquisition of GitHub" survey. These
> results can be accessed at "
>
Dear contributors,
I am happy to announce that we are ready to release preliminary results of the
"Developer Perception to Microsoft's acquisition of GitHub" survey. These
results can be accessed at "
https://naist-se.github.io/study-of-microsofts-github-acquisition/;. Again
thank you for
https://fedorapeople.org/groups/389ds/ci/nightly/2018/08/06/report-389-ds-base-1.4.0.13-20180805gitba8f57d.fc28.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
https://bugzilla.redhat.com/show_bug.cgi?id=1612612
Bug ID: 1612612
Summary: perl-Protocol-HTTP2-1.09 is available
Product: Fedora
Version: rawhide
Component: perl-Protocol-HTTP2
Keywords: FutureFeature, Triaged
Assignee:
On Sat, Aug 4, 2018 at 9:48 PM Jerry James wrote:
> I've accumulated another set of package updates for the
> sagemath/Macaulay2 set of packages. I would like to build these in
> Rawhide in about a week. Here are the proposed changes. Please let
> me know of any objections. I believe I have
On Tue, Jul 31, 2018 at 12:19 PM, Miro Hrončok wrote:
> On 31.7.2018 18:15, Jun Aruga wrote:
>>
>> 9.0.x -> 10.0.x then 18.0?
>>
>>> https://github.com/pypa/pip/blob/master/NEWS.rst
>>> Switch to a Calendar based versioning scheme.
>>
>>
>> Oh they changed the versioning rule.
>
>
> See also
>
On 08/05/2018 01:13 PM, Florian Weimer wrote:
On 08/05/2018 09:48 PM, Samuel Sieb wrote:
What am I missing here? Why can't this be put in RPM macros? Then
when the situation changes in the future, there's only one place to
change.
There already is such a macro, %{valgrind_arches}, but it
On 5.8.2018 23:53, Nico Kadel-Garcia wrote:
On Tue, Jul 31, 2018 at 12:19 PM, Miro Hrončok wrote:
On 31.7.2018 18:15, Jun Aruga wrote:
9.0.x -> 10.0.x then 18.0?
https://github.com/pypa/pip/blob/master/NEWS.rst
Switch to a Calendar based versioning scheme.
Oh they changed the
> On Tue, Jul 31, 2018 at 12:19 PM, Miro Hrončok wrote:
>> On 31.7.2018 18:15, Jun Aruga wrote:
>>
>> 9.0.x -> 10.0.x then 18.0?
>>
>>> https://github.com/pypa/pip/blob/master/NEWS.rst
>>> Switch to a Calendar based versioning scheme.
>>
>>
>> Oh they changed the versioning rule.
>
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=1603528
Emmanuel Seyman changed:
What|Removed |Added
Status|NEW |ASSIGNED
On Sun, 2018-08-05 at 22:13 +0200, Florian Weimer wrote:
> On 08/05/2018 09:48 PM, Samuel Sieb wrote:
> > What am I missing here? Why can't this be put in RPM macros? Then when
> > the situation changes in the future, there's only one place to change.
>
> There already is such a macro,
On 08/05/2018 09:48 PM, Samuel Sieb wrote:
What am I missing here? Why can't this be put in RPM macros? Then when
the situation changes in the future, there's only one place to change.
There already is such a macro, %{valgrind_arches}, but it may not
accurately reflect the suitability of
What am I missing here? Why can't this be put in RPM macros? Then when
the situation changes in the future, there's only one place to change.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Try
...
%check
%ifarch ppc64 ppc64p7
exit 0
%endif
...
My comments apply to the rest of what you appear to be proposing everywhere.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Jul 30, 2018, at 10:42 AM, Andrew Lutomirski wrote:
On Jul 27, 2018, at 9:58 AM, Owen Taylor wrote:
On Fri, Jul 27, 2018 at 9:44 AM, Florian Weimer wrote:
> On 07/27/2018 03:33 PM, John Reiser wrote:The key principle is that
> sizeof(foo) must be the stride of an array of foo,
>
> and
I don't think so
On Sun, Aug 5, 2018, 11:43 AM Julien Enselme wrote:
> @Robert Just checking to know how things are moving on. Were you added
> to the packager group?
> --
> Julien Enselme
> http://www.jujens.eu/
>
> On Tue, 2018-07-31 at 15:25 -0400, Robert Brown wrote:
> > Got it. Thanks. I'm
On 08/05/2018 04:36 PM, Jeff Johnson wrote:
Your 14 line example will suffer a similar fate if valgrind is fixed to run on
ppc64, or ppc64 aliases start to proliferate.
But in general, valgrind works on ppc64. Only the package-specific test
fails there.
Florian
@Robert Just checking to know how things are moving on. Were you added
to the packager group?
--
Julien Enselme
http://www.jujens.eu/
On Tue, 2018-07-31 at 15:25 -0400, Robert Brown wrote:
> Got it. Thanks. I'm not sure what to do at this point.
>
> On Tue, Jul 31, 2018, 3:18 PM Miro Hrončok
>
Yuck.
So you are recommending using 14 lines (with comments) of spec file goop that
uses 2 %ifarch build section tests in order to set/unset a macro.
There's further baggage in spec files needed to add a BR, pass an option to
configure, add libraries to link, etc
You are in the wrong
On 08/05/2018 12:38 AM, Christian Dersch wrote:
> Hi,
>
> awesome! The themes are a seperate point, yes. Please note that libfm-qt
> released a bugfix 0.13.1. In any case, your work is fine so I'll give
> you access to lxqt-sig FAS group, which means you'll have commit access
> to the LXQt
W dniu 3.08.2018 o 17:58 Neal Gompa pisze:
> On Fri, Aug 3, 2018 at 11:27 AM Athos Ribeiro wrote:
> >
> > On Fri, Aug 03, 2018 at 09:18:29AM -0400, Zachary Snyder wrote:
> > > I will be interested in joining the sig! Frequent GO user and Fedora is my
> > > daily driver. I will not be at flock
On Sun, 05 Aug 2018 14:47:06 +0200, Andrey Ponomarenko wrote:
> I've just created Fedora package for hw-probe. See
> https://github.com/linuxhw/hw-probe/blob/master/INSTALL.md#install-on-fedora.
Installing a package out of repository for its maintenance is not great.
I tried to find a repository
03.03.2018, 10:08, "Andrey Ponomarenko" :
> Hi there!
>
> Good news for all interested in hardware compatibility and reliability.
>
> I've started a new project to estimate reliability of hard drives and SSD in
> real-life conditions based on the SMART data reports collected by Linux users
> in
On Sun, 05 Aug 2018 13:39:58 +0200, Charalampos Stratakis wrote:
> Here we are referring to the python2-debug or python3-debug builds, which
> are just extra python builds that are compiled with the --with-pydebug flag
Not just --with-pydebug:
- Original Message -
> From: "Troy Curtis Jr"
> To: "Development discussions related to Fedora"
>
> Cc: "Fedora Python SIG"
> Sent: Sunday, August 5, 2018 3:44:39 AM
> Subject: Re: Why are we shipping debug builds of pythons?
>
>
>
> On Sat, Aug 4, 2018 at 5:16 PM Miro Hrončok <
On 5.8.2018 03:20, Sérgio Basto wrote:
On Sat, 2018-08-04 at 22:25 +0200, Miro Hrončok wrote:
Hi,
an interesting discussion came up in the Python Maint team recently,
about not shipping python3-debug and python2-debug.
On the Chesterton's fence principle [0], I'd would like to know why
are
we
On 5.8.2018 03:20, Sérgio Basto wrote:
On Sat, 2018-08-04 at 22:25 +0200, Miro Hrončok wrote:
Hi,
an interesting discussion came up in the Python Maint team recently,
about not shipping python3-debug and python2-debug.
On the Chesterton's fence principle [0], I'd would like to know why
are
we
Hi all.
'libsbw' soname will change from 2.11 to 2.12
Just 'COPASI' will need a rebuild, probably.
Regards.
--
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x5E212EE1D35568BE
GPG key server: https://keys.fedoraproject.org/
signature.asc
Description:
29 matches
Mail list logo
