Bug#913874: ITP: peony-extensions -- Adds extended functionality to the Peony file manager.
Package: wnpp Severity: wishlist Owner: handsome_feng * Package name: peony-extensions Version : 1.1.2 Upstream Author : quankang * URL : http://www.github.com/ukui/peony-extensions * License : GPL-2+, LGPL-2+, GPL-3+, GFDL-1.1+ Programming Lang: C Description : Adds extended functionality to the Peony file manager. This package cantians a set of extensions for Peony, the UKUI file manager, such as open-terminal, sendto, wallpaper, image-converter, parchives, xattr- tags and so on. And this package will be maintained by the Kylin team.
Bug#913880: ITP: overlay-userns -- Overlay mounting in user namespaces (DKMS)
Package: wnpp Severity: wishlist Owner: Nicolas Schier * Package name: overlay-userns Version : 0.4 Upstream Author : Nicolas Schier * URL : https://rocketgit.com/user/nicolas/overlay-userns-dkms * License : GPL Programming Lang: C Description : Overlay mounting in user namespaces (DKMS) This DKMS package enables overlay file system mounts within user namespaces. Please be aware that this induces a security risk and thus cannot be recommended in general. Overlay file system is considered to be a security risk when it would be allowed to be used within user namespaces. The utilisation of unprivileged Linux containers in combination with overlay-based snapshotting is thus not possible by default. The 'lxc' provides unpriviledged LXC snapshot support by using overlay within user namespaces, which is currently only enabled in Ubuntu Linux kernels. When unpriviledged overlay LXCs are required on Debian systems, this package provides an alternative to a manually patched and built Linux kernel. Personally, I use that DKMS module at work, as I have to stick to unpriviledged LXCs but still would like to run a Debian kernel rather than a manually patched and updated one. I know that patching the runtime kernel is quite dirty, and I am expecting that this technique is not possible in the far future, but right now (and since the last two years) it worked quite fine on a few machines. As I am not an official Debian Maintainer, I do need a sponsor for the package. I am going to push the Debian stuff into a personal salsa repository (nsc-guest/overlay-userns); iff the package gets sponsored, moving to an official Debian salsa repo would be great. Kind regards, Nicolas
Bug#913884: ITP: super-save-el -- auto-save buffers, based on your activity
Package: wnpp Owner: Lev Lamberov Severity: wishlist * Package name: super-save-el Version : 0.3.0 Upstream Author : Bozhidar Batsov * URL or Web page : https://github.com/bbatsov/super-save * License : GPL-3+ Programming Lang: Emacs Lisp Description : auto-save buffers, based on your activity This package provides Emacs mode that auto-saves your buffers, when certain events happen - e.g. you switch between buffers, an Emacs frame loses focus, etc. One can think of it as both something that augments and replaces the standard auto-save-mode.
Re: Debian CI pipeline for Developers
Hi, 2018年11月16日(金) 2:14 Inaki Malerba : > > Hi Leopold, > > snip > >> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md > >> > > I don't know if it's the correct place but I have some issues about this. > > > > - I have not be able to set up directly a gitlab-ci.yaml directly in a debian > > directory. If I define it as the document says, I cannot activate the CI. > > However if I activate first in the root directory then I can activate the > > pipeline and after I can move it to the debian directory. > You can find information about that on the pipeline readme[0]. The > default path is in the root of the repo, but it can be changed on the > project's setting. I felt that default path which is set to the root of the repo is not suitable for package repository, sure we can change the project's setting, but debian/.gitlab-ci.yml seems to be the proper default setting. I'm a bit confused because it seems that https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md recommends debian/.gitlab-ci.yml but project default setting isn't so. -- Kentaro Hayashi
Bug#913889: ITP: pmdk -- persistent memory development kit
Package: wnpp Severity: wishlist Owner: Adam Borowski * Package name: pmdk Version : 1.5 Upstream Author : Intel and contributors * URL : https://pmem.io/pmdk/ * License : BSD-3 Programming Lang: C, C++ Description : persistent memory development kit The Persistent Memory Development Kit is a collection of libraries and tools to manage and access non-volatile memory. Via the DAX feature, most operations don't require a call to the kernel, allowing operating directly on such memory with only minimal latencies. . While basic access would require nothing but a mmap() call, it is non-trivial for a programmer to achieve consistency when facing unexpected power loss -- individual cachelines often don't get committed to actual memory for a prolonged time, become persistent in an unexpected order; etc. PMDK hides all this complexity, and provides tools to check for errors that would make stores non-durable, fail crash consistency, persistently leak space, etc. . Available Libraries: * libpmem: provides low level persistent memory support * libpmemobj: provides a transactional object store, providing memory allocation, transactions, and general facilities for persistent memory programming. * libpmemblk: supports arrays of pmem-resident blocks, all the same size, that are atomically updated. * libpmemlog: provides a pmem-resident log file. * libvmem: turns a pool of persistent memory into a volatile memory pool, similar to the system heap but kept separate and with its own malloc-style API. * libvmmalloc: transparently converts all dynamic memory allocations into persistent memory allocations. * libpmempool: provides support for off-line pool management and diagnostics. * librpmem: provides low-level support for remote access over RDMA. Available Utilities: * pmempool: manages and analyzes persistent memory pools. * pmemcheck: pmem-specific instrumentation for Valgrind. There's existing packaging in Ubuntu (for 1.4) and upstream (current and well-tested, but not very debianish), I intend to take pieces from both.
Re: Debian CI pipeline for Developers
Hi, 2018年11月16日(金) 23:24 Inaki Malerba : > > Hi Kentaro, > > snip > > > I felt that default path which is set to the root of the repo is not suitable for > package repository, sure we can change the project's setting, but > debian/.gitlab-ci.yml seems to be the proper default setting. > > I'm a bit confused because it seems that https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md > recommends debian/.gitlab-ci.yml but project default setting isn't so. > > > -- > Kentaro Hayashi > > > The default (.gitlab-ci.yml) it's a config provided by gitlab, not by salsa. > > There's already an issue open on gitlab-ce with this request. https://gitlab.com/gitlab-org/gitlab-ce/issues/41764 > > -- > - ina Thanks! I didn't aware of the above issue is already opened one. -- Kentaro Hayashi
Bug#913898: ITP: centreon-broker -- Network, system, applicative supervision and monitoring - broker
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-broker Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon-broker * License : Apache-2 Programming Lang: C++ Description : Network, system, applicative supervision and monitoring - broker Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the broker daemon.
Bug#913900: ITP: centreon-connectors -- Network, system, applicative supervision and monitoring - connectors
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-connectors Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon-connectors * License : Apache-2 Programming Lang: C++ Description : Network, system, applicative supervision and monitoring - connectors Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the connectors.
Bug#913899: ITP: centreon-clib -- Network, system, applicative supervision and monitoring - core libraries
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-clib Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon-clib * License : Apache-2 Programming Lang: C++ Description : Network, system, applicative supervision and monitoring - core libraries Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the core clib libraries.
Bug#913901: ITP: centreon-engine -- Network, system, applicative supervision and monitoring - engine
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-engine Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon-engine * License : GPL-2 Programming Lang: C++ Description : Network, system, applicative supervision and monitoring - engine Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the engine daemon.
Bug#913902: ITP: centreon-lang-fr -- Network, system, applicative supervision and monitoring - French translation
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-lang-fr Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon-translations * License : Apache-2 ? (https://github.com/centreon/centreon-translations/issues/5) Programming Lang: None Description : Network, system, applicative supervision and monitoring - French translation Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the French language pack.
Bug#913903: ITP: centreon-web -- Network, system, applicative supervision and monitoring - main app
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: centreon-web Version : 18.10.0 Upstream Author : Centreon * URL : https://github.com/centreon/centreon * License : GPL-2 Programming Lang: PHP, JavaScript Description : Network, system, applicative supervision and monitoring - main app Centreon is a modular and flexible platform for network, system and applicative supervision and monitoring. * monitoring of network services * monitoring of host resources * simple plugin design that allows users to easily develop their own service checks * parallelized service checks * ability to define network hierarchies * contact notifications when service or host problems occur and get resolved (via email, page, or user-defined method) * ability to define event handlers to be run during service or host events for proactive problem resolution * automatic log file rotation * support for implementing redundant monitoring hosts This package contains the main Centreon application.
Re: Debian CI pipeline for Developers
On 11/16/18 3:14 PM, Kentaro Hayashi wrote: > package repository, sure we can change the project's setting, but > debian/.gitlab-ci.yml seems to be the proper default setting. i don't think there is any reason to use a (hidden) dotfile in the debian/ directory. the default uses a dotfile in order to not clutter the root directory of the repository, at least visually (ignoring the fact that the dotfiles are still pretty much visibly and having the configuration for all those various CI-services in your root - .gitlab-yi.yml, .travis.yml, appveyor.yml and what - not is *quite* a clutter). so if you put the file in the debian/ directory anyhow, i'd just pick a sensible and visible name, like "debian/salsa-ci.yml" gfamdsr IOhannes signature.asc Description: OpenPGP digital signature
Re: Debian CI pipeline for Developers
IOhannes m zmölnig (Debian/GNU) wrote: > On 11/16/18 3:14 PM, Kentaro Hayashi wrote: >> package repository, sure we can change the project's setting, but >> debian/.gitlab-ci.yml seems to be the proper default setting. > i don't think there is any reason to use a (hidden) dotfile in the > debian/ directory. I see one reason: If the file is named "somedir/.gitlab-ci.yml" Gitlab automatically verifies the file and presents a "This GitLab CI configuration is valid." hint (or an error message) when viewing. If the file is named differently, this does not happen. The "Custom CI config path" setting does not influence this. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: Debian CI pipeline for Developers
Le 16/11/2018 à 21:39, IOhannes m zmölnig (Debian/GNU) a écrit : > On 11/16/18 3:14 PM, Kentaro Hayashi wrote: >> package repository, sure we can change the project's setting, but >> debian/.gitlab-ci.yml seems to be the proper default setting. > > i don't think there is any reason to use a (hidden) dotfile in the > debian/ directory. > the default uses a dotfile in order to not clutter the root directory of > the repository, at least visually (ignoring the fact that the dotfiles > are still pretty much visibly and having the configuration for all those > various CI-services in your root - .gitlab-yi.yml, .travis.yml, > appveyor.yml and what - not is *quite* a clutter). > > so if you put the file in the debian/ directory anyhow, i'd just pick a > sensible and visible name, like "debian/salsa-ci.yml" I'm using debian/gitlab-yi.yml as proposed on https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md [...]adding the following definitions to your gitlab-ci.yml file[...] [...]On Debian projects, you would normally want to put this file under the debian/ folder,[...] Regards, Vincent > gfamdsr > IOhannes > signature.asc Description: OpenPGP digital signature
Bug#913917: ITP: gajim-openpgp -- OpenPGP for XMPP
Package: wnpp Severity: wishlist Owner: "W. Martin Borgert" * Package name: gajim-openpgp Version : 1.1.1 Upstream Author : Philipp Hörist * URL : https://dev.gajim.org/gajim/gajim-plugins/blob/gajim_1.1/openpgp/manifest.ini * License : GPL3 Programming Lang: Python Description : OpenPGP for XMPP This is an experimental plugin supporting the new OpenPGP for XMPP standard XEP-0373 (https://xmpp.org/extensions/xep-0373.html). The package will be maintained with the XMPP packaging team.
Bug#913920: ITP: valinor -- generate IDE project files to debug ELF files
Package: wnpp Owner: Nick Morrott Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: valinor Version : 0.0.11+git20160222.486094a Upstream Author : ARM Limited * URL : https://github.com/ARMmbed/valinor * License : Apache-2.0 Programming Lang: Python Description : generate IDE project files to debug ELF files Valinor is used to generate debugger project files, and launch a debugger, when debugging an ELF file. Valinor is designed to be used as a proxy debug command for yotta targets to provide as their scripts.debug command. Valinor is a dependency of yotta [1]. [1] https://bugs.debian.org/908781 I plan to maintain this package in the Python Applications Packaging Team.
Bug#913923: ITP: project-generator -- generate tailored project files for embedded tools (IDEs)
Package: wnpp Owner: Nick Morrott Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: project-generator Version : 0.9.13 Upstream Author : Martin Kojtal * URL : https://github.com/project-generator/project_generator * License : Apache-2.0 Programming Lang: Python Description : generate tailored project files for embedded tools (IDEs) project-generator is a dependency of valinor [1]. [1] https://bugs.debian.org/913920 I plan to maintain this package in the Python Applications Packaging Team.
Bug#913924: ITP: project-generator-definitions -- collection of target/MCU definitions for project-generator
Package: wnpp Owner: Nick Morrott Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: project-generator-definitions Version : 0.2.36 Upstream Author : Martin Kojtal * URL : https://github.com/project-generator/project_generator_definitions * License : Apache-2.0 Programming Lang: Python Description : collection of target/MCU definitions for project-generator project-generator-definitions is a dependency of project-generator [1]. [1] https://bugs.debian.org/913923 I plan to maintain this package in the Python Applications Packaging Team.
