ngine and/or wing closest to you, that would help. ;)
>
> # openQA
So here's the good news - releng did the first 24 Branched pungi4
compose, and it ran, and the openQA tests ran! Here's the bad news:
they all failed. :)
https://openqa.fedoraproject.org/tests/overview?distri=fed
> "DJ" == Dave Johansen writes:
DJ> I think the confusion comes from the fact that for several releases
DJ> we heard "get ready because Python 3 is going to be the default" and
DJ> then all of the sudden that just stopped.
In that case, the issue is simply the definition of "default" and
per
On Wed, 2016-02-24 at 13:23 +0100, Peter Lemenkov wrote:
> Hello All!
> I'm going to upgrade libcue. Unfortunately this requires a soname
> bump. Fortunately only recompilation is necessary.
It works better if you plan this a bit *ahead of time* and actually
plan for the rebuilds to happen, as opp
On Wed, Feb 24, 2016 at 3:08 PM, Jason L Tibbitts III
wrote:
> > "SG" == Stephen Gallagher writes:
>
> SG> To supplement this, it's the default in the sense that packagers are
> SG> expected to ship python3 packages if they are supported upstream and
> SG> if the package includes the same bi
> "SG" == Stephen Gallagher writes:
SG> To supplement this, it's the default in the sense that packagers are
SG> expected to ship python3 packages if they are supported upstream and
SG> if the package includes the same binary executable name for py2 and
SG> py3, only the py3 package should sh
Hi John,
This[0] is tutorial how to create custom policy RPM package.
[0]
http://lvrabec-selinux.rhcloud.com/2015/07/07/how-to-create-selinux-product-policy/
If you have any questions, feel free to contact me.
Thank you.
On 02/24/2016 06:06 PM, John Florian wrote:
Is this[0] really the lat
On 02/24/2016 11:17 AM, Josh Boyer wrote:
On Wed, Feb 24, 2016 at 2:09 PM, Xose Vazquez Perez
wrote:
Jóhann_B._Guðmundsson wrote:
Arguably the regression in 4.4 with drm/i915 that causes screen
flickering in dual monitor setups needs to be looked at before this gets
released since it will g
I plan to make this update on saturday, can anyone take care of the rebuilds?
2016-02-20 21:13 GMT+01:00 Sébastien Willmann :
> Hi,
>
> I’m planning to update jsoncpp in rawhide to version 1.6.5 in a week
> (when f24 is branched)
> (https://bugzilla.redhat.com/show_bug.cgi?id=1209654)
>
> The outp
On Wed, Feb 24, 2016 at 12:35 PM, Honza Šilhan wrote:
> TL;DR
>
> Hawkey project [1] is being obsoleted, use libhif [2] instead. For hawkey
> Python API consumers,
> the transition should be painless.
>
>
> Why we have done that?
>
> Nowadays there are three major consumers of hawkey - DNF, Packa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/02/16 17:08, Stephen Gallagher wrote:
> I no longer need these packages in Fedora (they were there to
> support Review Board which is now only in EPEL due to Django
> incompatibilities), so I've orphaned them.
>
> I will continue to maintain t
On Wed, Feb 24, 2016 at 7:23 PM, Jóhann B. Guðmundsson
wrote:
>
>
> On 02/24/2016 05:22 PM, Laura Abbott wrote:
>>
>> On 02/18/2016 05:51 PM, Laura Abbott wrote:
>>>
>>> Hi,
>>>
>>> 4.4.2 is currently building and should be in updates-testing soon. As
>>> usual,
>>> please test and give karma appr
On Wed, Feb 24, 2016 at 2:09 PM, Xose Vazquez Perez
wrote:
> Jóhann_B._Guðmundsson wrote:
>
>> Arguably the regression in 4.4 with drm/i915 that causes screen
>> flickering in dual monitor setups needs to be looked at before this gets
>> released since it will get tiresome quite quickly for end
Hi,
libselinux upstream plans to disallow to use getpidcon(0, ) in sense of
getpidcon(getpid(), )
This behavior has never been documented and it's implementation is
considered error prone.
There seems to be no such case in Fedora but if your project uses
getpidcon() with pid == 0 to get the cont
Jóhann_B._Guðmundsson wrote:
> Arguably the regression in 4.4 with drm/i915 that causes screen
> flickering in dual monitor setups needs to be looked at before this gets
> released since it will get tiresome quite quickly for end users trying
> to do some work when suddenly one of the screen
Hi guys,
at the moment there is approximately 250 packages shipping projects
written in go. In general, each project has its own set of dependencies
and provided import paths (golang packages). As usually each package has
four active branches. Thus, we are dealing with approximately 1000 spec
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2016-02-25 17:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2016-02-25 09:00 Thu US/Pacific PST
2016-02-25 12:00 Thu US/Eastern EST
2016-02-25 1
On 02/24/2016 05:22 PM, Laura Abbott wrote:
On 02/18/2016 05:51 PM, Laura Abbott wrote:
Hi,
4.4.2 is currently building and should be in updates-testing soon. As
usual,
please test and give karma appropriately (negative karma for new issues,
not existing issues).
Thanks,
Laura
A use afte
it, probably a
day or two. They're quite heavily tied to fedfind versioning and to an
assumption which is no longer true: there will be exactly one nightly
compose per day. When we decide what compose to compare the latest
compose against, we simply pick the compose for the same release from
the
On 02/24/2016 06:31 PM, Jan Kratochvil wrote:
Google found that message in:
https://ppisar.fedorapeople.org/perl_rebuild/scratch/latest/packages/perl-version/build.log
dwz: ./usr/lib64/perl5/vendor_perl/auto/version/vxs/vxs.so.debug: Couldn't find
DIE referenced by DW_OP_GNU_implicit_pointer
S
TL;DR
Hawkey project [1] is being obsoleted, use libhif [2] instead. For hawkey
Python API consumers,
the transition should be painless.
Why we have done that?
Nowadays there are three major consumers of hawkey - DNF, PackageKit and
rpm-ostree. The hawkey
API was not in final form yet and was
On Wed, 24 Feb 2016 17:59:29 +0100, Sérgio Basto wrote:
> Hello,
> What $subject means ? , should I be worried ?
>
> Only happens in rawhide , I think is GCC6 warning.
Google found that message in:
https://ppisar.fedorapeople.org/perl_rebuild/scratch/latest/packages/perl-version/build.log
dwz
Hi all,
We're at the last stages of preparing the first major owncloud update in a
while.
The current version of owncloud in Fedora is the fairly old stable 8.0
release (presently 8.0.10) which we want to bring back in line with the
current owncloud upstream release of 8.2.2.
Unfortunately it's
On 02/18/2016 05:51 PM, Laura Abbott wrote:
Hi,
4.4.2 is currently building and should be in updates-testing soon. As usual,
please test and give karma appropriately (negative karma for new issues,
not existing issues).
Thanks,
Laura
A use after free bug was found in the 4.4.2 release. Since
On Wed, Feb 24, 2016 at 8:02 AM, Stephen Gallagher
wrote:
> On 02/24/2016 09:58 AM, Kaleb S. KEITHLEY wrote:
>
>> On 02/24/2016 09:45 AM, Stephen Gallagher wrote:
>>
>>> On 02/24/2016 09:30 AM, Peter Robinson wrote:
>>>
1) usually after the branch I build new packages for rawhide (i.e.
>
Is this[0] really the latest greatest documentation for doing this? Given that
it references FC5 it seems rather dated and I wouldn't expect something like
this to still be in Draft.
[0] https://fedoraproject.org/wiki/SELinux_Policy_Modules_Packaging_Draft
--
John Florian
--
devel mailing list
Hello,
What $subject means ? , should I be worried ?
Only happens in rawhide , I think is GCC6 warning.
Thanks,
--
Sérgio M. B.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/24/2016 10:41 AM, Bill Nottingham wrote:
> Peter Robinson (pbrobin...@gmail.com) said:
>>> Yeah, this is because the Samba and FreeIPA packages didn't quite
>>> finish their python 3 conversion in time. By F25, we should be able to
>>> avoid ship
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I no longer need these packages in Fedora (they were there to support Review
Board which is now only in EPEL due to Django incompatibilities), so I've
orphaned them.
I will continue to maintain them on EPEL 7.
-BEGIN PGP SIGNATURE-
Version: Gn
On 02/24/2016 10:46 AM, Orion Poplawski wrote:
> On 02/24/2016 07:17 AM, Kaleb S. KEITHLEY wrote:
>> Hi,
>>
>> 1) usually after the branch I build new packages for rawhide (i.e.
>> $branch+1). But atm in the master branch, a `fedpkg build` gives me
>>
>> Could not execute build: Package gluster
On 02/24/2016 07:17 AM, Kaleb S. KEITHLEY wrote:
> Hi,
>
> 1) usually after the branch I build new packages for rawhide (i.e.
> $branch+1). But atm in the master branch, a `fedpkg build` gives me
>
> Could not execute build: Package glusterfs-3.7.8-1.fc24 has already
> been built
>
> Am I ju
Peter Robinson (pbrobin...@gmail.com) said:
> > Yeah, this is because the Samba and FreeIPA packages didn't quite finish
> > their python 3 conversion in time. By F25, we should be able to avoid
> > shipping python 2 in the default installation of Fedora Server.
>
> Except if you want to use ansi
> Yeah, this is because the Samba and FreeIPA packages didn't quite finish
> their python 3 conversion in time. By F25, we should be able to avoid
> shipping python 2 in the default installation of Fedora Server.
Except if you want to use ansible to managed that, although in theory
support for th
On 02/24/2016 09:58 AM, Kaleb S. KEITHLEY wrote:
On 02/24/2016 09:45 AM, Stephen Gallagher wrote:
On 02/24/2016 09:30 AM, Peter Robinson wrote:
1) usually after the branch I build new packages for rawhide (i.e.
$branch+1). But atm in the master branch, a `fedpkg build` gives me
Could not
On Wed, Feb 24, 2016 at 9:17 AM, Kaleb S. KEITHLEY wrote:
> Hi,
>
> 1) usually after the branch I build new packages for rawhide (i.e.
> $branch+1). But atm in the master branch, a `fedpkg build` gives me
>
> Could not execute build: Package glusterfs-3.7.8-1.fc24 has already
> been built
>
>
On 02/24/2016 09:45 AM, Stephen Gallagher wrote:
> On 02/24/2016 09:30 AM, Peter Robinson wrote:
>>> 1) usually after the branch I build new packages for rawhide (i.e.
>>> $branch+1). But atm in the master branch, a `fedpkg build` gives me
>>>
>>> Could not execute build: Package glusterfs-3.7
On 02/24/2016 09:30 AM, Peter Robinson wrote:
1) usually after the branch I build new packages for rawhide (i.e.
$branch+1). But atm in the master branch, a `fedpkg build` gives me
Could not execute build: Package glusterfs-3.7.8-1.fc24 has already
been built
Am I just too early? Or is the
> 1) usually after the branch I build new packages for rawhide (i.e.
> $branch+1). But atm in the master branch, a `fedpkg build` gives me
>
> Could not execute build: Package glusterfs-3.7.8-1.fc24 has already
> been built
>
> Am I just too early? Or is there something missing that's preventin
Hi,
1) usually after the branch I build new packages for rawhide (i.e.
$branch+1). But atm in the master branch, a `fedpkg build` gives me
Could not execute build: Package glusterfs-3.7.8-1.fc24 has already
been built
Am I just too early? Or is there something missing that's preventing
build
Hello All!
That would be great!
2016-02-24 13:24 GMT+01:00 Igor Gnatenko :
> I can take care about rebuilds.
>
>
> On Wed, Feb 24, 2016, 1:23 PM Peter Lemenkov wrote:
>>
>> Hello All!
>> I'm going to upgrade libcue. Unfortunately this requires a soname
>> bump. Fortunately only recompilation is
I can take care about rebuilds.
On Wed, Feb 24, 2016, 1:23 PM Peter Lemenkov wrote:
> Hello All!
> I'm going to upgrade libcue. Unfortunately this requires a soname
> bump. Fortunately only recompilation is necessary.
>
> --
> With best regards, Peter Lemenkov.
> --
> devel mailing list
> devel@
Hello All!
I'm going to upgrade libcue. Unfortunately this requires a soname
bump. Fortunately only recompilation is necessary.
--
With best regards, Peter Lemenkov.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
41 matches
Mail list logo
