Review request: battray

[Globe Trotter]

Hi,

Would someone be willing to review a simple package for me? The BZ  is here: 
Bug 1573695 – Review Request: Battray - simple tray icon to show a laptop’s 
battery status.

I have some experience with Fedora's packaging and have maintained a few 
packages (pdf-stapler, python-PDF2, sylfilter) for a while.

Happy to reciprocate as needed.

FAS username: aarem



| 
| 
|  | 
Bug 1573695 – Review Request: Battray - simple tray icon to show a lapto...


 |

 |

 |



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

[EPEL-devel] heketi has been retired from EPEL6 and EPEL7

[Niels de Vos]

Heketi, an intelligent management service for Gluster with a ReST
interface, has been retired from EPEL6 and EPEL7. Some of the Gluster
components that were in EPEL gave conflicts with versions available in
RHEL and/or Red Hat Gluster Storage. In order to prevent issues, all
Gluster packages have been remove from EPEL.

Heketi and other Gluster components are available through the CentOS
Extras and the CentOS Storage SIG repositories.

Kind regards,
Niels de Vos


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] ansible back available in EPEL7

[Kevin Fenzi]

Greetings.

Ansible was added to the RHEL7 extras channel and removed from EPEL7 a
while back. Now, ansible is no longer going to be updated in the RHEL7
extras channel per:

https://access.redhat.com/articles/3359651

So, accordingly ansible is back in EPEL7.

Users are welcome to install from EPEL7, upstream
https://releases.ansible.com/ansible/ or use
https://access.redhat.com/articles/3174981 to enable and get
Red Hat Ansible Engine from Red hat.

Thanks,

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

Re: libicu upgrade to 61.1 with soname bump in rawhide/F29

[Pete Walter]

01.05.2018, 19:05, "Jonathan Wakely" :
> On 26/04/18 19:49 +0200, Eike Rathke wrote:
>> Hi,
>>
>> I'm upgrading libicu to 61.1 for rawhide, which as usual comes with
>> a soname bump. I requested a side target f29-icu for the builds, I'll
>> ask Pete Walter (who already did it for 60.1) to help with rebuilding
>> the dependent packages, or another proven packager if he's not
>> available.
>
> I see that your rebuild of ledger failed due to my boost packaging
> changes:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=26686488
>
> I've fixed the build to work now (by adding boost-python2-devel) but
> it will need to be bumped again and rebuilt in your f29-icu side tag.

Done.

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

Re: Orphaning schroot package

[Sérgio Basto]

I take it, as is part of debian tools , I tried to see if some trick
here, rawhide version still in 1.6.5 when 1.6.10 is available since
2014-05-05 ...



On Mon, 2018-04-30 at 10:37 -0700, Zach Carter wrote:
> I'm orphaning the schroot package, since I no longer use it or work
> with it:
> 
>  https://src.fedoraproject.org/rpms/schroot
> 
> There is currently a serious (crash) bug affecting the package in
> F28:
> 
>  https://bugzilla.redhat.com/show_bug.cgi?id=1573253
> 
> Upstream:
> 
>  https://packages.debian.org/search?keywords=schroot
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Status of OwnCloud/NextCloud

[Adam Williamson]

On Tue, 2018-05-01 at 21:19 +, mark preston wrote:
> i remember OC being very protective of their stream and not working
> well with others to get it in other distributions.  I was an oC user
> that switch to nC and still running V10.  I've been waiting for an
> update to nC and would like to stay with it even if i have to upgrade
> though 11 and 12 to get to 13. 
> Is there another package out there that does what oC/nC does that
> would be a bettter fit for fedora?  i'd consider a migration to
> different product that does the same thing if it is easier to
> maintain.

OC/NC sort of gloms a *lot* of different jobs together, which is one
reason the code is kind of a nightmare. So there aren't really many
alternatives to "everything OC/NC does" (Kolab may be the closest). But
most people don't actually use "everything", I don't think, just
certain bits. So the answer is: it depends what bits of OC/NC you
actually rely on, what goals does it help you accomplish?

Personally, I replaced my use of OC/NC with a webdav share configured
directly in Apache, and Radicale (dnf install radicale) to replace the
shared calendar/todo list. But if you use OC/NC for different things,
your 'replacement' may differ.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Status of OwnCloud/NextCloud

