Re: sysusage f27 and rawhide blocked in koji

[Frank Crawford]

On Sun, 2018-01-07 at 06:41 +, Peter Robinson wrote:
> On Sun, Jan 7, 2018 at 1:31 AM, Frank Crawford  .au> wrote:
> > Folks,
> > 
> > Sorry to drop this in here, but I've can't find where else it could
> > go. I'm
> > the maintainer for sysusage, which was un-retired mid 2017, around
> > the time
> > of conversion to pagure.io for packages.
> > 
> > The builds for F25 & F26 worked fine, and I assumed it would roll
> > over to
> > F27, etc, but I find that it isn't in F27 and when I try and build
> > new
> > versions for F27 and rawhide, I seem to be blocked in koji. What I
> > get is:
> > 
> > FAILED: BuildError: package sysusage is blocked for tag
> > f27-updates-candidate or FAILED: BuildError: package sysusage is
> > blocked for
> > tag f28-pending
> > 
> > So, how do I go about getting getting these tags unblocked for this
> > package?
> 
> File a rel-eng ticket [1] as per the packaging guidelines
> 
> [1] https://pagure.io/releng

Thanks.  I was looking in the wrong place.

Regards
Frank___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: sysusage f27 and rawhide blocked in koji

[Peter Robinson]

On Sun, Jan 7, 2018 at 1:31 AM, Frank Crawford  wrote:
> Folks,
>
> Sorry to drop this in here, but I've can't find where else it could go. I'm
> the maintainer for sysusage, which was un-retired mid 2017, around the time
> of conversion to pagure.io for packages.
>
> The builds for F25 & F26 worked fine, and I assumed it would roll over to
> F27, etc, but I find that it isn't in F27 and when I try and build new
> versions for F27 and rawhide, I seem to be blocked in koji. What I get is:
>
> FAILED: BuildError: package sysusage is blocked for tag
> f27-updates-candidate or FAILED: BuildError: package sysusage is blocked for
> tag f28-pending
>
> So, how do I go about getting getting these tags unblocked for this package?

File a rel-eng ticket [1] as per the packaging guidelines

[1] https://pagure.io/releng
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: EXTERNAL: Re: After suspension

[Jared K. Smith]

(Apologies for the top-posting -- I'm on a mobile device at the moment.)

Interesting... I noticed something similar today, but with a WebDAV
external filesystem mounted.  Turning off fprintd seemed to stop the delay,
however.  Does turning off fprintd solve the problem for you as well?

-Jared

On Thu, Jan 4, 2018 at 8:18 AM, Wells, Roger K.  wrote:

> On 01/02/2018 01:18 PM, Al Stone wrote:
>
>> On 12/26/2017 12:23 PM, Wells, Roger K. wrote:
>>
>>> Small inconvenience but new and annoying:
>>> Machine is Thinkpad x260
>>> uname -a: Linux rwells-x260 4.14.7-300.fc27.x86_64 #1 SMP Mon Dec 18
>>> 16:06:12
>>> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>>> Desktop: Gnome 3.26.4-1.fc27.x86_64
>>>
>>> When the lid is opened on the suspended machine the screen saver appears
>>> and the
>>> clock proceeds to update until
>>> the enter key is hit.  Then the clock stops updating for 27 seconds
>>> followed by
>>> the login entry dialog appearing.
>>> Then everything is back to normal.
>>> This began right after the upgrade from F26 to F27 and has persisted
>>> through one
>>> or two subsequent routine updates.
>>> There are inconsistencies, sometimes it only does it when there is only
>>> wireless
>>> connections and no wired options.
>>> Sometimes it doesn't do it at all, no pattern here.
>>> Sometimes the 27 second delay is much shorter but this is quite rare.
>>> I have been running Fedora/Gnome for years and have never seen this.
>>>
>>> Any thoughts or things to try to help pin it down will be appreciated.
>>>
>>> thanks
>>>
>> There have been a lot of recent changes in ACPI code for suspend and
>> hibernate;
>> it's always possible that something got tweaked in a recent kernel that
>> could
>> affect this particular model of machine.
>>
>> That being said, the 27 second delay sounds like the laptop hibernated
>> (not
>> suspended); if you waited a variable length of time to open the lid
>> again, it
>> might explain some of the variation -- sometimes it suspended, sometimes
>> it was
>> caught before hibernation was complete, sometime it was caught after it
>> had
>> fully hibernated.  The other things that occur to me are that perhaps
>> hibernate
>> was not working before for this model of laptop and now it does; or, the
>> power
>> settings changed defaults, or did not retain settings when updating; or,
>> some
>> of the recent changes for lid notification aren't quite right for this
>> laptop
>> (there have been a few cases of that).  Those are some of the places
>> where I
>> would start looking, at least...
>>
>> It turns out that this delay only occurs when the suspend happened when
> an external filesystem is mounted.
> In this case a cifs mount, and IIRC there have been some issues related to
> version changes that necessitated specifying "vers=1.0" in the fstab file.
> I will do some experiments and report back if anything interesting
> develops.
>
> --
> Roger Wells, P.E.
> leidos
> 221 Third St
> Newport, RI 02840
> 401-847-4210 (voice)
> 401-849-1585 (fax)
> roger.k.we...@leidos.com
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

sysusage f27 and rawhide blocked in koji

[Frank Crawford]

Folks,

Sorry to drop this in here, but I've can't find where else it could go.
 I'm the maintainer for sysusage, which was un-retired mid 2017, around
the time of conversion to pagure.io for packages.

The builds for F25 & F26 worked fine, and I assumed it would roll over
to F27, etc, but I find that it isn't in F27 and when I try and build
new versions for F27 and rawhide, I seem to be blocked in koji.  What I
get is:

FAILED: BuildError: package sysusage is blocked for tag f27-updates-
candidate
or
FAILED: BuildError: package sysusage is blocked for tag f28-
pending

So, how do I go about getting getting these tags unblocked for this
package?

Regards
Frank___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1531969] New: perl-DBIx-Class-DeploymentHandler-0.002222 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531969

