Fedora-Atomic 27-20180419.0 compose check report
No missing expected images. Passed openQA tests: 2/2 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: iverilog orphaned
On Thu, Apr 19, 2018 at 03:51:29AM +, Vascom wrote: > I can take it. > FAS name: vascom The package was already orphaned by Kiara, so you need to either ask chitlesh or open a releng ticket. Zbyszek > > чт, 19 апр. 2018 г., 4:06 Kiara Navarro : > > > Hi all, > > > > I am orphaning iverilog package ( > > https://src.fedoraproject.org/rpms/iverilog). Please adopt it. I know > > that some contributor is already interested in this package, then go ahead. > > > > Best regards! > > > > -- > > *K.N* > > > > *GPG-KEY*: A81DB1D8 > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Stop building zenmap/ndiff since F29
Hi all nmap GUI users (if any :-) ), Due to python2 deprecation/EOL in 2020. We'll stop building zenmap and ndiff (GUI interface for nmap) starting from fedora 29. Upstream ticket [1] opened. In meantime I'm working on porting it to python3 but it's pygtk application s... [1] https://github.com/nmap/nmap/issues/1176 -- Pavel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: ** Newsletter/Marketing email** Fedora-Atomic 27-20180414.0 compose check report
On 16/04/18 09:02 -0500, mcatanz...@gnome.org wrote: Look at the mail footer: "To unsubscribe send an email to devel-le...@lists.fedoraproject.org" This has already been pointed out to you months ago: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ILRUD2M3HQ2URE3Y7O7CN5FRXI3AWXKP/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora 28 Final release Go/No-Go Meeting on Thursday, April 26 @ 17:00 UTC
Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 28 Final. The meeting is going to be held on Thursday, April 26, 2018 at 17:00 UTC. Please check the [1] link for your time zone. Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. Release Candidate (RC) availability and good QA coverage are prerequisites for the Go/No-Go meeting. If you have any bug on the list, please help us with Beta release. If we won't be ready by Thursday, we will use this meeting to review blockers and decide what to do. In the meantime, please keep also an eye on the Fedora 28 Final Blocker list [2]. For more details about this meeting please follow the [3] link. [1] https://apps.fedoraproject.org/calendar/meeting/9025/ [2] http://qa.fedoraproject.org/blockerbugs/milestone/28/final/buglist [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting Thank you in advance 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 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora 28 Final Release Readiness Meeting on Thursday, April 26 @ 19:00 UTC
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 28 Final Release Readiness Meeting meeting. The meeting is going to be held on Thursday, April 26, 2018 at 19:00 UTC. Please check the [1] link for your time zone. We will meet to make sure we are coordinated and ready for the Final release of Fedora 28. Please note that this meeting is going to be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but it is by purpose 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 please check the [2] link. [1] https://apps.fedoraproject.org/calendar/meeting/9024/ [2] https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you 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 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: plan to update brotli to 1.0.4 in Rawhide
On Wed, 18 Apr 2018 15:53:06 -0700 Adam Williamson wrote: > On Wed, 2018-04-18 at 17:43 -0500, po...@pouar.net wrote: > > the soname the reverse deps link to doesn't seemed to have changed as > > they all link to the .so.1 soname, but I'm not sure how to check for > > "weirdness" in these packages > > > From what you've posted I don't think there's any problem, basically. > Just go ahead and send the new package to Rawhide and everything should > keep working. I promise not to yell if it doesn't. :P Just did after I read this email, though I didn't say anything until now as I didn't think to respond to this until now -- GPG Keys: https://keybase.io/pouar Tox ID: 2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A Matrix ID: @Pouar:matrix.org Social Links: https://www.pouar.net/social.php pgpIbPVUzsOCj.pgp Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Should boost package install boost-python2 / boost-python3 / both or none?
I was recently surprised that `dnf install boost` brings in python2. It is like that because boost brings in bost-python and that is python2 ATM. I've reported it as a bug, because it bugs me :) https://bugzilla.redhat.com/show_bug.cgi?id=1569483 However Jonathan Wakely (the boost maintainer) says this needs broader audience. So I'm asking here on devel: Should the 'boost' metapackage install boost-python at all? If so, what versions? -- 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 28 compose report: 20180419.n.0 changes
OLD: Fedora-28-20180418.n.0 NEW: Fedora-28-20180419.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:1 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:15.32 MiB Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Container_Minimal_Base docker s390x Path: Container/s390x/images/Fedora-Container-Minimal-Base-28-20180419.n.0.s390x.tar.xz = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = Package: axis-1.4-37.fc28 Summary: SOAP implementation in Java RPMs:axis axis-javadoc axis-manual Size:15.32 MiB = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Should boost package install boost-python2 / boost-python3 / both or none?
On 19/04/18 19:07 +0200, Miro Hrončok wrote:
I was recently surprised that `dnf install boost` brings in python2.
It is like that because boost brings in bost-python and that is
python2 ATM. I've reported it as a bug, because it bugs me :)
https://bugzilla.redhat.com/show_bug.cgi?id=1569483
However Jonathan Wakely (the boost maintainer) says this needs broader
audience.
So I'm asking here on devel:
Should the 'boost' metapackage install boost-python at all? If so,
what versions?
I think my preference would be to simply remove boost-python and
boost-numpy from the 'boost' package, and remove their headers and
shared library symlinks from the boost-devel package.
This would make the Boost.Python packaging consistent for python2 and
python3: you'd always need to explicitly choose which you want.
This will mean if you want to install Boost.Python you won't be able
to just use 'dnf install boost' you'll need to also install
boost-python2 or boost-python3 explicitly.
If you want to compile code using Boost.Python it won't be enough to
install boost-devel, you'll need to choose either boost-python2-devel
or boost-python3-devel.
The alternative would be to switch the "default" to be the python3
packages (and split some things out into new packages, e.g. currently
boost-mpich-devel installs %{_libdir}/mpich/lib/libboost_mpi_python.so
but this should really be in a separate boost-mpich-python2-devel
package).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Should boost package install boost-python2 / boost-python3 / both or none?
On 19/04/18 18:42 +0100, Jonathan Wakely wrote:
On 19/04/18 19:07 +0200, Miro Hrončok wrote:
I was recently surprised that `dnf install boost` brings in python2.
It is like that because boost brings in bost-python and that is
python2 ATM. I've reported it as a bug, because it bugs me :)
https://bugzilla.redhat.com/show_bug.cgi?id=1569483
However Jonathan Wakely (the boost maintainer) says this needs
broader audience.
So I'm asking here on devel:
Should the 'boost' metapackage install boost-python at all? If so,
what versions?
I think my preference would be to simply remove boost-python and
boost-numpy from the 'boost' package, and remove their headers and
shared library symlinks from the boost-devel package.
This would make the Boost.Python packaging consistent for python2 and
python3: you'd always need to explicitly choose which you want.
This will mean if you want to install Boost.Python you won't be able
to just use 'dnf install boost' you'll need to also install
boost-python2 or boost-python3 explicitly.
If you want to compile code using Boost.Python it won't be enough to
install boost-devel, you'll need to choose either boost-python2-devel
or boost-python3-devel.
The alternative would be to switch the "default" to be the python3
packages (and split some things out into new packages, e.g. currently
boost-mpich-devel installs %{_libdir}/mpich/lib/libboost_mpi_python.so
but this should really be in a separate boost-mpich-python2-devel
package).
I forgot to mention that this will break any packages using
Boost.Python which currently just have BR: boost-devel but that's
arguably a good thing anyway. It will be easy to fix them, and we will
have to make an explicit decision whether they should really be
using the python2 version, or should use boost-python3 instead.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Should boost package install boost-python2 / boost-python3 / both or none?
On Thu, Apr 19, 2018 at 1:02 PM, Jonathan Wakely wrote: > > I forgot to mention that this will break any packages using > Boost.Python which currently just have BR: boost-devel but that's > arguably a good thing anyway. It will be easy to fix them, and we will > have to make an explicit decision whether they should really be > using the python2 version, or should use boost-python3 instead. +1 Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora 28-20180419.n.0 compose check report
No missing expected images. Failed openQA tests: 5/137 (x86_64), 3/24 (i386), 1/2 (arm) New failures (same test did not fail in 28-20180417.n.0): ID: 226702 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/226702 Old failures (same test failed in 28-20180417.n.0): ID: 226721 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/226721 ID: 226722 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/226722 ID: 226737 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/226737 ID: 226741 Test: x86_64 AtomicWorkstation-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/226741 ID: 226745 Test: x86_64 AtomicWorkstation-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/226745 ID: 226747 Test: x86_64 AtomicWorkstation-dvd_ostree-iso install_no_user URL: https://openqa.fedoraproject.org/tests/226747 ID: 226761 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/226761 ID: 226822 Test: i386 universal install_simple_encrypted URL: https://openqa.fedoraproject.org/tests/226822 Soft failed openQA tests: 5/137 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) New soft failures (same test did not soft fail in 28-20180417.n.0): ID: 226704 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/226704 Old soft failures (same test soft failed in 28-20180417.n.0): ID: 226686 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/226686 ID: 226699 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/226699 ID: 226700 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/226700 ID: 226778 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/226778 ID: 226784 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/226784 ID: 226807 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/226807 Passed openQA tests: 121/137 (x86_64), 19/24 (i386) New passes (same test did not pass in 28-20180417.n.0): ID: 226706 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/226706 Skipped openQA tests: 7 of 163 Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 40 packages(s) added since previous compose: ModemManager, ModemManager-glib, NetworkManager-bluetooth, NetworkManager-wifi, NetworkManager-wwan, atmel-firmware, authselect-compat, b43-fwcutter, b43-openfwwf, bluez... 1 packages(s) removed since previous compose: authconfig 1 services(s) added since previous compose: ModemManager.service System load changed from 0.08 to 0.22 Previous test data: https://openqa.fedoraproject.org/tests/224799#downloads Current test data: https://openqa.fedoraproject.org/tests/226676#downloads Installed system changes in test x86_64 Server-boot-iso install_default: 40 packages(s) added since previous compose: ModemManager, ModemManager-glib, NetworkManager-bluetooth, NetworkManager-wifi, NetworkManager-wwan, atmel-firmware, authselect-compat, b43-fwcutter, b43-openfwwf, bluez... 1 packages(s) removed since previous compose: authconfig 1 services(s) added since previous compose: ModemManager.service Previous test data: https://openqa.fedoraproject.org/tests/224800#downloads Current test data: https://openqa.fedoraproject.org/tests/226677#downloads Installed system changes in test x86_64 Server-dvd-iso install_default_upload: 39 packages(s) added since previous compose: ModemManager, ModemManager-glib, NetworkManager-bluetooth, NetworkManager-wifi, NetworkManager-wwan, atmel-firmware, b43-fwcutter, b43-openfwwf, bluez, bluez-libs... 1 services(s) added since previous compose: ModemManager.service Previous test data: https://openqa.fedoraproject.org/tests/224801#downloads Current test data: https://openqa.fedoraproject.org/tests/226678#downloads Installed system changes in test x86_64 Server-dvd-iso install_default@uefi: 39 packages(s) added since previous compose: ModemManager, ModemManager-glib, NetworkManager-bluetooth, NetworkManager-wifi, NetworkManager-wwan, atmel-firmware, b43-fwcutter, b43-openfwwf, bluez, bluez-libs... 1 services(s) added since previous compose: ModemManager.service Previous test data: https://openqa.fedoraproject.org/tests/225187#downloads Current test data: https://openqa.fedoraproject.org/tests/226679#downloads Installed system changes in test i386 Server-boot-iso install_default: 39 packages(s) added since previous compose:
Fedora Atomic Host Two Week Release Announcement: 27.122
A new Fedora Atomic Host update is available via an OSTree update: Version: 27.122 Commit(x86_64): 931ebb3941fc49af706ac5a90ad3b5a493be4ae35e85721dabbfd966b1ecbf99 Commit(aarch64): 837cd0c5e3a5656316ebf6142315ac107c8592d5c8d64a02e8a62919eee9f46f Commit(ppc64le): a1f565d73f1f1b6f6d7ef992251f21a704c4a8de40c41fc62be69c5ec2a65329 We are releasing images from multiple architectures but please note that x86_64 architecture is the only one that undergoes automated testing at this time. Existing systems can be upgraded in place via e.g. `atomic host upgrade`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Alternatively, image artifacts can be found at the following links: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180419.0.iso https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180419.0.iso https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180419.0.iso https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-libvirt.box https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-virtualbox.box Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-27-20180419.0-aarch64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20180419.0-ppc64le-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-27-20180419.0-x86_64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20180419.0-aarch64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180419.0-ppc64le-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20180419.0-x86_64-CHECKSUM For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Atomic Wiki space. https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Schedule for Friday's FESCo Meeting (2018-04-20)
Following is the list of topics that will be discussed in the FESCo meeting Friday at 15:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2018-04-20 15:00 UTC' Links to all issues below can be found at: https://pagure.io/fesco/report/meeting_agenda = Followups = #topic #1868 Change the Changes template .fesco 1868 https://pagure.io/fesco/issue/1868 #topic #1872 Disable Test Gating requirements until more UI is enabled .fesco 1872 https://pagure.io/fesco/issue/1872 #topic #1876 Please orphan all LXQt packages / nonresponsive maintainer heliocastro .fesco 1876 https://pagure.io/fesco/issue/1876 = New business = #topic #1880 Request to take over a package - 3+ weeks have passed .fesco 1880 https://pagure.io/fesco/issue/1880 #topic #1882 F28 Self Contained Change: java-openjdk 10 - rolling release for Short Term Support releases of OpenJDK .fesco 1882 https://pagure.io/fesco/issue/1882 #topic #1883 Request for rebase of libdnf/dnf after Fedora 28 GA .fesco 1883 https://pagure.io/fesco/issue/1883 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or 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
looking for the maintainer of python-flask-wtf
if you're the owner of python-flask-wtf. There's a pull request waiting for you. https://src.fedoraproject.org/rpms/python-flask-wtf ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Fedora Atomic Host Two Week Release Announcement: 27.122
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/19/2018 05:55 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 27.122 > Commit(x86_64): > 931ebb3941fc49af706ac5a90ad3b5a493be4ae35e85721dabbfd966b1ecbf99 > Commit(aarch64): > 837cd0c5e3a5656316ebf6142315ac107c8592d5c8d64a02e8a62919eee9f46f > Commit(ppc64le): > a1f565d73f1f1b6f6d7ef992251f21a704c4a8de40c41fc62be69c5ec2a65329 > > > We are releasing images from multiple architectures but please note > that x86_64 architecture is the only one that undergoes automated > testing at this time. > > Existing systems can be upgraded in place via e.g. `atomic host upgrade`. > > Corresponding image media for new installations can be downloaded from: > > https://getfedora.org/en/atomic/download/ > > Alternatively, image artifacts can be found at the following links: > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180419.0.iso > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180419.0.iso > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180419.0.iso > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-libvirt.box > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-virtualbox.box > > Respective signed CHECKSUM files can be found here: > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-27-20180419.0-aarch64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20180419.0-ppc64le-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-27-20180419.0-x86_64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20180419.0-aarch64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180419.0-ppc64le-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20180419.0-x86_64-CHECKSUM > > For direct download, the "latest" targets are always available here: > https://getfedora.org/atomic_iso_latest > https://getfedora.org/atomic_qcow2_latest > https://getfedora.org/atomic_raw_latest > https://getfedora.org/atomic_vagrant_libvirt_latest > https://getfedora.org/atomic_vagrant_virtualbox_latest > > Filename fetching URLs are available here: > https://getfedora.org/atomic_iso_latest_filename > https://getfedora.org/atomic_qcow2_latest_filename > https://getfedora.org/atomic_raw_latest_filename > https://getfedora.org/atomic_vagrant_libvirt_latest_filename > https://getfedora.org/atomic_vagrant_virtualbox_latest_filename > > For more information about the latest targets, please reference the Fedora > Atomic Wiki space. > > > https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links > > Do note that it can take some of the mirrors up to 12 hours to "check-in" at > their own discretion. > > Thank you, > Fedora Release Engineering > Hi everyone! We apologize for the delay in getting this release out the door. As a bonus for the wait we have AMIs that are available in additional regions (ap-northeast-2, ap-south-1). We'll be adding additional regions (the remaining missing regions) next release. Additionally, this will most likely be our last release of Fedora 27 Atomic Host. Very soon Fedora 28 will be released and we will be
tmux 2.7 will land on rawhide soon
Hi everyone, I'll update tmux (from 2.6 to 2.7) on rawhide in a few days, and after a week will update also for F28. the copr build is here, if you need to make some tests: https://copr.fedorainfracloud.org/coprs/filiperosset/rosset-rpms/build/743200/ - packages that could be affected by this update: anaconda-29.11-1.fc29.src.rpm atomic-devmode-0.3.7-4.fc28.src.rpm byobu-5.125-1.fc29.src.rpm powerline-2.6-7.fc29.src.rpm python-libtmux-0.6.0-3.fc28.src.rpm tmuxinator-0.6.11-5.fc28.src.rpm wemux-3.2.0-8.fc28.src.rpm powerline-0:2.6-7.fc29.src upstream changes: https://raw.githubusercontent.com/tmux/tmux/2.7/CHANGES Regards, Filipe R. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Stop building zenmap/ndiff since F29
On Thu, 2018-04-19 at 11:24 +0200, Pavel Zhukov wrote: > Hi all nmap GUI users (if any :-) ), > > Due to python2 deprecation/EOL in 2020. We'll stop building zenmap > and > ndiff (GUI interface for nmap) starting from fedora 29. Upstream > ticket > [1] opened. In meantime I'm working on porting it to python3 but it's > pygtk application s... IMHO, I don't agree, 1 years and 8 months to 2020, what is the rush ? Have we any alternative ? > [1] https://github.com/nmap/nmap/issues/1176 > > -- > Pavel > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
