[RFS#880264] kconfig-frontends / Standalone implementation of the Linux Kconfig parser and frontends
Dear mentors, After some time I'm pinging again, looking for a sponsor for my package "kconfig-frontends" Package name: kconfig-frontends Version : 4.11.0.1-1 Upstream Author : Yann Morin URL : http://ymorin.is-a-geek.org/projects/kconfig-frontends License : GPL-2+ Programming Lang: C Section : devel Description : Standalone implementation of the Linux Kconfig parser and frontends It builds those binary packages: kconfig-frontends: Kconfig-frontends provides the kconfig parser, as well as all the frontends (dialog, ncurses, Qt and Gtk based) to configure and generate config files and config headers for various projects. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kconfig-frontends Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kconfig-frontends/kconfig-frontends_4.11.0.1-1.dsc This project aims to give an out of Linux tree support for Kconfig files, in order to use the same syntax and mechanisms for emedded (or any other) project configuration. This permits to highly simplify the configuration part and to help in the integration of the configuration as much in the project's production system as in the project's code itself (through autoconf.h support). If anyone would kingly sponsor the package (or take a look at it to begin with)... Regards, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 0xC22D06D4.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#880264: RFS: kconfig-frontends/4.11.0.1-1 [ITP] -- Standalone implementation of the Linux Kconfig parser and frontends
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "kconfig-frontends" * Package name : kconfig-frontends Version : 4.11.0.1-1 Upstream Author : Yann Morin * URL : http://ymorin.is-a-geek.org/projects/kconfig-frontends * License : GPL-2+ Programming Lang: C Section : devel Description : Standalone implementation of the Linux Kconfig parser and frontends It builds those binary packages: kconfig-greontds: Kconfig-frontends provides the kconfig parser, as well as all the frontends (dialog, ncurses, Qt and Gtk based) to configure and generate config files and config headers for various projects. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kconfig-frontends Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kconfig-frontends/kconfig-frontends_4.11.0.1-1.dsc This project aims to give an out of Linux tree support for Kconfig files, in order to use the same syntax and mechanisms for emedded (or any other) project configuration. This permits to highly simplify the configuration part and to help in the integration of the configuration as much in the project's production system as in the project's code itself (through autoconf.h support). Regards, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 signature.asc Description: OpenPGP digital signature
Re: [deb-ci] testing sysvinit scripts when both sysvinit and systemd supported by package
Le 13 juin 2017 12:36:49 GMT+02:00, Ansgar Burchardt a écrit : >Hi, > >On Tue, 2017-06-13 at 09:13 +0200, p...@reseau-libre.net wrote: >> I'm writting deb-ci tests to check backward support to sysvinit for >> openscap-daemon. I've written a sysvinit script, the systemd service >> file also exists [1]. >> >> The problem is that the deb-ci test (which run explicitly >> /etc/init.d/openscap-daemon) fails because adt-run create a testbed >> with >> systemd installed, even if i specified a test-dependency on sysv-rc, >> sysv-rc-conf, sysvinit-core, sysvinit-utils. > >Just installing sysvinit-core doesn't make sysvinit the active init >system: you need to reboot. > >I think the boot-smoke test in the systemd source package does that. >At least it claims to check that rebooting 20 times works. The >autopkgtest documentation also mentions "needs-reboot". > >Ansgar Thank's a lot Ansgar ! It works perfectly ! The boot-smoke script you pointed is a very good example of such a usage. -- Philippe.
Bug#862763: atomic/1.17.1-1 [ITP] -- Atomic Run Tool for installing/running/managing container images
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "atomic" * Package name: atomic Version : 1.7.1-1 Upstream Author : Atomic Project * URL : https://github.com/projectatomic/atomic * License : GPL-2+ Programming Lang: Python Section : admin Description : Atomic Run Tool for installing/running/managing container images It builds those binary packages: atomic: allows an image provider to specify how a container image expects to be run atomic-doc: various documentations and concepts behind atomic To access further information about this package, please visit the following URL: https://mentors.debian.net/package/atomic Alternatively, one can download the package with dget using this command: dget -x https//mentors.debian.net/debian/pool/main/a/atomic/atomic_1.7.1-1.dsc This project defines the entrypoint for Project Atomic hosts. On an Atomic Host, there are at least two distinct software delivery vehicles; Docker (often used in combination with the traditional RPM/yum/dnf), and rpm-ostree to provide atomic upgrades of the host system. The goal of Atomic is to provide a high level, coherent entrypoint to the system, and fill in gaps in Linux container implementations. For Docker, |atomic| can make it easier to interact with special kinds of containers, such as super-privileged debugging tools and the like. atomic host does not support Debian-based OS by now (limited to rpm-based OS). Yet it permit to easily install/uninstall docker container into the system. Regards, -- Philippe THIERRY
Bug#861394: RFS: wcc/20170424-1 [ITP] -- a collection of compilation tools to perform binary black magic on the GNU/Linux and other
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "wcc" * Package name: wcc Version : 20170424-1 Upstream Author : Jonathan Brossard * URL : https://github.com/endrazine/wcc * License : MIT Section : utils It builds those binary packages: wcc - This tool permits one to manipulate binaries and shared liraries to reuse their API into an external usage, as a relocatable object that can be linked to a new project, or through an interpreter (wsh) to execute internal API directly. wcc-doc - All documentations including Doxygen output and various Howtos on how to use the Witchcraft Compiler Collection. This documentation also include various examples. This project is a set of tool to manipulate ELF, PE and COFF binaries to transform them into relocatable object (.o) file or to reuse their API directly through an interpreter. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wcc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wcc/wcc_20170424-1.dsc More information about hello can be obtained from https://github.com/endrazine/wcc Changes since the last upload: * Initial release (Closes: #861390). * Updated various spelling error. * Updated man pages. * Created two binary packages separating a complete documentation pkg. Regards, -- Philippe THIERRY
Bug#860145: RFS: openscap-daemon/0.1.6-1 [ITP] -- SCAP security policy compliance daemon for a complete infrastructure
Le 26/04/2017 à 11:36, Gianfranco Costamagna a écrit : control: tags -1 moreinfo control: owner -1 ! I've updated the package with a lot of updates/corrections. missing copyrights, e.g. Copyright (C) 2015 Brent Baude Copyright (c) 2003-2005 by Peter Astrand Hi Gianfranco, Thank's for the review. Should be ok for copyright. Take some time to manage license-reconcile output. It still says that "LGPL (v2 or later)" is not equal to "LPGL-2+", but no more copyright error messages. -- Philippe.
Bug#860145: RFS: openscap-daemon/0.1.6-1 [ITP] -- SCAP security policy compliance daemon for a complete infrastructure
Le 17/04/2017 à 08:12, Paul Wise a écrit : I don't intend to sponsor this, but here is a quick review: [...] Thanks for this review ! I've updated the package with a lot of updates/corrections. The package is now based on python3 only and use pybuild -- Philippe Thierry.
Bug#856404: RFS: scap-security-guide/0.1.31-9 ITP: security guides and conformity checks using SCAP standard
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "scap-security-guide" Package name: scap-security-guide Version : 0.1.31-9 Upstream Author : Watson Yuuma Sato (ws...@redhat.com) URL :https://www.open-scap.org/security-policies/scap-security-guide/ License : unlicenced (seehttps://github.com/OpenSCAP/scap-security-guide/blob/master/LICENSE) Section : admin It builds those binary packages: ssg-applications - SCAP Guides and benchmarks targeting applications such as ssg-base - SCAP Security guide base content and documentation ssg-debfamilly - SCAP Guides and benchmarks targeting all deb-based ssg-debian - SCAP Guides and benchmarks targeting Debian 8 ssg-otheros - SCAP Guides and benchmarks targeting other GNU/Linux To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scap-security-guide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scap-security-guide/scap-security-guide_0.1.31-9.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Updated binary packages name to simplify the structure * bin packages are familly-based, avoiding variation when updating About SCAP-security-guide: SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. The goal of this package is to deploy SCAP XCCDF Benchmarks and Guides for various targets not deployed by the OpenSCAP core package, but supported by the SCAP-security-guide community in which I work as contributor for Ubuntu, Debian and ANSSI best practices. Using these guides/benchmarks, it is possible to validate conformity of Debian-based deployment against standard security policies such as ANSSI Best-practices, PCI-DSS, NIST SP-800... and to launch remediation scripts when needed. Using the OpenSCAP ecosystem, it is possible to manage the security policy of a complete infrastructure, when launching OpenSCAP tool with the above benchmarks through ssh (for e.g.) or on VM or docker templates. Regards, Philippe Thierry
Bug#853903: RFS: scap-security-guide/0.1.31-6 [ITP] -- security guides and conformity checks using SCAP standard
Package: sponsorship-requests Severity: wishlist Dear mentors, First, thanks Tobi for your message ! I've corrected Warnings and Informational from lintian. Pedantic ones are harder to correct : - there is no explicit upstream changelog in sources, the scap-security-guide.spec is used as a changelog file. I deploy it through the ssg-base package - other binary packages don't deploy this file, ssg-base being a dependency of all other binary pacakges - there is not gpg check available on the github repository for uscan - the .svn control dir is voluntary in the upsteam sources, used as a "git submodule" like mechanism for the Red-Hat specific documentation - duplicated files is due to a current work on new PCIDSS derivative on which the RedHat team is working. When the 0.1.31 version has been released, the derivative was just a duplication of the PCIDSS content. To continue this mail in a standard way... I am looking for a sponsor for my package "scap-security-guide" Package name: scap-security-guide Version : 0.1.31-6 Upstream Author : Watson Yuuma Sato (ws...@redhat.com) URL :https://www.open-scap.org/security-policies/scap-security-guide/ License : unlicenced (seehttps://github.com/OpenSCAP/scap-security-guide/blob/master/LICENSE) Section : admin It builds those binary packages: ssg-base - SCAP Security guide base content and documentation ssg-debian8 - SCAP Guides and benchmarks targeting Debian 8 ssg-firefox - SCAP Guides and benchmarks targeting Firefox Browser ssg-jre- SCAP Guides and benchmarks targeting Java Runtime Environment ssg-rhel5 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 5 ssg-rhel6 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 6 ssg-rhel7 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 7 ssg-ubuntu1604 - SCAP Guides and benchmarks targeting Ubuntu 16.04 ssg-webmin - SCAP Guides and benchmarks targeting Webmin To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scap-security-guide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scap-security-guide/scap-security-guide_0.1.31-6.dsc More information about scap-security-guide can be obtained fromhttps://www.open-scap.org/security-policies/scap-security-guide The repository is onhttps://github.com/OpenSCAP/scap-security-guide Changes since the last upload: * Various corrections for lintian conformity. Only pedantic and experimental are still present. About SCAP-security-guide: SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. The goal of this package is to deploy SCAP XCCDF Benchmarks and Guides for various targets not deployed by the OpenSCAP core package, but supported by the SCAP-security-guide community in which I work as contributor for Ubuntu, Debian and ANSSI best practices. Using these guides/benchmarks, it is possible to validate conformity of Debian-based deployment against standard security policies such as ANSSI Best-practices, PCI-DSS, NIST SP-800... and to launch remediation scripts when needed. Using the OpenSCAP ecosystem, it is possible to manage the security policy of a complete infrastructure, when launching OpenSCAP tool with the above benchmarks through ssh (for e.g.) or on VM or docker templates. Regards, Philippe Thierry