Bug ID: 1531969
   Summary: perl-DBIx-Class-DeploymentHandler-0.00 is
available
   Product: Fedora
   Version: rawhide
 Component: perl-DBIx-Class-DeploymentHandler
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org



Latest upstream release: 0.00
Current version/release in rawhide: 0.002221-1.fc28
URL: http://search.cpan.org/dist/DBIx-Class-DeploymentHandler

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/8029/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 1035  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087   
dokuwiki-0-0.24.20140929c.el7
 797  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f   
mcollective-2.8.4-1.el7
 379  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-04bc9dd81d   
libbsd-0.8.3-1.el7
 277  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d241156dfe   
mod_cluster-1.3.3-10.el7
 109  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e27758bd23   
libmspack-0.6-0.1.alpha.el7
  46  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e64eeb6ece   
nagios-4.3.4-5.el7
  35  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d704442ae7   
qpid-cpp-1.37.0-1.el7
  16  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-957aa05f33   
heketi-5.0.1-1.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8d57a2487b   
monit-5.25.1-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-753e392fc4   
xrdp-0.9.5-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2e2d08b1ff   
awstats-7.6-4.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-49ca8440a1   
gifsicle-1.90-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

autowrap-0.14.0-1.20170807git31dbeb.el7
clamav-0.99.2-14.el7
nova-agent-2.1.11-1.el7

Details about builds:



 autowrap-0.14.0-1.20170807git31dbeb.el7 (FEDORA-EPEL-2018-ad5cbc1960)
 Generates Python Extension modules from [Cython] PXD files

Update Information:

-Update to 0.14.0




 clamav-0.99.2-14.el7 (FEDORA-EPEL-2018-713df7476e)
 End-user tools for the Clam Antivirus scanner

Update Information:

Fixes for rhbz 1530678 and 1518016

References:

  [ 1 ] Bug #1530678 - clamav-server requires nmap-ncat, security concerns
https://bugzilla.redhat.com/show_bug.cgi?id=1530678
  [ 2 ] Bug #1518016 - the jitoff patch is no longer needed and should be 
removed
https://bugzilla.redhat.com/show_bug.cgi?id=1518016




 nova-agent-2.1.11-1.el7 (FEDORA-EPEL-2018-6289af73ce)
 Agent for setting up clean servers on Xen

