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
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,
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
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
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
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
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
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:
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
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 09 May 2019 05:14:54 +0900
Source: firefox-esr
Architecture: source
Version: 60.6.3esr-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages
Changed-By: Mike Hommey
Changes:
(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
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
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
> *
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 20:25:23 +0200
Source: gcc-snapshot
Architecture: source
Version: 1:20190508-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Changes:
gcc-snapshot (1
> "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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 19:27:08 +0200
Source: node-mqtt-packet
Architecture: source
Version: 6.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 928673
Changes:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 19:03:39 +0200
Source: python-reportlab
Architecture: source
Version: 3.5.21-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose
Changed-By: Matthias Klose
Changes:
python-reportlab (3.5.21-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 17:46:16 +0100
Source: gjs
Architecture: source
Version: 1.56.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Iain Lane
Changes:
gjs (1.56.2-1) experimental;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 18:11:11 +0200
Source: creduce
Architecture: source
Version: 2.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Changes:
creduce (2.9.0-1) unstable;
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
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
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
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
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 09:25:26 +0200
Source: dpdk
Binary: dpdk dpdk-dev dpdk-doc dpdk-igb-uio-dkms dpdk-rte-kni-dkms libdpdk-dev
librte-bbdev18.11 librte-ethdev18.11 librte-acl18.11 librte-bus-dpaa18.11
librte-bus-fslmc18.11
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 16:16:12 +0200
Source: gambas3
Binary: gambas3 gambas3-dev gambas3-templates gambas3-examples gambas3-gb-cairo
gambas3-gb-clipper gambas3-gb-dbus gambas3-gb-form-stock gambas3-gb-gmp
gambas3-gb-chart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 06 May 2019 10:18:38 -0300
Source: octave-doctest
Binary: octave-doctest
Architecture: source
Version: 0.7.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Octave Group
Changed-By: Rafael Laboissiere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 15:57:07 +0200
Source: gambas3
Binary: gambas3 gambas3-dev gambas3-templates gambas3-examples gambas3-gb-cairo
gambas3-gb-clipper gambas3-gb-dbus gambas3-gb-form-stock gambas3-gb-gmp
gambas3-gb-chart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 15:26:40 +0200
Source: cups
Architecture: source
Version: 2.3~b8-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team
Changed-By: Didier Raboud
Changes:
cups (2.3~b8-1) experimental;
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
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
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
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
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*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 15:09:14 +0200
Source: virtualbox
Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source
virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11
virtualbox-guest-utils
Architecture: source
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 12:37:57 +0100
Source: clsync
Binary: clsync clsync-dbgsym libclsync-dev libclsync0 libclsync0-dbgsym
Architecture: source amd64
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Artyom A Anikeev
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 13:46:47 +0300
Source: mesa
Architecture: source
Version: 19.0.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Timo Aaltonen
Changes:
mesa (19.0.3-1) experimental;
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 12:31:20 +0200
Source: libirman
Binary: libirman-dev libirman0 lirc-drv-irman
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team
Changed-By: Gianfranco
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 11:41:01 +0200
Source: node-lockfile
Architecture: source
Version: 1.0.4-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 928645
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 15:33:06 +0900
Source: texlive-lang
Binary: texlive-lang-all texlive-lang-arabic texlive-lang-chinese
texlive-lang-cjk texlive-lang-cyrillic texlive-lang-czechslovak
texlive-lang-english texlive-lang-european
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 15:32:48 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links
texlive-formats-extra texlive-games
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 19 Feb 2019 15:20:25 +
Source: doxygen
Binary: doxygen doxygen-latex doxygen-doc doxygen-gui
Architecture: source
Version: 1.8.15-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Paolo Greppi
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 May 2019 15:32:11 +0900
Source: texlive-base
Binary: texlive texlive-base texlive-fonts-recommended
texlive-fonts-recommended-doc texlive-full texlive-latex-base
texlive-latex-base-doc texlive-latex-recommended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 07 May 2019 17:19:08 +0200
Source: pacemaker
Architecture: source
Version: 2.0.1-3
Distribution: unstable
Urgency: high
Maintainer: Debian HA Maintainers
Changed-By: Ferenc Wágner
Closes: 927714
Changes:
pacemaker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 10:06:10 +0200
Source: pytsk
Binary: python-tsk python3-tsk
Architecture: source
Version: 20190507-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Hilko Bengen
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 05 May 2019 19:32:32 +0100
Source: linux-signed-i386
Binary: kernel-image-4.19.0-5-686-di nic-modules-4.19.0-5-686-di
nic-wireless-modules-4.19.0-5-686-di nic-shared-modules-4.19.0-5-686-di
serial-modules-4.19.0-5-686-di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 02:05:01 +0100
Source: shim-helpers-i386-signed
Binary: shim-helpers-i386-signed
Architecture: source
Version: 1+15+1533136590.3beb971+7
Distribution: sid
Urgency: medium
Maintainer: Debian EFI team
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 02:05:01 +0100
Source: shim-helpers-amd64-signed
Binary: shim-helpers-amd64-signed
Architecture: source
Version: 1+15+1533136590.3beb971+7
Distribution: sid
Urgency: medium
Maintainer: Debian EFI team
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 May 2019 02:05:01 +0100
Source: shim-helpers-arm64-signed
Binary: shim-helpers-arm64-signed
Architecture: source
Version: 1+15+1533136590.3beb971+7
Distribution: sid
Urgency: medium
Maintainer: Debian EFI team
Changed-By:
On Tue, 07 May 2019 03:45:33 +0900,
Hideki Yamane wrote:
> * IME (Input Method Editor)
>- anthy: not yet
done.
> * "Natural language processing" Japanese dictionaries
>- mecab-ipadic: not yet
done.
unidic is still active maintained dictionary by upstream, but there
are no new
71 matches
Mail list logo