[mark preston]

i remember OC being very protective of their stream and not working well with 
others to get it in other distributions.  I was an oC user that switch to nC 
and still running V10.  I've been waiting for an update to nC and would like to 
stay with it even if i have to upgrade though 11 and 12 to get to 13. 
Is there another package out there that does what oC/nC does that would be a 
bettter fit for fedora?  i'd consider a migration to different product that 
does the same thing if it is easier to maintain.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: updating condor

[Stephen John Smoogen]

On 1 May 2018 at 15:57, Mátyás Selmeci  wrote:
> Hi folks,
>
> The versions of condor in EPEL 6 (8.4.3) and 7 (8.3.8) are out of date and
> no longer supported by upstream. The current release is 8.6.10.
>
> Most configurations should work fine without changes between the two
> versions. However, there are some admin-visible changes, most notably
> enabling use of cgroups by default, and listening on a single port instead
> of a port range. There are also some changes to the default output of the
> command-line tools.
>

It might be possible, and I have cc'd the package maintainer for
condor for their take on it. The bigger issue is whether other parts
need to be updated to make it work also or if existing systems would
explode when updated.


> Are these changes considered too disruptive for EPEL stable?
>
> Thanks,
> -Mat
>
> --
> Mátyás (Mat) Selmeci
> Open Science Grid Software Team / Center for High-Throughput Computing
> University of Wisconsin-Madison Department of Computer Sciences
>
>
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
>



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

[EPEL-devel] updating condor

[Mátyás Selmeci]

Hi folks,

The versions of condor in EPEL 6 (8.4.3) and 7 (8.3.8) are out of date 
and no longer supported by upstream. The current release is 8.6.10.


Most configurations should work fine without changes between the two 
versions. However, there are some admin-visible changes, most notably 
enabling use of cgroups by default, and listening on a single port 
instead of a port range. There are also some changes to the default 
output of the command-line tools.


Are these changes considered too disruptive for EPEL stable?

Thanks,
-Mat

--
Mátyás (Mat) Selmeci
Open Science Grid Software Team / Center for High-Throughput Computing
University of Wisconsin-Madison Department of Computer Sciences

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

Fedora 28-20180426.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 4/137 (x86_64), 4/24 (i386), 1/2 (arm)

ID: 231763  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/231763
ID: 231799  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/231799
ID: 231807  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/231807
ID: 231808  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/231808
ID: 231823  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/231823
ID: 231855  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/231855
ID: 231907  Test: x86_64 universal install_rescue_encrypted@uefi
URL: https://openqa.fedoraproject.org/tests/231907
ID: 231914  Test: i386 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/231914
ID: 231923  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/231923

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

ID: 231771  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/231771
ID: 231785  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/231785
ID: 231786  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/231786
ID: 231810  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/231810
ID: 231847  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/231847
ID: 231876  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/231876
ID: 231894  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/231894
ID: 231895  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/231895

Passed openQA tests: 127/137 (x86_64), 18/24 (i386)

Skipped openQA tests: 1 of 163
-- 
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

Re: Should boost package install boost-python2 / boost-python3 / both or none?

[Jonathan Wakely]

On 26/04/18 23:44 +0100, Jonathan Wakely wrote:

On 19/04/18 19:02 +0100, Jonathan Wakely wrote:

I forgot to mention that this will break any packages using
Boost.Python which currently just have BR: boost-devel but that's
arguably a good thing anyway. It will be easy to fix them, and we will
have to make an explicit decision whether they should really be
using the python2 version, or should use boost-python3 instead.


I am about to push these changes to dist-git and build boost-1.66.0-6
for rawhide.

It looks like the packages below use boost-python and so might need
their spec files adjusting to add BuildRequires: boost-python2-devel