Update Information:

- Latest upstream

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: [Proposal] Mass change: remove executing gtk-update-icon-cache in %post/%postu/%postrans to update hicolor theme cache

[Robert-André Mauchin]

On vendredi 5 janvier 2018 18:21:59 CET Jason L Tibbitts III wrote:
> > "IG" == Igor Gnatenko  writes:
> 
> 
> IG> First thing you should do is to open a ticket for FPC[0] in order to
> IG> fix guidelines.
> 
> I'm still catching up on list mail but someone sent me a personal email
> about this.  Not sure why they didn't open a ticket, but in the end it
> doesn't matter.  I did see that even in F26 that icon cache stanza is
> not needed and so I went ahead and moved that bit to the EPEL:Packaging
> page.
> 
>  - J<

I sent the personal email before I found out about this thread, it was during 
a review for a package from Rex Dieter that he poinsed out that hicolor-icon-
theme had transfiletrigger and that the guidelines were outdated.

Robert-André
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1531814] Update to perl-Tree-Simple from 1.31 to 1.32 causes new warning spew

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531814



--- Comment #4 from Fedora Update System  ---
perl-Tree-Simple-1.33-1.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-aed84f4b44

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531529] perl-RDF-Trine-1.019 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531529



--- Comment #5 from Fedora Update System  ---
perl-RDF-Trine-1.019-1.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-cca86e4fc0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531814] Update to perl-Tree-Simple from 1.31 to 1.32 causes new warning spew

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531814

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Tree-Simple-1.33-1.fc26 has been pushed to the Fedora 26 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-90aefcc4a7

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531529] perl-RDF-Trine-1.019 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531529

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-RDF-Trine-1.019-1.fc26 has been pushed to the Fedora 26 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-41359732ae

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 6 updates-testing report

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
 913  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031   
python-virtualenv-12.0.7-1.el6
 907  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168   
rubygem-crack-0.3.2-2.el6
 797  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb   
mcollective-2.8.4-1.el6
 768  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9   
thttpd-2.25b-24.el6
 379  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3e50897ac   
libbsd-0.8.3-2.el6
 108  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-4c76ddcc92   
libmspack-0.6-0.1.alpha.el6
  28  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-ed87c07972   
hostapd-2.6-7.el6
  28  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6aaee32b7e   
optipng-0.7.6-6.el6
  28  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-3432442a31   
shellinabox-2.20-5.el6
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6e4ce19598   
monit-5.25.1-1.el6
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-37c8dbd6f1   
gifsicle-1.90-1.el6
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8c9006d462   
heimdal-7.5.0-1.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

heimdal-7.5.0-1.el6
lighttpd-1.4.47-1.el6
nova-agent-2.1.11-1.el6

Details about builds:



 heimdal-7.5.0-1.el6 (FEDORA-EPEL-2018-8c9006d462)
 A Kerberos 5 implementation without export restrictions

Update Information:

Update to 7.5.0 GA release (CVE-2017-17439)

References:

  [ 1 ] Bug #1524546 - CVE-2017-17439 heimdal: NULL pointer dereference via 
crafted UDP packets
https://bugzilla.redhat.com/show_bug.cgi?id=1524546




 lighttpd-1.4.47-1.el6 (FEDORA-EPEL-2018-30b25ee0c6)
 Lightning fast webserver with light system requirements

Update Information:

1.4.47 with backported patch.

References:

  [ 1 ] Bug #1530548 - Update to lighttpd 1.4.48
https://bugzilla.redhat.com/show_bug.cgi?id=1530548




 nova-agent-2.1.11-1.el6 (FEDORA-EPEL-2018-9a5c28e397)
 Agent for setting up clean servers on Xen

Update Information:

- Latest upstream

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: [Test-Announce] Call for testing: updates to address today's CPU/kernel vulnerability

[Chris Adams]

Once upon a time, Adam Williamson  said:
> * If the fix does cause problems on your hardware, you can disable it
> by booting with the kernel parameter 'nopti'.

So, on RHEL/CentOS kernels, there are three new entries in
/sys/kernel/debug/x86; ibpb_enabled, ibrs_enabled, and pti_enabled.  I
don't see these on the Fedora kernel.

