Bug#356416: marked as done (Cupsys links to /etc/xpf/xdfrc, but poppler-utils doesn't provide it)
Your message dated Mon, 16 Jul 2007 11:27:54 -0400
with message-id <1184599674.3657.77.camel@ceruleancity.mit.edu>
and subject line Bug#356416: [Debian QA] please review your old bug reports against CUPS
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Does not include /etc/xpdf/xpdfrc, supplied by dependencies of xpdf-utils
- From: EspeonEefi <espeoneefi@eep.dnsalias.org>
- Date: Sat, 11 Mar 2006 18:21:41 -0500
- Message-id: <20060311232141.28600.56705.reportbug@ceruleancity.mit.edu>
Package: poppler-utils
Version: 0.4.5-3
Severity: normal
I'm not totally sure whether this is a real bug or if this is more
cupsys' fault or not. Feel free to redirect / close as you see fit.
cupsys depends on xpdf-utils. xpdf-utils depends on xpdf-common.
xpdf-common supplies the file /etc/xpdf/xpdfrc. cupsys in turn installs
a symbolic link to /etc/xpdf/xpdfrc from /etc/cups/pdftops.conf.
poppler-utils provides xpdf-utils. Since I already have evince, I
thought I'd try installing poppler-utils intead of xpdf-utils to satisfy
cupsys' dependency.
However, poppler-utils does not provide /etc/xpdf/xpdfrc. Therefore, I
end up with the broken link /etc/cups/pdftops.conf.
I don't have anything to print right now, so I'm not sure whether this
broken link really affects anything. However, I feel like there's
something wrong somewhere here... either poppler-utils isn't providing
everything it should be providing or cupsys is depending on more aspects
of xdpf-utils than it should be depending on.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages poppler-utils depends on:
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-10 GCC support library
ii libpoppler0c2 0.4.5-3 PDF rendering library
ii libstdc++6 4.0.2-10 The GNU Standard C++ Library v3
poppler-utils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: q-funk@iki.fi, 356416-done@bugs.debian.org
- Subject: Re: Bug#356416: [Debian QA] please review your old bug reports against CUPS
- From: EspeonEefi <eefi@MIT.EDU>
- Date: Mon, 16 Jul 2007 11:27:54 -0400
- Message-id: <1184599674.3657.77.camel@ceruleancity.mit.edu>
- In-reply-to: <11fae7c70707150310k76632255w455040e257f14f8b@mail.gmail.com>
- References: <11fae7c70707150310k76632255w455040e257f14f8b@mail.gmail.com>
Package: cupsys
Version: 1.1.99.rc2-0exp1
Thanks for the reminder of this bug report. I took a look, and indeed,
this bug is fixed. I looked in the changelog.Debian and found a matching
entry for the above version number.
Cheers!
-- eefi
On Sun, 2007-07-15 at 13:10 +0300, =?UTF-8?Q? Martin-=C3=89ric?= Racine
wrote:
> Dear Debian user,
>
> You are receiving this e-mail because you have filed a bug report
> against an old version of CUPS that is no longer available in any
> current Debian release.
>
> Please review your bug report and inform us whether it still applies
> to version 1.2.7-4, as present in Debian release 4.0 (Etch), or to
> newer releases present in the testing branch.
>
> Reply directly to the bug itself at NNN@bugs.debian.org to give us your answer.
>
> See http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cupsys&repeatmerged=no
> for the whole list of bugs concerning CUPS, if you need help
> remembering which bug number was assigned to your report.
>
--- End Message ---
Reply to: