Bug#414321: Seems to miss conflict with emacs21-common 21.4a+1-3 (emacsclient.1emacs21.gz file conflict)
Package: emacs21-bin-common Version: 21.4a+1-4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The upgrade from 21.4a+1-3 failed, because it was tried to overwrite /usr/share/man/man1/emacsclient.1emacs21.gz, which is also in emacs21-common (<< 21.4a+1-4). apt-get install -f succeeded. So it seems, that only a versioned conflict is missing. Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.11 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages emacs21-bin-common depends on: ii emacs21-common 21.4a+1-4The GNU Emacs editor's shared, arc ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii liblockfile11.06.1 NFS-safe locking library, includes emacs21-bin-common recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF8zqcm0bx+wiPa4wRAmVWAKC7NakLWAAxvA+wturzG6rS9VjKVACfV7y1 IzX+77608VgeIducARJmSvg= =j+WU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#315780: update-xmlcatalog should support non-Debian-packaged
Hello, Some long time ago you wrote, > I'm trying to figure out how to integrate existing local catalogs, > installed on a distributed file system (AFS in my case, but it could > just as easily be NFS or SMB), with Debian's /etc/xml/catalog. > > The easiest (but maybe not the most robust) way would be to use a > element pointing to the catalog I'm already keeping on the > network share. Unfortunately, update-xmlcatalog only allows --type > (public|system|uri); I see no way to make it generate a > element (least of all in the root catalog, where I'd prefer to put it). > > My main reason for wanting support is that a number of XML > bundles out there ship with their own catalog.xml files, and it seems > easiest to just include them in this way. Any problems with expanding the XML_CATALOG_FILES environment variable (filenames, separated by colons or spaces IIRC)? You cna simply create you own catalog using the xmlcatalog utility and simply merge the Debian root catalog and your own catalog together by adding them both to the XML_CATALOG_FILES environment variable. Is this an solution to your problem? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414352: manpage lists --svn-noninteractive option twice
Package: svn-buildpackage Version: 0.6.16 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is just a minor bug. In the manpage, you have the description of the - --svn-noninteractive option twice. The second one seems to be a part copy of the first one, that was probably created/copied by accident. Should be easy to fix ;) Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.11 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages svn-buildpackage depends on: ii devscripts 2.9.27 Scripts to make the life of a Debi ii file4.19-1 Determines file type using "magic" ii libsvn-perl 1.4.2dfsg1-2 Perl bindings for Subversion ii perl5.8.8-7 Larry Wall's Practical Extraction ii subversion 1.4.2dfsg1-2 Advanced version control system ii wget1.10.2-2 retrieves files from the web svn-buildpackage recommends no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF863fm0bx+wiPa4wRAgASAJ9R3iUQ8Sqaagn0oDGnLwnBYkS00gCfX9kR uWuJ29DmmnGbkSXGCmrJC+g= =gUZt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414353: Please add option to allow removal of "orig-dir" before a build
Package: svn-buildpackage Version: 0.6.16 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Say, you want to build package foo-x.y. If there is already a directory foo-x.y in the buildArea, it is moved away: /usr/local/src/packages/foo/foo-x.y exists, renaming to /usr/local/src/packages/foo/foo-x.y.obsolete.0.515648078479902 I would like to request a switch, that removes the directory (not moves it out of the way). I would prefer this behaviour, because it doesn't leave many copies of the source (in my case, almost identical copies, because I build with pdebuild) in the buildArea. Thanks and regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.11 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages svn-buildpackage depends on: ii devscripts 2.9.27 Scripts to make the life of a Debi ii file4.19-1 Determines file type using "magic" ii libsvn-perl 1.4.2dfsg1-2 Perl bindings for Subversion ii perl5.8.8-7 Larry Wall's Practical Extraction ii subversion 1.4.2dfsg1-2 Advanced version control system ii wget1.10.2-2 retrieves files from the web svn-buildpackage recommends no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF87AFm0bx+wiPa4wRAtRVAJwPWxwlM4mcbPoFGe1XoZr97eNaggCfZQ7O EP1kxLLjvvGaOq40o9tQ0Jw= =d5Zy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414261: Added .desktop file
Am Samstag, den 10.03.2007, 14:15 +0100 schrieb Luca Falavigna: > Please find attached a debdiff implementing this. > Thank you. > einfaches Textdokument-Anlage (xawtv_3.95.dfsg.1-3.debdiff) > diff -Nru xawtv-3.95.dfsg.1/debian/changelog > xawtv-3.95.dfsg.1/debian/changelog > --- xawtv-3.95.dfsg.1/debian/changelog2007-03-10 14:13:19.0 > +0100 > +++ xawtv-3.95.dfsg.1/debian/changelog2007-03-10 14:13:20.0 > +0100 > @@ -1,3 +1,9 @@ > +xawtv (3.95.dfsg.1-3) unstable; urgency=low > + > + * Added .desktop file > + > + -- Luca Falavigna <[EMAIL PROTECTED]> Sat, 10 Mar 2007 14:11:02 +0100 > + > xawtv (3.95.dfsg.1-2) unstable; urgency=low > >* QA upload. > diff -Nru xawtv-3.95.dfsg.1/debian/rules xawtv-3.95.dfsg.1/debian/rules > --- xawtv-3.95.dfsg.1/debian/rules2007-03-10 14:13:19.0 +0100 > +++ xawtv-3.95.dfsg.1/debian/rules2007-03-10 14:13:20.0 +0100 > @@ -50,6 +50,10 @@ > echo "v4l-conf: setuid-binary" \ > > debian/v4l-conf/usr/share/lintian/overrides/v4l-conf > > + # install desktop file > + install -d $(CURDIR)/debian/xawtv/usr/share/applications > + install -m 644 debian/xawtv.desktop > $(CURDIR)/debian/xawtv/usr/share/applications > + > binary-indep: build install > > binary-arch: build install > diff -Nru xawtv-3.95.dfsg.1/debian/xawtv.desktop > xawtv-3.95.dfsg.1/debian/xawtv.desktop > --- xawtv-3.95.dfsg.1/debian/xawtv.desktop1970-01-01 01:00:00.0 > +0100 > +++ xawtv-3.95.dfsg.1/debian/xawtv.desktop2007-03-10 14:13:20.0 > +0100 > @@ -0,0 +1,18 @@ > +[Desktop Entry] > +Comment=TV viewer for X11 > +NoDisplay=false > +Name=XawTV > +Encoding=UTF-8 > +Exec=xawtv > +Terminal=false > +GenericName=XawTV > +Comment[en_GB]=TV extensions for X11 > +Comment[en_US]=TV extensions for X11 > +Icon[en_GB]=/usr/share/pixmaps/gnome-term-linux2.png > +Icon[en_US]=/usr/share/pixmaps/gnome-term-linux2.png > +Hidden=false > +Name[en_GB]=XawTV > +Name[en_US]=XawTV > +Type=Application > +Categories=Applications;AudioVideo > +Icon=/usr/share/pixmaps/gnome-term-linux2.png Please note, that "Applications" is not a valid category (obsolete category of GNOME, not valid in the freedesktop.org standard) and every category must be followed by a semicolon. You can easily check with the desktop-file-validate tool for such issues. JFTR: I would also remove the Hidden and NoDisplay fields and the localized (en_*) Comment, Icon and Name fields. They seem a bit useless here. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414541: Newer version available (20050304)
Package: ldp-docbook-xsl Version: 0.0.20040321-2 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is a newer version available at http://www.happy-monkey.net/docbook/tldp/. This also seems to be the homepage (following http://en.tldp.org/authors/index.html, the URL in the copyright file). Maybe it could be updated (as part of the Debian XML/SGML group). Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.11 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages ldp-docbook-xsl depends on: ii docbook-xsl 1.72.0.dfsg.1-1 stylesheets for processing DocBook ldp-docbook-xsl recommends no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9T+Hm0bx+wiPa4wRAjp9AKCpNpbXQll2nYU8ugKYYN4BKCgPjQCglalX j7/ytdnM8JMp5aDkeaqvJvA= =GjiC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414547: Shouldn't copy unversionned files
Am Montag, den 12.03.2007, 14:04 +0100 schrieb Loïc Minier: > Package: svn-buildpackage > Version: 0.6.16.1 > Severity: important > > Hi, > > svn-buildpackage copies unversionned files when building packages, that > is files marked as '?' by subversion; this made me include files I > didn't want to ship in the package yet. I'm using svn-ignore-new mode > if that makes any difference. Personally I see this as feature. So I can test, without the necessity to move files untested under version control. So I would like to request, to allow both behaviours. Regards, Daniel
Bug#414547: Shouldn't copy unversionned files
Am Dienstag, den 13.03.2007, 10:21 +0100 schrieb Loïc Minier: > On Tue, Mar 13, 2007, Daniel Leidert wrote: > > Personally I see this as feature. So I can test, without the necessity > > to move files untested under version control. So I would like to > > request, to allow both behaviours. > > I do the same usage as you do. There are three types of files: > - files under version control and unchanged in the WC; these do not >appear in svn status -- these are committed > - files under version control but changed in the WC (added files, >modified files, removed files...); these appear in svn status as "A" >"M" or "D" etc. -- these are not committed > - files not under version control, such as new files which were not svn >added; these appear as "?" in svn status -- these wont be committed > > I know of two types of usage of svn-buildpackage: > - Joss in the GNOME team commits files, and then tests the build; >this often results in more commits, especially with commits fixing >the previous commits > - I personally change files, svn add or svn rm them, do a test build, >and then do the commit; I set svn-ignore-new in >.svn-buildpackage.conf for this to be allowed I see ... > What I don't like it the handling of the third type of files; these > files should not ever be considered by svn-buildpackages since these > are not in SVN. If you don't plan to add these to the SVN, why would > you build with these files? > > Are you advocating for an option to still be able to build with these > files, the '?' files? Well, I sometimes used to do that. But you are right. You can put files under version control without committing them and you can still test them. This is enough I need. So if it's more intentional to not consider unversioned files for a build, I support your request. So I can finally put my personal TODO files in the SVN directories too :) Regards, Daniel
Bug#415288: CVE-2007-0002 Multiple Buffer Overflow Vulnerabilities
Package: libwpd8c2a Version: 0.8.7-5 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There seem to be multiple buffer overflow vulnerabilities: http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=490 I read the package changelog and it seems, the issues were not addressed yet. I initially set the severity to important. Please adjust it if necessary. Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.11 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages libwpd8c2a depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-21 GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 libwpd8c2a recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/GSDm0bx+wiPa4wRAu1rAJ47TRS2edrphWEKXsbdZv1Ro0XSpgCfReJD lYYdRRvVrDFSc0hiXB9Zt1s= =9NH/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415468: aptitude: Manpages unreadable
tags 415468 + patch thanks Am Montag, den 19.03.2007, 20:54 +0100 schrieb Florentin Duneau: > The aptitude manpages (en, fr for example) are wrongly generated. See > below the english manpage: Change the literal matching template to: Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415488: docbook-xsl: broken stylesheets for nroff
retitle 415488 Unwanted substitution of '\' in groff escape sequences severity 415488 minor tags 415488 + fixed-upstream tags 415488 - patch unblock 415468 by 415488 thanks This issue isn't a blocker. I provided a working patch for bug #415468. It is also not a bug (see manpages/utility.xsl -> bold/italic mode templates - for how to correctly do it with docbook-xsl 1.72.0). There has been a change to escape backslashes, dots and dashes. This change makes it necessary to escape them in elements too. But it has been reverted recently in upstream VCS. So I will leave this report open until a new docbook-xsl version has been released. But I downgraded severity. For the moment, use the workaround I supplied and escape backslashes in elements, if you need them there. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408483: /etc/logcheck/ignore.workstation.d should be /etc/logcheck/ignore.d.workstation (IMO)
Package: debarchiver Version: 0.7.0 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 debarchiver installs a logcheck file into /etc/logcheck/ignore.workstation.d, where it is the only package, that installs the file to this place. All other applications seem to install their files into /etc/logcheck/ignore.d.workstation instead. I didn't test, if the chosen directory has a negative effect. Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.08070117 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages debarchiver depends on: ii adduser 3.102 Add and remove users and groups ii apt-utils 0.6.46.4 APT utility programs ii dpkg-dev 1.13.25package building tools for Debian ii opalmod 0.1.14 A set of Perl modules for various debarchiver recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFuZQVm0bx+wiPa4wRAi6JAKCwjBeJ7Ge9ZGvU0TOrtHA39Dft8ACdEf/E uCmUs+1tXI8KsUZ8Yuij3Rs= =1uEn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408826: shared-mime-info: identify dpatch files as diff
Am Sonntag, den 28.01.2007, 16:30 +0100 schrieb Fabian Greffrath: > package: shared-mime-info > version: 0.19-1 > severity: wishlist > tags: patch > > Hi! > > Please make dpatch-files (or actually all files ending on .dpatch) being > recognized as diff-files. See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386492. > A trivial patch could be: > --- /usr/share/mime/packages/freedesktop.org.xml 2007-01-28 > 16:27:15.0 +0100 > +++ /usr/share/mime/packages/freedesktop.org.xml 2007-01-28 > 16:27:53.0 +0100 > @@ -12835,6 +12835,7 @@ > > > > + > > > But I'm not sure, if .doatch files should really be added to text/x-patch. Maybe a subtype text/x-dpatch, that is a sub-class-of text/x-patch would be better. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408574: deskbar-applet.pc defines dependency on python-gtk2-dev the package misses (was: pkg-config --variable broken=
reassign 408574 deskbar-applet 2.14.2-4.2 retitle 408574 deskbar-applet.pc defines dependency on python-gtk2-dev the package misses severity 408574 serious thanks Does a pkg-config --print-errors --variable handlersdir deskbar-applet give you any output? I get: $ pkg-config --print-errors --variable handlersdir deskbar-applet Package pygtk-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `pygtk-2.0.pc' to the PKG_CONFIG_PATH environment variable Package 'pygtk-2.0', required by 'Deskbar Applet Handlers Location', not found and that's why there is no output. That's a bug in the deskbar-applet package, that defines a dependency via pkg-config file, but not via Debian package dependencies. This bug should be reassigned to deskbar-applet. You can workaround the issue temporarily by installing/defining a dependency to python-gtk2-dev for the package you want to build. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398434: pkg-config.1 formatting error
Package: pkg-config Version: 0.21-1 Followup-For: Bug #398434 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tags 398434 + patch thanks I've attached a simple patch to fix this issue. Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.08070117 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages pkg-config depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries pkg-config recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFw/7/m0bx+wiPa4wRAm9rAJ977V1+OOF/VT0vqh31TFS8rUP8qACfRgyt 9IqHOGAt7ZETEZDQg+8It5s= =1Yet -END PGP SIGNATURE- --- pkg-config.1.bk 2006-08-16 19:38:33.0 +0200 +++ pkg-config.12007-02-03 03:44:50.0 +0100 @@ -304,12 +304,14 @@ Note that if there is a possibility the PKG_CHECK_MODULES might not happen, you should be sure to include an explicit call to PKG_PROG_PKG_CONFIG in your configure.ac +.TP .I "PKG_PROG_PKG_CONFIG([MIN-VERSION])" Defines the PKG_CONFIG variable to the best pkg-config available, useful if you need pkg-config but don't want to use PKG_CHECK_MODULES. -.I "PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])" +.TP +.I "PKG_CHECK_EXISTS(MODULES,[ACTION-IF-FOUND],[ACTION-IF-NOT-FOUND])" Check to see whether a particular set of modules exists. Similar to PKG_CHECK_MODULES(), but does not set variables or print errors.
Bug#403854: Requires.private is broken
Hello, This is probably a duplicate of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390132. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409524: FTBFS: illegal input sequence at position 1323
Am Samstag, den 03.02.2007, 20:25 +0100 schrieb Martin Michlmayr: > Package: docbook2x > Version: 0.8.3-1 > Severity: serious > Tags: sid > > This package fails to build in sid (but not in etch): > > > Automatic build of docbook2x_0.8.3-1 on em64t by sbuild/amd64 0.52 > ... > > Build started at 20070201-0709 > > ** [..] > > make[2]: Entering directory `/build/tbm/docbook2x-0.8.3/doc' > > ../libxslt/db2x_xsltproc -C ../xslt/catalog.xml -s ./ss-texinfo.xsl -o > > docbook2X.txml docbook2X.xml > > I/O error : Attempt to load network entity > > http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd > > /usr/bin/perl -I../perl ../perl/db2x_texixml > > --utf8trans-program=../utf8trans/utf8trans > > --utf8trans-map=../charmaps/texi.charmap docbook2X.txml > > /usr/bin/iconv: illegal input sequence at position 1323 > > makeinfo docbook2X.texi > > docbook2X.texi:38: No matching [EMAIL PROTECTED] detailmenu'. > > docbook2X.texi:23: No matching [EMAIL PROTECTED] menu'. > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:8: Next reference to > > nonexistent node `Quick start' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:36: Menu reference to > > nonexistent node `Concept index' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:35: Menu reference to > > nonexistent node `Package installation' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:33: Menu reference to > > nonexistent node `Design notes' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:32: Menu reference to > > nonexistent node `Release history' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:31: Menu reference to > > nonexistent node `Todo' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:30: Menu reference to > > nonexistent node `FAQ' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:28: Menu reference to > > nonexistent node `Charset considerations' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:27: Menu reference to > > nonexistent node `The XSLT processor' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:26: Menu reference to > > nonexistent node `Converting to Texinfo' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:25: Menu reference to > > nonexistent node `Converting to man pages' (perhaps incorrect sectioning?). > > /build/tbm/docbook2x-0.8.3/doc//docbook2X.texi:24: Menu reference to > > nonexistent node `Quick start' (perhaps incorrect sectioning?). > > makeinfo: Removing output file > > `/build/tbm/docbook2x-0.8.3/doc/docbook2X.info' due to errors; use --force > > to preserve. > > make[2]: *** [docbook2X.info] Error 1 Adding an '--encoding=utf-8' to the command line in doc/Makefile(.in|.am) or adding libxml-sax-expat-perl to build dependencies seems to solve the problem. I guess, there are changes in the libxml-sax-perl version in Sid, that make the build break. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292046: New version of docbook2x out
I will try to update the package to 0.8.7 in the near future. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409660: test: German translation of the manpage does not document -h switch
Package: manpages-de Version: 0.5-2 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The test(1) manpage contains: -h FILE FILE exists and is a symbolic link (same as -L) But the German tramslation misses to document this switch. Regards, Daniel - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.08070117 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFxgWFm0bx+wiPa4wRAhWrAJ95ycqzv+0UAtsTUwbWfpFgh/SHvQCfRj+Z jAbdgof6bRjmpzyCs+wYQlk= =cVZk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409816: libxslt1.1: error returned when parsing pages using 'exsl:node-set()'
Am Montag, den 05.02.2007, 12:05 -0600 schrieb Chris Jenkins: > When using libxslt1.1 with most recent libxml2, we're getting the > following error when attempting to parse a stylesheet using exsl > functions: "xmlXPathCompOpEval: function node-set bound to undefined > prefix exsl" Sure, that you defined the prefix? > I can't pinpoint when this broke, but it has been going on for a > number of releases now. I can say for sure it worked properly in > libxslt1.1_1.1.12-8_i386.deb, as that is the release we are currently > frozen at until it can be fixed. I cannot reproduce the problem. All my stylesheets using exsl work (recent Sid, same arch). Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#417465: FTBFS with GCC 4.3: missing #includes
tags 417465 + patch thanks Hi Michael, For the recently released 2.1.0 version, Jean Bréfort wrote a patch to fix all problems with GCC 4.3. See http://jean.brefort.free.fr/openbabel-2.1.patch. Regards, Daniel
Bug#292046: [xml/sgml-pkgs] Bug#292046: New version of docbook2x out
Am Dienstag, den 10.04.2007, 18:01 +0200 schrieb Rafael Laboissiere: > * Daniel Leidert <[EMAIL PROTECTED]> [2007-02-04 01:01]: > > > I will try to update the package to 0.8.7 in the near future. > > Shouldn't we upload 0.8.7 to unstable, now that etch is released? 0.8.8 has already been released. This can go into unstable. I think, I can do this during this week. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382505: fo output does not respect /etc/papersize
Just as a pointer for myself: Much easier than any XInclude solution: &papersize; And then we can evaluate the my.papersize variable. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418703: [xml/sgml-pkgs] Bug#418703: docbook2x: fails to build a manpage (used to work)
Am Mittwoch, den 11.04.2007, 13:39 +0200 schrieb Ondrej Certik: > Package: docbook2x > Version: 0.8.3-1 > Severity: grave > Justification: renders package unusable > > [EMAIL PROTECTED]:~/sympy$ docbook2x-man doc/man/isympy.xml > I/O error : Attempt to load network entity > http://docbook2x.sf.net/latest/xslt/man/docbook.xsl > warning: failed to load external entity > "http://docbook2x.sf.net/latest/xslt/man/docbook.xsl"; > cannot parse http://docbook2x.sf.net/latest/xslt/man/docbook.xsl > Ran out of memory for input buffer at /usr/lib/perl5/XML/Parser/Expat.pm line > 469. Sounds like a catalog problem. I guess, we simply need to register the XML catalog (as already noted in TODO.Debian) to solve this problem. I will check today and upload a fix asap. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362066: xf86cfg mentioned in description but not included in package
Am Mittwoch, den 11.04.2007, 21:44 +0200 schrieb Brice Goglin: > I just fixed the description in our git repo, this bug will be fixed by > next upload of 1:7.2 Thanks for taking care of this small issue. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418846: Manpage issues
Package: svn-buildpackage Version: 0.6.18 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The manpage(s) contain a few issues: * Options are not separated: [..] --svn-lintian--svn-linda [..] [..] --svn-prebuild--svn-postbuild--svn-pretag--svn-posttag [..] * The manpage contains two sections called "OPTIONS". But the first probably should be "DESCRIPTION". * The options mentioned in "OPTIONS" (in both sections) probably should also be bold to emphasize them: e.g. in [..] option may break --svn-lintian, --svn-linda and --svn-move functionality [..] the options ishould be bold too to emphasize them. * Further the manpage references in "SEE ALSO" do not follow the manpage recommendations, that say, that the referenced refentry should be bold (refer to http://www.schweikhardt.net/man_page_howto.html#q3 -> "The SEE ALSO section" and http://www.schweikhardt.net/man_page_howto.html#q8 -> "Any reference to another man page [..]"). * The "AUTHOR" sections contains an invalid UTF-8 character ( to SGML by Gonéri Le Bouder). You should try to use the groff code for this character. I'm not familar with the docbook-utils package, that seems to be used to create the manpages. The docbook-xsl stylesheets provide the following parameters to fix some of these issues: /usr/share/doc/docbook-xsl-doc-html/doc/manpages/variablelist.term.separator.html /usr/share/doc/docbook-xsl-doc-html/doc/manpages/variablelist.term.break.after.html (define handling of option lists realized with the variablelist element) /usr/share/doc/docbook-xsl-doc-html/doc/manpages/man.charmap.use.subset.html (set to zero to escape all UTF-8 characters) The docbook-xsl package contains an example of a manpage written in DocBook XML, that shows the current power and usage of DocBook to write manpages. Regards, Daniel - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18.11 (PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages svn-buildpackage depends on: ii devscripts 2.10.2 Scripts to make the life of a Debi ii file4.20-4 Determines file type using "magic" ii libsvn-perl 1.4.2dfsg1-2 Perl bindings for Subversion ii perl5.8.8-7 Larry Wall's Practical Extraction ii subversion 1.4.2dfsg1-2 Advanced version control system ii unp 1.0.12 unpack (almost) everything with on ii wget1.10.2-2 retrieves files from the web svn-buildpackage recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGHgSxm0bx+wiPa4wRAqykAJ4q/nOfbBdy1CbO9l27P3YgV2x5XgCg1OM5 OlX0+mQtC4XUO5IsbCFbP9o= =3qkg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418847: Perl prints out warnings
Package: svn-buildpackage Version: 0.6.18 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see the following warnings when working with the current svn-buildpackage version (reportbug times out when trying to check for a new version, so please excuse, if a new version is already up, that fixes these warnings): $ svn-buildpackage --svn-ignore "my" variable %tmp masks earlier declaration in same scope at /usr/bin/svn-buildpackage line 396 (#1) "my" variable $ctx masks earlier declaration in same scope at /usr/bin/svn-buildpackage line 398 (#1) Use of uninitialized value in exit at /usr/share/svn-buildpackage/SDCommon.pm line 272, line 1 (#2) Regards, Daniel - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18.11 (PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages svn-buildpackage depends on: ii devscripts 2.10.2 Scripts to make the life of a Debi ii file4.20-4 Determines file type using "magic" ii libsvn-perl 1.4.2dfsg1-2 Perl bindings for Subversion ii perl5.8.8-7 Larry Wall's Practical Extraction ii subversion 1.4.2dfsg1-2 Advanced version control system ii unp 1.0.12 unpack (almost) everything with on ii wget1.10.2-2 retrieves files from the web svn-buildpackage recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGHgVrm0bx+wiPa4wRAgpGAKDNYYvGYciM4gk16MYFa6+aAS2qmQCgk3Mx okRdWebvlUUgQ5/MiuiJpwA= =QMOK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418703: docbook2x: fails to build a manpage (used to work)
tags 418703 + pending thanks Hi, I found the problem and another grave issue. Fixes are on their way. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419279: Newer upstream version available
Package: cvschangelogbuilder Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is a newer upstream version available since a while. The latest stable release is 2.3 and a development release 2.4 is available too. Any plans to update the package? Regards, Daniel - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18.11 (PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages cvschangelogbuilder depends on: ii cvs 1:1.12.13-8 Concurrent Versions System ii perl 5.8.8-7 Larry Wall's Practical Extraction cvschangelogbuilder recommends no packages. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGITbMm0bx+wiPa4wRAqLtAJ0ZrjDlz0aoNg1kV770VefkKv9QTACgonfS SQzD/e+Tf85/jvxvdcGdueg= =J/SO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419461: [checks/scripts] Add maintainer-script-needs-depends-on-xml-core check
Package: lintian
Version: 1.23.29
Severity: wishlist
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to request a template
maintainer-script-needs-depends-on-xml-core to check for an xml-core
dependency if the maintainer-script calls update-xmlcatalog. Missing
this dependency appeared several times (probably only for me :)), so I
would like to request this check. To add it, simply add a
[ 'xml-core' => '\bupdate-xmlcatalog\b' ],
to @depends_needed in /usr/share/lintian/checks/scripts and
Tag: maintainer-script-needs-depends-on-xml-core
Type: error
Info: This script calls update-xmlcatalog, which comes from the xml-core
package, but does not depend or pre-depend on xml-core. Packages that call
update-xmlcatalog need to depend on xml-core. If you are using
dh_installxmlcatalogs, add a dependency on ${misc:Depends} and
dh_installxmlcatalogs will take care of this for you.
to /usr/share/lintian/checks/scripts.desc.
Just to prove, that it happens to miss the dependency (yes, shame on me,
both my faults):
http://bugs.debian.org/382576
http://bugs.debian.org/419419
Thanks and regards, Daniel
- -- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.11 (PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages lintian depends on:
ii binutils 2.17-3The GNU assembler, linker and bina
ii diffstat 1.43-2produces graph of changes introduc
ii dpkg-dev 1.13.25 package building tools for Debian
ii file 4.20-4Determines file type using "magic"
ii gettext0.16.1-1 GNU Internationalization utilities
ii intltool-debian0.35.0+20060710.1 Help i18n of RFC822 compliant conf
ii libparse-debianchangel 1.0-1 parse Debian changelogs and output
ii man-db 2.4.4-2 The on-line manual pager
ii perl [libdigest-md5-pe 5.8.8-7 Larry Wall's Practical Extraction
lintian recommends no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGIoQ9m0bx+wiPa4wRAh4DAJ458WDzGDPNsG3R4rrbYeZQ+XZZ9gCg2Nrz
SUnSHefVY3QdUpvLX/Ve/S4=
=EtLz
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418338: fglrx-driver: Xorg crashes when shutting down
severity 418338 important thanks Am Montag, den 09.04.2007, 08:29 +0200 schrieb sECuRE: > Package: fglrx-driver > Version: 8.28.8-4 > Severity: critical > Justification: breaks the whole system > > When running Xorg (via gdm or startx), there is no problem. fglrx runs as > expected. However, when > shutting down Xorg via Ctrl+Alt+Backspace or when shutting down, the system > just freezes. That means, > there is no monitor output anymore, it does not reboot properly, not pingable > and no SSH-Login > available. This is IMO not a critical, but important (maybe grave) bug and kind of a duplicate of #345040. See especially http://ati.cchtml.com/show_bug.cgi?id=239#c15 for a workaround. Does it help? @Flavio: Please upgrade severity again, if you disagree. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295579: any news on ITA: docbook-defguide ?
Am Montag, den 16.04.2007, 23:30 +0100 schrieb Neil Williams: > > thanks > > > > I'm going to adopt these packages as part of the Debian XML/SGML > > group. Let's see, if we can put the latest version into Etch. > > > > Regards, Daniel > > Umm, Etch is out and this bug is still open. > > Any news on packaging the updated upstream release? Yes, the recognition, that the build systems of the version in Debian and the latest upstream version are different and that there was no way to make the update happen for Etch. I locally "compiled" the package with xsltproc. But for a fully featured update, a new docbook-xsl-java package is necessary, because several elements are not fully supported by the XSLT processors we have in Debian. But the source for this package was not yet officially released seprataely and I would like to use this separate source. Discussion with upstream, respectively Michael Smith, has already been done. Making a pdf also fails atm because of bugs in the involved packages. And at least, it may also be possible to simply ship the ready-to-use html files instead of self-creating these files to workaround the above "issues". If this is just a ping, if I'm active, then: Yes, I'm still actively working to solve this bug. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419461: [checks/scripts] Add maintainer-script-needs-depends-on-xml-core check
Am Sonntag, den 15.04.2007, 21:59 +0200 schrieb Daniel Leidert:
> I would like to request a template
> maintainer-script-needs-depends-on-xml-core to check for an xml-core
> dependency if the maintainer-script calls update-xmlcatalog. Missing
> this dependency appeared several times (probably only for me :)), so I
> would like to request this check. To add it, simply add a
>
> [ 'xml-core' => '\bupdate-xmlcatalog\b' ],
>
> to @depends_needed in /usr/share/lintian/checks/scripts and
>
> Tag: maintainer-script-needs-depends-on-xml-core
> Type: error
> Info: This script calls update-xmlcatalog, which comes from the xml-core
>package, but does not depend or pre-depend on xml-core. Packages that call
>update-xmlcatalog need to depend on xml-core. If you are using
>dh_installxmlcatalogs, add a dependency on ${misc:Depends} and
>dh_installxmlcatalogs will take care of this for you.
>
> to /usr/share/lintian/checks/scripts.desc.
I found one issue with my suggestion: xml-core itself provides
update-xmlcatalog and also installs catalogs using this tool. But of
course cannot depend on itself. But the suggested check would make this
necessary to avoid an error :) Maybe the check should contain an
unless (($pkg eq $package) || ...
at the start too, to make sure, we don't try to check for a dependency
on ourselves.
Regards, Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#182445: ITP: xmlroff -- XSL Formatter
Hi, What is the current state of the ITP of xmlroff, Oliver? What is the current state of your intention to package it as part of the XML/SGML group, Wolfgang? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420153: [xml/sgml-pkgs] Bug#420153: docbook2x: line breaks mess up man page file names
tags 420153 + patch thanks Am Freitag, den 20.04.2007, 15:18 +0200 schrieb Daniel Leidert: > Am Freitag, den 20.04.2007, 13:23 +0200 schrieb Peter Eisentraut: > > > This broke between 0.8.8-1 and -2 and is still broken in -3. > > Hmm. I only registered the catalogs and fixed the broken paths between > 0.8.8-1 and -2. There was no change regarding the processing of XML > sources. BTW: 0.8.8-1 failed to work. How did it work for you? It had > broken paths in it's binaries, that couldn't be resolved (see #418703). > I guess, the problem was introduced between 0.8.3 and 0.8.8. Could you > please be so kind to check this? > > > The slony package contains several man pages affected by this problem. > > For example: > > > > MERGE > > SET7 > > > > In -1, this correctly created a man page file name "MERGE_SET.7". In -2, > > this creates "MERGE _SET.7". I think this is both useless and in > > violation of SGML whitespacing rules, so it probably ought to be reverted. > > Confirmed. I will check, where this comes from. Found it (manpage-filename template in xslt/man/manpage.xsl and the refentry-filename template in xslt/man/refentry.xsl and a possible fix. I sent a mail to Steve Cheng to discuss the solution with him. The fix will be uploaded after we have come to a conclusion. For the meantime, you can add the attached dpatch patch to a local docbook2x build to test it. Regards, Daniel 90_420153.dpatch Description: application/shellscript
Bug#420153: [xml/sgml-pkgs] Bug#420153: docbook2x: line breaks mess up man page file names
tags 420153 + confirmed thanks Am Freitag, den 20.04.2007, 13:23 +0200 schrieb Peter Eisentraut: > This broke between 0.8.8-1 and -2 and is still broken in -3. Hmm. I only registered the catalogs and fixed the broken paths between 0.8.8-1 and -2. There was no change regarding the processing of XML sources. BTW: 0.8.8-1 failed to work. How did it work for you? It had broken paths in it's binaries, that couldn't be resolved (see #418703). I guess, the problem was introduced between 0.8.3 and 0.8.8. Could you please be so kind to check this? > The slony package contains several man pages affected by this problem. > For example: > > MERGE > SET7 > > In -1, this correctly created a man page file name "MERGE_SET.7". In -2, > this creates "MERGE _SET.7". I think this is both useless and in > violation of SGML whitespacing rules, so it probably ought to be reverted. Confirmed. I will check, where this comes from. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420153: [xml/sgml-pkgs] Bug#420153: docbook2x: line breaks mess up man page file names
tags 420153 + pending thanks Am Freitag, den 20.04.2007, 15:59 +0200 schrieb Peter Eisentraut: > Am Freitag, 20. April 2007 15:18 schrieb Daniel Leidert: > > sources. BTW: 0.8.8-1 failed to work. How did it work for you? It had > > broken paths in it's binaries, that couldn't be resolved (see #418703). > > I guess, the problem was introduced between 0.8.3 and 0.8.8. Could you > > please be so kind to check this? > > You are right, it changed from 0.8.3. > > I also had to add xsltproc to the built dependencies. This wasn't > necessarily > earlier either. Yes. The package build fails, if xsltproc is not available. FYI: The package is waiting to be uploaded by my sponsor and available today or tomorrow. Steve Cheng agreed to the proposed solution. So your example will create a file called MERGE_SET.7 as expected in your OP. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420153: [xml/sgml-pkgs] Bug#420153: docbook2x: line breaks mess up man page file names
Am Samstag, den 21.04.2007, 16:13 +0200 schrieb Peter Eisentraut: > Daniel Leidert wrote: > > > I also had to add xsltproc to the built dependencies. This wasn't > > > necessarily earlier either. > > > > Yes. The package build fails, if xsltproc is not available. > > What I meant was that xsltproc apparently somehow used to be a > dependency of docbook2x. That is how it should be, since db2x_xsltproc > requires it. With 0.8.8 I had to add xsltproc to the build > dependencies of my package explicitly. That doesn't seem right. Ah, now I understand it. Seems, the xsltproc-dependency is missing. Added it too to -4 (and the other missing) Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420345: [xml/sgml-pkgs] Bug#420345: docbook2x: docbook2x-man fails in a clean chroot
tags 420345 + pending thanks Am Samstag, den 21.04.2007, 20:06 +0200 schrieb Adeodato Simó: > Hello. Installing the new version of docbook2x in a clean chroot yields an > unfunctional package: > > % docbook2x-man foo.docbook > /usr/bin/db2x_xsltproc: could not execute /usr/bin/xsltproc > /usr/bin/db2x_xsltproc: cannot use this XSLT processor --- try another one. > Ran out of memory for input buffer at /usr/lib/perl5/XML/Parser/Expat.pm > line 469. > > One would say a dependency on xsltproc is missing. The one would be right. > This is making some packages FTBFS. I know. Peter Eisentraut already reported it to me and -4 will fix this issue too (it's just waiting to be uploaded by my sponsor). Regards, Daniel
Bug#420174: Cannot Login to X server: module mismatch
Am Freitag, den 20.04.2007, 10:31 -0400 schrieb Carlos Moffat: > Package: fglrx-driver > Version: 8.28.8-4 > Severity: important > > --- Please enter the report below this line. --- > > After yesterday's update of xserver-xorg-core, I cannot longer login to > X, due to a module version mismatch. I believe this is due to > fglrx-driver. Switching to the radeon driver or (as I did) downgrading > xserver-xorg-core from snapshot.debian.net 'solved' the problem. It hits all fglrx-driver versions, including the latest 8.36.5 release. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420733: Place to save notes has changed - please mention it somewhere
Package: xfce4-notes-plugin
Version: 1.4.1-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After the update I found, that my notes were empty. Grepping through
.config/xfce4 showed, that the notes were saved in
${HOME}/.config/xfce4/panel/xfce4-notes-plugin-11705473010.rc
I copied my notes from this file into the notes-window, grepped again
and found, that the notes are now saved in:
${HOME}/.config/xfce4/panel/notes.rc:
I would expect a note about this (NEWS.Debian) or a conversion script.
Please add at least an entry to NEWS.Debian.
Regards, Daniel
- -- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.11 (PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xfce4-notes-plugin depends on:
ii libatk1.0-0 1.18.0-2 The ATK accessibility toolkit
ii libc6 2.5-4 GNU C Library: Shared libraries
ii libcairo2 1.4.4-1The Cairo 2D vector graphics libra
ii libfontconfig12.4.2-1.2 generic font configuration library
ii libglib2.0-0 2.12.11-3 The GLib library of C routines
ii libgtk2.0-0 2.10.11-2 The GTK+ graphical user interface
ii libice6 1:1.0.3-2 X11 Inter-Client Exchange library
ii libpango1.0-0 1.16.2-2 Layout and rendering of internatio
ii libsm61:1.0.2-2 X11 Session Management library
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxcursor1 1:1.1.8-2 X cursor management library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii libxfce4util4 4.4.1-1Utility functions library for Xfce
ii libxfcegui4-4 4.4.1-1Basic GUI C functions for Xfce4
ii libxfixes31:4.0.3-2 X11 miscellaneous 'fixes' extensio
ii libxi61:1.0.1-4 X11 Input extension library
ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library
ii libxrandr22:1.2.1-1 X11 RandR extension library
ii libxrender1 1:0.9.2-1 X Rendering Extension client libra
ii xfce4-panel 4.4.1-1The Xfce4 desktop environment pane
xfce4-notes-plugin recommends no packages.
- -- debconf-show failed
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGLeuwm0bx+wiPa4wRAhJmAKDTMu6U+RHqXfCyJsGhovckDNSZiQCfWiUW
hi/NcbwZU+lpn4TdA7VZr9w=
=N8ro
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420239: fglrx does not work with 2:1.3.0.0.dfsg-1 version of xserver-xorg-core
Am Dienstag, den 24.04.2007, 11:51 +0200 schrieb robin putters: > > Yes, fglrx needs to be updated, it only supports Xorg 7.1 so far > > according to ATI website. Reassigning and merging with other bugs. > > ATI supports xorg 7.2 since 8.33.6: ^^ 8.36.5? > http://www2.ati.com/drivers/linux/linux_8.36.5.html $ find downloads/ati/tmp -type d -name "x*" downloads/ati/tmp/arch/x86 downloads/ati/tmp/arch/x86_64 downloads/ati/tmp/x430 downloads/ati/tmp/x680 downloads/ati/tmp/x690 downloads/ati/tmp/x710 downloads/ati/tmp/x680_64a downloads/ati/tmp/x690_64a downloads/ati/tmp/x710_64a downloads/ati/tmp/x430_64a No directory for X.org 7.2. Also the created fglrx-amdcccle package, that shall replace fglrx-control, is empty (just as note for you, Flavio - please fill it with content when packaging for Debian). Further it was announced in 8.35.5 to drop support for X.org 6.8 and XFree86 4.3 and they are still there. The "System recommendations" section you reference also mentions X.org 6.7 as supported X.org server version. So it finally seems, the ATI-Installer and the release notes are both broken. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383495: Please update manpage.xml.ex to better work with latest docbook-xsl
reopen 383495 thanks What you did is exactly, what I told you not to do: - you removed the tags instead of removing the self-written author-section (#376378) - you did not update this completely outdated manpage XML template (#383495) This is a little bit disappointing. Which reasons did you have? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418846: Manpage issues
Am Dienstag, den 24.04.2007, 13:57 +0200 schrieb Gonéri Le Bouder: > tag 418846 pending > thanks > > On Thu, Apr 12, 2007 at 12:06:41PM +0200, Daniel Leidert wrote: > > I used sgml manpage from docbook-utils as example to improve the manpages. > > You can have a look on them here: > http://svn.debian.org/wsvn/collab-maint/deb-maint/svn-buildpackage/trunk/doc/?rev=0&sc=0 > svn co > svn://svn.debian.org/svn/collab-maint/deb-maint/svn-buildpackage/trunk/doc Hi, I discovered several semantic issues (and btw, there is also no need to remove the accent from your name). I suggest to use XML for the manpages. Looking at your build process does not show any regression by such a change (the ready-to-use manpages are used for building the documentation, not the SGML or XML sources). I will send you an update to svn-buildpackage written in XML (you can easily "convert" it back to SGML, if you need). I suggest XML, because the docbook-utils are outdated and I currently believe, manpages are best created from DB XML using docbook-xsl or docbook2x. Regards, Daniel
Bug#420239: fglrx does not work with 2:1.3.0.0.dfsg-1 version of xserver-xorg-core
Am Dienstag, den 24.04.2007, 21:42 +0900 schrieb Aric Cyr: > On 4/24/07, Daniel Leidert <[EMAIL PROTECTED]> wrote: > > Am Dienstag, den 24.04.2007, 11:51 +0200 schrieb robin putters: > > > > Yes, fglrx needs to be updated, it only supports Xorg 7.1 so far > > > > according to ATI website. Reassigning and merging with other bugs. > > > > > > ATI supports xorg 7.2 since 8.33.6: > > ^^ 8.36.5? > > > http://www2.ati.com/drivers/linux/linux_8.36.5.html > > > > $ find downloads/ati/tmp -type d -name "x*" > > downloads/ati/tmp/arch/x86 > > downloads/ati/tmp/arch/x86_64 > > downloads/ati/tmp/x430 > > downloads/ati/tmp/x680 > > downloads/ati/tmp/x690 > > downloads/ati/tmp/x710 > > downloads/ati/tmp/x680_64a > > downloads/ati/tmp/x690_64a > > downloads/ati/tmp/x710_64a > > downloads/ati/tmp/x430_64a > > > > No directory for X.org 7.2. Also the created fglrx-amdcccle package, > > that shall replace fglrx-control, is empty (just as note for you, Flavio > > The AMD installer is not maintained by Flavio, but by me. Flavio > maintains the official Debian packages only, which are still at 8.28 > as far as I can see. Do not bother him with ati-installer problems, > as it is not his responsibility and he probably does not want to worry > about it. Well, all I wanted to tell Flavio was, that the suggested package "fglrx-amdcccle" created by the ati-installer is empty. So when he prepares the packages for Debian, he should have a look, which files are considered for this package and not blindly copy your work. I do not expect him to fix bugs in the ati-installer itself. There are a lot more bugs in the Debian packages you provide. Simply run lintian/linda and you will see a bunch of (partly) easily fixable issues. > > - please fill it with content when packaging for Debian). Further it was > > announced in 8.35.5 to drop support for X.org 6.8 and XFree86 4.3 and > > they are still there. The "System recommendations" section you reference > > also mentions X.org 6.7 as supported X.org server version. So it finally > > seems, the ATI-Installer and the release notes are both broken. > > Due to a current versioning change in Debian (and Fedora Core 7 too > aparently) the fglrx driver will not load at all now. This is because > it expects a server version of 7.1, but the new modular version > reports 1.3.0 (xserver-xorg-core). I know, I read the bug reports and the workarounds and Flavios comment about the license issue with the workaround. All I wanted to say is, that the release notes do not fit, what the ati-installer ships. This is also just a FYI-information for the bug-readers and not a hint to Flavio to fix the ati-installer. But it was thought to be a hint for you. That's the reason, why I BCCed you in my answer to the BTS. [..] > Hopefully all these issues will be addressed for the next monthly > release from AMD, and I will update the ati-installer packaging > scripts as needed (fixing fglrx-amdcccle for example). BTW: Are you part of the ATI Linux Driver team? I'm planning to hand over the fglrx-manpages to ATI now, because of lack of time. So if you are part of this team or have contact to it's leader (Matthew Tippett?), I would kindly ask you to tell him and that he should contact me. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418846: Manpage issues
Am Dienstag, den 24.04.2007, 15:18 +0200 schrieb Daniel Leidert: > Am Dienstag, den 24.04.2007, 13:57 +0200 schrieb Gonéri Le Bouder: > > tag 418846 pending > > thanks > > > > On Thu, Apr 12, 2007 at 12:06:41PM +0200, Daniel Leidert wrote: > > > > I used sgml manpage from docbook-utils as example to improve the manpages. > > > > You can have a look on them here: > > http://svn.debian.org/wsvn/collab-maint/deb-maint/svn-buildpackage/trunk/doc/?rev=0&sc=0 > > svn co > > svn://svn.debian.org/svn/collab-maint/deb-maint/svn-buildpackage/trunk/doc > > Hi, I discovered several semantic issues (and btw, there is also no need > to remove the accent from your name). I suggest to use XML for the > manpages. Looking at your build process does not show any regression by > such a change (the ready-to-use manpages are used for building the > documentation, not the SGML or XML sources). I will send you an update > to svn-buildpackage written in XML (you can easily "convert" it back to > SGML, if you need). I suggest XML, because the docbook-utils are > outdated and I currently believe, manpages are best created from DB XML > using docbook-xsl or docbook2x. Attached. Produced with the command in the heading XML comment (as you can see, your name is correct too). If you want, I can update the other manpages too. Regards, Daniel .\" Title: SVN-BUILDPACKAGE .\"Author: Eduard Bloch <[EMAIL PROTECTED]> .\" Generator: DocBook XSL Stylesheets v1.72.0 <http://docbook.sf.net/> .\" Date: 04/24/2007 .\"Manual: svn-buildpackage User Manuals .\"Source: svn-buildpackage .\" .TH "SVN\-BUILDPACKAGE" "1" "04/24/2007" "svn\-buildpackage" "svn\-buildpackage User Manuals" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .SH "NAME" svn\-buildpackage \- build Debian packages from SVN repository .SH "SYNOPSIS" .HP 17 \fBsvn\-buildpackage\fR [\fBOPTION(S)\fR...] [\fBOPTION(S)\fR\ for\ dpkg\-buildpackage...] .SH "DESCRIPTION" .PP Builds a Debian package from a Subversion repository. The source code repository must be in the format created by \fBsvn\-inject\fR(1), and this script must be executed from the working directory (\fItrunk/package\fR). .PP By default, the working directory is used as the main source directory (assuming the whole upstream source is being stored in the repository). The alternative is so called \(lqmerge mode\(rq. With this method, only the debian directory (and maybe some other modified files) are stored in the repository. At build time, the contents of the svn trunk are copied to the extracted tarball contents (and can overwrite parts of it). To choose this working model, set the svn property \fImergeWithUpstream\fR on the Debian directory: .sp .RS 4 .nf $ \fBsvn propset mergeWithUpstream 1 debian\fR .fi .RE .PP The default behaviour is as follows: .sp .RS 4 \h'-04' 1.\h'+02'check the working directory, complain on uncommited files (also see \fB\-\-svn\-ignore\-new\fR) .RE .sp .RS 4 \h'-04' 2.\h'+02'copy the orig tarball to the build area if necessary (also see \fB\-\-svn\-no\-links\fR) .RE .sp .RS 4 \h'-04' 3.\h'+02'extract the tarball (in \(lqmerge mode\(rq) or export the svn work directory to the build directory (also see below and \fB\-\-svn\-no\-links\fR) .RE .sp .RS 4 \h'-04' 4.\h'+02'build with dpkg\-buildpackage (also see \fB\-\-svn\-builder\fR, \fB\-\-svn\-lintian\fR, etc.) .RE .sp .RS 4 \h'-04' 5.\h'+02'create a changelog entry for the future version .RE .SH "OPTIONS" .PP \fBsvn\-buildpackage\fR accepts the following options on the command\-line: .PP \fB\-\-svn\-builder=\fR\fB\fIcommand\fR\fR .RS 4 Specifies alternative build command instead of dpkg\-buildpackage, eg. \fBdebuild\fR(1), \fBpdebuild\fR(1) etc. Every parameters that svn\-buildpackage doesn't know (\fB\-\-svn\-*\fR) are passed to \fICOMMAND\fR. There is no difference between the command line and config file parameters. They are used at the same time. .sp .it 1 an-trap .nr an-no-space-flag 1 .nr an-break-flag 1 .br \fBWarning\fR Shell quotation rules do not completely apply here, better use wrappers for complex constructs. Using this option may break \fB\-\-svn\-lintian\fR, \fB\-\-svn\-linda\fR and \fB\-\-svn\-move\fR functionality. Some functions may be disabled when a custom build command is used because the output file location is not predictable. .RE .PP \fB\-\-svn\-ignore\-new\fR, \fB\-\-svn\-ignore\fR .RS 4 Don't stop on svn conflicts or new/changed files. To set this behaviour for single files set the \fIdeb:ignoreM\fR property to \fI1\fR on them. Also see documentation of the \fIsvn:ignore\fR property in
Bug#383495: UTF-8 as default encoding
Am Dienstag, den 24.04.2007, 17:07 +0200 schrieb Michael Biebl: > Zitat von Daniel Leidert <[EMAIL PROTECTED]>: [..] > > Ok. I added a note for this and fixed the encoding. Further I improved > > the manpage template slightly. The template and the results using > > xsltproc and docbook2x are attached. > > I know this is nitpicking but could you please also fix the > indentation of manpage.xml.ex. At some places it uses tabs, at others > spaces. This looks a bit ugly. Done and attached. > >> Having a man.make though is definitely a nice to have feature. > > > > Done. But I currently think about extending dh_installmanpages or > > similar to easey the process. > > That would be cool. I know :) Regards, Daniel manpage.xml.ex Description: application/docbook
Bug#372487: Fails to install: 'error parsing Python-Version attribute'
Package: python-numarray Version: 1.5.2-1 Followup-For: Bug #372487 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During todays installation: Setting up python-numarray (1.5.2-1) ... Traceback (most recent call last): File "/usr/bin/pycentral", line 1325, in ? main() File "/usr/bin/pycentral", line 1319, in main rv = action.run(global_options) File "/usr/bin/pycentral", line 854, in run pkg.read_version_info() File "/usr/bin/pycentral", line 526, in read_version_info self.version_info = pyversions.parse_versions(self.version_field) File "/usr/share/python/pyversions.py", line 41, in parse_versions raise ValueError, 'error parsing Python-Version attribute' ValueError: error parsing Python-Version attribute dpkg: error processing python-numarray (--configure): subprocess post-installation script returned error exit status 1 Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages python-numarray depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii python-central 0.5.5 register and build utility for Pyt python-numarray recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE9PGedg0kG0+YFBERAt4KAJ4sCiqlKEMJYQxgyTaWaTqpzYd26ACeLZrl 67jacRrtk6KyWgIS8IqkPzQ= =nP7K -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362066: xbase-clients: xf86cfg mentioned in description but not included in package
reopen 362066 thanks I got no response from you and because I still see 'xf86cfg' in the package description of xbase-clients (even in the latest SVN), I have to reopen the bug-report. Please simply remove the term 'xf86cfg' in the package description to close this bug-report. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347645: evolution: crashes randomly at Exit (backtrace attached)
Package: evolution Version: 2.6.3-1 Followup-For: Bug #347645 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I (also) observe random crahses, when I quit evolution. The backtrace (evolution-dbg is installed) is attached. I hope, this helps to solve the situation (or at least the crash I observe). Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages evolution depends on: ii dbus 0.62-4simple interprocess messaging syst ii evolution-common 2.6.3-1 architecture independent files for ii evolution-data-server 1.6.3-1 evolution database backend server ii gconf2 2.14.0-4 GNOME configuration database syste ii gnome-icon-theme 2.14.2-2 GNOME Desktop icon theme ii gtkhtml3.8 3.10.3-1 HTML rendering/editing library - b ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.12.1-1 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio ii libavahi-client3 0.6.13-2 Avahi client library ii libavahi-common3 0.6.13-2 Avahi common library ii libavahi-glib1 0.6.13-2 Avahi glib integration library ii libbonobo2-0 2.14.0-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-4 The Bonobo UI library ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libcairo2 1.2.4-1 The Cairo 2D vector graphics libra ii libcamel1.2-8 1.6.3-1 The Evolution MIME message handlin ii libdbus-1-20.62-4simple interprocess messaging syst ii libdbus-glib-1-2 0.62-4simple interprocess messaging syst ii libebook1.2-5 1.6.3-1 Client library for evolution addre ii libecal1.2-6 1.6.3-1 Client library for evolution calen ii libedataserver1.2-71.6.3-1 Utility library for evolution data ii libedataserverui1.2-6 1.6.3-1 GUI utility library for evolution ii libegroupwise1.2-101.6.3-1 Client library for accessing group ii libesd00.2.36-3 Enlightened Sound Daemon - Shared ii libexchange-storage1.2-1 1.6.3-1 Backend library for evolution cale ii libfontconfig1 2.3.2-7 generic font configuration library ii libfreetype6 2.2.1-2 FreeType 2 font engine, shared lib ii libgconf2-42.14.0-4 GNOME configuration database syste ii libgcrypt111.2.2-3 LGPL Crypto library - runtime libr ii libglade2-01:2.6.0-2 library to load .glade files at ru ii libglib2.0-0 2.10.3-3 The GLib library of C routines ii libgnome-keyring0 0.4.9-1 GNOME keyring services library ii libgnome-pilot22.0.12-1.6+b1 Support libraries for gnome-pilot ii libgnome2-02.14.1-3 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-6 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-1 GNOME virtual file-system (runtime ii libgnutls131.4.2-1 the GNU TLS library - runtime libr ii libgpg-error0 1.2-1 library for common error values an ii libgtk2.0-02.8.20-1 The GTK+ graphical user interface ii libgtkhtml3.8-15 3.10.3-1 HTML rendering/editing library - r ii libhal10.5.7.1-1 Hardware Abstraction Layer - share ii libice61:1.0.0-3 X11 Inter-Client Exchange library ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libldap2 2.1.30-13+b1 OpenLDAP libraries ii libnm-glib00.6.4-1 network management framework (GLib ii libnotify1 0.4.2-1 sends desktop notifications to a n ii libnspr4-0d1.8.0.5-3 NetScape Portable Runtime Library ii libnss3-0d 1.8.0.5-3 Network Security Service libraries ii liborbit2 1:2.14.0-2libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.12.3-2 Layout and rendering of internatio ii libpisock8 0.11.8-24 Library for communicating with a P ii
Bug#385670: apt is calculation wrong dependencies
Package: apt Version: 0.6.45 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sometimes apt wants to install apache2-mpm-prefork libapache2-mod-php4 for me, when I update the system. But there is really no need to do this and after the upgrade I normally have to run 'apt-get remove --purge ...' for these two packages to remove them again. See e.g. today: LANG=C sudo apt-get dist-upgrade -u Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following NEW packages will be installed: apache2-mpm-prefork libapache2-mod-php4 The following packages have been kept back: pan The following packages will be upgraded: cpp-4.1 fastjar g++-4.1 gcc-4.1 gcc-4.1-base gcc-4.1-locales gettext gettext-base libapache-mod-php4 libgcc1 libgfortran1 libmilter0 libmudflap0 libmudflap0-dev libssp0 libstdc++6 libstdc++6-4.1-dev libstdc++6-4.1-doc mysql-common php-pear php4 php4-cgi php4-cli php4-common php4-mysql php4-pear php5-common python-gdbm python-support python-tk 30 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 23.5MB/28.2MB of archives. After unpacking 3637kB of additional disk space will be used. Do you want to continue [Y/n]? y [..] And after installation: LANG=C sudo apt-get remove --purge apache2-mpm-prefork libapache2-mod-php4 Reading package lists... Done Building dependency tree... Done The following packages will be REMOVED: apache2-mpm-prefork* libapache2-mod-php4* 0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded. Need to get 0B of archives. After unpacking 3690kB disk space will be freed. Do you want to continue [Y/n]? y [..] So there should be no need to install these two packages and I guess, apt mis-calculates the dependecies in this special case. If you tell me, how I can help to examine the cause for this issue, I will do my best to help. This is not annoying, but also not very nice. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages apt depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 Versions of packages apt recommends: ii debian-archive-keyring2006.01.18 GnuPG archive keys of the Debian a - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE+Onqdg0kG0+YFBERAsJtAJ0QKrjfj8FqDp2u8E6JRLa8JlVhRwCdHkAb utvsEiY/r97saNakfMZVSOk= =eLTM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385670: apt is calculation wrong dependencies
Am Samstag, den 02.09.2006, 07:35 +0200 schrieb Marc Haber: > On Sat, Sep 02, 2006 at 04:18:18AM +0200, Daniel Leidert wrote: > > Sometimes apt wants to install apache2-mpm-prefork libapache2-mod-php4 > > for me, when I update the system. But there is really no need to do this > > and after the upgrade I normally have to run 'apt-get remove --purge > > ...' for these two packages to remove them again. > > Are you sometimes using a mixture of apt-get and aptitude? Never. > aptitude has its own database of packages it wants installed. Sure. But this issue appears with apt and is totally unrelated to aptitude (IMHO, because apt makes the suggestion, not aptitude). But it appears frequently. I did not yet examine, which package causes the behaviour (I guess it's one of the php* packages). > I recommend ditching apt-get altogether; aptitude is really smarter. In my experiences, aptitude is more problematic. For me it often made (really) senseless suggestions, when I tried it for a while. I simply don't like it (it doesn't fit my needs - whyever). Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385915: non-existent file automake-1.9.info.gz in doc-base control file
Package: automake1.9
Version: 1.9.6+nogfdl-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
During todays update:
Setting up automake1.9 (1.9.6+nogfdl-1) ...
warning: file `/usr/share/info/automake-1.9.info.gz' does not exist at
/usr/sbin/install-docs line 718, line
17.
warning: file mask `/usr/share/info/automake-1.9.info*' does not match
any files at /usr/sbin/install-docs line 723,
line 17.
Regards, Daniel
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.08060320
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages automake1.9 depends on:
ii autoconf 2.60a-2automatic configure script builder
ii autotools-dev 20060702.1 Update infrastructure for config.{
automake1.9 recommends no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE+147dg0kG0+YFBERAoQlAJ9q1niMz75SMKrhkOraURA8KtgFOACffilf
G2KYyFVvFkPAdRNP3qQIEok=
=82ZG
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383463: One further issue of a similar kind
Package: aptitude Version: 0.4.3-1 Followup-For: Bug #383463 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is one more issue. The template to match literal can also lead (and leads) to issues when nesting bold and italic elements (see e.g. in the section "COMMAND-LINE ACTIONS" the action "download": There you can see, that in "=" and "/" the '>' sign ist not bold. The attached patch will fix this. Then I have one more issue in the Makefiles: You can specify '-o - -o output-man/aptitude.8' without the manpage name (manpages output gets its name from refentrytitle and you cannot change this, so the name aptitude.8 is useless there and also not respected). You should specify: - -o output-man/ (see 'man xsltproc') and check refentrytitle and manvolnum to get the name of the resulting manpage. And a small cosmetic issue: The title is 'aptitude command-line referenc'. But because there is a length restriction, the last character of that title (the 'e') is not shown. Maybe you should decrease the title length by using a shorter title like simply 'aptitude reference' or 'command-line reference'. This is of course just a minor problem. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-6-3. 0.6.45 Advanced front-end for dpkg ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libncursesw5 5.5-2 Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.17-1type-safe Signal Framework for C++ ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc 0.4.3-1English manual for aptitude, a ter - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE+22Gdg0kG0+YFBERAnC7AJ0XJaetmzUtHCGngYso083pnwCVsACfdMFJ wgEvpHlYkPnmgnisylFdTeU= =06Ye -END PGP SIGNATURE- --- aptitude-0.4.3.orig/doc/aptitude-man.xsl2006-09-04 01:21:51.0 +0200 +++ aptitude-0.4.3/doc/aptitude-man.xsl 2006-09-04 01:26:35.0 +0200 @@ -19,7 +19,10 @@ - \fB\fR + + + + text
Bug#385940: Fixed.
Am Dienstag, den 05.09.2006, 09:20 +0900 schrieb Michael(tm) Smith: > I've checked in a fix for this to upstream source. If possible, > please test with the latest snapshot: > > http://docbook.sourceforge.net/snapshots/ Thanks. I'm currently testing. > But note this: address is a block element, always, and a DocBook > "verbatim" also (the equivalent of an HTML PRE -- all linebreaks > and whitespace within it are output as-is). So I'm not sure why > you had it marked up like the following in your test file: > > Foo2 FooScreen I was just testing with several verbatim elements to isolate the cause of this issue and the last I used was . That's the whole reason. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385940: Fixed.
Am Dienstag, den 05.09.2006, 09:53 +0900 schrieb Michael(tm) Smith: > Daniel Leidert <[EMAIL PROTECTED]>, 2006-09-05 02:49 +0200: > > > > Foo2 FooScreen > > > > I was just testing with several verbatim elements to isolate the cause > > of this issue and the last I used was . That's the whole > > reason. > > Ah, I see that now. I guess I would have realized that if I had > taken time to actually read through the whole original bug report. > Sorry for the noise about that. No problem. The fix looks good here. I've tested with several projects. None negative effects. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382505: We'd need to update the upstream docs also
Am Dienstag, den 05.09.2006, 16:30 +0900 schrieb Michael(tm) Smith: > If you were to change the Debian docbook-xsl package such that it > uses /etc/papersize as a default papersize instead of using > "letter", as the upstream docs say, then you run the risk of a > users discovering that every time they generate FO output, they > are getting a different default thatn what the upstream docs say > they should be getting, and them perhaps having no idea why that > is happening. True. > I suppose that if you implemented this, we could > update the upstream docs to say that the default is "letter" > except on Debian, where it's whatever is specified in > /etc/papersize. I thought about simply patching the docs in the debian package along with the param.xsl adding a notes - that we (Debian) try to read /etc/papersize to get the value and fall back to the described default - that this is limited to only reading /etc/papersize (PAPERSIZE and PAPERCONF cannot be examined) - that more info is in README.Debian (necessary commands) I don't think, that this should be put in upstream docs directly. I would maybe suggest (if you like the idea of reading the libpaper config), that you implement this in the XSL2 stylesheets using unparsed-text() of a file, set to /etc/papersize by default. The implementation for XSL1 is more a (working) workaround. But XSL2 offers the possibilities to do this, so it could be implemented. > But we've never put anything system-specific into > the upstream docs before, and IMHO, this wouldn't really merit a > setting a precedent for doing that. See above. Don't put anything system specific into the docs. It's also possible, that one day this patch will be dropped, because of a better solution or any issues and then upstream docs may be outdated (and wrong) then. So I really don't think it's a good idea to put this into upstream docs. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382505: We'd need to update the upstream docs also
Am Mittwoch, den 06.09.2006, 00:59 +0900 schrieb Michael(tm) Smith: > Daniel Leidert <[EMAIL PROTECTED]>, 2006-09-05 15:23 +0200: [Should the workaround be mentioned in upstream docs?] > > See above. Don't put anything system specific into the docs. It's also > > possible, that one day this patch will be dropped, because of a better > > solution or any issues and then upstream docs may be outdated (and > > wrong) then. So I really don't think it's a good idea to put this into > > upstream docs. > > And my point is that if it's not put into the upstream docs (and > believe me, I'm not disagreeing that is shouldn't be), then it the > patch should be dropped from Debian. You otherwise will have users > who have no idea where the default value is coming from. I could simply add a note [1] to the xsl:message, where you (upstream) output, which format is used (fo/docbook.xsl -> root.messages). IMHO this is enough to make users aware of this little workaround. [1] E.g.: "See /usr/share/doc/docbook-xsl/README.Debian for more information." Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363506: Upstream reached version number 0.10
Package: podbrowser Followup-For: Bug #363506 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Upstream released version 0.10 of podbrowser and I probably need it for another program. Are you still working on this package so an updated package can be expected? Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE/kOkdg0kG0+YFBERAvQPAJ99DRsxeByLOkkp2Jud5BBnlzGfbgCfcQBY nCKrUXgUZQyYJqGd/OimK2U= =CyKy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386492: Add an entry to shared MIME info database
Package: dpatch Version: 2.0.20 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was wondering, why my evolution did not show attached dpatch. Then I found, that there is no entry made to the shared-mime-info database. Maybe you could add such an entry (with ) and then evolution should show such patches too. I can write a patch if you want. But in this case I need to know, how the MIME type is called. Maybe text/x-dpatch? If you agree and an entry should be made to the shared-mime-info database directly, this report should be reassigned to shared-mime-info. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) dpatch depends on no packages. Versions of packages dpatch recommends: ii dpkg-dev 1.13.22package building tools for Debian ii fakeroot 1.5.10 Gives a fake root environment ii patchutils0.2.31-3 Utilities to work with patches - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFALiTdg0kG0+YFBERAh4DAJsHwD/VnR0OvGjs3Ita/OgiXr3j5QCfY/ZD 3TH+tYIujoMqW9DEOAJOgYI= =/5mL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383408: [xml/sgml-pkgs] Bug#383408: xsltproc: problems with dblatex interaction
Am Donnerstag, den 28.09.2006, 22:03 +0200 schrieb Andreas Hoenen:
> I have gained some more understanding of the problem:
>
> XInclude elements contained in dblatex XSLT stylesheets like
>
>
>
> lead to warnings like:
>
> /usr/share/xml/docbook/stylesheet/dblatex/xsl/common/mklistings.xsl:104:
> element include: XInclude error : encoding {$encoding} not supported
> /usr/share/xml/docbook/stylesheet/dblatex/xsl/common/mklistings.xsl:104:
> element include: XInclude error : could not load
> /usr/share/xml/docbook/stylesheet/dblatex/xsl/common/%7B$filename%7D, and no
> fallback was found
>
> when dblatex calls xsltproc.
[..]
> Possible solutions:
>
> 1)
> xsltproc gets enhanced by an new command line option with the meaning:
> Disable XInclude resolving in the parser, but enable it in the XSLT
> processor. IMHO the best solution, but one would have to convince
> upstream...
That is planned. I did not read all of the messages in this report, but
the following discussion at the xslt mailing list is probably related to
what you discuss:
http://mail.gnome.org/archives/xslt/2006-August/msg00027.html (Kasimier
B. sometimes broke the thread, so search for messages with the subject
"XInclude-processing in XSL stylesheets" too.
[..]
> One final remark:
>
> It seems possible that the next upstream release of xsltproc will
> include this problematic patch already included in Debian version
> 1.1.17-4, then also native dblatex installations will suffer from the
> warnings.
No, read http://mail.gnome.org/archives/xslt/2006-August/msg00048.html.
The patch will be changed. See
http://mail.gnome.org/archives/xslt/2006-September/msg5.html for the
reason, why it was not already done.
For the moment the patch as suggested in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383408 could be removed
from the Debian package, because the related bug #382505 cannot be
solved with this patch either, see
http://mail.gnome.org/archives/xslt/2006-August/msg00051.html.
Regards, Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390783: Depends on transitional packages
Package: tk8.4-dev Version: 8.4.12-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I found, that the package depends on transitonal packages, which are considered to be removed "safely" after the transition. But because it depends on x-dev, x-dev cannot be removed. Please update the dependencies to e.g.: x11proto-core-dev | x-dev. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.09060920 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages tk8.4-dev depends on: ii libc6-dev [libc-dev] 2.3.6.ds1-5 GNU C Library: Development Librari ii libx11-dev 2:1.0.0-9 X11 client-side library (developme ii libxt-dev1:1.0.2-2 X11 toolkit intrinsics library (de ii tcl8.4-dev 8.4.12-1.1 Tcl (the Tool Command Language) v8 ii tk8.48.4.12-1Tk toolkit for Tcl and X11, v8.4 - ii x-dev7.0.7-2 dummy package for transition purpo tk8.4-dev recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFIbjhdg0kG0+YFBERAg0MAJ4xhEQyu0QVGxcVVH56Ma5A84TDtACfc8vD IdMn/rpSkkq9+6sLepOjv+E= =rvL0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389681: Retrieving bug reports... 0% ... E: undefined local variable or method ...
Package: apt-listbugs Version: 0.0.57 Followup-For: Bug #389681 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You asked for proxies: There is a squid in the network where I'm located, which should handle HTTP and FTP. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.09060920 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages apt-listbugs depends on: ii apt 0.6.46 Advanced front-end for dpkg ii libdpkg-ruby1.8 0.3.2 modules/classes for dpkg on ruby 1 ii libhttp-access2-ruby1.8 2.0.6-1HTTP accessing library for ruby ii libintl-gettext-ruby1.8 0.11-8 Gettext wrapper for Ruby 1.8 ii libruby1.8 [libzlib-ruby1.8] 1.8.5-2Libraries necessary to run Ruby 1. ii libxml-parser-ruby1.8 0.6.8-2Interface of expat for the scripti ii ruby 1.8.2-1An interpreter of object-oriented apt-listbugs recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFIoKNm0bx+wiPa4wRAnifAKCPcd9X9GyrBkIlPdI9A+3L/lFIewCgt0k9 6vvUqAatKI5YFUkh01zRI2A= =z0Wm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383408: 'xsltproc --xinclude' should also force XInclude processing on a XSL-styleshett
Package: xsltproc Version: 1.1.17-3 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During my work on trying to solve bug #173093 and #382505 (docbook-xsl) I found, that xsltproc does not XInclude processing in XSL(T)-stylesheets. Daniel Veillard developed a patch to fix this behaviour and I would like to request, that you apply this patch. The patch can be found at: http://cvs.gnome.org/viewcvs/libxslt/xsltproc/xsltproc.c?r1=1.64&r2=1.65 Thanks and regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages xsltproc depends on: ii libc6 2.3.6-19 GNU C Library: Shared libraries ii libgcrypt111.2.2-3 LGPL Crypto library - runtime libr ii libgpg-error0 1.2-1 library for common error values an ii libxml22.6.26.dfsg-3 GNOME XML library ii libxslt1.1 1.1.17-3.1XSLT processing library - runtime xsltproc recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE498Adg0kG0+YFBERAniyAJ9p0ZYTf352WH9C5nfQm+fI7fRsnACaA8Hp KjfMG7ylOa8Qv06FBTSIq4M= =75XU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383463: manpages: avoid wrong encoding in translated manpages
Package: aptitude Version: 0.4.2-1 Severity: minor Tags: l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, After docbook-xsl 1.70.1 reached Debian, you should add the following param to the xsltproc call, which produces the aptitude manpage: xsltproc [..] --param man.charmap.use.subset "0" [..] This will replace all special characters with it's groff characters. ATM the German manpage e.g. shows some encoding issues on my system. BTW: In doc/aptitude-man.xsl I suggest: < > The only difference: The '<>' will not be underlined, but I think, that's ok. The reason for this: Your code is based on old code, that can lead to missig underlined/bold highlighting when nesting italic and bold elements. Further it's not respecting the man.hyphenate.computer.inlines parameter. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-6-3.1 0.6.45 Advanced front-end for dpkg ii libc6 2.3.6-19 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-10 GCC support library ii libncursesw5 5.5-2 Shared libraries for terminal hand ii libsigc++-2.0-0c2a2.0.16-3 type-safe Signal Framework for C++ ii libstdc++64.1.1-10 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc 0.4.2-1English manual for aptitude, a ter - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE5GjSdg0kG0+YFBERAgMYAKCKDe0g+rhunyi6NuUPjhFEWrIqrQCfVRCn ftXy2GXT749tcO1Z5QH0AEg= =f2kk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383495: Please update manpage.xml.ex to better work with latest docbook-xsl
Package: debhelper Version: 5.0.37.3 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I would like to request an update of the manpage.xml.ex example, dh_make uses. After docbook-xsl 1.70.1 reached Debian Sid, the current example will clash with the stylesheets: - - the mail address should me moved into the author element and a contrib element should be added - - the self-written AUTHOR section should be removed - the latest docbook-xsl package automatically creates an AUTHOR section and it also adds a COPYRIGHT section, that contains the copyright (copyright element) and license information (legalnotice element). - - several options inside a variablelist, should be put in several term elements (this behaviour is now controlled via the variablelist.term.separator and variablelist.term.break.after parameters) and not in one term element by default - - the copyright year should be set to 2006 manually or replaced by dh_make too - - referencing manpages should be done using the citerefentry element IMHO the DocBook DTD can be raised to 4.4 too. I attached a sample manpage.xml.ex, which improves the content and adds some more sections samples, you can find in manpages (only sections also mentioned in the Linux Man Page Howto). Have a look at it and tell me your opinion. I've attached a sample manpage resulting from the example too. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages debhelper depends on: ii binutils 2.17-2 The GNU assembler, linker and bina ii coreutils 5.97-3 The GNU core utilities ii dpkg-dev 1.13.22package building tools for Debian ii file 4.17-3 Determines file type using "magic" ii html2text 1.3.2a-3 An advanced HTML to text converter ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii po-debconf1.0.5 manage translated Debconf template debhelper recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE5Jstdg0kG0+YFBERAq0NAJwL3COanBgfPjMd8Lo8Octaf1ZRVACbBw6J 4rBswIqXELRggVfBxy3ymRI= =BcCY -END PGP SIGNATURE- manpage.xml.ex Description: Binary data
Bug#362066: closed by Daniel Stone <[EMAIL PROTECTED]> (no longer shipping x{free86,org}c{fg,onfig})
Am Samstag, den 12.08.2006, 13:19 -0700 schrieb Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > #362066: xf86cfg mentioned in description but not included in package, > which was filed against the xbase-clients package. > > It has been closed by Daniel Stone <[EMAIL PROTECTED]>. Why did you close my bug-report? The package description (xbase-clients 1:7.1.ds-3) still mentions xf86cfg: > The bitmap, editres, viewres, xbiff, xcalc, xconsole, xditview, xedit, > xf86cfg, xman, xsetroot, and xsm programs use bitmap images provided by the ^^^ > xlibs-data package. xkbcomp uses the XKEYBOARD (XKB) extension configuration > data provided by the xlibs package. _Because_ the applications are not shipped, they should not be mentioned in the package description. I cannot see, why this report has been closed, because the bug itself doesn't seem to be fixed. I hope for some response from you. If not, I have to reopen that bug-report. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336674: pan: Supersede and Cancel reference a false MID
forwarded 336674 http://bugzilla.gnome.org/show_bug.cgi?id=351577 thanks Am Dienstag, den 15.08.2006, 22:08 +0200 schrieb Daniel Leidert: > ATM Supersede and Cancel do not offer any functionality. > > My original bug-report to upstream at > http://bugzilla.gnome.org/show_bug.cgi?id=324795 The bug-report has changed and is now http://bugzilla.gnome.org/show_bug.cgi?id=351577. > was tagged "Target > 1.0", so I hope, a working Supersede and Cancel implementation will be > available before or with the official pan 1.0 release. Upstream is aware of the "new" issue and Charles Kerr provided a patch to add the Cancel and Supersede functionality: http://bugzilla.gnome.org/attachment.cgi?id=71108&action=view Maybe you could add this patch to the Debian package, so the code could be officially tested. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#376378: Please update manpage.xml.ex to better work with latest docbook-xsl
severity 376378 minor severity 383495 minor merge 383495 376378 thanks In reply to Damián Viano (http://bugs.debian.org/376378): > The manpage.xml.ex template includes an author secction and a refentry > for the author wich produces 2 author sections in the final manpage. > > This patch removes the author refentry instance. It works for me, but YMMV. [snip] You should not remove the authorgroup|author|editor|othercredit elements. Instead remove the separate "AUTHOR" section (implemented using a refsect1 element), as it is created automatically from the mentioned elements. The copyright and license information this section contains, should better be put into the copyright|legalnotice elements, which are also processed and a copyright and license section will be output too. Have a look at my proposal attached to bug #383495. In reply to myself (http://bugs.debian.org/383495): > I would like to request an update of the manpage.xml.ex example, dh_make > uses. After docbook-xsl 1.70.1 reached Debian Sid, the current example > will clash with the stylesheets: [snip] > IMHO the DocBook DTD can be raised to 4.4 too. I attached a sample > manpage.xml.ex, which improves the content and adds some more sections > samples, you can find in manpages (only sections also mentioned in the > Linux Man Page Howto). Have a look at it and tell me your opinion. I've > attached a sample manpage resulting from the example too. Seems I forgot it. Now it is attached too. I merged both reports, because they IMO belong together. Regards, Daniel
Bug#383495: Please update manpage.xml.ex to better work with latest docbook-xsl
Am Dienstag, den 22.08.2006, 00:03 +0200 schrieb Daniel Leidert:
[resulting manpage]
> Seems I forgot it. Now it is attached too.
Argh. Now it is.
Regards, Daniel
.\" Title: FOO
.\"Author: John Doe <[EMAIL PROTECTED]>
.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" Date: 2006.08.17
.\"Manual: foo User Manual
.\"Source: foo
.\"
.TH "FOO" "1" "2006\-08\-17" "foo" "foo User Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
foo \- program to do something
.SH "SYNOPSIS"
.HP 4
\fBfoo\fR \fB\-e\ \fR\fB\fIthis\fR\fR [\fB\-\-example=\fR\fB\fIthat\fR\fR] [{\fB\-e\fR\ |\ \fB\-\-example\fR}\ \fIthis\fR] [{\fB\-e\fR\ |\ \fB\-\-example\fR}\ {\fIthis\fR\ |\ \fIthat\fR}]
.HP 4
\fBfoo\fR [{\fB\-h\fR\ |\ \fB\-\-help\fR} | {\fB\-v\fR\ |\ \fB\-\-version\fR}]
.SH "DESCRIPTION"
.PP
This manual page documents briefly the
\fBfoo\fR
and
\fBbar\fR
commands.
.PP
This manual page was written for the
Debian(TM)
distribution because the original program does not have a manual page. Instead, it has documentation in the
GNU
Info
format; see below.
.PP
\fBfoo\fR
is a program that...
.SH "OPTIONS"
.PP
The program follows the usual
GNU
command line syntax, with long options starting with two dashes (`\-'). A summary of options is included below. For a complete description, see the
Info
files.
.PP
\fB\-e \fR\fB\fIthis\fR\fR, \fB\-\-example=\fR\fB\fIthat\fR\fR
.RS 3n
Does this and that.
.RE
.PP
\fB\-h\fR, \fB\-\-help\fR
.RS 3n
Show summary of options.
.RE
.PP
\fB\-v\fR, \fB\-\-version\fR
.RS 3n
Show version of program.
.RE
.SH "FILES"
.TP 3n
\fI/etc/foo.conf\fR
The system\-wide configuration file to control the behaviour of
foo. See
\fBfoo.conf\fR(5)
for further details.
.TP 3n
\fI${HOME}/.foo.conf\fR
The per\-user configuration file to control the behaviour of
foo. See
\fBfoo.conf\fR(5)
for further details.
.SH "ENVIONMENT"
.TP 3n
\fBFOO_CONF\fR
If used, the defined file is used as configuration file (see also
the section called \(lqFILES\(rq).
.SH "DIAGNOSTICS"
.PP
The following diagnostics may be issued on
\fIstderr\fR:
.TP 3n
Bad configuration file. Exiting.
The configuration file seems to contain a broken configuration line. Use the
\fB\-\-verbose\fR
option, to get more info.
.PP
\fBfoo\fR
provides some return codes, that can be used in scripts:
.\" line length increase to cope w/ tbl weirdness
.ll +(\n(LLu * 62u / 100u)
.TS
ll.
\fICode\fR \fIDiagnostic\fR
T{
\fB0\fR
T} T{
Program exited successfully.
T}
T{
\fB1\fR
T} T{
The configuration file seems to be broken.
T}
.TE
.\" line length decrease back to previous value
.ll -(\n(LLu * 62u / 100u)
.sp
.SH "BUGS"
.PP
The program is currently limited to only work with the
foobar
library.
.PP
The upstreams
BTS
can be found at
\fI\%http://bugzilla.foo.tld\fR.
.SH "SEE ALSO"
.PP
\fBbar\fR(1),
\fBbaz\fR(1),
\fBfoo.conf\fR(5)
.PP
The programs are documented fully by
The Rise and Fall of a Fooish Bar
available via the
Info
system.
.SH "AUTHOR"
.PP
\fBJohn\fR \fBDoe\fR <[EMAIL PROTECTED]>
.sp -1n
.IP "" 3n
Manpage author.
.SH "COPYRIGHT"
Copyright \(co 2006 John Doe
.br
.PP
This manual page was written for the
Debian(TM)
system (but may be used by others).
.PP
Permission is granted to copy, distribute and/or modify this document under the terms of the
GNU
General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation.
.PP
On Debian systems, the complete text of the GNU General Public License can be found in
\fIfile:///usr/share/common\-licenses/GPL\fR.
.br
Bug#332474: [EMAIL PROTECTED]"strong" supported in docbook-xsl 1.70.1.dfsg.1-0.2
tags 332474 + fixed fixed-upstream thanks Am Dienstag, den 22.08.2006, 03:20 +0200 schrieb Michael(tm) Smith: > Hi. I'm the upstream developer for the DocBook XSL manpages > stylesheet. I added support for [EMAIL PROTECTED]"strong" to the > upstream source quite a while back. I guess it was in the 1.69.1 > release (which never got packaged for Debian). Anyway the Debian > docbook-xsl 1.70.1.dfsg.1-0.2 package does contain the support, so > I think this bug can probably be closed out. Currently just tagging it "fixed" and "fixed-upstream". It will be closed with the next official (non-NMU) upload. Thanks to Michael Smith for the info. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383874: contrib normalization fixed upstream
tags 383874 + fixed-upstream thanks Am Dienstag, den 22.08.2006, 03:03 +0200 schrieb Michael(tm) Smith: > Hi. I'm the upstream developer for the DocBook XSL manpages > stylesheet. Daniel Leidert brought Debian bug #383874 to my > attention. > > I've checked in a fix for bug #383874 to the upstream source. You > can test it using the latest snapshot: I will include the fix http://sourceforge.net/mailarchive/forum.php?thread_id=30313029&forum_id=2281 with the next upload (along with another bug-fix http://sourceforge.net/mailarchive/forum.php?thread_id=30302421&forum_id=2281). > http://docbook.sourceforge.net/snapshots/ > > The fix will be included in the next release -- which will either > be numbered 1.70.2 or 1.80.0. Thanks for the reply Michael. Just a question: The same issue affects also other children of author|editor|othercredit (like email, firstname, surname, authorblurb, ...). Shouldn't they be treated the same way? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345750: docbook-xsl: Formatting bug for manpages with tabs/spaces
tags 345750 + fixed fixed-upstream thanks Hello, Aaron Isotton wrote: > Consider the following example: > > [1] There should be a space after the colon: > [2] -x but there is none because this line is indented > [3] with tabs. > > When the line [2] is indented with spaces, the output is as follows (as it > should): > > ...after the colon: -x but there... > > When the same line is indented with tabs, the output is as follows (notice the > missing space before the -x): > > ...after the colon:-x but there... This had been fixed by upstream and the example you provided does not longer produce a space-missing output (instead it can lead to a leading or doubled space - but this is probably a minor issue). I just tag this bug report for the moment and it will be closed with the next official upload. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383874: contrib normalization fixed upstream
Am Dienstag, den 22.08.2006, 04:49 +0200 schrieb Michael(tm) Smith: > Daniel Leidert <[EMAIL PROTECTED]>, 2006-08-22 04:32 +0200: > > > Thanks for the reply Michael. Just a question: The same issue affects > > also other children of author|editor|othercredit (like email, firstname, > > surname, authorblurb, ...). Shouldn't they be treated the same way? > > The authorblurb element can contain paragraph data, which can > include verbatim environments (programlisting, screen, etc.). So > it would be wrong to run normalize-space on it. Ok, ACK (never used authorblurb). > As far as > firstname and surname, yeah, perhaps they should be normalized. > I'll take a look. If you have others mind, I can look at them case > by case. I think, the firstname and surname (othername too?), email, honorific and probably lineage elements should be normalized too, to avoid unintended linebreaks in the AUTHOR section. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#200905: dh_installdocs still installs zero-byte files
Package: debhelper Version: 5.0.37.3 Followup-For: Bug #200905 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today I wanted to change to debhelper compat level to 5 (debian/compat) in docbook-xsl(-doc). There I have a dh_installdocs call, where I explicitely excluded several files (using the -X option) from beeing installed, because these files are zero-byte files. I now expected, that raising the compatibility level (fixing build-dependencies ...) to 5 should avoid an installation of these files. But this failed: W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/fo/param.html N: N: Package contains a file which is empty. N: W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/html/param.html W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/manpages/param.html W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/pi/pi.html W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/slides/param.html W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/website/param.html W: docbook-xsl-doc: zero-byte-file-in-doc-directory usr/share/doc/docbook-xsl-doc/doc/wordml/param.html My $package.docs files just contains the direcory name of the directory, containg all doc-files to install. This works pretty well, but I guess, it's also the reason, why your test, if the file is empty, fails. My fault (or: "I should immediately stop misuing the .docs file".) or "yours" (or: "The test could be improved to also catch this situation.")? Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages debhelper depends on: ii binutils 2.17-2 The GNU assembler, linker and bina ii coreutils 5.97-4 The GNU core utilities ii dpkg-dev 1.13.22package building tools for Debian ii file 4.17-3 Determines file type using "magic" ii html2text 1.3.2a-3 An advanced HTML to text converter ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii po-debconf1.0.5 manage translated Debconf template debhelper recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE8f5Ndg0kG0+YFBERAtfLAJ4lzzkruNby7XYS+1imniiJ34yhXQCfZUh5 /L313ah0gc+BwuIj9k6fkTg= =qTdD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380210: easychem freezes when exporting
> Hello again, > > Teemu Ikonen wrote: >> reopen 380210 >> thanks >> >> Hi, >> >> It seems that the patch did not fix this bug. At least I'm >> experiencing something similar with the Debian version 0.6-2. When I >> click File->Export (or press CTRL-E), easychem freezes and hogs the >> CPU (the gui is still updated though). >> >> Teemu > > In my last mail, I made some mistake: the bug that I encountered is > probably not the one Temmu has. > > Indeed, his symptoms seem rather related to another bug I found: when > you also have pstoedit installed, easychem freezes just as Teemu said. > > It seems to come from the function detect_pstoedit in detect.c, which > does things I do not understand. (Does stdout has an end ?) > > After correcting this bug, it appeared that the exporting function > fig_pstoedit_export in export.c itself was buggy. > > So here is some patch, replacing the one in my last mail, which does the > following changes: [snip] Thanks. Unfortunately I'm currently offline with a dying harddrive, so I cannot check and test the patch myself atm. But I asked someone else to test it. I will notify you, when the patch has been tested and/or the bug(s) havs been fixed. Thanks and regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387688: debian-archive-keyring: superfluous dependency on gnupg?
Hello, > OTOH apt-get update will print a helpful message that it can't > check signatures because of the missing gnupg so it wouldn't be too > much of a problem. IIRC apt-get completely fails if gnupg is not installed, because several commands cannot be found. And the warning only appears, if the signatures or the key-ring(s) are missing. So apt-get IMHO and IIRC really depends on gnupg. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386580: manpages/docbook.xsl: contents of a footnote is getting lost
tags 386580 + upstream forwarded 386580 http://sourceforge.net/tracker/index.php?func=detail&aid=1555087&group_id=21935&atid=373747 thanks Am Freitag, den 08.09.2006, 17:49 +0200 schrieb Jakub Wilk: > $ cat buggy.xml [snip] > $ xsltproc --nonet > /usr/share/xml/docbook/stylesheet/nwalsh/manpages/docbook.xsl buggy.xml > $ man -l buggy.1 [snip] Thanks for your report. I already observed this issue, but missed to create an entry in the upstream BTS. This is now done. I have to leave for some days, so I will have a closer look, when I'm back. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387064: File permission could be mangled
Package: pbuilder Version: 0.158 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is some really obscure issue. I'm maintaining docbook-xsl. I'm currently building version 1.71.0.dfsg.1-1. When I build this version with pbuilder, the file /usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl gets executable file permissions (0755). The checkout is made from CVS (using cvs-buildpackage). The file itself has only 0600 file permissons (definitely no executable tag). When I build the package with debuild, everything is ok. But when I use pbuilder, the file get's executable flags added, which results in a lintian warning. You can try it youself (with cvs-buildpackage installed, and a SID chroot): $ cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/debian-xml-sgml \ co -d pkg-doc-xsl docbook-xsl $ cd pkg-docbook-xsl $ cvs-buildpackage -C'pdebuild' The result is: $ dpkg-deb -c docbook-xsl_1.71.0.dfsg.1-1_all.deb | grep cmp.xsl - -rwxr-xr-x root/root 11589 2006-07-04 06:35 ./usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl W: docbook-xsl: executable-not-elf-or-script ./usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl N: N: This executable file is not an ELF format binary, and does not start N: with the #! sequence that marks interpreted scripts. It might be a sh N: script that fails to name /bin/sh as its shell. N: N: Refer to Policy Manual, section 10.4 for details. N: But when I simply build it with debuild: dpkg-deb -c docbook-xsl_1.71.0.dfsg.1-1_all.deb | grep cmp.xsl - -rw-r--r-- root/root 11589 2006-07-04 06:35 ./usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl The source should also be soon in Debian. So you can avoid cvs-buildpackage and instead use apt-get source. Or if there is any other way to help to solve this issue, please just tell me and I will do my best to provide the information you need. But this is really obscure. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages pbuilder depends on: ii cdebootstrap 0.3.13 Bootstrap a Debian system ii coreutils 5.97-5 The GNU core utilities ii debianutils 2.17.1 Miscellaneous utilities specific t ii debootstrap 0.3.3 Bootstrap a basic Debian system ii gcc 4:4.1.1-7 The GNU C compiler ii wget 1.10.2-2 retrieves files from the web Versions of packages pbuilder recommends: pn cowdancer (no description available) ii devscripts2.9.21 Scripts to make the life of a Debi ii fakeroot 1.5.10 Gives a fake root environment ii sudo 1.6.8p12-4 Provide limited super user privile - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFBf/tdg0kG0+YFBERAroSAJ43jrn1tzFKEPOKQ+FNKES0vz15zQCfQEIZ UHHQG6p60t24rRVYVpYutHc= =kylV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387064: [Pbuilder-maint] Bug#387064: File permission could be mangled
Hmm. It seems my mail did not reach the BTS. So this is the second try. Please excuse, if you get this mail twice. Am Dienstag, den 12.09.2006, 23:47 +0900 schrieb Junichi Uekawa: > Hi, > > > This is some really obscure issue. I'm maintaining docbook-xsl. I'm > > currently building version 1.71.0.dfsg.1-1. When I build this version > > with pbuilder, the file > > /usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl > > gets executable file permissions (0755). The checkout is made from CVS > > (using cvs-buildpackage). The file itself has only 0600 file permissons s/0600/0644 > > (definitely no executable tag). When I build the package with debuild, > > everything is ok. But when I use pbuilder, the file get's executable > > flags added, which results in a lintian warning. > > A few obvious things to check first: > > 1. Are you suing cowdancer ? It might be a bug in cowdancer. (I assume you > aren't) I don't use cowdancer. > 2. Does setting umask inside debian/rules help? I guess, it would (I can also exolicetly set the file permissions back to 0644 in debian/rules). But it will of course not solve the issue itself. Only the mentioned file gets executable flags. All other file permissions stay "unchanged". Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387064: [Pbuilder-maint] Bug#387064: File permission could be mangled
Am Dienstag, den 12.09.2006, 23:47 +0900 schrieb Junichi Uekawa: > Hi, > > > This is some really obscure issue. I'm maintaining docbook-xsl. I'm > > currently building version 1.71.0.dfsg.1-1. When I build this version > > with pbuilder, the file > > /usr/share/xml/docbook/stylesheet/nwalsh/slides/keynote/xsltsl/cmp.xsl > > gets executable file permissions (0755). The checkout is made from CVS > > (using cvs-buildpackage). The file itself has only 0600 file permissons s/0600/0644 > > (definitely no executable tag). When I build the package with debuild, > > everything is ok. But when I use pbuilder, the file get's executable > > flags added, which results in a lintian warning. > > A few obvious things to check first: > > 1. Are you suing cowdancer ? It might be a bug in cowdancer. (I assume you > aren't) I don't use cowdancer. > 2. Does setting umask inside debian/rules help? I guess, it would (I can also exolicetly set the file permissions back to 0644 in debian/rules). But it will of course not solve the issue itself. Only the mentioned file gets executable flags. All other file permissions stay "unchanged". Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385943: libgtk-java: Needs rebuild against libgcj7-0
Package: libgtk-java Version: 2.8.5-1 Followup-For: Bug #385943 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there someone working on this bug? I think, solving #375297, will also make this package binNMU-safe. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages libgtk-java depends on: ii libcairo-java 1.0.4-1CAIRO bindings for Java ii libglib-java 0.2.5-1GLIB bindings for Java ii libgtk-jni2.8.5-1GTK+ bindings for Java libgtk-java recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFDKnadg0kG0+YFBERAsJaAJ0d88jVSkHKq2bd3rvObz1pfFPYJQCeKaw6 zU/i/NWvM6n3+DfWikMIPRA= =j1ye -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380210: easychem crashes when exporting to eps/pdf
Am Dienstag, den 19.09.2006, 12:51 +0200 schrieb Fabian Greffrath: > Am Dienstag, den 01.08.2006, 13:24 +0200 schrieb Daniel Leidert: > > > However, the bug is fixed in upstream CVS. If you like, I can prepare a > > > patch for the package? > > > > Yes. If you know, where the issue is caused, this will ease the > > situation a lot. > > Why don't you apply the patch I sent to you? The complete patch is not necessary and also introduces a bug. Only the buffer overflow is IMO the problem. But then there is still the freeze when trying to use the export function. And I don't have a fix for this problem (and applying the "rewrite"-changes does not solve this issue). > It would be very nice to have a version of easychem in etch with pdf and > ps export working, because that is what this program is meant for (see > package description). Missing this functionality could be justification > enough for a grave bug. > If you are scared about the origin of the patch I can assure it's fresh > from upstream CVS. > > Please apply the patch so we can close this bug. I'm not the maintainer, but I prepared an NMU to fix this issue: http://svn.debian.org/wsvn/debichem/unstable/easychem/debian/ We will upload this NMU soon to the 6-days queue, if the maintainer refuses to react. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383507: Catalogs for ISO character entities should contain SYSTEM ID references
reassign 383507 sgml-data 2.0.3 thanks Seems, this bug must be filed against sgml-data, which ships /usr/share/xml/entities/xml-iso-entities-8879.1986/catalog.xml. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388336: Uninstallable due to libgcj7 -> libgcj7-0 transition
Package: libgconf-java Version: 2.12.3-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to the transition of libgcj7 -> libgcj7-0, the libgconf-java is uninstallable. Please rebuild it. Many packages had been rebuild via binNMU, so you maybe also want to find out, why not this package. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages libgconf-java depends on: ii libatk1.0-0 1.12.2-1The ATK accessibility toolkit ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libcairo-java1.0.4-1 CAIRO bindings for Java ii libcairo21.2.4-1 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.1-2 generic font configuration library ii libgcc1 1:4.1.1-13 GCC support library ii libgcj7 4.1.1-10Java runtime library for use with ii libgconf2-4 2.14.0-4GNOME configuration database syste ii libglib-java 0.2.5-1 GLIB bindings for Java ii libglib2.0-0 2.12.3-2The GLib library of C routines ii libgtk-jni 2.8.5-1 GTK+ bindings for Java ii libgtk2.0-0 2.8.20-1The GTK+ graphical user interface ii liborbit21:2.14.0-2 libraries for ORBit2 - a CORBA ORB ii libpango1.0-01.12.4-1Layout and rendering of internatio ii libx11-6 2:1.0.0-9 X11 client-side library ii libxcursor1 1.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-4 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-3 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii zlib1g 1:1.2.3-13 compression library - runtime libgconf-java recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEIRkdg0kG0+YFBERAvEQAJ9fnSPpOkkkoPcwHkf5+Mi9bLCRrQCdGnc6 yYcR3eXq+pUeHBkUNPv9QIQ= =TjzC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385670: apt is calculation wrong dependencies
Am Dienstag, den 12.09.2006, 11:55 +0200 schrieb Michael Vogt: > On Sat, Sep 02, 2006 at 04:18:18AM +0200, Daniel Leidert wrote: > > Package: apt > > Version: 0.6.45 > > Severity: minor > > Thanks for your bugreport. > > > Sometimes apt wants to install apache2-mpm-prefork libapache2-mod-php4 > > for me, when I update the system. But there is really no need to do this > > and after the upgrade I normally have to run 'apt-get remove --purge > > ...' for these two packages to remove them again. See e.g. today: > [..] > > If that happens again for you, can you please run: > # apt-get dist-upgrade -u -o Debug::pkgProblemResolver=true -o > Debug::pkgDepCache::AutoInstall=true > > and attach the result to this bugreport? Today I observe a similar behaviour (but with xserver-xorg-video-* packages and a not-going-to-be-installed xserver-xorg-video-all). The attached log: > LANG=C sudo apt-get dist-upgrade -u -o Debug::pkgProblemResolver=true -o > Debug::pkgDepCache::AutoInstall=true > Reading package lists... Done > Building dependency tree... Done > Calculating upgrade... Installing xserver-xorg-video-all as dep of > xserver-xorg > Installing xserver-xorg-video-apm as dep of xserver-xorg-video-all > Installing xserver-xorg-core as dep of xserver-xorg-video-apm > Installing xserver-xorg-video-ark as dep of xserver-xorg-video-all > Installing xserver-xorg-video-ati as dep of xserver-xorg-video-all > Installing xserver-xorg-video-chips as dep of xserver-xorg-video-all > Installing xserver-xorg-video-cirrus as dep of xserver-xorg-video-all > Installing xserver-xorg-video-cyrix as dep of xserver-xorg-video-all > Installing xserver-xorg-video-dummy as dep of xserver-xorg-video-all > Installing xserver-xorg-video-fbdev as dep of xserver-xorg-video-all > Installing xserver-xorg-video-glint as dep of xserver-xorg-video-all > Installing xserver-xorg-video-i128 as dep of xserver-xorg-video-all > Installing xserver-xorg-video-i740 as dep of xserver-xorg-video-all > Installing xserver-xorg-video-i810 as dep of xserver-xorg-video-all > Installing xserver-xorg-video-imstt as dep of xserver-xorg-video-all > Installing xserver-xorg-video-mga as dep of xserver-xorg-video-all > Installing xserver-xorg-video-neomagic as dep of xserver-xorg-video-all > Installing xserver-xorg-video-newport as dep of xserver-xorg-video-all > Installing xserver-xorg-video-nsc as dep of xserver-xorg-video-all > Installing xserver-xorg-video-nv as dep of xserver-xorg-video-all > Installing xserver-xorg-video-rendition as dep of xserver-xorg-video-all > Installing xserver-xorg-video-s3 as dep of xserver-xorg-video-all > Installing xserver-xorg-video-s3virge as dep of xserver-xorg-video-all > Installing xserver-xorg-video-savage as dep of xserver-xorg-video-all > Installing xserver-xorg-video-siliconmotion as dep of xserver-xorg-video-all > Installing xserver-xorg-video-sis as dep of xserver-xorg-video-all > Installing xserver-xorg-video-sisusb as dep of xserver-xorg-video-all > Installing xserver-xorg-video-tdfx as dep of xserver-xorg-video-all > Installing xserver-xorg-video-tga as dep of xserver-xorg-video-all > Installing xserver-xorg-video-trident as dep of xserver-xorg-video-all > Installing xserver-xorg-video-tseng as dep of xserver-xorg-video-all > Installing xserver-xorg-video-vesa as dep of xserver-xorg-video-all > Installing xserver-xorg-video-vga as dep of xserver-xorg-video-all > Installing xserver-xorg-video-via as dep of xserver-xorg-video-all > Installing xserver-xorg-video-voodoo as dep of xserver-xorg-video-all > Installing xserver-xorg-video-vmware as dep of xserver-xorg-video-all > Installing xserver-xorg-video-v4l as dep of xserver-xorg-video-all > Installing libruby1.8 as dep of ruby1.8-dev > Installing ruby1.8 as dep of irb1.8 > Installing libreadline-ruby1.8 as dep of irb1.8 > Installing libalsaplayer0 as dep of libalsaplayer-dev > Installing gnome-core as dep of gnome-office > Installing mysql-common as dep of mysql-server-5.0 > Installing mysql-client-5.0 as dep of mysql-server-5.0 > Installing libmysqlclient15off as dep of mysql-client-5.0 > Starting > Starting 2 > Investigating xserver-xorg-video-all > Package xserver-xorg-video-all has broken dep on xserver-xorg-video-apm > Considering xserver-xorg-video-apm 1 as a solution to > xserver-xorg-video-all 1 > Holding Back xserver-xorg-video-all rather than change > xserver-xorg-video-apm > Investigating conglomerate > Package conglomerate has broken dep on conglomerate-common > Try to Re-Instate conglomerate > Done > Done > The following NEW packages will be installed: > xserver-xorg-video-ark xserver-xorg-video-chips xserver-xorg-video-cirrus > xserver-xorg-video-cyrix xserver-xorg
Bug#358520: RFH: docbook, docbook-xml, sgml-data
Hello Adam, I would offer my help to maintain the packages: docbook, docbook-xml, sgml-data. I alraedy joined the Debian XML/SGML group and I currently maintain the docbook-xsl package. So if you are still interested in a co-maintainer, please tell me, which things must be done. IMHO at least both reports for sgml-data from Michael Smith should be solved before Etch is released. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383463: One further issue of a similar kind
Am Montag, den 25.09.2006, 07:08 -0700 schrieb Daniel Burrows: > On Mon, Sep 04, 2006 at 02:04:22AM +0200, Daniel Leidert <[EMAIL PROTECTED]> > was heard to say: > > Package: aptitude > > Version: 0.4.3-1 > > Followup-For: Bug #383463 > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > There is one more issue. The template to match literal can also lead > > (and leads) to issues when nesting bold and italic elements (see e.g. in > > the section "COMMAND-LINE ACTIONS" the action "download": There you can > > see, that in "=" and "/" the '>' sign ist not bold. > > The attached patch will fix this. > > Does it? I got the attached manpage when I applied it. You are right and I see the issue. What do you want: Shall '<', '>' be bold, underlined or nothing of both? Just tell me and I send you the revised patch. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383463: One further issue of a similar kind
Am Montag, den 25.09.2006, 20:27 -0700 schrieb Daniel Burrows: > On Tue, Sep 26, 2006 at 04:32:48AM +0200, Daniel Leidert <[EMAIL PROTECTED]> > was heard to say: > > Am Montag, den 25.09.2006, 07:08 -0700 schrieb Daniel Burrows: > > > On Mon, Sep 04, 2006 at 02:04:22AM +0200, Daniel Leidert <[EMAIL > > > PROTECTED]> was heard to say: > > > > Package: aptitude > > > > Version: 0.4.3-1 > > > > Followup-For: Bug #383463 > > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA1 > > > > > > > > There is one more issue. The template to match literal can also lead > > > > (and leads) to issues when nesting bold and italic elements (see e.g. in > > > > the section "COMMAND-LINE ACTIONS" the action "download": There you can > > > > see, that in "=" and "/" the '>' sign ist not bold. > > > > The attached patch will fix this. > > > > > > Does it? I got the attached manpage when I applied it. > > > > You are right and I see the issue. What do you want: Shall '<', '>' be > > bold, underlined or nothing of both? > > I'd like them to have the same attributes as the text between > them (which I guess would be underlined in this case). Ok. Try the following templates for replaceable and literal in doc/aptitude-man.xsl: > > > < > > > > > > > > > > > > > > > > > The tests were successful. I will try to find an easier way, but the above should do for the moment. Please check and tell me, if you find any issue. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347397: There is already a package in Debian for Gtk+Extra 2.0
reassign 313614 gtk+extra2 reassign 347397 gtk+extra2 thanks Hello, As far as I can see, there are packages for Gtk+Extra 2.0 in Debian: http://packages.qa.debian.org/g/gtk+extra2.html. So can we close my (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=313614) and Amaya's RFP (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347397) now? Thanks and regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389642: Wish: Could you add conflicts and replaces fields against my old private packages for Gtk+Extra2?
Package: gtk+extra2 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I want to kindly ask, if you could add replaces and conflicts fields for libgtkextra-x11-2.0-1 and libgtkextra-x11-2.0-dev against my privatly provided packages libgtkextra-2.0-1 libgtkextra-2.0-1-dev? I searched my logs and found >100 possible installations (no joke) of my packages, which I provided since June 2005 (so for more than a year). This would allow a clean update from my to the official packages. I already dropped my packages and added a note to my server [1], but there is no sane way for me to provide a clean update process to your packages. If you are not willing to add these fields, simply close this report as wontfix. [1] http://debian.wgdd.de/#news200609_2 Thanks and regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.09060920 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFGZoNdg0kG0+YFBERAjy/AKCEEDCQkbSVk+wdlkDENwywCd0IXACfWO0v P2zQdpAUIx2vIb1iWks8s5k= =+5eK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388794: fglrx driver 8.29.6 drops support for some cards
Am Dienstag, den 26.09.2006, 18:35 -0700 schrieb Max Alekseyev: > Please note that fglrx driver version 8.29.6 drops support for the following > products: > * Radeon® 8500/9000/9100/9200/9250 > * Mobility™ Radeon® 9000/9100/9200 > * Radeon® IGP 9000/9100/9200 > > So I think version 8.29.6 should be packaged separately from version 8.28.8 > rather than replace it. I don't think so. AFAIK the last 5 or 6 releases of the ATIs Linux driver had massive problems with these cards. Maybe it's cleaner to just add a note to postinst and NEWS, that the support for these cards has been finally dropped. The free drivers provide some good support for these cards. What do you think? Are there features, the free drivers cannot provide, but the proprietary can? Regards, Daniel
Bug#340713: bugs.debian.org: Done bug is shown as outstanding; attracts bogus followups
I still have some a sample of this bug. At http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=cvsweb;dist=unstable bug #247452 is shown as outstanding. But it has been closed some time ago. Maybe you can investigate it. It's an arch:all package. Thanks and regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340713: bugs.debian.org: Done bug is shown as outstanding; attracts bogus followups
Am Dienstag, den 26.09.2006, 21:19 -0700 schrieb Don Armstrong: > On Wed, 27 Sep 2006, Daniel Leidert wrote: > > I still have some a sample of this bug. At > > > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=cvsweb;dist=unstable > > > > bug #247452 is shown as outstanding. But it has been closed some time > > ago. Maybe you can investigate it. It's an arch:all package. > > It's not show that way on the page that you linked to: > > Resolved bugs -- Important bugs (1 bug) > > * #247452: Support for CGI-less execution broken > Package: cvsweb (3:3.0.0-1.1, cvsweb 3.0.5-1; fixed: cvsweb 3.0.6-1, > 3:3.0.6-1); > Severity: important; Reported by: Martin Schulze <[EMAIL PROTECTED]>; > Tags: patch > Done: Daniel Leidert <[EMAIL PROTECTED]>; Will be archived in 28 days True. I found the reason, why it was still shown as outstanding: I used "Source-Version: 3.0.6-1" instead of "Source-Version: 3:3.0.6-1", when I closed the bug. I really oversaw this mistake. I know, you or someone else mentioned this as possible cause for the "still shown as outstanding" issue. I'm sorry, but I wasn't able to write this earlier (I discovered my mistake last night, after writing the mail). Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345040: fglrx-driver: No console after logging out from Gnome/KDE/X
This bug is AFAIK known for a long time. There should be several entries in the ATI Linux driver bugzilla http://ati.cchtml.com (I read several discussions at rage3d.com, where also the related bugzilla bug-numbers were mentioned). Search there [1]. @Flavio: If you find the entry, you could mark this report as forwarded. IIRC the described issue occurred with 8.19.10, so it remained unfixed for 7 releases now. Ask ATI, when they are going to fix this _really_ annoying bug. A few workarounds are described there too. Try them. [1] Probably: http://ati.cchtml.com/show_bug.cgi?id=239 Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345040: fglrx-driver: No console after logging out from Gnome/KDE/X
This bug is AFAIK known for a long time. There should be several entries in the ATI Linux driver bugzilla http://ati.cchtml.com (I read several discussions at rage3d.com, where also the related bugzilla bug-numbers were mentioned). Search there [1]. @Flavio: If you find the entry, you could mark this report as forwarded. IIRC the described issue occurred with 8.19.10, so it remained unfixed for 7 releases now. Ask ATI, when they are going to fix this _really_ annoying bug. A few workarounds are described there too. Try them. [1] Probably: http://ati.cchtml.com/show_bug.cgi?id=239 Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#353503: New upstream version 0.7.1 available
Am Dienstag, den 08.08.2006, 20:51 +0200 schrieb Loïc Minier:
> I see you have been annoyed by these two bugs. 0.7.x are development
> releases, so I've uploaded 0.7.2 to experimental a couple of minutes
> ago. We will hopefully upload it to unstable as part of GNOME 2.16.
Thanks.
The patch to fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353503
is trivial. So if you plan to leave gnome-doc-utils 0.7.x in
experimental for a while (I don't know, when you will package GNOME 2.16
for Debian or when it is/was released) could you please be so kind to
still fix the bug? I've put the URL to the necessary patch into the
report for #353503.
("forwarded" this answer to #353503)
Regards, Daniel
Bug#382505: fo output does not respect /etc/papersize
severity 382505 wishlist merge 173093 382505 thanks Am Freitag, den 11.08.2006, 16:44 +0200 schrieb W. Borgert: > Package: docbook-xsl > Version: 1.68.1.dfsg.1-0.2 > Severity: minor > > I'm producing an FO file via: > > $ xsltproc /usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl \ > input.dbk > output.fo > Making portrait pages on USletter paper (8.5inx11in) > > Independent of the content of the system-wide configuration file > /etc/papersize (here: a4), the output is always USletter, not e.g. > ISO A4. By use "--stringparam paper.type A4" everything is OK. Ok. This is of course the "right" behaviour by design of docbook-xsl. There was already a similar wishlist report for this feature. I probably would solve this wishlist item via a paramter, that tells, what the default for paper.type and page.width.portrait should be. Probably: - intern definition (current) - /etc/papersize with LC_PAPER as default as alternative Not sure, how difficult this will be or if it will be possible in the way I think of it. It will need some sort of script to realize it. I will have a closer look, after the current dpcbook-xsl packages passed NEW. Then I also have a better overview, what issues are still outstanding. PS: A similar request was made in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=173093. Merged both requests. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382576: update-xmlcatalog: Fails to install: update-xmlcatalog: command not found
tags 382576 + pending thanks Am Freitag, den 11.08.2006, 23:29 +0200 schrieb Kurt Roeckx: > Package: docbook-xsl > Version: 1.70.1.dfsg.1-0.1 > Severity: serious > > Hi, > > Your package is failing to install with the following error: > Setting up docbook-xsl (1.70.1.dfsg.1-0.1) ... > /var/lib/dpkg/info/docbook-xsl.postinst: line 16: update-xmlcatalog: command > not found > dpkg: error processing docbook-xsl (--configure): > subprocess post-installation script returned error exit status 127 > > I'm guessing this is a missing depends. You are right. I removed a necessary line from debian/control. A new package is waiting for upload. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375503: manpages/docbook.xsl: linebreaks not preserved in environment
tags 375503 + fixed fixed-upstream thanks I cannot reproduce the described behaviour with the latest docbook-xsl 1.70.1 (NMU) packages in Sid. So I tag this bug fixed and fixed-upstream. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
