Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

[Andreas Tille]

Hi again,

On Wed, May 30, 2018 at 07:50:01AM +0200, Alexander Wirt wrote:
> > > Your repo has lfs disabled. You should enable it. 
> > 
> > How can I do this?
> > I've just found[1]:  "Your administrator only need to enable the LFS 
> > option."
> *seufz* we enabled it, but as you can guess it needs to get enabled per repo.
> 
> Settings -> Permissions -> Git Large File Storage

Thanks for the hint.  I would not call "Permissions" the obvious place to
look for this and my web search did not uncover this, sorry.

Unfortunately it does not work yet:


gatk(master) $ git push
Counting objects: 4599, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4453/4453), done.
Writing objects: 100% (4599/4599), 64.56 MiB | 462.00 KiB/s, done.
Total 4599 (delta 811), reused 1 (delta 0)
remote: Resolving deltas: 100% (811/811), completed with 1 local object.
remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a 
manual "git lfs push --all".
To salsa.debian.org:med-team/gatk.git
 ! [remote rejected] master -> master (pre-receive hook declined)
 ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook declined)
 ! [remote rejected] upstream -> upstream (pre-receive hook declined)
 ! [remote rejected] upstream/4.0.4.0 -> upstream/4.0.4.0 (pre-receive hook 
declined)
error: failed to push some refs to 'g...@salsa.debian.org:med-team/gatk.git'
gatk(master) $ git lfs push --all
Specify a remote and a remote branch name (`git lfs push origin master`)
gatk(master) $ LC_ALL=C git lfs push origin master
Locking support detected on remote "origin". Consider enabling it with:
  $ git config 
lfs.https://salsa.debian.org/med-team/gatk.git/info/lfs.locksverify true
LFS upload missing objects: (0/246), 0 B | 0 B/s

   
  (missing) src/test/resources/large/NA24385.vcf.gz 
(f3326d552a86197e1d8fbfee2941f6b8684f7b31bfab9730f953401566066e2b)
  (missing) 
src/test/resources/large/VQSR/ALL.wgs.indels_mills_devine_hg19_leftAligned_collapsed_double_hit.sites.20.1M-10M.vcf
 (48f0bdac467ee4d618e6425c0989a344e5d8523baaf5016e92ef246c4311c58b)
  (missing) src/test/resources/large/VQSR/g94982_b37_chr20_1m_10m.vcf.gz.tbi 
(97a7c779a82a4e3aea8de77a4e9bda68909d489e3c0553399c1e9affbba6c0d8)
  (missing) 
src/test/resources/large/cnv_somatic_workflows_test_files/wgs-no-gc.pon.hdf5 
(b916357182a024e126b7754e41d134e67e26d6328538eee8865ac264c981ab04)
  (missing) src/test/resources/large/mutect/dream_synthetic_bams/tumor_2.bam 
(9d9ce1ff6c68429befeef11b9626a959af109aa99a637f89d2abf643ab524ffb)
  (missing) 
src/test/resources/large/mutect/dream_synthetic_bams/normal_1.bam.bai 
(369eed4192701e4abd5a9be1e4d308ce46232983812a854a847465ab7a2fc2a5)
  (missing) 
src/test/resources/large/mutect/dream_synthetic_bams/tumor_1.bam.bai 
(566ede9346c4260d7810e112bd4f4892ab1aaa37f5b20ebf4b3ba0fe83db2993)
Uploading LFS objects:   0% (0/246), 0 B | 0 B/s, done
  (missing) src/test/resources/large/gvcfs/combined.gatk3.7.g.vcf.gz.tbi 
(403996681f4a0622236a45c71a63ba8c3594664e379cde16efd10f5f598499ff)
...
  (missing) src/test/resources/large/VQSR/snpRecal.vcf 
(a9c2535862d234fd09c5978c00a6127caa079989158a93cb13a2356911c561bb)
  (missing) 
src/test/resources/large/cnv_germline_workflows_test_files/SM-74P2T_20xy-downsampled.bam
 (7cfbe031257a12d39c460a775bd22b6713130b9a45f6976df7e7b1c7950a268b)
  (missing) src/test/resources/large/VQSR/g94982_b37_chr20_1m_10m.vcf.tbi 