$ dnf repoquery --releasever=rawhide --archlist=x86_64  --disablerepo='*' 
--enablerepo=updates --enablerepo=fedora --whatrequires 
'libboost_python.so.1.66.0()(64bit)'
enabling updates-debuginfo repository
enabling fedora-debuginfo repository
Last metadata expiration check: 0:00:15 ago on Thu 26 Apr 2018 23:36:30 BST.
Singular-libs-0:4.1.0p3-8.fc28.x86_64
avogadro-libs-0:1.2.0-15.fc28.x86_64
condor-0:8.6.10-1.fc29.x86_64
freeorion-0:0.4.7.1-8.fc29.x86_64
k3d-0:0.8.0.6-14.fc28.x86_64
kig-0:18.04.0-1.fc29.x86_64
openvdb-python2-0:5.0.0-2.fc29.x86_64
pyexiv2-0:0.3.2-33.fc28.x86_64
python2-condor-0:8.6.10-1.fc29.x86_64
rb_libtorrent-python2-0:1.1.7-1.fc29.x86_64
vegastrike-0:0.5.1-32.r1.fc28.x86_64


The packages above are fixed now, by adding boost-python2-devel to
BuildRequires (and in one case Requires as well).


python2-vigra-0:1.11.1-6.fc29.x86_64
python3-vigra-0:1.11.1-6.fc29.x86_64


I've created a pull request for vigra.


freecad-1:0.17-0.1.pre.fc29.x86_64


This fails for an unrelated reason:
dos2unix: copying.lib: No such file or directory

Richard, should I push the fix to add boost-python2-devel anyway, or
do you want to do it?


ledger-0:3.1.1-15.fc29.x86_64
python2-ledger-0:3.1.1-15.fc29.x86_64


These are rebuilt but need doing again for ICU.


I'm still working through the rest:


airinv-0:1.00.1-18.fc28.x86_64
airrac-0:1.00.1-15.fc28.x86_64
airtsp-0:1.01.3-8.fc28.x86_64
python2-botan-0:1.10.17-3.fc28.x86_64
python2-csdiff-0:1.3.3-4.fc28.x86_64
python2-dlib-0:19.4-7.fc29.x86_64
python2-dmlite-0:1.10.2-1.fc29.x86_64
python2-gattlib-0:0.20150805-4.fc28.x86_64
python2-gfal2-0:1.9.3-6.fc28.x86_64
python2-hokuyoaist-0:3.0.2-22.fc28.x86_64
python2-libpst-0:0.6.71-7.fc28.x86_64
python2-lmiwbem-0:0.7.2-18.fc28.x86_64
python2-mapnik-0:0.1-33.20170614git1635afe.fc29.x86_64
python2-openimageio-0:1.8.10-1.fc29.x86_64
python2-osmium-0:2.14.0-1.fc29.x86_64
python2-trademgen-0:1.00.2-17.fc28.x86_64
rmol-0:1.00.1-16.fc28.x86_64
sevmgr-0:1.00.2-16.fc28.x86_64
simcrs-0:1.01.1-15.fc28.x86_64
simfqt-0:1.00.1-15.fc28.x86_64
stdair-0:1.00.6-3.fc28.x86_64
trademgen-0:1.00.2-17.fc28.x86_64
travelccm-0:1.00.2-14.fc28.x86_64

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

Re: Working on a Dracut bug?

[Matthew Miller]

On Tue, May 01, 2018 at 08:32:36PM +0200, inderau...@arcor.de wrote:
> btw. just read that fedora workstation doesn't need a separate root
> account anymore. there are no security concerns i should have, don't
> i?

You can set a root password if you like. You might find this bit I
wrote a while ago for Stack Exchange to be helpful:

https://unix.stackexchange.com/a/8588/2511

-- 
Matthew Miller

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

Re: Working on a Dracut bug?

[Matthew Miller]

On Tue, May 01, 2018 at 08:30:19PM +0200, inderau...@arcor.de wrote:
> now ist 1st of may. And Fedora 28 is released. I want do upgrade. But i don't 
> want this error messages and related start up issues anymore.
> Is there any progress on fixing this long term issue?

We're working on it, and trying to find the best solution.

-- 
Matthew Miller

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

Re: libicu upgrade to 61.1 with soname bump in rawhide/F29

[Jonathan Wakely]

On 26/04/18 19:49 +0200, Eike Rathke wrote:

Hi,

I'm upgrading libicu to 61.1 for rawhide, which as usual comes with
a soname bump. I requested a side target f29-icu for the builds, I'll
ask Pete Walter (who already did it for 60.1) to help with rebuilding
the dependent packages, or another proven packager if he's not
available.


