Sponsor tasksel upload

2021-04-15 Thread Holger Wansing
Hi,

Paul Gevers  wrote (Thu, 15 Apr 2021 09:55:34 +0200):
> Hi Holger,
> 
> On 10-04-2021 18:14, Holger Wansing wrote:
> >>> 2. A problem came up during freeze regarding input methods for several 
> >>>languages:
> >>>Starting with bullseye, GNOME depends on ibus, which is not fully
> >>>compatible with the view of some language teams, who would like to
> >>>prefer fcitx. 
> >>>The best way to get this situation fixed would require some new
> >>>binary packages to be added to Bullseye (would only be tasks packages,
> >>>so no new code/functions to be added!).
> >>>A thread regarding this started at
> >>>   https://lists.debian.org/debian-boot/2021/03/msg00058.html
> >>>and the release-team was also added to the loop at some point.
> >>>Maybe release-team could look into this too, and try to make a 
> >>>decision?
> >>
> >> Did you conclude in that thread what the optimal option would be from
> >> your side? And what's the preferred option without new packages?
> > 
> > That's not just my opinion, but sort of consensus of the involved people.
> > Going through the above mentioned thread shows that.
> > There are also alternatives mentioned, but they all have their 
> > disadvantages,
> > that's why the consensus.
> 
> We had a bit of discussion on this and if you think with these addition
> (meta) packages we can fix this problem, let's have them. Please prepare
> and upload. We'll notify ftp-masters that this upload to NEW is meant
> for bullseye. Ideally of course, you'd be able to test in unstable that
> the solution actually works before we accept them in testing. Is that
> feasible?

Could someone upload tasksel 3.66 for me, please?

Since I only have DM upload rights, I cannot do this, because this upload
adds new packages.

tasksel is prepared ready for upload in git.


Thanks!
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Finding a tentative bullseye release date

2021-04-15 Thread Holger Wansing
Hi,

Holger Wansing  wrote (Thu, 15 Apr 2021 19:38:34 +0200):
> > Ideally of course, you'd be able to test in unstable that
> > the solution actually works before we accept them in testing. Is that
> > feasible?
> 
> Hmm, the installer installs tasksel from testing by default AFAIK, so that 
> would  need some special tweaking to allow for such tests ...
> I will need to look into this.

I found how to do such test, so let's do it like that:
upload to unstable, and then I will do some tests.
After that, I will file an unblock request.

Thanks again
Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



inquiring for input to the release notes

2021-04-15 Thread Paul Gevers
Hi boot team,

As is custom in the final phases of the release, I'm asking you to think
about issues that are worth mentioning in the release notes for bullseye
from the perspective of the installer.

Feel free to reply to this e-mail, or, even better, to bts against the
release-notes package if there's anything that comes to your mind.

Paul



OpenPGP_signature
Description: OpenPGP digital signature


Re: Finding a tentative bullseye release date

2021-04-15 Thread Holger Wansing
Hi,

Paul Gevers  wrote (Thu, 15 Apr 2021 09:55:34 +0200):
> Hi Holger,
> 
> On 10-04-2021 18:14, Holger Wansing wrote:
> >>> 2. A problem came up during freeze regarding input methods for several 
> >>>languages:
> >>>Starting with bullseye, GNOME depends on ibus, which is not fully
> >>>compatible with the view of some language teams, who would like to
> >>>prefer fcitx. 
> >>>The best way to get this situation fixed would require some new
> >>>binary packages to be added to Bullseye (would only be tasks packages,
> >>>so no new code/functions to be added!).
> >>>A thread regarding this started at
> >>>   https://lists.debian.org/debian-boot/2021/03/msg00058.html
> >>>and the release-team was also added to the loop at some point.
> >>>Maybe release-team could look into this too, and try to make a 
> >>>decision?
> >>
> >> Did you conclude in that thread what the optimal option would be from
> >> your side? And what's the preferred option without new packages?
> > 
> > That's not just my opinion, but sort of consensus of the involved people.
> > Going through the above mentioned thread shows that.
> > There are also alternatives mentioned, but they all have their 
> > disadvantages,
> > that's why the consensus.
> 
> We had a bit of discussion on this and if you think with these addition
> (meta) packages we can fix this problem, let's have them. Please prepare
> and upload. We'll notify ftp-masters that this upload to NEW is meant
> for bullseye. 

