Re: Bug#748583: ITP: get directories of configuration files -- get directories of configuration files
On Sun, 18 May 2014 18:29:39 +0200 Jonas Smedegaard wrote: > Package: wnpp > Severity: wishlist > Owner: Jonas Smedegaard > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > * Package name: get directories of configuration files Maybe reportbug needs to check for whitespace in proposed package names ... libfile-config-dir-perl ? libfile-configdir-perl ? > Version : 0.013 > Upstream Author : Jens Rehsack > * URL : https://metacpan.org/release/File-ConfigDir > * License : Artistic or GPL-1+ > Programming Lang: Perl > Description : get directories of configuration files > > File::ConfigDir is a helper for installing, reading and finding > configuration file locations. It's intended to work in every > supported Perl5 environment and will always try to Do The Right > Thing(tm). > > This module is needed (indirectly) by recent releases of > libmoox-options-perl. > > It will be maintained in the Debian Perl team. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#748654: ITP: gopacket -- packet capturing and decoding library for Go
Package: wnpp Owner: Hilko Bengen Severity: wishlist * Package name: gopacket Version : 1.0.12-1 Upstream Author : Andreas Krennmair; Google Inc. * URL or Web page : http://code.google.com/p/gopacket/ * License : BSD-3-clause Description : packet capturing and decoding library for Go The gopacket library provides various bindings for reading packets off the wire, logic for decoding packet protocols, TCP stream reassembly. -- 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/878upyoztu@msgid.hilluzination.de
Bug#748677: ITP: arrowhead -- micro-framework for flowchart-like computing
Package: wnpp Severity: wishlist Owner: Zygmunt Krynicki Package name: arrowhead Version : 1.0 Upstream Author : Zygmunt Krynicki URL : https://github.com/zyga/arrowhead/ License : BSD-3-clause Programming Lang: python Description : micro-framework for flowchart-like computing Arrowhead is a framework for constructing flow charts composed of steps connected by (possibly) conditional branches. Such flows can be executed, inspected (at runtime) and visualized (for documentation and verification) . The idea of flowchart computing is designed in a way that mimics a hand-made drawing, typically on a white-board or a piece of paper, that describes some process as a graph of interconnected steps. . Traditionally, once designed, the process is implemented as a collection of functions and classes. Very often the original idea of the process was supposed to work lost, especially after making changes over time. Usually it is impossible to easily reconstruct the initial idea from a complex implementation of that idea. . As an added issue, it is non-trivial to create derivative processes that somehow override, change, replace or remove parts of the process. This can affect one step or a particular group of steps. . The arrowhead framework aims to address both problems. . This package contains the python3 version of this library. This package is an upcoming dependency of the plainbox package. Is also useful to the re-emerging field of dataflow-driven computing and all kinds of flow computing in general. There are no similar packages in Debian that I could find (this is why I also created arrowhead in the first place). I will gladly co-maintain it in DPMT, along with my other packages. -- 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/20140519150859.10542.3906.reportbug@iffy
Re: Redefining critical bug severity (was: how to deal with a missed so bump already uploaded ?)
On Sat, May 17, 2014 at 08:46:20AM -0700, Russ Allbery wrote: > The confusion seems to always be around the "unrelated software" part of > that definition. The intended meaning is completely unrelated software on > the system, indicating a package that's mangling the system in some > fundamental way, but I've frequently seen people believe, sincerely, that > reverse dependencies, Perl programs that use a buggy module, or X programs > on a system with a buggy video driver qualify as unrelated software. > > This makes me think that part of the bug definition is adding more > confusion than clarity. Should we just drop it? I must admit I never really understood the meaning of unrelated software and it does cause confusion. It could mean anything from anything that isn't in that specific package (so includes dependencies), or anything except itself and depencies (so includes suggests), reverse depends or something else. > makes the entire system unusable, or causes serious data loss, or > introduces a security hole on systems where you install the package > > is closer to how we actually use the severity, and would avoid some of > these bug severity arguments. I agree. I also agree that there isn't, for me, much difference between the top three severities on how I treat the bugs. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- 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/20140519210509.ge26...@enc.com.au
Bug#748719: reportbug: check wnpp reports for spaces in proposed package names
Package: reportbug Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org On Mon, May 19, 2014 at 4:12 PM, Neil Williams wrote: > On Sun, 18 May 2014 18:29:39 +0200 Jonas Smedegaard wrote: > >> Package: wnpp >> Severity: wishlist >> Owner: Jonas Smedegaard >> >> * Package name: get directories of configuration files > > Maybe reportbug needs to check for whitespace in proposed package names Indeed, please add this. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6GXFe3c2J7o7iFuYazvrcq_oLUNCdcSw8x8O+=t15m...@mail.gmail.com
Re: Redefining critical bug severity (was: how to deal with a missed so bump already uploaded ?)
On Sat, 17 May 2014, Russ Allbery wrote: > I think defining critical as: > > makes the entire system unusable, or causes serious data loss, or > introduces a security hole on systems where you install the package > > is closer to how we actually use the severity, and would avoid some of > these bug severity arguments. I'm OK with either adding additional clarification or adopting this language. In my opinion, the wording of the severity levels is really there to give bug submitter guidance to the initial severity they select; ideally it represents the consensus view of most maintainers. If it doesn't represent the consensus view, I'd like to change it. Individual maintainers should feel free[0] to use the severity levels of bugs to set their own personal priority without regard to what the definition says.[1] 0: With the exception of whether bugs have severity >= serious; that can be overridden by the RMs. 1: But they shouldn't be surprised when a submitter follows the "consensus view". -- Don Armstrong http://www.donarmstrong.com Life would be way easier if I were easier. -- a softer world #473 http://www.asofterworld.com/index.php?id=473 -- 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/20140520024328.gb23...@teltox.donarmstrong.com
Re: Bug#748583: ITP: get directories of configuration files -- get directories of configuration files
On Mon, May 19, 2014 at 09:12:40AM +0100, Neil Williams wrote: > Maybe reportbug needs to check for whitespace in proposed package names ... And all the other package name requirements from policy. -- 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/20140520065159.ga8...@bryant.redmars.org
