September 2016 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] testing smartcardsupport in 42.2 beta 2
by stakanov＠freenet.de 28 Sep '16

28 Sep '16

I wish to test the smartcard support for pgp encryption in beta 2. (not Yubikey) Before to get to a working result I had to follow these steps and I was done: http://www.bress.net/blog/archives/203-How-to-use-a-cryptostick-with-Gnu-Pr… Question: a) is this still expected to require this user interaction to set up or should it work "out of the box". b) is local(!) root login via such a token foreseen or has the feature not been implemented (using RSA signature for authentication). c) is there any special function you would like me to try out for the sake of testing ( I will run signing, encrypting), i.e. I do not know if signing party is in the official repos and if it is expected to run. As it is a very widely used tool in signing parties, it would be good to know if it is functional. Does anybody know if this has been implemented (or is this packman and - in this case - does anybody know if packman will support beta2 with packages for testing? d) does Kleopatra now handle crypto hardware or wasn't it still implemented? The hardware is somewhat older but should be quite widely used especially in Germany and Northern Europe. A new version has been created by the producer https://blog.mozilla.org/security/files/2013/02/jpg-600x471.. Thank you. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] leap422 beta - brief installation report
by Per Jessen 27 Sep '16

27 Sep '16

I installed a xen guest this morning, server text-only pattern, all looks good. I was surprised by the new yast pattern selection, and also deselected a few font-related packages that I had no need for, but otherwise okay. -- Per Jessen, Zürich (19.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 70

Re: [opensuse-factory] 42.2 beta1 safe for daily use security wise?
by stakanov＠freenet.de 27 Sep '16

27 Sep '16

> -----Ursprüngliche Nachricht----- > Von: cagsm > Gesendet: Di. 27.09.2016 22:13 > An: suse-factory , > Betreff: Re: [opensuse-factory] 42.2 beta1 safe for daily use security wise? > > > Thank you for your elaboration, so leap 42.2 leans over towards > production use. Thanks for the published updates and cheers to all the > haters out there who try to derail and scare off people actually > trying to help with 42.2 testing and questions. I am sorry to hear that you have had bad experiences with hate speech and people who are spreading false information to try to scare of contributors (FUD). Could you please in future, once you encounter such facts, post them on opensuse(a)opensuse.org. Although it is difficult to hold hate speech and FUD personally responsible, at least on this lists there should not be space for it. So I think you are referring to other lists / forums? Please let us know, maybe we will be able to do something about it. If you use Luks encrypted LVM and EXT4 on your productive system you may want to wait a bit. There is a bug that may leave you with a non working system right after install. I do not know however if this is if you upgrade. For sure it can happen when you follow the proposal of the installer. http://bugzilla.opensuse.org/show_bug.cgi?id=997637 But I am sure you will work around it should it happen. Good luck and hope to hear more about the issues you pointed to. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] 42.2 beta1 safe for daily use security wise?
by cagsm 27 Sep '16

27 Sep '16

My rather testing machine of 42.1 upgraded to 42.2 beta1, I wonder if i should stay away from webbrowsing and real daily use on this beta1 state of the software, or can it still be considered somewhat safe? Should I better downgrade to 42.1 again via zypper dup and 41.1 and update repo again via forced replace packages or some parameters again? Thanks for hints. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

[opensuse-factory] How to install SuseStudio images now that yast2-live-installer is deprecated?
by S. 27 Sep '16

27 Sep '16

Hi everyone, Now that yast2-live-installer has been completely deprecated, I'm worried about the future of installing SuseStudio images. For now, the yast2-live-installer still works, although it requires replacing the /etc/YaST2/control.xml with this modified version: https://pastebin.mozilla.org/8912561 I'm worried that at some point it will completely break as Tumbleweed continues to evolve. What alternatives exist? Is anybody available to continue maintaining yast2-live-installer? Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] Reminder: openSUSE Leap 42.2 Beta 3 submission deadline Thursday
by Ludwig Nussel 27 Sep '16

27 Sep '16

Hi, This is a reminder for the upcoming openSUSE Leap 42.2 Beta 3 submission deadline. Please submit your packages latest Thursday, September 29 to openSUSE:Leap:42.2. The next milestone after Beta 3 will be RC1 so version updates should be completed now. The automatic submission of new Factory packages to 42.2 has been turned off. Let me also repeat what I wrote for Beta 2 as it still applies: If you've submitted already weeks ago but your submission wasn't accepted yet, please check why. The most common reasons are - Build failure in Staging:adi. All package submissions are built isolated in openSUSE:Leap:42.2:Staging:adi:<number> to make sure the submission is complete. Sometimes that fails due to different configurations in the devel project for example. Sometimes other packages need to be grouped into the same project. Let us know if your package needs manual help there. - Factory review. The 42.2 submissions wait for the submission to Factory in order to pass reviews there. Sometimes leaf packages have to wait a long time due to low priority. If your Factory submission is stuck e.g. in legal review for too long and it affects 42.2 let us know please, so we can adjust priorities. - Maintainer review. Packages submitted by someone other than the Factory package maintainer(s) have a review set to the devel project/package to ask for permission by the Factory package maintainer. If there's no reply for too long, try adding a comment in the request to get some attention or talk to the project maintainers directly. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Build Factory with -fPIE support
by Marcus Meissner 27 Sep '16

27 Sep '16

Hi, I have reestablished my PIE staging project, at openSUSE:Factory:Staging:PIE First rebuilds are looking largely good. There are some weird rpmlint python backtraces that hide the interesting errors :/ (Basically you can always test this yourself, osc meta prjconf -e <yourproject> and add: Requires: gcc-PIE (Or just add BuildRequires: gcc-PIE to your package for even quicker testing.) Check: - build was successful - extract RPMs and check binaries, using "file /usr/bin/foobar" BUILT WITH PIE: $ file /usr/bin/su /usr/bin/su: setuid ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=7a908643894dc9f6531406ac8ae9fa72008415dd, stripped "LSB shared object" is the trigger word. NOT YET PIE: $ file /bin/vim /bin/vim: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=e1848fb6201a18d0c17900dcf7936819c1a81ff9, stripped Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] New Tumbleweed snapshot 20160926 released!
by Dominique Leuenberger 27 Sep '16