Are these variables something added by Red Hat to their kernel,
something that will be added to Fedora, etc.?  They are useful to see
exactly what fix(es) are being applied, as well as to have a runtime way
to enable/disable them.
-- 
Chris Adams 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Anaconda modularization

[Matthew Miller]

On Sat, Jan 06, 2018 at 09:09:52AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > to support its customization, extensibility and testability. It will
> > be easier to monitor the installation, maintain an install class or an
> > addon, drop some modules or provide your own UI.
> Wow, that sounds like a hefty change. Has the work already begun?
> Is there a repo/branch where one can look at the WIP, test stuff, etc?

I'm not sure I'm comfortable with "Contingency deadline: Final freeze"
for this. Is the plan to keep making and testing the old (current)
version until that point?

Final freeze is 2018-04-17, with target release date just two weeks
later on 2018-05-01 — which means go/no-go on 2018-04-26, which means
we need a perfect release candidate on 2018-04-25, which means all
fixes need to be in on 2018-04-24. There's a weekend in there, so that
just means *five* working days.

If both branches are going to be kept and tested in a "could go this
way" state up until the final freeze, that could work. But if it's "all
development on new thing, old thing left in the freezer", I'm afraid
five days isn't enough time to get it out and get it into shape again.

Keeping both approaches up-to-date and tested seems like a lot of extra
work. On the other hand, putting the decision much earlier means that
we don't get the benefit of beta feedback. My inclination is to ask for
a contingency-activation check a week _before_ the final freeze, which
gives an extra two weeks (ideally) or one week (if the beta slips) to
get the contingency into shape.

Anaconda team, opinions on this?

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1531814] Update to perl-Tree-Simple from 1.31 to 1.32 causes new warning spew

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531814



--- Comment #2 from Fedora Update System  ---
perl-Tree-Simple-1.33-1.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-90aefcc4a7

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531814] Update to perl-Tree-Simple from 1.31 to 1.32 causes new warning spew

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531814



--- Comment #1 from Fedora Update System  ---
perl-Tree-Simple-1.33-1.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-aed84f4b44

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Anaconda modularization

[Colin Walters]

On Fri, Jan 5, 2018, at 7:28 AM, Jan Kurik wrote:

> Anaconda installer will be split into several modules that will
> communicate over DBus using stable API.

For the curious this blog entry is useful:
http://blog-jkonecny.rhcloud.com/2017/06/16/shining-new-anaconda-modularisation/

I also would still like
http://blog-jkonecny.rhcloud.com/2017/06/16/shining-new-anaconda-modularisation/#comment-3366641149

However my main concern here is: Anaconda is a baseline requirement
for really doing much at all in releasing anything "Fedora" - for example
we use Anaconda to generate both cloud images and the base container images.
And obviously it's required to do bare metal installs.

There are a few ways I could imagine doing this; ideally Fedora releng
would have a real branching concept.  I think it can sort of be set up manually.
Do you have any plans to request that?

At least let's be ready with a fallback plan of using the existing codebase?
Are there going to be git branches upstream so fixes can still land
in the current installer?

For example I had plans to work on
https://github.com/rhinstaller/anaconda/issues/1259
sometime soon, and *hopefully* it shouldn't conflict with modularization
but it seems likely the change would need to go in both branches or so?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 System Wide Change: Removal of Sun RPC Interfaces From glibc

[Kevin Kofler]

Jan Kurik wrote:
> This system-wide change covers the removal of interfaces related to
> Sun RPC from glibc.

This was pushed to Rawhide already, WITHOUT FESCo approval. (The change is 
still in "announced" state.) There was also NO announcement of the API 
change in Rawhide, contrary to policy. This is entirely unacceptable.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1470030

Mark Wielaard  changed:

   What|Removed |Added

External Bug ID||KDE Software Compilation
   ||386945



--- Comment #9 from Mark Wielaard  ---
I suspect this is upstream bug https://bugs.kde.org/show_bug.cgi?id=386945

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531705] [FTBFS] perl-Test-LeakTrace FTBFS rawhide

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531705

