[Fedocal] Reminder meeting : Modularity WG (once every two weeks)

[jkurik]

Dear all,

You are kindly invited to the meeting:
   Modularity WG (once every two weeks) on 2018-06-12 from 10:00:00 to 11:00:00 
US/Eastern
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki 
page](https://fedoraproject.org/wiki/Modularity_Working_Group)

The agenda for the meeting is available at [modularity-wg-agendas 
pad](https://board.net/p/modularity-wg-agendas).



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

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

[EPEL-devel] Re: atril dependency issue

[Ken Taylor]

On 06/11/2018 03:17 PM, Anssi Johansson wrote:

Ken Taylor kirjoitti 11.6.2018 klo 22.00:

The dependency issue is as follows:

Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
    Requires: libjavascriptcoregtk-1.0.so.0()(64bit)
Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
    Requires: libwebkitgtk-1.0.so.0()(64bit)
Error: Package: atril-libs-1.16.1-1.el7.x86_64 (epel)
    Requires: libwebkitgtk-1.0.so.0()(64bit)

Would the atril packager be kind enough to put this on their to-do 
list? If I need to file a bug report I will be happy to do that as well.


Already being taken care of: 
https://bugzilla.redhat.com/show_bug.cgi?id=1589486


Try your yum command with --enablerepo=epel-testing
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/KBOLIY7NSQL6C3N7JT6W6BTZQYQEZGUH/


Understood. Thanks!
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/PWU4J5EAKSQMY4E6O3IW6I6L4OLWW3ZV/

[EPEL-devel] Re: atril dependency issue

[Anssi Johansson]

Ken Taylor kirjoitti 11.6.2018 klo 22.00:

The dependency issue is as follows:

Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
    Requires: libjavascriptcoregtk-1.0.so.0()(64bit)
Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
    Requires: libwebkitgtk-1.0.so.0()(64bit)
Error: Package: atril-libs-1.16.1-1.el7.x86_64 (epel)
    Requires: libwebkitgtk-1.0.so.0()(64bit)

Would the atril packager be kind enough to put this on their to-do list? 
If I need to file a bug report I will be happy to do that as well.


Already being taken care of: 
https://bugzilla.redhat.com/show_bug.cgi?id=1589486


Try your yum command with --enablerepo=epel-testing
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/KBOLIY7NSQL6C3N7JT6W6BTZQYQEZGUH/

[EPEL-devel] Re: wine 3 package

[Richard Grainger]

Thanks for the confirmation Ken! For the benefit of others, the repo
should work with or without epel.  If you do have epel, wine32
coexists with wine64. Wine64 has the priority for the wine command
under the "alternatives" system. The i686 dependencies for wine32
coexist fine using the RHEL/CentOS multilib support (their versions
exactly match their x86_64 counterparts in epel).
On Mon, Jun 11, 2018 at 7:55 PM Ken Taylor  wrote:
>
> Thank you Mr. Grainger!!!
>
> I have just conducted a test as follows:
>
> 1 - fresh install CentOS 7.5 - minimal installation
> 2 - update and reboot
> 3 - add epel repository and yum-priorities
> 4 - set CentOS-Base priority=1, epel priority=10
> 5 - groupinstall "X Window system" mate-desktop-environment (issue with
> atril - skipped)
> 6 - systemctl set-target graphical.target and reboot
> 7 - installed your repo
> "ttps://harbottle.gitlab.io/wine32/7/i386/wine32-release.rpm" and set
> priority=9
> 8 - yum -y install wine.i686
> 9 - installed and tested a known 32 bit Windows program (GrabIt - a
> usenet nzb downloader). Works perfectly!
>
> I have a couple of other Windows programs which I will test but I think
> we can declare success.
>
> Thank you again,
>
> Ken Taylopr
>
> On 06/10/2018 07:47 PM, Richard Grainger wrote:
> > I've finally updated the wine32 repo for CentOS 7.5 (which has 32 bit
> > rebuilds of the required epel packages).  Details here:
> >
> > https://gitlab.com/harbottle/wine32
> > https://harbottle.gitlab.io/wine32/7/i386/
> >
> > Hope this helps!
> > On Thu, May 17, 2018 at 2:46 AM Ken Taylor  
> > wrote:
> >> I installed the wine 3 package from epel-testing this morning  on a
> >> newly installed CentOS 7.5 machine. The installation seemed to go fine.
> >> If I may ask two questions...
> >>
> >> Does this version of wine support 32 bit Windows programs on CentOS 7.5?
> >>
> >> If so, would someone please be kind enough to point me to some
> >> instructions as to how to configure the 32 bit environment?  I have
> >> tried configuring it as I would on Ubuntu but without luck.
> >>
> >> Thanks,
> >>
> >> Ken Taylor
> >> ___
> >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> >> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> > ___
> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/S76SYQTSSSBZRRIKV5WLZPKTUMWCKR6N/
>
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/RS6FWXRHWZ472TIDCXYOVZAKSFDPMMCS/
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/QI7YBA6IHFXHIWXAAEZF4DH2YF26E5D7/

Fedora Rawhide-20180611.n.0 compose check report

[Fedora compose checker]

No missing expected images.

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

New failures (same test did not fail in Rawhide-20180610.n.0):

ID: 248058  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/248058
ID: 248061  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/248061
ID: 248081  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/248081
ID: 248134  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/248134
ID: 248187  Test: i386 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/248187
ID: 248191  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/248191
ID: 248194  Test: i386 universal install_lvmthin
URL: https://openqa.fedoraproject.org/tests/248194
ID: 248195  Test: i386 universal install_blivet_ext3
URL: https://openqa.fedoraproject.org/tests/248195
ID: 248249  Test: x86_64 Server-dvd-iso server_database_client
URL: https://openqa.fedoraproject.org/tests/248249
ID: 248253  Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/248253

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

ID: 248062  Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/248062
ID: 248068  Test: x86_64 Workstation-live-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/248068
ID: 248079  Test: i386 Workstation-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/248079
ID: 248082  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/248082
ID: 248096  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/248096
ID: 248188  Test: i386 universal install_blivet_lvmthin
URL: https://openqa.fedoraproject.org/tests/248188
ID: 248254  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/248254

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

New soft failures (same test did not soft fail in Rawhide-20180610.n.0):

ID: 248065  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/248065
ID: 248173  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/248173
ID: 248179  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/248179
ID: 248182  Test: i386 universal install_software_raid
URL: https://openqa.fedoraproject.org/tests/248182

Old soft failures (same test soft failed in Rawhide-20180610.n.0):

ID: 248059  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/248059
ID: 248143  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/248143
ID: 248144  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/248144
ID: 248156  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/248156
ID: 248158  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/248158
ID: 248166  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/248166
ID: 248167  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/248167
ID: 248174  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/248174
ID: 248181  Test: i386 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/248181
ID: 248183  Test: i386 universal install_btrfs
URL: https://openqa.fedoraproject.org/tests/248183
ID: 248184  Test: i386 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/248184
ID: 248185  Test: i386 universal install_blivet_no_swap
URL: https://openqa.fedoraproject.org/tests/248185
ID: 248186  Test: i386 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/248186
ID: 248189  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/248189
ID: 248190  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/248190
ID: 248193  Test: i386 universal install_ext3
URL: https://openqa.fedoraproject.org/tests/248193
ID: 248196  Test: i386 universal install_blivet_btrfs
URL: https://openqa.fedoraproject.org/tests/248196

Passed openQA tests: 109/137 (x86_64), 4/24 (i386)

New passes (same test did not pass in Rawhide-20180610.n.0):

ID: 248071  Test: x86_64 Workstation-live-iso desktop_update_graphical

[EPEL-devel] atril dependency issue

[Ken Taylor]

This afternoon I was building a test machine as follows and experienced 
a dependency issue with atril


1 - fresh install CentOS 7.5 - minimal installation
2 - update and reboot
3 - add epel repository and yum-priorities
4 - set CentOS-Base priority=1, epel priority=10
5 - groupinstall "X Window system" mate-desktop-environment

At this point I received a dependency issue with atril. I skipped broken 
and completed the install. I determined that the atrl package was from epel.


[root@taylor15 ken]# repoquery -i atril

Name    : atril
Version : 1.16.1
Release : 1.el7
Architecture: x86_64
Size    : 4372080
Packager    : Fedora Project
Group   : Unspecified
URL : http://mate-desktop.org
Repository  : epel
Summary : Document viewer
Source  : atril-1.16.1-1.el7.src.rpm

The dependency issue is as follows:

Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
   Requires: libjavascriptcoregtk-1.0.so.0()(64bit)
Error: Package: atril-1.16.1-1.el7.x86_64 (epel)
   Requires: libwebkitgtk-1.0.so.0()(64bit)
Error: Package: atril-libs-1.16.1-1.el7.x86_64 (epel)
   Requires: libwebkitgtk-1.0.so.0()(64bit)

Would the atril packager be kind enough to put this on their to-do list? 
If I need to file a bug report I will be happy to do that as well.


Thanks,

Ken Taylor

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/SVFWND2OYTMHS6BUORPLC2HKRJXESG2H/

[EPEL-devel] Re: wine 3 package

[Ken Taylor]

Thank you Mr. Grainger!!!

I have just conducted a test as follows:

1 - fresh install CentOS 7.5 - minimal installation
2 - update and reboot
3 - add epel repository and yum-priorities
4 - set CentOS-Base priority=1, epel priority=10
5 - groupinstall "X Window system" mate-desktop-environment (issue with 
atril - skipped)

6 - systemctl set-target graphical.target and reboot
7 - installed your repo 
"ttps://harbottle.gitlab.io/wine32/7/i386/wine32-release.rpm" and set 
priority=9

8 - yum -y install wine.i686
9 - installed and tested a known 32 bit Windows program (GrabIt - a 
usenet nzb downloader). Works perfectly!


I have a couple of other Windows programs which I will test but I think 
we can declare success.


Thank you again,

Ken Taylopr

On 06/10/2018 07:47 PM, Richard Grainger wrote:

I've finally updated the wine32 repo for CentOS 7.5 (which has 32 bit
rebuilds of the required epel packages).  Details here:

