Package: deb-perl-macros
Version: 0.1-2.6
Architecture: all
Maintainer: Victor Zhestkov <vzhestkov@suse.com>
Installed-Size: 42
Depends: perl
Filename: all/deb-perl-macros_0.1-2.6_all.deb
Size: 2700
MD5sum: f9e1484a1fac66cb7414d9acd98686d4
SHA1: eafac48655d59c4437a469e30438052389a8905e
SHA256: 2c58e6b88032fd139c503d7a2b848b50e3aaec39a5fd9de093cdde04c2c5048c
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-3.2
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
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-3.2_all.deb
Size: 55172
MD5sum: 412cc52de6d76a00a84ee14b06a5acd9
SHA1: 37dc59e1b1069aa48d5b37440250b76f465af714
SHA256: 29e1e91cf5350e445f3dc37c8477239abd7d8a89469b078c732fb92ee23d38dd
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-3.2
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
Installed-Size: 32
Depends: debbuild (= 24.12.0-3.2),liblua-api-perl
Filename: all/debbuild-lua-support_24.12.0-3.2_all.deb
Size: 8620
MD5sum: be21ee7ab107b5d9071b07c579e268bd
SHA1: cc50ff87b6b63974b6e82d3edd05fe1e082fc83b
SHA256: 9cdd8e94d006eeae60dea23b72fbb34942c21de1fa5011a2be8fb74e5028b61c
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.7-2.2
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
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.7-2.2_all.deb
Size: 25512
MD5sum: 4e14c9399cd84b6ee39e044a8cba18b9
SHA1: 5351ce55e7a9d55967aba604d4a10aed43c84aff
SHA256: ec0ac8d1f61241866330e5b54e9c2ca38fe7c3b63492c93b3df143b4b26fca52
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.3
Architecture: ppc64el
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 401
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: ppc64el/liblua5-1-5_5.1.5-1.3_ppc64el.deb
Size: 76816
MD5sum: e5fb04154f4a29a94d9653d4b9472289
SHA1: e7080271a004df385214a1f69b22fa76da65a094
SHA256: a9ab5fd9bafa7137380b9e0a476e60b4df7c9d27326eb65e58e04ad95e6c99c8
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.3
Architecture: s390x
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 359
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: s390x/liblua5-1-5_5.1.5-1.3_s390x.deb
Size: 74660
MD5sum: f31ad330544ea8cc3806df0c94cadfd8
SHA1: afe180c69c85f1ae8d7a08ea34a7eba5a40a0bb6
SHA256: 872c02f24f284d9b0e239e02938e7ca6d3c8e0fe9dabe557e0f8212eddc10b89
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.3
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 749
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: armhf/liblua5-1-5_5.1.5-1.3_armhf.deb
Size: 281956
MD5sum: 8b2840b64e6adc02d26600fcca316c2d
SHA1: 45c927554770d517dc862cdcef2c5a75449316f1
SHA256: 688cd9bf689dfe06fcb0ab27a674be9ace0ea085104269e2aecb07c299b66197
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.3
Architecture: arm64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 862
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: arm64/liblua5-1-5_5.1.5-1.3_arm64.deb
Size: 294396
MD5sum: fd0a57571dacd62be5baa322fcbc5b68
SHA1: 4d671016786fa11bb1110bf6454e17c6eeac1c60
SHA256: a21abb21532ab5ba72221f5126c7bed9fb2c1f8f1526f15e975a9ed7ab993822
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.3
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 857
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: amd64/liblua5-1-5_5.1.5-1.3_amd64.deb
Size: 307548
MD5sum: cc26bfe201eab9c7b5ea7215709a71bd
SHA1: ac21e0eead675d0a429b3601555c65ca969663c8
SHA256: c040b2781660e6c55d9cfaec73b456965a3c2729d98fd320ea848de821a6f37b
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.3
Architecture: i386
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 804
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.3)
Provides: lua51-libs (= 5.1.5-1.3),liblua5-1 (= 5.1.5-1.3)
Filename: i386/liblua5-1-5_5.1.5-1.3_i386.deb
Size: 305904
MD5sum: d6f0f067eff1282dc853df944c504547
SHA1: f970c613f5f31fe026fc7958592bd44f3ae308e1
SHA256: 380deba2da1961ed9a451f71129c56d7150b85289880349b529037aeb4607592
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-28.2
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 25
Filename: all/lua-macros_20210827-28.2_all.deb
Size: 1604
MD5sum: 76508c5c27f181a33f7515d97866f9ee
SHA1: 0c9ffb0a6ad40373bd1962302a17f2a9ccb89bfa
SHA256: 07518098efcb09cc594be2fa146305a04bbd99d3265a05f3710aa7cf67399b0b
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.3
Architecture: ppc64el
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 645
Depends: dpkg,libreadline8,libc6,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: ppc64el/lua51_5.1.5-1.3_ppc64el.deb
Size: 91960
MD5sum: 66c621ce0e91651862a89464d540ba53
SHA1: 5efda96ac072025368df9c4b9aa69ed225279319
SHA256: 83d351f5a5554c2c1fc5f5c1be2cab1dfe981d42d3ea78395db8961939474051
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.3
Architecture: s390x
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 604
Depends: dpkg,libc6,libreadline8,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: s390x/lua51_5.1.5-1.3_s390x.deb
Size: 89776
MD5sum: 1445b43cf10480a33217aa297f9e9dcc
SHA1: e68f6b11fb0fb4406fe48724cbd4a009be1c57a7
SHA256: 994362872d04ea032242f2de6917ba72b65f0d4bb2606fea17f2b5050e8a8ddb
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.3
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1314
Depends: dpkg,libc6,libreadline8,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: armhf/lua51_5.1.5-1.3_armhf.deb
Size: 344812
MD5sum: 01d69d044d826531586a9fe652445dd4
SHA1: e144c84d0167f64af06812091a929a8573c2ecd4
SHA256: 9a63a27df0ee7a63ea25c7923fa1c5fe169a81c5d6da207c64b36f8fa3e50e15
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.3
Architecture: arm64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1510
Depends: dpkg,libreadline8,libc6,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: arm64/lua51_5.1.5-1.3_arm64.deb
Size: 360120
MD5sum: 03463e56dc241d82a602a30019c32ddc
SHA1: f9395e4f5a10a7639c50eb045371960ca02a3e99
SHA256: d64cf55879697a5d7fd7b3e91bf4f73dda88d6d2fab7ba16f26d370e9df46360
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.3
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1489
Depends: dpkg,libreadline8,libc6,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: amd64/lua51_5.1.5-1.3_amd64.deb
Size: 376688
MD5sum: 85a2578f5b86a301ee9649db50e96de8
SHA1: 00e3f2c2534601835444b46bf96402e70efd521c
SHA256: 494bd61f78e6a643d3b79b56d13be4985ea12186be59956844fe5deeaf867d84
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.3
Architecture: i386
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1413
Depends: dpkg,libreadline8,libc6,libtinfo6
Provides: lua (= 5.1.5-1.3),lua-api (= 5.1)
Filename: i386/lua51_5.1.5-1.3_i386.deb
Size: 374148
MD5sum: 625e7c10933b9842b2eff920ed97a338
SHA1: 4f9d446d2346dbd769dc8028bf12aa4ed79326f8
SHA256: 353fc2a46f294e2044a989e3703f6394daaf0c27540a7e4031f432a8ade9cc79
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.3
Architecture: ppc64el
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 583
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: ppc64el/lua51-devel_5.1.5-1.3_ppc64el.deb
Size: 92960
MD5sum: 36f52e69203ccd2c2d899df051df29d9
SHA1: b3f72acc33aced2b20ba040c87b8530ba3d38885
SHA256: f2131218355d133546716a8c71d328af19742265a2670d4364b01640e89222c7
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.3
Architecture: s390x
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 561
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: s390x/lua51-devel_5.1.5-1.3_s390x.deb
Size: 90312
MD5sum: fb63f1643ade8bf65f9ebda30607e5a7
SHA1: 703864e9ed4970addf9a6329716d24bd99ad5589
SHA256: 68c5a63bfcef8c3af09edb24e0123ce2544b19dd13ebd4d32eff0152552af829
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.3
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1109
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: armhf/lua51-devel_5.1.5-1.3_armhf.deb
Size: 356404
MD5sum: ee2b95f0e00a5a69c9b6f57cdd9d34b8
SHA1: 500f3fb2af32e434683156cf2321d7418154255b
SHA256: d8afccffd844c9546e763e592b50d752e0d209ee65c2a40f7d4cc348a233282e
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.3
Architecture: arm64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1662
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: arm64/lua51-devel_5.1.5-1.3_arm64.deb
Size: 372252
MD5sum: 61b7da9f336d20dac267aa8854cb7a9d
SHA1: 6f5336dd36868e52a9b375f07afdcbef4a47ae9b
SHA256: 78366a30f1c730737c82ea7f6d58ecc4efa11c468fedea317597e59810ac9d7c
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.3
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1685
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: amd64/lua51-devel_5.1.5-1.3_amd64.deb
Size: 383180
MD5sum: 9d62c3cf616d27e8d9e27fb235f86e72
SHA1: d205bbe235aa3510e54e4d0ca3d2fd1bd93a38cc
SHA256: a91e67189db3ef41517ecfc71999369715e85eb1192677ac2ca61976c5b308cb
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.3
Architecture: i386
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1190
Depends: liblua5-1-5 (= 5.1.5-1.3),lua51 (= 5.1.5-1.3),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-1.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.3)
Filename: i386/lua51-devel_5.1.5-1.3_i386.deb
Size: 381756
MD5sum: 9cef3ee1515bcaf23c6d9ce09374caf4
SHA1: 949d0144091bebd85df3341f7b14ed86329827ad
SHA256: 988369b44e968a83d565e5867dcf26e1681669bd305f9b0feeb0fb39e35e7f34
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.3
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 330
Filename: all/lua51-doc_5.1.5-1.3_all.deb
Size: 71640
MD5sum: b0cb1337bd89bbdbcb019bb52ee4ca26
SHA1: fba1bc4bfc38298d433fe89681abda788be23c26
SHA256: 9946df833deaebc4f56d6670a585ba6bea19571a85a647b1b7090f66eb7a3d54
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 121
Filename: all/perl-capture-tiny_0.48-3.6_all.deb
Size: 29992
MD5sum: 8c612b658c6f6f33e82d48e62b54d912
SHA1: bd50fc7700e7353b5ea8c006c83ae20e623596c7
SHA256: 3ab55f0e0101f925692123d76110d3b2af41da5581e64fd588517694f4bdf119
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-3.7
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 88
Filename: all/perl-carp_1.50-3.7_all.deb
Size: 22672
MD5sum: 49fc3e45d283670055f176389ed85f3f
SHA1: 58a831905661634bc08de772cc88c7f0da1399f8
SHA256: 66d1bf845ee58d0f9de277f13d75366d1689e529beb5557c523df84a688f4241
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 55
Filename: all/perl-class-data-inheritable_0.09-3.6_all.deb
Size: 7236
MD5sum: e05d415d7c63cbec24a22dbd8aaccdc9
SHA1: dea8aa76113205136b1ef1e441c484cffb5ff732
SHA256: d5deaa1f717f16de0053669cfec3cfde06b906957abb29fe3076f851b7baf430
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 113
Filename: all/perl-devel-stacktrace_2.04-3.6_all.deb
Size: 28408
MD5sum: 732efc315f59316319b364695674e802
SHA1: 733b04df76d221d27c3b40cd04111b7f0942b6f5
SHA256: a05edba7b058ff545746956b92e6426d484afe924352ba9bcadbae47ba60a90b
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 76
Depends: perl
Filename: all/perl-devel-symdump_2.18-3.6_all.deb
Size: 14372
MD5sum: 5d58b145d3a77f537cefd910e8174104
SHA1: 820a7f3b1928fe8b0304706a3b299dd26267aaff
SHA256: d416e580cd63e6de0fcb231e455bd9582a1a6accb5524e33bb52fcf87e10201d
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-3.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 142
Depends: perl-class-data-inheritable,perl-devel-stacktrace
Filename: all/perl-exception-class_1.45-3.16_all.deb
Size: 39052
MD5sum: 2776eddf567b09d21ffaed03df7ff0b8
SHA1: 9ec4edcc3a8b4a42778099b789e6399227e9ade4
SHA256: 4e75a30da3230016a564b98199cea71792fa996383af2ce4f6bdccede20ae205
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-2.20
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 155
Depends: perl,perl-ipc-cmd,perl-perl-ostype
Filename: all/perl-extutils-cbuilder_0.280236-2.20_all.deb
Size: 39240
MD5sum: ca4a4a35e6b1f1271f0df2e888f9a70d
SHA1: 5e0dce9ae56d0608c0822dc9c95a95ef9cb272d9
SHA256: 27977120f4991253a5b536473e01740ed00f8d4bb988bb8168d53cef9bc5b607
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-4.7
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 890
Filename: all/perl-extutils-makemaker_7.66-4.7_all.deb
Size: 304404
MD5sum: e9beec5bf7de83c8c343421860f44bd1
SHA1: 6c9085e1ec03a1896c68d4c493832762f3d283a5
SHA256: 10e1a2c0b862f28c1c8b7f49d70207a58ea7e416b4cf4c8ded5bfda705e68f98
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</"MAKE"> 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<ExtUtils::MakeMaker::FAQ> for details of the design and usage.

