Schedule for Thursday's FPC Meeting (2018-09-13 16:00 UTC)

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


  Local time information (via. uitime):

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


  Links to all tickets below can be found at:

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


= Followups =

#topic #665 SSLCertificateHandling policy update
.fpc 665
https://pagure.io/packaging-committee/issue/665

#topic #667 Recommend use of systemd sandboxing directives
.fpc 667
https://pagure.io/packaging-committee/issue/667

#topic #693 Wiki:Packaging:RPMMacros
.fpc 693
https://pagure.io/packaging-committee/issue/693

#topic #703 Inconsistency between "General Naming" and "Case Sensitivity"
.fpc 703
https://pagure.io/packaging-committee/issue/703

#topic #714 let's kill file deps!
.fpc 714
https://pagure.io/packaging-committee/issue/714

#topic #719 Simplify packaging of forge-hosted projects
.fpc 719
https://pagure.io/packaging-committee/issue/719

#topic #726 Review for SELinux Independent Policy packaging Draft
.fpc 726
https://pagure.io/packaging-committee/issue/726

#topic #727 convert guidelines to git and restructured text  
.fpc 727
https://pagure.io/packaging-committee/issue/727

#topic #743 Add link to C/C++ build flag docs. in redhat-rpm-config
.fpc 743
https://pagure.io/packaging-committee/issue/743

#topic #775 Allow to have %{?suse_version} condition in spec file
.fpc 775
https://pagure.io/packaging-committee/issue/775

#topic #784 forbid globs for shared libraries as it conceals sonames
.fpc 784
https://pagure.io/packaging-committee/issue/784


= New business =

#topic  #793 Python Guidelines: Move Python 2 to Appendix  
.fpc 793
https://pagure.io/packaging-committee/issue/793

= Open Floor =

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

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

  If you would like to add something to this agenda, you can:
   * Reply to this e-mail
   * File a new ticket at: https://pagure.io/packaging-committee
   * E-mail me directly
   * Bring it up at the end of the meeting, during the open floor topic.
 Note that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: No more automagic Python bytecompilation: I'll mass push to your packages

2018-09-12 Thread Scott Talbert 

On Wed, 12 Sep 2018, Miro Hrončok wrote:


Hello.

In line with
https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompil
ation_phase_2

I plan to mass push the following 3 lines on the top of your package spec:


I updated my packages to set _python_bytecompile_extra to 0, but for some
reason, python-pyqtgraph is still byte-compiling files under
/usr/share/doc/python-pyqtgraph-doc/ with Python 3.  Is this expected?

Scott___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2018-09-13 - 91% PASS

2018-09-12 Thread vashirov 
https://fedorapeople.org/groups/389ds/ci/nightly/2018/09/13/report-389-ds-base-1.4.0.16-20180912gite59b309.fc28.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

[Bug 1628414] New: perl-Archive-Zip-1.64 is available

2018-09-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1628414

Bug ID: 1628414
   Summary: perl-Archive-Zip-1.64 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Archive-Zip
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: al...@redhat.com, caillon+fedoraproj...@gmail.com,
john.j5l...@gmail.com, jples...@redhat.com,
ka...@ucw.cz, mbar...@fastmail.com,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com, st...@silug.org



Latest upstream release: 1.64
Current version/release in rawhide: 1.63-1.fc30
URL: http://search.cpan.org/dist/Archive-Zip/

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

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

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

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

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

[Bug 1628413] New: ctstream-29 is available

2018-09-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1628413

Bug ID: 1628413
   Summary: ctstream-29 is available
   Product: Fedora
   Version: rawhide
 Component: ctstream
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com



Latest upstream release: 29
Current version/release in rawhide: 28-1.fc29
URL: http://xpisar.wz.cz/ctstream/

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

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

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

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

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

Re: Orphaning qt5-qtwebengine

2018-09-12 Thread Kevin Kofler 
qt5-qtwebengine is now officially orphaned at src.fedoraproject.org and up 
for taking.

Kevin Kofler
___
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

Fedora Rawhide-20180912.n.0 compose check report

2018-09-12 Thread Fedora compose checker 
No missing expected images.

Failed openQA tests: 18/132 (x86_64), 3/24 (i386), 1/2 (arm)

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

ID: 278784  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/278784
ID: 278785  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/278785
ID: 278786  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/278786
ID: 278800  Test: i386 Workstation-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/278800
ID: 278814  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/278814
ID: 278835  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/278835
ID: 278836  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/278836
ID: 278837  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/278837
ID: 278838  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/278838
ID: 278878  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/278878
ID: 278879  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/278879
ID: 278889  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/278889
ID: 278899  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/278899
ID: 278900  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/278900

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

ID: 278811  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/278811
ID: 278817  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/278817
ID: 278843  Test: x86_64 universal install_blivet_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/278843
ID: 278844  Test: x86_64 universal install_blivet_no_swap@uefi
URL: https://openqa.fedoraproject.org/tests/278844
ID: 278845  Test: x86_64 universal install_blivet_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/278845
ID: 278864  Test: x86_64 universal install_blivet_ext3@uefi
URL: https://openqa.fedoraproject.org/tests/278864
ID: 278865  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/278865
ID: 278866  Test: x86_64 universal install_blivet_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/278866

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

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

ID: 278779  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/278779
ID: 278780  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/278780
ID: 278856  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/278856
ID: 278858  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/278858

Passed openQA tests: 103/132 (x86_64), 19/24 (i386)

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

ID: 278770  Test: x86_64 Server-dvd-iso base_system_logging
URL: https://openqa.fedoraproject.org/tests/278770
ID: 278816  Test: i386 KDE-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/278816
ID: 278832  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/278832
ID: 278857  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/278857
ID: 278859  Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/278859

Skipped openQA tests: 10 of 158

Installed system changes in test x86_64 Server-boot-iso install_default: 
Used mem changed from 198 MiB to 170 MiB
Previous test data: https://openqa.fedoraproject.org/tests/278214#downloads
Current test data: https://openqa.fedoraproject.org/tests/278753#downloads

Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 
System load changed from 1.47 to 1.08
Used mem changed from 199 MiB to 171 MiB
Previous test data: https://openqa.fedoraproject.org/tests/278215#downloads
Current test data: https://openqa.fedoraproject.org/tests/278754#downloads

Installed system changes in test x86_64 Server-dvd-iso install_default_upload: 
2 packages(s) removed since previous compose: python3-librepo, 
python3-smartcols
Previous test data:

Fedora 29 Beta 1.1 compose check report

2018-09-12 Thread Fedora compose checker 
No missing expected images.

Failed openQA tests: 8/132 (x86_64), 1/24 (i386), 1/2 (arm)

ID: 278953  Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/278953
ID: 278969  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/278969
ID: 278975  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/278975
ID: 279001  Test: x86_64 universal install_blivet_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/279001
ID: 279002  Test: x86_64 universal install_blivet_no_swap@uefi
URL: https://openqa.fedoraproject.org/tests/279002
ID: 279003  Test: x86_64 universal install_blivet_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/279003
ID: 279022  Test: x86_64 universal install_blivet_ext3@uefi
URL: https://openqa.fedoraproject.org/tests/279022
ID: 279023  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/279023
ID: 279024  Test: x86_64 universal install_blivet_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/279024
ID: 279057  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/279057

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

