Your message dated Tue, 16 Feb 2016 22:57:29 +0100 with message-id <[email protected]> and subject line Re: Bug#814533: texlive-latex-extra: dpkg fails parsing package status has caused the Debian Bug report #814533, regarding texlive-latex-extra: dpkg fails parsing package status 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 [email protected] immediately.) -- 814533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814533 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: texlive-latex-extra Severity: normal Dear Maintainer, In an upgrade I tried to day on a Testing System I got the following during installation MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. dpkg: error: parsing file '/var/lib/dpkg/status' near line 14427 package 'texlive-latex-extra': newline in field name '!.' So I am reporting it. This was a normal aptitude install. Nothing special. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ################################## minimal input file ################################## other files ###################################### List of ls-R files -rw-r--r-- 1 alan alan 92 Nov 25 2012 /home/alan/texmf/ls-R -rw-r--r-- 1 root root 2772 Jan 24 19:23 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Oct 14 04:48 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Jan 17 08:55 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Jan 17 08:55 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ###################################### Config files -rw-r--r-- 1 root root 1101 Oct 22 07:50 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 7016 Oct 14 09:17 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Jan 17 08:55 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 2844 Jan 24 19:23 /var/lib/texmf/tex/generic/config/language.dat ###################################### Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Jan 9 2013 mktex.cnf -rw-r--r-- 1 root root 1101 Oct 22 07:50 texmf.cnf ###################################### md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-latex-extra is related to: ii tex-common 6.04 ii texlive-binaries 2015.20150524.37493-7+b1
--- End Message ---
--- Begin Message ---Hi! On Mon, 2016-02-15 at 09:39:49 +0100, Guillem Jover wrote: > On Sat, 2016-02-13 at 10:20:59 +0900, Norbert Preining wrote: > > > MySQL database support detected, but apparently missing Depends on > > > dbconfig-mysql packages. Please report this issue to the package > > > maintainer.. > > > MySQL database support detected, but apparently missing Depends on > > > dbconfig-mysql packages. Please report this issue to the package > > > maintainer.. > > > > Was this a message from dpkg *during* the configuration of > > texlive-latex-extra? > > We don't have anything sql related in our package, so this > > looks like a message from a different pacakge. > > > > > dpkg: error: parsing file '/var/lib/dpkg/status' near line 14427 package > > > 'texlive-latex-extra': > > > newline in field name '!.' > > > > This is a problem with dpkg, reassigning it. > > Did you edit that file by hand? Can you either provide the surrounding > lines around line 14427 from the status file, or if you have privacy > concerns given the packages that you have installed, could you send > the status file privately to me? > > Did you experience other strange things happening on the system, I > could suspect a problem in the hard disk, the file system or the RAM. > Please check your logs and do run a file system and memory checker > just to be sure. Alan mentioned off-BTS to have experienced abrupt shutdowns, so the most probable cause of this file damage was that. Closing now. Thanks, Guillem
--- End Message ---