Package: perl-extutils-pkgconfig
Version: 1.160000-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 61
Depends: pkg-config
Provides: libextutils-pkgconfig-perl (= 1.160000-3.6)
Filename: all/perl-extutils-pkgconfig_1.160000-3.6_all.deb
Size: 10548
MD5sum: 658dba469e5bfdac4f863c6c3acaaec8
SHA1: 16448ecb8780b24f99e0f6906f0030471ec20dcf
SHA256: 3872652ceea73e8670c97aee7715206915d1518ded92e113dc4bba5897d68e97
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 107
Provides: libfile-path-perl (= 2.180000-3.6)
Filename: all/perl-file-path_2.180000-3.6_all.deb
Size: 30676
MD5sum: eae8b010ab004fa02cde3ab24f689959
SHA1: 3dbd772dc60ce134f3a80d9cb238ba85ab8e1de8
SHA256: ae5b8d338adf05a82892dcfd8e3aeb78b719175813777d743bf644635ad9d114
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-3.8
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 207
Depends: perl-file-path,perl-parent
Filename: all/perl-file-temp_0.2311-3.8_all.deb
Size: 53276
MD5sum: d514ef98f6f69d85ea5f3776f7fcea85
SHA1: 7d321878e762cd7c1c59fc91cdaaffbb6c717b2c
SHA256: 5d36a692182dfe339b30daa309f1782356b4a15a176411f2af8f03ec81d993a5
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-3.7
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 127
Depends: perl
Filename: all/perl-ipc-cmd_1.04-3.7_all.deb
Size: 33144
MD5sum: 25facfb8b57e491a8d2513209837808d
SHA1: 0cb0dda436384c998071e48f94ae56d61f7e45c2
SHA256: 7d4dcbe2766e4049e76882b49f70b694feb6b0d10018226fdfcf60dc7343455f
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-2.110
Architecture: ppc64el
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 790
Depends: perl-base,liblua5-1-5,libc6
Filename: ppc64el/perl-lua-api_0.04-2.110_ppc64el.deb
Size: 177164
MD5sum: 590b2b2d785a032e5420fc08309c5ac7
SHA1: 984d6f67d01087a06cf32478188ab0570b39e834
SHA256: 6fa493fe31e2b1f4100370b6d1c58c300a4b4044f93bae74b11416cdd3ca64c9
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-2.110
Architecture: s390x
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 724
Depends: perl-base,liblua5-1-5,libc6
Filename: s390x/perl-lua-api_0.04-2.110_s390x.deb
Size: 167864
MD5sum: 693799a54ec9b1ad8ea626a971717627
SHA1: 8bffa2665756bc09659aa68e5c7d6e38eae7e1fa
SHA256: ca40213ac8346ea5db4adc320c1c2b11af34253e929e30d182fdcce65b27ca34
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-2.110
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 640
Depends: perl-base,liblua5-1-5,libc6
Filename: armhf/perl-lua-api_0.04-2.110_armhf.deb
Size: 169820
MD5sum: 9adf380e65671ace9efe941fcd5cccda
SHA1: de9ec4532c5522f3c5f7d59381c7a4e1ddefda6a
SHA256: 22a1952d75274ee3c2b43d6f44aebf5495e04a8e6677c25566f3e2dd7547835d
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-2.110
Architecture: arm64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 750
Depends: perl-base,liblua5-1-5,libc6
Filename: arm64/perl-lua-api_0.04-2.110_arm64.deb
Size: 167204
MD5sum: 2e6b3625dcd5d11e3fc43e3a41f7da48
SHA1: e79b7e2f7f51f0ab1ba47db4af56b0fc660aa76d
SHA256: f68990660760dcca1d121fbaf9a58e3073ea5efb9ee9c8c6c7ae03b20d85b7d3
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-2.110
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 702
Depends: perl-base,liblua5-1-5,libc6
Filename: amd64/perl-lua-api_0.04-2.110_amd64.deb
Size: 173788
MD5sum: f351b581613ed9bd7475f9d1ddff9c8e
SHA1: 4703b406a5edd8b38cde4aff57a4c889e1e5e38f
SHA256: 68ba32029b1747f0682d7d645c8857e8f101aa0147aa645d44ac8e5b266c30ef
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-2.110
Architecture: i386
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 653
Depends: perl-base,liblua5-1-5,libc6
Filename: i386/perl-lua-api_0.04-2.110_i386.deb
Size: 162756
MD5sum: 6e8c0ad8e19e7042c168e5f107c1aa52
SHA1: 59e0365e8715d36a1b72848203b80b2759988b49
SHA256: 1aea3886ed70012ea1908638d07ff5fe1e435f1570060f00948d53bdd2f438fc
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-4.29
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
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-4.29)
Filename: all/perl-module-build_0.423400-4.29_all.deb
Size: 252316
MD5sum: eee3ca4d91b6178998bd9852c3b8929f
SHA1: 92a1800002ebd2dff5f0467623a3d9433de0f35a
SHA256: be635d1cd82a5b40dd82fe91e217065435f9aec0c028600faa0f3b54e674383e
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 111
Depends: perl
Filename: all/perl-module-metadata_1.000038-3.6_all.deb
Size: 29652
MD5sum: 51c1f06334619e2bc93088373d4853f7
SHA1: b4bda2e50e780a66c87b51239ea8824905e45df0
SHA256: 92a81611667c15a5fbd67acedd7fbbe38c6a66562a7f668d02a1bce4ffd5a463
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-3.52
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-module-runtime_0.016-3.52_all.deb
Size: 18440
MD5sum: 4f92b1f1ab4d046a0c0366af2efb79ba
SHA1: 5d205bbdf245ebf991f2316dfa192272853526be
SHA256: b3e44f72e9009a7c7d19f1ef40ad1c54f14b32f70825ec74a349984639785128
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 81
Filename: all/perl-mro-compat_0.15-3.6_all.deb
Size: 17188
MD5sum: 82091a78a13d911156f0a4194f691805
SHA1: c0cc5a999c37aa23abad21826aef05ccf4dd940f
SHA256: a24445a3b3b265ad33269367a841e16e26cbbb19cf166e9aa68bc0776ae8a232
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.5
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 48
Filename: all/perl-parent_0.241-1.5_all.deb
Size: 8872
MD5sum: 49df8f342a1ac0f7d9cd1b77ab59e83d
SHA1: cf59edc5e8a0cf4423c27d1c90a13eee8e3df06f
SHA256: 3086b41adae2a184f2c3e36773d71b347ccc009ca2e8b3aaef6d255eb8ceaacf
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-3.7
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-perl-ostype_1.010-3.7_all.deb
Size: 15192
MD5sum: b359d80c8d431fffbf7c7ec6fd0fa29b
SHA1: 364ce3b569a3f1afd09c63ef0cdbf6a38f492e84
SHA256: 9e6bb24e35360525410165497a99e804cfb72fe4756589593562e60d2381d8ee
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-3.13
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 85
Depends: perl-devel-symdump,perl
Filename: all/perl-pod-coverage_0.23-3.13_all.deb
Size: 19120
MD5sum: 0f9ddc88db6537ca16883536d1d262d4
SHA1: 5cbbc2f28f7aee23cc6818a9b4eff334af8c4216
SHA256: 8404d5ba4364f964feac6163493a7f09fbae9b8b135a3ffcd7cff34a600b6e38
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-2.47
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 112
Filename: all/perl-sub-uplevel_0.2800-2.47_all.deb
Size: 22168
MD5sum: 8004647e480b5b3c4436f47cdb8d9d10
SHA1: c5af13b88018df2a68db0f34227585e77691fdcf
SHA256: 91256d9eee05515ddf8720b85a8e6188175ba2744df1c2ebfaf3935993ac53fb
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-3.83
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 208
Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny
Filename: all/perl-test-class_0.52-3.83_all.deb
Size: 56796
MD5sum: ec32235d6deb5c93463a90b506c26405
SHA1: 53ddbc5faa9101c0bf08df362489f214a29bd1f2
SHA256: 5f7a8d72012ccbe862a7da6e305ae5de0a362b67935e57f1d2f7e74d8d7a6073
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-3.40
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 86
Depends: perl-base,perl-parent
Provides: libtest-compile-perl (= 3.3.1-3.40),libtest-compile-internal-perl (= 3.3.1-3.40)
Filename: all/perl-test-compile_3.3.1-3.40_all.deb
Size: 21448
MD5sum: fe761f4ed332657a95d748dc844370a2
SHA1: 045714945be44a6614f9aa2a8a73588eed233a32
SHA256: be6b6aa52915db432f6607227abf7ef202c8712e28256a1d85deb2c7ffacd76e
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-4.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 353
Depends: perl
Filename: all/perl-test-deep_1.204-4.15_all.deb
Size: 93228
MD5sum: 493a3f53cf393304f53c58af851b84e0
SHA1: 2cd02e6494de0b6f6d5478ea90bfe12a8e09c22a
SHA256: e52836c8ad9ec010b47603d72cd0227ce12832980d81bcc9bac685de729d2fbc
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-3.18
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 73
Depends: perl-capture-tiny,perl,perl-text-diff
Provides: libtest-differences-perl (= 0.710.0-3.18)
Filename: all/perl-test-differences_0.710.0-3.18_all.deb
Size: 18376
MD5sum: 90c10e321f0beafebdcecdbafcc3209a
SHA1: e94e65f49ce20272d61b041f02a94d48fad10ccb
SHA256: b0b836db0d606bbd28d54bfc7e743748d79c88969ad3b94fdb1c53a12d53473b
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-3.59
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 71
Depends: perl-sub-uplevel,perl
Provides: libtest-exception-perl (= 0.430000-3.59)
Filename: all/perl-test-exception_0.430000-3.59_all.deb
Size: 18084
MD5sum: 136120ff14271ffffcb61bca8a593d93
SHA1: 415f7a33c660b6d31c6a466ee5ae68dcc907145c
SHA256: 822b45b4785db2aa800a351d69b94f0f8874b1c04b889ce1470a325520496654
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 = <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-3.81
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
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-3.81_all.deb
Size: 23424
MD5sum: ec3cc6db418a6e941337bd7c81b51c9e
SHA1: 8e84e0a0be5478e580e7979fa17fb50945bdca1d
SHA256: 93cf711afd6435708c13ad647ae91d584c5772f96be01e8361a9b2ae22d80da9
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 62
Depends: perl
Filename: all/perl-test-pod_1.52-3.6_all.deb
Size: 13316
MD5sum: 91957342d70dc1c3aca82b8d4bd7fec6
SHA1: b7188830b621da99d67b4bc595335fb5d8b73ec4
SHA256: 4a03609ec5ba984c7f93e27648b61616e7e5be5f8480f3814a79ba0e012c7645
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-3.21
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 61
Depends: perl-pod-coverage
Filename: all/perl-test-pod-coverage_1.10-3.21_all.deb
Size: 10932
MD5sum: 3d152df4e4fea4849da5749e664f8b91
SHA1: 00614718b6ad1ea72cb27925f772633a8d14cefd
SHA256: f1cfdc3aa2b285afd66d3b436a030d7260040ea7924140e40fad4ba370df17c6
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-3.57
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 70
Depends: perl-carp,perl-sub-uplevel
Filename: all/perl-test-warn_0.37-3.57_all.deb
Size: 14840
MD5sum: fd9181d639af1f17197897626c419ece
SHA1: 55ec9616d92c2e3a26792d400a84d5fbcf2cba2b
SHA256: b7e136093dbc20b4830895bcc8f18d0a0fefe64e8e2d42953e0645303f2f0081
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 129
Depends: libalgorithm-diff-perl
Filename: all/perl-text-diff_1.45-3.6_all.deb
Size: 33348
MD5sum: 8640e61db0016c27ba6c34bbc45057e5
SHA1: 22f552375ae11b60bea5a65d2b99c78bd53137ba
SHA256: c8bde5065fbe4352c04ecae91d333be7cdb122201f5582d3f6e9d48fd58fb532
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 80
Filename: all/perl-try-tiny_0.31-3.6_all.deb
Size: 23968
MD5sum: 4b4144f33b1423bf5b363b38195fe92c
SHA1: 41e296603f0b9d08a427fb303cda1e685a008aa9
SHA256: 63793dfefc654a3171bc36fa24430c6ee13d8e7651e9130512d073741086e562
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-3.6
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 52
Filename: all/perl-universal-require_0.19-3.6_all.deb
Size: 8920
MD5sum: 44675cce759904e212bc969720495d47
SHA1: a3a3b7df41e1d4a6f5f1876bb2a53db9690fad36
SHA256: cbfd8b301e1e9368df55eb66c274cdac4b14c606c400b8d0fbc364d1776fb15e
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.