ID: 278911  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/278911
ID: 278912  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/278912
ID: 278937  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/278937
ID: 278938  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/278938
ID: 278939  Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/278939
ID: 278940  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/278940
ID: 278941  Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/278941
ID: 279013  Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/279013
ID: 279016  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/279016
ID: 279017  Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/279017
ID: 279025  Test: x86_64 universal install_kickstart_user_creation
URL: https://openqa.fedoraproject.org/tests/279025
ID: 279042  Test: x86_64 universal install_kickstart_hdd
URL: https://openqa.fedoraproject.org/tests/279042
ID: 279050  Test: x86_64 universal install_kickstart_nfs
URL: https://openqa.fedoraproject.org/tests/279050

Passed openQA tests: 114/132 (x86_64), 20/24 (i386)

Skipped openQA tests: 1 of 158
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: Managing stream (arbitrary) branch and module lifecycles

2018-09-12 Thread Matthew Miller 
On Mon, Sep 03, 2018 at 03:35:50PM +0200, Adam Samalik wrote:
> There would be a policy that a module can reach its EOL in the middle of a
> Fedora release to prevent madness.

Can or can't? I assume you mean "can't", because "can" doesn't sound like
preventing madness. :)



-- 
Matthew Miller

Fedora Project Leader
___
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

Re: Testing / feedback request: DNF 3 crashes

2018-09-12 Thread Adam Williamson 
On Wed, 2018-09-12 at 16:33 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Sep 12, 2018 at 09:16:54AM -0700, Adam Williamson wrote:
> > On Wed, 2018-09-12 at 06:27 +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Sep 11, 2018 at 12:26:09PM -0700, Adam Williamson wrote:
> > > > Hi folks!
> > > > 
> > > > Around the time DNF 3 landed in Rawhide (hence F29), we had quite a few
> > > > folks on these lists reporting issues, including crasher bugs. Many of
> > > > these seemed somehow related to the DNF history database. They also
> > > > were not easy to isolate and fix.
> > > > 
> > > > We're now close to the F29 Beta release, but we don't have a great
> > > > sense of how many people are still having these problems with DNF 3.2
> > > > or 3.3.
> > > > 
> > > > Can anyone who is still struggling with DNF crashes on *basic*
> > > > operations on F29 or Rawhide please reply, and provide a few details on
> > > > what you're seeing and any workarounds or fixes you've found?
> > > 
> > > I filed https://bugzilla.redhat.com/show_bug.cgi?id=1627694 yesterday.
> > > The gist is that dnf stopped having locking around the rpm operation,
> > > so it'll fail if two operations are invoked concurrently. Before it'd
> > > very nicely do the downloads in parallel and then run the actual 
> > > installations
> > > sequentially. I think this is a huge regression in usability.
> > 
> > Thanks. Doesn't really look like a Beta blocker, though.
> 
> It doesn't. I don't even think it'd be a Final blocker. Just unpleasant.
> 
> > > I also saw some "TransactionItem not found" messages, but this has already
> > > been reported extensively.
> > 
> > On what operation? We have:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1625259
> > for encountering them on downgrade or 'history undo' type operations.
> > If you hit one on upgrade or install, that'd be worse.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1627534
> 
> I marked it as duplicate, to avoid noise. Mikhail reported it during 'history 
> undo',
> but I saw during 'dnf upgrade'.

That seems significantly worse to me. I'm going to propose the bug as a
blocker and request input from dnf team. Thanks.
-- 
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
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

Reminder: Fedora 29 Beta Go/No-Go meeting

2018-09-12 Thread Ben Cotton 
Dear all,

The Go/No-Go meeting for the Fedora 29 Beta release will be held
tomorrow — Thursday, 2018-09-13 — at 17:00 UTC in #fedora-meeting-1.
For more information, see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

View the meeting on Fedocal at
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/9/10/#m9338

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org

Fedora rawhide compose report: 20180912.n.0 changes

2018-09-12 Thread Fedora Rawhide Report 
OLD: Fedora-Rawhide-20180911.n.0
NEW: Fedora-Rawhide-20180912.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  11
Dropped packages:1
Upgraded packages:   79
Downgraded packages: 0

Size of added packages:  9.56 MiB
Size of dropped packages:134.08 KiB
Size of upgraded packages:   2.81 GiB
Size of downgraded packages: 0 B

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

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

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: mate-user-admin-1.1.1-1.fc30
Summary: User management tool
RPMs:mate-user-admin
Size:4.98 MiB

Package: nghttp2-1.33.0-1.module_2177+076c917f
Summary: Experimental HTTP/2 client, server and proxy
RPMs:libnghttp2 libnghttp2-devel nghttp2
Size:3.78 MiB

Package: rust-abomonation-0.5.0-1.fc30
Summary: High performance and very unsafe serialization library
RPMs:rust-abomonation-devel
Size:20.70 KiB

Package: rust-alga-0.7.1-1.fc30
Summary: Abstract algebra for Rust
RPMs:rust-alga-devel
Size:38.05 KiB

Package: rust-cast-0.2.2-1.fc30
Summary: Ergonomic, checked cast functions for primitive types
RPMs:rust-cast-devel
Size:18.18 KiB

Package: rust-decimal-2.0.4-1.fc30
Summary: Decimal floating point arithmetic for Rust
RPMs:rust-decimal-devel
Size:650.88 KiB

Package: rust-fragile-0.3.0-1.fc30
Summary: Wrapper types for sending non-send values to other threads
RPMs:rust-fragile-devel
Size:18.75 KiB

Package: rust-itertools-num-0.1.2-1.fc30
Summary: Numerical iterator tools
RPMs:rust-itertools-num-devel
Size:11.91 KiB

Package: rust-matrixmultiply-0.1.14-1.fc30
Summary: General matrix multiplication of f32 and f64 matrices in Rust
RPMs:rust-matrixmultiply-devel
Size:24.88 KiB

Package: rust-semver-parser0.7-0.7.0-6.fc30
Summary: Parsing of the semver spec
RPMs:rust-semver-parser0.7-devel
Size:18.41 KiB

Package: rust-simplelog-0.5.2-1.fc30
Summary: Simple and easy-to-use logging facility for Rust's log crate
RPMs:rust-simplelog-devel
Size:22.52 KiB


= DROPPED PACKAGES =
Package: python-pypubsub3.3.0-3.3.0-2.fc29
Summary: Python Publish-Subscribe Package
RPMs:python2-pypubsub
Size:134.08 KiB


