Re:
On Thu, 2016-05-19 at 18:29 -0400, Adolfo Holzmann wrote: > i'm a real person not machine, i'm from chile and i have a friend who > knows php, Java,bootstrap,html5,phonegap,laravel,codeigniter and many > others. He is a father of 2 kids and he is unemployed, could you give > him a work as a dedicated developer? The Debian project does not employ developers, but your friend is welcome to volunteer to help out with various aspects of Debian: https://www.debian.org/intro/help Also, your friend may want to become a Debian consultant or watch the debian-jobs mailing list for job opportunities. https://www.debian.org/consultants/ https://lists.debian.org/debian-jobs/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Empty Contents and Packages files in http://deb.debian.org/debian-debug?
Theodore Ts'o: > Hi, is it intended that the Contents and Packages file in the dbgsyms > archive are empty? > Hi, http://debug.mirrors.debian.org/debian-debug/dists/unstable-debug/main/binary-amd64/Packages.xz does not appear to be empty? Mind you, the debug archive was created with less backwards compatibility (e.g. it does not have "Packages.gz") than the regular archive. As for the Contents files: Yes they are empty. I believe it was an artefact of the implementation. As the build-ids are present in the Packages file, there is little interest in fixing it for the debug archive. > [...] > > Also, does anyone know if someone is working on a FUSE client that > could be mounted on top of /usr/lib/debug/.build-id so that the > debuginfo files could be automatically made available as needed when > gdb tries to access them? > > ` - Ted > No, but if you find one, I would very much like to hear about it. Thanks, ~Niels signature.asc Description: OpenPGP digital signature
Empty Contents and Packages files in http://deb.debian.org/debian-debug?
Hi, is it intended that the Contents and Packages file in the dbgsyms archive are empty? I was hoping to be able to add http://debug.mirrors.debian.org/debian-debug/ to my apt.sources list so I could easily download the dbgsyms packages. Also, does anyone know if someone is working on a FUSE client that could be mounted on top of /usr/lib/debug/.build-id so that the debuginfo files could be automatically made available as needed when gdb tries to access them? ` - Ted
keyring package
Hi, We have those keyring packages. $ LANG=C apt-cache search archive-keyring debian-archive-keyring - GnuPG archive keys of the Debian archive debian-edu-archive-keyring - GnuPG archive keys of the Debian Edu archive debian-ports-archive-keyring - GnuPG archive keys of the debian-ports archive emdebian-archive-keyring - GnuPG archive keys for the emdebian repository neurodebian-archive-keyring - neuroscience-oriented distribution - GnuPG archive keys pkg-mozilla-archive-keyring - GnuPG archive keys for the Debian Mozilla team package repository ubuntu-archive-keyring - GnuPG keys of the Ubuntu archive Some packages does "apt-key add /usr/share/keyrings/foobarkey" and some doesn't. Handy way is adding keyring via script, but I'm afraid that it would be too much, because adding GPG key to trusted system keyring is ease to break security. So, which is the better way? just mention to add it by hand in README.Debian or add it in maintainer script automatically. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane
Re: Bug#824884: netbase: should not recommend ifupdown
Does anybody see a reason to NOT remove the recommends? On May 20, Ansgar Burchardt wrote: > netbase should not recommend ifupdown. Currently any package > depending on netbase will install ifupdown and a dhcp client if > recommends are installed, see [1]. > > As ifupdown is currently Priority: important (same as netbase), it > will be installed in everything but minimal installations anyway. -- ciao, Marco signature.asc Description: PGP signature
Re: Accepted qtcreator 3.2.1+dfsg-7+deb8u1 (source amd64 all) into proposed-updates->stable-new, proposed-updates
unsubscribe
Bug#824826: ITP: python-cement -- CLI Application Framework
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-cement Version : 2.8.2 Upstream Author : Data Folk Labs, LLC * URL : https://pypi.python.org/pypi/cement * License : BSD-3-clause Programming Lang: Python Description : CLI Application Framework Cement is an advanced CLI Application Framework for Python. Its goal is to introduce a standard, and feature-full platform for both simple and complex command line applications as well as support rapid development needs without sacrificing quality. Cement is flexible, and it’s use cases span from the simplicity of a micro-framework to the complexity of a mega-framework. . Features include: * Core pieces of the framework are customizable via handlers/interfaces * Extension handler interface to easily extend framework functionality * Config handler supports parsing multiple config files into one config * Argument handler parses command line arguments and merges with config * Log handler supports console and file logging * Plugin handler provides an interface to easily extend your application * Hook support adds a bit of magic to apps and also ties into framework * Handler system connects implementation classes with Interfaces * Output handler interface renders return dictionaries to console * Cache handler interface adds caching support for improved performance * Controller handler supports sub-commands, and nested controllers -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXPsXlAAoJEGlMre9Rx7W2n6sQAL4RaX96VCTpeHF7cZ9F7gMb BYVj6ps7QnfThJn30jyGQQ52GVBv+JvLblMu10GYqT0yM9ijImi6GMAc4iPYKWnj e9F+HC/tvOP7a7LADJVCRPqK2p+9v4eFpQwwqZtwtaiGJg8/fxmvRXnVa60F1TuB 73vMi1aURxrN2ZymN6ASW1S/Ha5ou/FJhlPwuyKGiD6tELOkkVIqzgSD9Kgp7pp4 rY/BKImWGTr1KwBxTuHnikXK767U1Bj0RyQtQhGDblGXvbAU15uLYCFJ4QqhCWss uG+i0gB6XzEmnyO+CH02rRv4BNZVdwGwvj9HDvgOsJMM4Eu9HKiay5KLL/TBqe+W +86Yo9vO7M/xznBosRO5WbfUdH15gbG6s4WMcSCCBAx/JXFv8cCsZJKC3RC+7tVt mjWEMROvTXjCeqbNCT43yCqPMkm19hE11Rdvr40CuQnc6u4VvydRevxLCBCCDsaZ lieONAzaAgi5HCl79tEfwO95CQixbrIqRxOPAEPW7kpSzY5ONNEHrl6eG3sxgduQ v5e1kAj8WeHucg+sjjvvLHq4FYhSe8TeJdhe8nP+HYiiQ3E6D1rPPG2ZtIbD6zhV d0sN27/EpYchPHqoCqsEHRNlWhw7n7lpV5XaCTD1y0tfsbWUvao7izKJqpmo6zYA Nn2K5ImtJ2kuu3GF1ERm =h5KV -END PGP SIGNATURE-
