Re: Intent to orphan php-gettext-gettext

2019-09-04 Thread Sundeep Anand
On Wed, Sep 4, 2019 at 7:06 PM Randy Barlow 
wrote:

> On Wed, 2019-09-04 at 11:12 +0530, Sundeep Anand wrote:
> > Hi Randy,
> >
> > I have some interest maintaining it.
>
> Is your FAS account sundeepanand? If so, it doesn't appear that you are
> a Fedora packager at the moment.
>

ah, sorry I didn't mention that; fas: suanand
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Open NeuroFedora Meeting agenda for 2019-09-05

2019-09-04 Thread Philip Rhoades

Ankur,


On 2019-09-05 02:38, Ankur Sinha wrote:

Hello,

Please join us for the weekly Open NeuroFedora team meeting tomorrow.
Details below:



As:

- a Linux user since the kernel 0.9 days
- a RH user since v4
- a Fedora user since the beginning
- an Ex Dir of the http://neuralarchivesfoundation.org and particularly 
interested in BCIs and consciousness uploading


it looks like I should participate in the meeting but it is at 1am 
Sydney time - would any of the participants be interested in a Jitsi 
chat at some stage?


Thanks,

Phil.



- Forwarded message -


Hi all!

You are kindly invited to attend the Open NeuroFedora team meeting 
this week

on Thursday (tomorrow) at 1500UTC in #fedora-neuro on IRC (Freenode):

        https://webchat.freenode.net/?channels=#fedora-neuro

You can convert the meeting time to your local time using: 
$ date --date='TZ="UTC" 1500 next Thu'
or use this link: 
https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting=20190905T15=1440=1


The agenda for the meeting is:
- Introductions and roll call
- Pagure tickets related to our progress on computational neuroscience 
tools

https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
- Planning for the next phase of NeuroFedora tasks
- Neuroscience query of the week
- Next meeting day and chair
- Open floor

Please go through the tickets on Pagure and mark and other tickets 
that need

to be disccused with the "S: Next meeting" tag.

Hope to see you there!


--
Danny Lee  <>





- End forwarded message -

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[389-devel] 389 DS nightly 2019-09-05 - 96% PASS

2019-09-04 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2019/09/05/report-389-ds-base-1.4.1.6-20190904git295ea07.fc30.x86_64.html
___
389-devel mailing list -- 389-de...@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-de...@lists.fedoraproject.org


[Bug 1749132] Too strict gir lib search pattern

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1749132

Vadim Raskhozhev  changed:

   What|Removed |Added

 Attachment|0   |1
#1611740 is||
   obsolete||



--- Comment #1 from Vadim Raskhozhev  ---
Created attachment 1611743
  --> https://bugzilla.redhat.com/attachment.cgi?id=1611743=edit
A less-strict template

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-de...@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-de...@lists.fedoraproject.org


[Bug 1749132] New: Too strict gir lib search pattern

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1749132

Bug ID: 1749132
   Summary: Too strict gir lib search pattern
   Product: Fedora
   Version: 30
Status: NEW
 Component: perl-Glib-Object-Introspection
  Assignee: berra...@redhat.com
  Reporter: iamde...@gmail.com
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com, dd...@cpan.org,
perl-de...@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Created attachment 1611740
  --> https://bugzilla.redhat.com/attachment.cgi?id=1611740=edit
A less-strict template

Description of problem: perli11ndoc script from perl-Glib-Object-Introspection
can either display a window with a drop-down list of available GIRs or, if
launched with a GIR name, find the corresponding file, parse it and dump to
stdout. The latter mode has, among other things, a check whether the given
argument can be a valid GIR name. However the pattern to check against is too
strict. For example, it filters out GdkX11, libxfce4panel, libxfce4ui,
libxfce4util and PangoFT2


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install and of the following — pango-devel, xfce4-panel, libxfce4ui,
gtk3-devel, libxfce4util
2. run perli11ndoc without arguments; ensure that the GIR matching the
installed package is listed in a drop-down list
3. run perli11ndoc GdkX11 (or whatever name from that packages installed on
step 1)

Actual results: "Cannot recognize the library name" on stderr

Expected results: contents of that GIR on stdout

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-de...@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-de...@lists.fedoraproject.org


[Bug 1749126] New: perl-Glib-Object-Introspection should depend on perl-Gtk3

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1749126

Bug ID: 1749126
   Summary: perl-Glib-Object-Introspection should depend on
perl-Gtk3
   Product: Fedora
   Version: 30
Status: NEW
 Component: perl-Glib-Object-Introspection
  Assignee: berra...@redhat.com
  Reporter: iamde...@gmail.com
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com, dd...@cpan.org,
perl-de...@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Description of problem: perli11ndoc script from perl-Glib-Object-Introspection
package fails to work if no perl-Gtk3 is installed. Please consider adding
runtime dependency on perl-Gtk3.

Version-Release number of selected component (if applicable):
perl-Glib-Object-Introspection-0.047-1.fc30.x86_64

How reproducible: always

Steps to Reproduce:
1. dnf remove perl-Gtk3
2. dnf install perl-Glib-Object-Introspection
3. perli11ndoc

Actual results:
Usage: perli11ndoc [::[::]] at
/usr/bin/perli11ndoc line 31.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-de...@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-de...@lists.fedoraproject.org


Re: [Test-Announce] Fedora 31 Beta Freeze

2019-09-04 Thread Jason L Tibbitts III
> "CM" == Chris Murphy  writes:

CM> But anyway, I did laugh a bit out loud at 23:45 UTC because *of
CM> course* there are many other totally unambiguous times to choose
CM> from instead. Some of the best comedy is pointing out the obvious.

If we're going to bikeshed it, I'll vote for two minutes to midnight.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


FedoraRespin-30-updates-20190904.0 compose check report

2019-09-04 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 2/31 (x86_64)

ID: 442226  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/442226
ID: 442228  Test: x86_64 KDE-live-iso release_identification
URL: https://openqa.fedoraproject.org/tests/442228

Soft failed openQA tests: 1/31 (x86_64)
(Tests completed, but using a workaround for a known bug)

ID: 442253  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/442253

