Bug#924368: I'll take it
On Tue, 12 Mar 2019 16:09:35 +0100 Adam Borowski wrote:
> Control: retitle -1 ITA: btrfs-progs -- Checksumming Copy on Write Filesystem
> utilities
> Control: owner -1 !
>
> As a long-time user ("thou shalt have no other filesystems before btrfs")
> and an occassional contributor, I can take it.
>
Thanks Adam for taking care of it!
Just a side note: I think I sponsored a lot of backports for Nicholas in the
past,
he is a good contributor, and he sends patches upstream and to Debian packaging
(dated 2017).
Maybe you can both work on the package, he is a DM so he might even upload by
himself if you
feel comfortable with his work (Nicholas please tell us if you are still
interested in btrfs!)
In any case, two is better than one, specially when one is an upstream
contributor and Debian maintainer :)
I hope to see Nicholas back in the team :)
G.
Bug#924917: ITP: golang-github-gliderlabs-ssh -- Easy SSH servers in Golang
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-gliderlabs-ssh Version : 0.1.3-1 Upstream Author : Glider Labs * URL : https://github.com/gliderlabs/ssh * License : BSD-3-clause Programming Lang: Go Description : Easy SSH servers in Golang This Go package wraps the crypto/ssh package (https://godoc.org/golang.org/x/crypto/ssh) with a higher-level API for building SSH servers. The goal of the API was to make it as simple as using net/http (https://golang.org/pkg/net/http/), so the API is very similar. This package is in the dependency tree of Lazygit (#908894) and it depends on another package: "golang-github-anmitsu-go-shlex-dev" (#924783)
Bug#924917: RFS: golang-github-gliderlabs-ssh/0.1.3-1
Dear Go team, I am looking for a sponsor for the package "golang-github-gliderlabs-ssh". This package is a prerequisite for upcoming package "lazygit" (#908894). I pushed to our team's Salsa: https://salsa.debian.org/go-team/packages/golang-github-gliderlabs-ssh Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated. This package depends on another package: "golang-github-anmitsu-go-shlex-dev" (#924783)
Bug#924918: ITP: golang-github-stvp-roll -- Simple(er) Rollbar client for Go
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-stvp-roll Version : 0.0~git20170522.3627a5c-1 Upstream Author : Stovepipe Studios * URL : https://github.com/stvp/roll * License : Expat Programming Lang: Go Description : Simple(er) Rollbar client for Go roll is a basic Rollbar client for Go that reports errors and logs messages. It automatically builds stack traces and also supports arbitrary traces. All errors and messages are sent to Rollbar synchronously. This package is in the dependency tree of Lazygit (#908894)
Bug#924368: I'll take it
On Mon, Mar 18, 2019 at 12:53:12PM +0100, Gianfranco Costamagna wrote:
> On Tue, 12 Mar 2019 16:09:35 +0100 Adam Borowski wrote:
> > Control: retitle -1 ITA: btrfs-progs -- Checksumming Copy on Write
> > Filesystem utilities
> > Control: owner -1 !
> >
> > As a long-time user ("thou shalt have no other filesystems before btrfs")
> > and an occassional contributor, I can take it.
> >
>
> Thanks Adam for taking care of it!
> Just a side note: I think I sponsored a lot of backports for Nicholas in the
> past,
> he is a good contributor, and he sends patches upstream and to Debian
> packaging (dated 2017).
>
> Maybe you can both work on the package, he is a DM so he might even upload by
> himself if you
> feel comfortable with his work (Nicholas please tell us if you are still
> interested in btrfs!)
That might work, yeah.
On the other hand, even though there's some quite obvious work to do, doing
disruptive changes to an udeb-producing package during the freeze would be a
very bad idea, thus I plan no uploads anytime soon, doing all changes in
git.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄
Bug#924918: RFS: golang-github-stvp-roll/0.0~git20170522.3627a5c-1
Dear Go team, I am looking for a sponsor for the package "golang-github-stvp-roll". This package is a prerequisite for upcoming package "lazygit" (#908894). I pushed to our team's Salsa: https://salsa.debian.org/go-team/packages/golang-github-stvp-roll Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924922: ITP: golang-gopkg-src-d-go-billy.v4 -- The missing interface filesystem abstraction for Go
Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla
* Package name: golang-gopkg-src-d-go-billy.v4
Version : 4.3.0-1
Upstream Author : source{d}
* URL : https://github.com/src-d/go-billy
* License : Apache-2.0
Programming Lang: Go
Description : The missing interface filesystem abstraction for Go
Billy implements an interface based on the os standard library,
allowing to develop applications without dependency on the underlying storage.
Makes it virtually free to implement mocks and testing over filesystem
operations.
This package is in the dependency tree of Lazygit (#908894)
Bug#924921: ITP: golang-github-nozzle-throttler -- Throttler fills the gap between sync.WaitGroup and manually monitoring your goroutines with channels.
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-nozzle-throttler Version : 1.1-1 Upstream Author : Nozzle * URL : https://github.com/nozzle/throttler * License : Apache-2.0 Programming Lang: Go Description : Throttler fills the gap between sync.WaitGroup and manually monitoring your goroutines with channels. The API is almost identical to WaitGroups, but it allows you to set a max number of workers that can be running simultaneously. It uses channels internally to block until a job completes by calling Done() or until all jobs have been completed. It also provides a built in error channel that captures your goroutine errors and provides access to them as []error after you exit the loop. This package is in the dependency tree of Lazygit (#908894)
Processed: wordplay
Processing commands for cont...@bugs.debian.org: > retitle #922894 ITA: wordplay -- anagram generator Bug #922894 [wnpp] O: wordplay -- anagram generator Changed Bug title to 'ITA: wordplay -- anagram generator' from 'O: wordplay -- anagram generator'. > owner #922894 ! Bug #922894 [wnpp] ITA: wordplay -- anagram generator Owner recorded as Moshe Piekarski . > thanks Stopping processing here. Please contact me if you need assistance. -- 922894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924921: RFS: golang-github-nozzle-throttler/1.1-1
Dear Go team, I am looking for a sponsor for the package "golang-github-nozzle-throttler". This package is a prerequisite for upcoming package "lazygit" (#908894). I pushed to our team's Salsa: https://salsa.debian.org/go-team/packages/golang-github-nozzle-throttler Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924922: RFS: golang-gopkg-src-d-go-billy.v4/4.3.0-1
Dear Go team, I am looking for a sponsor for the package "golang-gopkg-src-d-go-billy.v4". This package is a prerequisite for upcoming package "lazygit" (#908894). I pushed to our team's Salsa: https://salsa.debian.org/go-team/packages/golang-gopkg-src-d-go-billy.v4 Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924930: ITP: golang-github-cloudfoundry-jibber-jabber -- Cross Platform locale detection for Golang
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-cloudfoundry-jibber-jabber Version : 0.0~git20151120.bcc4c83-1 Upstream Author : cloudfoundry-attic * URL : https://github.com/cloudfoundry/jibber_jabber * License : Apache-2.0 Programming Lang: Go Description : Cross Platform locale detection for Golang Jibber Jabber is a GoLang Library that can be used to detect an operating system's current language. OS Support OSX and Linux via the LC_ALL and LANG environment variables. These are standard variables that are used in ALL versions of UNIX for language detection. This package is in the dependency tree of Lazygit (#908894)
Bug#924930: RFS: golang-github-cloudfoundry-jibber-jabber/0.0~git20151120.bcc4c83-1
Dear Go team, I am looking for a sponsor for the package "golang-github-cloudfoundry-jibber-jabber". This package is a prerequisite for upcoming package "lazygit" (#908894). I pushed to our team's Salsa: https://salsa.debian.org/go-team/packages/golang-github-cloudfoundry-jibber-jabber Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Processed: Fwd: wordplay
Processing commands for cont...@bugs.debian.org: > owner #922894 ! Bug #922894 [wnpp] ITA: wordplay -- anagram generator Owner changed from Moshe Piekarski to Moshe Piekarski . > thanks Stopping processing here. Please contact me if you need assistance. -- 922894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915237: RFP: systemd-docker -- Wrapper for "docker run" to handle systemd quirks
As a followup, I can't help but think this is all a huge horrible hack and that we're over thinking this problem completely. A container is what: * an image "filesystem" (a tarball of tarballs really) * a manifest (which volumes should be exported, ports, etc) * a running process (or multiple, if you're into that kind of heresies) under a vague set of constraints (cgroups, apparmor, selinux, namespaces, pick your worst) systemd supports the latter more or less natively, but does not support Docker (or OCI) images and manifests out of the box. All the work systemd-docker is doing is trying to bridge that gap, with Docker. What if there would be a (better, simpler) way of doing this (almost) without Docker? I've found this inspiring post that tries to run Docker container using `systemd-nspawn` instead of Docker: https://seanmcgary.com/posts/run-docker-containers-with-systemd-nspawn/ The basic approach is similar to systemd-docker: hijack the pre/post hooks to do magic things. Example: ExecStartPre=/bin/bash -c 'docker pull quay.io/seanmcgary/nspawn-test:latest || true' ExecStartPre=/bin/bash -c 'mkdir /home/core/containers/nspawntest_new || true' ExecStartPre=/bin/bash -c 'docker export "$(docker create --name nspawntest quay.io/seanmcgary/nspawn-test true)" | tar -x -C /home/core/containers/nspawntest_new' ExecStartPre=/bin/bash -c 'docker rm nspawntest || true' ExecStartPre=/bin/bash -c 'mv /home/core/containers/nspawntest_new /home/core/containers/nspawntest_running' ExecStart=/bin/bash -c 'sudo systemd-nspawn --machine nspawntest --directory /home/core/containers/nspawntest_running /run.sh' ExecStop=/bin/bash -c 'sudo machinectl terminate nspawntest' Now there's way too much bash -c in there for me to be happy, but I like the idea. I can't help but think that `docker pull` could be replaced by [Skopeo][] and [docker export][] replaced by ... something? In any case, I wouldn't advise using the autistici packages for now, as all dependencies are vendored inside the package which means they might not be updated as regularly as we might expect. A. PS: This is one of those days where when I look for answers to a problem I find a very detailed article full of wit and wisdom but not quite any answers, written by myself a year ago: https://anarc.at/blog/2017-12-20-docker-without-docker/ yaaay thanks for nothing, past anarcat! -- We are discreet sheep; we wait to see how the drove is going, and then go with the drove. - Mark Twain
Bug#924949: ITP: energy2d -- Interactive 2D heat transfer simulator
Package: wnpp Severity: wishlist Owner: Wookey Package name: energy2d Version : 3.0.2 Upstream Author : Charlie Xie URL : https://github.com/charxie/energy2d License : LGPL 3.0 Programming Lang: Java Description : Interactive 2D heat transfer simulator Based on Computations physics, Energy2D is an interactive visual multiphsyics simulation program that models all three modes of heat trasfer: conduction, convection, and radiation, and their coupling with particle dynamics. It allows you to design 'computational experiments' to test a scientific hypothesis or solve an engineering problem, and thus is useful for teaching, research and design. Energy2D runs quickly and lets you run computation fluid dynamics simulations without switching between multiple pieces of software, making this type of simulation much more accessible to non-experts.
Bug#924951: RFP: node-underscore-deep-extend -- A deepExtend implementation for underscore, lodash and friends
Package: wnpp Severity: wishlist * Package name: node-underscore-deep-extend Version : 1.1.5 Upstream Author : Kurt Milam (http://xioup.com) * URL : https://salsa.debian.org/themusicgod1-guest/underscoreDeepExtend * License : MIT Programming Lang: javascript Description : A deepExtend implementation for underscore, lodash and friends Based conceptually on the _.extend() function in underscore.js. (Extend: to Shallowly copy all of the properties in the source objects over to the destination object, and return the destination object. Any nested objects or arrays will be copied by reference, not duplicated. It's in-order, so the last source will override properties of the same name in previous arguments.) This function is especially useful if you're working with JSON config documents. It allows you to create a default config document with the most common settings, then override those settings for specific cases. It accepts any number of objects as arguments, giving you fine-grained control over your config document hierarchy. It is a prerequisite of mist ( #827314 )
Bug#882640: Closing the ITP for dm-zoned-tools as I have uploaded a package
On Sat, 2019-03-16 at 17:08 +1100, Andrew Worsley wrote: > Closing the ITP for dm-zoned-tools as I have uploaded a package The ITP should only be closed when the package reaches Debian. Normally this happens automatically when a package with (Closes: #123456) in the Debian changelog file reaches the archive. Bart Martens has corrected this premature closing by reopening the bug. > I opened another RFS bug 924708: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924708 > > I think I slightly mucked up the RFP as I used the reportbug and > pasted in a description into the wrong field - but it seems to be ok. Bart Martens corrected the title of the RFS bug report to be more like the RFS template. In addition the newcomer tag is not meant to be used in the way that you used it because the idea of the tag is to indicate bugs that aren't being worked on right now but that a new contributor could work on, Andrey Rahmatullin corrected that by removing the tag. https://mentors.debian.net/sponsors/rfs-howto https://www.debian.org/Bugs/Developer#tags Somehow your RFS bug report didn't reach the debian-mentors mailing list. I have resent the mail to the list but the mail still didn't reach the list so I think there must be some sort of filtering. I have asked the #debian-lists channel what happened there. > I didn't realise that I had to open *another* RFS bug or to close the > original ITP bug when uploading the package. The RFS (Request for Sponsor) bug helps indicate to potential sponsors that you need a sponsor, while the ITP (Intent to Package) bug is opened *before* you start creating the package and closed *after* it gets included into Debian. > I believe I have fixed all the issues that I know how to do - it > claims the watch file doesn't work - but it seems to work for me? I expect this is because the mentors site uses an old version of devcripts but your watch file uses the new git support. In addition, phpmode is not a valid option in watch files, I think you meant the pgpmode option. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