(3540c3ec7d15607a541b5ccf51c8cc60d03d826c5abbd866f4573d2694a86e9f)
  (missing) 
src/test/resources/large/funcotator/gencode.v19.chr_patch_hapl_scaff.chr3.gtf 
(3e935c5ac87020a90689b86f9a6ca5f05c24736528f550ea54a0c84772c6fdd3)
  (missing) 
src/test/resources/large/cnv_somatic_workflows_test_files/wes-do-gc.pon.hdf5 
(b9c1b28743e4569379f987d5eeebc5393467fd2fc981c85475873b219576dfa4)
  (missing) 
src/test/resources/large/cnv_somatic_workflows_test_files/human_g1k_v37.chr-20.truncated.dict
 (604e04600e644864c34e2fce42241febac0f0be062223a66e88499fca1c55147)
  (missing) 
src/test/resources/large/cnv_somatic_workflows_test_files/SM-74NEG-v1-chr20-downsampled.deduplicated.cram.crai
 (fc99f68bcc0a4fc1ff3a240ad64d62fa8bfd31ecdc11d326107a5e1ec969ccca)
  (missing) 
src/test/resources/large/mutect/dream_synthetic_bams/normal_4.bam.bai 
(14620c7d836db17cd2d473658208d44ae3a5c3cec3baf0f6b697dcc87e7075b6)
gatk(master) git lfs push --all
Specify a remote and a remote branch name (`git lfs push origin master`)
gatk(master) $ git push
Counting objects: 4599, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4453/4453), done.
Writing objects: 100% (4599/4599), 64.56 MiB | 410.00 KiB/s, done.
Total 4599 (delta 810), reused 1 (delta 0)
remote: Resolving deltas: 100% (810/810), completed with 1 local object.
remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a 
manual "git lfs

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

[Alexander Wirt]

On Wed, 30 May 2018, Andreas Tille wrote:

> Hi,
> 
> On Tue, May 29, 2018 at 11:35:00PM +0200, Alexander Wirt wrote:
> > > I intend to push a new version of gatk[1] which contains some large
> > > files.  I imported the new upstream package the usual way.  But if I
> > > want to push I get:
> > > 
> > > (master) $ LC_ALL=C git push
> > > Counting objects: 4599, done.
> > > Delta compression using up to 4 threads.
> > > Compressing objects: 100% (4453/4453), done.
> > > Writing objects: 100% (4599/4599), 64.56 MiB | 1.09 MiB/s, done.
> > > Total 4599 (delta 811), reused 1 (delta 0)
> > > remote: Resolving deltas: 100% (811/811), completed with 1 local object.
> > > remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or 
> > > try a manual "git lfs push --all".
> > > To salsa.debian.org:med-team/gatk.git
> > >  ! [remote rejected] master -> master (pre-receive hook declined)
> > >  ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook 
> > > declined)
> > >  ! [remote rejected] upstream -> upstream (pre-receive hook declined)
> > >  ! [remote rejected] upstream/4.0.4.0 -> upstream/4.0.4.0 (pre-receive 
> > > hook declined)
> > > error: failed to push some refs to 
> > > 'g...@salsa.debian.org:med-team/gatk.git'
> > > 
> > > 
> > > I installed git-lfs locally and tried the command above but it seems it
> > > is really needed remotely on Salsa.  Am I missing something or is there
> > > some action needed?
> > Your repo has lfs disabled. You should enable it. 
> 
> How can I do this?
> I've just found[1]:  "Your administrator only need to enable the LFS option."
*seufz* we enabled it, but as you can guess it needs to get enabled per repo.

Settings -> Permissions -> Git Large File Storage
 
Alex

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

[Andreas Tille]

Hi,

