On Thu, 2017-03-30 at 02:55 +, Fedora compose checker wrote:
> No missing expected images.
>
> Failed openQA tests: 9/107 (x86_64), 1/18 (i386), 1/2 (arm)
>
> New failures (same test did not fail in 26 Alpha 1.5):
>
> ID: 73174 Test: x86_64 Server-dvd-iso server_cockpit_default
> URL: ht
Dear all,
You are kindly invited to the meeting:
Fedora 26 Alpha Go/No-Go Meeting on 2017-03-30 from 17:00:00 to 19:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Before each public release Development, QA and Release Engineering meet to
determine if the release
Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].
At this time the following Container Images are available in the
Fedora R
No missing expected images.
Failed openQA tests: 9/107 (x86_64), 1/18 (i386), 1/2 (arm)
New failures (same test did not fail in 26 Alpha 1.5):
ID: 73174 Test: x86_64 Server-dvd-iso server_cockpit_default
URL: https://openqa.fedoraproject.org/tests/73174
ID: 73214 Test: x86_64 KDE-liv
HI there,
just at the moment I orphaned abakus.
Abakus [0] is still based on qt4. There's an already long open bug [1] about
open work in coordination with upstream to port it to Qt5. I remember found
some patches somewhere (lost link) tor a qt5 port, but do not find them any
more. Further, up
According to the schedule [1], Fedora 26 Candidate Alpha-1.7 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 c
Missing expected images:
Xfce raw-xz armhfp
Failed openQA tests: 12/107 (x86_64), 2/18 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20170328.n.0):
ID: 72865 Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/72865
ID:
Missing expected images:
Server dvd i386
Server boot i386
Failed openQA tests: 6/108 (x86_64), 1/2 (arm)
New failures (same test did not fail in 26-20170328.n.0):
ID: 72968 Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/72968
ID: 73018
On 03/27/2017 11:35 PM, Adam Williamson wrote:
>
> It never used to be like that, it's probably just load as more and more
> stuff is moved to it.
yeah. Note that I mentioned upthread that we had been working on
performance improvements of late. We just rolled out a new version this
morning that
On 29 March 2017 at 17:04, Michael Schwendt wrote:
> It has been discussed several times, has met resistance and lead to
> actions like
> https://fedoraproject.org/wiki/Features/SystemPythonExecutablesUseSyst
> emPython
> but I don't remember any special section in the guidelines about it.
>
Q
On Wed, 2017-03-29 at 15:22 +0200, Jan Sedlak wrote:
> 2017-03-29 4:07 GMT+02:00 Fedora compose checker :
> > Average CPU usage changed from 2.28571429 to 24.55238095
>
> In what units is this? Isn't this like, really high?
It's percentage - the values are read from top. And yeah, seems pretty
hi
On Wed, 29 Mar 2017 14:40:31 +0100, Tom Hughes wrote:
> On 29/03/17 14:16, Ralf Corsepius wrote:
> > On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote:
> >> I would say using env in the shebang line is useful. Particularly for
> >> portability. As a developer, I wouldn't like removing it from my
On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote:
I would say using env in the shebang line is useful. Particularly for
portability. As a developer, I wouldn't like removing it from my programs.
Does it enable running packages unchanged against runtimes packaged as
Software Collections?
Than
Hi!
I'm in Germany and although it doesn't take as much as a minute or half
minute as others stated, it does takes too long. And once it failed to
load a page because it was taking too long.I don't know what it causes
it, it was working nicely last weekend when I checked.
Cheers,Sylvia
On Mon, 20
On 29 March 2017 at 15:17, Nikolai Kondrashov
wrote:
> > Getting rid of using env is much more legacy related things
> Most of them comes from the the time when Solaris and other flavours of
> the Unixes where the dominant Unix on the market.
Well, my concern was mostly
Don't worry about this
On 29 March 2017 at 15:14, Vít Ondruch wrote:
> I can't imagine how you want to convince most of the Ruby developers,
> who are typically using Mac with RVM or rbenv, to accept patch to change
> shebang from "/usr/bin/env ruby" to "/usr/bin/ruby". I suppose the
> situation is similar for Python w
On 03/29/2017 04:52 PM, Tomasz Kloczko wrote:
> On Wed, 2017-03-29 at 12:26 +, Nikolai Kondrashov wrote:
>> I would say using env in the shebang line is useful. Particularly for
>> portability. As a developer, I wouldn't like removing it from my programs.
>
> Portability is not an issue at all
Dne 29.3.2017 v 15:52 Tomasz Kloczko napsal(a):
> On Wed, 2017-03-29 at 12:26 +, Nikolai Kondrashov wrote:
>> I would say using env in the shebang line is useful. Particularly for
>> portability. As a developer, I wouldn't like removing it from my programs.
> Portability is not an issue at al
On Wed, 2017-03-29 at 14:40 +0100, Tom Hughes wrote:
> > FPC repeated discussed this and we decided to ban env, years ago.
>
> AFAIK it was was never made official though - it is still in draft:
>
> https://fedoraproject.org/wiki/Script_Interpreters_(draft)
As well my pointing on using env does
On Wed, 2017-03-29 at 13:23 +0100, Jonathan Wakely wrote:
[..]
> And my point is the code doesn't need fixing. "Fixing" code to stop
> using std::auto_ptr usually means replacing it with std::unique_ptr,
> which will break that code if it's supposed to build with a C++98
> compiler.
As you perfect
On Wed, 2017-03-29 at 12:26 +, Nikolai Kondrashov wrote:
> I would say using env in the shebang line is useful. Particularly for
> portability. As a developer, I wouldn't like removing it from my programs.
Portability is not an issue at all here in this exact discussed case because
distributi
On 29/03/17 14:16, Ralf Corsepius wrote:
On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote:
I would say using env in the shebang line is useful. Particularly for
portability. As a developer, I wouldn't like removing it from my
programs.
FPC repeated discussed this and we decided to ban env, yea
On 03/29/2017 04:16 PM, Ralf Corsepius wrote:
> On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote:
>> I would say using env in the shebang line is useful. Particularly for
>> portability. As a developer, I wouldn't like removing it from my programs.
>
> FPC repeated discussed this and we decided to
2017-03-29 4:07 GMT+02:00 Fedora compose checker :
> Average CPU usage changed from 2.28571429 to 24.55238095
In what units is this? Isn't this like, really high?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to dev
On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote:
I would say using env in the shebang line is useful. Particularly for
portability. As a developer, I wouldn't like removing it from my programs.
FPC repeated discussed this and we decided to ban env, years ago.
Moreover, if your PATH is compro
https://bugzilla.redhat.com/show_bug.cgi?id=1435189
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |MODIFIED
CC|
On Tue, Mar 28, 2017 at 12:09:47AM +0200, Kevin Kofler wrote:
> > Kevin, I genuinely don't understand your worry here. If Fedora had a
> > long per-release lifetime already, and we were talking about shortening
> > it, that'd be one thing, but I think the most common situation will
> > actually be
Hi,
Le 29/03/2017 à 14:08, Tomasz Kloczko a écrit :
>
> There are several issues with /usr/bin/env dependencies and all those issues
> are related to scripts which in script preamble are using
> "#!/usr/bin/env ":
For php tools (at least the ones I own), this is a deliberate packaging
choice, w
I would say using env in the shebang line is useful. Particularly for
portability. As a developer, I wouldn't like removing it from my programs.
Moreover, if your PATH is compromised, you're most likely screwed.
I understand, that env use in scripts makes is inconvenient in some cases,
but I thin
On 29/03/17 12:09 +0100, Tomasz Kloczko wrote:
For some reason you email landed in my spam folder :)
On Wed, 2017-03-29 at 10:15 +0100, Jonathan Wakely wrote:
On 19/03/17 03:33 +, Tomasz Kłoczko wrote:
> Started cleaning parted.spec and found method *much* more often used.
>
> [tkloczko@dom
There are several issues with /usr/bin/env dependencies and all those issues
are related to scripts which in script preamble are using
"#!/usr/bin/env ":
- if some scrip is using env rpm package build procedure find requires scripts
are not able to recognize that script is
script. It switches
On Wednesday, March 29, 2017 12:09:14 Tomasz Kloczko wrote:
> What I'm trying to tell is that as long
> as suppressing such warnings is hard coded in spec files it
> decreases probability of fixing the code.
Because you are trying to use wrong tools to capture compiler warnings from
Fedora packag
Rex Dieter wrote:
> Rex Dieter wrote:
>
>> Mostly fyi/heads-up,
>>
>> kde-sig members imported Qt 5.8 into git over the weekend (kudos to
>> heliocastro for initial packaging/copr and kkofler for merging import),
>> and
>> bootstrap builds are under way. I'm hoping to have the whole stack done
For some reason you email landed in my spam folder :)
On Wed, 2017-03-29 at 10:15 +0100, Jonathan Wakely wrote:
> On 19/03/17 03:33 +, Tomasz Kłoczko wrote:
> > Started cleaning parted.spec and found method *much* more often used.
> >
> > [tkloczko@domek SPECS.fedora]$ grep CFLAGS * | grep --
Does anyone have suggestions on troubleshooting an issue with
apparently intermittent wifi on Fedora after upgrade to 25? The
machine is working okay in its location on windows and was okay on
F22, and other devices are alright on the access point. The
networkmanager status (KDE) doesn't show the c
On 19/03/17 03:33 +, Tomasz Kłoczko wrote:
Started cleaning parted.spec and found method *much* more often used.
[tkloczko@domek SPECS.fedora]$ grep CFLAGS * | grep -- -Wno
alex4.spec: CFLAGS="$RPM_OPT_FLAGS *-Wno*-deprecated-declarations"
There's nothing wrong with this option. Many C++
> Am Tue, 28 Mar 2017 13:19:29 -
> schrieb "Martin Gansser"
>
> The attached patch fixes the issue and should work with local and
> global installation.
> It first checks for the local path and uses it, if it exists, otherwise
> uses the global path.
> It does not really look good, but I tri
ppisar changed perl-sig's 'watchbugzilla' permission on
perl-Dist-Zilla-Plugin-ModuleBuildTiny (master) to 'Approved'
https://admin.fedoraproject.org/pkgdb/package/perl-Dist-Zilla-Plugin-ModuleBuildTiny/
___
perl-devel mailing list -- perl-de...
38 matches
Mail list logo
