Bug#767558: dpkg says libjpeg62 version is

Package:libjpeg62-turbo Version: 1:1.3.1-10 Dist- debian sid current: 31 oct 2014 Arch- amd64 I have updated my debian sid and dselect/apt removed my cr3 version 3.0.57 because there is no libjpeg62 (>= 6b1). I tried to install cr3 version 3.0.59 and dpkg refu

Bug#767379: 767379 my package also depends on libjpeg62 (>= 6b1)

I think I have the same problem as shown in this bug. I am running amd64 sid and cannot update because of libjpeg issues. There are still problems because I use a hard to find cr3_3.0.57-15.deb outside package that dselect wants to uninstall for: Cool Reader 3.0.57-15 2012-05-29 I get this error

Bug#707757: worked around problem

I was able to work around the problem by placing the libasound2 and alsa-utils packages on hold in dselect. The dselect then upgraded the rest of my packages without choosing the liboss4 packages. I then allowed dselect to upgrade the libasound2 and alsa-utils and the problem was gone. That ti

Bug#707757: liboss4-salsa-asound2: dselect chooses liboss4 packages when nothing depends on liboss4 and packages are unwanted

Package: liboss4-salsa-asound2 Version: 4.2-build2007-2 Severity: normal Greetings Maintainer, I am trying to update my debian unstable and dselect tries to install the liboss4-salsa2 and the liboss4-salsa-asound2 packages for no reason. These packages conflict with the libasound2 and so now dse

Bug#374927: pdnsd multiple servers do make sense

Package: pdnsd Subject: multiple servers do make sense Greetings- There has been some mention of using pdnsd with bind or other dns servers: > BTW, does it make sense to have 2 name servers running in parallel ? 1. pdnsd is actually made to work with bind for example and maybe others 2. pdnsd c

Bug#374928: disregard my previous message

Ref: my message to bug 374928 sent in error Apologies- Please disregard or purge my message sent 20 Oct 06 to this bug report. My mailto typo caused my message to be sent here in error. -Captain

Bug#374928: multiple servers do make sense

Greetings- There has been some mention of using pdnsd with bind or other dns servers: > BTW, does it make sense to have 2 name servers running in parallel ? 1. pdnsd is actually made to work with bind for example and maybe others 2. pdnsd can be used to cache recent lookups from bind 3. bind can

Bug#389609: bug #389609 is not bogus after all

Greetings again- Thanks for the reply: > I don't agree. If the primary use of the package is to run a daemon, and > the daemon fails to start for *any* reason, it's better to leave the package > in an unconfigured state so that the admin can address this by hand. OK, that sounds good. My compla

Bug#389609: bug #389609 against pdnsd is bogus and attempted fix is bigger problem

Package: pdnsd Version: 1.2.4par-0.2 Arch: i386 Greetings- This bug against pdnsd is a simple misconfiguration problem and the fixes are an even bigger problem. The reason pdnsd does not start when the init.d script is called by the install script is shown to be the named already using port 53.

Bug#392535: regarding diff for 1.2.4par-0.2 NMU

Package: pdnsd Version: 1.2.4par-0.2 Port: i386 Hi- The NMU diff changes pdnsd behavior and no longer functions the same. The pdnsd is supposed to co-exist with bind9 as explained in the docs. I was running named on localhost 127.0.0.1 and pdnsd on 127.0.0.2 as described in the docs and now pdnsd