27 Sep '16

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: fonts-config (20160914 -> 20160921) gstreamer-plugins-bad intel-gpu-tools (1.15 -> 1.16) libXfont (1.5.1 -> 1.5.2) patterns-openSUSE perl-Apache-AuthCookie (3.24 -> 3.25) perl-MIME-tools (5.507 -> 5.508) perl-Moose (2.1804 -> 2.1805) perl-Sub-Exporter-Progressive (0.001011 -> 0.001012) xf86-video-nouveau (1.0.12 -> 1.0.13) xorriso (1.4.4 -> 1.4.6) xproto (7.0.29 -> 7.0.31) === Details === ==== fonts-config ==== Version update (20160914 -> 20160921) - version 20160921 * add 59-family-prefer-lang-specific.conf to specify prefered family for each language * fix Noto Sans CJK is used for serif alias (boo#998301) * assign monospace to default of Oxygen Mono ==== gstreamer-plugins-bad ==== Subpackages: libgstadaptivedemux-1_0-0 libgstbadaudio-1_0-0 libgstbadbase-1_0-0 libgstbadvideo-1_0-0 libgstbasecamerabinsrc-1_0-0 libgstcodecparsers-1_0-0 libgstgl-1_0-0 libgstmpegts-1_0-0 libgstphotography-1_0-0 libgsturidownloader-1_0-0 libgstwayland-1_0-0 - Enable pkgconfig(tiger) BuildRequires for Tumbleweed. ==== intel-gpu-tools ==== Version update (1.15 -> 1.16) - Update to version 1.16 A new intel-gpu-tools quarterly release is available with the following changes: - Build automatically tests required when issueing a make check, Tests/subtests that receive a crash signal should print a backtrace when i-g-t is built with libunwind support (Marius Vlad) - lib/igt_kms: Force connector probing on first use (Chris Wilson) - vc4: Add a test for BO lookup failure error path (Eric Anholt) - tests/gem_mocs_settings: Remove direct register tests, and added RC6 tests (Peter Antoine) - Check for libdrm_intel and build if present, Add stubs for intel_bufmgr (Robert Foss) - igt/gem_mmap_gtt: Add a test to detect non-WC access (Chris Wilson) - Various documentation improvements (Daniel Vetter) - Added new tests: tests/kms_rmfb and tests/kms_atomic_transition, a test for fastboot, tests/kms_panel_fitting, and a test that only tries to set the current property values back, tests/kms_properties. Various improvements to tests/kms_cursor_legacy (Maarten Lankhorst) - lib/igt_kms: Use pipes for committing, not outputs and assign pipe properties in pipe init and many other improvements (Maarten Lankhorst) - tests/gem_workarounds: read test added as a basic test, fix assertion of num of regs (Mika Kuoppala) - Various improvements to tools/intel_bios_reader and tools/intel_reg (Ville Syrj�l�) - lib: Add x86 cpuid based feature detection (Chris Wilson) - demos/intel_sprite_on: Instead of looping until the first disconnected port is found, now go through all possible connectors, drawing the sprite on any connected display. (Jim Bride) - Multiple improvements to lib/igt_kms (Robert Foss) - lib/igt_aux: Framework for measuring latency in raising signals (Chris Wilson) - Various modifications to intel_chipset: Replace lookup of GT size with computation, remove unused PCI_CHIP ids, converting platforms names using device info (Chris Wilson) - tests/kms_chv_cursor_fail: Run the tests with fewer steps (Maarten Lankhorst) - lib/intel_chipset: Add more Kabylake PCI IDs and removed PCI IDs that are no longer listed as Kabylake (Rodrigo Vivi) - Basic framework for GVT-g testing has landed (Chris Wilson) - Various improvements to tests/kms_flip (Ville Syrj�l�) - igt/kms_cursor_legacy: Add a rudimentary test to detect stalled cursors, detect pageflip errors and check that cursor updates do not stall flips (Chris Wilson) - vGEM support: lib and added tests/vgem_basic, tests/vgem_slow and tests/vgem_reload_basic (Chris Wilson) - Various fixes to tests/kms_frontbuffer_tracking: prefer BLT drawing, recreate FBS at every subtest and properly handle mixing GTT and WC mmaps (Paulo Zanoni) - Replace drv_missed_irq_hang script with a C-equivalent: tests/drv_missed_irq (Chris Wilson) - Added a test case for polling dma-buf fences: tests/prime_busy (Chris Wilson) - lib/igt_gt: Omit illegal instruction on gen8+ and time constrains on hang detection (igt/gem_reset_stats) (Mika Kuoppala) - Added tests/kms_invalid_dotclock, a test that makes sure every modeset gets rejected by the kernel if the requested dotclock is beyond the hardware capabilities (Ville Syrj�l�) - tests/gem_stolen: Verify contents of stolen-backed objects across hibernation, fix for no_mmap subtest and check for available stolen memory size (Ankitprasad Sharma) - tests/core_prop_blob: Add invalid tests to set fb props (Daniel Vetter) - Many more fixes and improvements. ==== libXfont ==== Version update (1.5.1 -> 1.5.2) Subpackages: libXfont-devel libXfont1 - Update to release 1.5.2 Maintenance branch release, primarily for bdftopcf's benefit as it's the only thing that really needs the Xfont1 API. (xfs uses it too, I believe, but could be ported to Xfont2). If someone wanted to step up and merge Xfont1 into bdtopcf directly, that'd be great. - supersedes U_bdfReadCharacters-Allow-negative-DWIDTH-values.patch ==== patterns-openSUSE ==== Subpackages: patterns-openSUSE-apparmor patterns-openSUSE-apparmor_opt patterns-openSUSE-base patterns-openSUSE-books patterns-openSUSE-console patterns-openSUSE-devel_C_C++ patterns-openSUSE-devel_basis patterns-openSUSE-devel_gnome patterns-openSUSE-devel_ide patterns-openSUSE-devel_java patterns-openSUSE-devel_kde patterns-openSUSE-devel_kde_frameworks patterns-openSUSE-devel_kernel patterns-openSUSE-devel_osc_build patterns-openSUSE-devel_perl patterns-openSUSE-devel_python patterns-openSUSE-devel_qt4 patterns-openSUSE-devel_qt5 patterns-openSUSE-devel_rpm_build patterns-openSUSE-devel_ruby patterns-openSUSE-devel_web patterns-openSUSE-dhcp_dns_server patterns-openSUSE-directory_server patterns-openSUSE-enhanced_base patterns-openSUSE-enhanced_base_opt patterns-openSUSE-file_server patterns-openSUSE-fonts patterns-openSUSE-fonts_opt patterns-openSUSE-games patterns-openSUSE-gateway_server patterns-openSUSE-generic_server patterns-openSUSE-gnome patterns-openSUSE-gnome_admin patte rns-openSUSE-gnome_basis patterns-openSUSE-gnome_basis_opt patterns-openSUSE-gnome_games patterns-openSUSE-gnome_ide patterns-openSUSE-gnome_imaging patterns-openSUSE-gnome_imaging_opt patterns-openSUSE-gnome_internet patterns-openSUSE-gnome_laptop patterns-openSUSE-gnome_multimedia patterns-openSUSE-gnome_multimedia_opt patterns-openSUSE-gnome_office patterns-openSUSE-gnome_office_opt patterns-openSUSE-gnome_utilities patterns-openSUSE-gnome_yast patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-kde patterns-openSUSE-kde_edutainment patterns-openSUSE-kde_games patterns-openSUSE-kde_ide patterns-openSUSE-kde_imaging patterns-openSUSE-kde_internet patterns-openSUSE-kde_multimedia patterns-openSUSE-kde_office patterns-openSUSE-kde_plasma patterns-openSUSE-kde_telepathy patterns-openSUSE-kde_utilities patterns-openSUSE-kde_utilities_opt patterns-openSUSE-kde_yast patterns-openSUSE-kvm_server patterns-openSUSE-lamp_server patterns-openSUSE-laptop patterns-openSUS E-lxde patterns-openSUSE-lxde_laptop patterns-openSUSE-lxde_office patterns-openSUSE-mail_server patterns-openSUSE-minimal_base patterns-openSUSE-minimal_base-conflicts patterns-openSUSE-misc_server patterns-openSUSE-multimedia patterns-openSUSE-multimedia_opt patterns-openSUSE-network_admin patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-office patterns-openSUSE-office_opt patterns-openSUSE-print_server patterns-openSUSE-remote_desktop patterns-openSUSE-rest_dvd patterns-openSUSE-sw_management patterns-openSUSE-sw_management_gnome patterns-openSUSE-sw_management_kde patterns-openSUSE-tabletpc patterns-openSUSE-technical_writing patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-x11_yast patterns-openSUSE-xen_server patterns-openSUSE-xfce patterns-openSUSE-xfce_basis patterns-openSUSE-xfce_laptop patterns-openSUSE-xfce_office patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf - Update GNOME pattern to be more in line with the GNOME Core application recommendations: + brasero: only suggested instead of recommended. Writing optical media is no longer the 'standard'. By suggesting it, we ensure the programs stays on the media though. + gnome-clocks and gnome-logs: newly recommended tools. - Demote libreoffice-base-extenstions from Recommends to Suggests: we already don't explicitly recommend Base (which also does not make much sense for most users) - so the extensions make even less sense. Keeping it as suggests ensures it still ends up on the media though. - Added kdebase4-workspace-libs Recommend to the kde_plasma pattern so qt4 apps use the breeze style instead of depending on indirect requirements to install that package. ==== perl-Apache-AuthCookie ==== Version update (3.24 -> 3.25) - updated to 3.25 see /usr/share/doc/packages/perl-Apache-AuthCookie/Changes 3.25 2016-08-30 - 2.4: fix POD typo and add missing ABSTRACT - reorganize real.t tests into subtests - make sure signature test ignores generated files - remove autobox dependency - fix authenticate so that r->user is copied from r->main on subrequests. Previously this was only done for internal redirects (r->prev is defined). This fixes DirectoryIndexes on AuthCookie enabled directories under apache 2.4. ==== perl-MIME-tools ==== Version update (5.507 -> 5.508) - updated to 5.508 see /usr/share/doc/packages/perl-MIME-tools/ChangeLog 5.508 2016-08-29 Dianne Skoll <dfs(a)roaringpenguin.com> * VERSION 5.508 RELEASED * Fix test broken by Perl update https://rt.cpan.org/Ticket/Display.html?id=113887 ==== perl-Moose ==== Version update (2.1804 -> 2.1805) - updated to 2.1805 see /usr/share/doc/packages/perl-Moose/Changes 2.1805 2016-08-19 [BUG FIXES] - remove inc/Config.pm that should not have appeared in the distribution (an issue since 2.1800; RT#117071) ==== perl-Sub-Exporter-Progressive ==== Version update (0.001011 -> 0.001012) - updated to 0.001012 see /usr/share/doc/packages/perl-Sub-Exporter-Progressive/Changes Revision history for Sub-Exporter-Progressive 0.001012 2016-08-23 11:18:21-07:00 America/Los_Angeles - Many small performance improvements (Peter Rabbitson) ==== xf86-video-nouveau ==== Version update (1.0.12 -> 1.0.13) - Update to version 1.0.13: New Nouveau ddx release. Included in this release are fixes for reverse prime and the upcoming XServer 1.19. ==== xorriso ==== Version update (1.4.4 -> 1.4.6) - xorriso 1.4.6: * Bug fix: The default setting of -compliance did not apply rec_mtime to Joliet and ISO:1999. mkisofs emulation was not affected by this bug. * Bug fix: -file_size_limit did not increase ISO level if necessary. * New API calls isoburn_igopt_set_gpt_guid(), isoburn_igopt_get_gpt_guid() * New command -use_immed_bit, new -as cdrecord option use_immed_bit= * New -volume_date mode "all_file_dates" * New -as mkisofs option --set_all_file_dates * New bootspec "gpt_disk_guid=", new -as mkisofs option - -gpt_disk_guid * New -report_system_area modes "gpt_disk_guid", "make_guid" * New environment variable SOURCE_DATE_EPOCH * New -find action "set_to_mtime" - xorriso 1.4.4: * -as mkisofs did not unescape "\=" in the source part of pathspecs * -boot_image "any" "system_area=/dev/zero" did not zeroize loaded data * -pathspecs "on" did not properly handle "\\=" * HFS+ production could cause MBR partition of type 0xEE without GPT * HFS+ directories could announce more children than they actually have * The HFS+ filesystem was not marked by in GPT of GRUB2 hybrid layout * When reading an ISO filesystem, the presence of - -protective-msdos-label was not recognized if a partition is appended * Bug fix: xorrisofs option --protective-msdos-label did not work if no system area data were given by option -G or alike * -modesty_on_drive properties timeout_sec, min_usec, max_usec read wrong numbers from the parameter text * Letting -as mkisofs --norock revoke the special effect of -r * Letting -blank on overwritable media invalidate UDF extended descriptors * New -pathspecs mode "as_mkisofs" * New -boot_image setting mbr_force_bootable=, -as mkisofs - -mbr-force-bootable * New -boot_image bootspecs appended_part_as=apm, part_like_isohybrid=on * New -as mkisofs options -appended_part_as_apm, - part_like_isohybrid * New command -scsi_dev_family, new -as cdrecord option drive_scsi_dev_family= - Update to 1.4.2: * Bug fix: -backslash_codes "on" did not work outside quotes and with showing "\r" * New API calls isoburn_ropt_set_truncate_mode() isoburn_ropt_get_truncate_mode() * New options with isoburn_ropt_set_extensions(): isoburn_ropt_map_* * New command -modesty_on_drive, new -as cdrecord -immed, minbuf=, modesty_on_drive= * New command -ecma119_map * New command -read_fs * New -boot_image action "replay" * New command -file_name_limit, -as mkisofs -file_name_limit * New -find test -name_limit_blocker. * Result of a Coverity audit: 50+ code changes, but no easy-to-trigger bugs - includes changes from 1.4.0: * Bug fix: -dev or -indev of medium with non-ISO data caused SIGSEGV by NULL * New API calls isoburn_igopt_set_appended_as_gpt(), isoburn_igopt_get_appended_as_gpt() * New API call isoburn_igopt_set_part_flag() and libisofs interval reader flags * New -find action "show_stream_id" * Optional libisofs interval reader with -append_partition and System Area * New -boot_image bootspec "appended_part_as=", new -as mkisofs option -appended_part_as_gpt * New -report_system_area formats "cmd" and "as_mkisofs" * verify source signature - Update to 1.3.8 Bug fixes towards previous stable version xorriso-1.6.pl01: * -boot_image grub2_mbr= prevented -boot_image partition_table=on * A final fsync(2) was performed with stdio drives, even if - stdio_sync was set to "off". * -boot_image grub grub2_mbr= did not work (but -as mkisofs - -grub2-mbr did work) * Wrong stack usage caused SIGBUS on sparc when compiled by gcc -O2 * -blank force:all on DVD+RW had no effect Enhancements towards previous stable version xorriso-1.3.6.pl01: * New bootspecs hppa_*, new -as mkisofs options -hppa-* for HP-PA via PALO * New -find pseudo tests -use_pattern , -or_use_pattern * New -find action report_sections * New command -concat * New commands -report_system_area and -report_el_torito * Enabled use of libedit as alternative to libreadline * Enabled recording and restoring of extattr on NetBSD - Update to 1.3.6.pl01: Bug fixes towards previous stable version xorriso-1.3.4: * Division by zero if HFS+ was combined with TOC emulation for overwritable media. * -list_speeds did not work any more with old CD drives. Regression introduced by release 1.3.4 * -check_media marked untested sectors in sector map as valid * Paths with symbolic links preceding ".." were not interpreted properly Bug fixes in xorriso-1.3.6.pl01 towards xorriso-1.3.6: * Command -status produced FAILURE event if no drive was acquired. Regression introduced by release 1.3.6 * Compilation warning for unsupported systems mutated into an error. Regression introduced by release 1.3.6 * CD TAO with add-on sessions could cause a buffer overrun. Introduced 7 years ago by release 0.3.2. Enhancements: * New -compliance rule joliet_utf16, new -as mkisofs option -joliet-utf16 * New -find test -bad_outname, new -find action print_outname * New capability to operate optical drives and media on NetBSD - Update to 1.3.4: Bug fixes: * Command -blank "as_needed" formatted blank BD-R. * -as mkisofs option -log-file put the log file into the image * -cut_out did not add x-permission to r-permission of directory * Command -zisofs did not accept all options emitted by -status -zisofs * blank force:... failed on appendable or closed media * Drive LG BH16NS40 stalled on inspection of unformatted DVD+RW Enhancements: * Default sort weight of El Torito boot images is now 2 * Encoding HFS+ names in UTF-16 rather than UCS-2 * New command -read_speed * New -close mode "as_needed", new -as cdrecord option --multi_if_possible * New -alter_date types: a-c , m-c , b-c , c - update to 1.3.2: * Bugfixes: + readline history was spammed by -msg_op parsing and pipe loops + xorriso aborted on SIGCONT, SIGTSTP, SIGTTIN, SIGTTOU * Features: + improved granularity of SCSI log time measurement, now with timestamp + -pacifier behavior code "interval=" + -as mkisofs options --sort-weight-list and --sort-weight-patterns + -format mode "without_spare" (for BD-RE) + new command -named_pipe_loop + new command -sh_style_result + new -msg_op opcodes "parse_silently" and "parse_bulk_silently" + new command -application_use and new -as mkisofs option --application_use - Update to 1.3.0: Bug fixes: * Disk paths with components '.' or '..' could be mistaken for directories. * -as mkisofs -print-size failed with -isohybrid-mbr and a single boot image. * -as mkisofs -path-list did not switch to --no-emul-toc by default. * Reserved and unused fields of APM entries were not zeroed. * Unspecified Expiration Time and Effective Time of ISO volume was represented by 0-bytes rather than ASCII '0' digits. * GPT header CRC was computed from all 512 bytes rather than from 92. * The protective MBR partition for GPT started at block 0 instead of 1. Enhancements: * New -boot_image bootspecs grub2_mbr= and grub2_boot_info= * New -boot_image bootspec grub2_sparc_core= * New -as mkisofs options --grub2-mbr , --grub2-boot-info , - -grub2-sparc-core * New -hardlinks mode "lsl_count" / "no_lsl_count" - Added libbz2-devel as build requirement. - update to 1.2.8: * Bug fix: -tell_media_space altered the pointers to MD5 of data files which stem from a previous session. This produced false mismatches with -check_md5_r. * Bug fix: CD tracks were reported with the sizes of the tracks in the first session. * Bug fix: -check_media use=outdev sector_map= stored TOC of input drive * Bug fix: -hide hfsplus and -as mkisofs -hide-hfsplus had no effect. * New command -move * New -as mkisofs options -eltorito-id , -eltorito-selcrit - Update to 1.2.6: Bug fixes: * SIGSEGV by uninitialized local variable with -check_media patch_lba0="on". Regression by version 1.0.6 * -partition_offset 16 kept -isohybrid-gpt-basdat from writing MBR entries 0xef * -rollback did not work if indev and outdev were empty Enhancements: * New -boot_image partition_cyl_align mode "all" * New -blank mode prefix "force:" * New -osirrox settings "blocked" and "unblock" * New command -lns for creating symbolic links * New command -toc_of * New command -msg_op * New command -launch_frontend * Proof-of-concept of a GUI frontend program: xorriso-tcltk written in Tcl/Tk. - Removed %debug_package (not needed). - Added new xorriso-tcltk subpackage. - update to 1.2.4: * New API call isoburn_igopt_set_hfsp_serial_number() * New API calls isoburn_igopt_set_prep_partition, isoburn_igopt_set_efi_bootp * New API calls isoburn_igopt_set_hfsp_block_size() and isoburn_igopt_get_hfsp_block_size() * New -check_media option async_chunks= * New xorriso command -write_type * New xorriso command -rockridge * New xorriso command -hfsplus * New -find tests -has_hfs_crtp, has_hfs_bless * New -find actions set/get_hfs_crtp, set/get_hfs_bless * New -find test -disk_path * New -boot_image bootspec hfsplus_serial= * New -boot_image bootspecs hfsplus_block_size= and apm_block_size= * New -boot_image bootspecs efi_boot_part, prep_boot_part, chrp_boot_part * Command -hide allows hiding in HFS+ filesystem * New -as cdrecord options -tao -sao -dao * New -as mkisofs option -log-file * New -as mkisofs option --norock * New -as mkisofs option -hfsplus * New -as mkisofs option -hfsplus-file-creator-type * New -as mkisofs options -hfs-bless and -hfs-bless-by * New -as mkisofs option -hfsplus-serial-no * New -as mkisofs options -hfsplus-block-size and -apm-block-size * New -as mkisofs option -hide-hfsplus, -hide-hfsplus-list * New -as mkisofs options -prep-boot-part, -efi-boot-part, -chrp-boot-part * New -as mkisofs options -isohybrid-gpt-basdat, -isohybrid-gpt-hfsplus, - isohybrid-apm-hfsplus * Bug fix: Memory corruption when reading bootable image that was truncated * Bug fix: -update deleted MD5 of files of which only attributes had changed - update to 1.2.2: * new commands -x, -list_arg_sorting * new command -rr_reloc_dir * new command -data_cache_size * new -as mkisofs option -rr_reloc, implemented option -hide-rr-moved * now ignoring -as mkisofs -no-split-symlink-components - no-split-symlink-fields * bug fix: -osirrox on:sort_lba_on -extract from / restored nearly nothing * bug fix: -as mkisofs without -graft-points could not handle names with "=" * bug fix: relaxation options joliet_rec_mtime and iso1999_rec_mtime had wrong values - update to 1.2.0: Bug fixes: * mkisofs emulation did not record mtime in ECMA-119 directories * Program abort while drive tray is loading led to endless loop * Solaris adapter mishandled write commands which failed on first try * libisoburn.ver had a duplicate function entry Enhancements: * New relaxations isoburn_igopt_joliet_rec_mtime, isoburn_igopt_iso1999_rec_mtime * Made -compliance "rec_mtime" default - Spec file updates: * Changes based on spec-cleaner run. * Changed License: to GPL-3.0+ (SPDX style). * Added libacl-devel and zlib-devel in BuildRequires: (used by libisofs). * Removed libstdc++-devel, ncurses-devel, gcc, make, glibc-devel, autoconf, automake, libtool from BuildRequires: (not needed). * Require "info" package for preun instead of postun. * Added missing %changelog section. - update to 1.1.8: * intermediate opening and closing of of drive device files is now avoided * xorriso operates on QEMU DVD-ROM and on qemu virtio-blk-pci devices * emulation mode xorrecord now has its own man page and info document - update to 1.1.6: * bugs were fixed in processing of ACLs * vanishing udev links on GNU/Linux no longer disturb ongoing burn runs - update to 1.1.4: * an old bug could cause xorriso to prepare incorrect internal addresses, this happened only with some CD drives and never in mkisofs emulation mode * the new option -device_links shall be used on modern GNU/Linux systems instead of the option -devices: it lists the drives by their usual udev links rather than by their kernel device addresses - update to 1.1.2: * a severe regression was fixed, which was introduced with version 1.0.6: it caused ISO 9660 images to be unreadable if they were written to a write-only random-access file - update to 1.0.8: * a bug in the mkisofs emulation of xorriso could cause options to be ignored; the problem was freshly introduced with GNU xorriso-1.0.6 - update to 1.0.6: * allows Joliet names of up to 103 characters * burns DVD-R DAO sessions with 2 kB size granularity rather than 32 kB - update to 1.0.4: * fixes several bugs in its mkisofs emulation * the emulation (xorrisofs) has its own man page and info document - changes from 1.0.2: * several bugs were fixed * it is now possible to copy files inside an ISO image * emulation of mkisofs has been improved - update to 1.0.0: * now allows you to create an ISO 9660:1999 directory tree * the emulation fidelity of the "-as mkisofs" command was improved * the default abort threshold for batch mode was lowered, and that threshold was increased for dialog mode * the version number took a leap to 1.0.0 in order to emphasize the maturity of the software - update to 0.6.6: * can now read ISO images that were copied to a different start address than the address for which they were prepared * now possible to produce bootable images for SUN SPARC systems - update to 0.6.4: * adds upcoming libjte, which produces Jigdo files along with the ISO image * further filesystem images may be appended as MBR partitions 1 to 4: the capability was added to produce boot blocks for computers with MIPS CPUs - update to 0.6.2: * introduces a partition with non-zero offset for ISO 9660 images on USB sticks * improves mkisofs emulation * fixes a regression that existed since version 0.4.2 - update to 0.6.0: * adds more options to the mkisofs emulation * fixes minor bugs and shortcomings - update to 0.5.8: * enhances the emulations of mkisofs and cdrecord - removed xorriso-fix_buffer_overflow.patch (merged upstream) - update to 0.5.6: * provides new boot preparation features requested by GRUB development - update to 0.5.4: * add support for future versions of the GRUB script grub-mkrescue * follows a request of Syslinux to not use the deprecated built-in ISOLINUX MBR of libisofs any more - changes from 0.5.2: * documentation in Texinfo format - update to 0.5.0: * now an official GNU project * license is now GPLv3+ * some bug fixes - update to 0.4.8pl01: * fixes a regression where the -boot_image option could lead to a SIGSEGV - update to 0.4.8: * bugfixes for libburn and libisofs - update to 0.4.6: * fixes a bug with the LG GH22LS30 drive * allows performance tuning of output to DVD drives or disk files - update to 0.4.4pl1: * works around problems with Pioneer DVR-216D: DVD-R runs made the drive stick until the machine was power cycled and ejecting the tray did not work properly - update to 0.4.4: * fixes a bug with cdrecord emulation * introduces new information options about media type and ISO image id strings * helps with mounting two sessions of the same media simultaneously - update to 0.4.2.pl02: * fixes a bug that could cause loss of blanks in file names when a new session was added to an ISO image; With names shorter than 251 characters, this happened only to trailing blanks - update to 0.4.2.pl01: * fixes a bug with the xorriso option -cut_out that deleted previously cut pieces of the same large file - update to 0.4.2: * record MD5 checksums for the whole session and for each single data file * one may verify data file content in the image * when comparing image files with files in the local filesystem, the MD5 sums avoid the need for reading file content from the image - update to 0.4.0pl01: * when using recent releases of xorriso underneath growisofs, it did not maintain the files from the older sessions; this is a regression which appeared with version 0.3.2 in January 2009; it does not affect the main use case where xorriso does the burning by itself - update to 0.4.0: * this release can record and restore hard link relations of files * performance of data reading has been improved * the test expression of option -find now supports logical operators * some rarely occurring bugs have been fixed - bzipped sources - update to 0.3.8: * makes use of the new libisofs capability to perform content filtering of data files * builtin filters allow compression to the gzip and zisofs formats * external filter processes allow arbitrary data conversions like encryption - update to 0.3.6 - update to 0.3.4: * xorriso now can record ACLs and Extended Attributes in its ISO images ==== xproto ==== Version update (7.0.29 -> 7.0.31) - Update to version 7.0.31: The update to version 7.0.30 is included + Xfuncproto.h: Define __has_feature(), __has_extension() + Xfuncproto: Add support for _X_DEPRECATED_MSG(), _X_NOTSAN macro + Fix typo __has_extenstion -> __has_extension -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] 42.2 Beta 2 bug assigned to Novell ?
by Roger Price 27 Sep '16

27 Sep '16

I filed a bug report: 1001276. It was assigned to bnc-team-screening(a)forge.provo.novell.com It is possible that openSUSE 42.2 bug management is more subtle than I imagined, but I had understood that Novell was no longer the owner of Suse and no longer had any responsibility for Suse. I assume that since Novell is in no way responsible, they will do nothing about 1001276. Roger -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 4

Re: [opensuse-factory] 42.2 beta1 safe for daily use security wise?
by stakanov＠freenet.de 27 Sep '16

27 Sep '16

> -----Ursprüngliche Nachricht----- > Von: cagsm > Gesendet: Di. 27.09.2016 11:30 is it now safe or advised to add the update repo when using > leap 42.2 beta2 and onwards? > >" target="_blank">http://download.opensuse.org/update/leap/42.2/oss/> > > how about the other nify security problems we see daily in the > software world? openssl and such comes to my mind? > > -----Ursprüngliche Nachricht Ende----- I am a bit puzzled why you post this (what I would feel belong to "general knowledge of software" and therefore to opensuse(a)opensuse.org) here in the developers forum. To get you an answer on the "security problem": This is beta software. This warning is displayed several time during install to you. Wikipedia states about betasoftware: Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. Unknown bugs are intrinsically unsafe and may lead to security problems and / or data loss. This is fairly easy to understand. You have a productive system that serves to you as a bread-giver in you daily activity: you do not use beta software. You have security requirements that come down to: be always patched and have save practice ... you do not use beta software. You are somebody who decides to contribute to others and want to find security and other bugs and report them, while running either a virtualized system without vital data or the full OS on a spare computer where you just try out whether migration of you old system "would" work and if your usual requirements for safe work are met: then you do(!) use and install a beta version. If you do not know how to file a bug report and/or you do not have a spare system I would really advice (IMO) NOT to use any beta. And to wait up to 6 month after release to get the most stable experience. There is a world of difference between running beta and stable. So also: if you use beta, even for testing, you always, even more than usual, make a backup(!) of ALL your data BEFORE you start. And I really think you should post these kind of questions to opensuse(a)opensuse.org where they seem fitting. YMMV, of course. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0