Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: vagr...@debian.org, debian-boot@lists.debian.org
Please unblock package simple-cdd
This update fixes several release-critical and important bugs, as well
as documentation
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: vagr...@debian.org, debian-boot@lists.debian.org
Please unblock package ltsp
This fixes two release-critical bugs, an important bug, and updates
the debconf translation for
Hi Philipp,
Philipp Huebner (2019-05-20):
> I just ran into this very same issue.
>
> > I seem to remember having seen some discussion regarding how to detect
> > binary or armoured keys; maybe a cheap(er) fix would be to make sure we
> > install the needed gnupg bits into /target when such a
Your message dated Mon, 3 Jun 2019 04:19:02 +0200
with message-id <20190603021902.daqayg655aray...@mraw.org>
and subject line Re: Bug#929911: installation-reports: d-i rc1 - apt-setup:
local repositories broken
has caused the Debian Bug report #929911,
regarding installation-reports: d-i rc1 -
Your message dated Mon, 3 Jun 2019 04:16:45 +0200
with message-id <20190603021645.pjzlnzz3lvxqr...@mraw.org>
and subject line Re: Bug#929910: installation-reports: d-i rc1 - wrong
defaultroot
has caused the Debian Bug report #929910,
regarding installation-reports: d-i rc1 - wrong defaultroot
to
Package: installation-reports
Severity: normal
Dear Maintainer,
* What led up to the situation?
I have a TFTP server that holds several releases of Debian, and preseed
files. It works well for current and past releases, but I noticed two
problems with the current Buster installer (RC1).
Package: installation-reports
Severity: normal
Dear Maintainer,
* What led up to the situation?
I have a TFTP server that holds several releases of Debian, and preseed
files. It works well for current and past releases, but I noticed two
problems with the current Buster installer (RC1).
Karsten Merker (2019-06-02):
> Kibi, a question regarding the handling of the the
> u-boot-menu-installer package: As it only contains shell scripts,
> in conformance with normal policy rules I have marked it as an
> arch-all package that limits its execution to riscv64 with an
> "isinstallable"
[crossposted to debian-boot and debian-riscv]
Hello everybody,
I'm working on getting d-i support for riscv64 into a useable
state. With the recent upload of elfutils 0.176-1.1 into the
archive it is now possible to complete the "install the base
system" step on riscv64. What is still missing
Hi Casey,
Casey Stone (2019-05-29):
> I installed Debian 10 RC1 in a QEMU/KVM virtual machine on my Fedora 29
> laptop using 'Virtual Machine Manager' -- I overwrote a previously-working
> Debian 9 test VM.
>
> I installed from debian-buster-DI-rc1-amd64-netinst.iso. I chose the first
> listed
Package: debootstrap
Version: 1.0.114
Severity: normal
The following patch fixes issues when the hard-coded
PATH=/sbin:/usr/sbin:/bin:/usr/bin does not contain chroot or other
commonly used utilities, by changing to PATH=$PATH:/sbin:...
live well,
vagrant
From
ButterflyOfFire, le dim. 02 juin 2019 15:43:41 +, a ecrit:
> >> "لاحقاً"
>
> This word means "later" and can be replaced by "لاحقا".
That avoids the issue here indeed. I however see it used in various
places, notably in the grub installer:
msgid ""
"Warning: If the installer failed to
Hi,
>> "لاحقاً"
This word means "later" and can be replaced by "لاحقا".
Samuel Thibault, le dim. 02 juin 2019 17:07:04 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:47:49 +0200, a ecrit:
> > But it's translated along the two other pieces "The installer can guide
> > you..." and "If you choose guided..." so the issue might be in those.
>
> It's when I add
Samuel Thibault, le dim. 02 juin 2019 16:47:49 +0200, a ecrit:
> But it's translated along the two other pieces "The installer can guide
> you..." and "If you choose guided..." so the issue might be in those.
It's when I add this piece that gtk starts choking. Any idea?
"الفرصة لاحقاً لرؤية
Samuel Thibault, le dim. 02 juin 2019 16:44:45 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:33:03 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> > > Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > > > Samuel Thibault, le dim.
Samuel Thibault, le dim. 02 juin 2019 16:33:03 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > > Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > > > Holger Wansing, le dim. 02
Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > > Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > > > So, that would come down to
Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > > So, that would come down to this two commits
> > > (if it's a matter of arabic translations):
> >
Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > So, that would come down to this two commits
> > (if it's a matter of arabic translations):
> >
Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> So, that would come down to this two commits
> (if it's a matter of arabic translations):
> https://salsa.debian.org/installer-team/d-i/commit/1e16f41d79578a47a370c7a47ec49abdcfc7fb52
>
ButterflyOfFire, le dim. 02 juin 2019 12:12:04 +, a ecrit:
> Tested right now on my laptop, I cannot reproduce the bug. It seems working.
>
> Tested with :
> kvm -cdrom /var/tmp/d-i/debian-buster-DI-rc1-amd64-netinst.iso -drive
> file=blip -m 1G
Hum :/
I tried to rebuild partman-base
While ButterflyOfFire reported to be unable to reproduce this, I can indeed
reproduce this with qemu here.
Looking more closely, that bug is there for me with the rc1 installer, however
not with the alpha5 one.
So, that would come down to this two commits
(if it's a matter of arabic
Hi,
Tested right now on my laptop, I cannot reproduce the bug. It seems working.
Tested with :
kvm -cdrom /var/tmp/d-i/debian-buster-DI-rc1-amd64-netinst.iso -drive file=blip
-m 1G
Salutations,
Samuel Thibault, le dim. 02 juin 2019 13:00:51 +0200, a ecrit:
> Cc-ing debian-l10n-arabic because they can perhaps look at the partman
> translation files and check that there is nothing odd in the file (e.g.
> odd ligatures or such odd thing that might disturb gtk).
I forgot to mention that I
Package: installation-reports
Severity: serious
Justification: prevents from installing at all in arabic language
Hello,
Cc-ing debian-l10n-arabic because they can perhaps look at the partman
translation files and check that there is nothing odd in the file (e.g.
odd ligatures or such odd thing
26 matches
Mail list logo