Passed openQA tests: 28/31 (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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


How to contact hno (Henrik Nordström)?

2019-09-04 Thread Miro Hrončok

Hey,

anybody knows how to properly contact hno (Henrik Nordström) and whether they 
are still interested in maintaining bzr?


https://bugzilla.redhat.com/show_bug.cgi?id=1749118
https://bugzilla.redhat.com/show_bug.cgi?id=1486686
https://bugzilla.redhat.com/show_bug.cgi?id=1734995
https://bugzilla.redhat.com/show_bug.cgi?id=1737937

See also 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/OUMBR2LWRMWWXRWU4S4DREVHNVKYQGJV/

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[389-devel] Please review: 50584, 49212 - docker healthcheck and configuration

2019-09-04 Thread William Brown
https://pagure.io/389-ds-base/issue/50584

https://pagure.io/389-ds-base/issue/49212

https://pagure.io/389-ds-base/pull-request/50585

Thanks! 

--
Sincerely,

William
___
389-devel mailing list -- 389-de...@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-de...@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Miro Hrončok

On 04. 09. 19 14:40, Petr Pisar wrote:

I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
changed libproj soname from libproj.so.13 to libproj.so.15.
...

A similar issue is in Fedora 31 where the rebuilds should go to proj
update .


The change was unpushed from Fedora 31.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Packages with broken dependencies on Python 3.7

2019-09-04 Thread Miro Hrončok

Hello packagers!

The following packages failed to build on Fedora 32 with Python 3.8 and they 
still require Python 3.7 on runtime.


If the packages won't build with Python 3.8, they won't be installable, along 
with all their dependent packages, in Fedora 32.


If there is an "actual" build failure, you should have already received a bug 
report blocking the tracking bug:


https://bugzilla.redhat.com/showdependencytree.cgi?id=PYTHON38_resolved=1

If it is a dependency failure caused by an external factor (retired package, 
etc.) there should be a bugreport as well.


However, if the package fails to resolve build dependencies only because some 
other package hasn't been rebuilt with Python 3.8, we have not opened a bug 
report (yet) to avoid duplication. If you see your package here and are blocked 
by another package, I recommend to see if the dependency isn't waiting for your 
help (e.g. the package maintainers haven't yet got time to look into this).


Chances are, there is some undiscovered dependency loop as well.

The Red Hat Python Maintenance team will gladly help with specific problems, but 
we will not fix all the packages ourselves.


See also https://fedoraproject.org/wiki/Changes/Python3.8

Affected maintainers are bcced (except orphan, groups and maintainers usually 
disturbed by my spam).


Maintainers by package:
blender  design-sw hobbes1069 ignatenkobrain kwizart luya roma 
s4504kr slaanesh

certbot  jhogarth nb
clingo   thofmann
coccinelle   rjones
condor   bbockelm bcotton eerlands matt matyas stevetraylen tstclair 
ttheisen valtri

coreboot-utils   lkundrak peter
datagrepper  ianweller ralph
dee  jspaleta spot
dionaea  rebus
freecad  hobbes1069 jkastner zultron
gcc-python-plugindmalcolm jakub
gdl  orion
gnucash  notting
gplugin  ignatenkobrain
graphite-api piotrp
graphite-web jamielinux jsteffan piotrp
kdevelop-python  dvratil jgrulich minh
libcec   pbrobinson
libpst   carllibpst
libunity rdieter
mailman3 abompard
matrix-synapse   dcallagh jcline
mraa pbrobinson
ocrmypdf qulogic
paraview deji orion sagitter
player   kwizart rmattes timn ttorling
pocketsphinx mikep
pybind11 jussilehtola
python-APScheduler   orphan
python-OBD   rathann
python-Pympler   rathann
python-agate jujens
python-agate-dbf jujens
python-agate-excel   jujens
python-agate-sql jujens
python-aioresponses  gsauthof
python-aiosmtpd  abompard
python-alchimia  vpopovic
python-anymarkup jchaloup orphan
python-anymarkup-core jchaloup orphan
python-astroML   lupinix
python-astroML-addons lupinix
python-astropy-healpix lupinix
python-astroscrappy  lupinix
python-asttokens zbyszek
python-asynctest rathann
python-behavechurchyard orphan
python-beniget   churchyard
python-bz2file   besser82
python-cartopy   qulogic
python-cattrsbrouhaha
python-ccdproc   lupinix
python-certbot-apache jhogarth nb
python-certbot-dns-cloudflare nb
python-certbot-dns-cloudxns nb
python-certbot-dns-digitalocean elyscape nb
python-certbot-dns-dnsimple nb
python-certbot-dns-dnsmadeeasy nb
python-certbot-dns-gehirn elyscape
python-certbot-dns-google elyscape nb
python-certbot-dns-linode elyscape
python-certbot-dns-luadns nb
python-certbot-dns-nsone nb
python-certbot-dns-ovh elyscape
python-certbot-dns-rfc2136 logic nb
python-certbot-dns-route53 elyscape nb
python-certbot-dns-sakuracloud elyscape
python-certbot-nginx jhogarth nb
python-chaospy   lbazan
python-cheetah   mikeb mskalick panovotn
python-cliappsalimma
python-crochet   jcline
python-csvkitjujens
python-dask  qulogic
python-dbus-python-client-gen grover ignatenkobrain mulhern
python-django-appconf mrunge
python-django-pyscss mrunge
python-elephant  lbazan
python-envisage  orion
python-epub  athoscr
python-flake8-import-order zbyszek
python-gast  churchyard
python-gatspylupinix
python-geoplot   qulogic
python-gfm   thm
python-gnocchiclient mrunge pkilambi
python-grafyaml  orphan
python-imagehash fab
python-inema gsauthof
python-into-dbus-python grover ignatenkobrain ilgrad
python-jenkins-job-builder ignatenkobrain ktdreyer pabelanger
python-jira  ishcherb ralph stevetraylen
python-joblibbesser82 ignatenkobrain sergiopr
python-junit_xml jhogarth
python-leveldb   carlwgeorge
python-libpysal  qulogic
python-logging-tree  orphan ralph
python-marshmallow-enum orphan
python-mdp   zbyszek
python-missingno lbazan
python-mne   ignatenkobrain
python-mne-bids  lbazan
python-mplcairo  qulogic
python-mplcursorsqulogic
python-neo   ankursinha
python-neurosynthlbazan

Re: Better interactivity in low-memory situations

2019-09-04 Thread Kyle Marek
On 9/4/19 3:38 PM, Chris Murphy wrote:
> On Wed, Sep 4, 2019 at 1:03 PM Chris Murphy  wrote:
>> I'm skeptical of swapfiles for this use case, because it likely
>> increases the chance for file system disk contention, see section
>> 11.17
>> https://www.kernel.org/doc/gorman/html/understand/understand014.html
> Actually that looks outdated now.
>
> https://patchwork.kernel.org/patch/10347293/
>
> Btrfs since 5.0 also supports swapfiles by avoiding bmap, using
> btrfs_swap_activate, the btrfs equivalent of iomap_swap_activate

I misspoke when I said "file". It's an LVM logical volume.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Kyle Marek
On 9/4/19 3:16 PM, Florian Weimer wrote:
> * Kyle Marek:
>
>> I'm finding that 32G is not necessarily sufficient for compiling clang
>> itself. Similarly I've had a hard time compiling UnrealEngine from
>> source. I usually see ld using up to 12G of memory to link each
>> artifact. Using -j$(nproc) on a 16 VCPU system amplifies the issue. I
>> rely on adding another 32G swap file to complete the job.
> Out of curiosity, which ld do you use?  BFD ld, gold, or LLVM's?
>
> Thanks,
> Florian

In both cases, I believe it was GNU ld.

I know it was GNU ld when building clang/llvm tools itself. I only had
GCC and GNU binutils installed at the time.

UnrealEngine requires clang to compile, but I can't remember for sure if
they finally linked with ld (GNU on my $PATH) or lld.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unresponsive maintainers: Alex Chernyakhovsky & Othman Madjoudj

2019-09-04 Thread Robbie Harwood
Alex Chernyakhovsky  writes:

> On Wed, Sep 4, 2019 at 5:16 PM Alex Chernyakhovsky  wrote:
>> On Wed, Sep 4, 2019 at 3:33 PM Robbie Harwood  wrote:
>>>
>>> Hi Fedora,
>>>
>>> I'm trying to contact Alex Chernyakhovsky and Othman Madjoudj, who
>>> are the maintainers of mosh as far as I can tell.  I have started
>>> the nonresponsive maintainer process due to lack of contact through
>>> bugzilla mail; bugs are
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1697355 and
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1749058 .
>>
>> I do not know who "Othman Madjoudj" is. I am not aware of having a
>> co-maintainer for mosh.

Ah, appears to just be someone CC'd to all your bugs.

Unresponsive maintainer call still stands for them, though.  I've moved
the bug to a more appropriate component for them.

> (looking at mosh is on my TODO list, but I don't get notifications of
> failed builds... or at least I don't think I do)

A bug was filed against mosh at the time:
https://bugzilla.redhat.com/show_bug.cgi?id=1604884

Thanks,
--Robbie


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748636] perl-DBIx-Class-EncodedColumn-0.00017 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748636

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-DBIx-Class-EncodedColumn-0.00017-1.fc31 has been pushed to the Fedora 31
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-2019-d854b50520

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1749083] New: RFE: EPEL-8 builds of perl-Test-Object and other PPI dependencies

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1749083

Bug ID: 1749083
   Summary: RFE: EPEL-8 builds of perl-Test-Object and other PPI
dependencies
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Test-Object
  Assignee: tcall...@redhat.com
  Reporter: p...@city-fan.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com,
perl-devel@lists.fedoraproject.org,
rob.my...@gtri.gatech.edu, tcall...@redhat.com
  Target Milestone: ---
Classification: Fedora



Hi Spot,

I'm trying to build perl-PPI for EPEL-8 and there are still some missing
dependencies, one of which is perl-Test-Object. Also needed are
perl-Test-SubCalls and its dependency perl-Hook-LexWrap. I believe all of these
are maintained by you.

If you're not into doing EPEL-8 builds I'll be happy to do them myself. I'm
also happy to co-maintain these packages in Fedora (FAS: pghmcfc) if you like.

Cheers, Paul.

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Schedule for Thursday's FPC Meeting (2019-09-05 16:00 UTC)

2019-09-04 Thread James Antill
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-09-05 16:00 UTC in #fedora-meeting-1 on 
irc.freenode.net.

 Local time information (via. uitime):

= Day: Thursday ==
2019-09-05 09:00 PDT  US/Pacific
2019-09-05 12:00 EDT  --> US/Eastern <--
2019-09-05 16:00 UTC  UTC   
2019-09-05 17:00 BST  Europe/London 
2019-09-05 18:00 CEST Europe/Berlin 
2019-09-05 18:00 CEST Europe/Paris  
2019-09-05 21:30 IST  Asia/Calcutta 
 New Day: Friday -
2019-09-06 00:00 HKT  Asia/Hong_Kong
2019-09-06 00:00 +08  Asia/Singapore
2019-09-06 01:00 JST  Asia/Tokyo
2019-09-06 02:00 AEST Australia/Brisbane


 Links to all tickets below can be found at: 

https://pagure.io/packaging-committee/issues?status=Open=meeting

= Followups =

#topic #902 Cleanup & enhance spec files 
.fpc 902
https://pagure.io/packaging-committee/issue/902

#topic #904 Caret versioning 
.fpc 904
https://pagure.io/packaging-committee/issue/904

#topic #907 Which %__foo macros for executables are acceptable? 
.fpc 907
https://pagure.io/packaging-committee/issue/907

#topic #909 Suggest that linting/measuring-coverage is not for %check
.fpc 909
https://pagure.io/packaging-committee/issue/909

#topic #914 Automatic R runtime dependencies
.fpc 914
https://pagure.io/packaging-committee/issue/914

= Pull Requests =

#topic #894 Add rules for Cython 
https://pagure.io/packaging-committee/pull-request/894

#topic #903 Update Python guidelines for Fedora 31 
https://pagure.io/packaging-committee/pull-request/903

#topic #915 Modernize python spec file example 
https://pagure.io/packaging-committee/pull-request/915

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://pagure.io/packaging-committee/issues?status=Open=meeting

 If you would like to add something to this agenda, you can:
  * Reply to this e-mail
  * File a new ticket at: https://pagure.io/packaging-committee
  * E-mail me directly
  * Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Chris Murphy
On Wed, Sep 4, 2019 at 1:03 PM Chris Murphy  wrote:
>
> I'm skeptical of swapfiles for this use case, because it likely
> increases the chance for file system disk contention, see section
> 11.17
> https://www.kernel.org/doc/gorman/html/understand/understand014.html

Actually that looks outdated now.

https://patchwork.kernel.org/patch/10347293/

Btrfs since 5.0 also supports swapfiles by avoiding bmap, using
btrfs_swap_activate, the btrfs equivalent of iomap_swap_activate

-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Unresponsive maintainers: Alex Chernyakhovsky & Othman Madjoudj

2019-09-04 Thread Robbie Harwood
Hi Fedora,

I'm trying to contact Alex Chernyakhovsky and Othman Madjoudj, who are
the maintainers of mosh as far as I can tell.  I have started the
nonresponsive maintainer process due to lack of contact through bugzilla
mail; bugs are https://bugzilla.redhat.com/show_bug.cgi?id=1697355 and
https://bugzilla.redhat.com/show_bug.cgi?id=1749058 .

My primary concern is making sure that mosh doesn't get removed from the
distribution, since it's failed to build since fc29
https://bugzilla.redhat.com/show_bug.cgi?id=1604884

Per policy, a full bug list follows.

Alex Chernyakhovsky:
https://bugzilla.redhat.com/show_bug.cgi?id=1250413
https://bugzilla.redhat.com/show_bug.cgi?id=1558965
https://bugzilla.redhat.com/show_bug.cgi?id=1604884
https://bugzilla.redhat.com/show_bug.cgi?id=1749054

Othman Madjoudj:
https://bugzilla.redhat.com/show_bug.cgi?id=581132
https://bugzilla.redhat.com/show_bug.cgi?id=970972
https://bugzilla.redhat.com/show_bug.cgi?id=1570826
https://bugzilla.redhat.com/show_bug.cgi?id=1578165
https://bugzilla.redhat.com/show_bug.cgi?id=1605383
https://bugzilla.redhat.com/show_bug.cgi?id=1605543
https://bugzilla.redhat.com/show_bug.cgi?id=1613856
https://bugzilla.redhat.com/show_bug.cgi?id=1668653
https://bugzilla.redhat.com/show_bug.cgi?id=1668654
https://bugzilla.redhat.com/show_bug.cgi?id=1674509
https://bugzilla.redhat.com/show_bug.cgi?id=1686127
https://bugzilla.redhat.com/show_bug.cgi?id=1696430
https://bugzilla.redhat.com/show_bug.cgi?id=1697348
https://bugzilla.redhat.com/show_bug.cgi?id=1697355
https://bugzilla.redhat.com/show_bug.cgi?id=1710239
https://bugzilla.redhat.com/show_bug.cgi?id=1711202
https://bugzilla.redhat.com/show_bug.cgi?id=1737829
https://bugzilla.redhat.com/show_bug.cgi?id=1737958
https://bugzilla.redhat.com/show_bug.cgi?id=1741008
https://bugzilla.redhat.com/show_bug.cgi?id=1742597

Thanks,
--Robbie


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Chris Murphy
per cgroup swap file support
https://lwn.net/Articles/591495/

This might be interesting. What happens if swap is only assigned to
new unprivileged tasks? Your compile might take three days but it
doesn't make the GUI fall over? *shrug*

---
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Florian Weimer
* Kyle Marek:

> I'm finding that 32G is not necessarily sufficient for compiling clang
> itself. Similarly I've had a hard time compiling UnrealEngine from
> source. I usually see ld using up to 12G of memory to link each
> artifact. Using -j$(nproc) on a 16 VCPU system amplifies the issue. I
> rely on adding another 32G swap file to complete the job.

Out of curiosity, which ld do you use?  BFD ld, gold, or LLVM's?

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora 31 compose report: 20190904.n.0 changes

2019-09-04 Thread Fedora Branched Report
OLD: Fedora-31-20190903.n.0
NEW: Fedora-31-20190904.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   1
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   125.73 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -21.84 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: LXQt live x86_64
Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-31-20190904.n.0.iso
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-31-20190904.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  podman-2:1.5.1-2.17.dev.gitce64c14.fc31
Old package:  podman-2:1.5.1-2.16.dev.gitce64c14.fc31
Summary:  Manage Pods, Containers and Container Images
RPMs: podman podman-docker podman-manpages podman-remote podman-tests
Size: 125.73 MiB
Size change:  -21.84 KiB
Changelog:
  * Tue Aug 27 2019 Daniel J Walsh  - 2:1.5.1-2.17
  - Require crun rather then runc
  - Switch to crun by default for cgroupsV2 support



= DOWNGRADED PACKAGES =
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaned packages looking for new maintainers

2019-09-04 Thread Jerry James
On Mon, Sep 2, 2019 at 4:01 AM Miro Hrončok  wrote:
>  Package  (co)maintainers   Status 
> Change
> 
[snip]
> libsvmbesser82, orphan 5 weeks ago

I requested ownership of libsvm: https://pagure.io/releng/issue/8740
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Chris Murphy
On Wed, Sep 4, 2019 at 12:01 PM Kyle Marek  wrote:
>
> I'm finding that 32G is not necessarily sufficient for compiling clang
> itself. Similarly I've had a hard time compiling UnrealEngine from
> source. I usually see ld using up to 12G of memory to link each
> artifact. Using -j$(nproc) on a 16 VCPU system amplifies the issue. I
> rely on adding another 32G swap file to complete the job.

I setup swap on ZRAM device at 1.5X RAM. That was just as
intermittently unresponsive (seconds, and periods above 10 minutes)
GUI, to the degree using the laptop as a laptop was pointless. But,
webkitgtk build did complete with the default command, and in a
shorter time than with a swap partition on SSD (which became
sufficiently unresponsive even via ssh that I gave up and forced power
off).

But, I don't think I can recommend such a setup as a default
installation of Fedora Workstation. On a system with 32G RAM, that
would mean a 48G /dev/zram device for swap. If it completely filled
up, it would use ~24G of RAM, leaving 8GiB for compiling + OS +
workstation stuff. You are getting a huge swap device that's almost as
fast as RAM, but it's so fast that it means burning a huge amount of
CPU cycles on compression/decompression. And kswapd is not threaded,
it maxes out at 100% of a single core, and once it's there, that's it,
you can't scale beyond it.


> I'm now using an NVME SSD for my swap file. No more hangs for the most
> part! Usually if I lock up, it's for maybe a minute before OOM steps in.
>
> However, I'd definitely like to see a non-zram "solution" for use cases
> like this. Ultimately I'd like to see the use of traditional swap files
> to not hang a system even if it is placed on a md RAID array. I'm
> guessing that the long term fix is for OOM to happen sooner, and/or
> kernel schedulers to be improved, as mentioned elsewhere in this thread.
> Ideally this wouldn't require the use of systemd or cgroups to make it
> possible.

I'm skeptical of swapfiles for this use case, because it likely
increases the chance for file system disk contention, see section
11.17
https://www.kernel.org/doc/gorman/html/understand/understand014.html

And in heavy swap use and memory pressure, I already see evidence of
applications evicting their own executable code and constantly
re-reading it from disk. That's increasing the chance of IO pressure
resulting in stalls.

Incidental swap is fine, and I think it's possible to use either zram
or zswap to moderate the transition to a swap partition. But once this
grows to an aggressive swap dependency, the desktop is responsiveness
is lost.


-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[rpms/bugzilla] PR #2: Drop unused build dependency on Python 2

2019-09-04 Thread Emmanuel Seyman

eseyman merged a pull-request against the project: `bugzilla` that you are 
following.

Merged pull-request:

``
Drop unused build dependency on Python 2
``

https://src.fedoraproject.org/rpms/bugzilla/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: inotify-tools with dead upstream cannot be fixed in Fedora

2019-09-04 Thread Jan Kratochvil
On Mon, 02 Sep 2019 23:33:32 +0200, Richard W.M. Jones wrote:
> On Sun, Sep 01, 2019 at 09:33:29PM +0200, Jan Kratochvil wrote:
> > Fix stack overflow in: `inotifytools_replace_filename`
> > https://bugzilla.redhat.com/show_bug.cgi?id=1741472
> > 
> > Not sure how to fix this crashing bug. Upstream is dead while Fedora package
> > maintainer requires to upstream the fix first. A Catch 22.
> > 
> > Debian has the crasher fixed by an off-trunk simple patch, Fedora cannot?
> 
> I would start by pulling in the Debian fix into the Fedora package.

This is what I tried in the Bug above and I failed. So I have submitted
a request to become co-maintainer with no response so far.

(Besides that the Debian fix compared to my fix is a hack, not properly coded
from programming point of view. But I agree the Debian fix does work.)


> Then talk to the Debian folk and see if you can set up a simple git
> repo on one of the many free hosting services to collect these patches
> "upstream".

There is already upstream but its maintainer does not respond. So do you mean
to make a new upstream? Is it really required to push 2 characters of a fix to
Fedora package?


Jan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora-31-20190904.n.0 compose check report

2019-09-04 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 16/152 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-31-20190903.n.0):

