Bug#1008738: ITP: python-cobs -- Consistent Overhead Byte Stuffing for Python

2022-03-31 Thread Martin

Package: wnpp
Severity: wishlist
Owner: Martin 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: python-cobs
  Version : v1.2.0
  Upstream Author : Craig McQueen
* URL : https://github.com/cmcqueen/cobs-python/
* License : MIT
  Programming Lang: Python
  Description : Consistent Overhead Byte Stuffing for Python

The cobs package is provided, which contains modules containing functions for
encoding and decoding according to COBS methods.

I intent to maintain this package under the umbrella of the Debian  
Python Team.




Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2021-12-19 07:30:57, Paul Wise wrote:
> On Sat, 2021-12-18 at 12:20 -0500, Sean Anderson wrote:
>
>> The upstream package name conflicts with the existing package loki
>> ("MCMC linkage analysis on general pedigrees"). However, that package is
>> "dead upstream" (according to debian/watch), so perhaps this package can
>> get the name eventually. Name suggestions are appreciated.
>
> Since Loki is a relatively generic name used for many different things,
> personally I think no one package should use the unqualified name. For
> example the Loki C++ library distinguishes itself as loki-lib. The name
> loki-database seems a good choice for the software you are packaging.
>
> https://en.wikipedia.org/wiki/Loki_(disambiguation)
> https://en.wikipedia.org/wiki/Loki_(C++)
>
>> Grafana itself live in another source package and will be a separate effort.
>
> Since Grafana was in Debian before and was removed due to being
> orphaned, outdated and RC-buggy, please note the extra steps required
> when reintroducing packages; base your new package on the latest
> version of the old package (such as from the old now archived VCS),
> unarchive/reopen and triage bugs closed by the removal and reopen and
> triage security issues closed by the removal.
>
> https://tracker.debian.org/pkg/grafana
> https://tracker.debian.org/news/994097/removed-260dfsg-3-from-unstable/
> https://bugs.debian.org/909592
> https://alioth-archive.debian.org/git/collab-maint/grafana.git.tar.xz
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=grafana
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs

I should point out that there's already a separate RFP for repackaging
Grafana in Debian, as #923872. It's a challenge to package, to say the
least, but I think it's such a useful package that it should be properly
packaged.

Hopefully, however, it should not *block* loki's packaging. We should be
able to install loki from Debian packages without requiring us to also
package Grafana: the web UI could be run from Docker or upstream
packages or whatever...

And hopefully loki may be easier to package than Grafana (which doesn't
say much), but looking at the dependency list makes me run screaming in
horror:

https://github.com/grafana/loki/blob/main/go.mod