That's great. Thanks!

> Ideally of course, you'd be able to test in unstable that
> the solution actually works before we accept them in testing. Is that
> feasible?

Hmm, the installer installs tasksel from testing by default AFAIK, so that 
would  need some special tweaking to allow for such tests ...
I will need to look into this.

> 
> Side note, on our check list [1], there's also a note on asking you if
> the install guide is up-to-date. Can you confirm that?

Yes, the version currently in Bullseye was meant for the release, and it
should be fine for it!


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#986506: marked as done (debian-installer: Please rebuild the installer images (Bullseye) in order to get a newer kernel version)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 18:32:47 +0200
with message-id <20210415163247.rrv47y7jyphgm...@mraw.org>
and subject line Re: Bug#986506: The released version of debian-installer still 
has the old kernel
has caused the Debian Bug report #986506,
regarding debian-installer: Please rebuild the installer images (Bullseye) in 
order to get a newer kernel version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
986506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20201202
Severity: important
Tags: d-i

Hello maintainers of the Debian installer,

Now that Debian Bullseye is in hard freeze, could you consider to update the
Debian installer images to use the current kernel from Bullseye [2]? This would
help in building live images using live-build [3].

The last published image of the Debian installer is from 2020-12-02 [1], and
the kernel version is 5.9.0-4-amd64, while in Bullseye the kernel currently is
5.10.0-5-amd64. The daily-built images contain the current kernel [4].

With kind regards,
Roland Clobus

PS: This was also posted to the mailing list [5], without a reply so far

[1] http://deb.debian.org/debian/dists/bullseye/main/installer-amd64/
[2]
http://deb.debian.org/debian/dists/bullseye/main/installer-
amd64/current/images/cdrom/
[3] https://wiki.debian.org/ReproducibleInstalls/LiveImages
[4] https://d-i.debian.org/daily-images/amd64/daily/cdrom/
[5] https://lists.debian.org/debian-boot/2021/03/msg00166.html


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'testing-
debug'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 20210415

Tomas Pospisek  (2021-04-14):
> I had checked that my installer had 5.10.0 and if your assessement is right
> then my installer must have been a daily build. Thanks a lot Roland for
> keeping the finger on this issue!
> *t

Uploaded some hours ago.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---


Re: Including partman-hfs to the team's git project

2021-04-15 Thread Cyril Brulebois
Hi,

John Paul Adrian Glaubitz  (2021-04-15):
> I created a partman-hfs package that is required for the installation
> of PowerMacs but will also allow to create HFS and HFS+ partitions on
> any machines. It might be useful on Intel Macs as well for creating
> shared partitions for dual-boot Macs.
> 
> While including the necessary hfsprogs-udeb in debian-installer is a
> bit tricky due to the non-free license of src:hfsprogs, I was
> wondering whether it would be okay nevertheless to include the git
> repository for partman-hfs packaging in the debian-installer's team
> project?

I don't think having an extra repository would be an issue.

Some care might be required to make sure we don't burden translators
with a somewhat special component, but AFAIR that shouldn't happen until
the package is (possibly) added to the list of packages that require
translations. Holger would likely know better.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Bug#985956: Merge request submittted to initramfs-tools

2021-04-15 Thread Samuel Thibault
Hello,

Pete Batard, le jeu. 15 avril 2021 16:11:02 +0100, a ecrit:
> Quite a few people are negatively affected by this bug, and one can expect a
> lot more to be if Debian 11 goes to release without the inclusion of
> mdio-bcm-unimac.ko in the netinst ARM64 ISOs.
> 
> I have created an initramfs-tools merge request to attempt to fix the
> problem, which can be found at:
> https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/46

AIUI initramfs-tools rules are not used to build the nic-modules
udeb, it'd rather be happening in the linux package, in
debian/installer/modules/nic-modules, which indeed doesn't include
drivers/net/mdio/.

Linux maintainers, do you know more on this issue?

Samuel



Bug#985956: Merge request submittted to initramfs-tools