ID: 442020  Test: x86_64 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/442020

Old failures (same test failed in Fedora-31-20190903.n.0):

ID: 441955  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/441955
ID: 441963  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/441963
ID: 441965  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/441965
ID: 441990  Test: x86_64 KDE-live-iso desktop_background
URL: https://openqa.fedoraproject.org/tests/441990
ID: 441991  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/441991
ID: 441993  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/441993
ID: 441995  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/441995
ID: 441997  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/441997
ID: 442024  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/442024
ID: 442031  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/442031
ID: 442057  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/442057
ID: 442062  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/442062
ID: 442066  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/442066
ID: 442067  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/442067
ID: 442068  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/442068
ID: 442071  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/442071

Soft failed openQA tests: 2/152 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-31-20190903.n.0):

ID: 442061  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/442061
ID: 442063  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/442063

Passed openQA tests: 114/152 (x86_64)

Skipped non-gating openQA tests: 21 of 154

Installed system changes in test x86_64 Server-boot-iso install_default: 
1 packages(s) removed since previous compose: fedora-release-notes
Previous test data: https://openqa.fedoraproject.org/tests/440571#downloads
Current test data: https://openqa.fedoraproject.org/tests/441926#downloads

Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 
1 packages(s) removed since previous compose: fedora-release-notes
Previous test data: https://openqa.fedoraproject.org/tests/440572#downloads
Current test data: https://openqa.fedoraproject.org/tests/441927#downloads

Installed system changes in test x86_64 Server-dvd-iso install_default_upload: 
System load changed from 0.08 to 0.22
Previous test data: https://openqa.fedoraproject.org/tests/440580#downloads
Current test data: https://openqa.fedoraproject.org/tests/441935#downloads

Installed system changes in test x86_64 KDE-live-iso install_default_upload: 
2 services(s) added since previous compose: 
dbus-:1.6-org.freedesktop.problems@0.service
  loaded active running dbus-:1.6-org.freedesktop.problems@0.service, 
pcscd.service
1 services(s) removed since previous compose: 
dbus-:1.7-org.freedesktop.problems@0.service
  loaded active running dbus-:1.7-org.freedesktop.problems@0.service
System load changed from 0.57 to 1.11
Previous test data: https://openqa.fedoraproject.org/tests/440623#downloads
Current test data: https://openqa.fedoraproject.org/tests/441978#downloads

Installed system changes in test x86_64 KDE-live-iso install_default@uefi: 
System load changed from 0.27 to 1.38
Previous test data: https://openqa.fedoraproject.org/tests/440625#downloads
Current test data: https://openqa.fedoraproject.org/tests/441980#downloads

Installed system changes in test x86_64 universal install_package_set_kde: 
System load changed from 2.21 to 0.58
Average CPU usage changed from 81.84761905 to 21.3667
Previous test data: https://openqa.fedoraproject.org/tests/440690#downloads
Current test data: https://openqa.fedoraproject.org/tests/442045#downloads
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel 

Re: Orphaned packages looking for new maintainers

2019-09-04 Thread Markku Korkeala

Fabio Valentini  writes:

> On Tue, Sep 3, 2019 at 5:41 PM Markku Korkeala  wrote:
>>
>> Miro Hrončok kirjoitti 2019-09-02 13:00:
>> > clojure   kushal, orphan, s4504kr, 1
>> > weeks ago
>> >   salimma, walters
>>
>> I would like to take clojure, filed a releng ticket:
>>
>> https://pagure.io/releng/issue/8732
>
> Be advised that clojure has failed to build since fedora 23, according to 
> koji.
> I wonder why it hasn't been retired at some point ...

Thanks for the warning. I already did a PR a while back, which would
have fixed the build issue and update to version 1.8.0, but it didn't
get merged. There is still work to do to update newer releases as
there are new build requirements to package.

Markku
> Fabio
>
>> BR,
>> Markku
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Better interactivity in low-memory situations

2019-09-04 Thread Kyle Marek
On 9/3/19 12:30 AM, John Harris wrote:
> On Tuesday, August 20, 2019 10:48:06 PM MST John Harris wrote:
>> On Sunday, August 18, 2019 4:33:47 AM MST Gordan Bobic wrote:
>>
>>> On Sun, Aug 11, 2019 at 10:36 AM  wrote:
>>>
 This seems like a distraction from the real goal here, which is to
 ensure Fedora remains responsive under heavy memory pressure,
>>>
>>> I think this is an overwhelmingly important point, and as somebody
>>> regularly working with ARM machines with tiny amounts of RAM, it is of
>>> considerable interest to me.
>>> I typically use CentOS because stability is important to me, but most
>>> worthwhile things filter to there, so I hope what I'm about to say is not
>>> _too_ deprecated.
>>>
>>> 1) Compile options
>>> From what I can tell from rpm macro options, default on C7 seems to be
>>> -O2.
>  -Os seems to help in most cases.
>>> Adding -ffunction-sections -fdata-sections to defaults can help
>>> considerably in producing smaller binaries, and is not the default.
>>> Linking with -Wl,--gc-sections helps a lot and is not the default
>>> Extensive stripping seems to already be the default (--strip-unneeded,
>>> removal of .comment and .note sections)
>>>
>>> 2) Runtime condiguration
>>> Default stack size is 8192 (ulimit -s). This unnecessarily eats a
>>> considerably amount of memory. I have yet to see anything that actually
>>> experiences problems with 1M.
>>>
>>> 3) zram
>>> This was mentioned earlier in the thread, and on most of my systems,
>>> memory constrained or otherwise, unless I have an overwhelming reason
>>> not to, I run with zram swap equal in size to RAM with lz4 compression
>>> and
>>> vm.swappiness=100. I typically see compression ratios between 2:1 and 3:1
>>> in zram, so on a system with, say, 10GB of RAM, it would provide 10GB of
>>> very fast swap at a cost of 3-5GB of RAM. This seems like a favourable
>>> trade off, especially on systems with extremely constrained RAM (e.g. ARM
>>> devices with 512MB of RAM).
>>>
>>> I'm sure there is more that can be done, but this seems like a good start
>>> as far as the cost / benefit is concerned.
>>
>> Python, Lua and a few other common programs can have issues with a stack
>> size  of 1MiB.
>>
>> -- 
>> John M. Harris, Jr. 
>> Splentity
>> https://splentity.com/
> I would also like to add that I don't see how it's even possible to run into 
> a 
> low-memory scenario on a system with 10 GiB (That's a *lot* of memory! I run 
> on a Core 2 Duo based system that can support a max of 8 GiB as my daily 
> driver.) often enough to have a problem with oom_killer.

I'm finding that 32G is not necessarily sufficient for compiling clang
itself. Similarly I've had a hard time compiling UnrealEngine from
source. I usually see ld using up to 12G of memory to link each
artifact. Using -j$(nproc) on a 16 VCPU system amplifies the issue. I
rely on adding another 32G swap file to complete the job.

I'm now using an NVME SSD for my swap file. No more hangs for the most
part! Usually if I lock up, it's for maybe a minute before OOM steps in.

However, I'd definitely like to see a non-zram "solution" for use cases
like this. Ultimately I'd like to see the use of traditional swap files
to not hang a system even if it is placed on a md RAID array. I'm
guessing that the long term fix is for OOM to happen sooner, and/or
kernel schedulers to be improved, as mentioned elsewhere in this thread.
Ideally this wouldn't require the use of systemd or cgroups to make it
possible.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: [ABRT] Intent to put abrt-hook-ccpp to rest

2019-09-04 Thread jfilak

If you no longer plan to add the feature for generating backtraces without
writing core files to disk,

then abrt-hook-ccpp is pretty much useless - IMHO.



-- Původní e-mail --
Od: Ernestas Kulik 
Komu: devel@lists.fedoraproject.org
Datum: 4. 9. 2019 10:06:05
Předmět: [ABRT] Intent to put abrt-hook-ccpp to rest
"Hello, fellow humans,

Since nowadays pretty much everyone has systemd-coredump in their
/proc/sys/kernel/core_pattern[1][2], I would like to remove the custom
ABRT hook that does largely the same thing.

