I am now using the BluRay image which contains Spyder and its dependencies, so
I am fine.
But obviously there is a problem with the current algo being used if the
dependencies of a software end up in an ISO but not the software actually
depending on them.
I remember being surprised by the size
On Thu, Jul 29, 2021 at 03:40:54AM +0200, epsommum...@virgilio.it wrote:
>Hi Steve!
>
>The 16GB image is actually less than 15GB.
Incorrect. Checking the size in the jigdo file:
Image size 15909054464 bytes
>The Spyder package is 200kb.
>There is ample room.
>Someone who does not use Spyder put
Hi Steve!
The 16GB image is actually less than 15GB.
The Spyder package is 200kb.
There is ample room.
Someone who does not use Spyder put python3-spyder in this ISO thinking it was
the real Spyder software, except that it was just one if its dependencies.
You could either remove the
Hi!
On Wed, Jul 28, 2021 at 08:26:53PM +0200, epsommum...@virgilio.it wrote:
>
>The Spyder package is missing from jigdo amd64 weekly 16 GB stick ISO.
>
>All its dependencies are there like python3-spyder, but since spyder
>itself is missing, spyder can not be used.
>
Hi !
The Spyder package is missing from jigdo amd64 weekly 16 GB stick ISO.
All its dependencies are there like python3-spyder, but since spyder itself is
missing, spyder can not be used.
https://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-16G/
Control: clone -1 -2
Control: reassign -1 cdrom-detect
Control: retitle -1 cdrom-detect: ask hw-detect to skip missing firmware
detection
Control: reassign -2 iso-scan
Control: retitle -2 iso-scan: maybe ask hw-detect to skip missing firmware
detection
Cyril Brulebois (2021-07-28):
> While I'm
Package: hw-detect
Version: 1.146
Severity: important
X-Debbugs-Cc: debian-cd@lists.debian.org
I hadn't seen the following when test-installing in loops, since I was
using a netboot-gtk image, but this can be seen with a regular netinst
image produced by debian-cd, since the d-i image used there
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jul 2021 01:02:03 +0100
Source: debian-cd
Architecture: source
Version: 3.1.35
Distribution: unstable
Urgency: medium
Maintainer: Debian CD Group
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 678065
debian-cd_3.1.35_source.changes uploaded successfully to localhost
along with the files:
debian-cd_3.1.35.dsc
debian-cd_3.1.35.tar.xz
debian-cd_3.1.35_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Hi CD team,
I have a merge request pending for webwml and I was suggested by Paul
Wise to see if you had any feedback.
Currently, the "Download" button on debian.org points directly to the
netinst iso. This MR would replace it with a page that still initiates
an automatic download of netinst,
Hi all
I'm also available, adding myself below:
El 22 de julio de 2021 21:18:43 CEST, Paul Gevers escribió:
>Hi all,
>
>Thanks to the reply from Ansgar, we now have a release date for
>bullseye: 14 August. For the avoidance of doubt, this is *not* a
>tentative date anymore. I'll do a proper
Hi all,
Thanks to the reply from Ansgar, we now have a release date for
bullseye: 14 August. For the avoidance of doubt, this is *not* a
tentative date anymore. I'll do a proper announcement later today or
tomorrow evening.
14 August (day before DebCamp)
RT: Adam
Image: Steve,
It seems that debian-cd (re)builds its own efi.img and doesn't
add the dtbs but only the EFI/ subdirectory from the d-i
efi.img.
This might fix the problem, please take it with a grain of salt
because I was unable to actually test it. I've tried the
commands by hand though.
diff --git
Iiii88 dc h by bfc x,, c, xf VG xc *7000*77, CWC f WC x ccg*gg
Hi,
On Tue, 2021-07-20 at 22:35 +0200, Paul Gevers wrote:
> We currently don't have any day yet with all involved
> teams comfortably present, the one coming closest is 4 September.
> Somebody from ftp available on 14 august?
That should be doable.
Ansgar
Hi all,
Current overview to check if I got things right and to hopefully trigger
more replies. We currently don't have any day yet with all involved
teams comfortably present, the one coming closest is 4 September.
Somebody from ftp available on 14 august?
14 August (day before DebCamp)
On 2021-07-17 22:25:17, Paul Gevers wrote:
> Hi all,
>
> On 11-07-2021 21:11, Paul Gevers wrote:
> > With less than three weeks to go until the tentative release date, I
> > would love to confirm the date by now, but there is a serious issue with
> > crucial infrastructure (cdbuilder.d.o). Apart
Hello,
On June 12th 2021, I submitted a Canadian website to be added to the
"Vendors of Debian installation media" page:
https://www.debian.org/CD/vendors/
I used this form: https://www.debian.org/CD/vendors/adding-form
I got a confirmation after submitting the form, but I did not get any email
We would like to register our Debian CD Image mirror
Submission-Type: new
Site: mirror.unair.ac.id
Type: leaf
Archive-architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel
powerpc ppc64el s390x
Archive -http: /debian-cd/
Archive-rsync: debian-cd/
Maintainer: Networking DSID Universitas
On Sun, Jul 18, 2021 at 10:27:41AM -0500, Scott Morton wrote:
> I have some old infomagic CD sets with Debian 1.1 and 2.0, would you be
> interested in copies?
>
> Regards,
> Scott
It's possible that Sledge has them but if not, depending on where you are,
you could offer to mail them :)
I only
On 16197 March 1977, Paul Gevers wrote:
Albeit there is some progress, we think it better for the people
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or
On Sat, 2021-07-17 at 22:25 +0200, Paul Gevers wrote:
> 14 August (day before DebCamp)
> 21 August (last day of DebCamp)
> RT: elbrus
These both look OK.
> 28 August (DebConf)
> RT: elbrus
That's a holiday weekend in the UK; I'll be visiting family and then
the Debian UK BBQ.
> 4
I have some old infomagic CD sets with Debian 1.1 and 2.0, would you be
interested in copies?
Regards,
Scott
- Forwarded message from "Andrew M.A. Cater" -
Date: Sun, 18 Jul 2021 11:08:43 +
From: "Andrew M.A. Cater"
To: debian-b...@lists.debian.org
Subject: Re: Finding a tentative bullseye release date
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:
> Hi all,
>
> On
On 18/07/2021 00:24, Donald Norwood wrote:
Hi!
On 7/17/21 4:58 PM, Steve McIntyre wrote:
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
With less than three weeks to go until the tentative release date, I
would love to confirm
Hi!
On 7/17/21 4:58 PM, Steve McIntyre wrote:
> On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:
>> Hi all,
>>
>> On 11-07-2021 21:11, Paul Gevers wrote:
>>> With less than three weeks to go until the tentative release date, I
>>> would love to confirm the date by now, but there is a
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:
>Hi all,
>
>On 11-07-2021 21:11, Paul Gevers wrote:
>> With less than three weeks to go until the tentative release date, I
>> would love to confirm the date by now, but there is a serious issue with
>> crucial infrastructure
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
> With less than three weeks to go until the tentative release date, I
> would love to confirm the date by now, but there is a serious issue with
> crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what
> it means for solving the
Package: debian-cd
Severity: normal
It is useful to have the device trees available on the ESP. If we have these,
(vanilla) u-boot should be able to boot any board which has a dtb in the kernel
out-of-the box using EFI.
The (arm64) mini.iso already includes the DTBs in /dtb (which is the path
Hi all,
On 08-06-2021 21:30, Steve McIntyre wrote:
> On Tue, Jun 08, 2021 at 08:50:55PM +0200, Paul Gevers wrote:
>> 31 July: ** tentative ** release date
>
> Cool, works for me. Pencilled into my calendar now. :-)
With less than three weeks to go until the tentative release date, I
would love
Processing commands for cont...@bugs.debian.org:
> reassign 990016 debian-installer
Bug #990016 [debian-cd] Debian installer images missing ASpeed video driver
Bug reassigned from package 'debian-cd' to 'debian-installer'.
Ignoring request to alter found versions of bug #990016 to the same values
On Mon, 28 Jun 2021 22:47:24 +0100
Steve McIntyre wrote:
> >I downloaded the debian live 10.10.0-amd64-gnome image file. I needed to
> >make
> >user authorisation but I couldn't find the root password anywhere on the
> >website.
>
> the username/password is user/live
Can we show it at login?
+debian-live
Hello Nathanael,
On 29/06/2021 06:14, Nathanael Higley wrote:
> Hi my name is Nathanael and I was wondering how I could build an
> unofficial/ for personal use Debian Buster livecd with updates and
> security patches included on the disc?
> I've had previously built a custom live-cd
Hi my name is Nathanael and I was wondering how I could build an
unofficial/ for personal use Debian Buster livecd with updates and security
patches included on the disc?
I've had previously built a custom live-cd with live-build on Debian
stretch with live-images or more precisely the
On Mon, Jun 28, 2021 at 08:48:30PM +, Odunola Ibrahim wrote:
>Hello,
>
>I downloaded the debian live 10.10.0-amd64-gnome image file. I needed to make
>user authorisation but I couldn't find the root password anywhere on the
>website.
the username/password is user/live
--
Steve McIntyre,
Hello,
I downloaded the debian live 10.10.0-amd64-gnome image file. I needed to make
user authorisation but I couldn't find the root password anywhere on the
website.
Kindly help.
Kind regards,
Ibrahim Odunola
On Fri, Jun 18, 2021 at 07:44:21PM -0700, Gnu Turd wrote:
I'm refusing to engage with messages from somebody choosing such
juvenile words in their name/email address.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is
A few days ago I did a Debian install with the
firmware-testing-amd64-netinst.iso I believe I downloaded on June 5, 2021.
I figured it was close enough to bullseye becoming the stable release that
the testing image would be quite stable enough and not likely to change too
much, so I could just set
Control: reassign -1 grub-ieee1275
Hi Timothy,
Reassigning this to the correct package where it should get more
attention...
On Thu, Jun 17, 2021 at 04:20:47PM -0500, Timothy Pearson wrote:
>Package: debian-cd
>Severity: Grave
>
>Attempting to use the latest Bullseye RC2 CD installer on an
Processing control commands:
> reassign -1 grub-ieee1275
Bug #990017 [debian-cd] [REGRESSION] Bullseye CD installer images fail to
install GRUB on OpenPOWER machines
Bug reassigned from package 'debian-cd' to 'grub-ieee1275'.
Ignoring request to alter found versions of bug #990017 to the same
Package: debian-cd
Severity: Grave
Attempting to use the latest Bullseye RC2 CD installer on an OpenPOWER machine
results in a fatal error during bootloader installation:
Jun 17 21:14:45 grub-installer: info: Installing grub on '/dev/sda1'
Jun 17 21:14:45 grub-installer: info: grub-install does
Package: debian-cd
Severity: Important
The current Bullseye installer images don't include the "ast" video driver,
making it impossible to install Debian on systems that don't have a fallback
VGA BIOS (anything non-x86, e.g. ARM/OpenPOWER).
Ubuntu fixed this issue almost 5 years ago:
Package: cdimage.debian.org
Severity: normal
Debian Images Team,
The recent use of eatmydata to create live images generates many errors,
and may not be effective.
Weekly Live Builds (Jun 14, 2021):
debian-live-testing-amd64-standard.iso
$ grep ERROR /var/log/bootstrap.log | uniq -c
6926
On 08/06/2021 19:50, Paul Gevers wrote:
Hi all again,
On 07-06-2021 23:08, Adam D. Barratt wrote:
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
Nevermind 10 July. Steve, you can stop contemplating about it. We'll
go for 24 July as the *tentative* release date.
Unfortunately I've
On Tue, Jun 08, 2021 at 08:50:55PM +0200, Paul Gevers wrote:
>
>So, if I did all the booking right (including updates from IRC) we now have:
>
>26 June
> [Ansgar (ftp), Sebastian (release), Adam (release)]
>3 July
> [Ansgar (ftp), Paul (release), Adam (release)]
>10 July
> [Steve + Andy (CD),
Hi all again,
On 07-06-2021 23:08, Adam D. Barratt wrote:
> On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
>> Nevermind 10 July. Steve, you can stop contemplating about it. We'll
>> go for 24 July as the *tentative* release date.
>
> Unfortunately I've just discovered that I was given the
On 07/06/2021 22:08, Adam D. Barratt wrote:
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
Hi all,
On 06-06-2021 20:03, Paul Gevers wrote:
With the availability of Adam now known (and some off-list info),
we have:
[...]
So, what to pick? We still believe that shorter freezes are
[ Re-adding the CC to the mailing list; please respond there too ]
On Tue, Jun 08, 2021 at 01:17:16PM +0200, valentí juanola wrote:
>It works. I apologize for my ignorance. Thank you very much, Steve. Have a nice
>life.
OK, so it seems you need to repair your system's locale
information. I'd
It works. I apologize for my ignorance. Thank you very much, Steve. Have a
nice life.
El dt., 8 de juny 2021, 13:03, Steve McIntyre va
escriure:
> [ Re-adding the CC to the mailing list; please respond there too ]
>
> On Tue, Jun 08, 2021 at 12:32:18PM +, valentí juanola wrote:
>
[ Re-adding the CC to the mailing list; please respond there too ]
On Tue, Jun 08, 2021 at 12:32:18PM +, valentí juanola wrote:
>AShFrtRm324fZ4pTjQvZRA debian-10.9.0-amd64-DVD-1.template
>
On Tue, Jun 08, 2021 at 11:57:48AM +0200, valentí juanola wrote:
>Dear Steve
>Thanks for your help. All Dvds give the same error message...
So what checksum do you get for the template file please?
Also, checking your error message again, what does the command
"locale" say on your system?
--
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
> Hi all,
>
> On 06-06-2021 20:03, Paul Gevers wrote:
> > With the availability of Adam now known (and some off-list info),
> > we have:
> >
[...]
> > So, what to pick? We still believe that shorter freezes are better
> > for
> > the Debian
On 07/06/21 19:38, Paul Gevers wrote:
> Hi all,
>
> On 06-06-2021 20:03, Paul Gevers wrote:
>> With the availability of Adam now known (and some off-list info), we have:
>>
>> 26 June
>> [Ansgar (ftp), Sebastian (release), Adam (release)]
>> 3 July
>> [Ansgar (ftp), Paul (release), Adam
Hi all,
On 06-06-2021 20:03, Paul Gevers wrote:
> With the availability of Adam now known (and some off-list info), we have:
>
> 26 June
> [Ansgar (ftp), Sebastian (release), Adam (release)]
> 3 July
> [Ansgar (ftp), Paul (release), Adam (release)]
> 10 July
> [Steve (CD) MAYBE , Ansgar
Thanks, I'll check them out.
El dl., 7 de juny 2021, 13:46, Steve McIntyre va
escriure:
> Hi Valentí,
>
> On Mon, Jun 07, 2021 at 01:30:32PM +, valentí juanola wrote:
> >[profile_ma]
> >
> > [profile_ma]
> > Cannot download via jigdo because
> >
> > Jigdo downloads fail at address
> >
Hi Valentí,
On Mon, Jun 07, 2021 at 01:30:32PM +, valentí juanola wrote:
>[profile_ma]
>
> [profile_ma]
> Cannot download via jigdo because
>
> Jigdo downloads fail at address
> https://cdimage.debian.org/debian-cd/current/amd64/jigdo-dvd/
>
> file: debian-10.9.0-amd64-DVD-1.template
>
Cannot download via jigdo because
Jigdo downloads fail at address
https://cdimage.debian.org/debian-cd/current/amd64/jigdo-dvd/
file: debian-10.9.0-amd64-DVD-1.template
from: https://laotzu.ftp.acc.umu.se(???)
Debian mirror [ftp://ftp.de.debian.org/debian/]:
jigdo-file:
Hi all,
On 04-06-2021 06:49, Paul Gevers wrote:
> 26 June [Ansgar (ftp)]
> 3 July[Ansgar (ftp), Sebastian (release), Paul (release)]
> 10 July [Steve (CD) MAYBE , Ansgar (ftp), Paul (release)]
> 17 July [Steve (CD), press, Ansgar (ftp), Paul (release)]
> 24 July [Steve (CD), press,
On Sun, 2021-05-30 at 09:09 +0200, Paul Gevers wrote:
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7 August
> 14 August
July 17th doesn't work well for me unfortunately*.
The others currently all look OK, although I'd prefer not to do two
Hi all,
On 30-05-2021 09:09, Paul Gevers wrote:
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7 August
> 14 August
This can now be updated to:
26 June [Ansgar (ftp)]
3 July[Ansgar (ftp), Sebastian (release), Paul (release)]
10 July
Package: extlinux
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org
On a freshly created and nearly empty filesystem, after extlinux
--install creates ldlinux.c32 and ldlinux.sys, they're both fragmented:
$ filefrag ldlinux.*
ldlinux.c32: 3 extents
On 2021-05-30 09:09:28 +0200, Paul Gevers wrote:
> [Press]
> > Press can do both the 17th and the 24th. Perhaps we add an additional 3
> > dates?
>
> Yes, let's do that, so the list becomes:
>
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7
Hi,
The next point release for "buster" (10.10) is scheduled for Saturday
June 19th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Isy and I can do 12th or 19th.
We have a prior commitment on the 26th... Sorry
/Andy (rattusrattus)
On 30 May 2021 17:41:54 BST, "Adam D. Barratt" wrote:
>Hi,
>
>We're now a little overdue for 10.10, but it looks like we're ready in
>terms of shim etc. changes, so we should look at dates.
On Sun, 2021-05-30 at 09:09 +0200, Paul Gevers wrote:
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7 August
> 14 August
Currently all of these are fine for me.
Ansgar
On Sun, 30, May, 2021 at 05:50:09PM +0100, Steve McIntyre spoke thus..
> >Saturday June 12th
> >Saturday June 19th
> >Saturday June 26th
19th is best for me.
Thanks,
Mark
--
Mark Hymers
Hi there,
We’re currently working on behalf of a major industry-leading client trying
to enhance their brand via editorial content.
Whilst looking for opportunities, we came across your website meebey.net
Please let us know the pricing and options to place sponsored content on
your
Adam D. Barratt (2021-05-30):
> We're now a little overdue for 10.10, but it looks like we're ready in
> terms of shim etc. changes, so we should look at dates.
>
> Please could you indicate your availability for (and any preferences
> amongst) the following:
>
> Saturday June 12th
> Saturday
On Sun, May 30, 2021 at 05:41:54PM +0100, Adam Barratt wrote:
>Hi,
>
>We're now a little overdue for 10.10, but it looks like we're ready in
>terms of shim etc. changes, so we should look at dates.
>
>Please could you indicate your availability for (and any preferences
>amongst) the following:
>
On Sun, May 30, 2021 at 09:09:28AM +0200, Paul Gevers wrote:
>On 30-05-2021 06:35, Donald Norwood wrote:
>> On 5/29/21 9:12 AM, Steve McIntyre wrote:
>>> On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
Assuming all goes well
with RC2 and RC3, we'd be looking at the following
Hi,
We're now a little overdue for 10.10, but it looks like we're ready in
terms of shim etc. changes, so we should look at dates.
Please could you indicate your availability for (and any preferences
amongst) the following:
Saturday June 12th
Saturday June 19th
Saturday June 26th
The 12th is
On Sun, May 30, 2021 at 09:09:28AM +0200, Paul Gevers wrote:
> Hi,
>
> On 30-05-2021 06:35, Donald Norwood wrote:
> > On 5/29/21 9:12 AM, Steve McIntyre wrote:
> >> On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
> >>> Assuming all goes well
> >>> with RC2 and RC3, we'd be looking at
Hi,
On 30-05-2021 06:35, Donald Norwood wrote:
> On 5/29/21 9:12 AM, Steve McIntyre wrote:
>> On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
>>> Assuming all goes well
>>> with RC2 and RC3, we'd be looking at the following candidate release dates:
>>>
>>> 26 June
>>> 3 July
>>> 10
Hey Paul!
On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
>
>On 24-04-2021 00:41, Donald Norwood wrote:
>> Indeed, from this and the last few posts in the discussion it reads that
>> perhaps June is the better option for the 'timed' ready when ready
>> release date.
>
>The progress
On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
> Hi all,
>
> On 24-04-2021 00:41, Donald Norwood wrote:
> > Indeed, from this and the last few posts in the discussion it reads that
> > perhaps June is the better option for the 'timed' ready when ready
> > release date.
>
> The
Hi all,
On 24-04-2021 00:41, Donald Norwood wrote:
> Indeed, from this and the last few posts in the discussion it reads that
> perhaps June is the better option for the 'timed' ready when ready
> release date.
The progress of fixing the blocking issues in the debian-installer is
good enough to
Package: debian-cd
Despite having a wide deployment of desktop-class systems, the ppc64le port
does not have a live CD/DVD available. This makes installation needlessly
difficult on desktop machines that may or may not have external BMC or serial
access, given that the installer images also
Hello,
Steve McIntyre, le dim. 16 mai 2021 15:55:20 +0100, a ecrit:
> This morning's bullseye build for amd64:
>
> -rw-r--r-- 1 debian-cd debian-cd 377487360 May 16 08:56
> debian-testing-amd64-netinst.iso
>
> and the build I've just triggered by hand:
>
> -rw-r--r-- 1 debian-cd debian-cd
Your message dated Sun, 16 May 2021 15:55:20 +0100
with message-id <20210516145520.ge31...@tack.einval.com>
and subject line Re: Bug#678065: debian-cd: Include brltty and espeakup in
netinst
has caused the Debian Bug report #678065,
regarding debian-cd: Include brltty and espeakup in netinst
to
Hey Samuel!
Sorry for not responding earlier, I've been swamped with other
things. :-/
On Thu, Apr 29, 2021 at 11:43:39PM +0200, Samuel Thibault wrote:
>Samuel Thibault, le sam. 27 mars 2021 17:24:25 +0100, a ecrit:
>> Samuel wrote:
>> > Currently, the netinst images do not contain brltty and
Sorry, but I didn't know where to properly send a bug report for a
non-official + non-free iso image.
Reporting about: d-live nf 10.9.0 gn amd64 iso image.
I downloaded this image from Debian's link and confirmed with SHA512SUM.
Problem: When running live, Movie application will not play any
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package debian-cd 3.1.34 as that's the version currently in use
on cdimage.debian.org to build bullseye images. The changes are straightforward,
trivial, tested and been in
Processing control commands:
> reassign -1 debian-installer
Bug #988013 [debian-cd] mini.iso fails to load grub.cfg (UEFI)
Bug reassigned from package 'debian-cd' to 'debian-installer'.
Ignoring request to alter found versions of bug #988013 to the same values
previously set
Ignoring request to
Control: reassign -1 debian-installer
Hi Andrei,
On Mon, May 03, 2021 at 09:02:08PM +0300, Andrei POPESCU wrote:
>Package: debian-cd
>Severity: important
>Tags: d-i
>
>Hello,
>
>The mini.iso (graphical version) boots to a grub prompt.
>
>Loading grub.cfg with 'configfile
Package: debian-cd
Severity: important
Tags: d-i
Hello,
The mini.iso (graphical version) boots to a grub prompt.
Loading grub.cfg with 'configfile (hd0)/boot/grub/grub.cfg' works and
afterwards the image works correctly.
I tried buster, bullseye rc1 and the daily image from 1.May.
The
Hello,
ping?
Samuel
Samuel Thibault, le sam. 27 mars 2021 17:24:25 +0100, a ecrit:
> Samuel wrote:
> > Currently, the netinst images do not contain brltty and espeakup.. This
> > means that blind users who install Debian without a network mirror end
> > up with an unusable installed system,
On Wed, Apr 28, 2021 at 01:56:13PM +0200, Samuel Thibault wrote:
> Philip Hands, le mer. 28 avril 2021 11:04:42 +0200, a ecrit:
> > Could we start out with a baby step having a new experimental-netinst
> > flavour of ISO, which includes a list of experimental udebs in addition
> > to the normal
Philip Hands, le mer. 28 avril 2021 11:04:42 +0200, a ecrit:
> Could we start out with a baby step having a new experimental-netinst
> flavour of ISO, which includes a list of experimental udebs in addition
> to the normal ones?
As a reminder, one can already use preseeding
d-i
Hello All,
On 2021.04.28 04:14, Cyril Brulebois wrote:
Hello Dave,
Yahoo pugh_ca (2021-04-27):
I am one of those Raspberry Pi 4 users who is vanilla-installing your
weekly Bullseye testing netinst.iso's.The one problem we always have
is that we must jump thru hoops to get the applicable .ko
Cyril Brulebois writes:
> Hi,
>
> ValdikSS (2021-04-28):
>> eatmydata-udeb package is designed to speed up the installation process.
>> However, it's not used by default and could be activated only with preseed
>> file or kernel cmdline argument.
>>
>> Please consider increasing eatmydata-udeb
Hi,
ValdikSS (2021-04-28):
> eatmydata-udeb package is designed to speed up the installation process.
> However, it's not used by default and could be activated only with preseed
> file or kernel cmdline argument.
>
> Please consider increasing eatmydata-udeb priority to standard in
>
Hello,
eatmydata-udeb package is designed to speed up the installation process.
However, it's not used by default and could be activated only with
preseed file or kernel cmdline argument.
Please consider increasing eatmydata-udeb priority to standard in
debian-installer overrides, for it to
Hello Dave,
Yahoo pugh_ca (2021-04-27):
> I am one of those Raspberry Pi 4 users who is vanilla-installing your
> weekly Bullseye testing netinst.iso's.The one problem we always have
> is that we must jump thru hoops to get the applicable .ko to use for
> bcmgenet (Broadcom gigabit ethernet).I
Hi:
I am one of those Raspberry Pi 4 users who is vanilla-installing your weekly
Bullseye testing netinst.iso's.The one problem we always have is that we must
jump thru hoops to get the applicable .ko to use for bcmgenet (Broadcom gigabit
ethernet).I was not successful finding a
On 25/04/21 at 11:04 +0200, Cyril Brulebois wrote:
> > B) In the installer, detect that firmware-amd-graphics or
> > firmware-misc-nonfree should be installed, and either install it (?),
> > or redirect the user to the unofficial installer that includes them.
>
> That could be achieved for an
[ cc+=-x@ ]
Hi Lucas,
Thanks for your summary, I'm not sure about every single detail, but it
seems to be a good basis for discussion. I might point to it from our
errata page (I didn't have a specific bug report when I wrote the most
recent entries):
Hi,
Lucas Nussbaum wrote (Sat, 24 Apr 2021 11:30:03 +0200):
> With Debian 10, the behaviour was that the installation succeeded
> without installing firmware-* packages, and then, and the first boot, X
> would start in a "degraded" mode (using, for example, the vesa driver).
> The user would
Lucas Nussbaum writes:
> It looks like the three open paths for resolution are:
>
> A) understand and restore the behaviour from Debian 10, that is, get X
> to work in a degraded mode after installation. How it worked with Debian
> 10 (and why it doesn't with Debian 11) is unknown.
>
> B) In the
On 24/04/21 at 09:25 +0200, Holger Wansing wrote:
> Hi,
>
> Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200):
> > D-I Bullseye RC 1 was published a few hours ago. And at the risk of
> > sounding like a broken record: I have *absolutely no guarantee* to
> > have a fix or workaround for the
Hi,
Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200):
> D-I Bullseye RC 1 was published a few hours ago. And at the risk of
> sounding like a broken record: I have *absolutely no guarantee* to
> have a fix or workaround for the amdgpu issue in less than a month,
> that would be tested
901 - 1000 of 16475 matches
Mail list logo
