Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer

2019-01-02 Thread Nicholas D Steeves
On Sat, Dec 29, 2018 at 04:51:49PM +1100, Dimitri John Ledkov wrote: > On Sat, 29 Dec 2018 at 15:54, Nicholas D Steeves wrote: > > > > Hi Alex, Cyril, Dimitri, and anyone else reading this, > > > > On Wed, Nov 28, 2018 at 08:41:18PM +0100, Alex Mestiashvili wrote: > > > > > > Hi Nicholas, it is in

Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer

2019-01-02 Thread Nicholas D Steeves
On Sat, Dec 29, 2018 at 04:53:02PM +0100, Cyril Brulebois wrote: > Hi FTP team, > > I've just been reminded (see below) of the zstd udeb addition currently > sitting in NEW; the udeb addition was reviewed (even amended) and should > be ready for use in other d-i components. Could you please let th

Re: Bug#917909: [text-based installer] right-to-left writing direction broken

2019-01-02 Thread Samuel Thibault
Cyril Brulebois, le mer. 02 janv. 2019 06:53:44 +0100, a ecrit: > And thanks for debugging this so quickly! I was afraid it might have been due to bogl changes :) > Samuel Thibault (2018-12-31): > > Ah, it's 98fa157c758d ('bidi.patch: Look for libfribidi in multi-arch > > directory.'). In fribid

win32-loader_0.9.3_source.changes ACCEPTED into unstable

2019-01-02 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 Jan 2019 18:38:43 +0100 Source: win32-loader Binary: win32-loader Architecture: source Version: 0.9.3 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Didier Raboud De

Processing of win32-loader_0.9.3_source.changes

2019-01-02 Thread Debian FTP Masters
win32-loader_0.9.3_source.changes uploaded successfully to localhost along with the files: win32-loader_0.9.3.dsc win32-loader_0.9.3.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#917940: Reporting abuse

2019-01-02 Thread jose . r . r
Don't have a cow, RELAX, 'kibi'- The message was not intended for you/Debian. It was created *before* the instance had set up any mail service. I usually just grab the installation reports file once it has been created at /tmp and publish its format in my blog. Yet somehow I forgot about remov