If anyone has made a conscious decision to keep using it, please let us 
know.

[1] - https://fedoraproject.org/wiki/Changes/coredumpctl
[2] -
https://abrt.github.io/abrt/systemd/core_pattern/2017/03/07/fedora-26-
change/

--
Ernestas Kulik
Associate Software Engineer - Base Operating Systems (Core
Services/ABRT)
Red Hat Czech, s.r.o.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of
-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
fedoraproject.org
"___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread Robbie Harwood
Alexander Bokovoy  writes:

> On ke, 04 syys 2019, alcir...@gmail.com wrote:
>>On Mon, 2019-09-02 at 17:14 +0200, Dario Lesca wrote:
>>>
>>> After few minutes almost everything work well, except for a thing ...
>>> all windows PC cannot access to others windows PC.
>>
>> Hey Dario.
>> Since in recent days I was testing and evaluating Samba as an AD domain
>> controller, but using another distro, I decided to configure a F30
>> server, and try to test what are you experiencing.
>>
>> I can see a lot of the messages you reported:
>>
>> Sep 03 01:14:09 adc1 krb5kdc[4059](info): TGS_REQ (5 etypes {aes256-
>> cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17),
>> DEPRECATED:arcfour- hmac(23), DEPRECATED:arcfour-hmac-exp(24),
>> (-135)}) 10.97.69.24: ISSUE: authtime 1567589350, etypes
>> {rep=aes256-cts-hmac-sha1-96(18), tkt=aes256-cts-hmac-sha1-96(18),
>> ses=aes256-cts-hmac-sha1-96(18)}, WINUNO$@MY.LAN for
>> krbtgt/my@my.lan
>
> This is not an issue. The message above is normal. It says that WINUNO
> machine asked for an initial Kerberos ticket granting ticket, asking for
> one of 5 encryption types and got it granted with AES256. The textual
> description of those encryption types is a feature we added upstream
> this year. DEPRECATED: prefix tells that a particular encryption type is
> weak and is marked for removal in future versions of Kerberos (there are
> RFCs for this removal).

Indeed, they are https://tools.ietf.org/html/rfc8429 and
https://tools.ietf.org/html/rfc6649

The changes are part of
https://fedoraproject.org/wiki/Changes/krb5_crypto_modernization

"Deprecated" has its usual meaning in this context: you should look into
migrating to another enctype if at all possible, and disabling support
for it when you have (because it will be gone in the future, probably
sometime next year).

Thanks,
--Robbie


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Open NeuroFedora Meeting agenda for 2019-09-05

2019-09-04 Thread Ankur Sinha
Hello,

Please join us for the weekly Open NeuroFedora team meeting tomorrow.
Details below:

- Forwarded message -
> 
> Hi all!
> 
> You are kindly invited to attend the Open NeuroFedora team meeting this week
> on Thursday (tomorrow) at 1500UTC in #fedora-neuro on IRC (Freenode):
> 
>         https://webchat.freenode.net/?channels=#fedora-neuro
> 
> You can convert the meeting time to your local time using:  
> $ date --date='TZ="UTC" 1500 next Thu'
> or use this link: 
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting=20190905T15=1440=1
> 
> The agenda for the meeting is:
> - Introductions and roll call
> - Pagure tickets related to our progress on computational neuroscience tools
> https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
> - Planning for the next phase of NeuroFedora tasks
> - Neuroscience query of the week
> - Next meeting day and chair
> - Open floor
> 
> Please go through the tickets on Pagure and mark and other tickets that need
> to be disccused with the "S: Next meeting" tag.
> 
> Hope to see you there!
> 
> 
> -- 
> Danny Lee  <>

> 
- End forwarded message -

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: New version of Copr

2019-09-04 Thread John Harris
On Wednesday, September 4, 2019 5:28:08 AM MST Dominik Turecek wrote:
> Hello.
> 
> Today, we have released a new version of Copr.
> Main highlights from the release was the addition
> of discussion panels in Copr projects and speed
> optimization of front page.
> 
> For more information, see:
>  https://bodhi.fedoraproject.org/updates/FEDORA-2019-4aca9d983d
> 
> Dominik

Has the new version been tested without "discussion"s? If not, I would imagine 
it'd be much faster with that feature disabled.

Does the inefficiency of that feature outweigh its usefulness? Why does it 
rely on Discourse for that feature?

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1744678] [RFE] Can perl-Linux-Pid be branched for EPEL8

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1744678

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2019-c90987b8fe has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c90987b8fe

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: BackupPC selinux help

2019-09-04 Thread John Florian

On 2019-09-04 10:40, Richard Shaw wrote:
On Wed, Sep 4, 2019 at 9:36 AM John Florian > wrote:


On 2019-08-30 13:51, Richard Shaw wrote:
> He's already tried restorecon, changed from a symlink to a bind
mount
> (for the backup root)...

Maybe a dumb Q, but have you tried doing the same?  Maybe it's
your host
that's not per defaults.


I'm not quite sure what you mean. I don't have the problem with my 
install and I haven't been able to reproduce the problem.
I mean have *you* ran restorecon?  Could it be that your host is simply 
mislabeled?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Minimization Objective report

2019-09-04 Thread Adam Samalik
This is the Minimization Objective [0] update.

Status: Discovery phase

== Feedback Pipeline ==

A prototype is live [1]!

It shows packages and an overall size of use cases we are focusing on,
installed on top of various Fedora bases.

In addition to showing the current status, it will be also pushing package
lists into git. By that, we'll get free web UI (Pagure or Github) showing
differences between any points in time.

Use cases and bases can be easily configured [2].

A blog post is still coming!

== How to get involved ==

See if there is anything interesting to you on action plan [42], or reach
out with something you think is useful but is missing there. Open a ticket
in the tracker [43] or discuss in #fedora-devel on IRC.

Cheers,
Adam


[0] Objective: https://docs.fedoraproject.org/en-US/minimization/
[1] Feedback Pipeline prototype: https://minimization.github.io/reports/
[2] Feedback Pipeline config:
https://pagure.io/minimization/feedback-pipeline-config
[42] Action plan:
https://docs.fedoraproject.org/en-US/minimization/action-plan/
[43] Issue tracker: https://pagure.io/minimization/issues

-- 

Adam Šamalík
---
Senior Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Minimization Team Meeting notes 2019-09-04

2019-09-04 Thread Adam Samalik
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-04/minimization.2019-09-04-15.00.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-04/minimization.2019-09-04-15.00.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-04/minimization.2019-09-04-15.00.log.html


#fedora-meeting-1: Minimization Team Meeting



Meeting started by asamalik at 15:00:33 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-04/minimization.2019-09-04-15.00.log.html
.



Meeting summary
---
* Roll call  (asamalik, 15:00:33)

* === Admin ===  (asamalik, 15:06:19)

* === Focus & what's next? ===  (asamalik, 15:14:45)
  * Feedback Pipeline prototype deployed, a note about coming to the
devel list  (asamalik, 15:20:29)
  * LINK: https://minimization.github.io/reports/   (asamalik, 15:20:36)
  * We'll be tracking use cases that we want to minimize both in the
tracker and in the Feedback Pipeline reports  (asamalik, 15:21:07)
  * looking into CoreOS this Friday, findings coming next week!
(asamalik, 15:23:24)
  * looking into IoT  (asamalik, 15:23:32)

* === Open Floor ===  (asamalik, 15:37:25)

Meeting ended at 15:45:54 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* asamalik (44)
* jaruga (16)
* tdawson (14)
* zodbot (11)
* lorbus (5)
* ignatenkobrain (1)
* salimma (0)
* feborges (0)
* pbrobinson (0)
* zbyszek (0)
* Son_Goku (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 

Adam Šamalík
---
Senior Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unresponsive Maintainer: Chitlesh Goorah

2019-09-04 Thread Geoffrey Marr
Chitlesh,

Just to confirm, you meant "Back in 2010 I mentioned that I could*n't*
continue as a fedora developer due to time constraints.", not how you wrote
it above?

Geoff Marr
IRC: coremodule


On Wed, Sep 4, 2019 at 5:35 AM Chitlesh Goorah  wrote:

> Hello everyone,
>
> Back in 2010 I mentioned that I could continue as a fedora developer due
> to time constraints.
>
> Please do take over FEL.
>
> Cheers
> Chitlesh
>
> Sent from my iPhone
>
> On 2 Sep 2019, at 18:31, Geoffrey Marr  wrote:
>
> Hi devel-list,
>
> I am trying to contact Chitlesh Goorah [0], as he is the maintainer of the
> Fedora Electronics Lab Spin [1]. The spin desperately needs some love and
> maintenance. Does anyone know how to contact him? I have reached out to him
> three times in total, once in 2016, and again twice in 2019 and haven't
> heard back. I have started the unresponsive maintainer process, here is a
> link to the Bugzilla bug [2]. After a week of this mail being on the list,
> I will open a FESCo ticket.
>
> Thanks,
> Geoff Marr
> IRC: coremodule
>
> [0] https://fedoraproject.org/wiki/User:Chitlesh
> [1] https://fedoraproject.org/wiki/Electronic_Lab?rd=ElectronicLab_Spin
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1739872
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1744783] (RFE) EPEL8 branch of perl-Net-Netmask

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1744783

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2019-641abd1546 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-641abd1546

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: BackupPC selinux help

2019-09-04 Thread Richard Shaw
On Wed, Sep 4, 2019 at 9:36 AM John Florian  wrote:

> On 2019-08-30 13:51, Richard Shaw wrote:
> > He's already tried restorecon, changed from a symlink to a bind mount
> > (for the backup root)...
>
> Maybe a dumb Q, but have you tried doing the same?  Maybe it's your host
> that's not per defaults.
>

I'm not quite sure what you mean. I don't have the problem with my install
and I haven't been able to reproduce the problem.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: BackupPC selinux help

2019-09-04 Thread John Florian

On 2019-08-30 13:51, Richard Shaw wrote:
He's already tried restorecon, changed from a symlink to a bind mount 
(for the backup root)...



Maybe a dumb Q, but have you tried doing the same?  Maybe it's your host 
that's not per defaults.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


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

2019-09-04 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 385  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d   
condor-8.6.11-1.el7
 161  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294   
cinnamon-3.6.7-5.el7
 127  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80   
python-gnupg-0.4.4-1.el7
 125  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b   
bubblewrap-0.3.3-2.el7
  61  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-12067fc897   
dosbox-0.74.3-2.el7
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dea2d705d0   
python-mitogen-0.2.8-1.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b4713b164c   
chromium-76.0.3809.132-1.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ca3444781e   
perl-SOAP-Lite-1.10-2.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-954cf3770a   
seamonkey-2.49.5-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9bc2214140   
nsd-4.2.2-1.el7
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9166ad1315   
cobbler-2.8.5-0.1.el7


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

cube-4.4.4-1.el7
libmodulemd2-2.8.0-1.el7
otf2-2.2-4.el7
scalasca-2.5-3.el7
scorep-6.0-4.el7

Details about builds:



 cube-4.4.4-1.el7 (FEDORA-EPEL-2019-edb0c7ed8f)
 CUBE Uniform Behavioral Encoding generic presentation component

Update Information:

Update to the current version of the Scalasca toolset.  Changelogs:  otf2:
https://www.vi-hps.org/cms/upload/packages/otf2/otf2-2.2-ChangeLog.txt  scorep:
https://www.vi-hps.org/cms/upload/packages/scorep/scorep-6.0-ChangeLog.txt
cube: http://scalasca.org/scalasca/front_content.php?idart=1194  scalasca:
https://scalasca.org/scalasca/front_content.php?idart=1072

ChangeLog:

* Thu Aug  1 2019 Dave love  - 4.4.4-1
- New version
* Wed Jul 24 2019 Fedora Release Engineering  - 
4.4.3-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
* Thu Mar 21 2019 Dave Love  - 4.4.3-1
- New version
- Drop qt patch
* Thu Jan 31 2019 Fedora Release Engineering  - 
4.4.2-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Wed Jan 16 2019 Dave Love  - 4.4.2-4
- Add empty %files so cube-devel actually built
* Wed Jan 16 2019 Dave Love  - 4.4.2-3
- Remove /usr/lib64/libcube4gui.so from cube-libs
* Mon Dec  3 2018 Dave Love  - 4.4.2-2
- Adapt to el8, with qt5
- Add guilib{,-devel} sub-packages really to separate GUI dependency
- Add missing license files
* Mon Oct 22 2018 Dave Love  - 4.4.2-1
- Update to cubew 4.4.1, cubelib and cubeGUI 4.4.2
* Mon Oct 22 2018 Dave Love  - 4.4-6
- Avoid rpath in -config program ldflags
- Only ship one copy of .cubex example files
* Fri Oct 12 2018 Dave Love  - 4.4-5
- Bump release for f28 rebuild
* Tue Jul 31 2018 Florian Weimer  - 4.4-4
- Rebuild with fixed binutils
* Fri Jul 27 2018 Dave Love  - 4.4-3
- Add .abignore file
- Fix desktop file
- Move libcube4gui to cube package to avoid cube-libs requiring Qt
* Thu Jul 12 2018 Fedora Release Engineering  - 4.4-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Mon May 14 2018 Dave Love  - 4.4-1
- New version
- Considerably restructured for new source structure, but keeping the
  same built packages
* Wed Feb  7 2018 Fedora Release Engineering  - 
4.3.5-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Aug  2 2017 Fedora Release Engineering  - 
4.3.5-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering  - 
4.3.5-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Wed May 31 2017 Dave Love  - 4.3.5-1
- Update to 4.3.5 (#1456614)
* Mon May 15 2017 Fedora Release Engineering  
- 4.3.4-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_27_Mass_Rebuild
* Fri Feb 10 2017 Fedora Release Engineering  - 
4.3.4-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Mon Jan  9 2017 Kalev Lember  - 4.3.4-6
- Fix icon path in the desktop file
* Fri Oct 21 2016 Orion Poplawski  - 4.3.4-5
- Add patch to not wrap includes in extern "C" {}
* Tue May 10 2016 Dave Love  - 4.3.4-4
- Run ldconfig for both main as well as libs (for libgraphwidgetcommon-plugin)
* Mon May  9 2016 Dave Love  - 4.3.4-3
- Run ldconfig for libs package, not main
* Thu May  5 2016 Dave Love  - 4.3.4-2
- Have cube require matching cube-libs
- Don't do network check for new version
* Wed May  4 2016 Dave Love  - 4.3.4-1
- Update to 4.3.4
- Adjust for desktop and module files removed from distribution
- Remove xerces from configure
- Reinstate smp make
* Wed Feb  3 2016 Fedora 

[Bug 1748856] [RFE] EPEL8 branch of perl-Sub-Quote

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748856

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2019-95e264eabc has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-95e264eabc

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


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

2019-09-04 Thread updates
The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fabd190d13   
clamav-0.101.4-1.el8


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

clide-0.9-23.20160305git11c0895.el8
colordiff-1.0.18-6.el8
crudini-0.9.3-1.el8
libisds-0.10.8-6.el8
pcllib-1.12-13.el8
radcli-1.2.11-3.el8
synergy-1.10.2-1.el8
txt2regex-0.8-21.el8
whowatch-1.8.6-5.el8

Details about builds:



 clide-0.9-23.20160305git11c0895.el8 (FEDORA-EPEL-2019-7c7e4e299c)
 Color and style highlighting program for text

Update Information:

Initial package for EPEL 8

References:

  [ 1 ] Bug #1747759 - Add clide to EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1747759




 colordiff-1.0.18-6.el8 (FEDORA-EPEL-2019-d2da30fa60)
 Color terminal highlighter for diff files

Update Information:

Initial package for EPEL 8

References:

  [ 1 ] Bug #1747760 - Add colordiff to EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1747760




 crudini-0.9.3-1.el8 (FEDORA-EPEL-2019-446b141b65)
 A utility for manipulating ini files

Update Information:

Latest upstream: python 3 support




 libisds-0.10.8-6.el8 (FEDORA-EPEL-2019-1058f02ef9)
 Library for accessing the Czech Data Boxes

Update Information:

This errata brings you a library for accessing the Czech Data Boxes.




 pcllib-1.12-13.el8 (FEDORA-EPEL-2019-37394a6c11)
 Portable Coroutine Library (PCL)

Update Information:

Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild




 radcli-1.2.11-3.el8 (FEDORA-EPEL-2019-1658304468)
 RADIUS protocol client library

Update Information:

Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild




 synergy-1.10.2-1.el8 (FEDORA-EPEL-2019-710c6c049d)
 Share mouse and keyboard between multiple computers over the network

Update Information:

Build synergy 1 for epel-8




 txt2regex-0.8-21.el8 (FEDORA-EPEL-2019-e214516218)
 Regular expression wizard that converts human sentences to regexes

Update Information:

Initial package for EPEL 8

References:

  [ 1 ] Bug #1747762 - Add txt2regex to EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1747762




 whowatch-1.8.6-5.el8 (FEDORA-EPEL-2019-e7d8258f87)
 Display information about users currently logged on

Update Information:

Initial package for EPEL 8

References:

  [ 1 ] Bug #1747763 - Add whowatch to EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1747763



[Bug 1748877] perl-Sys-Virt-5.7.0 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748877

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Sys-Virt-5.7.0-1.fc32
 Resolution|--- |RAWHIDE
Last Closed||2019-09-04 13:56:49



-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748910] perl-DBD-Mock-1.46 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748910

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-DBD-Mock-1.46-1.fc32
 Resolution|--- |RAWHIDE
Last Closed||2019-09-04 13:47:49



--- Comment #2 from Petr Pisar  ---
An enhancement release safer for Rawhide only.

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748754] [RFE] EPEL8 branch of perl-Test-UseAllModules

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748754

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2019-64360711cd has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-64360711cd

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Intent to orphan php-gettext-gettext

2019-09-04 Thread Randy Barlow
On Wed, 2019-09-04 at 11:12 +0530, Sundeep Anand wrote:
> Hi Randy,
> 
> I have some interest maintaining it.

Is your FAS account sundeepanand? If so, it doesn't appear that you are
a Fedora packager at the moment.


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748636] perl-DBIx-Class-EncodedColumn-0.00017 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748636



--- Comment #1 from Fedora Update System  ---
FEDORA-2019-d854b50520 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d854b50520

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748928] New: perl-PDL-2.19.0-8 FTBFS: proj-nad dependency does not exist

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748928

Bug ID: 1748928
   Summary: perl-PDL-2.19.0-8 FTBFS: proj-nad dependency does not
exist
   Product: Fedora
   Version: 31
Status: NEW
 Component: perl-PDL
  Assignee: jples...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: caillon+fedoraproj...@gmail.com,
john.j5l...@gmail.com, jples...@redhat.com,
ka...@ucw.cz, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com
  Target Milestone: ---
Classification: Fedora



perl-PDL-2.19.0-8 fails to build in F31 because proj-nad does not exist there.

According to proj-5.2.0-5.fc31 changelog, proj-nad package was renamed to
proj-datumgrid.

Please note that in F32 is a rebased proj-6.2.0 with a different API.

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread Dario Lesca
Il giorno mer, 04/09/2019 alle 12.48 +0200, alcir...@gmail.com ha
scritto:
> Accessing a folder shared by windows machine 1 from windows machine
> 2doesn't work... if I use the computer name or the fqdn (name
> resolutionworks using nslookup). But if I use the IP address I'm able
> to accessthe shared folder.

This is also my problem: "win to win access deny" (after a
classicupdate)

Then the problem is not caused by classicupdate, also create a new DC,
new user and join new machine to domain you get same problem

Pleas, add this info to bugzilla.

Thanks

-- 
Dario Lesca
(inviato dal mio Linux Fedora 30 Workstation)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaning pylint and its requirements python-astroid and python-lazy-object-proxy

2019-09-04 Thread Gwyn Ciesla via devel
Thank you!


-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, September 4, 2019 8:07 AM, Christian Dersch 
 wrote:

> Am 04.09.19 um 14:37 schrieb Gwyn Ciesla via devel:
> 

> > I will. FAS: limb
> 

> Thanks! You own the packages now.
> 

> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748636] perl-DBIx-Class-EncodedColumn-0.00017 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748636

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
   Fixed In Version||perl-DBIx-Class-EncodedColu
   ||mn-0.00017-1.fc32



-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: New version of Copr

2019-09-04 Thread Miroslav Suchý
Dne 04. 09. 19 v 14:44 Kamil Paral napsal(a):
> 
> The discussion page is a neat idea. For some projects, I see "start 
> discussion" button, but for others, I see just
> "Loading Discussion..." that eventually changes to "Error embedding".

Yes, the loading takes too long when the topic has to be created and the 
Discourse javascript times out.
If you reload the page, it should load correctly since then.

This is a case of old projects. Or projects which should not be shown on front 
page.
All new projects should have created topic on Discussion.f.o in advance within 
60 seconds as it consume our RSS feed.

-- 
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaning pylint and its requirements python-astroid and python-lazy-object-proxy

2019-09-04 Thread Christian Dersch


Am 04.09.19 um 14:37 schrieb Gwyn Ciesla via devel:

I will. FAS: limb




Thanks! You own the packages now.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaned packages looking for new maintainers

2019-09-04 Thread Fabio Valentini
On Wed, Sep 4, 2019 at 2:47 PM Miro Hrončok  wrote:
>
> On 04. 09. 19 14:12, Fabio Valentini wrote:
> > Be advised that clojure has failed to build since fedora 23, according to 
> > koji.
> > I wonder why it hasn't been retired at some point ...
>
> The mass rebuild was not attempted at all. Maybe this is because:
>
> https://pagure.io/releng/issue/8601

I don't think this is the same issue. I checked out the dist-git repo
for clojure and the sources can be downloaded from the lookaside cache
just fine.
That doesn't change the fact that it *really* fails to build from
source on fedora 29+, according to koschei.

Fabio

> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Tom Hughes

On 04/09/2019 14:00, Petr Pisar wrote:

On 2019-09-04, Tom Hughes  wrote:

On 04/09/2019 13:40, Petr Pisar wrote:


I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
changed libproj soname from libproj.so.13 to libproj.so.15.


This may be a significant problem as I believe 6.x removes the
old 4.x API which was only deprecated before and some of the
dependants may still be using it...


Indeed. The API has changed. At least header files:


I suspect that is just detail - you normally either
include proj_api.h or proj.h depending on whether you want
the old or new interface and and they are still there.

I think most of it is the new C++ API which is in
addition to the C APIs.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Petr Pisar
On 2019-09-04, Tom Hughes  wrote:
> On 04/09/2019 13:40, Petr Pisar wrote:
>
>> I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
>> changed libproj soname from libproj.so.13 to libproj.so.15.
>
> This may be a significant problem as I believe 6.x removes the
> old 4.x API which was only deprecated before and some of the
> dependants may still be using it...
>
Indeed. The API has changed. At least header files:

