Package: wnpp
Severity: wishlist
Owner: Lev Lamberov
* Package name: py-isort-el
Version : 2016.1
Upstream Author : Friedrich Paetzke
* URL : https://github.com/paetzke/py-isort.el
* License : GPL-3+
Programming Lang: Emacs Lisp
Description : use isort
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: github-release
Version: 0.6.2
Upstream Author: Nicolas Hillegeer
URL: https://github.com/aktau/github-release
Latest Release: https://github.com/aktau/github-release/archive/v0.6.2
.
Control: rename -1 ITP: gnome-recipes: Recipe application for GNOME
On Sun, Feb 12, 2017 at 10:30 AM, Simon McVittie wrote:
> On Sun, 12 Feb 2017 at 09:44:53 -0500, Jeremy Bicha wrote:
>> On Sun, Feb 12, 2017 at 9:22 AM, Simon McVittie wrote:
>> > I think this is too generic. The upstream name i
Ben Finney writes:
> Russ Allbery writes:
>> I really want something that will pass Lintian completely but that
>> dput will refuse to upload, which is what UNRELEASED currently
>> accomplishes.
> Wookey writes:
>> 1. I really dislike dch's enthusiasm for putting in 'UNRELEASED'. It
>> gives
Simon McVittie writes:
> On Mon, 13 Feb 2017 at 09:42:32 +1100, Ben Finney wrote:
> > I'm in agreement with Ian that the “write the documentation
> > (including the changelog) along with the change it describes”
> > workflow should have full support from our tools.
>
> Are you making the stronger
On Mon, 13 Feb 2017 at 09:42:32 +1100, Ben Finney wrote:
> Simon McVittie writes:
> > This works fine if every commit is final and immutable and is sent
> > directly to the master VCS immediately, but works very poorly if you
> > are proposing commits for someone else to merge at a later dat
Russ Allbery writes:
> I really want something that will pass Lintian completely but that
> dput will refuse to upload, which is what UNRELEASED currently
> accomplishes.
Wookey writes:
> 1. I really dislike dch's enthusiasm for putting in 'UNRELEASED'. It
> gives me nothing I wanted, and just
Simon McVittie writes:
> I think you're the only person I've ever seen using unfinalized
> changelog entries for Debian packages.
I think the fact you don't know we're using this workflow isn't very
informative :-)
> Broadly, the two extremes of workflows for Debian packages' changelogs
> maint
Hi there,
On Sun, 12 Feb 2017 14:11:12 +, Simon McVittie wrote:
> On Sun, 12 Feb 2017 at 12:48:35 +, Ian Jackson wrote:
> > What do people think ?
>
> I think you're the only person I've ever seen using unfinalized
> changelog entries for Debian packages.
FWIW, I am another user of this
On Sun, Feb 12, 2017 at 06:34:26PM +, Wookey wrote:
> But the
> UNRELEASED/'dch -r' thing pisses me off on a daily basis, and this
> seemed like the time to point out that some of us don't find it all
> helpful. From that POV, moving it from suite to version would
> definitely be less annoying.
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-django-dynamic-scraper
Version : 0.11.3
Upstream Author : Holger Drewes
* URL : https://github.com/holgerd77/django-dynamic-scraper
* Lic
On 2017-02-12 12:48 +, Ian Jackson wrote:
> We do not seem to have a coherent approach to how to handle
> debian/changelog in trees (eg, vcs branches) which are not yet ready
> for upload.
>
> See below two examples of things done differently.
> The questions are:
>
> Q1. Should the suite in
Ian Jackson writes:
> Q2: The information in the trailer line of the changelog entry in a new
> branch is not meaningful. Depending on the vcs etc. in use, it can
> cause pointless merge conflicts. Often the information is quite wrong:
> for example, a date which is earlier than the most recent
On Sun, Feb 12, 2017 at 02:11:12PM +, Simon McVittie wrote:
> On Sun, 12 Feb 2017 at 12:48:35 +, Ian Jackson wrote:
> > Q1. Should the suite in the changelog entry be UNRELEASED,
> > or the suite at which the vcs branch is targeted ?
>
> If you're trying to change common practice (bein
On Sun, Feb 12, 2017 at 4:09 PM, Alec Leamas wrote:
>
>
> On 12/02/17 13:47, Simon McVittie wrote:
>
> Hi, thanks for thoughts!
>
>
>> /lib/udev/??-mm-*.rules are probably of interest. ModemManager
>> implements a whitelist (devices that are definitely modems), a blacklist
>> (devices that are def
On Sun, 12 Feb 2017 at 09:44:53 -0500, Jeremy Bicha wrote:
> On Sun, Feb 12, 2017 at 9:22 AM, Simon McVittie wrote:
> > I think this is too generic. The upstream name is Recipes, and that name is
> > fine within the context of GNOME
>
> Thanks. I requested that the developer change the name to gn
On Sun, Feb 12, 2017 at 1:47 PM, Simon McVittie wrote:
> On Sun, 12 Feb 2017 at 11:33:22 +0100, Alec Leamas wrote:
>> On 12/02/17 11:16, Bastien Roucaries wrote:
>> > Last time braille stuff break (brick) a FPGA device with a jtag adaptator
>> > (serial to jtag). So i really dislike package that
On 12/02/17 13:47, Simon McVittie wrote:
Hi, thanks for thoughts!
/lib/udev/??-mm-*.rules are probably of interest. ModemManager
implements a whitelist (devices that are definitely modems), a blacklist
(devices that are definitely not modems), and a greylist (devices that
might be modems, bu
Control: forwarded -1 https://bugzilla.gnome.org/778531
On Sun, Feb 12, 2017 at 9:22 AM, Simon McVittie wrote:
> I think this is too generic. The upstream name is Recipes, and that name is
> fine within the context of GNOME (particularly when its machine-readable
> name is actually org.gnome.Reci
Hello Ian,
On Sun, Feb 12, 2017 at 12:48:35PM +, Ian Jackson wrote:
> Q1. Should the suite in the changelog entry be UNRELEASED,
> or the suite at which the vcs branch is targeted ?
> [...]
> Q1: Replacing the suite with "UNRELEASED" means that it is not
> possible to distinguish a branch
On Sun, Feb 12, 2017 at 12:48:35PM +, Ian Jackson wrote:
> We do not seem to have a coherent approach to how to handle
> debian/changelog in trees (eg, vcs branches) which are not yet ready
> for upload.
True. We also don't have one recommended way how to write debian/rules, how to
build pack
On Sun, 12 Feb 2017 at 07:55:18 -0500, Jeremy Bicha wrote:
> Package Name: recipes
I think this is too generic. The upstream name is Recipes, and that name is
fine within the context of GNOME (particularly when its machine-readable
name is actually org.gnome.Recipes), but within Debian/Ubuntu it w
On Sun, 12 Feb 2017 at 12:48:35 +, Ian Jackson wrote:
> What do people think ?
I think you're the only person I've ever seen using unfinalized
changelog entries for Debian packages.
If I'm understanding correctly, your motivation to do so is that you
have a strong belief that building a Debia
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package Name: recipes
Version: 0.12-1
Upstream Author: Matthias Clasen
URL: https://wiki.gnome.org/Apps/Recipes
License: GPL-3+
Description: Recipe application for GNOME
GNOME Recipes is an easy-to-use application that wi
We do not seem to have a coherent approach to how to handle
debian/changelog in trees (eg, vcs branches) which are not yet ready
for upload.
See below two examples of things done differently.
The questions are:
Q1. Should the suite in the changelog entry be UNRELEASED,
or the suite at which t
On Sun, 12 Feb 2017 at 11:33:22 +0100, Alec Leamas wrote:
> On 12/02/17 11:16, Bastien Roucaries wrote:
> > Last time braille stuff break (brick) a FPGA device with a jtag adaptator
> > (serial to jtag). So i really dislike package that bind to all char device.
> >
> > Btw if you do this you need
Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin
* Package name: sphinx-celery
Version : 1.3.1
Upstream Author : Ask Solem
* URL : https://github.com/celery/sphinx_celery
* License : BSD
Programming Lang: Python
Description : Sphinx Celery th
On 12/02/17 11:16, Bastien Roucaries wrote:
Last time braille stuff break (brick) a FPGA device with a jtag adaptator
(serial to jtag). So i really dislike package that bind to all char device.
>
> Btw if you do this you need a break on braille stuff...
Now, we are not talking about all
Le 11 février 2017 11:46:14 GMT+01:00, Alec Leamas a
écrit :
>
>
>On 11/02/17 10:29, Bastien Roucaries wrote:
>> Le 10 février 2017 16:13:15 GMT+01:00, Alec Leamas
> a écrit :
>>> Dear list,
>[cut]
>>> Proposed /dev/ permissions after installing lirc:
>>>
>>> - The /dev/lirc? devices are set us
29 matches
Mail list logo
