Your message dated Sat, 18 Apr 2020 14:07:11 -0400
with message-id 
<CA+ya19JMyzEgX+c8tcjdn-myWBBON98+GLYnmz=ms2qsgmv...@mail.gmail.com>
and subject line Re: Bug#933001: Acknowledgement (returns 1 to plymouth 
initramfs hook, breaks initramfs creation)
has caused the Debian Bug report #933001,
regarding returns 1 to plymouth initramfs hook, breaks initramfs creation
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.)


-- 
933001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig
Version: 2.13.1-2
Severity: grave

After recent upgrades, initramfs update fails here. When I patch
/usr/share/initramfs-tools/hooks/plymouth with "set -x", this is what we
get. And this error handling = NOT helpfull.

+ '[' n = y ']'
+ cp -pP /usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 
/var/tmp/mkinitramfs_n38cu7//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1
+ cp -a /usr/share/plymouth/themes/details 
/var/tmp/mkinitramfs_n38cu7//usr/share/plymouth/themes
+ cp -a /usr/share/plymouth/themes/text 
/var/tmp/mkinitramfs_n38cu7//usr/share/plymouth/themes
+ '[' -f /etc/os-release ']'
+ cp /etc/os-release /var/tmp/mkinitramfs_n38cu7/etc
+ case "${THEME_NAME}" in
+ cp /usr/share/plymouth/debian-logo.png 
/var/tmp/mkinitramfs_n38cu7/usr/share/plymouth
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/etc/fonts/conf.d
+ cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_n38cu7/etc/fonts
+ cp -rL /etc/fonts/conf.d/60-latin.conf 
/var/tmp/mkinitramfs_n38cu7/etc/fonts/conf.d
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/var/cache/fontconfig
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/usr/local/share/fonts
+ '[' -e /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf ']'
+ mkdir -p /var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
/var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
/var/tmp/mkinitramfs_n38cu7/usr/share/fonts/truetype/dejavu
+ fc-cache -s -y /var/tmp/mkinitramfs_n38cu7
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.2.2+ with 1.

Ok, trying more verbosity, still does not work. I expect
"--really-force" to fix everything, but it doesn't.

+ fc-cache --verbose --really-force -s -y /var/tmp/mkinitramfs_OYu7kU
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts: caching, new cache contents: 0 
fonts, 1 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype: caching, new cache 
contents: 0 fonts, 1 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype/dejavu: caching, new 
cache contents: 2 fonts, 0 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/X11R6/lib/X11/fonts: 
"/usr/X11R6/lib/X11/fonts": scanning error
[/var/tmp/mkinitramfs_OYu7kU]/usr/local/share/fonts: caching, new cache 
contents: 0 fonts, 0 dirs
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype: skipping, looped 
directory detected
[/var/tmp/mkinitramfs_OYu7kU]/usr/share/fonts/truetype/dejavu: skipping, looped 
directory detected
/var/tmp/mkinitramfs_OYu7kU//var/cache/fontconfig: cleaning cache directory
fc-cache: failed

And now? The used font does exist!

$ debsums fonts-dejavu-core
/usr/share/doc/fonts-dejavu-core/AUTHORS                                      OK
/usr/share/doc/fonts-dejavu-core/BUGS                                         OK
/usr/share/doc/fonts-dejavu-core/README.md                                    OK
/usr/share/doc/fonts-dejavu-core/changelog.Debian.gz                          OK
/usr/share/doc/fonts-dejavu-core/changelog.gz                                 OK
/usr/share/doc/fonts-dejavu-core/copyright                                    OK
/usr/share/doc/fonts-dejavu-core/langcover.txt.gz                             OK
/usr/share/doc/fonts-dejavu-core/status.txt.gz                                OK
/usr/share/doc/fonts-dejavu-core/unicover.txt.gz                              OK
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf                          OK
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf                               OK
/usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf                      OK
/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf                           OK
/usr/share/fonts/truetype/dejavu/DejaVuSerif-Bold.ttf                         OK
/usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf                              OK

EOF

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0+ (SMP w/12 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fontconfig depends on:
ii  fontconfig-config  2.13.1-2
ii  libc6              2.28-10
ii  libfontconfig1     2.13.1-2
ii  libfreetype6       2.9.1-4

fontconfig recommends no packages.

fontconfig suggests no packages.

-- no debconf information

--
<Rhonda> Im Amazon find ich nur englische Thesauren, das ist ja krank....
<Rhonda> ThesaurĂ¼sse?
<Rhonda> Ah! Thesauri.
<youam> Thesaurier?

--- End Message ---
--- Begin Message ---
Version: 2.13.1-3
X-Debbugs-CC: e...@gmx.de

Hi Eduard,

I believe this bug has been fixed with fontconfig 2.13.1-3. Could you
please try the new version and verify the fix is actually working?

Also I believe you could delete /usr/X11R6/lib/X11/fonts since it is
no longer useful.

-- 
Regards,
Boyuan Yang

--- End Message ---

Reply via email to