$ rpmdiff -i 5 -i S -i T proj-devel-*
S.5.SUMMARY
S.5.URL
removed REQUIRES libproj.so.13()(64bit)
removed REQUIRES proj(x86-64) = 5.2.0-5.fc31
added   REQUIRES libproj.so.15()(64bit)
added   REQUIRES proj(x86-64) = 6.2.0-1.fc32
removed PROVIDES pkgconfig(proj) = 5.2.0
removed PROVIDES proj-devel(x86-64) = 5.2.0-5.fc31
added   PROVIDES pkgconfig(proj) = 6.2.0
added   PROVIDES proj-devel(x86-64) = 6.2.0-1.fc32
added   /usr/include/proj
added   /usr/include/proj/common.hpp
added   /usr/include/proj/coordinateoperation.hpp
added   /usr/include/proj/coordinatesystem.hpp
added   /usr/include/proj/crs.hpp
added   /usr/include/proj/datum.hpp
added   /usr/include/proj/io.hpp
added   /usr/include/proj/metadata.hpp
added   /usr/include/proj/nn.hpp
added   /usr/include/proj/util.hpp
added   /usr/include/proj_constants.h
added   /usr/include/proj_experimental.h
added   /usr/include/proj_json_streaming_writer.hpp
added   /usr/include/proj_symbol_rename.h
removed /usr/include/projects.h
added   /usr/share/proj/projjson.schema.json

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Tom Hughes

On 04/09/2019 13:51, Tom Hughes wrote:

On 04/09/2019 13:40, Petr Pisar wrote:


I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
changed libproj soname from libproj.so.13 to libproj.so.15.


This may be a significant problem as I believe 6.x removes the
old 4.x API which was only deprecated before and some of the
dependants may still be using it...


I think they might have changed this from the original plan.

According to https://proj.org/news.html#id54 the proj_api.h interface is
still there but now requires the ACCEPT_USE_OF_DEPRECATED_PROJ_API_H
define.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Richard Shaw
On Wed, Sep 4, 2019 at 7:52 AM Tom Hughes  wrote:

>
> > A similar issue is in Fedora 31 where the rebuilds should go to proj
> > update .
>
> Doing it in F31 this late is especially problematic...
>

Looks like the update should be unpushed then...

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Fabio Valentini
On Wed, Sep 4, 2019 at 2:41 PM Petr Pisar  wrote:
>
> I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
> changed libproj soname from libproj.so.13 to libproj.so.15.

I don't think this soname bump even happened by accident, because the
.so file names %files entries in the .spec file were explicitly
adapted to the changed version number ...

Do some people really just blatantly ignore the current updates policy [0]?

It explicitly states that ABI bumps should be announced a week before
they are pushed to *rawhide* to coordinate with dependent packages,
and that they should be "avoided if at all possible" in branched ...

Fabio

[0]: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/

> x86_64 Fedora 32 contains these packages needs rebuilding:
>
> # dnf --quiet repoquery --whatrequires 'libproj.so.13()(64bit)' --source  | 
> sed 's/-[^-]*-[^-]*$//' | sort -f -u | grep -v '^proj$'
> gdal
> grass
> libgeotiff
> libspatialite
> mapnik
> mapserver
> merkaartor
> ncl
> ogdi
> osm2pgsql
> perl-Geo-Proj4
> perl-PDL
> postgis
> pyproj
> python-cartopy
> qgis
> qlandkartegt
> qmapshack
> qt-mobility
> R-rgdal
> saga
> spatialite-gui
> vtk
>
> A similar issue is in Fedora 31 where the rebuilds should go to proj
> update .
>
> -- Petr
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Unannounced libproj soname bump

2019-09-04 Thread Tom Hughes

On 04/09/2019 13:40, Petr Pisar wrote:


I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
changed libproj soname from libproj.so.13 to libproj.so.15.


This may be a significant problem as I believe 6.x removes the
old 4.x API which was only deprecated before and some of the
dependants may still be using it...


mapnik


This one is mine. I'll try and have a look later but I fear this
in particular may need patching significantly to use the new API.


A similar issue is in Fedora 31 where the rebuilds should go to proj
update .


Doing it in F31 this late is especially problematic...

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaned packages looking for new maintainers

2019-09-04 Thread Miro Hrončok

On 04. 09. 19 14:12, Fabio Valentini wrote:

Be advised that clojure has failed to build since fedora 23, according to koji.
I wonder why it hasn't been retired at some point ...


The mass rebuild was not attempted at all. Maybe this is because:

https://pagure.io/releng/issue/8601

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748913] New: Please build perl-Email-Date-Format for EPEL 8

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748913

Bug ID: 1748913
   Summary: Please build perl-Email-Date-Format for EPEL 8
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-Email-Date-Format
  Assignee: tcall...@redhat.com
  Reporter: jpazdzi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
tcall...@redhat.com
Blocks: 1748037
  Target Milestone: ---
Classification: Fedora



Description of problem:

We have a request to build perl-MIME-Lite in EPEL 8 (bug 1748037) which is a
build dependency of perl-SOAP-Lite in EPEL 8 (requested in bug 1744683). It has
a build dependency on perl(Email::Date::Format):
https://koji.fedoraproject.org/koji/taskinfo?taskID=37454621

Please consider building perl-Email-Date-Format in EPEL 8.

Steps to Reproduce:
1. Search for package providing perl(Email::Date::Format) in EPEL 8.

Actual results:

No perl-Email-Date-Format in EPEL 8.

Expected results:

perl-MIME-Lite-3.030-16.el8 in EPEL 8.

Additional info:

Please let me know if you are not interested in maintaining the package on EPEL
8.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1748037
[Bug 1748037] Please build perl-MIME-Lite for EPEL 8
-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: New version of Copr

2019-09-04 Thread Kamil Paral
On Wed, Sep 4, 2019 at 2:29 PM Dominik Turecek  wrote:

> Hello.
>
> Today, we have released a new version of Copr.
> Main highlights from the release was the addition
> of discussion panels in Copr projects and speed
> optimization of front page.
>

The discussion page is a neat idea. For some projects, I see "start
discussion" button, but for others, I see just "Loading Discussion..." that
eventually changes to "Error embedding".
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread Dario Lesca
Il giorno mer, 04/09/2019 alle 14.27 +0300, Alexander Bokovoy ha
scritto:
> I still need to see network traces that show breakage between Windows
> clients.

I have update the filezilla bug with tcpdump pcap

-- 
Dario Lesca
(inviato dal mio Linux Fedora 30 Workstation)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Unannounced libproj soname bump

2019-09-04 Thread Petr Pisar
I noticed proj-5.2.0 was rebased to 6.2.0 in Fedora ≥ 31. This rebase
changed libproj soname from libproj.so.13 to libproj.so.15.

x86_64 Fedora 32 contains these packages needs rebuilding:

# dnf --quiet repoquery --whatrequires 'libproj.so.13()(64bit)' --source  | sed 
's/-[^-]*-[^-]*$//' | sort -f -u | grep -v '^proj$'
gdal
grass
libgeotiff
libspatialite
mapnik
mapserver
merkaartor
ncl
ogdi
osm2pgsql
perl-Geo-Proj4
perl-PDL
postgis
pyproj
python-cartopy
qgis
qlandkartegt
qmapshack
qt-mobility
R-rgdal
saga
spatialite-gui
vtk

A similar issue is in Fedora 31 where the rebuilds should go to proj
update .

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748910] New: perl-DBD-Mock-1.46 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748910

Bug ID: 1748910
   Summary: perl-DBD-Mock-1.46 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-DBD-Mock
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jan.pra...@gmail.com, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.46
Current version/release in rawhide: 1.45-20.fc31
URL: http://search.cpan.org/dist/DBD-Mock/

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/2805/

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748910] perl-DBD-Mock-1.46 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748910



--- Comment #1 from Upstream Release Monitoring 
 ---
An unexpected error occurred while creating the scratch build and has been
automatically reported. Sorry!

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Orphaning pylint and its requirements python-astroid and python-lazy-object-proxy

2019-09-04 Thread Gwyn Ciesla via devel
I will. FAS: limb

Sent from ProtonMail mobile

 Original Message 
On Sep 4, 2019, 4:54 AM, Christian Dersch wrote:

> Hi,
>
> I intend to orphan pylint, python-astroid and python-lazy-object-proxy
> (both required by pylint), anybody interested in taking them?
>
> Greetings
>
> Christian
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[rpms/bugzilla] PR #2: Drop unused build dependency on Python 2

2019-09-04 Thread Miro Hrončok

churchyard opened a new pull-request against the project: `bugzilla` that you 
are following:
``
Drop unused build dependency on Python 2
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/bugzilla/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


New version of Copr

2019-09-04 Thread Dominik Turecek
Hello.

Today, we have released a new version of Copr.
Main highlights from the release was the addition
of discussion panels in Copr projects and speed
optimization of front page.

For more information, see:
 https://bodhi.fedoraproject.org/updates/FEDORA-2019-4aca9d983d

Dominik
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread Dario Lesca
Il giorno mer, 04/09/2019 alle 12.48 +0200, alcir...@gmail.com ha
scritto:
> P.S. if this list is not the right place to discuss such topic, we
> cango elsewhere.
I have open this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1748860

-- 
Dario Lesca
(inviato dal mio Linux Fedora 30 Workstation)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaned packages looking for new maintainers

2019-09-04 Thread Fabio Valentini
On Tue, Sep 3, 2019 at 5:41 PM Markku Korkeala  wrote:
>
> Miro Hrončok kirjoitti 2019-09-02 13:00:
> > clojure   kushal, orphan, s4504kr, 1
> > weeks ago
> >   salimma, walters
>
> I would like to take clojure, filed a releng ticket:
>
> https://pagure.io/releng/issue/8732

Be advised that clojure has failed to build since fedora 23, according to koji.
I wonder why it hasn't been retired at some point ...

Fabio

> BR,
> Markku
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Looking for maintainers of Bazaar / Breeze (bzr / brz)

2019-09-04 Thread Miro Hrončok

Hello,

it seems that the current maintainers of Bazaar (bzr) are not likely interested 
anymore in the package.


It is mostyl dead upstream, depends on Python 2 and brings a quite a stack of 
required packages.


There is s Python 3 compatible fork called Breeze (brz).
I've prepared the spec file for Breeze, but I don't have interest in maintaining 
it. Is there any volunteer to maintain Bazaar / Breeze?


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

Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Intend to orphan i3 and some related packages

2019-09-04 Thread Christian Dersch


Am 04.09.19 um 13:49 schrieb Dan Čermák:

Christian Dersch  writes:


Am 04.09.19 um 12:36 schrieb Dan Čermák:

Thanks! i3 packages are yours now. Are you also interested in dzen2? It
is required by i3.

Ugh, I was hoping that it wasn't... But in that case: yes, please give
it to me too, otherwise taking over i3 is futile.


Also yours now, thanks again :)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Intend to orphan i3 and some related packages

2019-09-04 Thread Dan Čermák
Christian Dersch  writes:

> Am 04.09.19 um 12:36 schrieb Dan Čermák:
>
> Thanks! i3 packages are yours now. Are you also interested in dzen2? It 
> is required by i3.

Ugh, I was hoping that it wasn't... But in that case: yes, please give
it to me too, otherwise taking over i3 is futile.


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora rawhide compose report: 20190904.n.0 changes

2019-09-04 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20190903.n.0
NEW: Fedora-Rawhide-20190904.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  3
Dropped packages:110
Upgraded packages:   116
Downgraded packages: 0

Size of added packages:  330.04 MiB
Size of dropped packages:75.37 MiB
Size of upgraded packages:   3.33 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   70.68 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-Rawhide-20190904.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: f31-backgrounds-31.0.2-2.fc32
Summary: Fedora 31 default desktop background
RPMs:f31-backgrounds f31-backgrounds-animated f31-backgrounds-base 
f31-backgrounds-extras-base f31-backgrounds-extras-gnome 
f31-backgrounds-extras-kde f31-backgrounds-extras-mate 
f31-backgrounds-extras-xfce f31-backgrounds-gnome f31-backgrounds-kde 
f31-backgrounds-mate f31-backgrounds-xfce
Size:329.87 MiB

Package: fctxpd-0.1-1.20190813gitc195e67.fc32
Summary: Fibrechannel transport daemon
RPMs:fctxpd
Size:128.50 KiB

Package: golang-github-vultr-govultr-0.1.4-1.fc32
Summary: Vultr Go API client
RPMs:golang-github-vultr-govultr-devel
Size:47.30 KiB