2021-04-15 Thread Pete Batard
Note that this is a rather critical regression (since it used to work 
fine with previous bullseye ISOs), that is currently preventing 
installation of Debian on the Raspberry Pi 4, i.e. by far the most 
widespread ARM64 platform out there.


Quite a few people are negatively affected by this bug, and one can 
expect a lot more to be if Debian 11 goes to release without the 
inclusion of mdio-bcm-unimac.ko in the netinst ARM64 ISOs.


I have created an initramfs-tools merge request to attempt to fix the 
problem, which can be found at:

https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/46

However, since I am not entirely familiar with how netinst ISO kernel 
modules are generated and picked, I can't vouch that the proposed fix, 
which consists of referencing the mdio/ subdirectory for inclusion, is 
the proper way to go...




Re: Please dak copy-installer 20210415

2021-04-15 Thread Mark Hymers
On Thu, 15, Apr, 2021 at 04:21:40AM +0200, Cyril Brulebois spoke thus..
> Hi,
> 
> FTP Masters, please sync the installer from sid to testing, as it seems
> to be Installed for all release architectures (9 total):
> 
>   dak copy-installer 20210415
> 
> (Release team: FYI, I've urgented it.)


Done,

Mark

-- 
Mark Hymers 


signature.asc
Description: PGP signature


Bug#958527: marked as done (installation-reports: Successful install of Debian Ports on PowerMac G5)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:23:57 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #958527,
regarding installation-reports: Successful install of Debian Ports on PowerMac 
G5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: CD
Image version: 
https://cdimage.debian.org/cdimage/ports/2020-04-19/debian-10.0-ppc64-NETINST-1.iso
Date: 

Machine: PowerMac G5 "PowerMac7,3"
Partitions: 
rbthomas@kmac:~$ df -Tl | grep -v tmpfs
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/sdb3  ext4 235283576 1341840 221920328   1% /
/dev/sdb2  hfs 1249906522118468   6% /boot/grub
rbthomas@kmac:~$ lsblk
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:00 931.5G  0 disk 
├─sda18:10  31.5K  0 part 
├─sda28:20   977K  0 part 
├─sda38:30 244.1M  0 part 
├─sda48:40 931.3G  0 part 
│ ├─kmac--vg-root   254:00   6.5G  0 lvm  
│ ├─kmac--vg-swap_1 254:10  11.4G  0 lvm  
│ └─kmac--vg-home   254:20 913.4G  0 lvm  
└─sda58:50  24.5K  0 part 
sdb   8:16   0 232.9G  0 disk 
├─sdb18:17   0  31.5K  0 part 
├─sdb28:18   0 122.1M  0 part /boot/grub
├─sdb38:19   0   229G  0 part /
├─sdb48:20   0   3.8G  0 part [SWAP]
└─sdb58:21   0  56.5K  0 part 
sdc   8:32   1  28.9G  0 disk 
└─sdc18:33   1  28.9G  0 part 
sr0  11:01  1024M  0 rom  



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect media:   [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:


Works great!  Congrats to Adrian!

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20200315"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux kmac 5.5.0-2-powerpc64 #1 SMP Debian 5.5.17-1 (2020-04-15) 
ppc64 GNU/Linux
lspci -knn: lspci: Unable to load libkmod resources: error -12
lspci -knn: :f0:0b.0 Host bridge [0600]: Apple Inc. U3H AGP Bridge 
[106b:0059]
lspci -knn: Kernel driver in use: agpgart-uninorth
lspci -knn: :f0:10.0 VGA compatible controller [0300]: Advanced Micro 
Devices, Inc. [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series] [1002:4150]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 
9550/9600/X1050 Series] [1002:4150]
lspci -knn: 0001:00:00.0 Host bridge [0600]: Apple Inc. U3 HT Bridge [106b:0057]
lspci -knn: 0001:00:01.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge 
[106b:0045]
lspci -knn: 0001:00:02.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge 
[106b:0046]
lspci -knn: 0001:00:03.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge 
[106b:0047]
lspci -knn: 0001:00:04.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge 
[106b:0048]
lspci -knn: 0001:00:05.0 PCI bridge [0604]: Apple Inc. K2 HT-PCI Bridge 
[106b:0049]
lspci -knn: 0001:01:07.0 Unassigned class [ff00]: Apple Inc. K2 KeyLargo Mac/IO 
[106b:0041] (rev 60)
lspci -knn: Kernel driver in use: macio
lspci -knn: 0001:01:08.0 USB controller [0c03]: Apple Inc. K2 KeyLargo USB 
[106b:0040]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:01:09.0 USB controller [0c03]: Apple Inc. K2 KeyLargo USB 
[106b:0040]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:02:0d.0 Unassigned class [ff00]: 

Bug#959467: marked as done (installation-reports: succesful installation on powermac G4 - powerpc)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:20:38 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #959467,
regarding installation-reports: succesful installation on powermac G4 - powerpc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
959467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: CD
Image version: 
https://cdimage.debian.org/cdimage/ports/2020-04-19/debian-10.0-powerpc-NETINST1.iso
Date: 2020-05-02

Machine: PowerBook G4, PowerBook5,8, A1138
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   1012380   0   1012380   0% /dev
tmpfs  tmpfs   206180 956205224   1% /run
/dev/sda4  ext4  60184256 4223440  52873876   8% /
tmpfs  tmpfs  1030888   0   1030888   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  1030888   0   1030888   0% /sys/fs/cgroup
/dev/sda2  hfs 1249906676118314   6% /boot/grub
tmpfs  tmpfs   206176   0206176   0% /run/user/0
tmpfs  tmpfs   206176   8206168   1% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:



ALL ok
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20200315"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux powerbook 5.5.0-2-powerpc #1 Debian 5.5.17-1 (2020-04-15) ppc 
GNU/Linux
lspci -knn: lspci: Unable to load libkmod resources: error -12
lspci -knn: :00:0b.0 Host bridge [0600]: Apple Inc. Intrepid2 AGP Bridge 
[106b:0066]
lspci -knn: Kernel driver in use: agpgart-uninorth
lspci -knn: :00:10.0 VGA compatible controller [0300]: Advanced Micro 
Devices, Inc. [AMD/ATI] RV350/M10 / RV360/M11 [Mobility Radeon 9600 (PRO) / 
9700] [1002:4e50]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV350/M10 / 
RV360/M11 [Mobility Radeon 9600 (PRO) / 9700] [1002:4e50]
lspci -knn: Kernel driver in use: radeonfb
lspci -knn: 0001:10:0b.0 Host bridge [0600]: Apple Inc. Intrepid2 PCI Bridge 
[106b:0067]
lspci -knn: 0001:10:11.0 Network controller [0280]: Broadcom Inc. and 
subsidiaries BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller 
[14e4:4318] (rev 02)
lspci -knn: Subsystem: Apple Inc. Device [106b:4318]
lspci -knn: Kernel driver in use: b43-pci-bridge
lspci -knn: 0001:10:14.0 CardBus bridge [0607]: Texas Instruments PCI1510 PC 
card Cardbus Controller [104c:ac56]
lspci -knn: Kernel driver in use: yenta_cardbus
lspci -knn: 0001:10:15.0 USB controller [0c03]: NEC Corporation OHCI USB 
Controller [1033:0035] (rev 43)
lspci -knn: Subsystem: NEC Corporation OHCI USB Controller [1033:0035]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:10:15.1 USB controller [0c03]: NEC Corporation OHCI USB 
Controller [1033:0035] (rev 43)
lspci -knn: Subsystem: NEC Corporation OHCI USB Controller [1033:0035]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:10:15.2 USB controller [0c03]: NEC Corporation 

Bug#986894: marked as done (installation report)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:19:57 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #986894,
regarding installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
986894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: DVD 1
Image version: 
https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-dvd/
Date: 04/12/2021 23:00 UTC-5

Machine: Desktop
Processor: Intel Core i5-8600k
Memory: 16.0 GiB
Partitions:
S.ficheros Tipo bloques de 1KUsados Disponibles Uso% Montado en
udev   devtmpfs   8109116 0 8109116   0% /dev
tmpfs  tmpfs  1626412  1648 1624764   1% /run
/dev/sda5  ext4 102687492   496792492460316   6% /
tmpfs  tmpfs  8132048142952 7989096   2% /dev/shm
tmpfs  tmpfs 5120 45116   1% /run/lock
/dev/sda7  ext4 648173624 111246536   530314948  18% /media/datos
tmpfs  tmpfs  1626408   168 1626240   1% /run/user/1000
/dev/sdb1  iso96603875424   3875424   0 100%
/media/snt/Debian bullseye-DI-a3 amd64 1

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor
Host Bridge/DRAM Registers [8086:3ec2] (rev 07)
Subsystem: Gigabyte Technology Co., Ltd 8th Gen Core Processor Host
Bridge/DRAM Registers [1458:5000]
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller [0300]: Intel Corporation
CometLake-S GT2 [UHD Graphics 630] [8086:3e92]
DeviceName:  Onboard IGD
Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) 
[1458:d000]
Kernel driver in use: i915
Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6
/ E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
[8086:1911]
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/v6 / E3-1500
v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [1458:5000]
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370
Chipset Family USB 3.0 xHCI Controller [8086:a2af]
Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller [1458:5007]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 200 Series
PCH CSME HECI #1 [8086:a2ba]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH CSME HECI 
[1458:1c3a]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA
controller [AHCI mode] [8086:a282]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SATA
controller [AHCI mode] [1458:b005]
Kernel driver in use: ahci
Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #17 [8086:a2e7] (rev f0)
Kernel driver in use: pcieport
00:1b.2 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #19 [8086:a2e9] (rev f0)
Kernel driver in use: pcieport
00:1b.3 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #20 [8086:a2ea] (rev f0)
Kernel driver in use: pcieport
00:1b.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #21 [8086:a2eb] (rev f0)
Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #1 [8086:a290] (rev f0)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #5 [8086:a294] (rev f0)
Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #7 [8086:a296] (rev f0)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #9 [8086:a298] (rev f0)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Z370 Chipset LPC/eSPI
Controller [8086:a2c9]
Subsystem: Gigabyte Technology Co., Ltd Z370 Chipset LPC/eSPI
Controller [1458:5001]
00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370
Chipset Family Power Management Controller [8086:a2a1]
Subsystem: Gigabyte 

