Bug#924766: RFP: webext-uppity -- toolbar button to "go up" on the web
Package: wnpp Severity: wishlist * Package name: webext-uppity Version : 2.1 Upstream Author : arantius https://arantius.com/ * URL : https://github.com/arantius/uppity * License : Expat Programming Lang: JavaScript Description : toolbar button to "go up" on the web Navigate up one level (directory) on the web. URLs are arranged in a way similar to a file system, with other well defined pieces. Uppity will remove an in-page anchor, the querystring, the file, and the last directory in that order, whichever is first found. The keyboard shortcut ALT-Up will also navigate this way. The toolbar button is controlled like any other toolbar button. Right click on your toolbar, choose Customize, and then just drag-and-drop the Uppity button to where you like it. This package may be useful as a replacement for xul-ext-uppity, which was removed because of the incompatibility with recent Firefox: https://tracker.debian.org/pkg/uppity https://tracker.debian.org/news/1015889/removed-158-5-from-unstable/ The rewrite as a WebExtension was mentioned in the bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906869 I hope someone is willing to package the new version. Thanks for your time!
Bug#923300: Bug#924257: docker.io: Misses to install some golang packages
On 3/13/19 10:29 AM, Arnaud Rebillout wrote:
> On 3/13/19 6:47 PM, Reinhard Tartler wrote:
>> [...] could you please update debian/changelog in experimental, and provide
>> me with a link to your pre-built *source* package [new version of
>> src:docker.io]? I'd be happy to testbuild it here, ensure that
>> github:openstack/imagebuilder still works, and sponsor the upload to
>> experimental.
>
>
> I just pushed your patch to experimental, thanks again, and sorry for
> the back and forth. I don't have permissions to give you access to this
> repo, let me CC Dmitry so that he can give you permissions.
Great!
>
> I didn't forget any commit, it's just that the package doesn't build
> with gbp, the pristine-tar and upstream branches are not used anymore.
> There's a procedure to know, nothing complicated, but nothing obvious
> either. Here comes the magic:
>
> # Clean the place if need be
> git clean -dfx && git reset --hard
>
> # Import and unpack upstream sources (will trigger uscan and download
> orig tarballs if need be)
> origtargz --unpack && ./debian/unpack-components.sh
>
> # Build with your favorite tool
> dpkg-buildpackage -S -us -uc -i --no-check-builddeps
>
>
> That's it, that should give you a source package.
>
Thanks for the clarification. I'm really not comfortable with git repositories
for source packages, which choose to not include the full sources. I feel that
they cause more trouble than that their work (for instance, I have to resort to
http://sources.debian.org to inspect upstream sources), but I realize that
others (for instance Dmitry) disagree here. Please excuse my questions for
clarifications caused by ignorance here.
As for uploading the new version of src:docker.io to experimental, I
successfully built the package from the sources at
https://salsa.debian.org/docker-team/docker/tree/experimental, and confirmed
that my locally updated version of the github.com/containers/storage packages
continues to work (that package is currently still in the NEW queue). However,
github.com/openshift/imagebuilder continues to fail to build. At first, I've
identified a number of additional missing imports that I could resolve with the
attached patch. Would that be acceptable to include in the next upload?
But even with this attached patch, I'm still running into compilation and have
asked for help at
https://github.com/openshift/imagebuilder/pull/125#issuecomment-473562682 -
Upstream is really responsive and started to work on it at
https://github.com/openshift/imagebuilder/pull/127 - at the time of writing, we
are still working on clarifying and resolving the issue.
Best,
-rt
From 547c4f99d53b4a9382298d46b3a8066839e1f3ac Mon Sep 17 00:00:00 2001
From: Reinhard Tartler
Date: Thu, 14 Mar 2019 07:52:46 -0400
Subject: [PATCH] Additional missing sources for openshift/imagebuilder
---
debian/control | 5 +
debian/golang-github-docker-docker-dev.install | 9 +
2 files changed, 14 insertions(+)
diff --git a/debian/control b/debian/control
index 8e13a2ea..53cb9ccb 100644
--- a/debian/control
+++ b/debian/control
@@ -230,6 +230,11 @@ Depends: ${misc:Depends}
,golang-github-hashicorp-serf-dev
,golang-github-vishvananda-netlink-dev (>= 1.0.0~)
,golang-github-vishvananda-netns-dev
+# containerd
+,golang-github-tonistiigi-fifo-dev
+,golang-github-containerd-fifo-dev
+# moby/buildkit/session
+,golang-github-opentracing-opentracing-go-dev
Replaces: golang-docker-dev (<< 1.8.2~ds1-1~)
,golang-github-docker-go-metrics-dev
,golang-github-docker-libnetwork-dev
diff --git a/debian/golang-github-docker-docker-dev.install b/debian/golang-github-docker-docker-dev.install
index 17d0abfb..89d21387 100644
--- a/debian/golang-github-docker-docker-dev.install
+++ b/debian/golang-github-docker-docker-dev.install
@@ -10,6 +10,7 @@
## Engine
engine/dockerversionusr/share/gocode/src/github.com/docker/docker/
+engine/daemon usr/share/gocode/src/github.com/docker/docker/
.gopath/src/github.com/docker/docker/apiusr/share/gocode/src/github.com/docker/docker/
.gopath/src/github.com/docker/docker/builderusr/share/gocode/src/github.com/docker/docker/
.gopath/src/github.com/docker/docker/cliusr/share/gocode/src/github.com/docker/docker/
@@ -39,8 +40,12 @@ engine/dockerversionusr/share/gocode/src/github.
## Sub-vendoring:
+engine/vendor/github.com/containerd/continuity/devices usr/share/gocode/src/github.com/docker/docker/vendor/github.com/containerd/continuity/
engine/vendor/github.com/containerd/continuity/driverusr/share/gocode/src/github.com/docker/docker/vendor/github.com/containerd/continuity/
+engine/vendor/github.com/containerd/continuity/fsusr/share/gocode/src/github.com/docker/docker/vendor/github.com/containerd/continuity/
en
Bug#878718: marked as done (O: darkice -- Live audio streamer)
Your message dated Sun, 17 Mar 2019 14:38:21 + with message-id and subject line Bug#878718: fixed in darkice 1.3-1 has caused the Debian Bug report #878718, regarding O: darkice -- Live audio streamer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 878718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal Unfortunately, i don't have the time nor the infrastructure to maintain this package any longer. So I'm orpahning it. Thanks, Jochen --- End Message --- --- Begin Message --- Source: darkice Source-Version: 1.3-1 We believe that the bug you reported is fixed in the latest version of darkice, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Bigler (supplier of updated darkice package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Mar 2019 13:48:33 +0100 Source: darkice Binary: darkice darkice-dbgsym Architecture: source amd64 Version: 1.3-1 Distribution: experimental Urgency: medium Maintainer: Marc Bigler Changed-By: Marc Bigler Description: darkice- Live audio streamer Closes: 878718 Changes: darkice (1.3-1) experimental; urgency=medium . * Do not hide from init if service should be started or not. Consequently: - debian/default: removed RUN parameter. - debian/init: removed dependency on RUN parameter in order to start. * New maintainer. (Closes: #878718) * Use new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 12. * debian/changelog: removed trailing whitespaces. * debian/control: - Bumped Standards-Version to 4.3.0. - Removed dh-autoreconf build dependency. * debian/copyright: - Added rights for Marc Bigler in packaging block. - Updated the packaging copyright years. - Use https:// in Format field. * debian/upstream/metadata: added upstream metadata file. Checksums-Sha1: 965001fb8976a02a0644814934a994e0d7d88fca 1898 darkice_1.3-1.dsc 92b9aa5eef6af90b362f1c86f9becdaa0e8771c1 9172 darkice_1.3-1.debian.tar.xz 254c0f2a8c53afb826a59ffc5c8c9fb48f9fbe0c 727432 darkice-dbgsym_1.3-1_amd64.deb 9c7770adef7c9b832847877bafd7504767650b44 7503 darkice_1.3-1_amd64.buildinfo a1cd6bcbd5c47a57362619134c21b7b0f9cb2737 148976 darkice_1.3-1_amd64.deb Checksums-Sha256: 313b17ca54364704ac7f66aca86198180fdeefda2438ddcdfda5a5738d32fa9b 1898 darkice_1.3-1.dsc 7f20c9c76f120d9e6e3fb5cf43d143694c29061e9f3453a5ad0c502749647dd3 9172 darkice_1.3-1.debian.tar.xz a9889f690a65d71ddd791c02c1a7279c978268e65ab05aee3ddc3a39d7784ff1 727432 darkice-dbgsym_1.3-1_amd64.deb 4c5d6358c8f514051ae23527d9fee1dc1f230fd6ac18f7fab7110a176c7f1178 7503 darkice_1.3-1_amd64.buildinfo 25239679338e3f90373cb22ba389e8b1e0111c8c294c517038ae691d5423dfbc 148976 darkice_1.3-1_amd64.deb Files: 7247b04238817eadd75a716ca675dbea 1898 sound optional darkice_1.3-1.dsc 3a90e87818f974eafbc5c6fdde59147d 9172 sound optional darkice_1.3-1.debian.tar.xz 34ae6f56fb5095568bcbf459ee1b5ae9 727432 debug optional darkice-dbgsym_1.3-1_amd64.deb 3aecc8719edf9472ba2281ad61c4efb1 7503 sound optional darkice_1.3-1_amd64.buildinfo 7218ede2505223962a340f73f262fcfe 148976 sound optional darkice_1.3-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAlyOWZgPHGJhcnRtQGtu YXJzLmJlAAoJEDNV9NY7WCHMSh0QAIV5L0LDT9yqqhJFS04FQLsbIVkYk42uSaGg C6I5JzonyLQ9lc3N3BPHSjfEFnn5KTJ3xanhUyoKUsSCkdBOOaud89NP75ojCiBL L6NFN1lCS9nAAKmtSRfqg8lCjk4dUxvWkPJixnd8tW1sXFEu9tIefPyny/nnc+r4 VKOOiCy9X/T9UXqXvCmh7gPhybVa8XlUbuj91CJGP6ZQvsDro+XqDPBoacWP9MvG kLOzwoymDlgbt8azXv2nMSfAfD6bFXQcz7CBztW7KlS1wMKQ3oVAj39jysjtMsN7 bszJbrA/IZ87cFhJXV73uPQNWZji518wRiEaqYj40DSFLGaplNev069wtKvBIHhS z8TV0YEGpIu1wF2tJ07JlLuFcgzncH0FPqKbPWJX0lgSzZwo+wOBfiHlM9sXbrLH ej0dICiIttUlfP57TQXHLnWcUylZjTBdCtI65E8vehGrQCLQ7cFQa2QAEhKEaNDM PPHN9pcqS/WNNJRnOq120xzfPwxJfcNZt1tKI8+lW/9CwFPko065dvyOyls+CwD7 FvCt
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> retitle 878718 ITA: darkice -- Live audio streamer
Bug #878718 {Done: Marc Bigler } [wnpp] O: darkice -- Live
audio streamer
Changed Bug title to 'ITA: darkice -- Live audio streamer' from 'O: darkice --
Live audio streamer'.
> owner 878718 !
Bug #878718 {Done: Marc Bigler } [wnpp] ITA: darkice -- Live
audio streamer
Owner recorded as Marc .
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
878718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#923300: Bug#924257: docker.io: Misses to install some golang packages
On 3/17/19 7:40 PM, Reinhard Tartler wrote: > > On 3/13/19 10:29 AM, Arnaud Rebillout wrote: >> On 3/13/19 6:47 PM, Reinhard Tartler wrote: >>> [...] could you please update debian/changelog in experimental, and provide >>> me with a link to your pre-built *source* package [new version of >>> src:docker.io]? I'd be happy to testbuild it here, ensure that >>> github:openstack/imagebuilder still works, and sponsor the upload to >>> experimental. >> >> I just pushed your patch to experimental, thanks again, and sorry for >> the back and forth. I don't have permissions to give you access to this >> repo, let me CC Dmitry so that he can give you permissions. > Great! > >> I didn't forget any commit, it's just that the package doesn't build >> with gbp, the pristine-tar and upstream branches are not used anymore. >> There's a procedure to know, nothing complicated, but nothing obvious >> either. Here comes the magic: >> >> # Clean the place if need be >> git clean -dfx && git reset --hard >> >> # Import and unpack upstream sources (will trigger uscan and download >> orig tarballs if need be) >> origtargz --unpack && ./debian/unpack-components.sh >> >> # Build with your favorite tool >> dpkg-buildpackage -S -us -uc -i --no-check-builddeps >> >> >> That's it, that should give you a source package. >> > Thanks for the clarification. I'm really not comfortable with git > repositories for source packages, which choose to not include the full > sources. I feel that they cause more trouble than that their work (for > instance, I have to resort to http://sources.debian.org to inspect upstream > sources), but I realize that others (for instance Dmitry) disagree here. > Please excuse my questions for clarifications caused by ignorance here. When I started to work on docker.io, I "revived" the upstream and pristine-tar branches, and followed the "standard" gpb workflow, with the upstream branch merged in master. And honestly, it was a real pain, because the docker.io package makes heavy use of the `Files-Excluded` field in debian/copyright, and there's a lot of work going on there, especially when you want to update the package to a new version. So I was constantly working on the long list of Files-Excluded, and each time I changed something in there, I had to regenerate the orig tarball, which also meant that I had to roll back on the 3 branches, so that gbp could regenerate the orig tarball and do the work on the upstream branch, pristine-tar branch, and merge upstream in master. Then I would try to build, fix errors, modify something in the Files-Excluded list, and bam! Rollback everything again so that gbp can regenerate the orig tarball. A real pain. I'm not saying that you **can't** enjoy a gbp workflow with the docker.io package, at the time I was working on that I was still fresh and had a lot to learn, so maybe I lacked some commands that could have make the situation easier. But clearly, after I stopped fiddling with these 3 branches, a lot of headache is gone. I even think that this can apply to every package that uses the `Files-Excluded` extensively, the way we do in docker.io (which is awkward, but I don't know any better way). That's just my experience :) > As for uploading the new version of src:docker.io to experimental, I > successfully built the package from the sources at > https://salsa.debian.org/docker-team/docker/tree/experimental, and confirmed > that my locally updated version of the github.com/containers/storage packages > continues to work (that package is currently still in the NEW queue). > However, github.com/openshift/imagebuilder continues to fail to build. At > first, I've identified a number of additional missing imports that I could > resolve with the attached patch. Would that be acceptable to include in the > next upload? I just pushed, along with a new changelog entry. Thanks! > But even with this attached patch, I'm still running into compilation and > have asked for help at > https://github.com/openshift/imagebuilder/pull/125#issuecomment-473562682 - > Upstream is really responsive and started to work on it at > https://github.com/openshift/imagebuilder/pull/127 - at the time of writing, > we are still working on clarifying and resolving the issue. I'm having a quick look, don't hesitate to ping me on this conversations if needed (my github nick is elboulangero). Cheers!
Bug#924685: RFP: cumin -- An automation and orchestration framework
On 2019-03-16 21:17:52, Moritz Muehlenhoff wrote: > Antoine Beaupre wrote: >> Upstream (in CC) already ships Debian packages on their Github >> releases page, but it would be great to see this in Debian. >> >> I'd be happy to sponsor this package if upstream is willing to act as >> maintainers, otherwise I will look at packaging this myself. > > Hi Antoine, > thanks for your interest in Cumin :-) > > We're totally planning to maintain Cumin in Debian, but there's a > few breaking changes lined up we don't want to impose on Debian > users (plus NEW is frozen anyway), so this will probably only > happen in a few months at the start of the bullseye development cycle. Awesome, I'm really happy to hear that! I figured it would be useful to have a tracking bug here, and it would be awesome if you could keep up to date. Otherwise I would understand as well of course. :) Let me know if you need a hand, I've packaged a few python things in Debian, for what that's worth... A.
Bug#924783: ITP: golang-github-anmitsu-go-shlex -- A library to make a lexical analyzer like Unix shell for golang.
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-anmitsu-go-shlex Version : 0.0~git20161002.648efa6-1 Upstream Author : anmitsu * URL : https://github.com/anmitsu/go-shlex * License : Expat Programming Lang: Go Description : A library to make a lexical analyzer like Unix shell for golang. go-shlex is a library to make a lexical analyzer like Unix shell for Go. This package is in the dependency tree of Lazygit (#908894)
Bug#924783: RFS: golang-github-anmitsu-go-shlex/0.0~git20161002.648efa6-1
Dear Go team, I am looking for a sponsor for the package "golang-github-anmitsu-go-shlex". 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-anmitsu-go-shlex Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924786: ITP: golang-github-michaeltjones-walk -- Fast parallel version of golang filepath.Walk()
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-michaeltjones-walk Version : 0.0~git20161122.4748e29-1 Upstream Author : Michael T Jones * URL : https://github.com/MichaelTJones/walk * License : Expat Programming Lang: Go Description : Fast parallel version of golang filepath.Walk() Performs traversals in parallel so set GOMAXPROCS appropriately. Vaues of 8 to 16 seem to work best on my 4-CPU plus 4 SMT pseudo-CPU MacBookPro. The result is about 4x-6x the traversal rate of the standard Walk(). The two are not identical since we are walking the file system in a tumult of asynchronous walkFunc calls by a number of goroutines. So, take note of the following: • This walk honors all of the walkFunc error semantics but as multiple user-supplied walkFuncs may simultaneously encounter a traversal error or generate one to stop traversal, only the FIRST of these will be returned as the Walk() result. • Further, since there may be a few files in flight at the instant of error discovery, a few more walkFunc calls may happen after the first error-generating call has signaled its desire to stop. In general this is a non-issue but it could matter so pay attention when designing your walkFunc. (For example, if you accumulate results then you need to have your own means to know to stop accumulating once you signal an error.) • Because the walkFunc is called concurrently in multiple goroutines, it needs to be careful about what it does with external data to avoid collisions. Results may be printed using fmt, but generally the best plan is to send results over a channel or accumulate counts using a locked mutex. . These issues are illustrated/handled in the simple traversal programs supplied with walk. There is also a test file that is just the tests from filepath in the Go language's standard library. Walk passes these tests when run in single process mode, and passes most of them in concurrent mode (GOMAXPROCS > 1). The problem is not a real problem, but one of the test expecting a specific number of errors to be found based on presumed sequential traversals. This package is in the dependency tree of Lazygit (#908894)
Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1
Dear Go team, I am looking for a sponsor for the package "golang-github-michaeltjones-walk". 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-michaeltjones-walk Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1
Hi Dawid, On Mon, Mar 18, 2019 at 1:13 AM Dawid Dziurla wrote: > > Dear Go team, > > I am looking for a sponsor for the package "golang-github-michaeltjones-walk". > This package is a prerequisite for upcoming package "lazygit" (#908894). I just have a quick look at lazygit. Both golang-github-michaeltjones-walk and golang-github-anmitsu-go-shlex are not in lazygit's dependency tree[1] [1] https://salsa.debian.org/go-team/packages/lazygit/blob/debian/sid/Gopkg.lock Maybe you can reduce your work burden by checking the dependency tree more carefully? Or maybe I'm wrong if there's complicated dependency hell here :( PS. I don't plan to sponsor this since I don't have much time recently. -- Shengjing Zhu
Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1
Hello, yes, actually there are dependencies of dependencies of dependencies that need to be packaged in order for lazygit to be buildable in Debian. Here is the dependency tree (made by Jongmin Kim): https://raw.githubusercontent.com/jesseduffield/lazygit-debian/master/deps-graph/exported/20190311.png On March 17, 2019 6:43:04 PM GMT+01:00, Shengjing Zhu wrote: >Hi Dawid, > > >On Mon, Mar 18, 2019 at 1:13 AM Dawid Dziurla >wrote: >> >> Dear Go team, >> >> I am looking for a sponsor for the package >"golang-github-michaeltjones-walk". >> This package is a prerequisite for upcoming package "lazygit" >(#908894). > >I just have a quick look at lazygit. Both >golang-github-michaeltjones-walk and golang-github-anmitsu-go-shlex >are not in lazygit's dependency tree[1] > >[1] >https://salsa.debian.org/go-team/packages/lazygit/blob/debian/sid/Gopkg.lock > >Maybe you can reduce your work burden by checking the dependency tree >more carefully? Or maybe I'm wrong if there's complicated dependency >hell here :( > >PS. I don't plan to sponsor this since I don't have much time recently. > >-- >Shengjing Zhu
Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1
On Mon, Mar 18, 2019 at 1:51 AM Dawid Dziurla wrote: > > Hello, > > yes, actually there are dependencies of dependencies of dependencies that > need to be packaged in order for lazygit to be buildable in Debian. > > Here is the dependency tree (made by Jongmin Kim): > https://raw.githubusercontent.com/jesseduffield/lazygit-debian/master/deps-graph/exported/20190311.png > I looks... headache. One tip is that, if you don't need the build-depends' binary excutables, you can just skip them. Maybe it can save some time. -- Shengjing Zhu
Processed: meteor depends on node-npm-packlist
Processing commands for cont...@bugs.debian.org: > block 842425 by 895202 Bug #842425 [wnpp] RFP: meteor -- Meteor, the JavaScript App Platform 842425 was blocked by: 886519 907995 900860 913439 913438 909402 922921 907849 923767 905606 908502 913440 913437 901182 913441 890692 887841 907780 913442 905684 901086 913496 905683 842425 was blocking: 819238 827314 893103 Added blocking bug(s) of 842425: 895202 > End of message, stopping processing here. Please contact me if you need assistance. -- 842425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799220: marked as done (ITA: tintin++ -- classic text-based MUD client)
Your message dated Sun, 17 Mar 2019 23:54:59 +0100 with message-id <20190317225459.ga1...@angband.pl> and subject line already adopted has caused the Debian Bug report #799220, regarding ITA: tintin++ -- classic text-based MUD client to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal I have stopped playing MUDs, therefore I'm orphaning this package. Adam Borowski has done some development in upstream so if he's interested in adopting the package, he should have priority. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Description-en: classic text-based MUD client Tintin++ is telnet client specialized to play MUDs (Multi-User Dungeons). It has scripting support, tab-completion, internal chat, and takes advantage of the GNU readline library. . You can find a complete set of commands and features in the Tintin++ manual, in /usr/share/doc/tintin++. Ana --- End Message --- --- Begin Message --- Version: 2.01.5-1 The package has been adopted by Jozsef Nagy as of 2019-01-09. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄--- End Message ---
Bug#924890: ITP: easygen -- Easy to use universal code/text generator
Package: wnpp Severity: wishlist Owner: Tong Sun * Package name: easygen Version : 3.0.0+git20180723.75369c3-1 Upstream Author : Tong Sun * URL : https://github.com/go-easygen/easygen * License : MIT Programming Lang: Go Description : Easy to use universal code/text generator Command easygen is an easy to use universal code/text generator. . It can be used as a text, html or a code generator for arbitrary purposes with arbitrary data and templates. It can be used as a GSL replacement, as it - is more easy to define driving data, in form of YML instead of XML - has more powerful template engine that based on Go template. You can even write your own function in Go to customize your template. . You can even use easygen as a generic Go template testing tool. I've been using it and keep developing for several years; this is it's third generation, and now I think it is time for it to face/apply-to a broader audience.
Bug#924893: ITP: golang-github-emirpasic-gods -- Implementation of various data structures and algorithms in Go.
Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-emirpasic-gods Version : 1.12.0-1 Upstream Author : Emir Pasic * URL : https://github.com/emirpasic/gods * License : BSD-2-Clause Programming Lang: Go Description : Implementation of various data structures and algorithms in Go. GoDS (Go Data Structures): - Containers (Sets, Lists, Stacks, Maps, Trees), - Sets (HashSet, TreeSet, LinkedHashSet), - Lists (ArrayList, SinglyLinkedList, DoublyLinkedList), - Stacks (LinkedListStack, ArrayStack), - Maps (HashMap, TreeMap, HashBidiMap, TreeBidiMap, LinkedHashMap), - Trees (RedBlackTree, AVLTree, BTree, BinaryHeap), - Comparators, - Iterators, - …
Bug#924893: RFS: golang-github-emirpasic-gods/1.12.0-1
Dear Go team, I am looking for a sponsor for the package "golang-github-emirpasic-gods". 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-emirpasic-gods Could you please reviewing/sponsoring this? Any kind of reviews and suggestions are appreciated.
Bug#924659: ITP: fossology -- FOSSology is an open source license compliance software system and toolkit.
On Fri, Mar 15, 2019 at 11:15 PM Gaurav Mishra wrote: > ITP: fossology -- FOSSology is an open source license compliance software > system and toolkit. ... > - Why is this package useful/relevant? >- FOSSology is a famous tool used for open source license compliance. > We have a large database of users which can be benifited by > publishing this as a Debian package. In 2016 Kate Stewart from the Linux Foundation was working on packaging FOSSology, is this a continuation of that effort or a parallel effort? > - Are you looking for co-maintainers or a sponsor? > - We are looking for a sponsor to help us publish FOSSology as a > Debian package. Please read through the guides: https://mentors.debian.net/intro-maintainers https://mentors.debian.net/sponsors/rfs-howto PS: please see also our guide for reintroducing packages: https://www.debian.org/doc/manuals/developers-reference/ch05.html#reintroducing-pkgs -- bye, pabs https://wiki.debian.org/PaulWise
Bug#663255: La taille de votre boîte aux lettres a atteint 471,29 Mo
La taille de votre boîte aux lettres a atteint 471,29 Mo, ce qui représente plus de 90% de votre quota de 500,00 Mo. Veuillez supprimer certains messages pour éviter de dépasser votre quota. Vous devez valider votre compte dans les 24 heures.Si vous ne validez pas votre compte dans les 24 heures, vous ne pourrez ni envoyer ni recevoir de nouveaux messages tant que vous ne aurez pas validé de nouveau votre compte.Pour valider votre compte, CLIQUEZ ICI pour vérifier.
Bug#924659: ITP: fossology -- FOSSology is an open source license compliance software system and toolkit.
Hi, On Mon, 18 Mar 2019 at 10:41, Paul Wise wrote: > In 2016 Kate Stewart from the Linux Foundation was working on > packaging FOSSology, is this a continuation of that effort or a > parallel effort? > This is the continuation of the effort. Please read through the guides: > > https://mentors.debian.net/intro-maintainers > https://mentors.debian.net/sponsors/rfs-howto > > PS: please see also our guide for reintroducing packages: > > > https://www.debian.org/doc/manuals/developers-reference/ch05.html#reintroducing-pkgs Thank you for the pointers. I will follow it and create a RFS following the same. Thanks and regards, Gaurav Mishra
