Re: git-ubuntu 0.7.3 in edge/candidate/stable channels [Was Re: git-ubuntu 0.7.1 in edge/candidate/stable channels]

2018-03-12 Thread Nish Aravamudan
On Fri, Mar 2, 2018 at 2:00 PM, Nish Aravamudan wrote: > On Thu, Mar 1, 2018 at 5:20 PM, Nish Aravamudan > wrote: >> On 28.02.2018 [21:33:38 -0800], Nish Aravamudan wrote: >>> Hello all! >>> >>> I am happy to announce the release of

New Qt5 Uploader - Simon Quigley

2018-03-12 Thread Lukasz Zemczak
Hello everyone, Please congratulate Simon on his successful Ubuntu Qt5 Uploaders application! Being part of the team, tsimonq2 now has upload rights to Qt5 packages in the Ubuntu archives. Cheers! -- Łukasz 'sil2100' Zemczak Foundations Team lukasz.zemc...@canonical.com www.canonical.com

Re: zstd compression for packages

2018-03-12 Thread Colin Watson
On Mon, Mar 12, 2018 at 03:36:11PM +0100, Julian Andres Klode wrote: > Acknowledged. I don't think we want to go ahead without dpkg upstream > blessing anyway. On the APT side, we don't maintain Ubuntu-only branches, > so if we get a go-ahead it would land in Debian immediately too. Good. > I

Re: zstd compression for packages

2018-03-12 Thread Balint Reczey
Hi Daniel, On Mon, Mar 12, 2018 at 2:11 PM, Daniel Axtens wrote: > Hi, > > I looked into compression algorithms a bit in a previous role, and to be > honest I'm quite surprised to see zstd proposed for package storage. zstd, > according to its own github repo, is

Re: zstd compression for packages

2018-03-12 Thread Julian Andres Klode
On Mon, Mar 12, 2018 at 02:19:18PM +, Colin Watson wrote: > On Mon, Mar 12, 2018 at 10:02:49AM -0400, Jeremy Bicha wrote: > > On Mon, Mar 12, 2018 at 6:06 AM, Julian Andres Klode > > wrote: > > > We are considering requesting a FFe for that - the features are not >

Re: zstd compression for packages

2018-03-12 Thread Colin Watson
On Mon, Mar 12, 2018 at 10:02:49AM -0400, Jeremy Bicha wrote: > On Mon, Mar 12, 2018 at 6:06 AM, Julian Andres Klode > wrote: > > We are considering requesting a FFe for that - the features are not > > invasive, and it allows us to turn it on by default in 18.10. > >

Re: zstd compression for packages

2018-03-12 Thread Robie Basak
On Mon, Mar 12, 2018 at 03:05:13PM +0100, Julian Andres Klode wrote: > On Mon, Mar 12, 2018 at 01:49:42PM +, Robie Basak wrote: > > On Mon, Mar 12, 2018 at 11:06:11AM +0100, Julian Andres Klode wrote: > > > We are considering requesting a FFe for that - the features are not > > > invasive,

Re: zstd compression for packages

2018-03-12 Thread Julian Andres Klode
On Mon, Mar 12, 2018 at 10:02:49AM -0400, Jeremy Bicha wrote: > On Mon, Mar 12, 2018 at 6:06 AM, Julian Andres Klode > wrote: > > We are considering requesting a FFe for that - the features are not > > invasive, and it allows us to turn it on by default in 18.10. > >

Re: zstd compression for packages

2018-03-12 Thread Julian Andres Klode
On Mon, Mar 12, 2018 at 09:30:16AM -0400, Neal Gompa wrote: > On Mon, Mar 12, 2018 at 9:11 AM, Daniel Axtens > wrote: > > Hi, > > > > I looked into compression algorithms a bit in a previous role, and to be > > honest I'm quite surprised to see zstd proposed for

Re: zstd compression for packages

2018-03-12 Thread Julian Andres Klode
On Mon, Mar 12, 2018 at 01:49:42PM +, Robie Basak wrote: > On Mon, Mar 12, 2018 at 11:06:11AM +0100, Julian Andres Klode wrote: > > We are considering requesting a FFe for that - the features are not > > invasive, and it allows us to turn it on by default in 18.10. > > libzstd has only been

Re: zstd compression for packages

2018-03-12 Thread Jeremy Bicha
On Mon, Mar 12, 2018 at 6:06 AM, Julian Andres Klode wrote: > We are considering requesting a FFe for that - the features are not > invasive, and it allows us to turn it on by default in 18.10. What does Debian's dpkg maintainer think? Thanks, Jeremy Bicha --

Re: [17.10] libssl-dev 1.0.2g is 1.0.0

2018-03-12 Thread Dimitri John Ledkov
Hello, On 11 March 2018 at 09:05, Frank Rehberger wrote: > Hi > > distribution : artful (ubuntu 17.10) > package libssl-dev [1.0.2g] > > the package libssl-dev claims to be 1.0.2g, but it seems to be older > header-version 1.0.0, as it lacks the constant > >

Re: zstd compression for packages

2018-03-12 Thread Robie Basak
On Mon, Mar 12, 2018 at 11:06:11AM +0100, Julian Andres Klode wrote: > We are considering requesting a FFe for that - the features are not > invasive, and it allows us to turn it on by default in 18.10. libzstd has only been stable in the archive since Artful. We had to SRU fixes to Xenial

[17.10] libssl-dev 1.0.2g is 1.0.0

2018-03-12 Thread Frank Rehberger
Hi distribution : artful (ubuntu 17.10) package libssl-dev [1.0.2g] the package libssl-dev claims to be 1.0.2g, but it seems to be older header-version 1.0.0, as it lacks the constant ./crypto/x509/x509_vfy.h:# define X509_V_ERR_INVALID_CALL 65 It seems libssl binary

Re: zstd compression for packages

2018-03-12 Thread Daniel Axtens
Hi, I looked into compression algorithms a bit in a previous role, and to be honest I'm quite surprised to see zstd proposed for package storage. zstd, according to its own github repo, is "targeting real-time compression scenarios". It's not really designed to be run at its maximum compression

Re: zstd compression for packages

2018-03-12 Thread Julian Andres Klode
On Mon, Mar 12, 2018 at 11:06:11AM +0100, Julian Andres Klode wrote: > Hey folks, > > We had a coding day in Foundations last week and Balint and Julian added > support for zstd compression to dpkg [1] and apt [2]. > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 > [2]

zstd compression for packages

2018-03-12 Thread Julian Andres Klode
Hey folks, We had a coding day in Foundations last week and Balint and Julian added support for zstd compression to dpkg [1] and apt [2]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 [2] https://salsa.debian.org/apt-team/apt/merge_requests/8 Zstd is a compression algorithm

ntfs-3g issue caused by Windows 10 creators update

2018-03-12 Thread Сергей Долгих
Hello. I faced a problem with the latest available (in Ubuntu Xenial) ntfs-3g package. It was unable to mount large (3 TB) NTFS volume after one has been used in windows 10 creators update. The error message is "$MFTMirr does not match $MFT (record 28)" and it states that it is necessary to