Bug#762191: ITP: rubyluabridge -- access Lua from Ruby
Package: wnpp Severity: wishlist Owner: "Roberto C. Sanchez" -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: rubyluabridge Version : 0.8.0 Upstream Author : Evan Weis * URL : https://bitbucket.org/neomantra/rubyluabridge * License : BSD Programming Lang: C++ Description : access Lua from Ruby RubyLuaBridge is a seamless bridge between Ruby and Lua. It is a C extension that uses the actual Lua C library. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUHCEqAAoJECzXeF7dp7IP9sMQAIuS3DjgaVqFXNDjlpEJI8dT RPb+c6SiAqSYmnbrXxekw/4zsRx6FbwlF6J+Q0JZ0RhK8WygBXJ4SCK4H+ShBhHf tSjiV74tV7/zW9FYveFIK79KTn7DQsQBGW9V7QuoPSi6gBfhTxHU+wSOaPMQYnsJ NBWLpMkoicxRjOHQoKHmxYvDI/YRqr+pcf3N3/9ZpYmW8VAvzJulFtceJxfSa93w yE37cT2P+VubR5M0owvXjhK0BJmm6lRq/CUPbz7koNE4NWnsfLnjolV6hDYZ3imz 8IspSQtSKsucu43ToHubM3T9jj/ovYxPlw0LBGIGTTuUwM6F50znjFRWu/Jsxe2G DWZcsQRxQTVieqQfxpIVeNCb+qjZn87REQXiD6VyT+zZi3ulbDoEt+v1D/quT+Zu sdVIwxsAYgzVIh6phxj+Yy+21PPtao4B8u0wby+FFH/2Gt29fGe/3hE+9wSm2Tc8 En4GYGJLVFwmlVtaoSHv6wHnjAaRjgzPls+8kKvTxLrlAC45Xf877WeWcT3c9PYX 99v137AZSXmpEeHfdG+nPRLwjGvD9JqmV/UdMWHqjmbF3W4mdcrpUzqfqxKv8d8Y G+5fJcXLghumAJ5Rc+7SjUebgN5FH1TqotJ87OfgNeAmKarZx0uOeaHpByOno/S+ 1tm+y9YCfJukYypnQr81 =AKrV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140919122723.53052.85824.report...@santiago.connexer.com
Re: Installing debian-security-support by default
On 17/09/2014 22:15, Moritz Muehlenhoff wrote: > Hi, > during the last security team meeting we decided that starting > with jessie debian-security-support should be installed by default > on all systems (both freshly installed and upgraded) to have a > reliable notification channel in case security supports needs to > be ended prior to the lifetime of the general support timeframe. I just tried this package that I did not know. Two remarks: - I find very strange to get notification when upgrading to sid about packages not supported - I find very inconvenient to get message during the upgrade that require that I click on "ok". Debconf have been developped so that all questions (but very specific ones) are ask *before* the upgrade. debian-security-support regularly stops the upgrade asking for a confirmation. So, on all my systems (but one perhaps), I will remove this package. Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541c5d74.3030...@free.fr
Bug#762252: ITP: afdko -- Adobe Font Development Kit for OpenType
Package: wnpp Severity: wishlist Owner: Debian Fonts Task Force * Package name: afdko Version : 0~20140920 Upstream Author : Adobe Systems Incorporated * URL : https://github.com/adobe-type-tools/afdko * License : Apache License Programming Lang: C, Python Description : Adobe Font Development Kit for OpenType Adobe Font Development Kit for OpenType (AFDKO) is a set of tools for building OpenType font files from PostScript and TrueType font data. -- ChangZhuo Chen (陳昌倬) http://czchen.info/ Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D signature.asc Description: Digital signature
Re: Bug#762116: marked as done (general: Some packages depend on a particular init system)
> I'm closing this bug because this ain't a general bug in Debian. Some packages > depend on Gnome too (or KDE or some obscure OCAML library) and it's no secret > mean conspirancy that they do so, but rather relying on some feature > somewhere. Aka: "business as usual". > > Please direct your energy elsewhere than into useless bug filing. Code changes > the world. So, Holger, are you saying that failure to accomplish our goal of supporting several init systems is not a bug? Would you ask a random user (not a developer) to develop code if he notices that e.g. installing brasero changes his init system? Closing bugs because you do not want to acknowledge that there is really a problem is hardly a solution. systemd is the default we choose, not something we should impose on all users wherever they want or not at the least opportunity. A cd writer changing an init system is not "bussiness as usual". Regards Noel Torres er Envite signature.asc Description: This is a digitally signed message part.
