No missing expected images.
Failed openQA tests: 1/137 (x86_64), 3/23 (i386), 1/2 (arm)
ID: 213956 Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/213956
ID: 213957 Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject
Dne 28.3.2018 v 19:55 Pierre-Yves Chibon napsal(a):
> On Wed, Mar 28, 2018 at 07:34:51PM +0200, Vít Ondruch wrote:
>
>> And please rename this thread to "Gating packages in Fedora", because
>> Rawhide should be just Fedora.
> You do realize that there is already gating in place for stable release
Dear all,
You are kindly invited to the meeting:
F28 Beta release Go/No-Go Meeting - 2nd round on 2018-03-29 from 17:00:00 to
19:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Source: https://apps.fedoraproject.org/calendar/meeting/9017/
_
On Thu, 2018-03-29 at 02:48 +, rawh...@fedoraproject.org wrote:
> According to the schedule [1], Fedora 28 Candidate Beta-1.3 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.or
According to the schedule [1], Fedora 28 Candidate Beta-1.3 is now
available for testing. Please help us complete all the validation
testing! For more information on release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the cu
Dropping packagekitd and gnome-software starting up on lives has
helped quite a bit.
Netinstall has zram.service enabled by default, so a zram swap device
is automatically created during boot. This service exists on the live,
but is disabled by default. If there could be a
ConditionKernelCommandLi
On Fri, Mar 09, 2018 at 10:20:12AM +0100, Pierre-Yves Chibon wrote:
> On Thu, Mar 08, 2018 at 01:00:32PM -0500, Randy Barlow wrote:
> > I would like to kick off a general discussion about how we might gate
> > packages in Rawhide. I think it would be nice to get something in place
> > for the Fedor
On Wed, Mar 28, 2018 at 2:00 PM, Christopher wrote:
> On Wed, Mar 28, 2018 at 3:43 PM Chris Murphy
> wrote:
>>
>> On Wed, Mar 28, 2018 at 12:58 PM, Christopher
>> wrote:
>> > So, I've been seeing this problem recently where every time I update the
>> > Fedora kernel (currently F27), my grub conf
Tom Hughes wrote:
> On 28/03/18 15:47, Peter Robinson wrote:
>
>> Personally I think the better question is why popplar has to break
>> it's ABI so often? I mean it's not like the PDF spec is evolving that
>> quickly, why is it so terrible and unstable that is has to change so
>> much? I mean I'm
On Wed, 2018-03-28 at 09:18 -0700, Adam Williamson wrote:
> On Wed, 2018-03-28 at 12:07 +, rawh...@fedoraproject.org wrote:
> > According to the schedule [1], Fedora 28 Candidate Beta-1.2 is now
> > available for testing. Please help us complete all the validation
> > testing! For more informat
On Wed, Mar 28, 2018 at 3:43 PM Chris Murphy
wrote:
> On Wed, Mar 28, 2018 at 12:58 PM, Christopher
> wrote:
> > So, I've been seeing this problem recently where every time I update the
> > Fedora kernel (currently F27), my grub configuration gets mangled.
> >
> > I have tuned installed, so it h
I'm not sure if this is a gcc issue or not, but asymptote segfaults in
some situations (which is causing the FTBFS, since it bootstraps itself
with itself). I filed a bug upstream with the crash and gdb backtrace:
https://github.com/vectorgraphics/asymptote/issues/62
If any gcc c++ people could l
On Wed, Mar 28, 2018 at 12:58 PM, Christopher
wrote:
> So, I've been seeing this problem recently where every time I update the
> Fedora kernel (currently F27), my grub configuration gets mangled.
>
> I have tuned installed, so it has installed /etc/grub.d/00_tuned, which
> executes /etc/tuned/boo
So, I've been seeing this problem recently where every time I update the
Fedora kernel (currently F27), my grub configuration gets mangled.
I have tuned installed, so it has installed /etc/grub.d/00_tuned, which
executes /etc/tuned/bootcmdline, which in turn spits out when
grub2-mkconfig is run.
I've just discovered that gdl appears to be segfaulting a lot now deep in the
antlr c++ generated parser code with the switch to gcc 8.
A bugzilla report would be nice. Run under gdb, report register contents
and the instruction stream surrounding $pc, etc. Also any clues
about the correspond
On Wed, Mar 28, 2018 at 09:58:13AM +0200, Florian Weimer wrote:
> On 03/28/2018 06:10 AM, Kevin Fenzi wrote:
> > So, is this hardware limitation something that is likely to affect other
> > packages? Is there something we could look for in how they consume
> > atomic types to tell? I would hate for
On 03/28/2018 04:46 PM, Stephen John Smoogen wrote:
Just to be clear, when other 32 bit architectures don't support it..
if this code was attempted to be compiled on arm32 the compiler
complains and errors?
Generic 32-bit ARM does not have any 64-bit atomics at all. This is
what I meant: You
On 03/28/2018 12:46 PM, Vít Ondruch wrote:
> And if you can do chain build in Rawhide, I can't see any reason why it
> should not be possible for stable branch.
It's more that it's tricky and not that it's impossible, because of the
Koji buildroot. Packages built into Rawhide become part of the bu
On Wed, Mar 28, 2018 at 07:34:51PM +0200, Vít Ondruch wrote:
>
>
> Dne 28.3.2018 v 19:06 Pierre-Yves Chibon napsal(a):
> > On Wed, Mar 28, 2018 at 06:46:50PM +0200, Vít Ondruch wrote:
> >>Why are you stressing MultiplePkgs vs single pkgs. Single pgk process is
> >>just subcase of multiple
Dne 28.3.2018 v 19:06 Pierre-Yves Chibon napsal(a):
> On Wed, Mar 28, 2018 at 06:46:50PM +0200, Vít Ondruch wrote:
>>Why are you stressing MultiplePkgs vs single pkgs. Single pgk process is
>>just subcase of multiplepkgs process.
> And because it is just a subcase, it can be simplified.
>
On Wed, Mar 28, 2018 at 06:46:50PM +0200, Vít Ondruch wrote:
>Why are you stressing MultiplePkgs vs single pkgs. Single pgk process is
>just subcase of multiplepkgs process.
And because it is just a subcase, it can be simplified.
>And if you can do chain build in Rawhide, I can't see
Why are you stressing MultiplePkgs vs single pkgs. Single pgk process is
just subcase of multiplepkgs process.
And if you can do chain build in Rawhide, I can't see any reason why it
should not be possible for stable branch.
IOW the process for Rawhide should be as close to stable version as
poss
No missing expected images.
Failed openQA tests: 6/137 (x86_64), 3/23 (i386), 1/2 (arm)
ID: 213464 Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/213464
ID: 213465 Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject
So, is this hardware limitation something that is likely to affect other
packages? Is there something we could look for in how they consume
atomic types to tell? I would hate for us to ship something else that is
subject to this problem.
<>
The way I read some of the comments on the bugs in
On Wed, 2018-03-28 at 12:07 +, rawh...@fedoraproject.org wrote:
> According to the schedule [1], Fedora 28 Candidate Beta-1.2 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.or
>>> So, is this hardware limitation something that is likely to affect other
>>> packages? Is there something we could look for in how they consume
>>> atomic types to tell? I would hate for us to ship something else that is
>>> subject to this problem.
>>
>>
>> There is lots of fingerpointing, but
On 28/03/18 15:47, Peter Robinson wrote:
Personally I think the better question is why popplar has to break
it's ABI so often? I mean it's not like the PDF spec is evolving that
quickly, why is it so terrible and unstable that is has to change so
much? I mean I'm sure I've seen java script imple
On Sat, Mar 24, 2018 at 9:07 AM, Tomasz Kłoczko
wrote:
> On 24 March 2018 at 03:14, Kevin Fenzi wrote:
> [..]
>>> BTW In situations like this is possible to observe how really bad idea
>>> was building ALL Fedora +5.6k texlive* packages from single sec file.
>>
>> Except that is no longer the cas
On 28 March 2018 at 03:58, Florian Weimer wrote:
> On 03/28/2018 06:10 AM, Kevin Fenzi wrote:
>>
>> So, is this hardware limitation something that is likely to affect other
>> packages? Is there something we could look for in how they consume
>> atomic types to tell? I would hate for us to ship so
On Wed, Mar 28, 2018 at 01:51:26PM +, Fabio Valentini wrote:
>On Wed, Mar 28, 2018, 15:47 Pierre-Yves Chibon
>wrote:
>
> On Wed, Mar 28, 2018 at 01:39:34PM +, Fabio Valentini wrote:
> >Â Â One example where running tests against a single-package update
> would be
I've just discovered that gdl appears to be segfaulting a lot now deep
in the antlr c++ generated parser code with the switch to gcc 8. Has
anyone else run into similar issues?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX:
On Wed, Mar 28, 2018, 15:47 Pierre-Yves Chibon wrote:
> On Wed, Mar 28, 2018 at 01:39:34PM +, Fabio Valentini wrote:
> >One example where running tests against a single-package update would
> be
> >nice IMO would be for toolchain and base packages, for example,
> updates to
> >ann
On Wed, Mar 28, 2018 at 01:39:34PM +, Fabio Valentini wrote:
>One example where running tests against a single-package update would be
>nice IMO would be for toolchain and base packages, for example, updates to
>annobin or binutils, where the answer to "Does this update break
>c
On 03/24/2018 05:07 AM, Tomasz Kłoczko wrote:
> Rhetorical question: is it any and/or at least one good reason why
> those ~180 texlive-base packages using ~350 source tar balls must be
> (re)built always together?
Legitimate answer: Those are the CTAN TeX components that either include
(or are en
Hi Fedorans,
If your package uses code under the Eclipse Public License, please take
a moment and change the license tag to reflect the version. There are
now two versions of the EPL, 1.0 and 2.0. Both are permitted in Fedora,
neither is GPL compatible.
You do not need to push an update solely to
On Wed, Mar 28, 2018, 14:51 Pierre-Yves Chibon wrote:
> On Wed, Mar 28, 2018 at 11:16:35AM +, Fabio Valentini wrote:
> >On Wed, Mar 28, 2018, 12:53 Pierre-Yves Chibon
> >wrote:
> > Based on the outcome of this discussion, I started trying to draw
> how
> > the
> > proc
On Wed, Mar 28, 2018 at 11:16:35AM +, Fabio Valentini wrote:
>On Wed, Mar 28, 2018, 12:53 Pierre-Yves Chibon
>wrote:
> Based on the outcome of this discussion, I started trying to draw how
> the
> process to update a package in rawhide would look like with rawhide
>
On 03/24/2018 12:30 AM, Adam Williamson wrote:
poppler was updated from 0.62.0-2 to 0.63.0-1 in Rawhide on 2018-03-23.
This update bumped the soname from libpoppler.so.73 to libpoppler.so.74.
This soname bump was not announced, as it is supposed to be.
Hi,
I'm sorry about that. I'll do the ann
According to the schedule [1], Fedora 28 Candidate Beta-1.2 is now
available for testing. Please help us complete all the validation
testing! For more information on release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the cu
On Wed, Mar 28, 2018, 12:53 Pierre-Yves Chibon wrote:
> Good Morning Everyone,
>
Good morning!
> Based on the outcome of this discussion, I started trying to draw how the
> process to update a package in rawhide would look like with rawhide being
> gated
> on tests.
>
> There are currently two
I've built modem-manager-gui for F28, F27 and F26 and submitted the updates to
bodhi.
Thank you, Rex.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Good Morning Everyone,
Based on the outcome of this discussion, I started trying to draw how the
process to update a package in rawhide would look like with rawhide being gated
on tests.
There are currently two proposals:
- one that does not involve bodhi updates
- one that does
Both proposals h
= Proposed Self Contained Change: Ansible python3 default =
https://fedoraproject.org/wiki/Changes/Ansible_python3_default
Owner(s):
* Kevin Fenzi
Ansible started out as a python2 only application, but in recent years
a large amount of work has gone into porting things to python3. Last
year
On 03/28/2018 06:10 AM, Kevin Fenzi wrote:
So, is this hardware limitation something that is likely to affect other
packages? Is there something we could look for in how they consume
atomic types to tell? I would hate for us to ship something else that is
subject to this problem.
There is lots
No missing expected images.
Passed openQA tests: 2/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
45 matches
Mail list logo
