ANNOUNCE storaged 2.1.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, a new version of storaged [1] is now available at [2]. Rawhide packages have already been built. The most significant feature of this release is: iSCSI initiator configuration API. Detailed list of changes since the first release: - - introduced CreatePartitionAndFormat() which combines 2 steps needed to create a partition and format it - - introduced *iSCSI initiator API*: - DiscoverFirmware() - DiscoverSendTargetsChap() - DiscoverSendTargetsNoAuth() - GetInitiatorName() - SetInitiatorName() - Login() - Logout() - for each iSCSI session, there is a separate object living on D-Bus - this depends, if my patch gets included into Fedora's iscsi-initiator-utils - - modular API was (a bit) redesigned - - daemon can be run from build directory --uninstalled - - added several tests for storagedctl - - moved from transifex to zanata [1]: https://github.com/storaged-project/storaged [2]: https://github.com/storaged-project/storaged/releases/tag/storaged-2.1.0 Please, feel free to forward this announce message to any other mailing list so that people get to know about it. Thanks and regards, - -- Peter Hatina EMEA ENG Developer Experience PGP:F32822A9 Red Hat, Inc. http://cz.redhat.com -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVeXI3AAoJELOyt3XzKCKpCf4H/2pJQfLbzPkSeCMNRQFT8Ju9 62tiJ36OXUH6IF0KiPCIfh82LDZewMpvl7qIGMYDIwSq+XfveAplyZSg9TBg+vmu vUWoPUrENBnin2a/wqHjJiBsPGlHUC4rGEs5Imh/DF2SXV+98GrirjnsbOhmESvY UXntqfR7/HbEdcm5XA4UXg829sQ5kG3KJFzxS7UiMzZxIKqbJ0SreIAdHBZ3SqLE 6AN99O6XCVzyUc1xIfVJ4OYClaCVBHu4I4n89A4DNw7VyJK7f6kbAqAEY+DLYe6A 6yosPKYb0KGNZCRrfY2T+bfbLagAspP+qqaAKAp+BS5eYYH4gVUxQ/Foz+NWKEA= =jlPc -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Heads up! I'm going to upgrade Wireshark up to 1.10.x in Fedora 18
Hi Peter, On 09/12/2013 10:00 AM, Peter Lemenkov wrote: Hello All! There are *lots* of CVEs against Wireshark shipped with Fedora 18 (quite old 1.8.8 version). * https://bugzilla.redhat.com/965942 * https://bugzilla.redhat.com/972762 * https://bugzilla.redhat.com/990189 In order to fix them and not to add additional work for the maintainers I'm thinking of upgrading up to 1.10.2 from 1.8.x. Well, idea looks fine, but before pushing such update, give us some time to reply to your message (3 minutes is not enough). Instead of backporting stuff let's build the latest stable! I'm sure users will love this, since new Wireshark adds a lot of new features and fixes all these CVEs. I would rather stick to 1.8.10, which is the latest Maintenance release of wireshark. 1.8.10 will be certainly more OK with Fedora Update Policy [1] [2] [3]. I don't think, Wireshark is on exception list. [1] http://fedoraproject.org/wiki/Updates_Policy#Stable_Releases [2] http://fedoraproject.org/wiki/Updates_Policy#Philosophy [3] Have a nice day :) -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Heads up! I'm going to upgrade Wireshark up to 1.10.x in Fedora 18
On 09/12/2013 10:17 AM, Peter Hatina wrote: Hi Peter, On 09/12/2013 10:00 AM, Peter Lemenkov wrote: Hello All! There are *lots* of CVEs against Wireshark shipped with Fedora 18 (quite old 1.8.8 version). * https://bugzilla.redhat.com/965942 * https://bugzilla.redhat.com/972762 * https://bugzilla.redhat.com/990189 In order to fix them and not to add additional work for the maintainers I'm thinking of upgrading up to 1.10.2 from 1.8.x. Well, idea looks fine, but before pushing such update, give us some time to reply to your message (3 minutes is not enough). Instead of backporting stuff let's build the latest stable! I'm sure users will love this, since new Wireshark adds a lot of new features and fixes all these CVEs. I would rather stick to 1.8.10, which is the latest Maintenance release of wireshark. 1.8.10 will be certainly more OK with Fedora Update Policy [1] [2] [3]. I don't think, Wireshark is on exception list. [1] http://fedoraproject.org/wiki/Updates_Policy#Stable_Releases [2] http://fedoraproject.org/wiki/Updates_Policy#Philosophy [3] Have a nice day :) Ah, link 3 is missing. [3] http://fedoraproject.org/wiki/Updates_Policy#All_other_updates [4] http://fedoraproject.org/wiki/Updates_Policy#Exceptions Cheers -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Heads up! I'm going to upgrade Wireshark up to 1.10.x in Fedora 18
Hi, On 09/12/2013 02:12 PM, Jan Kratochvil wrote: On Thu, 12 Sep 2013 10:42:20 +0200, Peter Lemenkov wrote: I'm afraid that's just adds additional work for maintainers w/o any visible benefits. The benefits are the stable Fedora release does not break 3rd party applications during its deployment/lifecycle. Let's move further instead of backporting - that's just a leafnode app so nobody got hurt by a potential dependency issue. wireshark.rpm contains many commandline utilities which may be used by 3rd party sysadmin scripts (and maybe even 3rd party C applications). Correct. further in your explanation means nullifying the long Fedora alpha/beta release engineering and also nullifying the upstream efforts to release 1.8.x versions even after 1.10.0 had been already released. Agree. joke So let's drop the Fedora releases effort and we can all just run Rawhide. /joke Actually, this will make living releases of Fedora kind of Rawhide. As stated in former mail, it would be good to do 1.8.10 upgrade in Fedora 18. Regards, Jan -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
debuginfo package
Hi, can you, please, help me fix these warnings in wireshark package? I get plenty of warnings when creating debuginfo package, that look like this: ... cpio: wireshark-1.2.15/asn1/x509if/packet-x509if-dis-tab.c: Cannot stat: No such file or directory cpio: wireshark-1.2.15/asn1/x509if/packet-x509if-ett.c: Cannot stat: No such file or directory cpio: wireshark-1.2.15/asn1/x509if/packet-x509if-exp.h: Cannot stat: No such file or directory ... Does find-debuginfo.sh get confused, or where do those non-existing files come from? Thank you in advance. -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
