Bug#876963: ITP: elastalert -- easy and flexible alerting with Elasticsearch
Package: wnpp Severity: wishlist Owner: Sophie Brun * Package name: elastalert Version : 0.1.20 Upstream Author : Yelp * URL : https://github.com/Yelp/elastalert * License : Apache-2.0 Programming Lang: Python Description : easy and flexible alerting with Elasticsearch It is a simple framework for alerting on anomalies, spikes, or other patterns of interest from data in Elasticsearch. ElastAlert is designed to be reliable, highly modular, and easy to set up and configure. It works by combining Elasticsearch with two types of components, rule types and alerts. Elasticsearch is periodically queried and the data is passed to the rule type, which determines when a match is found. When a match occurs, it is given to one or more alerts, which take action based on the match. This is configured by a set of rules, each of which defines a query, a rule type, and a set of alerts. .
Re: ftp master uploads disappearing?
Hi, On Tue, Sep 26, 2017 at 07:21:51PM +0200, Adam Borowski wrote: > > > Indeed, dupload worked right ahead. Thanks. > > > > How odd. Is there a bug filed against dput ? > > Also note there's also dput-ng. I like dput-ng a lot and I'm using it. However, I'm *frequently* observing failed uploads when sitting behind weak connections. I guess it is a bit hard to debug and so instead of filing a bug report was to rsync to some host with a good connection and dput(-ng) from there. BTW, I did several uploads today and a single one of statsmodels did not arrived somewhere - seems the same case as OP had. I do not have the power as Julien to try ssh usper.debian.org grep statsmodels and so I tried again with a source upload. To answer Mattias question why not using source uploads all the time: Once I have build the package to see whether all those lintian issues are fixed I want to fix I have a sensible package to upload and somehow this workflow to upload what is just there remains. Lets see what happens now but I suspect that there is some issue and wanted to provide an additional example. Kind regards Andreas. -- http://fam-tille.de
Re: ftp master uploads disappearing?
I need to correct myself On Wed, Sep 27, 2017 at 02:46:00PM +0200, Andreas Tille wrote: > BTW, I did several uploads today and a single one of statsmodels did > not arrived somewhere - seems the same case as OP had. The according mails arrived right after I wrote this in my inbox - may be only the mails were delayed ... Sorry for that part of my mail - the dput-ng issue remains true Andreas. -- http://fam-tille.de
Bug#876997: ITP: node-flush-write-stream -- A write stream constructor that supports a flush function
Package: wnpp Severity: wishlist Owner: Preyass Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-flush-write-stream Version : 1.0.2 Upstream Author : Mathias Buus (@mafintosh) * URL : https://github.com/mafintosh/flush-write-stream * License : Expat Programming Lang: JavaScript Description : A write stream constructor that supports a flush function This write stream constructor supports a flush function that is called before finish is emitted . Node.js is an event-based server-side JavaScript engine. This module is a dependency of npm, nodejs package manager I would like to join javascript maintenance team. Praveen has already agreed to sponsor this package.
debian/control file: how to selectively suppress recommends?
Dear fellow Debianauts, right now I am in the process of migrating my selection of manually installed packages to a freshly debootstrapped install using a set of meta-packages built with equivs. While that works nice and well, in some instances, I would like to limit the number of recommends being pulled in, without turning recommends off completely (the meta-packages themselves use Recommends:dependencies). So the --no-install-recommends parameter or APT::Install-Recommends "0" are of no help in this case. Any ideas how to block installation of only some packages' recommendations? #Best Regards/Marcel Partap
Re: ftp master uploads disappearing?
Andreas Tille wrote: [...] > To answer Mattias question why not using source uploads all the time: > Once I have build the package to see whether all those lintian issues > are fixed I want to fix I have a sensible package to upload and somehow > this workflow to upload what is just there remains. [...] Hello, I am also doing regular local builds, because I like being able to a) use debdiff to the previous upload and b) compare buildlogs. This is not a blocker for source-only uploads, though, you can generate a source-only changes file from the full_build_changes file like this: mergechanges --source -f exim4_4.89-7_amd64.changes exim4_4.89-7_amd64.changes hth, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Re: Compressed apt index files by default?
On Sat, Sep 09, 2017 at 04:48:29PM +0200, Julian Andres Klode wrote:
> Hi,
>
> I'd like us to try out using LZ4 compressed index files in
> /var/lib/apt/lists for the next APT release series, starting
> in October, after the release of Ubuntu 17.10 "artful".
I'll actually be turning this on in the first half next
week, either on Oct 1st or on Oct 3rd, if I manage to fix
the tests in the test suite that expect uncompressed ones :)
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Re: Compressed apt index files by default?
On Sat, Sep 09, 2017 at 04:48:29PM +0200, Julian Andres Klode wrote:
> Hi,
>
> I'd like us to try out using LZ4 compressed index files in
> /var/lib/apt/lists for the next APT release series, starting
> in October, after the release of Ubuntu 17.10 "artful".
>
> This is done by swapping the default for Acquire::gzipIndexes
> from false to true.
>
> On my system, this compresses /var/lib/apt/lists
> from 1.3 GB down to 241 MB, which is a lot of space.
There's been a mistake in testing methodology, I compared
with Contents files uncompressed as well. Real values are more
like
188 vs 75 MB for just Packages
446 vs 278 MB for all files (Sources too)
so, like a 60% saving for systems without apt-file, and a
40% saving for systems with apt-file installed.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Bug#877017: ITP: python-rstr -- easily generate random strings of various types
Package: wnpp Severity: wishlist Owner: Ximin Luo * Package name : python-rstr Version : 2.2.6 Upstream Author : Brendan McCollam * URL : https://bitbucket.org/leapfrogdevelopment/rstr/ * License : BSD-3-Clause Programming Lang: Python Description : Easily generate random strings of various types rstr is a helper module for easily generating random strings of various types. It could be useful for fuzz testing, generating dummy data, or other applications. It has no dependencies outside the standard library, and is compatible with Python 3. The basic method of rstr is rstr(). At a minimum, it requires one argument, an alphabet of characters from which to create a string. Inspired by the Java library of the same name, the xeger() method allows users to create a random string from a regular expression. You can combine rstr with Python's built-in string formatting to produce strings that fit a variety of templates.
Re: ftp master uploads disappearing?
Hi, On Wed, Sep 27, 2017 at 07:38:22PM +0200, Andreas Metzler wrote: > Andreas Tille wrote: > [...] > > To answer Mattias question why not using source uploads all the time: > > Once I have build the package to see whether all those lintian issues > > are fixed I want to fix I have a sensible package to upload and somehow > > this workflow to upload what is just there remains. > [...] > > Hello, > > I am also doing regular local builds, because I like being able to > a) use debdiff to the previous upload and b) compare buildlogs. > > This is not a blocker for source-only uploads, though, you can generate > a source-only changes file from the full_build_changes file like this: > > mergechanges --source -f exim4_4.89-7_amd64.changes exim4_4.89-7_amd64.changes Nice hint in general. However, in the statsmodels case it was an upload to new (due to additional binary packages) - it does not permit source only uploads. Kind regards Andreas. -- http://fam-tille.de
Bug#877019: ITP: nix -- Purely functional package manager
Package: wnpp Severity: wishlist Owner: Kai Harries * Package name: nix Version : 1.1.15 Upstream Author : Eelco Dolstra * URL : https://nixos.org/nix/ * License : LGPL v2.1 Programming Lang: C++, Shell, C, Perl Description : Purely functional package manager A powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible. Nix provides atomic upgrades and rollbacks, side-by-side installation of multiple versions of a package, multi-user package management and easy setup of build environments. I personally use it to install software that is not part of Debian or software that I need in a newer version. My packaging efforts can be found here [1]. I am looking for a sponsor. [1] https://github.com/KaiHa/nix-debian/releases
Bug#877030: ITP: pat -- Winlink client with basic messaging capabilities
Package: wnpp Severity: wishlist Owner: Antoine Beaupre * Package name: pat Version : 0.3.0 Upstream Author : Martin Hebnes Pedersen * URL : http://getpat.io/ * License : MIT (Expat) Programming Lang: Go Description : Winlink client with basic messaging capabilities Pat is a cross platform Winlink client with basic messaging capabilities. It is the primary sandbox/prototype application for the wl2k-go project, and provides both a command line interface and a responsive (mobile-friendly) web interface. It is mainly developed for Linux, but are also known to run on OS X, Windows and Android. Features * Message composer/reader (basic mailbox functionality). * Auto-shrink image attachments. * Post position reports with location from local GPS, browser location or manual entry. * Rig control (using hamlib) for winmor PTT and QSY. * CRON-like syntax for execution of scheduled commands (e.g. QSY or connect). * Built in http-server with web interface (mobile friendly). * Git style command line interface. * Listen for P2P connections using multiple modes concurrently. * AX.25, telnet, WINMOR and ARDOP support. * Experimental gzip message compression I have used pat and it works pretty well. It's the first time I'm able to use WinLink in a meaningful way in Linux. I remember trying the Windows binary in Wine a while back and it was really painful. Now there's a nice interface, both web GUI and commandline. I have yet to test AX-25, but i'm hopeful to get good results. There are a lot of vendored dependencies present in the source, however: github.com/bndr/gotabulate github.com/elazarl/go-bindata-assetfs github.com/fsnotify/fsnotify github.com/gorhill/cronexpr github.com/gorilla/context github.com/gorilla/mux github.com/gorilla/websocket github.com/howeyc/gopass github.com/jteeuwen/go-bindata github.com/la5nta/wl2k-go github.com/mattn/go-runewidth github.com/microcosm-cc/bluemonday github.com/nfnt/resize github.com/peterh/liner github.com/spf13/pflag golang.org/x/crypto golang.org/x/net golang.org/x/sys golang.org/x/text I'm unsure which one are already in debian and which ones are not. Of the above, only the following are missing from Debian, which is pretty awesome: github.com/bndr/gotabulate github.com/la5nta/wl2k-go and the latter is basically the library backend for pat. I would be happy to comaintain this or delegate maintainership: just scratching an itch here. I would also love to get help from the golang packages as I have never packaged golang stuff before. An equivalent free software of this is "paclink-unix", but it's apparently less user-friendly. A comparative of different winlink clients is available here: https://www.winlink.org/ClientSoftware
Re: debian/control file: how to selectively suppress recommends?
On Wed, Sep 27, 2017 at 10:28 PM, Marcel Partap wrote: > Any ideas how to block installation of only some packages' recommendations? I assume that adding Breaks or Conflicts to your meta-packages for the packages you do not like should do the trick. You can even go one step further and add Provides for the cases where the packages you do not like are Depended on by some package in Debian. For example some desktops may Depend on CD/DVD related tools but your computer might not have a CD/DVD drive. With versioned Provides now being supported you can even prevent versioned Depends being installed. -- bye, pabs https://wiki.debian.org/PaulWise
Re: ftp master uploads disappearing?
Quoting Andreas Metzler (2017-09-27 19:38:22) > Andreas Tille wrote: > [...] > > To answer Mattias question why not using source uploads all the time: > > Once I have build the package to see whether all those lintian issues > > are fixed I want to fix I have a sensible package to upload and somehow > > this workflow to upload what is just there remains. > [...] > > Hello, > > I am also doing regular local builds, because I like being able to > a) use debdiff to the previous upload and b) compare buildlogs. > > This is not a blocker for source-only uploads, though, you can generate > a source-only changes file from the full_build_changes file like this: > > mergechanges --source -f exim4_4.89-7_amd64.changes exim4_4.89-7_amd64.changes or, if you are using sbuild to build your package, you can use the --source-only-changes option which generates a .changes file for a source-only upload alongside the regular .changes file. It might also not hurt to generate a source-only .changes file for every build with sbuild by putting this into your ~/.sbuildrc: $source_only_changes = 1; cheers, josch signature.asc Description: signature
Re: pasting license text into debian/copyright
On Thursday, 21 September 2017 16:11:52 CEST Andreas Tille wrote:
> May be if cme would have the same effect as wrap-and-sort there is at
> least no disagreement between the users of both tools any more (leaving
> those who are not happy with either of them :-P ).
Unfortunately, wrap-and-sort has its own way of sorting: special entries (i.e.
that do not begin with letters) are sorted after "normal" entries. So
dependencies like "${misc:Depends}" are sorted after package dependencies.
Usually, sort algorithms do the reverse. May be wrap-and-sort should be called
wrap-and-sort-ish :-p
I don't really mind this weird order except emulating this requires adding yet
another special case (aka wart) to the way dpkg is handled in cme.
All the best
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
