On Thu, May 09, 2019 at 12:02:26AM +0200, Adam Borowski wrote:
> > We have various applications that only want to extract single members of
> > the package (changelog, NEWS, copyright, ...); tar is a really bad
> > format for such an operation. Other formats (zip, 7z, ...) are more
> > suited for
On Wed, May 08, 2019 at 10:22:18PM -0300, Emmanuel Arias wrote:
> I was writing a serie of blog's entry [1] (on spanish)
> trying to let for me on the future some data. Maybe
> it could be helpful for you.
>
> I have to write it on english version too and updated,
> because I was using a virtual
Hello VIpul,
I was writing a serie of blog's entry [1] (on spanish)
trying to let for me on the future some data. Maybe
it could be helpful for you.
I have to write it on english version too and updated,
because I was using a virtual machine, but now I was using
chroot (that I think is better)
Ian Jackson writes:
> So far I have gained the impression that the kind of people who are
> using packaging-only git trees tend to be very conservative, and very
> comfortable with .dsc/tarball/patch/quilt based tools, and not really
> convinced of the usefulness of git.
Let me counter that impr
On Thu, May 09, 2019 at 07:37:55AM +0800, Paul Wise wrote:
On Thu, May 9, 2019 at 1:38 AM Adam Borowski wrote:
Thus, even though we'd want to stick with xz for the official archive, speed
gains from zstd are so massive that it's tempting to add support for it,
at least for non-official uses, po
On Wed, May 8, 2019 at 9:27 PM Vipul wrote:
> I've been using Debian from couples of years but haven't contributed yet back
> to community.
There are a number of different ways to contribute to Debian:
https://www.debian.org/intro/help
> I want to contribute to Debian by maintaining packages a
On Thu, May 9, 2019 at 1:38 AM Adam Borowski wrote:
> Thus, even though we'd want to stick with xz for the official archive, speed
> gains from zstd are so massive that it's tempting to add support for it,
> at least for non-official uses, possibly also for common Build-Depends.
Could we use cust
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: libsmithlab
* URL : https://github.com/smithlabcode/smithlab_cpp
* License : GPL
Programming Lang: C++
Description : low-level code collection for computational biology
To be team-maintained o
On Wed, May 08, 2019 at 10:35:58PM +0200, Ansgar wrote:
> Adam Borowski writes:
> > I've recently did some research on how can we improve the speed of unpacking
> > packages. There's a lot of other stages that can be improved, but let's
> > talk about the .deb format.
> >
> > First, the 0.939 form
On Wed, May 08, 2019 at 09:04:49PM +, Jeremy Stanley wrote:
> On 2019-05-08 22:35:58 +0200 (+0200), Ansgar wrote:
> > Adam Borowski writes:
> > > I've recently did some research on how can we improve the speed of
> > > unpacking
> > > packages. There's a lot of other stages that can be improv
On Wed, May 08, 2019 at 10:45:21PM +0300, Adrian Bunk wrote:
> On Wed, May 08, 2019 at 07:38:26PM +0200, Adam Borowski wrote:
> > So let's pick compressors to enable. For compression ratio, xz still wins
> > (at least among popular compressors). But there's a thing to say about
> > zstd: firefox.
Jeremy Stanley writes:
> On 2019-05-08 22:35:58 +0200 (+0200), Ansgar wrote:
>> Switching to a different binary format will break various tools. If we
>> want to do this, I wonder if we shouldn't take the chance to move away
>> from tar?
>>
>> We have various applications that only want to extrac
On 2019-05-08 22:35:58 +0200 (+0200), Ansgar wrote:
> Adam Borowski writes:
> > I've recently did some research on how can we improve the speed of unpacking
> > packages. There's a lot of other stages that can be improved, but let's
> > talk about the .deb format.
> >
> > First, the 0.939 format,
(adding debian-dpkg)
Adam Borowski writes (".deb format: let's use 0.939, zstd, drop bzip2"):
> First, the 0.939 format, as described in "man deb-old". While still being
> accepted by dpkg, it had been superseded before even the very first stable
> release. Why? It has at least two upsides over
Adam Borowski writes:
> I've recently did some research on how can we improve the speed of unpacking
> packages. There's a lot of other stages that can be improved, but let's
> talk about the .deb format.
>
> First, the 0.939 format, as described in "man deb-old". While still being
> accepted by
Adrian Bunk - 08.05.19, 21:45:
> On Wed, May 08, 2019 at 07:38:26PM +0200, Adam Borowski wrote:
> >...
> >
> > So let's pick compressors to enable. For compression ratio, xz
> > still wins (at least among popular compressors). But there's a
> > thing to say about zstd: firefox.deb zstd -19 takes
Package: wnpp
Severity: wishlist
Owner: Robert Lemmen
* Package name: perl6-openssl
Version : 0.1.22
Upstream Author : Filip Sergot and others
* URL : https://github.com/sergot/openssl
* License : MIT
Programming Lang: Perl 6
Description : OpenSSL bind
Le 08/05/2019 à 19:38, Adam Borowski a écrit :
> Hi!
> I've recently did some research on how can we improve the speed of unpacking
> packages. There's a lot of other stages that can be improved, but let's
> talk about the .deb format.
>
> First, the 0.939 format, as described in "man deb-old".
On Wed, May 08, 2019 at 07:38:26PM +0200, Adam Borowski wrote:
>...
> So let's pick compressors to enable. For compression ratio, xz still wins
> (at least among popular compressors). But there's a thing to say about
> zstd: firefox.deb zstd -19 takes to unpack:
> * 2.644s .xz, stock dpkg
> * 2.5
> "Adam" == Adam Borowski writes:
Adam> Hi! I've recently did some research on how can we improve the
Adam> * there's no 10¹⁰ bytes (~9.31GB) limit While no package this
Adam> big is in the archive _yet_ (max being 1⎖652⎖244⎖360 bytes),
Adam> both storage sizes and software b
Hi!
I've recently did some research on how can we improve the speed of unpacking
packages. There's a lot of other stages that can be improved, but let's
talk about the .deb format.
First, the 0.939 format, as described in "man deb-old". While still being
accepted by dpkg, it had been superseded
Vipul writes ("Configure your PC to contribute to Debian community"):
> I've been using Debian from couples of years but haven't contributed
> yet back to community. I want to contribute to Debian by maintaining
> packages and fixing bugs. Since I'm using Debian for work purpose
> also so, I don't
Simon McVittie writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> On Sat, 04 May 2019 at 21:10:34 +0100, Ian Jackson wrote:
> > So far I have gained the impression that
> > the kind of people who are using packaging-only git trees tend to be
> > very conserva
Simon McVittie writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> On Tue, 07 May 2019 at 19:25:39 +0100, Ian Jackson wrote:
> > What I am primarily advocating for in this thread is that maintainers
> > should choose `dgit push-source' over `dput' (where this
Simon McVittie writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> On Wed, 08 May 2019 at 12:18:41 +0100, Ian Jackson wrote:
> > Indeed, you yourself say you avoid gbp but for many packages, the
> > Vcs-Git header gives you a patches-unapplied format which req
On Wed, May 08, 2019 at 04:14:00PM +0100, Ian Jackson wrote:
> > > [Ian Jackson:]
> > > > You should use dgit for the benefit of users. See my other mail which
> > > > answers why Vcs-Git and debcheckout is not enough.
> > >
> > > could you be so kind and provide a pointer, this thread is rather
Ckghfwssm Ckghfwssm,
I am Donna Baker. I am a recruiter. Our company is recruiting a outgoing,
responsible, punctual person to fill the position of the online manager.
After examining a lot of CVs, we would like to see you as our employee.
We offer this work as underemployment at the mom
Holger Levsen writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> could you be so kind and provide a pointer, this thread is rather long
> already? (Maybe this is also worth an FAQ entry somewhere..)
Jonathan Carter writes ("Re: Preferred git branch structure
On Wed, May 08, 2019 at 03:57:08PM +0100, Ian Jackson wrote:
> > both.
> For packaging-only, dgit does not properly support that. Do you have
> the upstream source in git form too, and if so how do you combine
> them ? Do you manipulate patches using quilt ? [1]
hm/i'm sorry, I cannot really thi
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: python-pybigwig
Version : 0.3.15
* URL : https://github.com/deeptools/pyBigWig
* License : MIT
Programming Lang: Python
Description : read/write chromosomal sequence data in bigWig fi
Holger Levsen writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> On Wed, May 08, 2019 at 12:18:41PM +0100, Ian Jackson wrote:
> > I'm not sure what git branch format you are using. (Maybe you said it
> > earlier in this thread.) Packaging-only ? git-merge
Matthew Vernon writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> Scott Kitterman writes:
> > For what it's worth, when you start calling me names (unethical)
> > because I'm not using your shiny new toy, my immediate reaction is to
> > decide to ignore furt
On Sat, 04 May 2019 at 21:10:34 +0100, Ian Jackson wrote:
> So far I have gained the impression that
> the kind of people who are using packaging-only git trees tend to be
> very conservative, and very comfortable with .dsc/tarball/patch/quilt
> based tools, and not really convinced of the usefulne
On Tue, 07 May 2019 at 19:25:39 +0100, Ian Jackson wrote:
> What I am primarily advocating for in this thread is that maintainers
> should choose `dgit push-source' over `dput' (where this is possible).
> This is the only way for a maintainer to provide users with the git
> history in a sensible fo
Dmitry Bogatov 于2019年4月22日周一 下午5:56写道：
>
>
> [ I know, it month and half late ]
> [ I did my best to recover thread. Sorry, If I failed. ]
>
> [ Please, CC me if you want me to reply. I'm not subscribed to debian-devel@ ]
>
> [ Alexander Wirt ]
> > Thats where you come in, please tell me how tools
Hey there,
I've been using Debian from couples of years but haven't contributed yet back
to community. I want to contribute to Debian by maintaining packages and fixing
bugs. Since I'm using Debian for work purpose also so, I don't want to mess-up
with my system by installing unstable packages
Scott Kitterman writes:
> On May 7, 2019 8:50:57 PM UTC, Sam Hartman wrote:
>>> "Ian" == Ian Jackson writes:
>>Ian> The latter point is because using dgit push is an ethical
>>Ian> imperative, not because the two somehow have some deep
>> Ian> technical linkage. IMO almost *any*
On Wed, 08 May 2019 at 12:18:41 +0100, Ian Jackson wrote:
> Indeed, you yourself say you avoid gbp but for many packages, the
> Vcs-Git header gives you a patches-unapplied format which requires[1]
> gbp pq to switch to a patches-applied view before you build it.
This step is not required: for 3.0
Package: wnpp
Severity: wishlist
Owner: Mikhail f. Shiryaev
* Package name: golang-github-naegelejd-go-acl
Version : 0.0~git20160113.f33f861-1
Upstream Author : Joseph Naegele
* URL : https://github.com/naegelejd/go-acl
* License : MIT
Programming Lang: Go
On 2019/05/08 13:23, Holger Levsen wrote:
>> You should use dgit for the benefit of users. See my other mail which
>> answers why Vcs-Git and debcheckout is not enough.
>
> could you be so kind and provide a pointer, this thread is rather long
> already? (Maybe this is also worth an FAQ entry som
Dzień dobry,
zajmujemy się tworzeniem nowoczesnych, responsywnych*_ Stron i Sklepów
internetowych. _*
Jeśli chcieliby Państwo otrzymać bezpłatną propozycję w tym zakresie dla
Państwa firmy prosimy o odpowiedź *TAK.*
- - - -
Pozdrawiamy Serdecznie,
Twórcy Stron i Sklepów WWW
On Wed, May 08, 2019 at 12:18:41PM +0100, Ian Jackson wrote:
> I'm not sure what git branch format you are using. (Maybe you said it
> earlier in this thread.) Packaging-only ? git-merge ?
both.
> You should use dgit for the benefit of users. See my other mail which
> answers why Vcs-Git and
Holger Levsen writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> as a data point: I never really got my head around gbp, too many times
> it came in the way, did things I didnt expect to do (or couldnt easily
> figure out what it did), so I basically (try to)
On Tue, May 07, 2019 at 07:25:39PM +0100, Ian Jackson wrote:
> A maintainer who is currently using gbp pq can (and IMO generally
> should) use `dgit push' to do their uploads, rather than dput/dupload.
as a data point: I never really got my head around gbp, too many times
it came in the way, did
Sam Hartman writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> Ian Jackson writes:
> > The latter point is because using dgit push is an ethical
> > imperative, not because the two somehow have some deep
> > technical linkage. IMO almost *any* tutorial bein
45 matches
Mail list logo