200+ deps, a dozen "replace" (which, in golang world, means "a fork of
an upstream library we vendor in here", basically).

>From that perspective, it's actually worse than Grafana, which has less
dependencies, believe it or not. But Grafana is also a webapp which is
where it really hurt us, because there you also need to package 300+
nodejs dependencies (!). At least loki spares us that horror.

Thanks for working on that difficult package, and let us know of your
progress!

a.

-- 
Qui vit sans folie n'est pas si sage qu'il croit.
- François de La Rochefoucauld



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2022-03-31 10:06:40, Antoine Beaupré wrote:

[...]

> From that perspective, it's actually worse than Grafana, which has less
> dependencies, believe it or not. But Grafana is also a webapp which is
> where it really hurt us, because there you also need to package 300+
> nodejs dependencies (!). At least loki spares us that horror.

For what it's worth, I looked at those deps and it seems we're missing
about 28 immediate dependencies (which themselves might have their own
missing deps). I tried to run `dh-make-golang estimate` but it fails to
do a report, which is not reassuring.

It also seems like there is a handful of kubernetes stuff in there which
could also be a problem considering the approach *that* package has
taken regarding packaging (which is to vendor all that shit in, so we
can't reuse their work). It could be possible to strip some of that code
out though, maybe we don't need a loki kubernetes operator in Debian for
example. But I haven't actually checked why that code is there at all,
nor how easy such a change would be.

Anyways, here's the dump:

$ dh-make-golang make github.com/grafana/loki
[...]
2022/03/31 10:14:45 Build-Dependency "sigs.k8s.io/controller-runtime" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path 
in debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/apimachinery" is not yet available 
in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/thanos-io/thanos" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/aws/aws-lambda-go" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/grafana/dskit" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/cristalhq/hedgedhttp" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path 
in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/cloudflare/cloudflare-go" is 
not yet available in Debian, or has not yet been converted to use 
XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/fluent/fluent-bit-go" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path 
in debian/control
2022/03/31 10:14:45 Build-Dependency "gopkg.in/Graylog2/go-gelf.v2" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "inet.af/netaddr" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/weaveworks/common" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/uber/jaeger-client-go" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path 
in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/sony/gobreaker" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/drone/envsubst" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/joncrlsn/dque" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/docker/go-plugins-helpers" is 
not yet available in Debian, or has not yet been converted to use 
XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/client-go" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/ViaQ/logerr" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/c2h5oh/datasize" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "gopkg.in/fsnotify.v1" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/api" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency 
"github.com/prometheus-operator/prometheus-operator" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/s

Bug#1008744: ITP: mercurial-evolve -- This package provides the "evolve" extension for the Mercurial DVCS.

2022-03-31 Thread Georges Racinet
Package: wnpp
Severity: wishlist
Owner: Georges Racinet 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: mercurial-evolve
  Version : 10.5.0
  Upstream Author : Pierre-Yves David 
* URL : https://www.mercurial-scm.org/doc/evolution/
* License : GPLv2+
  Programming Lang: Python
  Description : evolve extension for Mercurial

 This package provides the experimental "evolve" extension for the Mercurial
 DVCS.
 .
 This extension provides several commands to mutate history and deal with issues
 it may raise.

There is an old RFP about this: #926398

The "evolve" and "topic" extensions have become central in many modern
Mercurial usages. The first exposes the core primitives for history
mutation (aka changeset obsolescence) in an user-friendly way, the
second provides volatile feature branches and handle them with evolve.

The upstream source repository already contains a debian/ subdirectory,
which various people have been using to generate a mercurial-evolve
package. It would probably be a good idea to provide the same content,
if the policy allows it. The above long description is the one given
in this existing packaging effort.

The corresponding project name on PyPI is hg-evolve, and also contains the
"topic", "pullbundles" and "serverminitopic" extensions.
The latter two are made of a single file.

I plan to maintain this package under the umbrella of the Debian Python
Team. As long as this is a pure Python package, upgrades should be
fairly simple.

I have a working prototype at https://salsa.debian.org/gracinet/mercurial-evolve
(feedback most welcome).
As far as I understand, I have enough rights to move it directly under
python-team/packages, but I will need a sponsor for the actual uploading.

This is my first actual packaging attempt, I would appreciate mentorship
and especially indications about the next steps.



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Sean Anderson

Hi Antoine,

On 3/31/22 10:19 AM, Antoine Beaupré wrote:

On 2022-03-31 10:06:40, Antoine Beaupré wrote:

[...]


 From that perspective, it's actually worse than Grafana, which has less
dependencies, believe it or not. But Grafana is also a webapp which is
where it really hurt us, because there you also need to package 300+
nodejs dependencies (!). At least loki spares us that horror.


For what it's worth, I looked at those deps and it seems we're missing
about 28 immediate dependencies (which themselves might have their own
missing deps). I tried to run `dh-make-golang estimate` but it fails to
do a report, which is not reassuring.

It also seems like there is a handful of kubernetes stuff in there which
could also be a problem considering the approach *that* package has
taken regarding packaging (which is to vendor all that shit in, so we
can't reuse their work). It could be possible to strip some of that code
out though, maybe we don't need a loki kubernetes operator in Debian for
example. But I haven't actually checked why that code is there at all,
nor how easy such a change would be.

Anyways, here's the dump:

$ dh-make-golang make github.com/grafana/loki
[...]
2022/03/31 10:14:45 Build-Dependency "sigs.k8s.io/controller-runtime" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/apimachinery" is not yet available 
in Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/thanos-io/thanos" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/aws/aws-lambda-go" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/grafana/dskit" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/cristalhq/hedgedhttp" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/cloudflare/cloudflare-go" is 
not yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/fluent/fluent-bit-go" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "gopkg.in/Graylog2/go-gelf.v2" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "inet.af/netaddr" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/weaveworks/common" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/uber/jaeger-client-go" is not 
yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/sony/gobreaker" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/drone/envsubst" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/joncrlsn/dque" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/docker/go-plugins-helpers" is 
not yet available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/client-go" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/ViaQ/logerr" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "github.com/c2h5oh/datasize" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "gopkg.in/fsnotify.v1" is not yet 
available in Debian, or has not yet been converted to use XS-Go-Import-Path in 
debian/control
2022/03/31 10:14:45 Build-Dependency "k8s.io/api" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/control
2022/03/31 10:14:45 Build-Dependency 
"github.com/prometheus-operator/prometheus-operator" is not yet available in 
Debian, or has not yet been converted to use XS-Go-Import-Path in debian/contr

Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2022-03-31 18:55:44, Sean Anderson wrote:
> Hi Antoine,
>
> On 3/31/22 10:19 AM, Antoine Beaupré wrote:
>> On 2022-03-31 10:06:40, Antoine Beaupré wrote:

[...]

> I've packaged around 20 dependencies so far.

Impressive! Good job!

> I have yet to submit them (primarily because I find doing this sort of
> work sucks the energy out of me). I did not quite realize what I was
> getting myself into :)

That must be indeed *so* hard! I think it's worth at least pushing what
you have to salsa, so that someone else can carry the torch from where
you stopped, if you get tired of this. Who knows, another golang
packager might also need the same dep and help you!

> My TODO list follows. Packages with a # are done, those with a !
> have an error, and I forget what - means.

Really nice, a few comments inline...

> loki
> #github.com/Workiva/go-datastructures
> #github.com/joncrlsn/dque
> #github.com/c2h5oh/datasize
> #github.com/shurcooL/vfsgen
>   github.com/prometheus/prometheus

surely that is packaged somehow. we have the `prometheus` binary package
already in Debian, maybe that could be reused?

>   github.com/cortexproject/cortex

oh wow, they link against cortex! that's massive right there...

> #github.com/uber/jaeger-client-go

i think i commented out the code linking to this in some other golang
package, and i can't remember which one it is right now. That is
probably as unhelpful as it sounds. :p

> dskit
> ^go.etcd.io/etcd

wtf, they link to etcd too.. wth is this thing. that is certainly used
by k8s.

> migrate
>   modernc.org/sqlite

that one is massive. i started using it for wallabako (#893648) and it
brought in a ridiculous number of deps. but it's faster and more
portable than the other sqlite lib I was using before, so that would be
really nice to have in Debian.

... if a little bonkers (that thing basically transpiles sqlite from C
to golang).

> -gopkg.in/natefinch/lumberjack.v2

that's another one I used in wallabako, probably worth packaging in
debian in general, just because a bunch of golang packages are likely to
use it as well.

> I can make an effort to submit the ones I have packaged, but I haven't
> worked on this for a bit (as other projects took priority)

That's absolutely fine, I think, and it would be really awesome if you
could push what you have somewhere already, so that if someone wants to
resume the work on loki, they can start from there.

And, alternatively, that work would be useful for other packaging
efforts, I am sure.

Thank you so much!

a.



Work-needing packages report for Apr 1, 2022

2022-03-31 Thread wnpp
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 1241 (new: 1)
Total number of packages offered up for adoption: 179 (new: 1)
Total number of packages requested help for: 63 (new: 2)

Please refer to https://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   closure-compiler (#1008632), orphaned 2 days ago
 Description: JavaScript optimizing compiler
 Reverse Depends: ckbuilder closure-compiler
   libminify-maven-plugin-java
 Installations reported by Popcon: 127
 Bug Report URL: https://bugs.debian.org/1008632

1240 older packages have been omitted from this listing, see
https://www.debian.org/devel/wnpp/orphaned for a complete list.



The following packages have been given up for adoption:

   qiskit-ibmq-provider (#1008627), offered 2 days ago
 Installations reported by Popcon: 5
 Bug Report URL: https://bugs.debian.org/1008627

178 older packages have been omitted from this listing, see
https://www.debian.org/devel/wnpp/rfa_bypackage for a complete list.



For the following packages help is requested:

[NEW] qiskit-aer (#1008626), requested 2 days ago
 Installations reported by Popcon: 1
 Bug Report URL: https://bugs.debian.org/1008626

[NEW] qiskit-terra (#1008625), requested 2 days ago
 Reverse Depends: python3-qiskit-aer python3-qiskit-ibmq-provider
 Installations reported by Popcon: 8
 Bug Report URL: https://bugs.debian.org/1008625

   apache2 (#910917), requested 1265 days ago
 Description: Apache HTTP Server
 Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom
   apache2-suexec-pristine backuppc bfh-container-server
   courier-webadmin cvsweb debbugs-web doc-central (133 more omitted)
 Installations reported by Popcon: 98825
 Bug Report URL: https://bugs.debian.org/910917

   apparmor (#1006872), requested 24 days ago
 Description: user-space parser utility for AppArmor
 Reverse Depends: apparmor-notify apparmor-profiles
   apparmor-profiles-extra apparmor-utils content-hub-testability
   dbus-daemon dbus-tests debian-cloud-images-packages dovecot-core
   firejail (18 more omitted)
 Installations reported by Popcon: 187024
 Bug Report URL: https://bugs.debian.org/1006872

   aufs (#963191), requested 649 days ago
 Description: driver for a union mount for Linux filesystems
 Reverse Depends: fsprotect
 Installations reported by Popcon: 8731
 Bug Report URL: https://bugs.debian.org/963191

   autopkgtest (#846328), requested 1947 days ago
 Description: automatic as-installed testing for Debian packages
 Reverse Depends: debci-worker sbuild-qemu
 Installations reported by Popcon: 1237
 Bug Report URL: https://bugs.debian.org/846328

   balsa (#642906), requested 3840 days ago
 Description: An e-mail client for GNOME
 Reverse Depends: balsa
 Installations reported by Popcon: 663
 Bug Report URL: https://bugs.debian.org/642906

   cargo (#860116), requested 1815 days ago
 Description: Rust package manager
 Reverse Depends: dh-cargo rust-all
 Installations reported by Popcon: 2835
 Bug Report URL: https://bugs.debian.org/860116

   courier (#978755), requested 455 days ago
 Description: Courier mail server
 Reverse Depends: courier-faxmail courier-filter-perl courier-imap
   courier-ldap courier-mlm courier-mta courier-pcp courier-pop
   courier-webadmin couriergrey (3 more omitted)
 Installations reported by Popcon: 862
 Bug Report URL: https://bugs.debian.org/978755

   cron (#984736), requested 389 days ago
 Description: new maintainer need
 Reverse Depends: apticron autolog backintime-common btrfsmaintenance
   buildd checksecurity clamtk cricket email-reminder exim4-base (20
   more omitted)
 Installations reported by Popcon: 208551
 Bug Report URL: https://bugs.debian.org/984736

   cyrus-imapd (#921717), requested 1147 days ago
 Description: Cyrus mail system - IMAP support
 Reverse Depends: cyrus-admin cyrus-caldav cyrus-clients cyrus-dev
   cyrus-imapd cyrus-murder cyrus-nntpd cyrus-pop3d cyrus-replication
 Installations reported by Popcon: 409
 Bug Report URL: https://bugs.debian.org/921717

   debtags (#962579), requested 659 days ago
 Description: Debian Package Tags support tools
 Reverse Depends: packagesearch
 Installations reported by Popcon: 1461
 Bug Report URL: https://bugs.debian.org/962579

   dee (#831388), requested 2085 days ago
 Description: model to synchronize mutiple instances over DBus
 Reverse Depends: dee-too

Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Sean Anderson

On 3/31/22 8:36 PM, Antoine Beaupré wrote:

On 2022-03-31 18:55:44, Sean Anderson wrote:

Hi Antoine,

On 3/31/22 10:19 AM, Antoine Beaupré wrote:

On 2022-03-31 10:06:40, Antoine Beaupré wrote:


[...]


I've packaged around 20 dependencies so far.


Impressive! Good job!


I have yet to submit them (primarily because I find doing this sort of
work sucks the energy out of me). I did not quite realize what I was
getting myself into :)


That must be indeed *so* hard! I think it's worth at least pushing what
you have to salsa, so that someone else can carry the torch from where
you stopped, if you get tired of this. Who knows, another golang
packager might also need the same dep and help you!


My TODO list follows. Packages with a # are done, those with a !
have an error, and I forget what - means.


Really nice, a few comments inline...


loki
#github.com/Workiva/go-datastructures
#github.com/joncrlsn/dque
#github.com/c2h5oh/datasize
#github.com/shurcooL/vfsgen
   github.com/prometheus/prometheus


surely that is packaged somehow. we have the `prometheus` binary package
already in Debian, maybe that could be reused?


Sorry, # is more like "I packaged it or someone else has" (e.g. no more work 
necessary)


   github.com/cortexproject/cortex


oh wow, they link against cortex! that's massive right there...


#github.com/uber/jaeger-client-go


i think i commented out the code linking to this in some other golang
package, and i can't remember which one it is right now. That is
probably as unhelpful as it sounds. :p


dskit
^go.etcd.io/etcd


wtf, they link to etcd too.. wth is this thing. that is certainly used
by k8s.


migrate
   modernc.org/sqlite


that one is massive. i started using it for wallabako (#893648) and it
brought in a ridiculous number of deps. but it's faster and more
portable than the other sqlite lib I was using before, so that would be
really nice to have in Debian.

... if a little bonkers (that thing basically transpiles sqlite from C
to golang).


-gopkg.in/natefinch/lumberjack.v2


that's another one I used in wallabako, probably worth packaging in
debian in general, just because a bunch of golang packages are likely to
use it as well.


Basically I looked at this and thought "OK that's 20 or so first order deps,
I can do this" and then I discovered that several of these had 20 first-order
deps of their own.


I can make an effort to submit the ones I have packaged, but I haven't
worked on this for a bit (as other projects took priority)


That's absolutely fine, I think, and it would be really awesome if you
could push what you have somewhere already, so that if someone wants to
resume the work on loki, they can start from there.

And, alternatively, that work would be useful for other packaging
efforts, I am sure.

Thank you so much!


Well, as a first step, I requested access to the golang package group, but
it looks like it was never approved. My username is butterball_geometry.

--Sean



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2022-03-31 20:54:32, Sean Anderson wrote:
> On 3/31/22 8:36 PM, Antoine Beaupré wrote:

[...]

> Basically I looked at this and thought "OK that's 20 or so first order deps,
> I can do this" and then I discovered that several of these had 20 first-order
> deps of their own.

Typical dependency hell. I'm so sorry for your loss of innocence. :p

>>> I can make an effort to submit the ones I have packaged, but I haven't
>>> worked on this for a bit (as other projects took priority)
>> 
>> That's absolutely fine, I think, and it would be really awesome if you
>> could push what you have somewhere already, so that if someone wants to
>> resume the work on loki, they can start from there.
>> 
>> And, alternatively, that work would be useful for other packaging
>> efforts, I am sure.
>> 
>> Thank you so much!
>
> Well, as a first step, I requested access to the golang package group, but
> it looks like it was never approved. My username is butterball_geometry.

I just approved you.

-- 
Work expands so as to fill the time available for its completion.
- Parkinson's law



Bug#1008768: ITP: pytest-relaxed -- provide relaxed test discovery for pytest

2022-03-31 Thread Antoine Beaupre
Package: wnpp
Severity: wishlist
Owner: Antoine Beaupre 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: pytest-relaxed
  Version : 1.1.5
  Upstream Author : bitprophet
* URL : https://github.com/bitprophet/pytest-relaxed/
* License : BSD-2
  Programming Lang: Python
  Description : provide relaxed test discovery for pytest

This is the spiritual successor to https://pypi.python.org/pypi/spec,
but is built for pytest instead of nosetests, and rethinks some
aspects of the design (such as increased ability to opt-in to various
behaviors.)

Has it ever felt strange to you that we put our tests in tests/, then
name the files test_foo.py, name the test classes TestFoo, and finally
name the test methods test_foo_bar? Especially when almost all of the
code inside of tests/ is, well, tests?

This pytest plugin takes a page from the rest of Python, where you
don't have to explicitly note public module/class members, but only
need to hint as to which ones are private. By default, all files and
objects pytest is told to scan will be considered tests; to mark
something as not-a-test, simply prefix it with an underscore.



This is a dependency of the python-invoke test suite. Binary package
would, of course, probably be python3-pytest-relaxed.



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Sean Anderson

On 3/31/22 9:05 PM, Antoine Beaupré wrote:

On 2022-03-31 20:54:32, Sean Anderson wrote:

On 3/31/22 8:36 PM, Antoine Beaupré wrote:


[...]


Basically I looked at this and thought "OK that's 20 or so first order deps,
I can do this" and then I discovered that several of these had 20 first-order
deps of their own.


Typical dependency hell. I'm so sorry for your loss of innocence. :p


I can make an effort to submit the ones I have packaged, but I haven't
worked on this for a bit (as other projects took priority)


That's absolutely fine, I think, and it would be really awesome if you
could push what you have somewhere already, so that if someone wants to
resume the work on loki, they can start from there.

And, alternatively, that work would be useful for other packaging
efforts, I am sure.

Thank you so much!


Well, as a first step, I requested access to the golang package group, but
it looks like it was never approved. My username is butterball_geometry.


I just approved you.



OK, I uploaded a package to 
https://salsa.debian.org/go-team/packages/golang-github-c2h5oh-datasize/

Can you have a quick look at it? I used dh-make-golang, but if there's
anything I need to tweak I'd like to know before I start uploading.

And should I send ITPs for everything, or is it OK to leave the closes
as TODO in the changelog?

--Sean



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2022-03-31 21:15:21, Sean Anderson wrote:
> OK, I uploaded a package to 
> https://salsa.debian.org/go-team/packages/golang-github-c2h5oh-datasize/
>
> Can you have a quick look at it? I used dh-make-golang, but if there's
> anything I need to tweak I'd like to know before I start uploading.

This looks good to me. Did you ask upstream for tags? Sometimes it
actually works! :)

> And should I send ITPs for everything, or is it OK to leave the closes
> as TODO in the changelog?

Typically I like to fire ITPs for everything, because the roundtrip with
NEW can be slow at times. It might also give a heads up for the FTP team
of the relationships between the packages, which might not be obvious
from the names.

-- 
Drowning people
Sometimes die
Fighting their rescuers.
- Octavia Butler



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Sean Anderson

On 3/31/22 9:21 PM, Antoine Beaupré wrote:

On 2022-03-31 21:15:21, Sean Anderson wrote:

OK, I uploaded a package to 
https://salsa.debian.org/go-team/packages/golang-github-c2h5oh-datasize/

Can you have a quick look at it? I used dh-make-golang, but if there's
anything I need to tweak I'd like to know before I start uploading.


This looks good to me. Did you ask upstream for tags? Sometimes it
actually works! :)


I did not. I'm going to start by focusing on uploading my past work.


And should I send ITPs for everything, or is it OK to leave the closes
as TODO in the changelog?


Typically I like to fire ITPs for everything, because the roundtrip with
NEW can be slow at times. It might also give a heads up for the FTP team
of the relationships between the packages, which might not be obvious
from the names.


Sending these out might be the slowest part of all this >.>

And what's the proper way to update an existing package? Should I create a PR?
Or should I just push directly? (what's the review process like)

--Sean



Bug#1008769: ITP: golang-github-joncrlsn-dque -- dque is a fast, embedded, durable queue for Go

2022-03-31 Thread Sean Anderson
Package: wnpp
Severity: wishlist
Owner: Sean Anderson 

* Package name: golang-github-joncrlsn-dque
  Version : 2.2.0-1
  Upstream Author : Jon Carlson
* URL : https://github.com/joncrlsn/dque
* License : Expat
  Programming Lang: Go
  Description : dque is a fast, embedded, durable queue for Go

 dque - a fast embedded durable queue for Go. dque is
 - persistent -- survives program restarts
 - scalable -- not limited by your RAM, but by your disk space
 - FIFO -- First In First Out
 - embedded -- compiled into your Golang program
 - synchronized -- safe for concurrent usage
 - fast or safe, you choose -- turbo mode lets the OS decide when to write to
   disk
 - has a liberal license -- allows any use, commercial or personal
 .
 This is a dependency of loki.



Re: Bug#1001903: ITP: loki-database -- Like Prometheus, but for logs.

2022-03-31 Thread Antoine Beaupré
On 2022-03-31 21:28:05, Sean Anderson wrote:
> On 3/31/22 9:21 PM, Antoine Beaupré wrote:
>> On 2022-03-31 21:15:21, Sean Anderson wrote:
>>> OK, I uploaded a package to 
>>> https://salsa.debian.org/go-team/packages/golang-github-c2h5oh-datasize/
>>>
>>> Can you have a quick look at it? I used dh-make-golang, but if there's
>>> anything I need to tweak I'd like to know before I start uploading.
>> 
>> This looks good to me. Did you ask upstream for tags? Sometimes it
>> actually works! :)
>
> I did not. I'm going to start by focusing on uploading my past work.

no problem.

>>> And should I send ITPs for everything, or is it OK to leave the closes
>>> as TODO in the changelog?
>> 
>> Typically I like to fire ITPs for everything, because the roundtrip with
>> NEW can be slow at times. It might also give a heads up for the FTP team
>> of the relationships between the packages, which might not be obvious
>> from the names.
>
> Sending these out might be the slowest part of all this >.>

How so? Do you have to copy-paste those in an MTA? :)

I found that setting up a local MTA helps tremendously in dealing with
those kind of problems, as you can just pipe things around easily...

> And what's the proper way to update an existing package? Should I create a PR?
> Or should I just push directly? (what's the review process like)

Since this is a 25+ year old project, there's probably a dozen ways to
do this. The canonical way is to open a bug report with a patch in the
BTS (bugtracker we're talking through here). If that doesn't get a
response, in theory, you're allowed to do an NMU. If that doesn't work,
you're allowed, again in theory, to salvage the package.

And then there's salsa where you can send merge requests. But sometimes
those get ignored by graybeards like me who forget it exists or forget
to setup notifications, so the BTS is always a safer bet.

All those acronyms are expanded somewhere in this article I just wrote
about salvaging packages, by pure coincidence (i swear):

https://anarc.at/blog/2022-03-31-first-package-salvaged/

Let me know if you have any further question
-- 
La nature n'a créé ni maîtres ni esclaves
Je ne veux ni donner ni recevoir de lois.
- Denis Diderot



Epoch for cl-anaphora

2022-03-31 Thread Sean Whitton
Hello,

I took over upstream maintenance of this package recently and started
tagging releases again.  The most recent release is 0.9.8.  But the
Debian package version is 20210111.gitab5f07e-1.  So I would like to
bump the epoch to go back to using upstream versions.  Thanks!

-- 
Sean Whitton


signature.asc
Description: PGP signature