Hi Eric!
Eric Evans writes:
> This is now a blocker on a recent upstream release of
> golang-github-gocql-gocql as well. I understand the argument about
> excluding test data, but there is probably a point at which users would be
> better served by a golang-github-pierrec-lz4.v4 without (comple
Package: syncthing
Version: 1.18.6~ds1-1~bpo11+1
Severity: normal
Control: affects -1 golang-github-shirou-gopsutil
Dear Maintainer,
The upload of golang-github-shirou-gopsutil/3.21.10-1 introduced the
following breaking changes:
https://github.com/shirou/gopsutil/blob/master/README.md#v3-mig
Source: golang-github-satta-ifplugo
Severity: normal
Control: affects -1 golang-github-shirou-gopsutil
Dear Maintainer,
The upload of golang-github-shirou-gopsutil/3.21.10-1 introduced the
following breaking changes:
https://github.com/shirou/gopsutil/blob/master/README.md#v3-migration
http
Package: golang-github-hashicorp-consul-dev
Severity: normal
Control: affects -1 golang-github-shirou-gopsutil
Dear Maintainer,
The upload of golang-github-shirou-gopsutil/3.21.10-1 introduced the
following breaking changes:
https://github.com/shirou/gopsutil/blob/master/README.md#v3-migratio
Control: tag -1 -moreinfo
Hi Sergio,
First, sorry it took me so long to follow up on this bug! [this reply
has been sitting in my drafts folder for almost two years :/]
With the info you've provided it looks like the issue has been resolved.
Rebuilding the index was a good idea :-) That said, d
Control: tag -1 -pending
Upload rejected because ftpmasters did not accept that the public domain
works had been implicitly relicensed by upstream as BSD-3-clause,
because I missed one Linux kernel image file in the test data (which
needs source to be DFSG free and for license compliance; this one
Nicholas D Steeves writes:
> I made some progress towards this, and our repository is currently at
> 1.19.1, but I am currently blocked by some failing tests with "no test
> files" and have run out of energy.
>
> Please lend assistance so that we can continue to make
I made some progress towards this, and our repository is currently at
1.19.1, but I am currently blocked by some failing tests with "no test
files" and have run out of energy.
Please lend assistance so that we can continue to make progress. Please
note that you'll need to build and add to a local
Control: retitle -1 Please import upstream v1.19.2
Control: block 884575 by -1
Syncthing Tray 1.1.17 requires Syncthing 1.19.2.
No immediate rush, since I still need to upload one more dependency, but
it would be nice to see Syncthing 1.19.2 imported in April :-)
Regards,
Nicholas
signature.as
Control: retitle -1 Please import upstream v1.19.1
I imported 1.18.6 into the repo, and plan to upload when the blocking
bug is resolved. That said, I decided to reuse this bug for upstream
v1.19.1, so have correspondingly retitled it; I won't close this bug
from the changelog of 1.18.6~ds1-1.
C
ailable for review here: https://salsa.debian.org/sten/syncthing.git
Reply follows inline.
Simon Frei writes:
> On 31/01/2022 03:04, Nicholas D Steeves wrote:
>> Aloïs Micard writes:
>>
>>> On Wed, 18 Nov 2020 11:10:44 +0100 =?utf-8?B?RsOpbGl4?= Sipma
>>> wrote:
Hi Félix,
Félix Sipma writes:
> Hi,
>
> Having a backport of syncthing would be great, but unfortunately I
> won't have a lot time to invest in it: a baby, a farm and involvement
> in other non-profit organisations do not let me as much time as I would
> like for Debian, sorry!
>
> Have a nic
Hi Félix and Aloïs,
Aloïs Micard writes:
> On Wed, 18 Nov 2020 11:10:44 +0100 =?utf-8?B?RsOpbGl4?= Sipma
> wrote:
>>
>> It would be nice to have a backport of syncthing. In particular, recent
>> versions contain several db optimisations.
>>
I didn't know about these db optimisations, but th
Source: syncthing
Severity: normal
X-Debbugs-Cc: s...@debian.org
Hi Alexandre!
Would you please import v1.18.6 into the repo? After that, I'll start
taking a look at what needs to be done, and I'm sure Aloïs will also
help out.
Cheers,
Nicholas
___
Pk
Subject: Please package stable tagged release v1.0.0
Source: golang-github-inconshreveable-mousetrap
Severity: normal
Hi,
While investigating alternatives to "Afterwriting", a nodejs fountain2pdf
converter with a nightmare dependency chain, I found "Wrap", which has much
more reasonable deps. It
Control: tag -1 +patch
I've filed an MR for each branch here:
https://salsa.debian.org/go-team/packages/golang-raven-go/-/merge_requests
Note that this update is still blocked by #966583.
Best,
Nicholas
signature.asc
Description: PGP signature
___
P
obvious oversights ;)
>
Of course, gladly! :-)
> On 21/07/2020 20:20, Nicholas D Steeves wrote:
>> Alexandre Viau writes:
>>> On Sun, Jul 19, 2020 at 10:57 PM Nicholas D Steeves
>>>> It seems to me that the most expedient path forward is to jump from
>>>
Source: golang-github-go-ldap-ldap
Version: 2.5.1-4
Severity: normal
Control: block 966466 by -1
Sorry for the delay filing this bug. I identified the blocking issue for
Syncthing ≥ 1.5.0 but was slow to file it.
___
Pkg-go-maintainers mailing list
Pkg
Package: syncthing
Version: 1.1.4~ds1-5
Severity: normal
Control: block -1 by 915649 966427
I was working on 1.5.1, but decided to do a quick check of what it would take
to jump straight to 1.7.1. My initial investigation showed the trip through
NEW for blobloom would probably be the greatest d
Update re: 1.5.0
This version requires golang-github-go-ldap-ldap-dev 3.1.7 and sid has
2.5.1. Is there pkg-go team tooling to parse go.mod:require() and run
rmadison against each dep?
blocked again.
signature.asc
Description: PGP signature
___
Pkg-
Hi Simon,
Thank you for replying, and sorry for the delay in my own.
On Tue, Apr 07, 2020 at 06:00:11PM +0200, Simon Frei wrote:
> Syncing a git repository, i.e. .git not the staging area, is prone to
> break: Git has an elaborate structure that needs to stay consistent,
> while Syncthing just se
Hi Alexandre,
Alexandre Viau writes:
> On Sun, Jul 19, 2020 at 10:57 PM Nicholas D Steeves
> wrote:
>> It seems to me that the most expedient path forward is to jump from
>> 1.2.x to 1.4.x. ACK?
>
> Right, it looks like we will have too.
>
> I was trying to avo
Hi Alexandre,
On Mon, Sep 16, 2019 at 01:46:06AM +0300, Giorgos Skafidas wrote:
> Package: syncthing
> Version: 1.0.0~ds1-1+b11
> Severity: wishlist
>
> Dear Maintainer,
>
> please consider updating Syncthing to its latest upstream version, 1.2.2.
>
> Thank you for your efforts!
I'm not famili
Control: block 964363 by -1
Hi,
On Wed, Dec 05, 2018 at 08:47:12PM +0530, Pirate Praveen wrote:
> Package: golang-github-getsentry-raven-go-dev
> Version: 0.0~git20150721.0.74c334d-4
> Severity: wishlist
>
> gitlab-workhorse 8.4 has the following in vendor.json
>
> "checksumSHA1": "hL8smC/vjdku
Package: go-mtpfs
Severity: normal
Hi,
Upstream released v1.0.0 several months ago. Please package this version or
newer.
Thanks!
Nicholas
P.S. My old died, and the replacement doesn't support MSC, which is why I'm
reviewing the available options for MTP support in Debian.
_
Control: tag -1 moreinfo
Hi Sergio,
Thank you for the bug report, reply follows inline:
On Sun, Oct 06, 2019 at 04:28:03AM +0300, sergio wrote:
> Package: syncthing
> Version: 1.1.4~ds1-4
> Severity: normal
>
> Dear Maintainer,
>
> % du -sh .config/syncthing/index-v0.14.0.db
> 2.2G .config/sy
Package: syncthing
Version: 1.0.0~ds1-1+b11
Severity: normal
I thought it would be neat to sync all my Debian work between my desktop and
laptop with syncthing, but ran into the following issue:
Steps to reproduce:
1. Setup two nodes, and add a ~/devel filled with git repos as a sync target.
2.
27 matches
Mail list logo