Bug#976421: marked as done (Debian 11 successfully installed at AMD-K10 desktop PC)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:16:37 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #976421,
regarding Debian 11 successfully installed at AMD-K10 desktop PC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-CDROM
Image version: Self-made ISO image with current installer from testing (Alpha3?)
Date: 2020-12-04

Machine: Self-made Desktop PC
Processor: AMD A10-5700 APU with Radeon(tm) HD Graphics
Memory: 4GB
Partitions: 

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   1905512   0   19055120% /dev
> tmpfs  tmpfs   384696 9123837841% /run
> /dev/sda1  ext4 113871044 8601812  994418568% /
> tmpfs  tmpfs  1923472   12332   19111401% /dev/shm
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs 4096   0  40960% /sys/fs/cgroup
> tmpfs  tmpfs   384692 1163845761% /run/user/1000

Output of lspci -knn (or lspci -nn):

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Root Complex [1022:1410]
>   Subsystem: ASUSTeK Computer Inc. Family 15h (Models 10h-1fh) Processor 
> Root Complex [1043:8526]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
>   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
>   Kernel driver in use: radeon
>   Kernel modules: radeon
> 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 
> HDMI Audio Controller [1002:9902]
>   Subsystem: ASUSTeK Computer Inc. Trinity HDMI Audio Controller 
> [1043:8526]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: ASUSTeK Computer Inc. FCH SATA Controller [AHCI mode] 
> [1043:8527]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 14)
>   Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8527]
>   Kernel driver in use: piix4_smbus
>   Kernel modules: i2c_piix4, sp5100_tco
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
> [1022:780e] (rev 11)
>   Subsystem: 