I see that your rebuild of ledger failed due to my boost packaging
changes:
https://koji.fedoraproject.org/koji/taskinfo?taskID=26686488

I've fixed the build to work now (by adding boost-python2-devel) but
it will need to be bumped again and rebuilt in your f29-icu side tag.

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

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

[smooge]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2018-05-02 from 18:00:00 to 19:00:00 GMT
   At fedora-meet...@irc.freenode.net

The meeting will be about:
The EPEL Steering Committee will have a weekly meeting to cover current tasks 
and problems needed to keep EPEL going.


Source: https://apps.fedoraproject.org/calendar/meeting/8724/

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

Fedora 28 compose report: 20180426.n.0 changes

[Fedora Branched Report]

OLD: Fedora-28-20180425.n.0
NEW: Fedora-28-20180426.n.0

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

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

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

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =

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

Re: Install failures on ppc64, ppc64le, aarch64 & armv7l (was: Re: Fedora 28 is officially here!)

[Richard W.M. Jones]

On Tue, May 01, 2018 at 08:42:53AM -0700, Adam Williamson wrote:
> On Tue, 2018-05-01 at 16:25 +0100, Richard W.M. Jones wrote:
> > Unfortunately the Anaconda install (using virt-install --location
> > method) didn't work well for me on any !x86 architecture.  I get the
> > exact same error on ppc64{,le}, aarch64 and armv7l:
> > 
> > 
> > ** (process:1963): WARNING **: 15:09:38.580: Cannot load the LVM plugin
> > anaconda 28.22.10-1.fc28 for Fedora 28 started.
> >  * installation log files are stored in /tmp during the installation
> >  * shell is available on TTY2
> >  * if the graphical installation interface fails to start, try again with 
> > the
> >inst.text bootoption to start text installation
> >  * when reporting a bug add logs from /tmp as separate text/plain 
> > attachments
> > 15:15:37 Anaconda DBus modules failed to start on time.
> > 15:15:37 Anaconda DBus modules failed to start on time.
> > 
> > 
> > Pane is dead
> 
> Odd. Install from an actual installer image was tested successfully on
> aarch64:
> 
> https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora=28=Fedora-28-20180425.0=6
> 
> and ppc64:
> 
> https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora=28=Fedora-28-20180425.0=3
> 
> ppc64le always fails in openQA due to some kind of weird rendering
> issues specific to that arch:
> https://bugzilla.redhat.com/show_bug.cgi?id=1546693
> but the installer does at least boot, and would be usable by a human.
> 
> (There are some failures on aarch64, many of those are bogus fails
> caused by the test system bugging out; I think the hardware we're
> running those tests on at present is somewhat under-resourced. There
> are sufficient passes to show that things at least basically work.)

I've now managed to collect the logs.  They are attached to:

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

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora 28 is officially here!

[John Dennis]

On 05/01/2018 10:00 AM, Matthew Miller wrote:

It's almost Mother's Day, and that means it's time for Fedora 28,
which is officially released today.


FWIW, there is a broken link to the install documentation.

If you visit:

https://getfedora.org/en/workstation/download/

and click on "Installation Guide" on the right hand pane

it will direct you to:

https://docs.fedoraproject.org/f28/install-guide/

which has an error page saying:

Fedora Documentation - 404 Page Not Found :(


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

Re: Install failures on ppc64, ppc64le, aarch64 & armv7l (was: Re: Fedora 28 is officially here!)

[Adam Williamson]

On Tue, 2018-05-01 at 16:25 +0100, Richard W.M. Jones wrote:
> Unfortunately the Anaconda install (using virt-install --location
> method) didn't work well for me on any !x86 architecture.  I get the
> exact same error on ppc64{,le}, aarch64 and armv7l:
> 
> 
> ** (process:1963): WARNING **: 15:09:38.580: Cannot load the LVM plugin
> anaconda 28.22.10-1.fc28 for Fedora 28 started.
>  * installation log files are stored in /tmp during the installation
>  * shell is available on TTY2
>  * if the graphical installation interface fails to start, try again with the
>inst.text bootoption to start text installation
>  * when reporting a bug add logs from /tmp as separate text/plain attachments
> 15:15:37 Anaconda DBus modules failed to start on time.
> 15:15:37 Anaconda DBus modules failed to start on time.
> 
> 
> Pane is dead

Odd. Install from an actual installer image was tested successfully on
aarch64:

https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora=28=Fedora-28-20180425.0=6

and ppc64:

https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora=28=Fedora-28-20180425.0=3

ppc64le always fails in openQA due to some kind of weird rendering
issues specific to that arch:
https://bugzilla.redhat.com/show_bug.cgi?id=1546693
but the installer does at least boot, and would be usable by a human.

(There are some failures on aarch64, many of those are bogus fails
caused by the test system bugging out; I think the hardware we're
running those tests on at present is somewhat under-resourced. There
are sufficient passes to show that things at least basically work.)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Install failures on ppc64, ppc64le, aarch64 & armv7l (was: Re: Fedora 28 is officially here!)

[Daniel P . Berrangé]

On Tue, May 01, 2018 at 04:25:11PM +0100, Richard W.M. Jones wrote:
> 
> Unfortunately the Anaconda install (using virt-install --location
> method) didn't work well for me on any !x86 architecture.  I get the
> exact same error on ppc64{,le}, aarch64 and armv7l:
> 
> 
> ** (process:1963): WARNING **: 15:09:38.580: Cannot load the LVM plugin
> anaconda 28.22.10-1.fc28 for Fedora 28 started.
>  * installation log files are stored in /tmp during the installation
>  * shell is available on TTY2
>  * if the graphical installation interface fails to start, try again with the
>inst.text bootoption to start text installation
>  * when reporting a bug add logs from /tmp as separate text/plain attachments
> 15:15:37 Anaconda DBus modules failed to start on time.
> 15:15:37 Anaconda DBus modules failed to start on time.
> 
> 
> Pane is dead
> 
> 
> Unfortunately x2 I couldn't work out how to get to the log window,
> since key sequences like Alt+Tab are captured by my window manager.

virt-viewer is supposed to inhibit the window manager, even with
GNOME shell on Wayland this is supposed to work now. If it doesn't
though, you can stil inject keys using virsh

$ virsh send-key --codeset linux myguestname KEY_LEFTALT KEY_TAB

Regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Install failures on ppc64, ppc64le, aarch64 & armv7l (was: Re: Fedora 28 is officially here!)

[Richard W.M. Jones]

Unfortunately the Anaconda install (using virt-install --location
method) didn't work well for me on any !x86 architecture.  I get the
exact same error on ppc64{,le}, aarch64 and armv7l:


** (process:1963): WARNING **: 15:09:38.580: Cannot load the LVM plugin
anaconda 28.22.10-1.fc28 for Fedora 28 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * if the graphical installation interface fails to start, try again with the
   inst.text bootoption to start text installation
 * when reporting a bug add logs from /tmp as separate text/plain attachments
15:15:37 Anaconda DBus modules failed to start on time.
15:15:37 Anaconda DBus modules failed to start on time.


Pane is dead


Unfortunately x2 I couldn't work out how to get to the log window,
since key sequences like Alt+Tab are captured by my window manager.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Modularity Working Group IRC Meeting Minutes (2018-05-01)

[Langdon White]

Meeting started by langdon at 14:01:52 UTC.

Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-01/modularity_wg.2018-05-01-14.01.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-01/modularity_wg.2018-05-01-14.01.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-01/modularity_wg.2018-05-01-14.01.log.html

Meeting summary
---
* roll call  (langdon, 14:03:28)
  * LINK: https://fedoramagazine.org/announcing-fedora-28/   (langdon,
14:04:50)

* back patting  (langdon, 14:05:02)
  * LINK: https://getfedora.org/server/   (langdon, 14:06:27)
  * yay!  (langdon, 14:07:16)

* agenda  (langdon, 14:07:31)

* open floor  (langdon, 14:11:04)

Meeting ended at 14:20:38 UTC.




Action Items




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




People Present (lines said)
---
* langdon (26)
* zodbot (10)
* sgallagh (6)
* sct (1)
* tflink (0)
* dgilmore (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Ansible execution errors

[Tom diehl]

Hi,

I upgraded my ansible control machine to to the latest centos-7-cr and
ansible-2.5.2-1.el7.noarch from epel. The latest yum update installed
python-urllib3-1.10.2-5.el7.noarch.

When I run ansible I am getting the following errors:

/usr/lib/python2.7/site-packages/requests/__init__.py:80: 
RequestsDependencyWarning: urllib3 (1.10.2) or chardet (3.0.4) doesn't match a 
supported version!
  RequestsDependencyWarning)