https://gitlab.com/harbottle/wine32
https://harbottle.gitlab.io/wine32/7/i386/

Hope this helps!
On Thu, May 17, 2018 at 2:46 AM Ken Taylor  wrote:

I installed the wine 3 package from epel-testing this morning  on a
newly installed CentOS 7.5 machine. The installation seemed to go fine.
If I may ask two questions...

Does this version of wine support 32 bit Windows programs on CentOS 7.5?

If so, would someone please be kind enough to point me to some
instructions as to how to configure the 32 bit environment?  I have
tried configuring it as I would on Ubuntu but without luck.

Thanks,

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

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/S76SYQTSSSBZRRIKV5WLZPKTUMWCKR6N/


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/RS6FWXRHWZ472TIDCXYOVZAKSFDPMMCS/

f28 dnf update, passivetex texlive broken?

[Carl Byington]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

 Problem 1: package passivetex-1.25-23.fc28.noarch requires xmltex >=
20020625-10, but none of the providers can be installed
  - package texlive-xmltex-7:20170520-29.fc28.noarch obsoletes texlive-
xmltex-bin < 7:20170520 provided by texlive-xmltex-
bin-6:svn3006.0-42.20160520.fc28.noarch
  - cannot install the best update candidate for package texlive-
xmltex-6:svn40855-42.fc28.2.noarch
  - cannot install the best update candidate for package
passivetex-1.25-23.fc28.noarch
 Problem 2: package xmlto-tex-0.0.28-6.fc28.noarch requires passivetex
>= 1.11, but none of the providers can be installed
  - package passivetex-1.25-23.fc28.noarch requires xmltex >=
20020625-10, but none of the providers can be installed
  - package texlive-xmltex-7:20170520-29.fc28.noarch obsoletes texlive-
xmltex-bin < 7:20170520 provided by texlive-xmltex-
bin-6:svn3006.0-42.20160520.fc28.noarch
  - cannot install the best update candidate for package xmlto-
tex-0.0.28-6.fc28.noarch
  - cannot install the best update candidate for package texlive-xmltex-
bin-6:svn3006.0-42.20160520.fc28.noarch


I am not sure how to work around this.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAlset9EACgkQL6j7milTFsGwdgCfZ6MWAq3mhC7Sh1dpzkm4NUsa
EEwAn1FSOKbHfembvKHltEyAx7nnNLy9
=5eKF
-END 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SHRRQYHC2YJWOIAB4UHGSGOQNK4NYV76/

[389-devel] please review: PR 49774 - remove python2 from scripts

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/49774
___
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org/message/NB532OGRBZBQYTDOYHDOHMEOQEKFDTTM/

Re: broken package needs attention: libgda

[Fabio Valentini]

On Mon, Jun 11, 2018 at 9:39 AM Haïkel  wrote:
>
> 2018-06-10 22:46 GMT+02:00 Sérgio Basto :
> > On Sun, 2018-06-10 at 18:27 +0200, Fabio Valentini wrote:
> >> Hi,
> >>
> >> The "libgda" package is quite broken in fedora, which is impacting
> >> dependent programs.
> >>
> >> - The last successful build of libgda was for the fedora 24 (!) mass
> >> rebuild. No more recent builds succeeded, and the packages was
> >> reported as FTBFS.
> >> - Not even the latest version is packaged (5.2.2 instead of 5.2.4).
> >>
> >> This is leading to problems in all current releases of fedora. For
> >> example, the mysql database provider can't be installed anymore,
> >> because libgda wasn't rebuilt for soname bumps in mariadb/mysql.
> >>
> >> Packages depending on libgda include:
> >>
> >> - anjuta
> >> - glom
> >> - gnumeric-plugins-extras
> >> - gtranslator
> >> - noise
> >> - sequeler
> >>
> >> Is there any procedure for dealing with a package that's obviously
> >> outdated and broken (and has been for 3 fedora releases), but is
> >> still depended on by other packages?
> >>
> >> There has been an open bug report [0] about the FTBFS issues, but no
> >> actions have been taken so far by the package maintainer(s).
> >>
> >> Fabio
> >>
> >> [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1423852
> >
> >
> > I see 3 patches there and we got another bug report  [1]
> >
> > The best would be add one pull request in src.f.o [2] , i.e do a fork
> > apply the patch and submit one pull request .
> >
> >
> > [1]
> > https://bugzilla.redhat.com/show_bug.cgi?id=1556039
> >
> >
> > [2]
> >  https://src.fedoraproject.org/rpms/libgda/pull-requests
> >
> > --
> > Sérgio M. B.
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KGBVPAILSYUXYYWPOGECPPSCDYMICFIX/
>

Hi Haïkel,

> Sending an email to libgda-owner would have raised the attention on
> your patches.
> I got a notification late night about and I planned to go through it
> later today (currently, I am teaching a class and I still have my
> $dayjob duty)

Nope, the patches weren't written by me. I was just trying to raise
attention to the issue that the package hasn't been built successfully
for 2 years and it's causing problems with my (and other) packages.

> libgda is co-maintained with the desktop team but it seems that the
> project is not anymore
> maintained in GNOME upstream hence its sore state.

However, it looks like there has been an influx of activity since the
project moved to GNOME's GitLab instance.

> So first task is to apply those patches and possibly, send them
> upstream. Second task is to determine if we should drop the packages
> (and it includes all the bindings to libgda),
> but I need more time for that.
>
> Alternative is you want comaintainership, just ask, you're welcome :)

I don't know if I would even want to maintain this package, the
upstream project looks like a terrible mess ;)
However, two of my packages depend on it - so I wouldn't want it to be
killed, either.