Bug#976812: marked as done (Debian 11 successfully installed at Asus ZenBook UX501)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:15:42 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #976812,
regarding Debian 11 successfully installed at Asus ZenBook UX501
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: Network
Image version: Debian 11 Alpha3
Date: 2020-12-08

Machine: Asus Zenbook Pro UX501J
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
Memory: 16GB
Partitions: 

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   8124836   0   81248360% /dev
> tmpfs  tmpfs  16285601132   16274281% /run
> /dev/sdb2  ext4 121044680 8577532 1062753288% /
> tmpfs  tmpfs  8142784   12124   81306601% /dev/shm
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs 4096   0  40960% /sys/fs/cgroup
> /dev/sdb1  vfat52324838565193921% /boot/efi
> tmpfs  tmpfs  1628556 132   16284241% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor DRAM Controller [8086:0c04] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
> DRAM Controller [1043:18dd]
>   Kernel modules: ie31200_edac
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor PCI Express x16 Controller [8086:0c01] (rev 06)
>   Kernel driver in use: pcieport
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
> Processor Integrated Graphics Controller [8086:0416] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
> Graphics Controller [1043:18dd]
>   Kernel driver in use: i915
>   Kernel modules: i915
> 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor HD Audio Controller [8086:0c0c] (rev 06)
>   Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
> Audio Controller [8086:2010]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB xHCI [8086:8c31] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB xHCI [1043:18dd]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
> Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> MEI Controller [1043:18dd]
>   Kernel driver in use: mei_me
>   Kernel modules: mei_me
> 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #2 [8086:8c2d] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
> High Definition Audio Controller [8086:8c20] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High 
> Definition Audio Controller [1043:18dd]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #1 [8086:8c10] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #3 [8086:8c14] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #4 [8086:8c16] (rev d5)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #1 [8086:8c26] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller 
> [8086:8c4b] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller 