Paul Howarth  changed:

   What|Removed |Added

 Depends On||1470030




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1470030
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test
'UninitCondition' on ppc64
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1470030

Paul Howarth  changed:

   What|Removed |Added

 Blocks||1531705



--- Comment #8 from Paul Howarth  ---
Still failing on ppc64:
https://koji.fedoraproject.org/koji/taskinfo?taskID=24037045
https://kojipkgs.fedoraproject.org/work/tasks/7045/24037045/build.log


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1531705
[Bug 1531705] [FTBFS] perl-Test-LeakTrace FTBFS rawhide
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1531885] New: perl-Net-GitHub-0.93 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1531885

Bug ID: 1531885
   Summary: perl-Net-GitHub-0.93 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Net-GitHub
  Keywords: FutureFeature, Triaged
  Assignee: jpazdzi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jpazdzi...@redhat.com, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org



Latest upstream release: 0.93
Current version/release in rawhide: 0.91-1.fc28
URL: http://search.cpan.org/dist/Net-GitHub/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/3150/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: How_do_I_request_commit_access_to_a_dist-git_repo where I'm admin ?

[Sérgio Basto]

On Sat, 2018-01-06 at 10:47 +0100, Pierre-Yves Chibon wrote:
> On Sat, Jan 06, 2018 at 03:20:26AM +, Sérgio Basto wrote:
> > On Fri, 2018-01-05 at 21:10 -0600, Jason L Tibbitts III wrote:
> > > > > > > > "SB" == Sérgio Basto  writes:
> > > 
> > > SB> I don't have permissions on epel7
> > > 
> > > There are a few repos where the gitolite permission setup wasn't
> > > regenerated after the switch to pagure.  I just checked and that
> > > definitely appears to be one of them, but I don't have permission
> > > to
> > > fix
> > > it for you.  If you file a ticket at
> > > https://pagure.io/fedora-infrastructure/ and ask for the gitolite
> > > configuration for the clamav repository to be regenerated, I'm
> > > sure
> > > someone can help you out.
> > 
> > Ah , OK and thanks :) 
> 
> Gitolite configuration updated, should be working now :)

Cool, thanks , yes it working now. 

-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 System Wide Change: Hardening Flags Updates for Fedora 28

[Richard W.M. Jones]

On Fri, Jan 05, 2018 at 01:10:21PM +0100, Florian Weimer wrote:
> On 01/05/2018 12:41 PM, Mark Wielaard wrote:
> >On Thu, Jan 04, 2018 at 09:36:27PM -0800, John Reiser wrote:
> >>2) The explicit write by the stack probe can mask a memcheck(valgrind)
> >>violation, at least until memcheck groks the probe.
> >
> >That should not be true. The probe is done after the stack pointer is
> >lowered, so memcheck/valgrind knows that memory is used. If the probe
> >is done below the actual stack pointer that would be a bug in the gcc
> >-fstack-protector implementation. Please do report such issues when you
> >encounter them. There were indeed such bugs in the past on some
> >architectures (especially in combination with no-return functions),
> >but I believe they have all been fixed now.
> 
> The generic -fstack-clash-protection in GCC has this problem, which
> is why we can't use it and have to disable it on architectures where
> there is no support, which currently includes armhfp.  (For aarch64,
> we still carry our own patch, and may have to continue doing that
> even after switching to GCC 8.)

I noticed as a side effect of compiling GCC for riscv64 that RISC-V's
GCC doesn't support -fstack-clash-protection.  Do you know what is
involved to add it?  From a naive point of view I don't understand why
this feature depends on architecture at all.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: VirtualBox Guest Integration

[Richard W.M. Jones]

On Fri, Jan 05, 2018 at 02:03:17PM +, Sérgio Basto wrote:
> Hi,
> 
> On Thu, 2018-01-04 at 14:16 +0100, Jan Kurik wrote:
> > - Add VirtualBox Guest Additions package to the default package list
> > for the Workstation product
> 
> I don't understand this one, VirtualBox Guest should *only* be
> installed in an virtual machine .

Sort of.  For VMware, the guest tools (open-vm-tools) are in a special
comps group ‘platform-vmware’ which Anaconda uses when installing on
VMware.  (There is also a comps group containing all guest agents)