/usr/lib/python2.7/site-packages/requests/__init__.py:80: 
RequestsDependencyWarning: urllib3 (1.10.2) or chardet (3.0.4) doesn't match a 
supported version!
  RequestsDependencyWarning)
/usr/lib/python2.7/site-packages/requests/__init__.py:80: 
RequestsDependencyWarning: urllib3 (1.10.2) or chardet (3.0.4) doesn't match a 
supported version!
  RequestsDependencyWarning)

Is this likely caused by Ansible needing to be rebuilt when Centos7.5
is actually released or does it look like this is something else?

FWIW, Ansible seems to be doing the right thing. It just complains at the start
of every run.

Regards,

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

Fedora Atomic Host Two Week Release Announcement: 28.20180425.0

[Dusty Mabe]

A new Fedora Atomic Host update is available via an OSTree update:

Version: 28.20180425.0
Commit(x86_64): 94a9d06eef34aa6774c056356d3d2e024e57a0013b6f8048dbae392a84a137ca
Commit(aarch64): 
12a95314084eaa2242bdfe24197774aac163433d2405bc2813b4d89180434630
Commit(ppc64le): 
d29c4549226ca8a50846360cf2f7149fbe15b4ab9d1c91d0d2aff1858b3ab1f3

This is our first release of Fedora 28 Atomic Host! We will be sending out blog
posts covering new features and upgrades very soon. In the meantime here is how
you go from F27 to F28:

# sudo ostree remote add --set=gpg-verify=true 
--set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary atomicrepo 
https://dl.fedoraproject.org/atomic/repo/
# sudo rpm-ostree rebase atomicrepo:fedora/28/x86_64/atomic-host


We are releasing images from multiple architectures but please note
that x86_64 architecture is the only one that undergoes automated
testing at this time.

Existing systems can be upgraded in place via e.g. `atomic host upgrade`.

Corresponding image media for new installations can be downloaded from:

https://getfedora.org/en/atomic/download/

Alternatively, image artifacts can be found at the following links:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0.aarch64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0.aarch64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180425.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0.ppc64le.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0.ppc64le.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180425.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0.x86_64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0.x86_64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180425.0.x86_64.vagrant-libvirt.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180425.0.x86_64.vagrant-virtualbox.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180425.0.iso

Respective signed CHECKSUM files can be found here:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180425.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180425.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0-x86_64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180425.0-x86_64-CHECKSUM

For direct download, the "latest" targets are always available here:
https://getfedora.org/atomic_iso_latest
https://getfedora.org/atomic_qcow2_latest
https://getfedora.org/atomic_raw_latest
https://getfedora.org/atomic_vagrant_libvirt_latest
https://getfedora.org/atomic_vagrant_virtualbox_latest

Filename fetching URLs are available here:
https://getfedora.org/atomic_iso_latest_filename
https://getfedora.org/atomic_qcow2_latest_filename
https://getfedora.org/atomic_raw_latest_filename
https://getfedora.org/atomic_vagrant_libvirt_latest_filename
https://getfedora.org/atomic_vagrant_virtualbox_latest_filename

The AMIs for this release are here:

Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-1 ami-cb17f1b4 hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-2 ami-70fc551e hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-south-1 ami-833110ec hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-1 ami-4ddbf431 hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-2 ami-7b65af19 hvm standard

Fedora 28 is officially here!

[Matthew Miller]

It's almost Mother's Day, and that means it's time for Fedora 28,
which is officially released today.

Congratulations to everyone who contributed to this amazingly
smooth and polished release. You all are awesome.

Read the official announcement at:

* https://fedoramagazine.org/announcing-fedora-28/

or just go ahead and grab it from:

* https://getfedora.org/


-- 
Matthew Miller

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

Fedora 28 is officially here!

[Matthew Miller]

It's almost Mother's Day, and that means it's time for Fedora 28,
which is officially released today.

Congratulations to everyone who contributed to this amazingly
smooth and polished release. You all are awesome.

Read the official announcement at:

* https://fedoramagazine.org/announcing-fedora-28/