Bug#973530: marked as done (installation-report: successful installation on SD card on EEE PC, runs on X230)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:09:26 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #973530,
regarding installation-report: successful installation on SD card on EEE PC, 
runs on X230
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
973530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Version: 2.75
Severity: minor

Dear Maintainer,

Everything went extremely well, just sending you this because the
installer asked me to.


-- Package-specific info:

Boot method: netinst/linux on hd
Image version: 
https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/ 
(downloaded 2020-10-31)
Date: 

Machine: installation: EEE PC X101H; runs on: X230
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O] via network (netinst)
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:



-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201031-00:08:02"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux debian-sd 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ac]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom 
Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 
02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ac]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ac]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family 
High Definition Audio Controller [8086:27d8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:84d3]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 1 [8086:27d0] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 2 [8086:27d2] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 4 [8086:27d6] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #1 [8086:27c8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #2 [8086:27c9] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #3 [8086:27ca] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #4 [8086:27cb] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Eee PC 1015PX [1043:83ad]
lspci -knn: Kernel driver in 

Bug#984727: marked as done (installation-reports: just an installation report)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:02:00 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #984727,
regarding installation-reports: just an installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: wishlist

-- Package-specific info:

Boot method: USB
Image version: debian-mac-10.8.0-amd64-netinst.iso 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ 2021-02-06
Date: 

Machine: MacBook3,1 (Nov 2007)
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u8"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 5 [8086:2847] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801H 

Bug#985917: marked as done (installation-reports: Bullseye Alpha 3 successful on GNOME Boxes in Mint 20)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:03:15 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #985917,
regarding installation-reports: Bullseye Alpha 3 successful on GNOME Boxes in 
Mint 20
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
985917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: wishlist
X-Debbugs-Cc: cdpa...@hotmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: GNOME Boxes, presented ISO to hypervisor as DVD.
Image version: debian-bullseye-DI-alpha3-amd64-netinst.iso
Date: Thu, Mar 25, 2021, approximately 5:30pm US-EDT

Machine: Lenovo H30-50 desktop, Linux Mint 20 Ulyanna Cinnamon host system 
(fully updated prior to guest installation), Intel Pentium G3260 processor, 4GB 
DDR3 memory.
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs669692   0669692   0% /dev
tmpfs  tmpfs   138516 884137632   1% /run
/dev/sda1  ext4  19525456 3812848  14697724  21% /
tmpfs  tmpfs   692576   26792665784   4% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   138512  52138460   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[E]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
Chose defaults for all options except mirror, where I chose ftp.us.debian.org 
and got an error message. However, it then seemed to proceed normally. All 
other aspects of installation were clean, guest rebooted and installed system 
is normal.


Chose Xfce instead of GNOME as the DE. Installation was smooth and pleasant.

Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201202"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux bullseye-testing-alpha3 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 
(2020-11-27) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL 
paravirtual graphic card [1b36:0100] (rev 04)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: 8139cp
lspci -knn: Kernel modules: 8139cp, 8139too
lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci 

