Re: How to change config script for multiarch?
On Wed, Feb 10, 2016 at 8:12 AM, NOKUBI Takatsugu wrote: > I am a maintainer of chasen package. It contains chasen-config, it > work as pkg-config like but it's a single script. > > Latest lintain reports: > E: libchasen-dev: old-style-config-script-multiarch-path > usr/bin/chasen-config full text contains architecture specific dir > x86_64-linux-gnu > > But I want to keep libchasen-dev as Multi-Arch: same. Would you tell > me finding the correct way to change the script? > See https://lintian.debian.org/tags/old-style-config-script.html
Re: How to change config script for multiarch?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi , I've solved this problem by: (1) creating a pkg-config script, adding it as multiarch. (2) editing the config script to use the pkg-config script. In particular, for any non-standard variables, you can read them, by eg: f90_compiler=$(pkg-config mypkg --variable=f90_compiler) Its probably a good idea to document the config script as deprecated in output, the man page, etc. regards Alastair On 10/02/2016 07:12, NOKUBI Takatsugu wrote: > I am a maintainer of chasen package. It contains chasen-config, it > work as pkg-config like but it's a single script. > > Latest lintain reports: > E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config full text contains architecture specific dir x86_64-linux-gnu > > But I want to keep libchasen-dev as Multi-Arch: same. Would you tell > me finding the correct way to change the script? > > > -- > Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry > Misentropy: doubting that the Universe is becoming more disordered. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWuwoCAAoJEMvmu05dmtOlhiUP/AuG7t8pMlzb4sgzvO//xAGK O8aNRi789Yun4svsClBFrO/lv2GcynH5h6fqLL1oAndmBCX5cuMqjCwzUEEngCcK Z5JiQ4MoQvFTqAneN0WGsvDPbq0Ofg6Lfti/FO3OsD6emvSn/f5f1RaF5mrd8vRd SolUJDjtABV6DVqX8tY8rbf7u/ecdeYq0zMnEPsKEnUgrNSJQLGm0XC5YyANeDcG 2kpxPtPhHF9yz0yqV/hqiYTjDFR53vY29q/9QjjI9amdEV2btdeVf5cvtGFwXNQm qL3VpeD0jbzMFYyIfcQy4IjhENkijyWl4BP9MD3sJ3vSpEjmLIfw5PGHVn2PgoEz 8zuAT4ub0D0ANRkA2JRLk9fVHtmGtEa4l2lpEztv4HeBeitEbKllOGQ1pU/GROax 2CmiGnxhG74T2qFC0bPDqHMKsc8W3SdXs6uYkuv+4WXiPuul14oD/7nOltGUc1p4 WHS5qSAZ/CV/madVZw1oeYDctehLYMk5RjYM32VO26lAoz0RkhAopdfmk+8QFUV8 nOJG2PKj1s4E3kJPZk2uLiFRSdhZe9PZXPnGcbJBpiEEw/Yo/6uhLOrm+n43gi/N ZAPWnWuEMY/22r7XJg0NQwmNCCPSqGeUVG2k18A7nYlf/eIY+lhnauJUwpKEFass JaVBSA7Fop2V1sPkOVzS =84mc -END PGP SIGNATURE-
Re: How to change config script for multiarch?
Hi Nokubi, Quoting Bastien ROUCARIES (2016-02-10 10:29:46) > On Wed, Feb 10, 2016 at 8:12 AM, NOKUBI Takatsugu wrote: > > I am a maintainer of chasen package. It contains chasen-config, it > > work as pkg-config like but it's a single script. > > > > Latest lintain reports: > > E: libchasen-dev: old-style-config-script-multiarch-path > > usr/bin/chasen-config full text contains architecture specific dir > > x86_64-linux-gnu > > > > But I want to keep libchasen-dev as Multi-Arch: same. Would you tell > > me finding the correct way to change the script? > > > See https://lintian.debian.org/tags/old-style-config-script.html your message would've been a better fit for debian-ment...@lists.debian.org You can see an explanation of lintian tags by doing: $ lintian-info --tags old-style-config-script-multiarch-path The old-style-config-script tag which src:chasen suffers from as well and which was also linked to by Bastien contains more valuable information. The important message is: please use pkg-config and not some package-specific configuration mechanism (as also already pointed out by Vincent). Otherwise, you (and/or upstream) will suffer from an unnecessary maintenance burden in case you ever want to (or in case we need to) cross-build that source package. For now though it should be sufficient to move the file into an architecture specific path. A bit OT: the old-style-config-script lintian description links to a 404 page on sources.debian.net. Maybe this link should be updated? Is there a way to create a link to a file on sources.debian.net where, if the version doesn't exist anymore, it will automatically fall-back to the next highest version? Thanks! cheers, josch signature.asc Description: signature
Re: How to change config script for multiarch?
On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi , > > I've solved this problem by: > (1) creating a pkg-config script, adding it as multiarch. > (2) editing the config script to use the pkg-config script. > > In particular, for any non-standard variables, you can read them, by eg: > > f90_compiler=$(pkg-config mypkg --variable=f90_compiler) > > Its probably a good idea to document the config script as deprecated > in output, the man page, etc. (2) wrapper are not cross build safe... > regards > Alastair > > On 10/02/2016 07:12, NOKUBI Takatsugu wrote: >> I am a maintainer of chasen package. It contains chasen-config, it >> work as pkg-config like but it's a single script. >> >> Latest lintain reports: >> E: libchasen-dev: old-style-config-script-multiarch-path > usr/bin/chasen-config full text contains architecture specific dir > x86_64-linux-gnu >> >> But I want to keep libchasen-dev as Multi-Arch: same. Would you tell >> me finding the correct way to change the script? >> >> >> -- >> Alastair McKinstry, , , > https://diaspora.sceal.ie/u/amckinstry >> Misentropy: doubting that the Universe is becoming more disordered. > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJWuwoCAAoJEMvmu05dmtOlhiUP/AuG7t8pMlzb4sgzvO//xAGK > O8aNRi789Yun4svsClBFrO/lv2GcynH5h6fqLL1oAndmBCX5cuMqjCwzUEEngCcK > Z5JiQ4MoQvFTqAneN0WGsvDPbq0Ofg6Lfti/FO3OsD6emvSn/f5f1RaF5mrd8vRd > SolUJDjtABV6DVqX8tY8rbf7u/ecdeYq0zMnEPsKEnUgrNSJQLGm0XC5YyANeDcG > 2kpxPtPhHF9yz0yqV/hqiYTjDFR53vY29q/9QjjI9amdEV2btdeVf5cvtGFwXNQm > qL3VpeD0jbzMFYyIfcQy4IjhENkijyWl4BP9MD3sJ3vSpEjmLIfw5PGHVn2PgoEz > 8zuAT4ub0D0ANRkA2JRLk9fVHtmGtEa4l2lpEztv4HeBeitEbKllOGQ1pU/GROax > 2CmiGnxhG74T2qFC0bPDqHMKsc8W3SdXs6uYkuv+4WXiPuul14oD/7nOltGUc1p4 > WHS5qSAZ/CV/madVZw1oeYDctehLYMk5RjYM32VO26lAoz0RkhAopdfmk+8QFUV8 > nOJG2PKj1s4E3kJPZk2uLiFRSdhZe9PZXPnGcbJBpiEEw/Yo/6uhLOrm+n43gi/N > ZAPWnWuEMY/22r7XJg0NQwmNCCPSqGeUVG2k18A7nYlf/eIY+lhnauJUwpKEFass > JaVBSA7Fop2V1sPkOVzS > =84mc > -END PGP SIGNATURE- >
Bug#814322: ITP: python-pyrax -- Python SDK for OpenStack/Rackspace APIs
Package: wnpp Severity: wishlist Owner: Sascha Girrulat * Package name: python-pyrax Version : 1.9.6 Upstream Author : Ed Leafe Matt Martz Brian Curtin Veres Lajos * URL : https://github.com/rackspace/pyrax * License : Apache 2.0 Programming Lang: Python Description : Python SDK for OpenStack/Rackspace APIs pyrax should work with most OpenStack-based cloud deployments, though it specifically targets the Rackspace public cloud. For example, the code for cloudfiles contains the ability to publish your content on Rackspace's CDN network, even though CDN support is not part of OpenStack Swift. But if you don't use any of the CDN-related code, your app will work fine on any standard Swift deployment.
Re: How to change config script for multiarch?
On Wed, 10 Feb 2016 at 11:03:04 +0100, Bastien ROUCARIES wrote: > On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry > wrote: > > I've solved this problem by: > > (1) creating a pkg-config script, adding it as multiarch. > > (2) editing the config script to use the pkg-config script. > > (2) wrapper are not cross build safe... Correct, but the existence of a foo-config script is not something that Debian should unilaterally change. Upstream software that depends on foo is still going to try to run foo-config, until/unless there is a release of foo that deprecates foo-config and provides equivalent pkg-config files. In other words, please talk to the upstream maintainers about adding pkg-config metadata and specifically deprecating foo-config. Debian-specific patches can only benefit Debian and its derivatives, upstream fixes benefit everyone. S
Re: How to change config script for multiarch?
* NOKUBI Takatsugu , 2016-02-10, 16:12: I am a maintainer of chasen package. It contains chasen-config, it work as pkg-config like but it's a single script. Latest lintain reports: E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config full text contains architecture specific dir x86_64-linux-gnu There is no chasen-config in the latest version of libchasen-dev (2.4.5-21). chasen-config is currently shipped in chasen-dictutils, for which Lintian incorrectly emits this tag. This will be fixed in the next Lintian release. Are you trying to move the script to libchasen-dev? Why? There are Debian maintainer scripts that use chasen-config. Are they going to depend on the -dev package? But I want to keep libchasen-dev as Multi-Arch: same. Would you tell me finding the correct way to change the script? It's hard to give a concrete answer without seeing the package you're working with; or at least without explanation how exactly it differs from the package in the archive. -- Jakub Wilk
Re: 50.000 binary packages
On 02/09/2016 05:06 PM, Enrico Zini wrote: > On Tue, Feb 09, 2016 at 07:04:11AM +1100, Riley Baird wrote: > Possibly someone should set up an online quiz thing, where you're shown a package name, its short description, and three randomly chosen short descriptions, and have to guess which short description is correct. > [...] >>> (script attached) >> I've modified the script so that it is interactive. > > Good one! I made it run multiple times so that there can be more play > for each lengthy initial computation: > > https://github.com/spanezz/pkgquiz > > > Enrico There's an RC bug... :P # ./pkgquiz Collecting package information... What is the description for package xfce4-appfinder? Traceback (most recent call last): File "./pkgquiz", line 122, in cont = quiz.run_once() File "./pkgquiz", line 81, in run_once cand_descs = self.pick_descs(name) File "./pkgquiz", line 44, in pick_descs cand = self.select_random() TypeError: select_random() missing 1 required positional argument: 'name'
Re: 50.000 binary packages
On Wed, Feb 10, 2016 at 09:19:11PM +0800, Thomas Goirand wrote: > There's an RC bug... :P Fixed. For the record, it grew even more: $ ./pkgquiz --help usage: pkgquiz [-h] [-i] [-a] [--hard] optional arguments: -h, --help show this help message and exit -i, --installed only quiz installed packages -a, --answersshow the correct answers in case you missed it --hard choose other descriptions from similar packages Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini
Re: another mount issue on jessie
On 2016-02-09 20:03, Bas Wijnen wrote: > On Tue, Feb 09, 2016 at 10:38:26AM -0700, Sebastian Kuzminsky wrote: >> On another Jessie machine I had to apply the same workaround to some >> additional services. I identified the services that needed the workaround >> by grepping for 'PrivateTmp' in /lib/systemd. > > So any program that uses this option is broken? Doesn't that mean we should > always disable it? Is there a reason that it is ever enabled for anything? > hmm @sebastian: could you confirm that you had to remove the PrivateTmp for each and every service you found by grepping? or did you just disable PrivateTmp for all of these services, and then no more problem occured (though by chance you might have disabled PrivateTmp for some services that would have actually worked with it). fgmadsr IOhannes
Re: 50.000 binary packages
On 2016-02-10 14:19, Thomas Goirand wrote: > There's an RC bug... :P > > # ./pkgquiz > Collecting package information... that's because you are in cheat mode. try playing with "--hard". ghsdt IOhannes
Bug#814352: ITP: veracrypt -- Cross-platform on-the-fly encryption
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: veracrypt
Version : 1.16
Upstream Author : Mounir IDRASSI
* URL : https://launchpad.net/veracrypt
* License : TC-3.0 or Ms-PL, E4M, BSD-3-clause, zlib
Programming Lang: C++
Description : Cross-platform on-the-fly encryption
VeraCrypt provides cross-platform on-the-fly encryption for Linux, MacOS X and
Windows. It can encrypt filesystems stored either within a file or on disk
partitions. Supported encryption algorithms include AES, Serpent and Twofish.
The current version uses the XTS mode of disk encryption. In addition,
VeraCrypt supports "hidden volumes" - unidentifiable volumes present in the
free-space of a VeraCrypt volume.
.
Veracrypt has been forked from Truecrypt 7.1a and I am aware of previous
discussion
about the non-free character of the license. [1]
.
With this ITP, I have also CC:ed the debian-legal mailing list. Question
at experts from the debian-legal mailing list:
.
TL;DR; I would like to bring VeraCrypt into the non-free part of the Debian
repo to offer
VeraCrypt to people in need of easy and GUI based encryption, suitable for
cross-platform
usage. Does the current license situation allow that?
.
Details / Questions:
.
1.
Is VeraCrypt suitable for the non-free section of Debian?
.
2.
I suppose VeraCrypt is not suitable for the main section of Debian
as the TC-3.0 license is not DFSG-compliant. I suppose
this has not changed for VeraCrypt, compared to TrueCrypt, right?
.
3.
The new upstream maintainer also states that all novelties of the code
are licensed under the Apache-2.0 license, but as long as any line from
the original code sticks out, the licensing of the code is governed by
the original Truecrypt 3.0 license, right?
[1] https://bugs.debian.org/364034
Example of the new license headers in VeraCrypt:
"""
/*
Derived from source code of TrueCrypt 7.1a, which is
Copyright (c) 2008-2012 TrueCrypt Developers Association and which is governed
by the TrueCrypt License 3.0.
Modifications and additions to the original source code (contained in this
file)
and all other portions of this file are Copyright (c) 2013-2015 IDRIX
and are governed by the Apache License 2.0 the full text of which is
contained in the file License.txt included in VeraCrypt binary and source
code distribution packages.
*/
"""
If acceptable, the veracrypt package will be maintained under the umbrella of
the
Debian Edu Packaging Team.
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: veracrypt
Source: http://sourceforge.net/projects/truecrypt/
Files: *
Copyright: 2003-2011, TrueCrypt Developers Association
2013-2014, IDRIX
License: TC-3.0 or Ms-PL
Files: src/Common/Apidrvr.h
src/Common/Cache.*
src/Common/Cmdline.*
src/Common/Combo.*
src/Common/Crc.*
src/Common/Crypto.*
src/Common/Dlgcode.*
src/Common/Endian.*
src/Common/Fat.*
src/Common/Format.*
src/Common/Password.*
src/Common/Pkcs5.*
src/Common/Progress.*
src/Common/Random.*
src/Common/Tcdefs.h
src/Common/Tests.*
src/Common/Volumes.*
src/Core/FatFormatter.cpp
src/Driver/Ntdriver.*
src/Driver/Ntvol.*
src/Format/Tcformat.*
src/Mount/Mount.*
src/Setup/Dir.*
src/Setup/Setup.*
src/Setup/Wizard.*
Copyright: 1998-2000, Paul Le Roux
License: E4M
Files: src/Common/GfMul.c
src/Common/GfMul.h
src/Crypto/Aescrypt.c
src/Crypto/Aes.h
src/Crypto/Aeskey.c
src/Crypto/Aesopt.h
src/Crypto/AesSmall.c
src/Crypto/AesSmall.h
src/Crypto/AesSmall_x86.asm
src/Crypto/Aestab.c
src/Crypto/Aestab.h
src/Crypto/Aes_x64.asm
src/Crypto/Aes_x86.asm
src/Crypto/Sha2.c
src/Crypto/Sha2.h
src/Crypto/Twofish.c
Copyright: 1998-2007, Brian Gladman, Worcester, UK
License: BSD-3-Clause
Files: src/Boot/Windows/Decompressor.c
Copyright: 2002-2004, Mark Adler
License: zlib
Files: debian/*
Copyright: 2013-2015, Unit 193
License: BSD-3-Clause
License: TC-3.0
TrueCrypt License Version 3.0
.
Software distributed under this license is distributed on an "AS
IS" BASIS WITHOUT WARRANTIES OF ANY KIND. THE AUTHORS AND
DISTRIBUTORS OF THE SOFTWARE DISCLAIM ANY LIABILITY. ANYONE WHO
USES, COPIES, MODIFIES, OR (RE)DISTRIBUTES ANY PART OF THE
SOFTWARE IS, BY SUCH ACTION(S), ACCEPTING AND AGREEING TO BE
BOUND BY ALL TERMS AND CONDITIONS OF THIS LICENSE. IF YOU DO NOT
ACCEPT THEM, DO NOT USE, COPY, MODIFY, NOR (RE)DISTRIBUTE THE
SOFTWARE, NOR ANY PART(S) THEREOF.
.
I. Definitions
.
1. "This Product" means the work (including, but not limited to,
source code, graphics, texts, and accompanying files) made
available under and governed by this version of this license
("License"), as may b
Re: another mount issue on jessie
On 02/10/2016 06:57 AM, IOhannes m zmölnig (Debian/GNU) wrote: @sebastian: could you confirm that you had to remove the PrivateTmp for each and every service you found by grepping? or did you just disable PrivateTmp for all of these services, and then no more problem occured (though by chance you might have disabled PrivateTmp for some services that would have actually worked with it). You're right: I disabled PrivateTmp for every service that wanted it (as identified by grepping for PrivateTmp in /lib/systemd) and then my mount test worked. The services in question (on my system) are: systemd-timedated rtkit-daemon colord systemd-localed systemd-machined systemd-hostnamed systemd-timesyncd cups I did the higher-fidelity test you requested like this: I removed the /etc/systemd/system/*/local.conf files I had installed for those 8 services, stopped them all with "systemctl stop", then ran "systemctl daemon-reload". At this point the mount test passes. Then for each service (one at a time) I started the service, ran the test, and stopped the service. What that showed is that if any one of those services is running, my test fails. Only if all of them are stopped does the test pass. (I got confused for a minute by cups starting colord, so stopping cups did not make the test pass until I also stopped colord.) -- Sebastian Kuzminsky
Re: GitLab B.V. to host free-software GitLab for Debian project
On Friday 22 January 2016 10:20 PM, Balasankar C wrote: > On വ്യാഴം 21 ജനുവരി 2016 07:11 വൈകു, Pirate Praveen wrote: >> I need help with integrating debconf for configuring hostname. Somehow I'm >> not able to troubleshoot the error. It seems I'm missing something simple, I >> tried to follow debconf tutorial and compare many times, but only to see a >> cryptic error message. >> >> https://gitlab.com/debian-ruby/TaskTracker/issues/41 > > This issue has been fixed. Two echo statements (for verbosity) used > before loading confmodule caused the issue. Removed them and debconf is > no longer an issue. > > Now gitlab in unstable is rc bug free and can migrate to testing (if we don't find any rc bugs in 5 days) and the version in git can now give you a fully configured (with https enabled, using letsencrypt certifictes) and up and running gitlab instance. You can try the package from https://people.debian.org/~praveen/gitlab/ right now or wait for the current version in unstable to migrate to testing (or someone files an rc bug). https://gitlab.pxq.in is a test instance that uses gitlab package in Cheers Praveen signature.asc Description: OpenPGP digital signature
Re: broken mount behaviour on jessie
Brian May writes: > I have a patched 1.6.10-2 for sid and jessie, amd64 and i386 at > https://linuxpenguins.xyz/debian/pool/main/s/schroot/ > > Haven't had a chance to test it extensively yet, but so far seems to > work. Still getting unexpected mount errors; don't have time to investigate right now. schroot.chroot.SchrootCommandError: u'E: 10mount: umount: /var/lib/schroot/mount/jessie-i386-02a65cf6-3770-44b6-a1b8-c2f38d0c090e/dev: target is busy\nE: 10mount: (In some cases useful info about processes that\nE: 10mount: use the device is found by lsof(8) or fuser(1).)\nE: jessie-i386-02a65cf6-3770-44b6-a1b8-c2f38d0c090e: Chroot setup failed: stage=setup-stop\n' -- Brian May
Bug#814382: RFH: samba -- SMB/CIFS file, print, and login server for Unix
Package: wnpp Severity: normal I request assistance with maintaining the samba package. The package description is: Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file and printer sharing with Microsoft Windows, OS X, and other Unix systems. Samba can also function as an NT4-style domain controller, and can integrate with both NT4 domains and Active Directory realms as a member server.
Bug#814384: ITP: golang-github-go-macaron-gzip -- Gzip middleware for Macaron
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: block -1 by 813903 Package name: golang-github-go-macaron-gzip Version: 0.0~git20151014 License: Apache-2.0 URL: https://github.com/go-macaron/gzip Description: Gzip middleware for Macaron Provides compress to responses for Macaron (https://github.com/go-macaron/macaron). signature.asc Description: This is a digitally signed message part.
Bug#814385: ITP: golang-github-kballard-go-shellquote -- Go utilities for performing shell-like word splitting/joining
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: affects -1 etcd Package name: golang-github-kballard-go-shellquote Version: 0.0~git20150810 Upstream Author: Kevin Ballard License: Expat URL: https://github.com/kballard/go-shellquote Description: Go utilities for performing shell-like word splitting/joining This library provides utilities for joining/splitting strings using sh's word-splitting rules. signature.asc Description: This is a digitally signed message part.
Bug#814386: ITP: python-pydot-ng -- interface to Graphviz's Dot
Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-pydot-ng Version : 1.0.0 Upstream Author : Ero Carrera * URL : https://github.com/pydot/pydot-ng * License : Expat Programming Lang: Python Description : interface to Graphviz's Dot This module provides with a full interface to create handle modify and process graphs in Graphviz’s dot language.
Bug#814387: ITP: golang-github-spacejam-loghisto -- counters and logarithmically bucketed histograms for distributed systems
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: affects -1 etcd Package name: golang-github-spacejam-loghisto Version: 1.0.0 Upstream Author: "The Cockroach Authors" License: Apache-2.0 URL: https://github.com/spacejam/loghisto Description: counters and logarithmically bucketed histograms for distributed systems A metric system for high performance counters and histograms. Unlike popular metric systems today, this does not destroy the accuracy of histograms by sampling. Instead, a logarithmic bucketing function compresses values, generally within 1% of their true value (although between 0 and 1 the precision loss may not be within this boundary). This allows for extreme compression, which allows us to calculate arbitrarily high percentiles with no loss of accuracy - just a small amount of precision. This is particularly useful for highly-clustered events that are tolerant of a small precision loss, but for which you REALLY care about what the tail looks like, such as measuring latency across a distributed system. signature.asc Description: This is a digitally signed message part.
Bug#814389: ITP: golang-github-go-macaron-binding -- request data binding and validation middleware for Macaron
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: block -1 by 813903 Package name: golang-github-go-macaron-binding Version: 0.0~git20151127 Upstream Author: "Macaron Authors" License: Apache-2.0 URL: https://github.com/go-macaron/binding Description: request data binding and validation middleware for Macaron Middleware binding provides request data binding and validation for Macaron (https://github.com/go-macaron/macaron). signature.asc Description: This is a digitally signed message part.
Re: broken mount behaviour on jessie
On Feb 10, 2016 19:34, Brian May wrote: > > Brian May writes: > > I have a patched 1.6.10-2 for sid and jessie, amd64 and i386 at > > https://linuxpenguins.xyz/debian/pool/main/s/schroot/ > > > > Haven't had a chance to test it extensively yet, but so far seems to > > work. > > Still getting unexpected mount errors; don't have time to investigate > right now. > > schroot.chroot.SchrootCommandError: u'E: 10mount: umount: > /var/lib/schroot/mount/jessie-i386-02a65cf6-3770-44b6-a1b8-c2f38d0c090e/dev: > target is busy\nE: 10mount: (In some cases useful info about > processes that\nE: 10mount: use the device is found by lsof(8) or > fuser(1).)\nE: jessie-i386-02a65cf6-3770-44b6-a1b8-c2f38d0c090e: Chroot setup > failed: stage=setup-stop\n' > -- > Brian May > This might be related to an issue I'm seeing: https://lists.debian.org/debian-devel/2016 Try stopping all systems services that use PrivateTmp=yes. -- Sebastian Kuzminsky
Bug#814391: ITP: golang-github-go-macaron-session -- session management middleware for Macaron
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: block -1 by 813903 Package name: golang-github-go-macaron-session Version: 0.0~git20151014 Upstream Author: "Macaron Authors" License: Apache-2.0 URL: https://github.com/go-macaron/session Description: session management middleware for Macaron Middleware session provides session management for Macaron (https://github.com/go-macaron/macaron). It can use many session providers, including memory, file, Redis, Memcache, PostgreSQL, MySQL, Couchbase, Ledis and Nodb. signature.asc Description: This is a digitally signed message part.
Bug#814392: ITP: golang-gopkg-redis.v2 -- Redis client for Golang
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: block 814391 by -1 Package name: golang-gopkg-redis.v2 Version: 2.3.2 Upstream Author: "The Redis Go Client Authors" License: BSD-3-Clause URL: https://github.com/go-redis/redis Description: Redis client for Golang This package provides Redis client for Golang. signature.asc Description: This is a digitally signed message part.
Fwd: Associating packages with file types using appstream succeeded
Hi, since I think this result of the Debian Med sprint might be of more general interest thus I'm simply forwarding to debian-devel what was posted on Debian Med list. Thread start was here: https://lists.debian.org/debian-med/2016/02/msg00049.html Kind regards Andreas. - Forwarded message from Charles Plessy - Date: Thu, 11 Feb 2016 11:52:22 +0900 From: Charles Plessy To: debian-...@lists.debian.org Subject: Re: Associating packages with file types using appstream succeeded Le Wed, Feb 10, 2016 at 07:15:02PM +0100, Petter Reinholdtsen a écrit : > > The goal was to use appstream to announce file format support in a > non-GUI package (aka one without a .desktop file), and we used the khmer > package as an example. It is now listed as a package supporting the > application/vnd.oxli.countgraph MIME type: > > % appstreamcli what-provides mimetype application/vnd.oxli.countgraph > Identifier: oxli [generic] > Name: khmer > Summary: in-memory DNA sequence kmer counting, filtering & graph traversal > Package: khmer > > % > > To do this, we added debian/khmer.metainfo.xml with the following > content and installed it in /usr/share/appdata/: > > > > oxli > MIT > khmer > in-memory DNA sequence kmer counting, filtering & graph > traversal > > > khmer is a library and suite of command line tools for working > with DNA sequence. It is primarily aimed at short-read > sequencing data such as that produced by the Illumina > platform. khmer takes a k-mer-centric approach to sequence > analysis, hence the name. > > > > application/vnd.oxli.countgraph > > Hi Petter, this is a great result, especially now that it is easy for any project to submit new media types to the IANA. I added the following information to the MimeTypesSupport page in the Debian wiki: Packages can declare support for media types using the AppStream system, by placing metainfo XML files in /usr/share/appdata/, with names such as .metainfo.xml. Commands like appstreamcli will then be able to report which package supports which media types, and package managers will be able to suggest the package for installation. https://wiki.debian.org/MimeTypesSupport#For_package_installation Corrections or improvements are welcome ! Have a nice day, -- Charles - End forwarded message - -- http://fam-tille.de
