Bug#834018: owfs-fuse: No init script included
Attached init script shamelessly hacked from the owserver script. One thing I'm not sure of is whether it's right to use the binary /usr/lib/owfs/owfs as /usr/bin/$NAME is a shell script that just execs the binary while adding "-c /etc/owfs.conf" Simon Hobson MA(Oxon) MIET Projects Engineer [http://furness.net/images/fi_sig_logo.png] Email: simon.hob...@furness.net<mailto:simon.hob...@furness.net> Phone: 01229 808050 Ext 207 Furness Internet Disclaimer This email, including any attachments, is confidential and for use only by intended recipient(s) for the purpose for which it has been sent. Its contents may be privileged and if you are not the intended recipient of this email, you must not use, disseminate, print or copy this email or any part of it or take any action in reliance on it. If you have received this email in error, please contact the sender immediately by return email or telephone and delete/destroy the message. We do not accept liability for any corruption, delay, interception or unauthorised amendment of the e-mail or their consequences. Furness Internet Limited - Registered Office: 1 Trinity Enterprise Centre, Barrow in Furness, Cumbria, LA14 2PN, United Kingdom. Registered in England and Wales Company Number 3225605. Furness Internet Limited. <http://www.furness.net> owfs Description: owfs
Bug#834018: owfs-fuse: No init script included
Package: owfs-fuse Version: 2.8p15-1 Severity: wishlist Dear Maintainer, There doesn't appear to be any init script included in the package. While it's not hard to create one it does mean every user re-inventing the wheel. -- System Information: Debian Release: 7.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages owfs-fuse depends on: ii libc6 2.13-38+deb7u11 ii libfuse2 2.9.0-2+deb7u2 ii libow-2.8-15 2.8p15-1 ii owfs-common 2.8p15-1 Versions of packages owfs-fuse recommends: pn fuse-utils ii owserver2.8p15-1 Versions of packages owfs-fuse suggests: pn owftpd pn owhttpd -- no debconf information
Bug#805015: Please package version 5.6 for Wheezy
Package: php5 Version: 5.4.45-0+deb7u2 Severity: wishlist On updating to latest version, the following is reported : php5 (5.4.45-0+deb7u2) wheezy-security; urgency=medium * PHP 5.4 has reached end-of-life on 14 Sep 2015 and as a result there will be no more new upstream releases. The security support of PHP 5.4 in Debian will be best effort only and you are strongly advised to upgrade to latest stable Debian release that includes PHP 5.6 that will reach end of security support on 28 Aug 2017. As Wheezy is still a supported version, could a supported version (5.6) of php5-* be packaged for it ?
Bug#789283: Depends on SystemD component while SystemD is supposed to be optional
Package: clamav-daemon Version: 0.98.7+dfsg-0+deb8u1 It would appear that ClamD should function on a system without SystemD. http://lists.clamav.net/pipermail/clamav-users/2015-June/001590.html http://lists.clamav.net/pipermail/clamav-users/2015-June/001592.html However, the package depends on SystemD libraries, and the daemon won't start without the library being present. # /etc/init.d/clamav-daemon start [] Starting ClamAV daemon: clamd /usr/sbin/clamd: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory Suggested fix : Remove the dependency - if package systemd is installed (ie SystemD is the init system) then the library will be present, if the library isn't present then the init system is not SystemD and there should be no need to call any of it's libraries. Test for the presence of the library before attempting to use it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721481: Is this package still maintained ?
Given the time since the last update, and the number of upstream versions that have been released in that time, I think it's reasonable to ask if the Debian package is still maintained ? If it isn't then we can stop waiting for updates (and grab the upstream version) and/or perhaps look for someone else prepared to do it. But if the package is still maintained then I'd prefer to keep the system using packaged software (for the benefit of whoever has to look after it after me). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743305: clamav-freshclam: Stops downloading updates (daily.cvd) from local mirror
Overnight I left Freshclam stopped on the master, so by this morning it was 3 revisions behind. Using PrivateMirror, one slave correctly recovered once the master was updated. However, there is a logging/feedback issue with PrivateMirror. The slave was sat there reporting that : daily.cvd is up to date (version: 18732 ... This is correct in as much as the PrivateMirror had version 18732, but incorrect in that the current version at the time was 18735. Nagios correctly picked up the fact that it was 3 revisions behind. Also, the logging is a bit verbose with warnings (as reported with Logwatch) : Last Status: Reading CVD header (main.cld): WARNING: main.cld not found on remote server Reading CVD header (main.cvd): OK main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) Reading CVD header (daily.cld): WARNING: daily.cld not found on remote server Reading CVD header (daily.cvd): OK daily.cvd is up to date (version: 18732, sigs: 865515, f-level: 63, builder: neo) Reading CVD header (bytecode.cld): WARNING: bytecode.cld not found on remote server Reading CVD header (bytecode.cvd): OK bytecode.cvd is up to date (version: 236, sigs: 43, f-level: 63, builder: dgoddard) While before it just logged : Last Status: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) daily.cvd is up to date (version: 18716, sigs: 860736, f-level: 63, builder: neo) bytecode.cvd is up to date (version: 236, sigs: 43, f-level: 63, builder: dgoddard) Thanks for the offer of a build with the patch. I'm happy to test it if it helps. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743305: clamav-freshclam: Stops downloading updates (daily.cvd) from local mirror
Also, the logging is a bit verbose with warnings (as reported with Logwatch) : Last Status: Reading CVD header (main.cld): WARNING: main.cld not found on remote server ... You followed my advice and used 'PrivateMirror ip-address'? Try with 'PrivateMirror DNS-name'. From a quick look at the code, this might remove the additional messages. That was with it set as a DNS name. From the Apache logs, it clearly tries to read the header from *.cld first, and only when those aren't found does it try *.cvd. The older action (just setting DatabaseMirror myserver.domain) has it just fetch the *.cvd files. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743305: Acknowledgement (clamav-freshclam: Stops downloading updates (daily.cvd) from local mirror)
I'll need to leave it for a little while to see that it's all fine, but adding PrivateMirror seems to fix it. It wasn't in the config file - so the disabled value has to be the default that's being reported. Had a look in the changelog - found it at line 962 so it's no wonder I'd not noticed it's silent arrival. As to how I made it work, I just shared /var/lib/clamav on my 'master' server with an Apache vhost (I already have Apache running for other stuff), and set DatabaseMirror virusdb.mydomain in freshclam.conf on the other servers. I don't know where it came from, but I recall (some time ago now) finding something about how to set it up this way. It may not have been this site I was referring to back then, but it's certainly Option 2 I did : https://github.com/vrtadmin/clamav-faq/blob/master/mirrors/CvdPrivateMirror.md The same test is referenced here : http://osdir.com/ml/clamav-users/2012-07/msg00030.html This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you. Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files fromhttp://database.clamav.net to the webserver’s DocumentRoot. Add the following line to freshclam.conf on machine1.mylan. ScriptedUpdates no First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on each client so that it reads. DatabaseMirror machine1.mylan ScriptedUpdates no Over on the ClamAV-users mailing list, Shawn Webb suggested that the issue is to do with some new code intended to make downloads more robust : http://lurker.clamav.net/message/20140401.183417.1930bc2b.en.html I'm not really in a position to test the patch. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743305: clamav-freshclam: Stops downloading updates (daily.cvd) from local mirror
Package: clamav-freshclam Version: 0.98.1+dfsg-1+deb7u3 Severity: normal Dear Maintainer, I have a private mirror set up so that only one machine needs to download updates. These are then shared via Apache and other machines are configured to use this main server as their sole mirror. This was working fine with the previous version (0.97), but stopped working after the recent updates to 0.98.1 Sometimes the mirror is not up to date when the slave checks for updates, the mirror is then marked as bad in some way, and then the slave will not try and download from it again. From the freshclam log : Received signal: wake up ClamAV update process started at Tue Apr 1 13:42:23 2014 main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) Downloading daily.cvd [100%] WARNING: Mirror 172.nn.nn.nn is not synchronized. Trying again in 5 secs... ClamAV update process started at Tue Apr 1 13:42:31 2014 main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) WARNING: Can't download daily.cvd from virusdb.redacted Trying again in 5 secs... A workaround is to remove /var/lib/clamav/mirrirs.dat at which point the slave can then use the mirror again. However, this is only a crude workaround. -- Package-specific info: --- configuration --- Checking configuration files in /etc/clamav Config file: clamd.conf --- LogFile = /var/log/clamav/clamav.log LogFileUnlock disabled LogFileMaxSize = 4294967295 LogTime = yes LogClean disabled LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose disabled LogRotate = yes ExtendedDetectionInfo = yes PidFile = /var/run/clamav/clamd.pid TemporaryDirectory disabled DatabaseDirectory = /var/lib/clamav OfficialDatabaseOnly disabled LocalSocket = /var/run/clamav/clamd.ctl LocalSocketGroup = clamav LocalSocketMode = 666 FixStaleSocket = yes TCPSocket disabled TCPAddr disabled MaxConnectionQueueLength = 15 StreamMaxLength = 10485760 StreamMinPort = 1024 StreamMaxPort = 2048 MaxThreads = 12 ReadTimeout = 180 CommandReadTimeout = 5 SendBufTimeout = 200 MaxQueue = 100 IdleTimeout = 30 ExcludePath disabled MaxDirectoryRecursion = 15 FollowDirectorySymlinks disabled FollowFileSymlinks disabled CrossFilesystems = yes SelfCheck = 3600 VirusEvent disabled ExitOnOOM disabled AllowAllMatchScan = yes Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = clamav AllowSupplementaryGroups = yes Bytecode = yes BytecodeSecurity = TrustSigned BytecodeTimeout = 6 BytecodeUnsigned disabled BytecodeMode = Auto DetectPUA disabled ExcludePUA disabled IncludePUA disabled AlgorithmicDetection = yes ScanPE = yes ScanELF = yes DetectBrokenExecutables disabled ScanMail = yes ScanPartialMessages disabled PhishingSignatures = yes PhishingScanURLs = yes PhishingAlwaysBlockCloak disabled PhishingAlwaysBlockSSLMismatch disabled HeuristicScanPrecedence disabled StructuredDataDetection disabled StructuredMinCreditCardCount = 3 StructuredMinSSNCount = 3 StructuredSSNFormatNormal = yes StructuredSSNFormatStripped disabled ScanHTML = yes ScanOLE2 = yes OLE2BlockMacros disabled ScanPDF = yes ScanSWF = yes ScanArchive = yes ArchiveBlockEncrypted disabled ForceToDisk disabled MaxScanSize = 104857600 MaxFileSize = 26214400 MaxRecursion = 16 MaxFiles = 1 MaxEmbeddedPE = 10485760 MaxHTMLNormalize = 10485760 MaxHTMLNoTags = 2097152 MaxScriptNormalize = 5242880 MaxZipTypeRcg = 1048576 ScanOnAccess disabled OnAccessIncludePath disabled OnAccessExcludePath disabled OnAccessExcludeUID disabled OnAccessMaxFileSize = 5242880 DevACOnly disabled DevACDepth disabled DevPerformance disabled DevLiblog disabled DisableCertCheck disabled Config file: freshclam.conf --- LogFileMaxSize = 4294967295 LogTime disabled LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose disabled LogRotate disabled PidFile = /var/run/clamav/freshclam.pid DatabaseDirectory = /var/lib/clamav/ Foreground disabled Debug disabled AllowSupplementaryGroups disabled UpdateLogFile = /var/log/clamav/freshclam.log DatabaseOwner = clamav Checks = 48 DNSDatabaseInfo = current.cvd.clamav.net DatabaseMirror = virusdb.redacted PrivateMirror disabled MaxAttempts = 5 ScriptedUpdates disabled TestDatabases = yes CompressLocalDatabase disabled ExtraDatabase disabled DatabaseCustomURL disabled HTTPProxyServer disabled HTTPProxyPort disabled HTTPProxyUsername disabled HTTPProxyPassword disabled HTTPUserAgent disabled NotifyClamd = /etc/clamav/clamd.conf OnUpdateExecute disabled OnErrorExecute disabled OnOutdatedExecute disabled LocalIPAddress disabled ConnectTimeout = 30 ReceiveTimeout = 30 SubmitDetectionStats disabled DetectionStatsCountry disabled DetectionStatsHostID disabled SafeBrowsing disabled Bytecode = yes clamav-milter.conf not found Software settings - Version: 0.98.1 Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 JIT Database information Database directory:
Bug#727027: clamav: new upsteam version
I notice that 0.98.1 is now out. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727027: clamav: new upsteam version
Another month on, and not even a reply to the bug ticket ? If the package is no longer maintained, or there's some other serious problem, then it would be nice to know - rather than just guessing and hoping that there's still someone there ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727027: clamav: new upsteam version
Can I bump this ? I notice that 0.98 hasn't even appeared in Sid yet, and it's now several weeks since it appeared upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718625: netdisco-common: Debian package (1.0) is now several versions behind upstream (1.3)
Package: netdisco-common Version: 1.0-3 Severity: important Dear Maintainer, The upstream package is now up to version 1.3.1, while the Debian package is still at 1.0 which is several years old. Is an updated Debian package likely to appear in the forseeable future, or would users be better of doing a manual install from the upstream sources ? -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages netdisco-common depends on: ii libdbd-pg-perl 2.19.2-2 ii libdbi-perl1.622-1 ii libsnmp-info-perl 2.06-1 ii perl 5.14.2-21 netdisco-common recommends no packages. Versions of packages netdisco-common suggests: ii netdisco-backend 1.0-3 ii netdisco-frontend 1.0-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706474: [Pkg-openssl-devel] Bug#706474: libssl1.0.0: saslauthd fails with PAM unable to dlopen(pam_mysql.so)
All I did was upgrade to the latest packages. I'm using : deb http://ftp.uk.debian.org/debian wheezy main contrib non-free deb http://ftp.uk.debian.org/debian wheezy-updates main contrib non-free deb http://security.debian.orgwheezy/updates main non-free #apt-get update apt-get upgrade .. Preparing to replace libssl1.0.0:i386 1.0.1c-4 (using .../libssl1.0.0_1.0.1e-2_i386.deb) ... SASL auth now fails : PAM unable to dlopen(pam_mysql.so): /usr/lib/i386-linux-gnu/i686/cmov/libcrypto.so.1.0.0: version `OPENSSL_1.0.1d' not found (required by /usr/lib/i386-linux-gnu/i686/cmov/libssl.so.1.0.0) # strings libcrypto.so.1.0.0 | grep OPENSSL_1 OPENSSL_1.0.0 OPENSSL_1.0.1 OPENSSL_1.0.1d # strings libssl.so.1.0.0 | grep OPENSSL_1 OPENSSL_1.0.0 OPENSSL_1.0.1 OPENSSL_1.0.1d # dpkg -i ~/libssl1.0.0_1.0.1c-4_i386.deb dpkg: warning: downgrading libssl1.0.0:i386 from 1.0.1e-2 to 1.0.1c-4 SASL auth now works # strings libcrypto.so.1.0.0 | grep OPENSSL_1 OPENSSL_1.0.0 OPENSSL_1.0.1 # strings libssl.so.1.0.0 | grep OPENSSL_1 OPENSSL_1.0.0 OPENSSL_1.0.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706474: [Pkg-openssl-devel] Bug#706474: libssl1.0.0: saslauthd fails with PAM unable to dlopen(pam_mysql.so)
Can you try restarting saslauthd? I'm pretty certain I'd done that before while testing various things out. I've rebooted the machine and now it works. My best guess is that it's linked in an other way to libcrypto.so.1.0.0 ... That would seem to be a logical explanation. Anyway, it's working now, sorry for taking up your time. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706474: libssl1.0.0: saslauthd fails with PAM unable to dlopen(pam_mysql.so)
Package: libssl1.0.0 Version: 1.0.1e-2 Severity: important Dear Maintainer, With version 1.0.1e-2 installed, authentication fails. Postfix is configured to use PAM to authenticate users against a MySQL database with libsasl2-2, libsasl2-modules (both version 2.1.25.dfsg1-6), and courier-authdaemon, courier-authlib, courier-authlib-mysql (all version 0.63.0-6+b1). Downgrading to version 1.0.1c-4 resolves the issue. The following is logged in auth.log when debugging turned up : saslauthd[2652]: PAM unable to dlopen(pam_mysql.so): /usr/lib/i386-linux-gnu/i686/cmov/libcrypto.so.1.0.0: version `OPENSSL_1.0.1d' not found (required by /usr/lib/i386-linux-gnu/i686/cmov/libssl.so.1.0.0) saslauthd[2652]: PAM adding faulty module: pam_mysql.so saslauthd[2652]: DEBUG: auth_pam: pam_authenticate failed: Module is unknown saslauthd[2652]: do_auth : auth failure: [user=*] [service=smtp] [realm=*] [mech=pam] [reason=PAM auth error] -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libssl1.0.0 depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii multiarch-support 2.13-38 ii zlib1g 1:1.2.7.dfsg-13 libssl1.0.0 recommends no packages. libssl1.0.0 suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698422: amavisd-new: Postfix Queue-ID missing from split log entries for messages with multiple recipients
Package: amavisd-new Version: 1:2.7.1-2 Severity: normal Tags: upstream There is an issue with log entries for messages with a large number of recipients which impacts on log analysys - I believe this will be an upstream issue. For messages with a small number of recipients, log entries are of the form : preamble Amavis result from - to[,to]... Queue-ID: ..., Message-ID: ... ... For longer lists of recipients, the log entry gets split : preamble Amavis result from - to,to,... preamble to[,to]... Queue-ID: ..., Message-ID: ... ... Normally, when investigating issues it is sufficient to just grep something mail.log where something is often the Queue ID. Where the log entry is split, this fails. Eg : grep Queue ID mail.log fails to show the Amavis result (Spammy, Clean, whatever). grep Spammy mail.log fails to show the queue ID. While it's not hard to copy/paste and grep for the preamble, it means extra steps and it's hard enough teaching first line to grep queue ID mail.log ! Would it be possible to include the Queue ID in all log entires, even when they have been split ? -- System Information: Debian Release: wheezy/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages amavisd-new depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.46 ii file5.11-2 ii libarchive-zip-perl 1.30-6 ii libberkeleydb-perl 0.51-1 ii libcompress-raw-zlib-perl 2.052-1 ii libconvert-tnef-perl0.17-11 ii libconvert-uulib-perl 1:1.4~dfsg-1+b1 pn libdigest-md5-perl none ii libio-stringy-perl 2.110-5 ii libmail-dkim-perl 0.39-1 ii libmailtools-perl 2.09-1 pn libmime-base64-perl none ii libmime-tools-perl 5.503-1 ii libnet-server-perl 2.006-1 ii libunix-syslog-perl 1.1-2+b2 ii pax 1:20120606-2 ii perl [libtime-hires-perl] 5.14.2-16 ii perl-modules [libarchive-tar-perl] 5.14.2-16 Versions of packages amavisd-new recommends: ii altermime 0.3.10-7 pn libnet-patricial-perl none ii ripole 0.2.0+20081101.0215-1 Versions of packages amavisd-new suggests: pn apt-listchanges none ii arj 3.10.22-10 pn cabextract none ii clamav 0.97.6+dfsg-1 ii clamav-daemon0.97.6+dfsg-1 ii cpio 2.11-8 pn dspamnone pn lha none pn lhasanone pn libauthen-sasl-perl none ii libdbi-perl 1.622-1 ii libmail-dkim-perl0.39-1 pn libnet-ldap-perl none pn libsnmp-perl none pn lzop none ii nomarch 1.4-3 pn p7zipnone pn rpm none ii spamassassin 3.3.2-4 pn unrarnone pn unrar-free none ii zoo 2.10-27 -- Configuration Files: /etc/amavis/conf.d/50-user changed [not included] /etc/cron.daily/amavisd-new [Errno 2] No such file or directory: u'/etc/cron.daily/amavisd-new' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669370: fixed in clamav 0.97.5+dfsg-3~squeeze1
Message dated 13th July says 0.97.5+dfsg-3~squeeze1 is due to be installed in the Debian FTP archive. Looking in http://ftp.debian.org/debian/pool/main/c/clamav/ shows the files to be there, however they are not showing up in package search : http://packages.debian.org/search?suite=allsearchon=nameskeywords=clamav shows Squeeze stable as still having version 0.97.3+dfsg-1~squeeze1. http://packages.debian.org/search?suite=squeeze-updatessearchon=nameskeywords=clamav says there's nothing in squeeze updates. Is this just a case of it not having been promoted to the appropriate package list(s) ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660882: Acknowledgement (Atalkd fails in Xen DomU - Can't configure multicast)
I have now built a test host with Wheezy Xen 4.1. With the same Squeeze guest, the problem persists. Host is now : Debian Wheezy Kernel : Linux saffy 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 GNU/Linux libc6: 2.13-27 libxen-4.1 4.1.2-2 libxenstore3.0 4.1.2-2 xen-hypervisor-4.1-amd64 4.1.2-2 xen-tools4.2.1-1 xen-utils-4.14.1.2-2 xen-utils-common 4.1.2-1 xenstore-utils 4.1.2-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660882: Atalkd fails in Xen DomU - Can't configure multicast
Further update. I've upgraded the client to Wheezy as well (same kernel and libc6 as host). Still no change. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660768: Atalkd fails in Xen DomU - Can't configure multicast
I believe it is not really a bug, but a limitation: Netatalk requires multicast which some NICs (virtual or not) perhaps do not provide. I thought it might be something like that - but figured it was probably better to get that from you guys before raising it as a bug against Xen and see what they make of it. I'll give it a couple of days and see if anyone else has any comments, then I'll raise a ticket against Xen. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660882: Atalkd fails in Xen DomU - Can't configure multicast
Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal See also, bug 660768 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660768 atalkd appears to be unable to open virtual network interfaces when run in a Xen PV guest. With nothing set in atalkd.conf, it reports : eth0: disabled. atalkd: zero interfaces, exiting. Adding eth0 to atalkd.conf results in : eth0: Invalid argument Can't configure multicast. eth0: disabled. atalkd: zero interfaces, exiting. If the entire VM is moved to a physical host (ie running native with no virtualisation), then atalkd works as expected. This physical machine has a GeForce chipset and the forcedeth network driver. the only changes were to use eth1 instead of eth0, and make the system bootable with GRUB. Suggestion from netatalk maintainer is that atalkd requires multicast support - but this is not provided by Xen virtual NIC/driver. For the Xen host : Debian: Squeeze Kernel : Linux serge 2.6.32-5-xen-amd64 #1 SMP Mon Jan 16 20:48:30 UTC 2012 x86_64 GNU/Linux LibC6: 2.11.3-2 libxenstore3.0 4.0.1-4 xen-hypervisor-4.0-amd64 4.0.1-4 xen-utils-4.04.0.1-4 xen-utils-common 4.0.0-1 xenstore-utils 4.0.1-4 For the guest (DomU) Debian: Squeeze Kernel : Linux newpatsy 2.6.32-5-xen-amd64 #1 SMP Mon Jan 16 20:48:30 UTC 2012 x86_64 GNU/Linux LibC6: 2.11.3-2 -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660768: Atalkd fails in Xen DomU - Can't configure multicast
Package: netatalk Version: 2.2.1-1 Severity: normal atalkd appears to be unable to open virtual network interfaces when run in a Xen PV guest. I don't know if it's a Xen or Netatalk problem. With nothing set in atalkd.conf, it reports : eth0: disabled. atalkd: zero interfaces, exiting. Adding eth0 to atalkd.conf results in : eth0: Invalid argument Can't configure multicast. eth0: disabled. atalkd: zero interfaces, exiting. This happens with netatalk from stable or testing. If the entire VM is moved to a physical host (ie running native with no virtualisation), then atalkd works as expected. This physical machine has a GeForce chipset and the forcedeth network driver. the only changes were to use eth1 instead of eth0, and make the system bootable with GRUB. Debian: Squeeze Kernel : Linux newpatsy 2.6.32-5-xen-amd64 #1 SMP Mon Jan 16 20:48:30 UTC 2012 x86_64 GNU/Linux LibC6: 2.11.3-2 For the Xen host : Debian: Squeeze Kernel : Linux serge 2.6.32-5-xen-amd64 #1 SMP Mon Jan 16 20:48:30 UTC 2012 x86_64 GNU/Linux LibC6: 2.11.3-2 libxenstore3.0 4.0.1-4 xen-hypervisor-4.0-amd64 4.0.1-4 xen-utils-4.04.0.1-4 xen-utils-common 4.0.0-1 xenstore-utils 4.0.1-4 -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626358: logwatch: Upgrade overwrites default config without prompting
Package: logwatch Version: 7.3.6.cvs20080702-2lenny1 Severity: normal When package is upgraded, /usr/share/logwatch/default.conf/logwatch.conf is silently overwritten, thus losing customisations. Most other packages prompt the user for options (overwrite/keep installed/compare) when a config file has been modified since installation. -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages logwatch depends on: ii perl 5.10.0-19lenny3 Larry Wall's Practical Extraction ii postfix [mail-transport- 2.5.5-1.1 High-performance mail transport ag Versions of packages logwatch recommends: pn libdate-manip-perlnone (no description available) Versions of packages logwatch suggests: pn fortune-mod none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