On Tue, May 29, 2018 at 11:35:00PM +0200, Alexander Wirt wrote:
> > I intend to push a new version of gatk[1] which contains some large
> > files.  I imported the new upstream package the usual way.  But if I
> > want to push I get:
> > 
> > (master) $ LC_ALL=C git push
> > Counting objects: 4599, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (4453/4453), done.
> > Writing objects: 100% (4599/4599), 64.56 MiB | 1.09 MiB/s, done.
> > Total 4599 (delta 811), reused 1 (delta 0)
> > remote: Resolving deltas: 100% (811/811), completed with 1 local object.
> > remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or 
> > try a manual "git lfs push --all".
> > To salsa.debian.org:med-team/gatk.git
> >  ! [remote rejected] master -> master (pre-receive hook declined)
> >  ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook 
> > declined)
> >  ! [remote rejected] upstream -> upstream (pre-receive hook declined)
> >  ! [remote rejected] upstream/4.0.4.0 -> upstream/4.0.4.0 (pre-receive hook 
> > declined)
> > error: failed to push some refs to 'g...@salsa.debian.org:med-team/gatk.git'
> > 
> > 
> > I installed git-lfs locally and tried the command above but it seems it
> > is really needed remotely on Salsa.  Am I missing something or is there
> > some action needed?
> Your repo has lfs disabled. You should enable it. 

How can I do this?
I've just found[1]:  "Your administrator only need to enable the LFS option."

Thanks for any hint

 Andreas.


[1] https://about.gitlab.com/2017/01/30/getting-started-with-git-lfs-tutorial/

-- 
http://fam-tille.de

Re: debian/watch for bintray ?

[Paul Wise]

On Wed, May 30, 2018 at 11:17 AM, Dirk Eddelbuettel wrote:

> Oh, nice!  With one of those sed expressions in the watch file you mean?

Yeah, there are some examples in the codesearch link above:

opts=downloadurlmangle=s/://,filenamemangle=s/://

https://codesearch.debian.net/search?q=path%3Adebian%2Fwatch+bintray

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
http://bonedaddy.net/pabs3/
http://wiki.openmoko.org/wiki/User:PaulWise

Re: debian/watch for bintray ?

[Dirk Eddelbuettel]

On 26 May 2018 at 11:00, Paul Wise wrote:
| On Sat, May 26, 2018 at 10:50 AM, Dirk Eddelbuettel wrote:
| 
| >https://www.quantlib.org/download.shtml
| 
| The bintray URL there eventually points here:
| 
| https://dl.bintray.com/quantlib/releases/
| 
| That has all the versions and if you remove the : character from the
| download URLs, then you can get tarballs.

Oh, nice!  With one of those sed expressions in the watch file you mean?
 
| BTW, you might want to let them know that the packages.d.o link there
| is obsolete:
| 
| You reached this site over an old URL. Depending on the exact
| parameters your search might work or not.
| 
| I suggest they switch to this one:
| 
| https://packages.debian.org/src:quantlib

I should, and will (unless I forget/get distracted).

Thanks!

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#900386: ITP: r-cran-rio -- GNU R package with Swiss-army knife for data i/o

[Dirk Eddelbuettel]

Package: wnpp
Owner: Dirk Eddelbuettel 
Severity: wishlist

* Package name: r-cran-rio
  Version : 0.5.10
  Upstream Author : Thomas Leeper 
* URL or Web page : https://cran.r-project.org/package=rio
* License : GPL-2
  Description : GNU R package with Swiss-army knife for data i/o

This is another new Build-Depends of package r-cran-car (which has been in
Debian since 2003); this package had been waiting on its own Build-Depends
r-cran-openxlsx for a few weeks.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#900385: ITP: golang-github-google-uuid -- generates and inspects UUIDs based on RFC 4122

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-devel@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org

   Package name: golang-github-google-uuid
Version: 0.2
Upstream Author: Google
License: BSD-3-Clause
URL: https://github.com/google/uuid
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-google-uuid
Description: generates and inspects UUIDs based on RFC 4122
 This package generates and inspects UUIDs based on RFC 4122
 (http://tools.ietf.org/html/rfc4122) and DCE 1.1: Authentication and
 Security Services.
 .
 This package is based on the "github.com/pborman/uuid" package. It differs
 from these earlier packages in that a UUID is a 16 byte array rather than
 a byte slice. One loss due to this change is the ability to represent an
 invalid UUID (vs a NIL UUID).


signature.asc
Description: This is a digitally signed message part.

Re: Removing packages perhaps too aggressively?

[Vincent Lefevre]

On 2018-05-29 15:35:24 +0200, Steve Cotton wrote:
> On Tue, May 29, 2018 at 03:03:11PM +0200, Vincent Lefevre wrote:
> > On 2018-05-23 09:46:09 +0800, Paul Wise wrote:
> > > Depends on obsolete WebKit version (fixed in experimental):
> > > 
> > > https://tracker.debian.org/pkg/gnucash
> > > https://tracker.debian.org/news/859896/gnucash-removed-from-testing/
> > > https://bugs.debian.org/790204
> > 
> > This bug was closed 4 months ago.
> 
> Fixed in experimental, but still open on the version in unstable.

But the bug status is closed. In particular, it is no longer shown
by the tracker:

  https://tracker.debian.org/pkg/gnucash

If one clicks on the number in the "RC" line, one just gets #893077,
which is a different bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

[Alexander Wirt]

On Tue, 29 May 2018, Andreas Tille wrote:

> Hi,
> 
> I intend to push a new version of gatk[1] which contains some large
> files.  I imported the new upstream package the usual way.  But if I
> want to push I get:
> 
> (master) $ LC_ALL=C git push
> Counting objects: 4599, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (4453/4453), done.
> Writing objects: 100% (4599/4599), 64.56 MiB | 1.09 MiB/s, done.
> Total 4599 (delta 811), reused 1 (delta 0)
> remote: Resolving deltas: 100% (811/811), completed with 1 local object.
> remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try 
> a manual "git lfs push --all".
> To salsa.debian.org:med-team/gatk.git
>  ! [remote rejected] master -> master (pre-receive hook declined)
>  ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook declined)
>  ! [remote rejected] upstream -> upstream (pre-receive hook declined)
>  ! [remote rejected] upstream/4.0.4.0 -> upstream/4.0.4.0 (pre-receive hook 
> declined)
> error: failed to push some refs to 'g...@salsa.debian.org:med-team/gatk.git'
> 
> 
> I installed git-lfs locally and tried the command above but it seems it
> is really needed remotely on Salsa.  Am I missing something or is there
> some action needed?
Your repo has lfs disabled. You should enable it. 

Alex
 

remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

[Andreas Tille]

Hi,

I intend to push a new version of gatk[1] which contains some large
files.  I imported the new upstream package the usual way.  But if I
want to push I get:

(master) $ LC_ALL=C git push
Counting objects: 4599, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4453/4453), done.
Writing objects: 100% (4599/4599), 64.56 MiB | 1.09 MiB/s, done.
Total 4599 (delta 811), reused 1 (delta 0)
remote: Resolving deltas: 100% (811/811), completed with 1 local object.
remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a 
manual "git lfs push --all".
To salsa.debian.org:med-team/gatk.git
 ! [remote rejected] master -> master (pre-receive hook declined)
 ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook declined)
 ! [remote rejected] upstream -> upstream (pre-receive hook declined)
 ! [remote rejected] upstream/4.0.4.0 -> upstream/4.0.4.0 (pre-receive hook 
declined)
error: failed to push some refs to 'g...@salsa.debian.org:med-team/gatk.git'


I installed git-lfs locally and tried the command above but it seems it
is really needed remotely on Salsa.  Am I missing something or is there
some action needed?

Kind regards

   Andreas.

[1] https://salsa.debian.org/med-team/gatk

-- 
http://fam-tille.de

Bug#900371: ITP: libhttp-tiny-multipart-perl -- module to add post_multipart method to HTTP::Tiny

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org

* Package name: libhttp-tiny-multipart-perl
  Version : 0.08
  Upstream Author : Renee Baecker 
* URL : https://metacpan.org/release/HTTP-Tiny-Multipart
* License : Artistic-2.0
  Programming Lang: Perl
  Description : module to add post_multipart method to HTTP::Tiny

HTTP::Tiny::Multipart adds a post_multipart method to HTTP::Tiny.

HTTP::Tiny is a very simple HTTP/1.1 client, designed for doing simple
requests without the overhead of a large framework like LWP::UserAgent, and
is part of perl core since 5.13.9

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Re: Bug#900286: ITP: spm -- simple password manager

[Ansgar Burchardt]

On Tue, 2018-05-29 at 13:11 -0400, Nicholas D Steeves wrote:
> On Mon, May 28, 2018 at 07:46:59PM +0200, Jakub Wilk wrote:
> > * Paride Legovini , 2018-05-28, 17:33:
> > > spm is a single fully POSIX shell compliant script
> 
> [...]
> > > In Debian the script will be installed as 'spm.sh'
> > 
> > That would be against Policy §10.4.
> > Please talk to upstream about choosing a different name.
> 
> Are there any reasons why a debian/spm.install like this one wouldn't
> be an appropriate solution to §10.4?
> 
> #!/usr/bin/dh-exec
> spm.sh => /usr/bin/spm