Bug#980445: marked as done (installation-reports: Bullseye Alpha 3 works well on my AND64)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:04:05 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #980445,
regarding installation-reports: Bullseye Alpha 3 works well on my AND64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
980445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: wishlist
Tags: d-i

Dear Maintainer,

the installation went smooth.  Compliments and thanks for your efforts to
provide the code!


-- Package-specific info:

Boot method: netinst.iso copied to USB stick
Image version: 
https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-cd/debian-bullseye-DI-alpha3-amd64-netinst.iso
 build 3 Dec'20
Date: 

Machine: Individual Desktop PC
Partitions:

Disk /dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L: 931.51 GiB, 1000204886016 
bytes, 1953525168 sectors
Disk model: TOSHIBA-RD500
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x273d524d

DeviceBoot StartEnd 
   Sectors   Size Id Type
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part1 * 2048  105467903 
 105465856  50.3G 83 Linux
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part2  105467904  136718335 
  31250432  14.9G 83 Linux
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part3  136718336  275781631 
 139063296  66.3G 83 Linux
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part4  275783678 1953523711 
1677740034   800G  5 Extended
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part5  275783680  316796927 
  41013248  19.6G 83 Linux
/dev/disk/by-id/nvme-TOSHIBA-RD500_X9IA212FKN2L-part6  316798976 1953523711 
1636724736 780.5G 83 Linux

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

No problems -- thanks again!
--

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201202"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Desktop 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse Root Complex [1022:1480]
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] X570-A PRO 
motherboard [1462:7c37]
lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse IOMMU [1022:1481]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
IOMMU [1022:1481]
lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
lspci -knn: 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse GPP Bridge [1022:1483]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
lspci -knn: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
lspci -knn: 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse GPP Bridge [1022:1483]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
lspci -knn: 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PCIe Dummy Host 

Bug#974883: marked as done (installation-reports: Successful install on AMD Ryzen)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:05:52 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #974883,
regarding installation-reports: Successful install on AMD Ryzen
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
974883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: minor

Hi,

No problem to report, this is a success report.

-- Package-specific info:

Boot method: USB key
Image version: Debian GNU/Linux 10.4.0 "Buster" - Unofficial amd64 NETINST with 
firmware 20200509-10:25 (torrent from 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/bt-cd/firmware-10.4.0-amd64-netinst.iso.torrent)
Date: 2020-05-21 21:43:13 +0200

Machine: Compact Fanless AMD Ryzen Mini PC
Partitions: (df -Tl)

Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   79076600   7907660   0% /dev
tmpfs  tmpfs  1589244  740   1588504   1% /run
/dev/sda3  ext4  14352840  3815856   9788184  29% /
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs  33738600   3373860   0% /dev/shm
/dev/sda2  ext427538742828213820  17% /boot
/dev/sda1  vfat 47371 5288 42083  12% /boot/efi
/dev/sda7  ext4 466841176 96470864 346586376  22% /donnees
/dev/sda6  ext4   4740224   138528   4341192   4% /home
/dev/sda5  ext4   3779640   468668   3099260  14% /var
tmpfs  tmpfs   20480041284163516  21% /tmp

(fdisk -l /dev/sda)

Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: TS512GMTS430S   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B31FF558-4100-4170-9B4A-C0B4A5409C78

DeviceStartEnd   Sectors   Size Type
/dev/sda1  2048  98303 9625647M EFI System
/dev/sda2 98304 684031585728   286M Linux filesystem
/dev/sda3684032   29980671  2929664014G Linux filesystem
/dev/sda4  29980672   31934463   1953792   954M Linux swap
/dev/sda5  31934464   39747583   7813120   3,7G Linux filesystem
/dev/sda6  39747584   49512447   9764864   4,7G Linux filesystem
/dev/sda7  49512448 1000214527 950702080 453,3G Linux filesystem


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