= DROPPED PACKAGES =
Package: perl-4:5.30.0-444.module_f32+5997+e06a93cb
Summary: Practical Extraction and Report Language
RPMs:perl perl-Attribute-Handlers perl-Devel-Peek perl-Devel-SelfStubber 
perl-Errno perl-ExtUtils-Embed perl-ExtUtils-Miniperl perl-IO perl-IO-Zlib 
perl-Locale-Maketext-Simple perl-Math-Complex perl-Memoize perl-Module-Loaded 
perl-Net-Ping perl-Pod-Html perl-SelfLoader perl-Test perl-Time-Piece 
perl-devel perl-interpreter perl-libnetcfg perl-libs perl-macros perl-open 
perl-tests perl-utils
Size:49.90 MiB

Package: perl-Algorithm-Diff-1.1903-14.module_f32+5988+6cd113e5
Summary: Compute `intelligent' differences between two files/lists
RPMs:perl-Algorithm-Diff
Size:47.40 KiB

Package: perl-Archive-Tar-2.32-440.module_f32+5988+6cd113e5
Summary: A module for Perl manipulation of .tar files
RPMs:perl-Archive-Tar
Size:72.22 KiB

Package: perl-Archive-Zip-1.64-4.module_f32+5988+6cd113e5
Summary: Perl library for accessing Zip archives
RPMs:perl-Archive-Zip
Size:99.80 KiB

Package: perl-CPAN-2.27-2.module_f32+5988+6cd113e5
Summary: Query, download and build perl modules from CPAN sites
RPMs:perl-CPAN
Size:545.41 KiB

Package: perl-CPAN-DistnameInfo-0.12-17.module_f32+5988+6cd113e5
Summary: Extract distribution name and version from a distribution filename
RPMs:perl-CPAN-DistnameInfo
Size:14.44 KiB

Package: perl-CPAN-Meta-2.150010-439.module_f32+5988+6cd113e5
Summary: Distribution metadata for a CPAN dist
RPMs:perl-CPAN-Meta
Size:176.02 KiB

Package: perl-CPAN-Meta-Requirements-2.140-440.module_f32+5988+6cd113e5
Summary: Set of version requirements for a CPAN dist
RPMs:perl-CPAN-Meta-Requirements
Size:31.59 KiB

Package: perl-CPAN-Meta-YAML-0.018-440.module_f32+5988+6cd113e5
Summary: Read and write a subset of YAML for CPAN Meta files
RPMs:perl-CPAN-Meta-YAML
Size:26.27 KiB

Package: perl-Carp-1.50-439.module_f32+5988+6cd113e5
Summary: Alternative warn and die for modules
RPMs:perl-Carp
Size:29.19 KiB

Package: perl-Compress-Bzip2-2.26-13.module_f32+5988+6cd113e5
Summary: Interface to Bzip2 compression library
RPMs:perl-Compress-Bzip2
Size:343.35 KiB

Package: perl-Compress-Raw-Bzip2-2.087-1.module_f32+5988+6cd113e5
Summary: Low-level interface to bzip2 compression library
RPMs:perl-Compress-Raw-Bzip2
Size:165.52 KiB

Package: perl-Compress-Raw-Zlib-2.087-1.module_f32+5988+6cd113e5
Summary: Low-level interface to the zlib compression library
RPMs:perl-Compress-Raw-Zlib
Size:295.09 KiB

Package: perl-Config-Perl-V-0.32-440.module_f32+5988+6cd113e5
Summary: Structured data retrieval of perl -V output
RPMs:perl-Config-Perl-V
Size:21.35 KiB

Package: perl-DB_File-1.852-4.module_f32+5988+6cd113e5
Summary: Perl5 access to Berkeley DB version 1.x
RPMs:perl-DB_File
Size:400.91 KiB

Package: perl-Data-Dumper-2.174-440.module_f32+5988+6cd113e5
Summary: Stringify perl data structures, suitable for printing and eval
RPMs:perl-Data-Dumper
Size:280.18 KiB

Package: perl-Data-OptList-0.110-11.module_f32+5988+6cd113e5
Summary: Parse and validate simple name/value option pairs
RPMs:perl-Data-OptList
Size:26.37 KiB

Package: perl-Data-Section-0.27-8.module_f32+5988+6cd113e5
Summary: Read multiple hunks of data out of your DATA section
RPMs:perl-Data-Section
Size:24.81 KiB

Package: perl-Devel-PPPort-3.52-440.module_f32+5988+6cd113e5
Summary: Perl Pollution Portability header generator
RPMs:perl-Devel-PPPort
Size:620.42 KiB

Package: perl-Devel-Size-0.83-3.module_f32+5988+6cd113e5
Summary: Perl extension for finding the memory usage of Perl

Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread Alexander Bokovoy

On ke, 04 syys 2019, alcir...@gmail.com wrote:

On Mon, 2019-09-02 at 17:14 +0200, Dario Lesca wrote:


After few minutes almost everything work well, except for a thing ...
all windows PC cannot access to others windows PC.


Hey Dario.
Since in recent days I was testing and evaluating Samba as an AD domain
controller, but using another distro, I decided to configure a F30
server, and try to test what are you experiencing.

I can see a lot of the messages you reported:

Sep 03 01:14:09 adc1 krb5kdc[4059](info): TGS_REQ (5 etypes {aes256-
cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-
hmac(23), DEPRECATED:arcfour-hmac-exp(24), (-135)}) 10.97.69.24: ISSUE:
authtime 1567589350, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha1-96(18), ses=aes256-cts-hmac-sha1-96(18)},
WINUNO$@MY.LAN for krbtgt/my@my.lan


This is not an issue. The message above is normal. It says that WINUNO
machine asked for an initial Kerberos ticket granting ticket, asking for
one of 5 encryption types and got it granted with AES256. The textual
description of those encryption types is a feature we added upstream
this year. DEPRECATED: prefix tells that a particular encryption type is
weak and is marked for removal in future versions of Kerberos (there are
RFCs for this removal).


But authentication and access to Windows machines (I'm using Windows
10) seems ok: I can join the domain and I can log in with the domain
administrator and with a user crated on the samba server.




Then, it is true that I can't browse the network from the windows PC,
but it could be a group policy or something else.

Network browsing requires either NetBIOS working or LLMNR (the latter is
not implemented by Samba). If you aren't running nmbd, you are not
advertising your servers. Or may be your Windows clients have NetBIOS
discovery disabled.


Accessing a folder shared by windows machine 1 from windows machine 2
doesn't work... if I use the computer name or the fqdn (name resolution
works using nslookup). But if I use the IP address I'm able to access
the shared folder.


In the bug that Dario filed, I can see problems with his Windows machine
using low-cased machine name while authenticating with its machine
account to Samba DC -- while being joined with all upper case name. E.g.
using 'foo' instead of 'FOO' as its account name. This doesn't work with
Kerberos because Kerberos is case-sensitive. But somehow it also doesn't
work with NTLM requests in his logs.


Using another distro, I was able to access the shared folder using the
computer name as well.
What is the beavihour you are observing?
What I mean is: maybe the issue is something in some little
configuration and not a big incompatibility issue preventing you to use
Fedora as DC.

P.S. if this list is not the right place to discuss such topic, we can
go elsewhere.


We can use https://bugzilla.redhat.com/show_bug.cgi?id=1748860 -- provide your 
logs there too.

I still need to see network traces that show breakage between Windows clients.

--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora Workstation and disabled by default firewall

2019-09-04 Thread Nico Kadel-Garcia
On Wed, Sep 4, 2019 at 5:46 AM Nicolas Mailhot via devel
 wrote:
>
> Le 2019-09-03 18:52, Kyle Marek a écrit :
>
> > Additionally, binding to a specific address does not handle dynamic
> > networks very well.
>
> Simplify that to binding to a specific address does not handle network
> very well, since everything is dynamic nowadays, on desktops, phones or
> servers (servers via vlans, binding, teaming, etc).
>
> Having every single networked app handle dynamic network changes on its
> own does not scale.
>
> There are not so many ways to handle this:
>
> 1. have every app bind to null, and hope the firewall filters out
> dangerous accesses. You'll get a *lot* of app collisions, because every
> app will fight for 443 ownership. And as soon as the firewall is down,
> the king has no clothes.
>
> 2. have every app bind to a private exotic or dynamic port, and map
> those to public well-known ports on the correct address and network at
> the firewall level. That's the usual strategy for containers set up by
> people with no network understanding, because they can not imagine more
> than one address per container. They forget that this will break all
> network management/inspection tools, because no network port will make
> any sense to tools anymore, and unless they go to full dynamic, their
> exotic ports will collide too because their choices are obvious and dumb
> (80xxx usually). And it requires some out of band data telling the
> firewall what the well-known port for each private port should be
> (complex mapping). Again, as soon as the firewall is down, the king has
> no clothes.
>
> 3. only bind to null apps actually intended to be exposed everywhere
> (sshd). Have every other app (containerized or not) use standard fixed
> well-known ports, but give each one a loopback address, and map public
> addresses+well-known port to the correct loopback address+same
> well-known port at the firewall level. It is safe (if the firewall goes
> down, the mappings go down with it, nothing is exposed). It is
> manageable (network flows use standard ports tools know about; the
> firewall does not need to learn complex port mapping, just what private
> ip owns the public port associate to a specific public networks; and the
> usual collision of 443 requests can be easily handled at layer set by
> deploying apache+mod-proxy on one of the private addresses).
>
> Using 3., there is not need to ask users to answer complex questions
> about network ports (because all the network ports are standard,
> well-known port, preset by upstream/the packager). The user only needs

You're trying to outsmart what other people want with a technological
procedure. Since sshd is a lethally dangerous protocol to expose by
default in the world of rootkitted hosts and stolen passwords, and is
one of the ports which should *most* be cut off from exposure to the
world at large, well, the premise of exposing it by default fails
immediately.

Yes, it's pretty much the only place to start with cloud based
machines, but one of the first security steps there is to activate
some kind of firewally to restrict access to your internal network
only.

> Making 3. work for the workstation case just needs some way to tell an
> app what system-specific loopback it should use, and some way for the
> app to declare to the firewall the well-known ports it wants, which is
> the kind and level of complexity systemd already manages.

Please, stop trying to treat the workstation as a fundamentally
different case. It's not. Let's leave the firewall on by default, to
encourage our users to actually learn about their systems and to leave
them in a considerably safer state at system installation.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora-Rawhide-20190904.n.0 compose check report

2019-09-04 Thread Fedora compose checker
No missing expected images.

Compose FAILS proposed Rawhide gating check!
10 of 45 required tests failed, 6 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
FAILED: compose.cloud.all
MISSING: fedora.Workstation-boot-iso.x86_64.64bit - compose.install_default
MISSING: fedora.Workstation-boot-iso.x86_64.uefi - compose.install_default

Failed openQA tests: 30/152 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-Rawhide-20190903.n.0):

ID: 441544  Test: x86_64 KDE-live-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/441544
ID: 441548  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/441548

Old failures (same test failed in Fedora-Rawhide-20190903.n.0):

ID: 441487  Test: x86_64 Server-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/441487
ID: 441488  Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/441488
ID: 441505  Test: x86_64 Server-dvd-iso 
server_role_deploy_domain_controller **GATING**
URL: https://openqa.fedoraproject.org/tests/441505
ID: 441506  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/441506
ID: 441507  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/441507
ID: 441508  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/441508
ID: 441510  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/441510
ID: 441511  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/441511
ID: 441516  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/441516
ID: 441520  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/441520
ID: 441521  Test: x86_64 Everything-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/441521
ID: 441522  Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/441522
ID: 441524  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/441524
ID: 441526  Test: x86_64 Workstation-live-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/441526
ID: 441552  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/441552
ID: 441553  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/441553
ID: 441554  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/441554
ID: 441556  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/441556
ID: 441558  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/441558
ID: 441585  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/441585
ID: 441592  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/441592
ID: 441618  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/441618
ID: 441620  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/441620
ID: 441621  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/441621
ID: 441623  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/441623
ID: 441627  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/441627
ID: 441628  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/441628
ID: 441629  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/441629
ID: 441632  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/441632

Passed openQA tests: 102/152 (x86_64)

New passes (same test not passed in Fedora-Rawhide-20190903.n.0):

ID: 441542  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/441542
ID: 441603  Test: x86_64 universal install_blivet_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/441603

Skipped gating openQA tests: 4/152 (x86_64)

Old skipped gating tests (same test skipped in Fedora-Rawhide-20190903.n.0):

ID: 441530  Test: x86_64 Workstation-live-iso base_update_cli **GATING**

Re: Intend to orphan i3 and some related packages

2019-09-04 Thread Christian Dersch


Am 04.09.19 um 12:36 schrieb Dan Čermák:

Christian Dersch  writes:


Hi,

I intend to orphan the packages related to i3 window manager:

* i3

* i3lock

* i3status

* i3-ipc


I'll take the i3 stack, since I have not yet migrated to sway
completely.

I'd be however more than happy to share the maintenance with others.



Thanks! i3 packages are yours now. Are you also interested in dzen2? It 
is required by i3.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Intend to orphan i3 and some related packages

2019-09-04 Thread Christian Dersch


Am 04.09.19 um 12:09 schrieb František Šumšal:

On 9/4/19 12:02 PM, Christian Dersch wrote:

I intend to orphan the packages related to i3 window manager

Hello!

I'd definitely take the dmenu package if there's no-one else!


Thanks, dmenu is yours now :)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748877] New: perl-Sys-Virt-5.7.0 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748877

Bug ID: 1748877
   Summary: perl-Sys-Virt-5.7.0 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sys-Virt
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com, crobi...@redhat.com,
jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 5.7.0
Current version/release in rawhide: 5.6.0-1.fc31
URL: http://search.cpan.org/dist/Sys-Virt/

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/3355/

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748251] Upgrade perl-Pod-PseudoPod to 0.19

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748251

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-Pod-PseudoPod-0.19-1.fc31 has been pushed to the Fedora 31 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-2019-432511c438

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748472] perl-DBD-Pg-3.10.0 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748472

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-DBD-Pg-3.10.0-1.fc31 has been pushed to the Fedora 31 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-2019-806cab0e93

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748169] perl-MCE-1.847 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748169

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
perl-MCE-1.848-1.fc31, perl-MCE-Shared-1.848-1.fc31 has been pushed to the
Fedora 31 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-2019-ece3d41a8e

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748740] perl-MCE-1.848 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748740

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-MCE-1.848-1.fc31, perl-MCE-Shared-1.848-1.fc31 has been pushed to the
Fedora 31 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-2019-ece3d41a8e

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Fedora Samba DC for what purpose it is released in Fedora ?

2019-09-04 Thread alciregi
On Mon, 2019-09-02 at 17:14 +0200, Dario Lesca wrote:
> 
> After few minutes almost everything work well, except for a thing ...
> all windows PC cannot access to others windows PC.

Hey Dario.
Since in recent days I was testing and evaluating Samba as an AD domain
controller, but using another distro, I decided to configure a F30
server, and try to test what are you experiencing.

I can see a lot of the messages you reported:

Sep 03 01:14:09 adc1 krb5kdc[4059](info): TGS_REQ (5 etypes {aes256-
cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-
hmac(23), DEPRECATED:arcfour-hmac-exp(24), (-135)}) 10.97.69.24: ISSUE:
authtime 1567589350, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha1-96(18), ses=aes256-cts-hmac-sha1-96(18)}, 
WINUNO$@MY.LAN for krbtgt/my@my.lan

But authentication and access to Windows machines (I'm using Windows
10) seems ok: I can join the domain and I can log in with the domain
administrator and with a user crated on the samba server.

Then, it is true that I can't browse the network from the windows PC,
but it could be a group policy or something else.

Accessing a folder shared by windows machine 1 from windows machine 2
doesn't work... if I use the computer name or the fqdn (name resolution
works using nslookup). But if I use the IP address I'm able to access
the shared folder.
Using another distro, I was able to access the shared folder using the
computer name as well.
What is the beavihour you are observing? 
What I mean is: maybe the issue is something in some little
configuration and not a big incompatibility issue preventing you to use
Fedora as DC.

P.S. if this list is not the right place to discuss such topic, we can
go elsewhere.


Thanks,
A.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Intend to orphan i3 and some related packages

2019-09-04 Thread Dan Čermák
Christian Dersch  writes:

> Hi,
>
> I intend to orphan the packages related to i3 window manager:
>
> * i3
>
> * i3lock
>
> * i3status
>
> * i3-ipc
>

I'll take the i3 stack, since I have not yet migrated to sway
completely.

I'd be however more than happy to share the maintenance with others.

> * dzen2
>
> * dmenu
>
> Anybody here interested in taking them? Otherwise I'll orphan them on 
> Friday.
>
>
> Greetings
>
> Christian
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[389-devel] 389 DS nightly 2019-09-04 - 96% PASS

2019-09-04 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2019/09/04/report-389-ds-base-1.4.1.6-20190904git295ea07.fc30.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org


[Bug 1748857] New: [RFE] EPEL8 branch of perl-Test-Needs

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748857

Bug ID: 1748857
   Summary: [RFE] EPEL8 branch of perl-Test-Needs
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Test-Needs
  Assignee: emman...@seyman.fr
  Reporter: p...@city-fan.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



I am attempting to build perl-Specio in EPEL 8 and it requires
perl(Test::Needs). Please consider building perl-Test-Needs in EPEL 8.

I have successfully built it locally to test my perl-Specio build.

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748856] New: [RFE] EPEL8 branch of perl-Sub-Quote

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748856

Bug ID: 1748856
   Summary: [RFE] EPEL8 branch of perl-Sub-Quote
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sub-Quote
  Assignee: jples...@redhat.com
  Reporter: p...@city-fan.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



I am attempting to build perl-Specio in EPEL 8 and it requires
perl(Sub::Quote). Please consider building perl-Sub-Quote in EPEL 8.

I have successfully built it locally to test my perl-Specio build.

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Intend to orphan i3 and some related packages

2019-09-04 Thread František Šumšal
On 9/4/19 12:02 PM, Christian Dersch wrote:
> I intend to orphan the packages related to i3 window manager

Hello!

I'd definitely take the dmenu package if there's no-one else!

-- 
Frantisek Sumsal
GPG key ID: 0xFB738CE27B634E4B



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1748169] perl-MCE-1.847 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748169

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |MODIFIED



--- Comment #6 from Fedora Update System  ---
FEDORA-2019-ece3d41a8e has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-ece3d41a8e

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748740] perl-MCE-1.848 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748740



--- Comment #2 from Fedora Update System  ---
FEDORA-2019-ece3d41a8e has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-ece3d41a8e

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1748740] perl-MCE-1.848 is available

2019-09-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1748740

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2019-ece3d41a8e has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-ece3d41a8e

-- 
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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Intend to orphan i3 and some related packages

2019-09-04 Thread Christian Dersch

Hi,

I intend to orphan the packages related to i3 window manager:

* i3

* i3lock

* i3status

* i3-ipc

* dzen2

* dmenu

Anybody here interested in taking them? Otherwise I'll orphan them on 
Friday.



Greetings

Christian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Intent to orphan dblatex (asciidoc dependency)

2019-09-04 Thread Josef Ridky
But due FOP doesn't use Latex, its configuration is different and FOP output 
looks very different to the Latex output, it would be probably better to 
request Python2 exception for dblatex (or rewrite it to Python3).

Josef Ridky
Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

- Original Message -
| From: "Josef Ridky" 
| To: "Development discussions related to Fedora" 

| Sent: Wednesday, September 4, 2019 11:47:41 AM
| Subject: Re: Intent to orphan dblatex (asciidoc dependency)
| 
| So good news, asciidoc(-py3) is already using FOP as second option for
| generating PDF files.
| 
| So it just need to be set as default option instead of dblatex and all should
| be fine.
| 
| Josef Ridky
| Software Engineer
| Core Services Team
| Red Hat Czech, s.r.o.
| 
| - Original Message -
| | From: "Josef Ridky" 
| | To: "Development discussions related to Fedora"
| | 
| | Sent: Wednesday, September 4, 2019 11:38:04 AM
| | Subject: Re: Intent to orphan dblatex (asciidoc dependency)
| | 
| | From asciidoc perspective, dblatex is quite important for generating PDF
| | files (even it's called just via shell method).
| | 
| | I have contacted asciidoc upstream (asciidoc-py3 to be precised) with
| | question about dblatex replacement.
| | I'll let you know once they reply.
| | 
| | Josef Ridky
| | Software Engineer
| | Core Services Team
| | Red Hat Czech, s.r.o.
| | 
| | - Original Message -
| | | From: "Jonathan Wakely" 
| | | To: "Development discussions related to Fedora"
| | | 
| | | Sent: Wednesday, September 4, 2019 10:42:01 AM
| | | Subject: Re: Intent to orphan dblatex (asciidoc dependency)
| | | 
| | | On 03/09/19 18:34 +0100, Jonathan Wakely wrote:
| | | >On 03/09/19 09:57 -0600, Jerry James wrote:
| | | >>On Tue, Sep 3, 2019 at 7:37 AM Michael J Gruber 
| | | >>wrote:
| | | >>>This is to let you know that I intend to orphan dblatex.
| | | >>
| | | >>Note that the gcc package uses dblatex to build libstdc++
| | | >>documentation.  We as a project need to figure out what to do about
| | | >>dblatex's python 2 dependency.
| | | >
| | | >I don't think it's used in Fedora actually. I'm pretty sure it's only
| | | >used to generate the PDF version of the libstdc++ manual hosted on the
| | | >gcc.gnu.org website. Those PDF files aren't packaged for Fedora. I
| | | >think we can try just dropping the BuildRequires and see if it still
| | | >builds. And if not, what needs to be changed to get it building again.
| | | >
| | | >For the upstream docs I'll look into using fop instead of dblatex.
| | | 
| | | An x86_64 scratch build with this change completed successfully:
| | | 
| | | --- a/gcc.spec
| | | +++ b/gcc.spec
| | | @@ -190,7 +190,7 @@ Requires: libisl.so.15
| | |  %endif
| | |  %if %{build_libstdcxx_docs}
| | |  BuildRequires: doxygen >= 1.7.1
| | | -BuildRequires: graphviz, dblatex, texlive-collection-latex,
| | | docbook5-style-xsl
| | | +BuildRequires: graphviz, texlive-collection-latex, docbook5-style-xsl
| | |  %endif
| | |  Requires: cpp = %{version}-%{release}
| | |  # Need .eh_frame ld optimizations
| | | 
| | | So the dblatex dependency can just be dropped from gcc.spec, which
| | | Jakub said he'll take care of when he updates it next.
| | | ___
| | | devel mailing list -- devel@lists.fedoraproject.org
| | | To unsubscribe send an email to devel-le...@lists.fedoraproject.org
| | | Fedora Code of Conduct:
| | | https://docs.fedoraproject.org/en-US/project/code-of-conduct/
| | | List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
| | | List Archives:
| | | 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
| | | 
| | ___
| | devel mailing list -- devel@lists.fedoraproject.org
| | To unsubscribe send an email to devel-le...@lists.fedoraproject.org
| | Fedora Code of Conduct:
| | https://docs.fedoraproject.org/en-US/project/code-of-conduct/
| | List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
| | List Archives:
| | https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
| | 
| ___
| devel mailing list -- devel@lists.fedoraproject.org
| To unsubscribe send an email to devel-le...@lists.fedoraproject.org
| Fedora Code of Conduct:
| https://docs.fedoraproject.org/en-US/project/code-of-conduct/
| List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
| List Archives:
| https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
| 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 

  1   2   >