That said, I tried to put all the stuff together and cleaned up and
fixed the package, updated it to 5.2.4, and this is as far as I've
come:

https://src.fedoraproject.org/fork/decathorpe/rpms/libgda/c/ee7d3434169944438d10939a1e2075b2b10ab3ed
https://koji.fedoraproject.org/koji/taskinfo?taskID=27562988

Remaining issues:

- building gtk-doc documentation fails miserably
- building with system sqlite3 fails miserably (I don't know if that's
a deal-breaker or not)

Fabio

> Regards,
> H.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BV6IP6FF6VRJDJM4PILHC3LCK74WRYSF/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JYMGKKU6MP2XL32ZFTE4DKO2B73LLEAB/

[Bug 1589473] perl-MooX-Struct-0.017 is available

[bugzilla]

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



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

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/GI3OWCERIYE6NHNH5VPL6XPWMQTWZYVS/

[Bug 1589471] perl-Email-Address-XS-1.04 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
perl-Email-Address-XS-1.04-1.fc28 has been pushed to the Fedora 28 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-22fb281193

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/D6ZYIPQAA7EKCTDECIU5GX5QXB5AWEEG/

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

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  61  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-dd6e4a3f0b   
python34-3.4.8-1.el6
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-fca9555db1   
cobbler-2.6.11-7.git95749a6.el6
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1ceee884b4   
prosody-0.10.2-1.el6
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-029b32bcf4   
singularity-2.5.1-1.el6
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c   
unrtf-0.21.9-8.el6


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

php-horde-Horde-Core-2.31.3-1.el6
python-fedmsg-meta-fedora-infrastructure-0.26.0-1.el6

Details about builds:



 php-horde-Horde-Core-2.31.3-1.el6 (FEDORA-EPEL-2018-af197075d3)
 Horde Core Framework libraries

Update Information:

**Horde_Core 2.31.3**  * [mjr] Protect against empty imap adapters when no email
support is enabled for EAS (Bug #14820).

ChangeLog:

* Mon Jun 11 2018 Remi Collet  - 2.31.3-1
- update to 2.31.3




 python-fedmsg-meta-fedora-infrastructure-0.26.0-1.el6 
(FEDORA-EPEL-2018-a485b29025)
 Metadata providers for Fedora Infrastructure's fedmsg deployment

Update Information:

Upgrade to 0.26.0  Changelog is at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0260  
Update to 0.25.0  Changelog at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0250

ChangeLog:

* Mon Jun 11 2018 Pierre-Yves Chibon  - 0.26.0-1
- Update to 0.26.0
* Tue May 29 2018 Pierre-Yves Chibon  - 0.25.0-2
- Fix the Requires in el6
* Fri May 25 2018 Pierre-Yves Chibon  - 0.25.0-1
- Update to 0.25.0

___
epel-devel mailing list -- epel-de...@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org/message/F6V4FXNWNUZTQGVHFKLYB5F4ICSODV3B/

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  15  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-90002f509e   
pdns-recursor-4.1.3-2.el7
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-65614e9fc9   
thunderbird-enigmail-2.0.6-1.el7
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-bbdc0ecf38   
cobbler-2.8.3-2.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7155fb2e51   
prosody-0.10.2-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-86538d58b1   
strongswan-5.6.3-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e14afdfcb2   
singularity-2.5.1-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3835d39d1a   
unrtf-0.21.9-8.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-04bf550089   
nikto-2.1.6-1.el7


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

php-horde-Horde-Core-2.31.3-1.el7
python-fedmsg-meta-fedora-infrastructure-0.26.0-1.el7

Details about builds:



 php-horde-Horde-Core-2.31.3-1.el7 (FEDORA-EPEL-2018-ac4617a8b4)
 Horde Core Framework libraries

Update Information:

**Horde_Core 2.31.3**  * [mjr] Protect against empty imap adapters when no email
support is enabled for EAS (Bug #14820).

ChangeLog:

* Mon Jun 11 2018 Remi Collet  - 2.31.3-1
- update to 2.31.3




 python-fedmsg-meta-fedora-infrastructure-0.26.0-1.el7 
(FEDORA-EPEL-2018-e431856757)
 Metadata providers for Fedora Infrastructure's fedmsg deployment

Update Information:

Upgrade to 0.26.0  Changelog is at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0260  
Update to 0.25.0  Changelog at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0250

ChangeLog:

* Mon Jun 11 2018 Pierre-Yves Chibon  - 0.26.0-1
- Update to 0.26.0
* Tue May 29 2018 Pierre-Yves Chibon  - 0.25.0-2
- Fix the Requires in el6
* Fri May 25 2018 Pierre-Yves Chibon  - 0.25.0-1
- Update to 0.25.0

___
epel-devel mailing list -- epel-de...@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org/message/XQITW3NEECY3WT6T3PV42KS2D2YPGMTC/

Fedora rawhide compose report: 20180611.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20180610.n.0
NEW: Fedora-Rawhide-20180611.n.0

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

Size of added packages:  31.77 MiB
Size of dropped packages:1.00 MiB
Size of upgraded packages:   400.29 MiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20180611.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20180610.n.0.s390x.tar.xz
Image: Container_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Base-Rawhide-20180610.n.0.s390x.tar.xz

= ADDED PACKAGES =
Package: R-hms-0.4.2-1.fc29
Summary: Pretty Time of Day
RPMs:R-hms
Size:63.11 KiB

Package: elementary-screenshot-tool-0.1.5-1.fc29
Summary: Screenshot tool designed for elementary
RPMs:elementary-screenshot-tool
Size:813.05 KiB

Package: golang-github-lucasb-eyer-colorful-1.0-1.fc29
Summary: A library for playing with colors in Go
RPMs:golang-github-lucasb-eyer-colorful-devel
Size:36.79 KiB

Package: golang-github-mattn-shellwords-1.0.3-5.fc29
Summary: Parse line as shell words
RPMs:golang-github-mattn-shellwords-devel
Size:12.13 KiB

Package: golang-github-pebbe-zmq4-0-0.1.20180610git5b443b6.fc29
Summary: Go interface to ZeroMQ version 4
RPMs:golang-github-pebbe-zmq4-devel
Size:44.54 KiB

Package: golang-github-thomsonreuterseikon-ntlm-0-0.6.20180610git51f51a3.fc29
Summary: Native implementation of NTLM for Go
RPMs:golang-github-thomsonreuterseikon-ntlm-devel
Size:40.92 KiB

Package: golang-gopkg-data-dog-sqlmock-1-1.3.0-1.fc29
Summary: SQL mock driver for golang to test database interactions
RPMs:golang-gopkg-data-dog-sqlmock-1-devel
Size:29.89 KiB

Package: python-PyMuPDF-1.13.9-1.fc29
Summary: Python binding for MuPDF - a lightweight PDF and XPS viewer
RPMs:python-PyMuPDF-doc python2-PyMuPDF python3-PyMuPDF
Size:30.76 MiB


= DROPPED PACKAGES =
Package: golang-github-ThomsonReutersEikon-go-ntlm-0-0.5.20171030git2a7c173.fc28
Summary: Native implementation of NTLM for Go
RPMs:golang-github-ThomsonReutersEikon-go-ntlm-devel 
golang-github-ThomsonReutersEikon-go-ntlm-unit-test-devel
Size:152.17 KiB

Package: golang-github-mattn-go-shellwords-1.0.3-4.fc28
Summary: Parse line as shell words
RPMs:golang-github-mattn-go-shellwords-devel 
golang-github-mattn-go-shellwords-unit-test-devel
Size:70.63 KiB

Package: screenshot-tool-0.1.4-5.fc28
Summary: Simple screen capture tool
RPMs:screenshot-tool
Size:804.92 KiB


= UPGRADED PACKAGES =
Package:  boomaga-1.3.0-1.git7e1e19c.fc29
Old package:  boomaga-1.2.0-2.git4f75b03.fc29
Summary:  A virtual printer for viewing a document before printing
RPMs: boomaga boomaga-selinux
Size: 3.30 MiB
Size change:  156.80 KiB
Changelog:
  * Sun Jun 10 2018 Martin Gansser  - 
1.3.0-1.git7e1e19c
  - Update to 1.3.0-1.7e1e19cd


Package:  buildah-1.2-1.gitb9983a6.fc29
Old package:  buildah-1.0-20.gitf449b28.fc29
Summary:  A command line tool used for creating OCI Images
RPMs: buildah
Size: 17.63 MiB
Size change:  22.29 KiB
Changelog:
  * Sun Jun 10 2018 Dan Walsh  1.1-1
  - Drop capabilities if running container processes as non root
  - Print Warning message if cmd will not be used based on entrypoint
  - Update 01-intro.md
  - Shouldn't add insecure registries to list of search registries
  - Report errors on bad transports specification when pushing images
  - Move parsing code out of common for namespaces and into pkg/parse.go
  - Add disable-content-trust noop flag to bud
  - Change freenode chan to buildah
  - runCopyStdio(): don't close stdin unless we saw POLLHUP
  - Add registry errors for pull
  - runCollectOutput(): just read until the pipes are closed on us
  - Run(): provide redirection for stdio
  - rmi, rm: add test
  - add mount test
  - Add parameter judgment for commands that do not require parameters
  - Add context dir to bud command in baseline test
  - run.bats: check that we can run with symlinks in the bundle path
  - Give better messages to users when image can not be found
  - use absolute path for bundlePath
  - Add environment variable to buildah --format
  - rm: add validation to args and all option
  - Accept json array input for config entrypoint
  - Run(): process RunOptions.Mounts, and its flags
  - Run(): only collect error output from stdio pipes if we created some
  - Add OnBuild support for Dockerfiles
  - Quick fix on demo readme
  - run: fix validate flags
  - buildah bud should require a context directory or URL
  - Touchup tutorial for run changes
  - Validate common bud and from flags
  - images

Re: Is there some problem uploading sources now?

[Richard W.M. Jones]

On Mon, Jun 11, 2018 at 09:58:40AM -0500, Michael Cronenworth wrote:
> On 06/11/2018 09:55 AM, Stephen John Smoogen wrote:
> >Yes at the time I am writing this 2018-06-11T10:54-0400 we are in an
> >unplanned outage on src.fedoraproject.org. [Whether we are still in an
> >outage when you read this is another matter.
> 
> Should be fixed now. I successfully ran new-sources and a Koji build.

Yes, seems to be working now, thanks!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EO3HK2E6FXFF4TVSOXB4KG7MJ4D2BNL5/

Re: Proposal: Abandon v8 package

[Eamon Walsh]

On 6/11/2018 10:42 AM, Tom Callaway wrote:
> Background:
>
> I made the original v8 Fedora package many moons ago, when I was more
> optimistic about the possibility of separating the useful components
> inside of chromium. Since that point, it has become clear that while v8
> is useful software, the following facts are also true:
>
> 1. The v8 upstream is entirely disinterested in the concept of
> maintaining any sort of ABI/API consistency between releases.
> 2. The v8 that is used in chromium is not necessarily compatible with
> the upstream v8, as they have a history of picking and choosing code
> changes (and even applying chromium specific changes locally).
> 3. Virtually all consumers of v8 (including chromium) take a git
> checkout (not a specific one, just whatever they decided to code to) and
> use that revision, often creating a local fork of v8 from that revision,
> as they are either unwilling or unable to track v8 upstream.
> 4. Since v8 has no concept of a "stable" release that I can see, they
> simply do security fixes to the master branch, which, combined with the
> code changing violently, makes it very difficult to backport security fixes.
>
> This means that other than plv8 (which is currently unable to build
> against the current v8 package in Fedora), I do not see any consumers of
> the Fedora v8 package (chromium has long since abandoned any possibility
> of using it). It does contain a "d8" binary, which is a javascript CLI
> debugger, but it is not clear to me that this is widely used, or that
> the benefit of its inclusion in Fedora outweighs the pain of maintaining
> this package.


My packages in COPR depend on libv8 but I can just bundle it so it's not
a problem. Thanks for maintaining it to this point.


-- 
Eamon Walsh
https://termysequence.io
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7ZAEIUBMIWGXTYSJJ5OT6PECP7J3UC6A/

[389-devel] please review: Ticket 49576 - Fix ds-replcheck certificate dir verification

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/49773
___
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-de...@lists.fedoraproject.org/message/SK5WH5Y4INEN4KOXLRJEW34AUU4Y2ULY/

Re: Is there some problem uploading sources now?

[Michael Cronenworth]

On 06/11/2018 09:55 AM, Stephen John Smoogen wrote:

Yes at the time I am writing this 2018-06-11T10:54-0400 we are in an
unplanned outage on src.fedoraproject.org. [Whether we are still in an
outage when you read this is another matter.


Should be fixed now. I successfully ran new-sources and a Koji build.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PGZYDKDVM3FRO7LHUR5XKRATJKML77XI/

Re: Is there some problem uploading sources now?

[Stephen John Smoogen]

On 11 June 2018 at 10:55, Stephen John Smoogen  wrote:
> Yes at the time I am writing this 2018-06-11T10:54-0400 we are in an
> unplanned outage on src.fedoraproject.org. [Whether we are still in an
> outage when you read this is another matter.
>

The outage was over by the time I hit send.

> On 11 June 2018 at 10:43, Richard W.M. Jones  wrote:
>>
>> To answer my own question, there's definitely some kind of problem ...
>>
>> $ fedpkg new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig
>> Could not execute new_sources: Error occurs inside the server.
>> $ fedpkg sources
>> Downloading nbdkit-1.3.3.tar.gz
>>  
>> 100.0%
>> Remove downloaded invalid file ./nbdkit-1.3.3.tar.gz
>> Could not execute sources: Server returned status code 404
>>
>> With -v it gives a long stack trace which seems to be some kind
>> of server problem I suppose:
>>
>> $ fedpkg -v new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig
>> Creating repo object from /home/rjones/d/fedora/nbdkit/master
>> Could not execute new_sources: Error occurs inside the server.
>> Traceback (most recent call last):
>>   File "/usr/bin/fedpkg", line 11, in 
>> load_entry_point('fedpkg==1.32', 'console_scripts', 'fedpkg')()
>>   File "/usr/lib/python2.7/site-packages/fedpkg/__main__.py", line 84, in 
>> main
>> sys.exit(client.args.command())
>>   File "/usr/lib/python2.7/site-packages/pyrpkg/cli.py", line 1619, in 
>> new_sources
>> self.cmd.upload(self.args.files, replace=self.args.replace)
>>   File "/usr/lib/python2.7/site-packages/pyrpkg/__init__.py", line 2435, in 
>> upload
>> f, file_hash)
>>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 296, in 
>> upload
>> if self.remote_file_exists(name, filename, hash):
>>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 262, in 
>> remote_file_exists
>> self.raise_upload_error(status)
>>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 133, in 
>> raise_upload_error
>> raise UploadError(message, http_status=http_status)
>> pyrpkg.errors.UploadError: Error occurs inside the server.
>>
>> 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
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BLTSDSPPMAUOWDPVPDLRS37OBH2GTTBM/
>
>
>
> --
> Stephen J Smoogen.



-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JUGOWF4RGNXZELQZRRAOE3JUSUYVIE6S/

Re: Is there some problem uploading sources now?

[Stephen John Smoogen]

Yes at the time I am writing this 2018-06-11T10:54-0400 we are in an
unplanned outage on src.fedoraproject.org. [Whether we are still in an
outage when you read this is another matter.

On 11 June 2018 at 10:43, Richard W.M. Jones  wrote:
>
> To answer my own question, there's definitely some kind of problem ...
>
> $ fedpkg new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig
> Could not execute new_sources: Error occurs inside the server.
> $ fedpkg sources
> Downloading nbdkit-1.3.3.tar.gz
>  
> 100.0%
> Remove downloaded invalid file ./nbdkit-1.3.3.tar.gz
> Could not execute sources: Server returned status code 404
>
> With -v it gives a long stack trace which seems to be some kind
> of server problem I suppose:
>
> $ fedpkg -v new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig
> Creating repo object from /home/rjones/d/fedora/nbdkit/master
> Could not execute new_sources: Error occurs inside the server.
> Traceback (most recent call last):
>   File "/usr/bin/fedpkg", line 11, in 
> load_entry_point('fedpkg==1.32', 'console_scripts', 'fedpkg')()
>   File "/usr/lib/python2.7/site-packages/fedpkg/__main__.py", line 84, in main
> sys.exit(client.args.command())
>   File "/usr/lib/python2.7/site-packages/pyrpkg/cli.py", line 1619, in 
> new_sources
> self.cmd.upload(self.args.files, replace=self.args.replace)
>   File "/usr/lib/python2.7/site-packages/pyrpkg/__init__.py", line 2435, in 
> upload
> f, file_hash)
>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 296, in 
> upload
> if self.remote_file_exists(name, filename, hash):
>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 262, in 
> remote_file_exists
> self.raise_upload_error(status)
>   File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 133, in 
> raise_upload_error
> raise UploadError(message, http_status=http_status)
> pyrpkg.errors.UploadError: Error occurs inside the server.
>
> 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
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BLTSDSPPMAUOWDPVPDLRS37OBH2GTTBM/



-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GNKOI2KF7H5OHANKGL4DBXFZERM7L2VL/

[Bug 1589473] perl-MooX-Struct-0.017 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/DNCKWLUFUYYOX22NW5WSSXIWESF3M6EC/

Plan to orphan 'plv8' package -- V8 Engine for PostgreSQL

[Pavel Raiskup]

Fedora's v8/v8-devel were updated (F28) and the environment is now
incompatible with F28's (already built) plv8.

Honestly, I plan to orphan the package because v8 environment is probably
only supposed to be bundled, and I'm not ready to take the responsibility
for bundling that huge thing...  If anyone has the use-case for plv8 --
and is OK to take care of 'Provides: bundled(v8)', let me know -- I'd be
happy to hand-over the package to new maintainer.

More info:

  https://bugzilla.redhat.com/show_bug.cgi?id=1584453
  https://bugzilla.redhat.com/1585159
  https://github.com/plv8/plv8/issues/281
  https://bugzilla.redhat.com/show_bug.cgi?id=1585212

Pavel


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5ASGLU7T5CQ4JP63SHYSBD7VOLERU2AP/

Re: Proposal: Abandon v8 package

[Stephen Gallagher]

On Mon, Jun 11, 2018 at 10:43 AM Tom Callaway  wrote:

> Background:
>
> I made the original v8 Fedora package many moons ago, when I was more
> optimistic about the possibility of separating the useful components
> inside of chromium. Since that point, it has become clear that while v8
> is useful software, the following facts are also true:
>
> 1. The v8 upstream is entirely disinterested in the concept of
> maintaining any sort of ABI/API consistency between releases.
> 2. The v8 that is used in chromium is not necessarily compatible with
> the upstream v8, as they have a history of picking and choosing code
> changes (and even applying chromium specific changes locally).
> 3. Virtually all consumers of v8 (including chromium) take a git
> checkout (not a specific one, just whatever they decided to code to) and
> use that revision, often creating a local fork of v8 from that revision,
> as they are either unwilling or unable to track v8 upstream.
> 4. Since v8 has no concept of a "stable" release that I can see, they
> simply do security fixes to the master branch, which, combined with the
> code changing violently, makes it very difficult to backport security
> fixes.
>


For all of these same reasons, the Node.js SIG opted to carry a bundled
copy of v8 in that package as well. I think we should move to have v8
considered to be a copylib for all reasonable purposes within Fedora.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SJOAJWXLPJRO4IK6SHGWW4DR5OD3USN6/

Is there some problem uploading sources now?

[Richard W.M. Jones]

To answer my own question, there's definitely some kind of problem ...

$ fedpkg new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig 
Could not execute new_sources: Error occurs inside the server.
$ fedpkg sources
Downloading nbdkit-1.3.3.tar.gz
 100.0%
Remove downloaded invalid file ./nbdkit-1.3.3.tar.gz
Could not execute sources: Server returned status code 404

With -v it gives a long stack trace which seems to be some kind
of server problem I suppose:

$ fedpkg -v new-sources nbdkit-1.3.3.tar.gz nbdkit-1.3.3.tar.gz.sig 
Creating repo object from /home/rjones/d/fedora/nbdkit/master
Could not execute new_sources: Error occurs inside the server.
Traceback (most recent call last):
  File "/usr/bin/fedpkg", line 11, in 
load_entry_point('fedpkg==1.32', 'console_scripts', 'fedpkg')()
  File "/usr/lib/python2.7/site-packages/fedpkg/__main__.py", line 84, in main
sys.exit(client.args.command())
  File "/usr/lib/python2.7/site-packages/pyrpkg/cli.py", line 1619, in 
new_sources
self.cmd.upload(self.args.files, replace=self.args.replace)
  File "/usr/lib/python2.7/site-packages/pyrpkg/__init__.py", line 2435, in 
upload
f, file_hash)
  File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 296, in 
upload
if self.remote_file_exists(name, filename, hash):
  File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 262, in 
remote_file_exists
self.raise_upload_error(status)
  File "/usr/lib/python2.7/site-packages/pyrpkg/lookaside.py", line 133, in 
raise_upload_error
raise UploadError(message, http_status=http_status)
pyrpkg.errors.UploadError: Error occurs inside the server.

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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BLTSDSPPMAUOWDPVPDLRS37OBH2GTTBM/

Proposal: Abandon v8 package

[Tom Callaway]

Background:

I made the original v8 Fedora package many moons ago, when I was more
optimistic about the possibility of separating the useful components
inside of chromium. Since that point, it has become clear that while v8
is useful software, the following facts are also true:

1. The v8 upstream is entirely disinterested in the concept of
maintaining any sort of ABI/API consistency between releases.
2. The v8 that is used in chromium is not necessarily compatible with
the upstream v8, as they have a history of picking and choosing code
changes (and even applying chromium specific changes locally).
3. Virtually all consumers of v8 (including chromium) take a git
checkout (not a specific one, just whatever they decided to code to) and
use that revision, often creating a local fork of v8 from that revision,
as they are either unwilling or unable to track v8 upstream.
4. Since v8 has no concept of a "stable" release that I can see, they
simply do security fixes to the master branch, which, combined with the
code changing violently, makes it very difficult to backport security fixes.

This means that other than plv8 (which is currently unable to build
against the current v8 package in Fedora), I do not see any consumers of
the Fedora v8 package (chromium has long since abandoned any possibility
of using it). It does contain a "d8" binary, which is a javascript CLI
debugger, but it is not clear to me that this is widely used, or that
the benefit of its inclusion in Fedora outweighs the pain of maintaining
this package.

Thus, I propose that the v8 package be abandoned/orphaned/taken to the
farm upstate to run and play with the other dogs.

If you disagree, or are crazy enough to want to take it over, speak now.

~tom

P.S. I'll still maintain v8-314 as best I can, since there are actually
users of that. The irony of that really ancient version being considered
stable (and thus, used by other software) as a result of Fedora sticking
on that version of v8 for so many releases is not lost on me.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DI4Q5526MVI5KS7OG4PH37QFK6KCDAY2/

Re: virt-bootstrap: libvirt and SELinux issues

[Richard W.M. Jones]

(Adding virt-tools-list)

On Fri, Jun 08, 2018 at 02:20:22PM +0200, Timothée Floure wrote:
> Hello,
> 
> I'm trying to package virt-bootstrap [0], but various tests fail due to
> SELinux. I know some selinux basics from redhat's selinux manual [1],
> but am unsure about how to approach the issue.
> 
> For example, the following command - extracted from a failing test -
> fails due to SELinux:
> 
> ```
> virt-sandbox -c qemu:///session --name=bootstrap_26639 -m 
> host-bind:/mnt=/tmp/tmps77ywg1n_bootstrap_dest -- /bin/tar xf 
> /tmp/tmp8gca1fzq_bootstrap_tarfiles/b52c708f02ff0ee783331f23f723ed9123dfc72994e19d1c33f3bd5db723007a.tar
>  -C /mnt --exclude "dev/*" --overwrite --absolute-names
> ```
> 
> ```
> type=AVC msg=audit(1525329618.892:19448): avc:  denied  { read } for  
> pid=31860 comm="qemu-system-x86" name="config" dev="dm-3" ino=4589515 
> scontext=unconfined_u:unconfined_r:svirt_t:s0:c422,c725 
> tcontext=unconfined_u:object_r:gconf_home_t:s0 tclass=dir permissive=0
> ```
> 
> I also attached the related specfile to this email. I would appreciate
> if someone could take a few minutes to redirect me.
> 
> 
> [0] https://github.com/virt-manager/virt-bootstrap
> [1] 
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/part_i-selinux
> 
> Thanks !
> 
> -- 
> Timothée Floure

> %global debug_package %{nil}
> 
> Name: virt-bootstrap
> Version:  1.0.0
> Release:  1%{?dist}
> Summary:  Easy way to setup the root file system for libvirt-based containers
> 
> License:  GPLv3
> URL:  https://github.com/virt-manager/%{name}
> Source0:  https://github.com/virt-manager/%{name}/archive/v%{version}.tar.gz
> 
> BuildArch: noarch
> BuildRequires: python3-devel
> BuildRequires: perl-podlators
> BuildRequires: sed
> # Provides virt-sandbox
> BuildRequires: libvirt-sandbox
> # Provides virt-builder
> BuildRequires: libguestfs-tools-c
> BuildRequires: python3-libguestfs
> BuildRequires: python3-passlib
> BuildRequires: python3-mock
> Requires: skopeo
> # Provides virt-sandbox
> Requires: libvirt-sandbox
> # Provides virt-builder
> Requires: libguestfs-tools-c
> Requires: python3-libguestfs
> Requires: python3-passlib
> 
> %description
> %{summary}.
> 
> %prep
> %setup -q
> 
> 
> %build
> %py3_build
> 
> %install
> %py3_install
> 
> sed -i 's|#!/usr/bin/env python|#!/usr/bin/python|' \
>   %{buildroot}%{python3_sitelib}/virtBootstrap/virt_bootstrap.py
> 
> chmod +x %{buildroot}%{python3_sitelib}/virtBootstrap/virt_bootstrap.py
> 
> %check
> %{__python3} setup.py test
> 
> %files
> %license LICENSE
> %doc README.md
> %{_bindir}/%{name}
> %{python3_sitelib}/*
> %{_mandir}/man1/%{name}.1*
> 
> %changelog
> * Mon Apr 30 2018 Timothée Floure  - 1.0.0-1
> - Let there be package




> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EYYT6HPMNJXQNFRUR3BA3NLVCFLY6RMA/


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CNPP4FAWIRIH3TZGFHQUUCBGQ435XSP5/

Re: F29 System Wide Change: Strong crypto settings: phase 2

[Tomas Mraz]

On Sat, 2018-06-09 at 20:49 -0400, John Florian wrote:
> On 06/08/2018 04:07 AM, Tomas Mraz wrote:
> > On Thu, 2018-06-07 at 16:13 -0400, John Florian wrote:
> > > On 06/07/2018 08:44 AM, Tomas Mraz wrote:
> > > > On Tue, 2018-06-05 at 16:34 -0400, John Florian wrote:
> > > > > On 06/05/2018 12:25 PM, Tomas Mraz wrote:
> > > > > > On Tue, 2018-06-05 at 16:11 +, Christian Stadelmann
> > > > > > wrote:
> > > > > > > "Fallback option" always smells like "protocol downgrade
> > > > > > > attack".
> > > > > > > This would undermine the idea of a crypto policy. Anyway,
> > > > > > > implementing it seems way out of scope for the crypto
> > > > > > > policy.
> > > > > > 
> > > > > > Yes, a fallback option is a no-way. You can switch the
> > > > > > system
> > > > > > policy to
> > > > > > LEGACY, however that does not necessarily mean that some
> > > > > > very
> > > > > > old
> > > > > > legacy HW will start to work with Firefox or another web
> > > > > > browser,
> > > > > > because with newer versions of the browsers and newer
> > > > > > versions
> > > > > > of
> > > > > > TLS/crypto libraries some very old and insecure algorithm
> > > > > > and
> > > > > > protocol
> > > > > > support is being also removed.
> > > > > > 
> > > > > 
> > > > > Makes sense, but what is the best way to deal with such old
> > > > > HW if
> > > > > you're
> > > > > stuck with it?  I don't want to compromise my workstation for
> > > > > all
> > > > > my
> > > > > normal needs just to deal with some ancient embedded https
> > > > > server,
> > > > > but
> > > > > it would kind of suck to have to boot some old live image
> > > > > just to
> > > > > do
> > > > > some routine config change.  It seems the industry has room
> > > > > for
> > > > > improvement here.
> > > > 
> > > > Use a virtual machine with some old live image for such
> > > > insecure
> > > > communication?
> > > > 
> > > > I do not think any "improvement" that involves changing the
> > > > defaults to
> > > > be more lenient even if accompanied with some big warning when
> > > > such
> > > > old
> > > > insecure connection is established would be a good idea. Оnly
> > > > if
> > > > the
> > > > users really have to boot some old live image or do some
> > > > similar
> > > > unpleasant task it will really force the old HW out of
> > > > production
> > > > where
> > > > it should belong. Or we can forget about security based on
> > > > cryptographic protocols altogether.
> > > > 
> > > > Note that we are talking about SSLv2, MD4 or similar long long
> > > > time
> > > > ago
> > > > obsolete stuff. Not things that were just "recently" found as
> > > > insecure.
> > > 
> > > Oh!  I didn't realize the proposal was covering stuff /that/
> > > old. 
> > > Somehow TLS 1.1 just didn't equate in my memory with that era.
> > > Thank
> > > you 
> > > Tomas for the clarification.
> > 
> > No, this is misunderstanding. The change proposal is about newer
> > stuff
> > but the proposal allows for easy revert by setting the crypto
> > policy to
> > LEGACY.
> > 
> > What I was talking in this tread starting with my message from Tue,
> > 05
> > Jun 2018 18:25:57 +0200 was about things that possible very old
> > legacy
> > devices might require for communication that are not present in the
> > TLS
> > libraries anymore.
> > 
> 
> Okay, so IIUC now, this is an all-or-nothing kind of change.  If I
> elect/need to use LEGACY to administer some old hardware that I
> cannot
> otherwise connect to using the defaults, then I'm compromising that
> host's security for anything/everything its used for until it's taken
> back off LEGACY and returned to whatever the non-LEGACY is called. 
> Do I
> have it right now?

Yes, except one thing. Just by switching to LEGACY it does not mean
you're compromising the host's security. The protocol negotiation and
ciphersuite ordering still applies and it will use the best available
protocol and ciphersuite and not some random insecure protocol version
and ciphersuite. The insecure protocols and ciphersuites will be used
only in the case the other end does not know anything better.

They are removed from the DEFAULT policy only as a precautionary
measure and to make you to do a conscious decision whether you want to
communicate with legacy devices or not.

Also note that some of the more insecure things such as SSLv2 support,
RC4 support or <1024 bit DH key support is completely disabled so even
with LEGACY mode you cannot use these.
-- 
Tomáš Mráz
No matter how far down the wrong road you've gone, turn back.
  Turkish proverb
[You'll know whether the road is wrong if you carefully listen to your
conscience.]
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

Re: python-sphinx_rtd_theme advice

[Miro Hrončok]

On 7.6.2018 03:05, Jerry James wrote:

I somehow wound up owning python-sphinx_rtd_theme...


And BTW whatever you do, please don't do it before the Python 3.7 
rebuild. python-sphinx_rtd_theme is somewhat critical and if we break it 
or add more deps, the entire Python 3.7 think might be stuck. 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LVOCZQ5RDITZIGZY3OPISMQJITWO5VYO/

Re: Prioritizing ~/.local/bin over /usr/bin on the PATH

[Miro Hrončok]

On 11.6.2018 13:05, Tomasz Kłoczko wrote:> I would be way more 
interested of real arguments about why someone is

trying to add those $PATH modifications.
So far only "argument is that someone proposed those changes without
justification except that some other people added something like this
to some "specification" in which is not possible to find what class of
the cases solves/handles/improves.


See the change description.

--
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SCPV6ZYHSQIQIXX5WJTRIYA4WIKGZOIC/

Re: Prioritizing ~/.local/bin over /usr/bin on the PATH

[Tomasz Kłoczko]

On Sun, 10 Jun 2018 at 21:02, Sorin Sbarnea  wrote:
>
> Well said, there is no catchy name for this (virtual) security threat. We 
> will have to let one of those that oppose this proposal to find a caching 
> name (PATHEXIT?), maybe even build a paper explaining how to mitigate it.
>
> I am bit disappointed because other distributions fixed it, even twice after 
> a temporary regression due to a mistake. We never did it.
>
> Now that we have a change proposal, how to continue? To get it accepted or 
> rejected, is there a way/process that we need to follow?
>
> Should we maybe add a section to the document with supporters and opposers 
> where people can record themselves?

I would be way more interested of real arguments about why someone is
trying to add those $PATH modifications.
So far only "argument is that someone proposed those changes without
justification except that some other people added something like this
to some "specification" in which is not possible to find what class of
the cases solves/handles/improves.

kloczek
-- 
Tomasz Kłoczko | Tel: 0774 1209067 | LinkedIn: http://lnkd.in/FXPWxH
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/G32OQODR4OD2NWUO7GUIGEORBX67XYY2/

Re: F29 System Wide Change: Hide the grub menu

[Hans de Goede]

Hi,

On 10-06-18 19:02, Gerald B. Cox wrote:

On Thu, Jun 7, 2018 at 2:07 AM, Hans de Goede mailto:hdego...@redhat.com>> wrote:

Hi,

On 04-06-18 21:17, Adam Williamson wrote:

On Thu, 2018-05-31 at 12:43 +0200, Jan Kurik wrote:

= Proposed System Wide Change: Hide the grub menu =
https://fedoraproject.org/wiki/Changes/HiddenGrubMenu 




I've updated this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1406844

Basically, since at least F24 - maybe longer my boot has been interrupted by 
this message:

> sp5100-tco sp5100-tco: I/O address 0x0cd6 already in use

The bug was closed, and then cloned and reopened.

As I mentioned before, I have no problem with the grub change as long as there 
is documentation
that shows people how to reverse it if they wish - and Hans (thank you very 
much) has agreed to this.

However, seems to me that having this bug (which appears to affect all AMD 
users) languishing
for years seems to negate the reasoning behind this change.  If we're wanting 
to implement
a more or less cosmetic change which saves a few seconds, having spurious 
messages
interrupting and slowing down the boot process should also be resolved.


I agree and I have this on my radar too.

Regards,

Hans
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WC22HVHLINIO7YF3GGKXF2MGYWQDI74R/

[heads-up] soname version bump for evolution-data-server in rawhide

[Milan Crha]

Hello,
next week's 3.29.3 release of evolution-data-server (on 2018-06-18)
will contain soname version bumps of libcamel and libedata-cal. I
expect that most of the packages can be just rebuilt.

I cannot provide the complete list of affected packages, because dnf is
inaccurate [1]. There's definitely no need to rebuild everything what
requires evolution-data-server, the less indirectly, as long as it's
not statically linked, which I doubt.

The main evolution packages (evolution, evolution-ews and evolution-
mapi) will be updated at the same time as evolution-data-server. The
other surely affected are evolution-rss and evolution-rspam.

I'll check what breaks after the update is done and available for
download and I'll rebuild packages I've commit rights for myself,
unless the main maintainer(s) will be quicker.
Bye,
Milan

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1589722
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GWQQM4VIPONQHZ35TEM2FJANF6MUHKUC/

[Bug 1589471] perl-Email-Address-XS-1.04 is available

[bugzilla]

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



--- Comment #1 from Fedora Update System  ---
perl-Email-Address-XS-1.04-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-22fb281193

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/HA5QEHRZENPX2OFIXDV3R746WVJ3MCCH/

Retiring compat-giflib

[Sandro Mani]

Hi

I'll be retiring compat-giflib in rawhide next weekend if there are no 
objections. All packages have since been built against the new giflib-5.1.4.


Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/TIEMINNIQAPWLKQA64HA4VVI4UAJZ4VE/

[Bug 1589471] perl-Email-Address-XS-1.04 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Email-Address-XS-1.04-
   ||1.fc29
 Resolution|--- |RAWHIDE
Last Closed||2018-06-11 04:41:25



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/YOE2WHRS7BSI2EEATXPBFFNWQNJLW6CN/

[Bug 1589402] perl-List-SomeUtils-XS-0.58 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-List-SomeUtils-XS-0.58
   ||-1.fc29
 Resolution|--- |RAWHIDE
Last Closed||2018-06-11 04:22:44



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/TLKYDK3CPMEKR3GMS6FUKJPW6B6GMC5G/

Fedora Elections May 2018 - Voting period of FESCo elections is open

[Jan Kurik]

The voting period is still open till Wednesday, June 13th, 2018.
Do not forget to vote [1] for your favourite nominees [2] to FESCo.

[1] https://admin.fedoraproject.org/voting/about/fesco-may-2018
[2] https://communityblog.fedoraproject.org/2018-may-elections-fesco-interviews/

Jan

On Thu, Jun 7, 2018 at 4:17 AM, Jan Kurik  wrote:
>
> Hi,
>
> the Voting period of the currently running Fedora Elections [0] has
> just started. Please vote for your candidates to FESCo [1].
> You can vote till June 13th, 2018 when the voting ends at 23:59:59 UTC.
>
> On Community blog [2] you can also find interviews with all the
> candidates. Please have a look at it.
>
> [0] https://fedoraproject.org/wiki/Elections
> [1] https://admin.fedoraproject.org/voting/vote/fesco-may-2018
> [2] https://communityblog.fedoraproject.org/tag/may-2018-elections-fesco/
> [2.1] Justin Forbes:
> https://communityblog.fedoraproject.org/fesco-election-interview-justin-forbes-jforbes/
> [2.2] Stephen Gallagher:
> https://communityblog.fedoraproject.org/fesco-election-interview-stephen-gallagher-sgallagh/
> [2.3] Till Maas:
> https://communityblog.fedoraproject.org/fesco-election-interview-till-maas-till/
> [2.4] Randy Barlow:
> https://communityblog.fedoraproject.org/fesco-election-interview-randy-barlow-bowlofeggs/
> [2.5] Petr Šabata:
> https://communityblog.fedoraproject.org/fesco-election-interview-petr-sabata-psabata-contyk/
>
> Thanks for your support.
> Regards,
> Jan
> --
> Jan Kuřík
> JBoss EAP Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic




-- 
Jan Kuřík
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GWPHLXBE63LQAVF5GP73BALLCQO7A3PT/

[389-devel] 389 DS nightly 2018-06-11 - 62% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2018/06/11/report-389-ds-base-1.4.0.10-20180611git24c5c00.fc28.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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-de...@lists.fedoraproject.org/message/EXAGIVG3C2LXFUFOWL27RPIIRRG7S6NA/

Re: broken package needs attention: libgda

[Haïkel]

2018-06-10 22:46 GMT+02:00 Sérgio Basto :
> On Sun, 2018-06-10 at 18:27 +0200, Fabio Valentini wrote:
>> Hi,
>>
>> The "libgda" package is quite broken in fedora, which is impacting
>> dependent programs.
>>
>> - The last successful build of libgda was for the fedora 24 (!) mass
>> rebuild. No more recent builds succeeded, and the packages was
>> reported as FTBFS.
>> - Not even the latest version is packaged (5.2.2 instead of 5.2.4).
>>
>> This is leading to problems in all current releases of fedora. For
>> example, the mysql database provider can't be installed anymore,
>> because libgda wasn't rebuilt for soname bumps in mariadb/mysql.
>>
>> Packages depending on libgda include:
>>
>> - anjuta
>> - glom
>> - gnumeric-plugins-extras
>> - gtranslator
>> - noise
>> - sequeler
>>
>> Is there any procedure for dealing with a package that's obviously
>> outdated and broken (and has been for 3 fedora releases), but is
>> still depended on by other packages?
>>
>> There has been an open bug report [0] about the FTBFS issues, but no
>> actions have been taken so far by the package maintainer(s).
>>
>> Fabio
>>
>> [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1423852
>
>
> I see 3 patches there and we got another bug report  [1]
>
> The best would be add one pull request in src.f.o [2] , i.e do a fork
> apply the patch and submit one pull request .
>
>
> [1]
> https://bugzilla.redhat.com/show_bug.cgi?id=1556039
>
>
> [2]
>  https://src.fedoraproject.org/rpms/libgda/pull-requests
>
> --
> Sérgio M. B.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KGBVPAILSYUXYYWPOGECPPSCDYMICFIX/


Sending an email to libgda-owner would have raised the attention on
your patches.
I got a notification late night about and I planned to go through it
later today (currently, I am teaching a class and I still have my
$dayjob duty)

libgda is co-maintained with the desktop team but it seems that the
project is not anymore
maintained in GNOME upstream hence its sore state.

So first task is to apply those patches and possibly, send them
upstream. Second task is to determine if we should drop the packages
(and it includes all the bindings to libgda),
but I need more time for that.

Alternative is you want comaintainership, just ask, you're welcome :)

Regards,
H.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BV6IP6FF6VRJDJM4PILHC3LCK74WRYSF/

Re: HEADS UP - libbson and libmongoc soname bump in rawhide - reverted

[Remi Collet]

Le 28/05/2018 à 13:32, Remi Collet a écrit :
> Soname are bumped
> 
> - libbson-1.0.so.0 => libbson-1.0.so.1
> - libmongoc-1.0.so.0 => libmongoc-1.0.so.1

With update to 1.10.2, the soname change was reverted

Everything have been rebuild in rawhide

Perhaps this new version will go in F28 later, if needed.


Remi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7YFDGIGCRFAMT2O7IFIE6YI4FQ4UF5WL/

[Bug 1589473] perl-MooX-Struct-0.017 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
perl-MooX-Struct-0.017-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-e1ee48d624

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/DLK3ZS3ZT53BO56WHAMHYVVFA56PQAVL/

[Bug 1589473] perl-MooX-Struct-0.017 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
perl-MooX-Struct-0.017-1.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-05e1a54459

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/CDWWX7RBPA7Y3RZABLYXEUEAZPGUJYKZ/

[Bug 1589401] perl-DateTime-Locale-1.22 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-DateTime-Locale-1.22-1
   ||.fc29
 Resolution|--- |RAWHIDE
Last Closed||2018-06-11 03:22:35



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/QJHDXEZJMFKORE5HENAZMFBHZSRSIHCG/

[Bug 1589473] perl-MooX-Struct-0.017 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-MooX-Struct-0.017-1.fc
   ||29



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/SDDAFKNJVP3NT45ZDJ6IY5L2T7SR6YTE/