Package: deb-perl-macros Version: 0.1-1.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-1.2_all.deb Size: 2700 MD5sum: 1825c2aff78ae19d8ed1e0d4a45bdc30 SHA1: 6b0f5a23f051ab365124b8556e47a963026a4cc0 SHA256: 34f5b869991208242214e1e4d312058c3a6acfad4938651bd4483ed967b07897 Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-1.2 Architecture: all Maintainer: debbuild developers Installed-Size: 209 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_24.12.0-1.2_all.deb Size: 55160 MD5sum: 6977c4e0e97f68e5fbe79da1c6efb405 SHA1: 1d9eb3bea8f65dc95e36859364fe403e8ec2dc06 SHA256: 37b6c730349ed9f44e1cc21fa76dbf485e9cb1898662c3cf7c7167533d3bd5df Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-1.2 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-1.2),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-1.2_all.deb Size: 8624 MD5sum: 0db78a851530df347b2a0bc37e841ca8 SHA1: 6ce1210fee303d555574655289d384a70c4564e0 SHA256: 4d22ae816ffd9678d0dc9692e82b3febe35cecb10f9bc4a6961d8e3e8914491e Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.8-1.1 Architecture: all Maintainer: debbuild developers Installed-Size: 126 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.8-1.1_all.deb Size: 25536 MD5sum: 8e12a99bf04e34e3d1482eae15799ff6 SHA1: e9016432b311d523652718b705896e0c63e32495 SHA256: 2df74971e5e346698c935e9436be542c7ef7f7165859d8a0c5c27b31031e2e93 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 355 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: s390x/liblua5-1-5_5.1.5-1.1_s390x.deb Size: 74644 MD5sum: 29ad87bc487de0c48067c7c31c0269b2 SHA1: 5cf9b31ef31cec1a4e68b5fbdf904d1762249ab4 SHA256: 8bdbfea4bd204f3d8464a6f67b2333a390d96da968c2659d2c6700777341e07f Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 745 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: armhf/liblua5-1-5_5.1.5-1.1_armhf.deb Size: 281944 MD5sum: 8a2781beff5a76159add3b8df74134bc SHA1: d82cdf437199733afe97d038e9f9315504c47f30 SHA256: 3192fe6e962d430934dc9b8b1bf16753afceb97997e251a90197e8c82b9aa15f Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 858 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: arm64/liblua5-1-5_5.1.5-1.1_arm64.deb Size: 294308 MD5sum: fc36da760a143a28899aa45bd4f7e3c6 SHA1: 4a0a6693d718f076e1692838849c8299a953321c SHA256: d16f06dffb3a33f751459a978437bb9706f42f756e6a3b169586e49ad5e0c3d9 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 853 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: amd64/liblua5-1-5_5.1.5-1.1_amd64.deb Size: 307428 MD5sum: 4eddc0a9aea897b030e9dcdde365fb55 SHA1: a20384883ba9795dbc1dca0b95d8fee6b3b2099a SHA256: bfd6c1fa36ed923d70cde39da3eb394bc2befa9524283280cae1e3d8f0d7c635 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 800 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: i386/liblua5-1-5_5.1.5-1.1_i386.deb Size: 305632 MD5sum: c64d7e69a7de4b050525b67c05a37304 SHA1: 0805c52eca843441d566ce3aacd42026020d060e SHA256: ef5696ca1c2086ce1adaa6e2db21c9c44ba6b03613f1d075433db7e60d5673c5 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: pkg-config Filename: all/lua-macros_20210827-1.1_all.deb Size: 2812 MD5sum: 1984a5fb8c02ba957a13f57281b38aa3 SHA1: 4fd868705fad1ff32ad2ebe8fb26a1623a3c1b60 SHA256: 0e187281e2d1e27c595f6d059c2cbab7c743fc2b90657f4f87e0b95266912383 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 600 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-1.1_s390x.deb Size: 90048 MD5sum: 4b31eda6bf2b7707732e64fda0cf1f8e SHA1: 86c3eb466329f2eaedb24834c2b95279e06512f5 SHA256: 3e27e4ec62402a41f99bc0a1baecda9245c8cd1e0cde4f953c3e2b8a91106b94 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1310 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-1.1_armhf.deb Size: 345072 MD5sum: 82edd02075d84ef550550d3188a2ec43 SHA1: d2d9aa2a0ead9f80aaf0a99a1e3b458ad85798ee SHA256: a3ca92aa4f4b172011a0cd2b9ffe5ee4e4f99d12e88c280101fb2087dda38cbb Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1506 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-1.1_arm64.deb Size: 360128 MD5sum: 8fcb81cbe325882116c0fe69d7051b7a SHA1: ba5355ffe9c8ea3d7c9fc81eff8c1c1555abed67 SHA256: 9dea4a5e7b6517efed60a1b68db03b9d7524d2c4592e418d94f38d371b2c48a1 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1485 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-1.1_amd64.deb Size: 376852 MD5sum: fa58eab566835b8da956951d09ae68c6 SHA1: c1f7d1fdbe36045e89265384a4d6d5ebd442c29f SHA256: c5d46363c79623851b3a1941f70c58a02424652fee363b6770462c069ff65b7b Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1405 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: i386/lua51_5.1.5-1.1_i386.deb Size: 374112 MD5sum: cd8c008b3ae1a21eff56d11c05cdc424 SHA1: de620474b992c232c2cbedd94d1b7011a8e20ae1 SHA256: 7b49c1bf439125e642b797726a6f51aa8746adeb5ff9b68119ecb0f28a72d53f Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 557 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: s390x/lua51-devel_5.1.5-1.1_s390x.deb Size: 90232 MD5sum: 042b55da0ee2145cbecedf39eb13adce SHA1: c165517ee33553c7b1661cf82ad3d5244158408d SHA256: 3f33a9de29b4f75c8ce0f4484a19c9b94d0bc65b9ca5213e555638b871133454 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1105 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: armhf/lua51-devel_5.1.5-1.1_armhf.deb Size: 356304 MD5sum: 05fbfe68c0adbc2051faa4e8aa05c00c SHA1: 430d725b540c90c9b4f48b340cd4924947703d69 SHA256: f5d590f367506598eb45c94f0e05633799b4a01c51b5d57ee927362467f2c148 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1658 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: arm64/lua51-devel_5.1.5-1.1_arm64.deb Size: 372408 MD5sum: ed3a1fbb5a39067e6427a1ba29a4a886 SHA1: 3f1cb9c7ddf006184f58af8f54e5971a9ce473a6 SHA256: cadba26f1f0dd84575662c933ae7d13b6cd175fadbb55909ed0a3336f4002178 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1681 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: amd64/lua51-devel_5.1.5-1.1_amd64.deb Size: 383264 MD5sum: f6656b35d600644d34fd180bac2cf061 SHA1: b4bb6bb5f7f82a72b11ca0ec1ca871b4827f1abb SHA256: 1e806ea79123b7499aeac211b16add3c386859f2eea3bcdca27f07ff65ad63be Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1185 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: i386/lua51-devel_5.1.5-1.1_i386.deb Size: 381908 MD5sum: 426b4995f7a589fcdb5a94b4f26db4a2 SHA1: e27c8165386375f10a563a38735b1bcb318e92a7 SHA256: 4243a8d1d7cd6d95d33cbb6e4333616caceed26d7fb423345eb580c54eb105d0 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-1.1_all.deb Size: 71684 MD5sum: 6fd35ead06693de5b0ae73477a15e31a SHA1: c52e1c3640480b44250cd56582ac6050c41a0469 SHA256: 273aec46e2e2bc6ee5ee651f5c513be97ba815178a9d8cffd0dea54b37b60082 Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-1.1_all.deb Size: 30012 MD5sum: 419e29e1ed63d6e8958e154302679e7f SHA1: ccbd2c9f42b15eddfb1fac591dcaba44439d6eeb SHA256: 951ffd0280e6e52f496ed8aced1e147da4e63a58ad4da71e554fc047b3af71b9 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-1.1_all.deb Size: 22668 MD5sum: eb0ae084080a4c9a5de84bc127bb3dc5 SHA1: df00aca73ac8f53c9adbd2208be5e7ee1ac6ce3b SHA256: c138b87d95414e0e433b9e9caa28e7f04b01cdbf67d3d46a1340f3a7093bfe69 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-1.1_all.deb Size: 7232 MD5sum: e3311324a7725b4596fdc2fce2b21ca3 SHA1: 24035cebab4fb3dfafedd2f60b24c95fdab80485 SHA256: 2a01c7ebf4839cea7b84c5fb94cbf6f0f08ccfbb65517cbbf0f1db36a525dc05 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-1.1_all.deb Size: 28396 MD5sum: b09807aec26afab30ef06597b0f34156 SHA1: 2a3f7ba528bc5c0593a91f6102ad19865ebb7903 SHA256: 4e673f294546956e91729ce537104010ff954ea7a9343d9d4ba63eac7decfaa6 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-1.1_all.deb Size: 14372 MD5sum: 28ebe7a6fdc5ac0495ccb81f5d175a45 SHA1: 19508003e85beb21e6cce9572c91ef739216438f SHA256: ece665241e16bd36bcd1aa37349e9430ca1705abbd0a28c3a6e2b08fb844477b Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-1.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-1.5_all.deb Size: 39044 MD5sum: 419d4b6423d0a9b87d46a2b245e5bff5 SHA1: 3563c4f69eb2b07d259dd6ab5b9b4b8f46712e17 SHA256: c8050cf54cc2e7f083ac32ec31c6c4dd9b0de02b253b0df19c1c560ffb5bb90b Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-1.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-1.5_all.deb Size: 39244 MD5sum: 4e2e9309f884ded2c17a1dcedbcb0078 SHA1: 5a969c3ebeca22f957c677ebe94e073024bfdc9f SHA256: 33b7672801af11cc77a0c190a6a3f4cf79287be90f23913e88dd99391a650919 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-1.1_all.deb Size: 304420 MD5sum: 7ec53a32ae8fc5bbfaf59e8abf535914 SHA1: 3ea2a9f4800e212736e858a329d7e32355fbde71 SHA256: ba8ac8b3b47ba1f7e5d5f6421cd26375670f130915bb84c9b1b875659478e573 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-1.1) Filename: all/perl-extutils-pkgconfig_1.160000-1.1_all.deb Size: 10552 MD5sum: 233dfd02aa4aafed6e7049e557260b6f SHA1: 78d6f7205df2e3042556cacaa567e4fa43809f3e SHA256: 2da9b2b72ea9e91d759212e65b86df749469221abd71e5e4741fa00e1022d490 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-1.1) Filename: all/perl-file-path_2.180000-1.1_all.deb Size: 30668 MD5sum: bef9801853a878d8a7bf87361540f57a SHA1: 980bf0544dc3465f1166d74025cd17430c384d8c SHA256: 04bd1c26af9f40b12313fd849f8f3a9b21d530bd80615fc4d39ac00fae437e4e Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-1.1_all.deb Size: 53284 MD5sum: f78a37985b4880ba7b1ac275b955d4e9 SHA1: 591e6f7348d824d788a90d3c13b60c63856ecd33 SHA256: 4d407380bedb36b8f39f21543dea3bf7318065d487b32e0826fa314199733fa1 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-1.1_all.deb Size: 33144 MD5sum: cd0d6329e3225a8044def9feef28e296 SHA1: e4317c60b2f605f80e3faadc6dd1b1d34c955334 SHA256: 9f249827459acd2c2fcb8f0c2a54c131cb6e5ac732aff2534b0d6750df6345b1 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-1.19 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-1.19_s390x.deb Size: 168000 MD5sum: 7db15e691a9f9425e3a3c72ef0583a3c SHA1: cd22d0cc2e8d2d76db59386957e6a6de3bfa20ff SHA256: 46cb58ff4af4a5ed7ac40c0a2a2ec02a2e5bacdd76d79b924dc73863f57294c3 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-1.19 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-1.19_armhf.deb Size: 169992 MD5sum: 7363aa41b021048b4ac77de4217937ea SHA1: 6ee37ad0499d9877b3d5c4357ef4001606f27c67 SHA256: 1d94bebfefd3135f5989146daa58024ede706fc4f7d52fc6074a0ce04771dd0b Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-1.19 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-1.19_arm64.deb Size: 167332 MD5sum: 70043d06c7fd3bbc6e72e86475438b88 SHA1: 063da50c9db8a6f7d87aade210936933188ca9b3 SHA256: 109cb24abf141bc0db928c9b2145135c3140861b1154294253aed286804b0f05 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-1.19 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-1.19_amd64.deb Size: 173732 MD5sum: 125600d355066ed1050f65bc2d2ad40a SHA1: 89ad7f673865e70d4d091537510a874f74608d7b SHA256: 7d4802010893f845656bba0009710986e9cd976c7cbf1ef9f73394de13c59f88 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-1.19 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-1.19_i386.deb Size: 162936 MD5sum: 2148407c45cb044552eeacad40c1b228 SHA1: 71778afaf00400b5b93b8fd74fd86a15cfcb0a7b SHA256: 4952ea65d386feff7ebb9cabb191608c2387fd2d6f1b62ccdee8e39012d72fce Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-1.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 733 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423400-1.7) Filename: all/perl-module-build_0.423400-1.7_all.deb Size: 251180 MD5sum: be6b3f9c2de0042f09402d2586131ef5 SHA1: 61ba53ecd60fc1acfcb1e27779c2a83b135ddffa SHA256: 7cc9c6df49699e350a2a782d86229cd7be86bac08e076bfb0a342ac2f8274857 Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-1.1_all.deb Size: 29644 MD5sum: ec20dab55356b5d60e65c8effb8f00ae SHA1: 356b1b30ee36e07314f9d802d3a3db983cea1409 SHA256: 12135f08f71e194d7ff9a41a9a637dc00c79fe380a22174cb5507e3969688c72 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-1.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-1.12_all.deb Size: 18444 MD5sum: f3b69146cd528fe027b0e2f48a3955bb SHA1: 9994305294c400ab533af5f3aead57f71c3a8d7e SHA256: 6af1e6edc12df7a9c695edcecd0bffc23691cf4b218f4695fe83d1c739256577 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-1.1_all.deb Size: 17200 MD5sum: 104334a2e16cd1b7bce4292ad9f8401b SHA1: 2e19d88554e5772218403e1a17f9fc1b1765050e SHA256: bcdfbbb4955f12cd928df14297532924f018ee485a4aaa9bf1e3b003cf193310 Priority: optional Homepage: https://metacpan.org/release/MRO-Compat Description: Mro::* interface compatibility for Perls < 5.9.5 The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. . This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). . It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. . If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. . Some parts of this code will work better and/or faster with Class::C3::XS installed (which is an optional prereq of Class::C3, which is in turn a prereq of this package), but it's not a requirement. . This module never exports any functions. All calls must be fully qualified with the 'mro::' prefix. . The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other useful information. Package: perl-parent Version: 0.241-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-parent_0.241-1.1_all.deb Size: 8876 MD5sum: f49960589b52a40ddcd8e7e00f657a0c SHA1: 65721c02057fa1fb734e0564817e83ff40563ffc SHA256: 2c065f4d9a72349bd61452a80d6f480b2c930adc6fd302c6c2b30c37267ef665 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-1.1_all.deb Size: 15188 MD5sum: 0906f2df634ba689c5ef7edd33724207 SHA1: 88f09b9a3138f86696b8cedf61a70fcf3adabe2f SHA256: b77a07abc31bafdae350eb53fa3267b8b3fe79d86329292f2e2fa2e5ac4d3044 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-1.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-1.3_all.deb Size: 19128 MD5sum: 413689eadbad1cd20c306121e6040f7f SHA1: f3980b7b57f1952b0ef77288e63a2b419e602644 SHA256: 856be80a6313f9c0669fd31fed2b468a47b82ab6cc7ea6c27dbbad585fd53c62 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-1.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-1.11_all.deb Size: 22176 MD5sum: 1f1bd15072ab000848335add5fbe0392 SHA1: f66eb2999fc0e4e1556aab7251aefed392ea7237 SHA256: 2cd937b9a6e8f282614a1a16b49f3e23861ab4ada78e905e86be95322f94e517 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-1.17 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-1.17_all.deb Size: 56800 MD5sum: 6a155d62e54f542cf08f4621ea81c9f8 SHA1: e556c4064c1dda23490a84ee6c36d33e46311bf3 SHA256: a0fecb9d6343b99df0e3afb1ec86916de89f69a09637ba5a82b2bfa03f8a4c00 Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-1.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-1.10),libtest-compile-internal-perl (= 3.3.1-1.10) Filename: all/perl-test-compile_3.3.1-1.10_all.deb Size: 21456 MD5sum: 78e529e921393ea15372685a09aabfa1 SHA1: 27b5c00b8aec3842350aa995c052d14b396491c8 SHA256: 881e985d808e453f972696f050f09edcb61ada3f24c8c35c6eb4f430a411a641 Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-1.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-1.4_all.deb Size: 93256 MD5sum: 373c0111f9b8328a243869bf59c2f52c SHA1: 9c7b6b521a3fde63f919b3d4ecf28373d3a0aef9 SHA256: 9d468d8a97aa96482a3730a134c049ba3b24d1df88635ffec50e1738c9cfab12 Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-1.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-1.7) Filename: all/perl-test-differences_0.710.0-1.7_all.deb Size: 18380 MD5sum: 4ca5585bc97eb99ec20da58ed914f2d0 SHA1: edb1db850dfd3d6324955a04867c14fbf0ab5247 SHA256: 93824e0f04c049d31223374b453deab43e00865a89c7aab1e9d7b320e5dc94ee Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-1.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-1.13) Filename: all/perl-test-exception_0.430000-1.13_all.deb Size: 18088 MD5sum: c091dd27d00712ed059c0b0c12cc0205 SHA1: f75839117d3bba98475f33728d725a1c11bda6bb SHA256: 4ccc4cfdceeaf5da1005418bbbf9404c165751cfed9dec2e15f583169d718447 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-1.19 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-1.19_all.deb Size: 23428 MD5sum: 7479b6a028c8a62b38299421948ac510 SHA1: 560ba4aa1e06b389febe7897578f040a0334d0f8 SHA256: 16c69269215ee91351c9c90591fd471d9b1b540d3a5f552b677dd0ae8c0a181c Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-1.1_all.deb Size: 13312 MD5sum: b7374513df94f255b3f4216655131b18 SHA1: 14342a62ebb00b6b4d90c482521fc5cad4cfa9ab SHA256: 26560305abfdd7b55559080fe8b7dba24353cf3a687db5fad27005cacb3e0b75 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-1.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-1.5_all.deb Size: 10932 MD5sum: 5977d8bec12d7d376d3a81321e6f5646 SHA1: 908028db45fba1abaa43ed742f087246afd7cde3 SHA256: 52c176303af229c3a4c1230d621b902345022e3a01a7e5ff559db624e5e75af3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-1.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-1.14_all.deb Size: 14844 MD5sum: e5c6515671f56236b0f6f9837e2c2144 SHA1: 66058de1f131549908955e1d023d78875b8d4e9a SHA256: 5df8d3112573bc96db5678cdba8593ed681e62c9e8428479badddd30ec659baa Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-1.1_all.deb Size: 33356 MD5sum: 728799e79eb68e303703a5d845fca68f SHA1: fc2abb43f720d589a621dc672e4c720ec2f3ad8b SHA256: 39ae95a9144dcbbca51c20cb3e092584e74438d8805b0e0d5c5d2fc703b0c78d Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-1.1_all.deb Size: 23968 MD5sum: c0c28ef2726254080bd63da0cede34b8 SHA1: e9959fd463a9a3fb581bd3fea82d003973c4c56e SHA256: fc9ef2dc410962ced8c0230b57f6d855f4337bc31159a45bbb10cf7398df841c Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-1.1_all.deb Size: 8920 MD5sum: d24dfacc3e3616bcb299feb363b4fff5 SHA1: 7812f9edbc0480ad82706fda00c472b6092728d8 SHA256: 98f0c8135a4ba69482df9dfd604e7307810d14c8db2e03f4f8bec1408ddabd64 Priority: optional Homepage: https://metacpan.org/release/UNIVERSAL-require Description: Require() modules from a variable [deprecated] Before using this module, you should look at the alternatives, some of which are listed in SEE ALSO below. . This module provides a safe mechanism for loading a module at runtime, when you have the name of the module in a variable. . If you've ever had to do this... . eval "require $module"; . to get around the bareword caveats on require(), this module is for you. It creates a universal require() class method that will work with every Perl module and its secure. So instead of doing some arcane eval() work, you can do this: . $module->require; . It doesn't save you much typing, but it'll make a lot more sense to someone who's not a ninth level Perl acolyte. Package: venv-salt-minion Version: 3006.0-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 164159 Depends: gnupg,logrotate,systemd Filename: s390x/venv-salt-minion_3006.0-1.1_s390x.deb Size: 30527004 MD5sum: 1138f8af0a9ad0e3f6ad353c1fe0272c SHA1: 07c1c4ec0e49bf9622f62155953d577771761799 SHA256: 7df237b9fe0bf18404aefec3ab29ed6443b8857c8eff1bff38b33aca3a1be7de Section: System/Management Priority: optional Homepage: http://saltstack.org/ Description: The venvjailed client component for Salt Virtual environment jail for Salt minion. Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands. Package: venv-salt-minion Version: 3006.0-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 153137 Depends: gnupg,logrotate,systemd Filename: armhf/venv-salt-minion_3006.0-1.1_armhf.deb Size: 30506540 MD5sum: bfc7b06042ca5d78b12317d15025a691 SHA1: 91833df8077edaec8473bcb335171d2026b6c254 SHA256: 97212f2620860a9e0d9289f2262a11120c8fb4afb414abf3b5aab0ab43b2d3c4 Section: System/Management Priority: optional Homepage: http://saltstack.org/ Description: The venvjailed client component for Salt Virtual environment jail for Salt minion. Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands. Package: venv-salt-minion Version: 3006.0-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 161432 Depends: gnupg,logrotate,systemd Filename: arm64/venv-salt-minion_3006.0-1.1_arm64.deb Size: 30551568 MD5sum: 58968051b489723df9f2b4fd9d2551fb SHA1: b99de3744256ad013ea8a3df8cca26465ee3ce01 SHA256: baf3e393adcd85a3e8c16fdb2651530cd2ead88c344423c51cecd5e1b31e6d99 Section: System/Management Priority: optional Homepage: http://saltstack.org/ Description: The venvjailed client component for Salt Virtual environment jail for Salt minion. Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands. Package: venv-salt-minion Version: 3006.0-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 158668 Depends: gnupg,logrotate,systemd Filename: amd64/venv-salt-minion_3006.0-1.1_amd64.deb Size: 31024496 MD5sum: 6e97d20f25d30c3f8dda20e43ae1982c SHA1: d045d1cca302b26d0a223ed25b2a24d6f48efbc9 SHA256: 51f52f5faa791a75320fab9e40c70769d07c6a71a8724f0d7cb33d193faabc83 Section: System/Management Priority: optional Homepage: http://saltstack.org/ Description: The venvjailed client component for Salt Virtual environment jail for Salt minion. Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands. Package: venv-salt-minion Version: 3006.0-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 157464 Depends: gnupg,logrotate,systemd Filename: i386/venv-salt-minion_3006.0-1.1_i386.deb Size: 30987784 MD5sum: 7ed08b6fee7c40ab7d383dd9da2c12fc SHA1: c568055708e39345e553acd5ca7651b078298aba SHA256: 528c76c14abfff8c1f4f83426a4f1aeab9add7a78b5a5550d4df5fb11959e9e4 Section: System/Management Priority: optional Homepage: http://saltstack.org/ Description: The venvjailed client component for Salt Virtual environment jail for Salt minion. Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands.