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: 2d9189503e11c8bf0b3128f8749bd274 SHA1: 0b00f4e784f550656f144ab01272eaf53186cb93 SHA256: 9be671c7af749dea5feaef4ab4f50aaec63ee5cb5bf09090683c732f0340871b 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: 55148 MD5sum: 2e6bdf9eee21e5ae5c56c601f7d1ca04 SHA1: de90216131b15dae2138b6c46f93f9cf004ee153 SHA256: 7a06bb115e32633e886ad5ecc443f55bd7daead79f7ee7048f9862e68e4427bf 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: 8620 MD5sum: df6267f6fd125655603b13ee703cd2f8 SHA1: 954716ed588304d4f1aafeb14b1803fff773eef3 SHA256: 0d055beac6665c326aeb26c02a5347126c99fcfa5bef9b783dd9d80d048abaeb 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: 25544 MD5sum: 394b41c143f9065711d0ed643ced6d73 SHA1: 23796ea1409de331dbef86ae1b46ab4b056825fa SHA256: 1c31b5677b52af1d786572161faffe8b450b24a36cd052a4d435c0408f1bf452 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: 74664 MD5sum: 1bd7c9e0814337549df4cf41ce8402fc SHA1: 1296d7194c11eb51b953392bc311547549f5a911 SHA256: c72f26a7fd5e3ea411c1c50a67bbe8fa198b6a6ebc5a217a0c222f2a2598421e 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: 281848 MD5sum: 2308bb9a7f4d4c4adc96ece0060d73a4 SHA1: eaf4c6e6872ec896ff3a9d5b93a2e7484fbef296 SHA256: 994018d4fa140a0a907fd45db0360dcd74abe4f7e7cb4de6af6e6b8b1e3f7fbd 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: 294216 MD5sum: 04dcb3a39f2a2117abcd2daae18fb69c SHA1: e679974fc4a444cf8f2007f0ea7f6d3b93af9962 SHA256: 266c92d9275b30b59d289087876edff0c38c2ee3b8bc91d962dfeea5881d87cd 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: 307500 MD5sum: 16a8a8ef5465ce134e76823b78169b74 SHA1: 0940193241386aae743534e540b41c80d7553650 SHA256: 4e8f9b9b38df5546e2ecc58663ba517b0b568d9891b9d6120767cb0329482f5c 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: 305600 MD5sum: d548f4da0d3bd0045cbc94ca60d64ec5 SHA1: ab9f8194047918c74993648a8bcba0e074122c4f SHA256: eb5fb691b4b9cb7c1ae88ae20b0756786b138312d9fe033b1655d9e623f95d15 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: 2808 MD5sum: 5aabf044a88f081565cb4eda1e3a2243 SHA1: 1353c42cef6b4e9839c981ae9ac1c8ee05f69060 SHA256: 278cac9d10c47ed7de11ff7f4eefa88a07974a595d34cdeee3e4dfc2dce4f718 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,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-1.1_s390x.deb Size: 89788 MD5sum: c59d115363a66e3f793128d9d84ae9b5 SHA1: acf7ee043be100674fe5172a3213beb740374ff5 SHA256: 2f95d29e31e2f09e0621d809622fed426661638aad54761dbb10140b808abbef 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: 344544 MD5sum: e9d950a289050bd07bf4c19a5624d018 SHA1: 56aee9027ae0b62a82f34d8e61ed516b3e155771 SHA256: dba961f42d5493220f244293cb6d468fc117baecf848bd863a92a4631308d6cd 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,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-1.1_arm64.deb Size: 360012 MD5sum: 3b2b700ee3756cb46f9f9d659be871f1 SHA1: 9f90b7e59a3c2bd08c175c915267de04989a7a09 SHA256: 2b226dffa880c265040fa3d7495779c6c2b3d98de6f8bfae562f6f57cf43ef99 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,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-1.1_amd64.deb Size: 376388 MD5sum: 6861c2d230a6d8728895f84a6606cfc1 SHA1: 07b1768fd08d4f846d9c5925ed3f8ee90d0689f5 SHA256: f89af3cf02e5a7f42bdb9c20253dff081ade44b8d839cb17c0480320e4e7152b 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,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: i386/lua51_5.1.5-1.1_i386.deb Size: 373924 MD5sum: 594f8c72d504e90e9762e39f5a81030c SHA1: b7a22bf569a95c1b2e378be66094468497329c9c SHA256: ae7bf426343c2d02d096c0f05fe5eb8f22d14c5e5dd8e18673c0c46c42c2a1cc 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: 90176 MD5sum: 6831782f0f53aafb807fc5e1ceccc9d9 SHA1: 5c3976ffb5773fad8226d6fd6da6c526d61ea146 SHA256: ef7120b869aeef6fd9c01be67ed6e90a283f310351d28142cd6f25d56a9c616c 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: 356436 MD5sum: bf8efafdda14206acd75be09e6e09edf SHA1: b8c0733ce48ac71d9a692f98c716c18677d1b14a SHA256: 2bb6f504d938ffe4829ed6eaae96ad81ac66dcf9c7cd49112bf9a480c1efae0f 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: 372400 MD5sum: af914f518cc92ee8691d822d1a12e1b6 SHA1: 0b54cf336368700fb1046d5fb060eec82e1d2375 SHA256: 0366c8693a5087a30e50ce81ec90b2d756543563da10f6099137ca03c6ac3c17 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: 383376 MD5sum: fbf8c78fef6da2bee8b6fe883c4bbdce SHA1: b04aee788d2ed393da04fb3b74666fbb76d3fc7d SHA256: a69a1d4d48bff35b5961e3964372ed9578bea1752323bb58451ac772bf2a220e 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: 381904 MD5sum: 4f86fcfabc88b2a29772d70a083e734f SHA1: dd2a0bb2aab396a51292a890d77f34b6ea849205 SHA256: 1a73e31d5326f4f5ae21df4689abaccf77a17c7c13d871e4d2889e00df143784 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: c9c235e4a151702da27291f06a8d4b76 SHA1: d2d23b2791c3ee8195c4cab71934e08e63180421 SHA256: 02417f982b97404e19bcfdd7640af01df0de2455f6731b19c1ec0499070663aa 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: 30004 MD5sum: 94ced98dcafdb6e71e3220c955cb81c3 SHA1: 624436a4e4a016d31b88ebf4fbf6fc1a748f38b0 SHA256: f72630d96499f691d60465c30df854d86392f369d62868e859a89580662c09bf 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: 22672 MD5sum: be387a8da5c5c63848551387b8a28cbe SHA1: fb60866f3d1359e346bbd5ea51556d480510dea5 SHA256: dd07b184c54c91224cd9f04ac9865233bc3ea0cbdc01a70a5287b190e030e9f5 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: 7d80de00bc41c03911e8755b6f4eb278 SHA1: 32d99d28dea9365e0add12bae1e01eb53df5b5f0 SHA256: 826a5e4465a16d91b6f4c176c92b0370cc7f60382f4ea84f4b8f8aee289b4004 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: 28400 MD5sum: e675d59fa2b64a9e70af7b2b211ae31e SHA1: fbdf0714d2765635e47116503ba5d97226870e8f SHA256: e474aaf211686f3876857a6b8d1f2f35a012b0f9873905ab860ffccb9c2f07e1 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: faa4a0ad43023d106bc774d265931e78 SHA1: c1d0ab52ecb08701d0225ae90ece67489bc5c537 SHA256: 145ecaeedee48df19e614e1e67578a13eab53fbe675fbc7124b5f3efa1ca2c53 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-1.4_all.deb Size: 39052 MD5sum: 0164cc5a6ceff5e0848c3b90bb12614c SHA1: 88d3908a8154e4c2f79700eac4344e5916326502 SHA256: d1729926ef06e6daaae3a47e9f60773c1a37c072300e7dc363ad69843c89a053 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-1.6_all.deb Size: 39256 MD5sum: 6ab08117efbf0d6f2f0843ef227845ee SHA1: a8e86eb6326c5504accdb83c06f5a137d44d8ebd SHA256: 60aa63a8ffe7f91bb01a49ca89e3145813f1041c8eab1b76e10b715bacacf65c 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: 304464 MD5sum: 6c76404b407f5b5fba56fd4c79029439 SHA1: 0d258a46f65c6c268d7e175797f68b79b4a66652 SHA256: 394abf4d4796c707a6ddd9452c07dc8e58ec1ca0025eaac050314be9f65421bd 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: a727d6734eb29d99f1a74afe90d599b9 SHA1: 16994cfff9fb6fcbaa1482e57f32c98fa4cdecdb SHA256: 0d0327d2f4ac01d808b56a4198d3f4f7699a6d1bc9308bae0b85687b2979b0e1 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: 30676 MD5sum: 5e5ca7e85d8961c3ffb8933feeaafdfb SHA1: c9f97bd8b7d8bab8f98e041b099889f07683c862 SHA256: 1ec966d56fabf2ab440bc5e607dc8e0314d66b2c150729190b8af88ac40ac2c3 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: 53296 MD5sum: 9ce48bd1f79bd83fb22b962863e09499 SHA1: f1c11a609b68670d500566fc57f2613ee2e8bae7 SHA256: aeab3171be27cff1717e4ae542056613d9bcfd3b9d56036d460ee7316ce6efe7 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: 33136 MD5sum: 73b67cf738ccd1a1cd1c42e4e3d59ddb SHA1: 4cd69625651c5421014aaa7b5eb70afaa3d2b894 SHA256: b7d52ffde4a9c24b353cce0b36eace1c9ac3dc3c26415c4fc968b43f6dbcdc3c 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.21 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-1.21_s390x.deb Size: 168200 MD5sum: b6744db2b716e11055832e8de59507da SHA1: 92329b27d1efb513ad0d7acdffd93f4437ac3006 SHA256: dd592b6fdefebea096af9a35762dcc01630f44618dcedf24fb55fc57ecc4087f 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.21 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-1.21_armhf.deb Size: 170076 MD5sum: c7023fea0f0028696b4de25f2669a359 SHA1: 29400ff34c6461e9a45cbe64304d345e1980a8f0 SHA256: 63c3223940b18de176e83f9980330ea46bd24a735e9e516291880e6093c2c7ef 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.21 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-1.21_arm64.deb Size: 167312 MD5sum: 4858cb826d7644593fbbbbca70ff5af8 SHA1: 56e75dae2d3effc19f274adcd3a5f0f6017ddf24 SHA256: c9466a85447c572cce5440e9b36d02b9050adb6cea13c5f8708e35c913ad4c0f 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.21 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-1.21_amd64.deb Size: 173852 MD5sum: b83e08286af5b66c2a5e723681984648 SHA1: afee391c64ca20c21fa3668c4c1d700ca56513ba SHA256: 5476e1cc75ae32e5b457c90b6ba90f2062b5b7e39b8e7a91ba680f081104ad96 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.21 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-1.21_i386.deb Size: 162596 MD5sum: f805a112012b9b92093f2c6c9bb721db SHA1: 317186868c383b7991ec521b1d3016b94adabe6b SHA256: 289b1bf454fb5dd82e06fb4f37062ca2f84e2ea51fc5c8e7982961e78e38af47 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: 251204 MD5sum: 2719dbcd137a4f89e72441a153ff2c4f SHA1: 078cc9d9ff52ff3ba39faa8e3c5ae02e3022dafd SHA256: 530c7b7470efa68e65431d40f33732525e1560b797fff1b674a977c9c5e4d79e 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: 1f66b4157b3ffb0c3e388c3fc4124a0f SHA1: 2dff1a3fe3f7006c7794fb7ffa07f8288566af60 SHA256: 010eebc889de1462ac76ffa5c723e8b854a8f7dbe11b3caae321b7b1d3655dc7 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-1.11_all.deb Size: 18444 MD5sum: 58d0d19379fa9b2471ddad82db4ade1b SHA1: 32b514eadae48b7a458566c3f2b50dccf8fbc11e SHA256: 7dd76ed6a37006af053ac34c0c00301500a9ddea5bacfddc2481138711039e04 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: 17196 MD5sum: c755ee3653baa28906689f41de70539b SHA1: 6bed97675f45ec7731484ee85ab9d1a1ad252942 SHA256: ceca8fd4e054f76dfa95b0e51abaf1626146f1687420847e8fa10b1baa72d7d2 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: 8868 MD5sum: 5730c3acb32541441e74e1d35b63d90e SHA1: a61331829178f8da4bc9f869831daa61472a889b SHA256: ee0cfbc1c47c048078ed0dd140138a9633ec296997128b0d394d4f45ea660671 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: 15200 MD5sum: 88984a6903655771553e92e8464b2e11 SHA1: 899cbe081bf61a0103208db3bdc3ec01665c8f60 SHA256: b252d78c3e2cfebf22c89e1f5431197298ac97bc956e2e871b46016d327d4832 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: 19140 MD5sum: 63b75c8f6bd41e13c96e832257765f2d SHA1: ae8de18284d1a14e2260480e07e92650ad493a30 SHA256: 009aded184d635cc4fcd9f837785491519bd63004adf859a8f3e344ae45edfaa 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.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-1.12_all.deb Size: 22172 MD5sum: a0f595694e3185a172eefa64ac096b13 SHA1: a721054d5378c2ebc939605142cd07ac2f167920 SHA256: ac553be7aabf9231cc834d16377c540777286e469f098755b0da07e8ccc8514d 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.18 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.18_all.deb Size: 56820 MD5sum: fc7b41b99d133a3d0b690dbbd19afb13 SHA1: 0b3c6e9ae1d0b3b42d7d9f2f89730503ddcfe260 SHA256: 27bc77ed1dec16960152f6ebf12aa3ee50824867fca35ce5ca961cc0c3c66785 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: 21468 MD5sum: ab83b7e06b59803459cb1d13b4e886bf SHA1: 08c461311a7f2c4a4cd8391ae60a0427d1b2f738 SHA256: de45dfede68fb5027175ae0d84a03372fb7dba94c71e248c2c0eddc621a5fdbd 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-1.3_all.deb Size: 93256 MD5sum: 00eca24e548b5a7a2794cd1e81d4864e SHA1: 78fa1992ec449408e090f542e34611ed1972950e SHA256: c949fb53b6e55dea3563eb37b52b7da7415a08d6b22e921d24648e11ebc22f04 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-1.5) Filename: all/perl-test-differences_0.710.0-1.5_all.deb Size: 18384 MD5sum: b622a2cccbcb9b7dc6fbf6046ca66fd6 SHA1: e9f21b7fab0396e58bbeb99e9c97bfba678f82de SHA256: b643a6077907961f9812c17cb87f658605166330b4dbc7e4e48225f2e8bff859 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.15 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-1.15) Filename: all/perl-test-exception_0.430000-1.15_all.deb Size: 18088 MD5sum: 52158f826665e381bfb03e66c31b900e SHA1: 48344c72d5fe01e5b63ce8dcb2f28ec2a499ab80 SHA256: 50278af9b0f1aec5cc351308598fdca002cdb6faf0702a7f74a4050f1eecdb7c 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.18 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.18_all.deb Size: 23424 MD5sum: f767bba2d7bf581dd0f8253db54f8df6 SHA1: 4807575c9c984a09565f0df52baa5099e96986b1 SHA256: 16034d6b028f81302517538d0e88a482c5b2b68a9df4ed4019868597e2e03e88 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: 600864fd65e42c5e1e8c9bd7521f0d87 SHA1: 1cec1ae440276e3e7de738436b54029fe4e37b4b SHA256: 2f5616e4baae89ff6b781e230146d1118cdace31ccf8cdfd24b167719f4e7987 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: 10928 MD5sum: 514d3ca449a6d5c384c7cb2211287bad SHA1: 4523bd4b98cf37d525818a01126331d66a2ff689 SHA256: c466c4fa5e2a52f14eea87ff8a58dc2085f29077c99a1bd92d390d1efedf2153 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: 14848 MD5sum: ffcde76ec70d8e7d36a948da93e17539 SHA1: 5a089913f452443a9a768a083a3a33358cd0de87 SHA256: 357747bdb5702f17795f413db6363f03dff4d198afeb6c2533af240e2334d658 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: defce08356752cae67ab479bdf7f7506 SHA1: c8ff492efa219616c71ad1cd5108219d429e74a1 SHA256: f8f1b1fa158bf79d583e44271bda2fda9a7e3ef438b61926a6297b5de889d744 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: 23976 MD5sum: 90a46d686c391bf858ad9fd7bf39658b SHA1: 1472cc5c0edf0501419148c844d0071d08d14678 SHA256: 9d8993b2f7b8517bc116ebded6451e551d7d5c738e1d65a42f855aed9869f8f0 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: 8924 MD5sum: 3f6a2621d39db72f84b2c63d2c57cc79 SHA1: ab4718c1298981aece48be46a8120821be731e82 SHA256: efe048fe490ce0ebffc51a0d4a9f4c0eee3974179913250f624118d7ae23882c 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: 164155 Depends: gnupg,logrotate,systemd Filename: s390x/venv-salt-minion_3006.0-1.1_s390x.deb Size: 30532188 MD5sum: 26e01b316a9bda05325b3c703c8c1d0c SHA1: 75af030c886214434de320d84178e48d96b1a315 SHA256: e5f03d9af1cafdd1b31aa5bf59ad0e8e85c6135f7bbce4df1200b02b51bd1741 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: 153125 Depends: gnupg,logrotate,systemd Filename: armhf/venv-salt-minion_3006.0-1.1_armhf.deb Size: 30507912 MD5sum: 6325b148fe3cee1e8a20d62f2cb72161 SHA1: 00e6be09ccf283cbb23976bcf9b6e36dcf5cbee4 SHA256: fb9dca50106aaf75796b7fc30a6d8046cfb4fdd7b178559d9bcbcfebb3bf9dd9 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: 30554400 MD5sum: b0f901f4b398937760faaf91efa82f30 SHA1: e80200a49b089fbb42c19cb6989842bd80f8f8d5 SHA256: 75680cff0e68bd60c6b7b418052d2f5796a80b9e3b8186b3f312578d11369a9b 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: 158672 Depends: gnupg,logrotate,systemd Filename: amd64/venv-salt-minion_3006.0-1.1_amd64.deb Size: 31023276 MD5sum: fb662ca3f85bbef9ce4c6c8a154f8b7b SHA1: 6d18fb2c2fadb11c7680fceebcface9850756213 SHA256: f71fb2ea3d77955243bd43197aa9cd7877dc95e9a177f3d6a3e6e718e170c502 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: 157472 Depends: gnupg,logrotate,systemd Filename: i386/venv-salt-minion_3006.0-1.1_i386.deb Size: 30988016 MD5sum: da6cd673266bae8eb72a37c1044513c0 SHA1: 8b52f2741a367c81dfc654f581bb038ad7e8cc11 SHA256: 7f573ecbca8f2fd7d6c284a8e2af131f7d6d54e1aba7d2ed81c9a0e217d3e416 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.