= UPGRADED PACKAGES =
Package:  anaconda-30.3-1.fc30
Old package:  anaconda-30.2-1.fc30
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-tui anaconda-widgets anaconda-widgets-devel
Size: 18.00 MiB
Size change:  -103.15 KiB
Changelog:
  * Tue Sep 11 2018 Martin Kolman  - 30.3-1
  - Save lsblk output to the Anaconda traceback file (vtrefny)
  - Remove librepo imports from Anaconda (#1626609) (jkonecny)
  - DNF 3.5 compatibility (mkolman)
  - Use the default LUKS version for auto partitioning (#1624680) (vponcova)
  - Remove the testing flag (vponcova)


Package:  aom-1.0.0-3.fc30
Old package:  aom-1.0.0-2.fc29
Summary:  Royalty-free next-generation video format
RPMs: aom aom-devel
Size: 9.09 MiB
Size change:  -489.21 KiB
Changelog:
  * Tue Sep 11 2018 Robert-Andr?? Mauchin  - 1.0.0-3
  - Update the archive in order to detect the correct version from the changelog


Package:  ara-0.16.1-2.fc30
Old package:  ara-0.14.6-1.fc29
Summary:  ARA Records Ansible playbook runs
RPMs: ara ara-common ara-doc python3-ara python3-ara-tests
Dropped RPMs: ara-python3 python2-ara python2-ara-tests
Size: 6.85 MiB
Size change:  3.38 MiB
Changelog:
  * Tue Jun 19 2018 Miro Hron??ok  - 0.14.6-2
  - Rebuilt for Python 3.7

  * Thu Jul 12 2018 Fedora Release Engineering  - 
0.14.6-3
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild

  * Mon Sep 10 2018 David Moreau Simard  - 0.16.1
  - Update to latest upstream release
  - Default to python3


Package:  bash-4.4.23-4.fc30
Old package:  bash-4.4.23-3.fc29
Summary:  The GNU Bourne Again shell
RPMs: bash bash-devel bash-doc
Size: 16.63 MiB
Size change:  -113.42 KiB
Changelog:
  * Mon Sep 10 2018 Siteshwar Vashisht  - 4.4.23-4
  - Set custom PATH in non-login shells
Resolves: #1615131


Package:  compiler-rt-7.0.0-0.4.rc3.fc30
Old package:  compiler-rt-7.0.0-0.3.rc1.fc30
Summary:  LLVM "compiler-rt" runtime libraries
RPMs: compiler-rt
Size: 13.32 MiB
Size change:  -3.11 KiB
Changelog:
  * Wed Sep 12 2018 Tom Stellard  - 7.0.0-0.4.rc3
  - 7.0.0-rc3 Release


Package:  cppcheck-1.84-1.fc30
Old package:  cppcheck-1.83-4.fc29
Summary:  Tool for static C/C++ code analysis
RPMs: cppcheck cppcheck-gui cppcheck-htmlreport
Size: 14.85 MiB
Size change:  132.85 KiB
Changelog:
  * Tue Sep 11 2018 Susi Lehtola  - 1.84-1
  - Update to 1.84.


Package:  ddgr-1.5-1.fc30
Old package:  ddgr-1.4-3.fc

Reminder: Fedora 29 Beta Release Readiness meeting

2018-09-12 Thread Ben Cotton 
Dear all,

Join us tomorrow on irc.freenode.net in #fedora-meeting-1 for the
Fedora 29 Beta Release Readiness meeting.

We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.

You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.

For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.

I will ask for readiness from each of the teams listed below. If there
are additional teams that should be explicitly included, let me know.
All teams and contributors are welcome to provide input at the
meeting.

* Ambassadors
* Cloud WG
* Design
* Desktop
* Documentation
* Fedora Project Leader
* FESCo
* Infrastructure
* Marketing
* QA
* Release Engineering
* Server WG
* Spins
* Translations
* Websites

View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/9/10/#m9337

--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
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

Reminder: Fedora 29 Beta Go/No-Go meeting

2018-09-12 Thread Ben Cotton 
Dear all,

The Go/No-Go meeting for the Fedora 29 Beta release will be held
tomorrow — Thursday, 2018-09-13 — at 17:00 UTC in #fedora-meeting-1.
For more information, see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

View the meeting on Fedocal at
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/9/10/#m9338

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
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

Re: Testing / feedback request: DNF 3 crashes

2018-09-12 Thread Zbigniew Jędrzejewski-Szmek 
On Wed, Sep 12, 2018 at 09:16:54AM -0700, Adam Williamson wrote:
> On Wed, 2018-09-12 at 06:27 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Sep 11, 2018 at 12:26:09PM -0700, Adam Williamson wrote:
> > > Hi folks!
> > > 
> > > Around the time DNF 3 landed in Rawhide (hence F29), we had quite a few
> > > folks on these lists reporting issues, including crasher bugs. Many of
> > > these seemed somehow related to the DNF history database. They also
> > > were not easy to isolate and fix.
> > > 
> > > We're now close to the F29 Beta release, but we don't have a great
> > > sense of how many people are still having these problems with DNF 3.2
> > > or 3.3.
> > > 
> > > Can anyone who is still struggling with DNF crashes on *basic*
> > > operations on F29 or Rawhide please reply, and provide a few details on
> > > what you're seeing and any workarounds or fixes you've found?
> > 
> > I filed https://bugzilla.redhat.com/show_bug.cgi?id=1627694 yesterday.
> > The gist is that dnf stopped having locking around the rpm operation,
> > so it'll fail if two operations are invoked concurrently. Before it'd
> > very nicely do the downloads in parallel and then run the actual 
> > installations
> > sequentially. I think this is a huge regression in usability.
> 
> Thanks. Doesn't really look like a Beta blocker, though.

It doesn't. I don't even think it'd be a Final blocker. Just unpleasant.

> > I also saw some "TransactionItem not found" messages, but this has already
> > been reported extensively.
> 
> On what operation? We have:
> https://bugzilla.redhat.com/show_bug.cgi?id=1625259
> for encountering them on downgrade or 'history undo' type operations.
> If you hit one on upgrade or install, that'd be worse.

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

I marked it as duplicate, to avoid noise. Mikhail reported it during 'history 
undo',
but I saw during 'dnf upgrade'.

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

Re: Testing / feedback request: DNF 3 crashes

2018-09-12 Thread Adam Williamson 
On Wed, 2018-09-12 at 06:27 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Sep 11, 2018 at 12:26:09PM -0700, Adam Williamson wrote:
> > Hi folks!
> > 
> > Around the time DNF 3 landed in Rawhide (hence F29), we had quite a few
> > folks on these lists reporting issues, including crasher bugs. Many of
> > these seemed somehow related to the DNF history database. They also
> > were not easy to isolate and fix.
> > 
> > We're now close to the F29 Beta release, but we don't have a great
> > sense of how many people are still having these problems with DNF 3.2
> > or 3.3.
> > 
> > Can anyone who is still struggling with DNF crashes on *basic*
> > operations on F29 or Rawhide please reply, and provide a few details on
> > what you're seeing and any workarounds or fixes you've found?
> 
> I filed https://bugzilla.redhat.com/show_bug.cgi?id=1627694 yesterday.
> The gist is that dnf stopped having locking around the rpm operation,
> so it'll fail if two operations are invoked concurrently. Before it'd
> very nicely do the downloads in parallel and then run the actual installations
> sequentially. I think this is a huge regression in usability.

Thanks. Doesn't really look like a Beta blocker, though.

> I also saw some "TransactionItem not found" messages, but this has already
> been reported extensively.

On what operation? We have:
https://bugzilla.redhat.com/show_bug.cgi?id=1625259
for encountering them on downgrade or 'history undo' type operations.
If you hit one on upgrade or install, that'd be worse.

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

[Test-Announce] Fedora 29 Candidate Beta-1.1 Available Now!

2018-09-12 Thread rawhide 
According to the schedule [1], Fedora 29 Candidate Beta-1.1 is now
available for testing. Please help us complete all the validation
testing! For more information on release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Test coverage information for the current release can be seen at:
https://www.happyassassin.net/testcase_stats/29

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Beta_1.1_Security_Lab

All Beta priority test cases for each of these test pages [2] must
pass in order to meet the Beta Release Criteria [3].

Help is available on #fedora-qa on irc.freenode.net [4], or on the
test list [5].

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1] http://fedorapeople.org/groups/schedule/f-29/f-29-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_29_Beta_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: Question regarding "Remove (sub)packages from Fedora 30+"

2018-09-12 Thread Miro Hrončok 

On 12.9.2018 16:43, Robert-André Mauchin wrote:

Hello,

What's the procedure for removing a Python 2 subpackage as requested? Should I
add it to fedora-obsolete-packages?


If it has problematic deps, you should. See 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/TX5OLJIXJ5KHFRQXCF6M7J2XWRMYFXUY/


I was planning to do it in bulk, however any help here is appreciated.


Should I add "Provides: deprecated()" to the subpackage?


No, remove it straight away please.

You MAY add deprecated() to not yet removed subpackages that are still 
depended upon (!= the ones I requested for removal).


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org

Question regarding "Remove (sub)packages from Fedora 30+"

2018-09-12 Thread Robert-André Mauchin 
Hello,

What's the procedure for removing a Python 2 subpackage as requested? Should I 
add it to fedora-obsolete-packages? Should I add "Provides: deprecated()" to 
the subpackage?

Thanks.

___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org

Re: fedpkg clone doesn*t work

2018-09-12 Thread Martin Gansser 
i have shared theinformartion on [1]

when i am trying to save the public rsa key on the fedora account, i get this 
error message:

500 Internal error
The server encountered an unexpected condition which prevented it from 
fulfilling the request.
Powered by CherryPy 2.3.0 

[1] https://files.fm/u/yjyfxz4m
___
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

Re: Random *** stack smashing detected *** message

2018-09-12 Thread Florian Weimer 

On 09/05/2018 05:30 PM, Richard W.M. Jones wrote:

It gives an odd error (see attached).  Is that a bug in eu-stack?


It seems that all debuginfo was successfully loaded.  I don't see a way 
to debug this further.  If it does not reproduce, I'm inclined to blame 
it on faulty memory. 8-p


Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: mlichvar pushed to lrzsz (master). "add man page symlinks for sb, sx, rb, rx programs (#1611501)"

2018-09-12 Thread Miroslav Lichvar 
On Wed, Sep 12, 2018 at 01:47:00PM +0200, Tomasz Kłoczko wrote:
> > From 20e576638ca6bbc6583bb357353a6c66760fe457 Mon Sep 17 00:00:00 2001
> > From: Miroslav Lichvar 
> > Date: Sep 12 2018 11:00:41 +
> > Subject: add man page symlinks for sb, sx, rb, rx programs (#1611501)
> > +for m in rb rx; do ln -s rz.1 %{buildroot}%{_mandir}/man1/$m.1; done
> > +for m in sb sx; do ln -s sz.1 %{buildroot}%{_mandir}/man1/$m.1; done
> > +
> >  %find_lang %{name}
> >
> 
> Just FTR: This kind of modifications are wrong.
> After compressing {rs}z.1 in %post it will be {rs}z.1.gz and created
> symlinks will be pointing nowhere.

That may have been true in the past, but the current compression script seems
to fix the symlinks as expected.

$ rpm -qlvp lrzsz-0.12.20-46.fc30.x86_64.rpm | grep man1
lrwxrwxrwx1 rootroot7 Sep 12 13:05 
/usr/share/man/man1/rb.1.gz -> rz.1.gz
lrwxrwxrwx1 rootroot7 Sep 12 13:05 
/usr/share/man/man1/rx.1.gz -> rz.1.gz
-rw-r--r--1 rootroot 5810 Sep 12 13:05 
/usr/share/man/man1/rz.1.gz
lrwxrwxrwx1 rootroot7 Sep 12 13:05 
/usr/share/man/man1/sb.1.gz -> sz.1.gz
lrwxrwxrwx1 rootroot7 Sep 12 13:05 
/usr/share/man/man1/sx.1.gz -> sz.1.gz
-rw-r--r--1 rootroot 7383 Sep 12 13:05 
/usr/share/man/man1/sz.1.gz

-- 
Miroslav Lichvar
___
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

Re: mlichvar pushed to lrzsz (master). "add man page symlinks for sb, sx, rb, rx programs (#1611501)"

2018-09-12 Thread Tomasz Kłoczko 
On Wed, 12 Sep 2018 at 13:06,  wrote:

> Notification time stamped 2018-09-12 11:01:03 UTC
>
> From 20e576638ca6bbc6583bb357353a6c66760fe457 Mon Sep 17 00:00:00 2001
> From: Miroslav Lichvar 
> Date: Sep 12 2018 11:00:41 +
> Subject: add man page symlinks for sb, sx, rb, rx programs (#1611501)
>
>
> ---
>
> diff --git a/lrzsz.spec b/lrzsz.spec
> index a751bba..c47cbb1 100644
> --- a/lrzsz.spec
> +++ b/lrzsz.spec
> @@ -37,6 +37,9 @@ make %{?_smp_mflags}
>
>  %install
>  %makeinstall
> +for m in rb rx; do ln -s rz.1 %{buildroot}%{_mandir}/man1/$m.1; done
> +for m in sb sx; do ln -s sz.1 %{buildroot}%{_mandir}/man1/$m.1; done
> +
>  %find_lang %{name}
>

Just FTR: This kind of modifications are wrong.
After compressing {rs}z.1 in %post it will be {rs}z.1.gz and created
symlinks will be pointing nowhere.
As well in such situation it should be not used symlinks to *gz files as
when compression of the man pages method may change in such situations
symlinks will be pointing to nowhere.
Only correct method for above is use roff link files like:

+for m in rb rx; do echo ".so man1/rz.1" > %{buildroot}%{_mandir}/man1/$m.1;
done
+for m in sb sx; do echo ".so man1/sz.1" > %{buildroot}%{_mandir}/man1/$m.1;
done

kloczek
-- 
Tomasz Kłoczko | 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

Re: [modularity] Removing obsolete github repositories with module definitions

2018-09-12 Thread Adam Samalik 
Thanks, I'll go ahead.

On Wed, Sep 12, 2018 at 9:54 AM Petr Šabata  wrote:

> On Tue, Sep 11, 2018 at 04:24:05PM -0400, Langdon White wrote:
> > On Tue, Sep 11, 2018 at 3:09 PM Stephen Gallagher 
> > wrote:
> >
> > > Go ahead
> > >
> > >
> > +1
>
> +1 as well.
>
> P
>
> >
> > On Tue, Sep 11, 2018 at 3:04 PM Adam Samalik 
> wrote:
> > >
> > >> We have some obsolete github repositories [1] from the f26 and f27
> period
> > >> we are no longer using. I feel like it might be confusing to people.
> So I'd
> > >> like to remove them all. Any objections?
> > >>
> > >> [1] https://github.com/modularity-modules/
> > >> --
> > >>
> > >> Adam Šamalík
> > >> ---
> > >> Software Engineer
> > >> Red Hat
> > >> ___
> > >> devel mailing list -- devel@lists.fedoraproject.org
> > >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > >> Fedora Code of Conduct: https://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
> > >>
> > > ___
> > > 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
> > >
>
> > ___
> > 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
>
> ___
> 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
>


-- 

Adam Šamalík
---
Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: Heads Up: python2 is marked as deprecated

2018-09-12 Thread Tomasz Kłoczko 
On Tue, 11 Sep 2018 at 23:38, Petr Viktorin  wrote:

> On 09/11/18 11:52, Tomasz Kłoczko wrote:
> > On Tue, 11 Sep 2018 at 16:48, Petr Viktorin  > > wrote:
> > [..]
> >
> > These numbers hide an important fact: many things currently come with
> > RPMs for both python2 and python3.
> >
> > More detailed statistics (based on SRPMs, not binary RPMs):
> > http://fedora.portingdb.xyz/
> > Graph with historical data: http://fedora.portingdb.xyz/history/
> >
> >  > In other words trying currently announcing python2 as depricated
> > is at
> >  > least a bit .. odd.
> >
> > Do you know a better way to make the python2 numbers go down?
> >
> > Would *you* be interested in maintaining python2 past 2020, with no
> > upstream support and 3415 dependent packages?
> >
> >
> > No and no .. of course :)
> > I've been only trying to say that with current numbers about balance
> > between python 2 and 3 packages are making announcement about
> > deprecation a bit to early. Only this and nothing more :P
>
> When will it not be too early?
>

IMO at least after porting to python 3 few crucial applications.
One of the most important is gimp.
Even more important would be getting rid of python 2 out of the @base
and @core kickstart profiles.

Gimp has another tail in form of gtk+2 dependency but IMO cutting python 2
dependency is way simpler task.
BTW: cutting off gtk+2 dependency is probably as same as python 2 important.

> I fully understand effort to migrate ASAP to python 3.
> > IMO it should be announced only kind of call to migrate as much as
> > possible with completing set of advises abut typical porting issues.
>
> Python 3 is now almost 10 years old. The "Python 3 as Default" change
> was for Fedora 21. Python's documentation has a section on porting.
> There are printed books about porting. There's a comprehensive guide at
> portingguide.readthedocs.io. Fedora's Python packaging guidelines say
> "If it supports only python2 then [...] upstream SHOULD be contacted and
> encouraged to rectify this issue." -- have you done that?
>
> We're honestly tired of making calls to migrate. What would another one
> of those accomplish?
>
> > Forming ad hoc team people which could help porting code to python 3 may
> > IMO be useful.
>
> Try the Python SIG!
>

Possibly .. however IMO python 2=>3 issues simple only massive and less
complicated than ggenerally all python issues.

> I have in my set of packages one of those which will require migration
> > to python 3 as well.
>
> Why have you waited so long?
>

To have a bit more time to do this. Recently I've been a bit more busy and
month ago started new contract in Brussels.
Will try to do this probably in the end of this month (with add use more
%lang() in mc.spec which I have in my own version of this file)

kloczek
-- 
Tomasz Kłoczko | 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

Re: fedpkg clone doesn*t work

2018-09-12 Thread Jakub Jelen 
On Wed, 2018-09-12 at 09:12 +0200, Pavel Zhukov wrote:
> Bug report:
> https://bugzilla.redhat.com/show_bug.cgi?id=1627875

All the above things, clonning and ssh to fedorapeople.org works for me
just fine with my RSA key added to the fedora account. Can you share
your configuration (ssh -G fedorapeople.org) and more verbose logs (ssh
-vvv your-usern...@fedorapeople.org)?

Jakub

> "Martin Gansser"  writes:
> 
> > I tried
> > 
> > fedpkg clone lollypop
> > 
> > Cloning into 'lollypop'...
> > marti...@pkgs.fedoraproject.org: Permission denied (publickey).
> > fatal: Could not read from remote repository.
> > 
> > Please make sure you have the correct access rights
> > and the repository exists.
> > Could not execute clone: Failed to execute command.
> > 
> > 
> > [martin@f28 fedora-scm]$ fedpkg clone lollypop
> > Cloning into 'lollypop'...
> > Enter passphrase for key '/home/martin/.ssh/id_rsa': 
> > packet_write_wait: Connection to 209.132.181.4 port 22: Broken pipe
> > fatal: Could not read from remote repository.
> > 
> > Please make sure you have the correct access rights
> > and the repository exists.
> > Could not execute clone: Failed to execute command.
> > 
> > [martin@f28 fedora-scm]$ ssh -vT 209.132.181.4
> > OpenSSH_7.8p1, OpenSSL 1.1.0h-fips  27 Mar 2018
> > debug1: Reading configuration data /home/martin/.ssh/config
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debug1: Reading configuration data /etc/ssh/ssh_config.d/05-
> > redhat.conf
> > debug1: Reading configuration data /etc/crypto-policies/back-
> > ends/openssh.config
> > debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying
> > options for *
> > debug1: Connecting to 209.132.181.4 [209.132.181.4] port 22.
> > debug1: Connection established.
> > debug1: identity file /home/martin/.ssh/id_rsa type 0
> > debug1: identity file /home/martin/.ssh/id_rsa-cert type -1
> > debug1: identity file /home/martin/.ssh/id_dsa type -1
> > debug1: identity file /home/martin/.ssh/id_dsa-cert type -1
> > debug1: identity file /home/martin/.ssh/id_ecdsa type -1
> > debug1: identity file /home/martin/.ssh/id_ecdsa-cert type -1
> > debug1: identity file /home/martin/.ssh/id_ed25519 type -1
> > debug1: identity file /home/martin/.ssh/id_ed25519-cert type -1
> > debug1: identity file /home/martin/.ssh/id_xmss type -1
> > debug1: identity file /home/martin/.ssh/id_xmss-cert type -1
> > debug1: Local version string SSH-2.0-OpenSSH_7.8
> > debug1: Remote protocol version 2.0, remote software version
> > OpenSSH_7.4
> > debug1: match: OpenSSH_7.4 pat
> > OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,Op
> > enSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x0402
> > debug1: Authenticating to 209.132.181.4:22 as 'martin'
> > debug1: SSH2_MSG_KEXINIT sent
> > debug1: SSH2_MSG_KEXINIT received
> > debug1: kex: algorithm: curve25519-sha...@libssh.org
> > debug1: kex: host key algorithm: ssh-rsa-cert-...@openssh.com
> > debug1: kex: server->client cipher: aes256-...@openssh.com MAC:
> >  compression: none
> > debug1: kex: client->server cipher: aes256-...@openssh.com MAC:
> >  compression: none
> > debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> > debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> > debug1: Server host certificate: ssh-rsa-cert-...@openssh.com
> > SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc, serial
> > 1534273416
> > ID "pkgs02.phx2.fedoraproject.org" CA ssh-rsa
> > SHA256:IPuhCSNXqj4m2eq6UKYE1jHFglLgLCbBzINft+OxUMA valid from
> > 2018-08-14T20:03:36 to 2019-08-13T21:03:36
> > debug1: No matching CA found. Retry with plain key
> > debug1: Host '209.132.181.4' is known and matches the RSA host key.
> > debug1: Found key in /home/martin/.ssh/known_hosts:3
> > debug1: rekey after 4294967296 blocks
> > debug1: SSH2_MSG_NEWKEYS sent
> > debug1: expecting SSH2_MSG_NEWKEYS
> > debug1: SSH2_MSG_NEWKEYS received
> > debug1: rekey after 4294967296 blocks
> > debug1: SSH2_MSG_EXT_INFO received
> > debug1: kex_input_ext_info: server-sig-algs= > 512>
> > debug1: SSH2_MSG_SERVICE_ACCEPT received
> > debug1: Authentications that can continue: publickey
> > debug1: Next authentication method: publickey
> > debug1: Offering public key: RSA
> > SHA256:82HdmjCwCpo/Ko2UZQVjBlOB4w+ma4vqMvXhqsE9WSU
> > /home/martin/.ssh/id_rsa
> > debug1: Authentications that can continue: publickey
> > debug1: Trying private key: /home/martin/.ssh/id_dsa
> > debug1: Trying private key: /home/martin/.ssh/id_ecdsa
> > debug1: Trying private key: /home/martin/.ssh/id_ed25519
> > debug1: Trying private key: /home/martin/.ssh/id_xmss
> > debug1: No more authentication methods to try.
> > martin@209.132.181.4: Permission denied (publickey).
> > 
> > Thanks for your help
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:

Re: [modularity] Recommended platform: [] and version 2 format

2018-09-12 Thread Adam Samalik 
That's right!

This and more is documented in the Modularity section of Fedora Docs:
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/

On Wed, Sep 12, 2018 at 10:56 AM Jun Aruga  wrote:

> Just sharing information.
>
> When talking with a person in modularity team, I have told that for a
> module config yaml file's below elements, the empty array "[]" was
> recommended on Fedora.
>
> /data/dependencies/buildrequires/platform
> /data/dependencies/requires/platform
>
> Because when platform is  "[]", the module is built on current
> supported platforms (right now f28, f29, and f30). The binary of the
> module are prepared for each platform.
> I hope the document is updated including this recommended setting as a
> best practice.
>
> ```
> diff --git a/ruby.yaml b/ruby.yaml
>  tracker: https://bugs.ruby-lang.org/
>  dependencies:
>  - buildrequires:
> -platform: [f29]
> +platform: []
>requires:
> -platform: [f29]
> +platform: []
>  components:
>  # SRPMs
>  rpms:
> ```
>
> Also seeing several modules' config YAML files, some config files are
> still version 1.
> I like to share that we can use the version 2, changing the /version
> element from 1 to 2.
>
> Version 2 spec:
> https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml
>
> Regards,
>
> --
> Jun Aruga jar...@redhat.com
> ___
> 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
>


-- 

Adam Šamalík
---
Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

[modularity] Recommended platform: [] and version 2 format

2018-09-12 Thread Jun Aruga 
Just sharing information.

When talking with a person in modularity team, I have told that for a
module config yaml file's below elements, the empty array "[]" was
recommended on Fedora.

/data/dependencies/buildrequires/platform
/data/dependencies/requires/platform

Because when platform is  "[]", the module is built on current
supported platforms (right now f28, f29, and f30). The binary of the
module are prepared for each platform.
I hope the document is updated including this recommended setting as a
best practice.

```
diff --git a/ruby.yaml b/ruby.yaml
 tracker: https://bugs.ruby-lang.org/
 dependencies:
 - buildrequires:
-platform: [f29]
+platform: []
   requires:
-platform: [f29]
+platform: []
 components:
 # SRPMs
 rpms:
```

Also seeing several modules' config YAML files, some config files are
still version 1.
I like to share that we can use the version 2, changing the /version
element from 1 to 2.

Version 2 spec:
https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml

Regards,

-- 
Jun Aruga jar...@redhat.com
___
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

Re: Managing stream (arbitrary) branch and module lifecycles

2018-09-12 Thread Dominik 'Rathann' Mierzejewski 
On Tuesday, 11 September 2018 at 21:43, Richard Shaw wrote:
[...]
> This would take care of most of the complains about people using "git merge
> master" across release branches (even though that's the workflow documented
> in the wiki). I know I CAN use git cherry-pick but I've never used it
> before and again, I'm not a program. Almost everything I've learned about
> git is through Fedora package maintenance and some small pull requests for
> minor build fixes with packages I maintain.
> 
> The hard part for me is maintaining EL 6/7 branches. I know there are a lot
> of complaints about using %if conditionals in specs to have one spec file
> for all Fedora and EPEL releases and I agree when it gets to be too much it
> makes the spec very unreadable especially by others (proven packagers) that
> may have to step in and make changes. If stream branches could somehow make
> this easier that would be great.

I found the "merging upwards" workflow from gitworkflows(7) quite useful for
Fedora for leaf packages that can be updated across the board while
retaining some small differences between branches like changelogs.

Branches remain mergeable and you can easily remove any conditionals and
keep cruft limited to older branches.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPMFusion   http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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

Re: [modularity] Removing obsolete github repositories with module definitions

2018-09-12 Thread Petr Šabata 
On Tue, Sep 11, 2018 at 04:24:05PM -0400, Langdon White wrote:
> On Tue, Sep 11, 2018 at 3:09 PM Stephen Gallagher 
> wrote:
> 
> > Go ahead
> >
> >
> +1

+1 as well.

P

> 
> On Tue, Sep 11, 2018 at 3:04 PM Adam Samalik  wrote:
> >
> >> We have some obsolete github repositories [1] from the f26 and f27 period
> >> we are no longer using. I feel like it might be confusing to people. So I'd
> >> like to remove them all. Any objections?
> >>
> >> [1] https://github.com/modularity-modules/
> >> --
> >>
> >> Adam Šamalík
> >> ---
> >> Software Engineer
> >> Red Hat
> >> ___
> >> devel mailing list -- devel@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://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
> >>
> > ___
> > 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
> >

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



signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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

Re: fedpkg clone doesn*t work

2018-09-12 Thread Pavel Zhukov 
"Martin Gansser"  writes:

> isn't possible.
>
> [martin@f28 ~]$ ssh -i ~/.ssh/id_rsa marti...@fedorapeople.org
> packet_write_wait: Connection to 152.19.134.199 port 22: Broken pipe
As it's written in bz#1623929
Please add
PubkeyAcceptedKeyTypes rsa-sha2-256,rsa-sha2-512
in corresponding section of your ssh config file as a workaround

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

Re: fedpkg clone doesn*t work

2018-09-12 Thread Pavel Zhukov 

Bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1627875

"Martin Gansser"  writes:

> I tried
>
> fedpkg clone lollypop
>
> Cloning into 'lollypop'...
> marti...@pkgs.fedoraproject.org: Permission denied (publickey).
> fatal: Could not read from remote repository.

>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute clone: Failed to execute command.
>
>
> [martin@f28 fedora-scm]$ fedpkg clone lollypop
> Cloning into 'lollypop'...
> Enter passphrase for key '/home/martin/.ssh/id_rsa': 
> packet_write_wait: Connection to 209.132.181.4 port 22: Broken pipe
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute clone: Failed to execute command.
>
> [martin@f28 fedora-scm]$ ssh -vT 209.132.181.4
> OpenSSH_7.8p1, OpenSSL 1.1.0h-fips  27 Mar 2018
> debug1: Reading configuration data /home/martin/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
> debug1: Reading configuration data 
> /etc/crypto-policies/back-ends/openssh.config
> debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
> debug1: Connecting to 209.132.181.4 [209.132.181.4] port 22.
> debug1: Connection established.
> debug1: identity file /home/martin/.ssh/id_rsa type 0
> debug1: identity file /home/martin/.ssh/id_rsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_dsa type -1
> debug1: identity file /home/martin/.ssh/id_dsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_ecdsa type -1
> debug1: identity file /home/martin/.ssh/id_ecdsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_ed25519 type -1
> debug1: identity file /home/martin/.ssh/id_ed25519-cert type -1
> debug1: identity file /home/martin/.ssh/id_xmss type -1
> debug1: identity file /home/martin/.ssh/id_xmss-cert type -1
> debug1: Local version string SSH-2.0-OpenSSH_7.8
> debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
> debug1: match: OpenSSH_7.4 pat 
> OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7*
>  compat 0x0402
> debug1: Authenticating to 209.132.181.4:22 as 'martin'
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: algorithm: curve25519-sha...@libssh.org
> debug1: kex: host key algorithm: ssh-rsa-cert-...@openssh.com
> debug1: kex: server->client cipher: aes256-...@openssh.com MAC:  
> compression: none
> debug1: kex: client->server cipher: aes256-...@openssh.com MAC:  
> compression: none
> debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> debug1: Server host certificate: ssh-rsa-cert-...@openssh.com
> SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc, serial 1534273416
> ID "pkgs02.phx2.fedoraproject.org" CA ssh-rsa
> SHA256:IPuhCSNXqj4m2eq6UKYE1jHFglLgLCbBzINft+OxUMA valid from
> 2018-08-14T20:03:36 to 2019-08-13T21:03:36
> debug1: No matching CA found. Retry with plain key
> debug1: Host '209.132.181.4' is known and matches the RSA host key.
> debug1: Found key in /home/martin/.ssh/known_hosts:3
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_EXT_INFO received
> debug1: kex_input_ext_info: server-sig-algs=
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering public key: RSA 
> SHA256:82HdmjCwCpo/Ko2UZQVjBlOB4w+ma4vqMvXhqsE9WSU /home/martin/.ssh/id_rsa
> debug1: Authentications that can continue: publickey
> debug1: Trying private key: /home/martin/.ssh/id_dsa
> debug1: Trying private key: /home/martin/.ssh/id_ecdsa
> debug1: Trying private key: /home/martin/.ssh/id_ed25519
> debug1: Trying private key: /home/martin/.ssh/id_xmss
> debug1: No more authentication methods to try.
> martin@209.132.181.4: Permission denied (publickey).
>
> Thanks for your help
> ___
> 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
___
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:

Re: Summary/Minutes from today's FESCo Meeting (2018-09-10) [announcement of additional resolutions]

2018-09-12 Thread Zbigniew Jędrzejewski-Szmek 
A few tickets were resolved before yesterday's meeting, but weren't
announced. Since the time is precious here, I'm announcing them here
(instead of waiting for the next week):


= Discussed and Voted in the Ticket =
== Decide status of dbus-broker change ==
https://pagure.io/fesco/issue/1986
This Change is deferred to F30 (+6, 0, 0)


== Forbid updating Qt to next major version in stable Fedora releases ==
https://pagure.io/fesco/issue/1984
The Qt maintainers are doing nothing wrong and the update is not in
violation of the Stable Updates Policy. (+6, 0, 0)

[to clarify: this means that the ticket is rejected, since the ticket
was about rejecting the update.]


== Implement keepalive requirement for Spins and Labs ==
https://pagure.io/fesco/issue/1972
In each release cycle, the Program Manager will send an request to the
owners of all Spins and Labs to confirm that they should be built for
the next release. The ones that don't respond will be dropped for that
release. Responses to this request must be made sufficiently in
advance of the Branch to allow RCM to react to the results. (+5, 0, 0)


-- 
Zbyszek



On Mon, Sep 10, 2018 at 01:48:43PM -0500, Randy Barlow wrote:
> =
> #fedora-meeting-1: FESCO (2018-09-10)
> =
>
>
> Meeting started by bowlofeggs at 15:00:00 UTC. The full logs are
> available at
> https://meetbot.fedoraproject.org/fedora-meeting-1/2018-09-10/fesco.2018-09-10-15.00.log.html
> .
>
>
>
> Meeting summary
> ---
> * init process  (bowlofeggs, 15:00:00)
>
> * #1988 Josh Boyer has resigned  (bowlofeggs, 15:02:05)
>   * AGREED: FESCo chooses Justin Forbes (@jforbes) to fill the seat
> until the next election. (+8, 0, -0)  (bowlofeggs, 15:05:48)
>   * ACTION: nirik will give jforbes access to fesco'y things
> (bowlofeggs, 15:06:57)
>   * ACTION: bowlofeggs will update the fesco wiki page  (bowlofeggs,
> 15:07:06)
>
> * #1967 Fedora 29 incomplete changes  (bowlofeggs, 15:13:41)
>   * LINK: https://fedoraproject.org/wiki/Changes/Update_festival_to_2.5
> (bowlofeggs, 15:15:10)
>   * AGREED: we will wait for festival to be done and push in the new
> version after beta if it is ready before GA (+8, 0, -0)
> (bowlofeggs, 15:19:18)
>   * AGREED: FESCo acks the cloud image updates change and notes that
> they need to be ready after GA (+8, 0, -0)  (bowlofeggs, 15:25:57)
>   * LINK: https://silverblue.fedoraproject.org/ looks quite good
> (zbyszek, 15:31:18)
>   * LINK: https://github.com/rhinstaller/anaconda/pull/1510/files
> (zbyszek, 15:39:14)
>   * AGREED: we will file a separate fesco ticket about the silverblue
> change, ask for status there, and vote there (+8, 1, -0)
> (bowlofeggs, 15:59:45)
>   * ACTION: zbyszek to create the ticket  (zbyszek, 15:59:54)
>
> * #1974 Problematic blocker for F29: dnf 'offline' module tracking
>   (bowlofeggs, 16:00:57)
>   * AGREED: we move this to a final blocker and also add a common bugs
> for beta and hope for the best (+7, 1, -0)  (bowlofeggs, 16:13:51)
>
> * #1976 Review of release-blocking deliverables for Fedora 29
>   (bowlofeggs, 16:14:06)
>   * AGREED: APPROVED (+9, 0, -0)  (bowlofeggs, 16:18:28)
>
> * Next week's chair  (bowlofeggs, 16:18:39)
>   * ACTION: sgallagh will chair next week's meeting  (bowlofeggs,
> 16:19:16)
>
> * open floor  (bowlofeggs, 16:19:21)
>   * LINK:
>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GYUFNAQENEMHJEIDNIBTUWNUEKS7XZ2U/
> (tyll, 16:26:54)
>
> Meeting ended at 16:33:14 UTC.
>




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

