Mpack Software
Roman Bayramdurdiyev
At present, stack definitions are bundled with Ambari core and are part of Apache Ambari releases. This enforces having to do an Ambari release with updated stack definitions whenever a new version of a stack is released. Also to add an "add-on" service (custom service) to the stack definition, one has to manually add the add-on service to the stack definition on an Ambari Server. There is no release vehicle that can be used to ship add-on services.
Management packs are released as tarballs, however they contain a metadata file (mpack.json) that specify the contents of the management pack and actions to perform when installing the management pack.
Note: Do not pass the "--purge" command line parameter when installing an add-on service management pack. The "--purge" flag is used to purge any existing stack definition (HDP is included in Ambari release) and should be included only when installing a Stack Management Pack.
Actually, it stopped working for me too when using curl. Wget still works though, which is weird. Have you tried writing to in...@fossies.org? Sounds like a bug to me. DLAGENTS could be added to the PKGBUILD, but I would rather have this resolved with the site operator if possible. In the meantime, you can change DLAGENTS in makepkg.conf according to _applications_package_guidelines#Custom_DLAGENTS.
Unfortunately the legacy version does not preserves filenames for me. I figured out that the Debian package of mpack fixed that in 1.6-4. Maybe this could be integrated here aswell within the patch file. Corresponding Debian patch file can be found here: -8.2/01-legacy.patch/
bigtop-ambari-mpack in master branch -packages/src/common/bigtop-ambari-mpack is based on BIGTOP 1.5.0 release and only support Hadoop 2.1.0. In upcoming BIGTOP 3.0 release Hadoop version bump up to 3.2.2, bigtop-mpack need upgrade to support Hadoop 3.x.
Working mostly, but not exclusively in the fresh produce industry, we help fruit and vegetable growers, packers and distributors meet the challenges of an ever changing and more competitive market
We have partnered with a number of leading equipment manufacturers, Egatec A/S, MAF Roda Agrobotic, and Gamaco Packaging Solutions - offering some of the most advanced and efficient solutions for your end of line automation, grading, weighing and packing requirements
At mpackwe pride ourselves in providing first class, honest, reliable and efficient service during the initial scoping stage of a project, during implementation and most importantly following installation and commissioning, ensuing our customers receive the service and peace of mind they deserve and expect
Search in specific suite:[focal][focal-updates][focal-backports][jammy][jammy-updates][jammy-backports][mantic][mantic-updates][mantic-backports][noble][noble-updates][noble-backports][oracular]Limit search to a specific architecture: [i386] [amd64] [powerpc] [arm64] [armhf] [ppc64el] [riscv64] [s390x] You have searched for packages that names contain mpack in all suites, all sections, and all architectures.Found 8 matching packages.
The package Suggests: mail-transport-agent. Perhaps the dependency could reasonably be upgraded to Recommends: but that is a matter of detailed opinion. The dependency declaration is there, and by policy, it is the user's choice whether or not to install the suggested package. Thus, I am setting the Status of this bug report to Invalid.
era, As I understand the documentation, this isn't an opinion thing. If the package does not operate without the other package, it is a depend, not a recommend. Below is my source for this information. If I misunderstand you, please correct or tell me how to use this package without the recommended package.
mpack -o ... works fine.
mpack ... [file] [emailaddress] fails with "execv: No such file or directory"
sudo mpack ... [file] [emailaddress] fails the same
ssmtp [emailaddress] works fine.