Processed: merging bugreporst because they are the same
Processing commands for cont...@bugs.debian.org: > reassign 858073 bash Bug #858073 [general] apparent freeze when exiting text session on second vt while X is running on first vt Bug reassigned from package 'general' to 'bash'. Ignoring request to alter found versions of bug #858073 to the same values previously set Ignoring request to alter fixed versions of bug #858073 to the same values previously set > merge 858073 791342 Bug #858073 [bash] apparent freeze when exiting text session on second vt while X is running on first vt Bug #858073 [bash] apparent freeze when exiting text session on second vt while X is running on first vt Marked as found in versions bash/4.3-11. Bug #791342 [bash] bash: A system freeze is possible when exiting a terminal Merged 791342 858073 > thanks Stopping processing here. Please contact me if you need assistance. -- 791342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791342 858073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858216: ITP: python-xapian-haystack -- Xapian backend for Django-Haystack
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-xapian-haystack Version : 2.1.0 Upstream Author : Jorge C. Leitão * URL : https://github.com/notanumber/xapian-haystack/ * License : GPL-2 Programming Lang: Python Description : Xapian backend for Django-Haystack Xapian-haystack is a backend of Django-Haystack for the Xapian search engine. It provides all the standard features of Haystack: * Weighting * Faceted search (date, query, etc.) * Sorting * Spelling suggestions * EdgeNGram and Ngram (for autocomplete) The endswith search operation is not supported. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAljO9EURHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90Wp1twf/TWkqzi4B7i18gI/7NqB2J8jf4FOKDByO dzMfiHFe06BfcjzdUKttGCPCHFWIY76sxU8N4/WJohJnNMeEuu7hnat35NUiXnPM bjoD0feB6eaQXX7BWcl6J0aRSFtkE6oQkw2re9IgZVz1LnBMPyt/qjCHf7ZRT7ax rctdM++TuOMQ9R2OaAO2yeG61cIbSbIk+7cIuHNYCQn2DmctuTKH9DVIvNwX82lp /Ur2DswLpo94+09aFy3Dn2yn6DQwRrzUEBjNLMGTsmYtB8Fc2X0t5CI8RD82d5ip dQkECX7uXXrJtV1YHVnNiGOiHKNSrx42KOJGKzJIMDLkxAOJmCLdug== =qCxT -END PGP SIGNATURE-
Bug#858229: ITP: passh -- passh: a pass fork - stores, retrieves, generates, and synchronizes passwords securely.
Package: wnpp Severity: wishlist Owner: Adrian Alves * Package name: passh Version : 1.7.1 Upstream Author : Ivan Ariel Barrera Oro * URL : https://github.com/HacKanCuBa/passh * License : GPL-3 Programming Lang: bash Description : passh: a pass fork - stores, retrieves, generates, and synchronizes passwords securely. Pass is a simple password store. This fork changes a few things while trying to maintain most of it intact, specially the core idea. I will keep pulling pass commits, and also pushing my modifications to them. . Forked from pass https://git.zx2c4.com/password-store.
Re: Bug#858229: ITP: passh -- passh: a pass fork - stores, retrieves, generates, and synchronizes passwords securely.
On 03/20/2017 06:18 AM, Adrian Alves wrote: > Package: wnpp > Severity: wishlist > Owner: Adrian Alves > > * Package name: passh > Version : 1.7.1 > Upstream Author : Ivan Ariel Barrera Oro > * URL : https://github.com/HacKanCuBa/passh > * License : GPL-3 > Programming Lang: bash > Description : passh: a pass fork - stores, retrieves, generates, and > synchronizes passwords securely. > > Pass is a simple password store. This fork changes a few > things while trying to maintain most of it intact, > specially the core idea. I will keep pulling pass commits, > and also pushing my modifications to them. It would be great if you could go into a bit more detail why this fork is needed? "changes a few things" is _very_ unspecific. I've had a look at the upstream website, and found this: https://github.com/HacKanCuBa/passh#user-content-changes-from-pass-master So apparently the only real difference (apart from branding) is extension handling. This should definitely go in the package description to allow people to decide which one they'd want to install. And while that shouldn't be part of the package description later on, a short comment in the ITP why a fork was required would also be nice. Did the original project just not want to merge this? What's the use case for these changes that can't be supported by the original? Also, a minor note, unrelated to Debian packaging: the fork claims in https://github.com/HacKanCuBa/passh#license that the original is GPL-2 and that the fork is GPL-3+. If that were actually true, the fork would be a license violation. Luckily for the fork from reading the COPYING file of the original, that is is actually licensed under GPL-2+ (not just GPL-2), so forking as GPL-3+ is fine. (That said, while I generally like the GPL-3, forking a GPL-2+ project under GPL-3+ does not allow the original project to easily merge back changes made in the fork, they'd first have to get explicit permission.) Regards, Christian