Re: fedpkg clone doesn*t work

2018-09-12 Thread Pavel Zhukov 

There's nothing to do with keys.
Similar issue was reported in ArchLinux:
https://bugs.archlinux.org/task/59838

I'm able clone repo from my F27 machine but F28 one with 
openssh-7.8p1-1.fc28.x86_64
failed with:

debug1: Offering public key: RSA SHA256:[...]
debug1: send_pubkey_test: no mutual signature algorithm



"Martin Gansser"  writes:

> I tried
>
> fedpkg clone lollypop
>
> Cloning into 'lollypop'...
> marti...@pkgs.fedoraproject.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute clone: Failed to execute command.
>
>
> [martin@f28 fedora-scm]$ fedpkg clone lollypop
> Cloning into 'lollypop'...
> Enter passphrase for key '/home/martin/.ssh/id_rsa': 
> packet_write_wait: Connection to 209.132.181.4 port 22: Broken pipe
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute clone: Failed to execute command.
>
> [martin@f28 fedora-scm]$ ssh -vT 209.132.181.4
> OpenSSH_7.8p1, OpenSSL 1.1.0h-fips  27 Mar 2018
> debug1: Reading configuration data /home/martin/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
> debug1: Reading configuration data 
> /etc/crypto-policies/back-ends/openssh.config
> debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
> debug1: Connecting to 209.132.181.4 [209.132.181.4] port 22.
> debug1: Connection established.
> debug1: identity file /home/martin/.ssh/id_rsa type 0
> debug1: identity file /home/martin/.ssh/id_rsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_dsa type -1
> debug1: identity file /home/martin/.ssh/id_dsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_ecdsa type -1
> debug1: identity file /home/martin/.ssh/id_ecdsa-cert type -1
> debug1: identity file /home/martin/.ssh/id_ed25519 type -1
> debug1: identity file /home/martin/.ssh/id_ed25519-cert type -1
> debug1: identity file /home/martin/.ssh/id_xmss type -1
> debug1: identity file /home/martin/.ssh/id_xmss-cert type -1
> debug1: Local version string SSH-2.0-OpenSSH_7.8
> debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
> debug1: match: OpenSSH_7.4 pat 
> OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7*
>  compat 0x0402
> debug1: Authenticating to 209.132.181.4:22 as 'martin'
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: algorithm: curve25519-sha...@libssh.org
> debug1: kex: host key algorithm: ssh-rsa-cert-...@openssh.com
> debug1: kex: server->client cipher: aes256-...@openssh.com MAC:  
> compression: none
> debug1: kex: client->server cipher: aes256-...@openssh.com MAC:  
> compression: none
> debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> debug1: kex: curve25519-sha...@libssh.org need=32 dh_need=32
> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> debug1: Server host certificate: ssh-rsa-cert-...@openssh.com
> SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc, serial 1534273416
> ID "pkgs02.phx2.fedoraproject.org" CA ssh-rsa
> SHA256:IPuhCSNXqj4m2eq6UKYE1jHFglLgLCbBzINft+OxUMA valid from
> 2018-08-14T20:03:36 to 2019-08-13T21:03:36
> debug1: No matching CA found. Retry with plain key
> debug1: Host '209.132.181.4' is known and matches the RSA host key.
> debug1: Found key in /home/martin/.ssh/known_hosts:3
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_EXT_INFO received
> debug1: kex_input_ext_info: server-sig-algs=
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering public key: RSA 
> SHA256:82HdmjCwCpo/Ko2UZQVjBlOB4w+ma4vqMvXhqsE9WSU /home/martin/.ssh/id_rsa
> debug1: Authentications that can continue: publickey
> debug1: Trying private key: /home/martin/.ssh/id_dsa
> debug1: Trying private key: /home/martin/.ssh/id_ecdsa
> debug1: Trying private key: /home/martin/.ssh/id_ed25519
> debug1: Trying private key: /home/martin/.ssh/id_xmss
> debug1: No more authentication methods to try.
> martin@209.132.181.4: Permission denied (publickey).
>
> Thanks for your help
> ___
> 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
___
devel mailing list --