I disabled secure boot in the BIOS for the install; now I can't seem able to
make it work: I get a message on boot about invalid keys. (I don't know
whether installing with secure boot from the start would've worked.)

I had no CD to detect; the install USB key was detected fine.

I like to control things and messed up partitions a few times (the defaults
didn't suit me) but encountered no actual problem with the installer. The
rest of the installation was rather straightforward.

I created my user and installed packages by hand afterwards (not via tasks),
including switching from SystemD to SysV init.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux caramel 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] 
Device [1022:15d0]
lspci -knn: Subsystem: ASRock Incorporation Device [1849:15d0]
lspci -knn: 00:00.2 IOMMU 

Bug#977587: marked as done (installation-reports: All went very well, thank you to all !)

2021-04-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Apr 2021 14:05:03 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #977587,
regarding installation-reports: All went very well, thank you to all !
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: minor

Dear Maintainer,

As noted in /usr/share/doc/installation-report/README.Debian
you appreciate reports even when everything went fine.

This was absolutely the case for me. I would like to thank
the whole Debian community for the amazing work done every single day.

You rock guys !

-- Package-specific info:

Boot method: USB Live Image
Image version: Debian Buster 10 Live amd64 gnome
Date: 31 Jan 2020

Machine: Intel NUC5i3RYK
Partitions: 

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

None


-- 

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u2"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux horous 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 
(2019-09-20) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host 
Bridge -OPI [8086:1604] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD 
Graphics 5500 [8086:1616] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio 
Controller [8086:160c] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP 
USB xHCI Controller [8086:9cb1] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Wildcat 
Point-LP MEI Controller #1 [8086:9cba] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (3) I218-V [8086:15a3] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP 
High Definition Audio Controller [8086:9ca0] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI 
Express Root Port #1 [8086:9c90] (rev e3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI 
Express Root Port #4 [8086:9c96] (rev e3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP 
USB EHCI Controller [8086:9ca6] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Wildcat Point-LP LPC 
Controller [8086:9cc3] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation Wildcat Point-LP 
SATA Controller [AHCI Mode] [8086:9c83] (rev 03)
lspci -knn: Subsystem: Intel Corporation Device [8086:2057]
lspci -knn: Kernel driver in use: ahci
lspci 

Re: Finding a tentative bullseye release date

2021-04-15 Thread Paul Gevers
Hi Holger,

On 10-04-2021 18:14, Holger Wansing wrote:
>>> 2. A problem came up during freeze regarding input methods for several 
>>>languages:
>>>Starting with bullseye, GNOME depends on ibus, which is not fully
>>>compatible with the view of some language teams, who would like to
>>>prefer fcitx. 
>>>The best way to get this situation fixed would require some new
>>>binary packages to be added to Bullseye (would only be tasks packages,
>>>so no new code/functions to be added!).
>>>A thread regarding this started at
>>> https://lists.debian.org/debian-boot/2021/03/msg00058.html
>>>and the release-team was also added to the loop at some point.
>>>Maybe release-team could look into this too, and try to make a 
>>>decision?
>>
>> Did you conclude in that thread what the optimal option would be from
>> your side? And what's the preferred option without new packages?
> 
> That's not just my opinion, but sort of consensus of the involved people.
> Going through the above mentioned thread shows that.
> There are also alternatives mentioned, but they all have their disadvantages,
> that's why the consensus.

We had a bit of discussion on this and if you think with these addition
(meta) packages we can fix this problem, let's have them. Please prepare
and upload. We'll notify ftp-masters that this upload to NEW is meant
for bullseye. Ideally of course, you'd be able to test in unstable that
the solution actually works before we accept them in testing. Is that
feasible?

Side note, on our check list [1], there's also a note on asking you if
the install guide is up-to-date. Can you confirm that?

Paul

[1]
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/BullseyeCheckList



OpenPGP_signature
Description: OpenPGP digital signature


Including partman-hfs to the team's git project

2021-04-15 Thread John Paul Adrian Glaubitz
Hi!

I created a partman-hfs package that is required for the installation of
PowerMacs but will also allow to create HFS and HFS+ partitions on any
machines. It might be useful on Intel Macs as well for creating shared
partitions for dual-boot Macs.

While including the necessary hfsprogs-udeb in debian-installer is a bit
tricky due to the non-free license of src:hfsprogs, I was wondering whether
it would be okay nevertheless to include the git repository for partman-hfs
packaging in the debian-installer's team project?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913