Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Package: debootstrap Version: debootstrap/1.0.110 Severity: serious Merged /usr is now the default in buster. As discussed on debian-devel, however, binary packages built on a merged-usr system are not installable on a non-merged-usr system. I think we would like ad hoc builds of packages from one buster machine to be installable on other buster machines. That is not compatible with the current approach. This was an unanticipated problem. The discussion on -devel has not reached a consensus on a way forward, and there is no transition plan. Accordingly, please revert this change for buster. IMO this revert should be done quickly, to minimise the number of installs which will generate broken packages. If you do not agree with my proposal, then I still think we should revert the change in sid/buster while the matter is discussed. This affects stretch-backports too, but I think it will be most convenient to file a separate bug for that. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#914898: debootstrap, stretch-backports: Please disabled merged /usr by default
Package: debootstrap Version: debootstrap/1.0.110~bpo9+1 Severity: serious In #914208 Simon McVittie writes: > [merge-/usr] is now the default in stretch-backports' debootstrap As discussed on debian-devel, however, binary packages built on a merged-usr system are not installable on a non-merged-usr system. Obviously we would like ad hoc builds of packages from one stretch machine to be installable on other stretch machines. I do not see any way in which this could be resolved for stretch. Accordingly, please urgently revert this change for stretch-backports. Ian. (I have CC'd debian-release@lists because this seems like it wants the attention of the stable release team. I wasn't able to find a separate contact address for the stable release team here https://www.debian.org/intro/organization and I have a vague memory that this is somehow the same list. Please redirect me if I am wrong.) -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#914898: debootstrap, stretch-backports: Please disabled merged /usr by default
On Wed, 28 Nov 2018, Ian Jackson wrote: > Package: debootstrap > Version: debootstrap/1.0.110~bpo9+1 > Severity: serious > > In #914208 Simon McVittie writes: > > [merge-/usr] is now the default in stretch-backports' debootstrap > > As discussed on debian-devel, however, binary packages built on a > merged-usr system are not installable on a non-merged-usr system. > Obviously we would like ad hoc builds of packages from one stretch > machine to be installable on other stretch machines. > > I do not see any way in which this could be resolved for stretch. > Accordingly, please urgently revert this change for stretch-backports. > > Ian. > > (I have CC'd debian-release@lists because this seems like it wants the > attention of the stable release team. I wasn't able to find a > separate contact address for the stable release team here > https://www.debian.org/intro/organization > and I have a vague memory that this is somehow the same list. Please > redirect me if I am wrong.) I didn't followed the discussion, but the default should be the same as in buster. I don't want debootstrap to behave different than in testing. Alex - Backports ftpmaster
Bug#914898: marked as done (debootstrap, stretch-backports: Please disabled merged /usr by default)
Your message dated Wed, 28 Nov 2018 13:22:30 +0100 with message-id <87bc37a8-3f5c-38dc-fe6b-544868634...@debian.org> and subject line Re: Bug#914898: debootstrap, stretch-backports: Please disabled merged /usr by default has caused the Debian Bug report #914898, regarding debootstrap, stretch-backports: Please disabled merged /usr by default 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.) -- 914898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debootstrap Version: debootstrap/1.0.110~bpo9+1 Severity: serious In #914208 Simon McVittie writes: > [merge-/usr] is now the default in stretch-backports' debootstrap As discussed on debian-devel, however, binary packages built on a merged-usr system are not installable on a non-merged-usr system. Obviously we would like ad hoc builds of packages from one stretch machine to be installable on other stretch machines. I do not see any way in which this could be resolved for stretch. Accordingly, please urgently revert this change for stretch-backports. Ian. (I have CC'd debian-release@lists because this seems like it wants the attention of the stable release team. I wasn't able to find a separate contact address for the stable release team here https://www.debian.org/intro/organization and I have a vague memory that this is somehow the same list. Please redirect me if I am wrong.) -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. --- End Message --- --- Begin Message --- On Wed, 28 Nov 2018, Ian Jackson wrote: > Package: debootstrap > Version: debootstrap/1.0.110~bpo9+1 > Severity: serious > > In #914208 Simon McVittie writes: >> [merge-/usr] is now the default in stretch-backports' debootstrap > > As discussed on debian-devel, however, binary packages built on a > merged-usr system are not installable on a non-merged-usr system. > Obviously we would like ad hoc builds of packages from one stretch > machine to be installable on other stretch machines. > > I do not see any way in which this could be resolved for stretch. > Accordingly, please urgently revert this change for stretch-backports. > AFAICT this is a dupe of 914897; closing. Cheers, Julien--- End Message ---
Bug#914897: debootstrap, buster: Please disabled merged /usr by default
On 11/28/18 1:07 PM, Ian Jackson wrote: > Package: debootstrap > Version: debootstrap/1.0.110 > Severity: serious > > Merged /usr is now the default in buster. As discussed on > debian-devel, however, binary packages built on a merged-usr system > are not installable on a non-merged-usr system. I think we would like > ad hoc builds of packages from one buster machine to be installable on > other buster machines. That is not compatible with the current > approach. > > This was an unanticipated problem. The discussion on -devel has not > reached a consensus on a way forward, and there is no transition plan. > > Accordingly, please revert this change for buster. > We already have a change queued to revert it for build chroots. I don't believe anything more is warranted at this stage. > IMO this revert should be done quickly, to minimise the number of > installs which will generate broken packages. If you do not agree > with my proposal, then I still think we should revert the change in > sid/buster while the matter is discussed. > > This affects stretch-backports too, but I think it will be most > convenient to file a separate bug for that. > Definitely not. Cheers, Julien
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Control: reassign -1 tech-ctte
Dear Technical Committee. I don't know if you are all aware of the
discussion surrounding this, so I will recap:
Recently debootstrap was changed to do merged-/usr by default, so that
/bin -> /usr/bin etc.
It was discovered that when this change took effect on the Debian
buildds, the buildds started to build packages which do not work on
non-merged-/usr systems.
This is a special case of a general problem: buster systems with
merged-/usr sometimes build packages which are broken on
non-merged-/usr systems.
Some people have suggested that this should be fixed by making
merged-/usr mandatory for buster. However, there is no transition
plan for this as yet and I don't think Debian is ready to commit to do
that.
So I believe that this change should be immediately reverted in sid
and buster, so that we do not prejudge the situation by increasing the
number of buster installs in the field which generate packages which
are broken on non-merged-/usr systemss.
I filed this bug against debootstrap but its maintainers do not agree:
Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
merged /usr by default"):
> We already have a change queued to revert it for build chroots. I don't
> believe anything more is warranted at this stage.
Obviously I disagree. I think the question is urgent. Please would
you rapidly overrule the debootstrap maintainers.
After we have ceased introducing new lossage we can have a proper
conversation about what the plan ought to be for buster and bullseye.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Processed: Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Processing control commands: > reassign -1 tech-ctte Bug #914897 [debootstrap] debootstrap, buster: Please disabled merged /usr by default Bug reassigned from package 'debootstrap' to 'tech-ctte'. Ignoring request to alter found versions of bug #914897 to the same values previously set Ignoring request to alter fixed versions of bug #914897 to the same values previously set -- 914897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Julien Cristau writes: > We already have a change queued to revert it for build chroots. I don't > believe anything more is warranted at this stage. Making the package behave differently on build chroots is adding a bug, not fixing one. Bjørn
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
On 11/28/18 2:49 PM, Ian Jackson wrote: > Recently debootstrap was changed to do merged-/usr by default, so that > /bin -> /usr/bin etc. > > It was discovered that when this change took effect on the Debian > buildds, the buildds started to build packages which do not work on > non-merged-/usr systems. > > This is a special case of a general problem: buster systems with > merged-/usr sometimes build packages which are broken on > non-merged-/usr systems. > > Some people have suggested that this should be fixed by making > merged-/usr mandatory for buster. However, there is no transition > plan for this as yet and I don't think Debian is ready to commit to do > that. > I'd suggest that this should be fixed by not shipping any packages that aren't built on buildds. Cheers, Julien
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
merged /usr by default"):
> On 11/28/18 2:49 PM, Ian Jackson wrote:
> > This is a special case of a general problem: buster systems with
> > merged-/usr sometimes build packages which are broken on
...
> I'd suggest that this should be fixed by not shipping any packages that
> aren't built on buildds.
It would be quite a radical departure for Debian to no longer support
"I built this package for my mate to install on their computer".
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
Hello,
On Wed, Nov 28, 2018 at 03:14:20PM +, Ian Jackson wrote:
> Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
> merged /usr by default"):
[...]
> > I'd suggest that this should be fixed by not shipping any packages that
> > aren't built on buildds.
>
> It would be quite a radical departure for Debian to no longer support
> "I built this package for my mate to install on their computer".
For the case of locally built binaries, bringing any problem
that usrmerge would hit to the light would be preferable.
eg. Consider the case of:
cat << EOF > /usr/local/bin/grep
#!/bin/sh
grep --color $@
EOF
chmod +x /usr/local/bin/grep
(Or export PATH=$HOME/bin:$PATH and something similar as above.)
I've certainly in my maintainer history had people demand fixes
for problems that where caused by their local build environment
setup containing alot crazier things than the above.
Regards,
Andreas Henriksson
PS. As previously mentioned reproducible builds has already been set up
to help catch issues so I don't understand the urgency, see:
https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html
Better ask release-team for permission to treat these as RC if you feel
strongly about these issues.
Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default
On 11/28/18 4:14 PM, Ian Jackson wrote:
> Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
> merged /usr by default"):
>> On 11/28/18 2:49 PM, Ian Jackson wrote:
>>> This is a special case of a general problem: buster systems with
>>> merged-/usr sometimes build packages which are broken on
> ...
>> I'd suggest that this should be fixed by not shipping any packages that
>> aren't built on buildds.
>
> It would be quite a radical departure for Debian to no longer support
> "I built this package for my mate to install on their computer".
>
It'll be just as "supported" as it is today (which is to say, basically
not at all). Likely to work in many cases, but also likely to explode
in a million pieces depending on the build environment. I'd just like
to stop inflicting this risk on people downloading debs from *.debian.org.
Cheers,
Julien
Bug#902215: marked as done (Installation Debian 10 Buster successfully on AMD A10 Desktop PC)
Your message dated Wed, 28 Nov 2018 18:45:36 +0100 with message-id <0b621552541ca3bce865580fa80bfb262c5d18f5.ca...@gmail.com> and subject line Installation was successfully has caused the Debian Bug report #902215, regarding Installation Debian 10 Buster successfully on AMD A10 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.) -- 902215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: USB-Stick Image version: Self-made ISO image with Debian 10 Alpha 3 Installer Date: 2018-06-23 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 1592320 0 15923200% /dev tmpfs tmpfs 32125648163164402% /run /dev/sda1 ext4 111556948 4954832 1008922925% / tmpfs tmpfs 16062723296 16029761% /dev/shm tmpfs tmpfs 5120 4 51161% /run/lock tmpfs tmpfs 1606272 0 16062720% /sys/fs/cgroup tmpfs tmpfs 321252 483212041% /run/user/1000 Output of lspci -knn: 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: ASUSTeK Computer Inc. FCH LPC Bridge [1043:8527]
Bug#902212: marked as done (Installation Debian 10 Buster successfully on Acer Aspire One)
Your message dated Wed, 28 Nov 2018 18:46:23 +0100 with message-id and subject line Installation was successfully has caused the Debian Bug report #902212, regarding Installation Debian 10 Buster successfully on Acer Aspire One 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.) -- 902212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: USB-Stick Image version: Self-made ISO image with Debian 10 Alpha 3 Installer Date: 2018-06-23 Machine: Acer Aspire One 532h Processor: Intel(R) Atom(TM) CPU N450 @ 1.66GHz Memory: 1GB Partitions: DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf udev devtmpfs497504 04975040% /dev tmpfs tmpfs 1015644504 970605% /run /dev/sda1 ext4 60255100 5416488 51748028 10% / tmpfs tmpfs 507816 05078160% /dev/shm tmpfs tmpfs 5120 4 51161% /run/lock tmpfs tmpfs 507816 05078160% /sys/fs/cgroup tmpfs tmpfs 101560 81015521% /run/user/1000 Output of lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge [1025:0349] 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1025:0349] Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1025:0349] 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family High Definition Audio Controller [1025:0349] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 02) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller [1025:0349] Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller [1025:0349] Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller [1025:0349] Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB UHCI Controller [1025:0349] Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family USB2 EHCI Controller [1025:0349] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) 00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller [8086:27bc] (rev 02) Subsystem: Acer Incorporated [ALI] NM10 Family LPC Controller [1025:0349] Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] [8086:27c1] (rev 02) Subsystem: Acer Incorporated [ALI] NM10/ICH7 Family SATA Controller [AHCI mode] [1025
Bug#895720: marked as done (Installation of Buster successfully at Asus UX501)
Your message dated Wed, 28 Nov 2018 18:47:04 +0100 with message-id <7c1d46d8b1bdfc382f297cc906cb6c7f6a525e96.ca...@gmail.com> and subject line Installation was successfully has caused the Debian Bug report #895720, regarding Installation of Buster successfully at Asus 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.) -- 895720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: installation-reports Boot method: USB Flash drive Image version: Self-made ISO image with current installer from testing Date: 2018-04-14 Machine: ASUS Zenbook 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 8144048 0 81440480% /dev > tmpfs tmpfs 16315729108 16224641% /run > /dev/sda1 ext4 106144480 5783648 949259526% / > tmpfs tmpfs 81578524960 81528921% /dev/shm > tmpfs tmpfs 5120 4 51161% /run/lock > tmpfs tmpfs 8157852 0 81578520% /sys/fs/cgroup > tmpfs tmpfs 1631568 20 16315481% /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 > Kernel modules: shpchp > 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 > Kernel modules: shpchp > 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 > Kernel modules: shpchp > 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 > Kernel modules: shpchp > 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 modul
Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer
Hi Alex, Cyril, and anyone else reading this, On Fri, Oct 12, 2018 at 10:09:48AM +0200, Cyril Brulebois wrote: > Hi, > > Alex Mestiashvili (2018-10-12): > > Fixed all the mentioned above issues in the repository. > > That's looking good indeed. > > Please note that by building a udeb you'll be subject to this once in a > while: > > https://lists.debian.org/debian-devel-announce/2014/08/msg3.html > > (That hasn't happened in a long while because I've been otherwise busy, > but I still hope to resume regular d-i releases at some point.) > > > Thank you for the detailed answer! > > No problem, always easier/happier to catch such issues before packages > reach the archive. ;) It seems libzstd 1.3.5+dfsg-2 hasn't yet reached the archive. Maybe it was not uploaded, or maybe it was rejected for some reason? https://salsa.debian.org/med-team/libzstd/commit/9b865b77d2bfc41c5865f255cf3e4aae18bbe934 Thanks you for working on this! Nicholas signature.asc Description: PGP signature
Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer
> It seems libzstd 1.3.5+dfsg-2 hasn't yet reached the archive. Maybe > it was not uploaded, or maybe it was rejected for some reason? > > > https://salsa.debian.org/med-team/libzstd/commit/9b865b77d2bfc41c5865f255cf3e4aae18bbe934 > > Thanks you for working on this! > Nicholas Hi Nicholas, it is in the new queue: https://ftp-master.debian.org/new/libzstd_1.3.5+dfsg-2.html We just need to wait or ?