Re: fedpkg clone doesn*t work

2018-09-12 Thread Martin Gansser 
isn't possible.

[martin@f28 ~]$ ssh -i ~/.ssh/id_rsa marti...@fedorapeople.org
packet_write_wait: Connection to 152.19.134.199 port 22: Broken pipe
___
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

Re: Testing / feedback request: DNF 3 crashes

2018-09-12 Thread Zbigniew Jędrzejewski-Szmek 
On Tue, Sep 11, 2018 at 12:26:09PM -0700, Adam Williamson wrote:
> Hi folks!
> 
> Around the time DNF 3 landed in Rawhide (hence F29), we had quite a few
> folks on these lists reporting issues, including crasher bugs. Many of
> these seemed somehow related to the DNF history database. They also
> were not easy to isolate and fix.
> 
> We're now close to the F29 Beta release, but we don't have a great
> sense of how many people are still having these problems with DNF 3.2
> or 3.3.
> 
> Can anyone who is still struggling with DNF crashes on *basic*
> operations on F29 or Rawhide please reply, and provide a few details on
> what you're seeing and any workarounds or fixes you've found?

I filed https://bugzilla.redhat.com/show_bug.cgi?id=1627694 yesterday.
The gist is that dnf stopped having locking around the rpm operation,
so it'll fail if two operations are invoked concurrently. Before it'd
very nicely do the downloads in parallel and then run the actual installations
sequentially. I think this is a huge regression in usability.

I also saw some "TransactionItem not found" messages, but this has already
been reported extensively.

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