or just go ahead and grab it from:

* https://getfedora.org/


-- 
Matthew Miller

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

[Bug 1569520] perl-Storable-3.06 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
perl-Storable-3.09-1.fc27 has been pushed to the Fedora 27 stable repository.
If problems still persist, please make note of it in this bug report.

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

[Bug 1570273] perl-Storable-3.09 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
perl-Storable-3.09-1.fc27 has been pushed to the Fedora 27 stable repository.
If problems still persist, please make note of it in this bug report.

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

[Bug 1570265] perl-Digest-SHA-6.02 is available

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
perl-Digest-SHA-6.02-1.fc27 has been pushed to the Fedora 27 stable repository.
If problems still persist, please make note of it in this bug report.

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

Re: I would like to propose that we turn on XFS Reflink in Fedora 29 by default

[Eric Sandeen]

On 4/30/18 1:16 PM, Neal Gompa wrote:
> On Mon, Apr 30, 2018 at 2:14 PM Jason L Tibbitts III 
> wrote:
> 
>>> "CW" == Colin Walters  writes:
> 
>> CW> I'd say it makes sense to revisit the default here globally in
>> CW> Anaconda.
> 
>> Maybe.  Have the issues which made XFS less suitable for use on laptops
>> been resolved?  The primary one I recall was that each mounted
>> filesystem would have a corresponding kernel thread doing about 20
>> wakeups per second.  This was not really good for battery life and power
>> consumption in general.
> 
>> Last I checked (which was 2016 or so) those wakeups were slated to be
>> around for a while longer.
>> https://www.spinics.net/lists/xfs/msg40210.html

As we discussed on IRC, I think idle filesystems won't get these wakeups;
if this is still a concern, investigation of the actual effects on battery
life (if any) are recommended.

> 
> And there's still the fun restriction of XFS not being able to shrink. It's
> not particularly important in the server case, but in the desktop/laptop
> case, it happens enough in my experience that I'm not sure I'd want a
> default filesystem that can't shrink.

XFS realistically is not going to get shrink.  Fedora will need to decide if
the other capabilities & features outweigh the lack of shrink capability.

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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  23  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2c81054303   
remctl-3.14-1.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f51587d6d2   
composer-1.6.4-1.el7
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-4d3c4577da   
gsoap-2.8.16-10.el7
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-26155198e1   
roundcubemail-1.1.11-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-cae67a6aed   
knot-resolver-2.3.0-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e4a3d0e9ef   
drupal7-7.59-1.el7


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

grip-3.7.1-1.el7
paho-c-1.2.1-0.el7
python-moksha-hub-1.5.6-1.el7
scapy-2.4.0-2.el7

Details about builds:



 grip-3.7.1-1.el7 (FEDORA-EPEL-2018-ef39af46e5)
 Front-end for CD rippers and Ogg Vorbis encoders

Update Information:

Updated to 3.7.1

ChangeLog:

* Thu Apr 26 2018 Adrian Reber  - 1:3.7.1-1
- Updated to 3.7.1
* Wed Feb  7 2018 Fedora Release Engineering  - 
1:3.6.3-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jan 31 2018 Adrian Reber  - 1:3.6.3-1
- Updated to 3.6.3
- Remove icon scriptlets

References:

  [ 1 ] Bug #1558285 - grip-3.7.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1558285




 paho-c-1.2.1-0.el7 (FEDORA-EPEL-2018-a924a3397c)
 MQTT C Client

Update Information:

Updates paho-c package to the latest upstream version 1.2.1

ChangeLog:

* Sat Apr 28 2018 Otavio R. Piske  - 1.2.1-0
- Updates paho-c package to the latest upstream version 1.2.1
- Adjust the location of the documentation within the documentation dir
* Thu Feb  8 2018 Fedora Release Engineering  - 
1.2.0-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild




 python-moksha-hub-1.5.6-1.el7 (FEDORA-EPEL-2018-26960d4fb5)
 Hub components for Moksha

Update Information:

STOMP: wait at most 60 seconds between reconnect attempts, c/o @mikeb
https://github.com/mokshaproject/moksha/pull/56

ChangeLog:

* Mon Apr 30 2018 Ralph Bean  - 1.5.6-1
- new version




 scapy-2.4.0-2.el7 (FEDORA-EPEL-2018-464dc8924c)
 Interactive packet manipulation tool and network scanner

Update Information:

Update to bugfix reease.

ChangeLog:

* Mon Apr 30 2018 Michal Ambroz  - 2.4.0-2
- disable the test for now - there is too many failing (network) tests
* Mon Apr 30 2018 Michal Ambroz  - 2.4.0-1
- bump to 2.4.0 release
* Fri Mar  9 2018 Michal Ambroz  - 2.4.0-0.rc5.1
- bump to upstream 2.4.0 release candidate 5
- enable separate python3 and python2 build
* Fri Feb  9 2018 Fedora Release Engineering  - 
2.3.3-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jan 31 2018 Iryna Shcherbina  - 2.3.3-3
- Update Python 2 dependency declarations to new packaging standards
  (See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
* Thu Jul 27 2017 Fedora Release Engineering  - 
2.3.3-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild

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

Re: Serious problem with SATA LPM in F28 on Lenovo 50 series laptops

[Lorenzo Dalrio]

Hi,
i run fedora 28 on a t450 since it was promoted to beta working with it
8-10 hours per day without any issue.

System Information
 Manufacturer: LENOVO
 Product Name: 20BUS003IX
 Version: ThinkPad T450

# cat /sys/class/scsi_host/host*/link_power_management_policy
med_power_with_dipm
med_power_with_dipm
med_power_with_dipm

=== START OF INFORMATION SECTION ===
Model Family: SanDisk based SSDs
Device Model: SanDisk SD7UB3Q256G1001
Serial Number:153446402316
LU WWN Device Id: 5 001b44 ec5b3450c
Firmware Version: X2240501
User Capacity:256,060,514,304 bytes [256 GB]
Sector Size:  512 bytes logical/physical
Rotation Rate:Solid State Device
Form Factor:  2.5 inches
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Tue May  1 08:39:01 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

-- 
Lorenzo Dalrio
Il giorno lun 30 apr 2018 alle ore 17:10 Hans de Goede 
ha scritto:

> Hi,

> On 29-04-18 21:03, Alexander Ploumistos wrote:
> > Hello Hans,
> >
> > I've just upgraded a G50-30 and like Christian, I can not reproduce the
> > issue. I logged into MATE and GNOME, played with the brightness settings
> > while plugged in and on battery, it did not hang.
> >
> > # cat /sys/class/scsi_host/host*/link_power_management_policy
> > med_power_with_dipm
> > med_power_with_dipm
> >
> >
> > SMART data:
> >
> > Model Family: Seagate FireCuda 2.5
> > Device Model: ST1000LX015-1U7172
> > Serial Number:
> > LU WWN Device Id: 5 000c50 0acde0e96
> > Firmware Version: SDM1
> > User Capacity:1,000,204,886,016 bytes [1.00 TB]
> > Sector Sizes: 512 bytes logical, 4096 bytes physical
> > Rotation Rate:5400 rpm
> > Form Factor:  2.5 inches
> > Device is:In smartctl database [for details use: -P show]
> > ATA Version is:   ACS-3 T13/2161-D revision 3b
> > SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
> > Local Time is:Sun Apr 29 20:48:35 2018 CEST
> > SMART support is: Available - device has SMART capability.
> > SMART support is: Enabled
> >
> > I hope that helps,

> It is good to hear that not everyone with a 50 series seems
> affected, note though that of the 3 reporters so far only
> one can reproduce with the brightness keys and the other
> 2 see a hard-freeze about once every 24 hours, so you might
> be affected but not know it yet.

> If you do experience unexplained freezes try disabling the
> LPM, see:
> https://fedoraproject.org/wiki/Common_F28_bugs#lpm-hang

> And then wait for a few days to confirm the freeze is
> really gone.

> Regards,

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

[Bug 1570273] perl-Storable-3.09 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
perl-Storable-3.09-1.fc28 has been pushed to the Fedora 28 stable repository.
If problems still persist, please make note of it in this bug report.

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

[Bug 1570265] perl-Digest-SHA-6.02 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
perl-Digest-SHA-6.02-1.fc28 has been pushed to the Fedora 28 stable repository.
If problems still persist, please make note of it in this bug report.

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