In addition the service files use systemd
‘ConditionVirtualization=vmware’ so the service should not start up
unless VMware is detected at run time.

> Today VirtualBox-server conflicts with VirtualBox-guest-additions and
> vice versa . 

This sounds right, unless nested virtualization is expected to work
(in which case a layer might be both a hypervisor and a guest).

>  %pre guest-additions
> +if [ $(systemd-detect-virt | grep -iP "oracle|kvm" -c) -eq 0 ]; then
> +echo "This package it is only to install in one Oracle VM VirtualBox."
> +echo "You are trying install VirtualBox guest-additions but it hasn't been \
> +detected that your system is running in a VirtualBox virtualization, so we \
> +forced the installation to fail."
> +exit 1
> +fi

This won't work because you often prepare guest images on a system
other than the final hypervisor.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How_do_I_request_commit_access_to_a_dist-git_repo where I'm admin ?

[Pierre-Yves Chibon]

On Sat, Jan 06, 2018 at 03:20:26AM +, Sérgio Basto wrote:
> On Fri, 2018-01-05 at 21:10 -0600, Jason L Tibbitts III wrote:
> > > > > > > "SB" == Sérgio Basto  writes:
> > 
> > SB> I don't have permissions on epel7
> > 
> > There are a few repos where the gitolite permission setup wasn't
> > regenerated after the switch to pagure.  I just checked and that
> > definitely appears to be one of them, but I don't have permission to
> > fix
> > it for you.  If you file a ticket at
> > https://pagure.io/fedora-infrastructure/ and ask for the gitolite
> > configuration for the clamav repository to be regenerated, I'm sure
> > someone can help you out.
> 
> Ah , OK and thanks :) 

Gitolite configuration updated, should be working now :)

Sorry for the inconvenience,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Anaconda modularization

[Zbigniew Jędrzejewski-Szmek]

On Fri, Jan 05, 2018 at 01:28:50PM +0100, Jan Kurik wrote:
> = Proposed Self Contained Change: Anaconda modularization =
> https://fedoraproject.org/wiki/Changes/AnacondaModularization
> 
> Change owner(s):
> * Jiří Konečný 
> 
> 
> Anaconda installer will be split into several modules that will
> communicate over DBus using stable API.
> 
> 
> == Detailed Description ==
> Anaconda will be split into several modules that will communicate over
> DBus. The goal is to introduce a stable way to interact with Anaconda
> to support its customization, extensibility and testability. It will
> be easier to monitor the installation, maintain an install class or an
> addon, drop some modules or provide your own UI.
Wow, that sounds like a hefty change. Has the work already begun?
Is there a repo/branch where one can look at the WIP, test stuff, etc?

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 System Wide Change: Removal of Sun RPC Interfaces From glibc

[Zbigniew Jędrzejewski-Szmek]

On Fri, Jan 05, 2018 at 10:12:50PM +0100, Florian Weimer wrote:
> On 01/05/2018 09:42 PM, Simo Sorce wrote:
> >On Fri, 2018-01-05 at 21:09 +0100, Florian Weimer wrote:
> >>On 01/05/2018 08:10 PM, Yaakov Selkowitz wrote:
> >>
> >>>Please be aware that not all RPC-dependent packages are "aware" of
> >>>libtirpc yet.  Notably, KDE's NFS kioslaves (in kdebase3, kde-runtime,
> >>>and kio-extras) would need to be patched to use libtirpc.  Without such,
> >>>the packages would rebuild, but without NFS support.
> >>
> >>Understood.  There are other packages affected in similar ways.  But we
> >>have announced the transition roughly ten years ago, and it's clear that
> >>we can't finish it simply by begging maintainers.  Sorry.
> >
> >Do you have a list of affected packages ?
> 
> This should be a reasonable approximation:
> 
>   source
> --
>  R-3.4.3-2.fc28.src.rpm
...
>  zfs-fuse-0.7.2.2-6.fc27.src.rpm
> (62 rows)

That's very helpful.

Are there some instructions how a maintainer would go about porting a package?
Something like "dnf uninstall blah && dnf install libtirpc-devel; build
your package; verify that the resulting package does not depend on foo"?

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org