/usr/bin/spm is already shipped by another package as noted in the
initial report.

Renaming the binary to simple-password-manager or so would probably
work.

Ansgar

Re: Bug#900286: ITP: spm -- simple password manager

[Nicholas D Steeves]

On Mon, May 28, 2018 at 07:46:59PM +0200, Jakub Wilk wrote:
> * Paride Legovini , 2018-05-28, 17:33:
> > spm is a single fully POSIX shell compliant script
[...]
> > In Debian the script will be installed as 'spm.sh'
> 
> That would be against Policy §10.4.
> Please talk to upstream about choosing a different name.

Are there any reasons why a debian/spm.install like this one wouldn't
be an appropriate solution to §10.4?

#!/usr/bin/dh-exec
spm.sh => /usr/bin/spm

I guess it might be annoying to carry a patch for a manpage that would
effectively s/spm.sh/spm/...

Cheers,
Nicholas


signature.asc
Description: PGP signature

Re: Removing packages perhaps too aggressively?

[Ian Campbell]

On Tue, 2018-05-29 at 15:00 +0200, Vincent Lefevre wrote:
> On 2018-05-22 15:19:50 +0500, Andrey Rahmatullin wrote:
> > On Tue, May 22, 2018 at 11:43:31AM +0200, Heinz Repp wrote:
> > > Just stumbled over some removals:
> > > 
> > > GnuCash removed from testing in August 2017
> > > FreeCad removed from testing in October 2017
> > > 
> > > no sign of any effort to readd them in sight ...
> > 
> > Maybe you are looking in a wrong place.
> > Last gnucash upload was in April.
> 
> But still not in testing:

Nonetheless, "being worked on in unstable/experimental" is nowhere near
the same as "no sign of any effort to readd them in sight", which was
the original claim.

Ian.

Re: Removing packages perhaps too aggressively?

[Steve Cotton]

On Tue, May 29, 2018 at 03:03:11PM +0200, Vincent Lefevre wrote:
> On 2018-05-23 09:46:09 +0800, Paul Wise wrote:
> > Depends on obsolete WebKit version (fixed in experimental):
> > 
> > https://tracker.debian.org/pkg/gnucash
> > https://tracker.debian.org/news/859896/gnucash-removed-from-testing/
> > https://bugs.debian.org/790204
> 
> This bug was closed 4 months ago.

Fixed in experimental, but still open on the version in unstable.

BR,
Steve

Re: Removing packages perhaps too aggressively?

[Vincent Lefevre]

On 2018-05-23 09:46:09 +0800, Paul Wise wrote:
> On Tue, May 22, 2018 at 5:43 PM, Heinz Repp wrote:
> 
> > GnuCash removed from testing in August 2017
> 
> Depends on obsolete WebKit version (fixed in experimental):
> 
> https://tracker.debian.org/pkg/gnucash
> https://tracker.debian.org/news/859896/gnucash-removed-from-testing/
> https://bugs.debian.org/790204

This bug was closed 4 months ago.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Removing packages perhaps too aggressively?

[Vincent Lefevre]

On 2018-05-22 15:19:50 +0500, Andrey Rahmatullin wrote:
> On Tue, May 22, 2018 at 11:43:31AM +0200, Heinz Repp wrote:
> > Just stumbled over some removals:
> > 
> > GnuCash removed from testing in August 2017
> > FreeCad removed from testing in October 2017
> > 
> > no sign of any effort to readd them in sight ...
> Maybe you are looking in a wrong place.
> Last gnucash upload was in April.

But still not in testing:

$ apt-show-versions -a gnucash
gnucash:amd64 1:2.6.19-1 install ok installed
gnucash:amd64 1:2.6.15-1 stable   ftp.fr.debian.org
No stable-updates version
No testing version
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#900355: ITP: golang-github-throttled-throttled -- rate limiting access to resources such as HTTP endpoints

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-devel@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: block 823556 by -1
Control: block -1 by 900340

   Package name: golang-github-throttled-throttled
