[Ben Hutchings]
> These packages have included AppStream files with elements
> for years (since 20160110-1). The elements are what I'm
> adding.
Aha. I did not remember. Checked isenkram-autoinstall-firmware and it
will both check the home made index files extracted from apt-file, and
Hi,
Ritesh Raj Sarraf (2021-04-30):
> The upload I prepped failed on some of the architectures.
> https://buildd.debian.org/status/logs.php?pkg=open-iscsi=2.1.3-3
It's lacking a push to the Git repository (git fetch didn't get anything
new from a few days ago).
> In d/control, there is:
>
>
Hi. I have been reading these threads about AMD GPUs failing and giving black
or distorted screens at boot. I am writing here to drop an idea. I
hope this helps,
if not, just forget it. :)
Could you make the system detect the unsuccessful boot failing to load
the graphical desktop interface,
On Fri, 2021-04-30 at 08:42 +0200, Petter Reinholdtsen wrote:
> [Ben Hutchings]
> > Here's what I came up with:
> > https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/19
> >
> > The generated files can be seen in:
> > https://people.debian.org/~benh/firmware-metainfo/
>
>
On Fri, Apr 30, 2021 at 09:25:47PM +0200, Rado Q wrote:
> Installation network setup was auto-configured while the system was
> in a network with proxy-auto-config active.
>
> Expectation:
> when choosing auto-configure-network during installation, the
> resulting system should be operative in
Package: installation-reports
Boot method: network
Image version: mini.iso with files within of Nov 30 09:49 2020
Date: sometime in Dec 2020
Machine: various
Processor: various
Memory: 8gb
Partitions: basically 2 ext4 parts, / + /home
Base System Installation Checklist:
[O] = OK, [E] = Error
On Fri, 2021-04-30 at 21:20 +0530, Ritesh Raj Sarraf wrote:
>
> How would you like to see this fixed Cyril ?
>
> The easiest option, if d-i supports, would be to extend architecture
> list to: `linux-any`, keeping it in line with what the actual open-
> iscsi package supports.
Here's what I've
The upload I prepped failed on some of the architectures.
https://buildd.debian.org/status/logs.php?pkg=open-iscsi=2.1.3-3
In d/control, there is:
```
Package: open-iscsi-udeb
# Note: the (virtual) udeb package scsi-modules (provided by different
# linux kernel udebs) must exist for these
I'm afraid that I was misinterpreting the screenshots, because it was
typing 'down' and 'ret' in quick enough succession for it only to show
the previous menu item.
This test shows what's going on much more clearly:
https://openqa.debian.net/tests/2401#step/locale/11
(that screenshot is the
* Cyril Brulebois [210430 09:47]:
> Anyway, looking at the diffstat between 1.43.0 (last known good) and
> 1.44.4 (first known bad), we have this:
> 179 files changed, 19157 insertions(+), 7045 deletions(-)
>
> Between 1.43.0 and 1.44 (if it were an earlier known bad):
> 165 files changed,
Chris Hofstaedtler (2021-04-29):
> > Alright, I think I'm hitting my limits here.
> >
> > Versions 1.44, 1.44.2, and 1.44.3 all fail in a similar way:
> ../pango/pangofc-font.c:371:44: error: ‘HB_OT_METRICS_UNDERLINE_SIZE’
> undeclared (first use in this function); did you mean
>
Package: debian-installer
Severity: normal
As per kibi's request on IRC I'm opening this as a separate bug to make tracking
it as a distinct scenario easier.
This was detected while hunting for ways to trigger #987449
In order to trigger a lock-up, one does the following:
At the language
[Ben Hutchings]
> Here's what I came up with:
> https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/19
>
> The generated files can be seen in:
> https://people.debian.org/~benh/firmware-metainfo/
Cool. I'll see what I can get isenkram to do with the tags.
Might take a while,
13 matches
Mail list logo