Version: 2.2.1
Upstream Author: 2014 Martin Angers
License: BSD-3-Clause
URL: https://github.com/throttled/throttled
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-throttled-throttled
Description: rate limiting access to resources such as HTTP endpoints
 Throttled implements rate limiting using the generic cell rate algorithm
 (https://en.wikipedia.org/wiki/Generic_cell_rate_algorithm) to limit
 access to resources such as HTTP endpoints.


signature.asc
Description: This is a digitally signed message part.

Re: make compilation not so gray

[Thomas Goirand]

On 05/26/2018 03:57 AM, Craig Small wrote:
> 
> 
> On Fri, 25 May 2018, 22:21 Adam Borowski,  > wrote:
> 
> But, nice folks who make gcc have introduced an option which helps here:
> -fdiagnostics-color.  It's very nice even for terse logs (such as the
> kernel), but for our use case it gives a ridiculously good improvement:
> instead of having to read a log pretty much line-by-line, you wiggle the
> scrollbar and watch for that speck of red flashing by.
> 
> 
> I think this is a great idea. There have been many others in this thread
> but just turning on the colour would be an improvement.
> 
>  - Craig

+1

Thanks Adam for working on this.

Re: Want to make salsa advertise contact and source code details [and 1 more messages]

[Ian Jackson]

Ansgar Burchardt writes ("Re: Want to make salsa advertise contact and source 
code details [and 1 more messages]"):
> That seems like an horrible maintenance nightmare just to avoid even
> talking to upstream...

OK, so does someone in Debian, maybe from the Salsa team, have any
contacts I could use ?  (I promise to be reasonable and polite.)
Or should I just try to go in through the "front door" and create an
issue in Gitlab CE's gitlab ?

ISTM that the former approach is more likely to work if we know anyone
at Gitlab already.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#900348: Bug #900348: ITP: sudo-pair

[Nicolas Braud-Santoni]

X-Debbugs-CC: debian-devel@lists.debian.org

On Tue, May 29, 2018 at 01:05:22PM +0200, Nicolas Braud-Santoni wrote:
> * Package name: sudo-pair

PS: I considered using the name libsudo-pair, but we already ship a sudo
policy plugin as sudo-ldap, and I prefer to be consistent.

Bug#900348: ITP: sudo-pair -- Plugin for sudo that requires another human to approve and monitor privileged sudo sessions.

[Nicolas Braud-Santoni]

Package: wnpp
Severity: wishlist
Owner: Nicolas Braud-Santoni 

* Package name: sudo-pair
  Version : 1.1.0
  Upstream Author : Square Inc.
* URL : https://github.com/square/sudo_pair
* License : Apache 2.0
  Programming Lang: Rust
  Description : Plugin for sudo that requires another human to approve and 
monitor privileged sudo sessions.

sudo is used to run commands as privileged users, but on some sensitive systems,
you really want to ensure that no individual can act entirely autonomously. This
plugin enforces that no user can act entirely on their own authority within
these systems, by requiring a separate auditor to monitor the interactive sudo
session.

Bug#900342: ITP: golang-github-mssola-user-agent -- HTTP User Agent parser for Golang

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-devel@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org

   Package name: golang-github-mssola-user-agent
Version: 0.4.1
Upstream Author: Miquel Sabaté Solà
License: Expat
URL: https://github.com/mssola/user_agent
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-mssola-user-agent
Description: HTTP User Agent parser for Golang
 Go library that parses HTTP User Agents.


signature.asc
Description: This is a digitally signed message part.

Bug#900340: ITP: golang-github-gomodule-redigo -- Go client for Redis

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-devel@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org

   Package name: golang-github-gomodule-redigo
Version: 2.0.0
Upstream Author: Gary Burd
License: Apache-2.0
URL: https://github.com/gomodule/redigo
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-gomodule-redigo
Description: Go client for Redis
 Go client for the Redis (http://redis.io/) database.
 Features
  • A Print-like API with support for all Redis commands.
  • Pipelining including pipelined transactions.
  • Publish/Subscribe
  • Connection pooling
  • Script helper type with optimistic use of EVALSHA.
  • Helper functions for working with command replies.


signature.asc
Description: This is a digitally signed message part.