Bug#684588: unblock: thinkfan/0.8.1-1 (pre-approval)
On Sun, Aug 12, 2012 at 10:11:22PM +0100, Adam D. Barratt wrote: On Sat, 2012-08-11 at 16:26 +0200, Evgeni Golov wrote: I would like to upload thinkfan/0.8.1-1 to unstable and get it into Wheezy with your help :) 0.8.1 is a bugfix release (diff is attached) which mainly fixes a RC bug: #684315 Tries to write level 0 to sysfs, not just 0. The only hunk that is not for that bug is the following: [...] → It's pretty safe not to include it, but it's a bug :) Would you be okay with uploading 0.8.1-1 to unstable and unblocking it? Or should I prepare a 0.8.0-2 instead, with the patch w/o parser.c? If the upload happens fairly quickly, I'd be happy with including both sets of changes; thanks. Thanks for the quick (p)review. thinkfan hit unstable in the meantime: Date: Mon, 13 Aug 2012 05:32:39 + From: Debian FTP Masters ftpmas...@ftp-master.debian.org To: Evgeni Golov evg...@debian.org Subject: thinkfan_0.8.1-1_amd64.changes ACCEPTED into unstable Thanks again Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684520: debootstrap: package validation fails when running on Android+busybox
Le vendredi, 10 août 2012 18.56:33, Hans-Christoph Steiner a écrit : Package: debootstrap Version: 1.0.42 Severity: normal Tags: upstream https://github.com/guardianproject/lildebi When using debootstrap 1.0.42 in the Android app Lil' Debi, it runs, gets the Release info, then starts downloading packages, but then fails on validation. It seems to be failing in verify_checksum() but we're not positive about that. The failure seems to be caused by the wrong checksums being compared, here's a debug print: I: Validation failed: 250368, 250368, edfaffdb7beea7e0e5db61c3b1b210e9, fc4c586d12c9e5e16edc707ec920f2f2e7122689e206fda78374886e7aecfaba Without diving much into the issue at hand, this debug line seems to be comparing apples and oranges (like sha1sum and sha512sum). Do you have all sha* utils available ? (Just wild-guessing…) Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533287: [PATCH v2] Only the owner of a configuration file should modify it
Policy §10.7.4 explains: If it is desirable for [...] packages to share a configuration file and for all of the related packages to be able to modify that configuration file, then the following should be done: [...] ii. The owning package should also provide a program that the other packages may use to modify the configuration file. iii. The related packages must use the provided program to make any desired modifications to the configuration file. [...] This advice suggests a few questions. Are these requirements release-critical? (Item iii says must but the opening to the list says it describes what should be done.) Is it be more important (must vs should) that packages use the provided program than that the program exist? Use should instead of must throughout and state clearly that packagers should not directly modify other packages' configuration files regardless of whether a tool for indirectly modifying is provided. With wording help from Russ. Closes: #533287 --- Russ Allbery wrote: This generally looks good, but here you remove the definition of owning package: Thanks. Here's an updated patch. policy.sgml | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/policy.sgml b/policy.sgml index 8c654d1..55f19a4 100644 --- a/policy.sgml +++ b/policy.sgml @@ -8445,14 +8445,16 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq /p p + Only the emowner/em of a configuration file should + modify it directly. If it is desirable for two or more related packages to share a configuration file emand/em for all of the related packages to be able to modify that configuration - file, then the following should be done: + file, then: enumlist compact=compact item One of the related packages (the owning package) - will manage the configuration file with maintainer + manages the configuration file with maintainer scripts as described in the previous section. /item item @@ -8461,10 +8463,10 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq configuration file. /item item - The related packages must use the provided program + The related packages should use the provided program to make any desired modifications to the configuration file. They should either depend on - the core package to guarantee that the configuration + the owning package to guarantee that the configuration modifier program is available or accept gracefully that they cannot modify the configuration file if it is not. (This is in addition to the fact that the -- 1.7.9.6 (Apple Git-31.1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571776: document symbols
Hi, On Sun, 12 Aug 2012, Russ Allbery wrote: I'm looking for seconds so that we can finally merge this monster. Presented as a diff since that was the request last time, but the branch has also been pushed to the Policy Git repository, so if you want to review it various other ways, you can start at: Seconded. Thank you very much for this work! Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ signature.asc Description: Digital signature
Bug#681564: Info received (Bug#681564: Acknowledgement (webgui: apache2 segfaults))
also... root@debian:~# ./test.sh GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/apache2...(no debugging symbols found)...done. (gdb) set args -X (gdb) run Starting program: /usr/sbin/apache2 -X [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Mon Aug 13 16:26:54 2012] [warn] NameVirtualHost *:80 has no VirtualHosts Loading webgui.conf Starting WebGUI 7.10.24 Program received signal SIGSEGV, Segmentation fault. 0x7fffe7d4eb60 in ?? () (gdb) bt #0 0x7fffe7d4eb60 in ?? () #1 0x74149bac in Perl_convert () from /usr/lib/libperl.so.5.14 #2 0x741518b6 in Perl_utilize () from /usr/lib/libperl.so.5.14 #3 0x7417f487 in Perl_yyparse () from /usr/lib/libperl.so.5.14 #4 0x741f7bb2 in ?? () from /usr/lib/libperl.so.5.14 #5 0x7420204f in Perl_pp_require () from /usr/lib/libperl.so.5.14 #6 0x741bd9b6 in Perl_runops_standard () from /usr/lib/libperl.so.5.14 #7 0x74158e06 in Perl_eval_sv () from /usr/lib/libperl.so.5.14 #8 0x744a94b6 in modperl_require_module () from /usr/lib/apache2/modules/mod_perl.so #9 0x744a0fb7 in ?? () from /usr/lib/apache2/modules/mod_perl.so #10 0x741f3cdc in Perl_leave_scope () from /usr/lib/libperl.so.5.14 #11 0x7415e29a in perl_parse () from /usr/lib/libperl.so.5.14 #12 0x744a1220 in modperl_startup () from /usr/lib/apache2/modules/mod_perl.so #13 0x744a11b0 in modperl_startup () from /usr/lib/apache2/modules/mod_perl.so #14 0x744a15d5 in modperl_init () from /usr/lib/apache2/modules/mod_perl.so #15 0x744a172b in modperl_hook_init () from /usr/lib/apache2/modules/mod_perl.so #16 0x5559af11 in ap_run_open_logs () #17 0x55585e8e in main () (gdb) On 09/08/12 11:03, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Ernesto Hernández-Novich (USB) e...@usb.ve If you wish to submit further information on this problem, please send it to 681...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684694: emacs24: CVE-2012-3479: GNU Emacs file-local variables
Package: emacs24 Version: 24.1+1-4 Severity: important Tags: security, fixed-upstream Paul Ling has found a security flaw in the file-local variables code in GNU Emacs. When the Emacs user option `enable-local-variables' is set to `:safe' (the default value is t), Emacs should automatically refuse to evaluate `eval' forms in file-local variable sections. Due to the bug, Emacs instead automatically evaluates such `eval' forms. Thus, if the user changes the value of `enable-local-variables' to `:safe', visiting a malicious file can cause automatic execution of arbitrary Emacs Lisp code with the permissions of the user. The bug is present in Emacs 23.2, 23.3, 23.4, and 24.1. More details: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155 http://www.openwall.com/lists/oss-security/2012/08/13/1 http://www.openwall.com/lists/oss-security/2012/08/13/2 I haven't manually verified this in Debian packages. Please ask in case you want me to do it. - Henri Salo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684695: emacs23: CVE-2012-3479: GNU Emacs file-local variables
Package: emacs23 Version: 23.2+1-7 Severity: important Tags: security, fixed-upstream Paul Ling has found a security flaw in the file-local variables code in GNU Emacs. When the Emacs user option `enable-local-variables' is set to `:safe' (the default value is t), Emacs should automatically refuse to evaluate `eval' forms in file-local variable sections. Due to the bug, Emacs instead automatically evaluates such `eval' forms. Thus, if the user changes the value of `enable-local-variables' to `:safe', visiting a malicious file can cause automatic execution of arbitrary Emacs Lisp code with the permissions of the user. The bug is present in Emacs 23.2, 23.3, 23.4, and 24.1. More details: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155 http://www.openwall.com/lists/oss-security/2012/08/13/1 http://www.openwall.com/lists/oss-security/2012/08/13/2 I haven't manually verified this in Debian packages. Please ask in case you want me to do it. - Henri Salo ps. another bug-report for emacs24 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684339: new upstream version (v0.1.99)
On Sun, 2012-08-12 at 21:13 -0700, Jeff Breidenbach wrote: Pascal, libwebp-0.1.99 bumps the soname from 2 to 3. Are you SURE you want that and are ready for this to ship? Soname changes are a big deal out here in packaging land. soname bumps are good when they mean that you can coinstall differn't incompatible versions. There are only three reverse depends right now: # grep-dctrl -FBuild-Depends libwebp-dev -sPackage /var/lib/apt/lists/*Sources Package: chromium-browser Package: leptonlib Package: sdl-image1.2 It would be a good idea to do a test build with leptonlib and sdl-image1.2, chromium isn't even using it right now, as was why this bug was opened. After doing a test build file the process here to get a go-ahead http://wiki.debian.org/Teams/ReleaseTeam/Transitions those two packages will have to be rebuilt on all architectures, with the new library after it is uploaded, to complete the transition. I'm not exactly how this works now in the world of multi-arch influencing the effectiveness of binNMUs. Shawn, I have the package built and ready, awaiting response from Pascal before submitting. -Jeff -- -Shawn Landden -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680655: scim and im-config
Hi Osamu Aoki, On Sun, Aug 12, 2012 at 6:57 PM, Osamu Aoki os...@debian.org wrote: Hi Andrew, I have just uploaded experimental im-config package. http://packages.debian.org/source/experimental/im-config This should fix some initialization problem related to dbus. Do you still have problem reported in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680655 Hi Tz-Huan Huang, This Bug#680655 is somehow related to im-config with scim. With recent multiarch and major system updates of scim, I am not sure what is happening. Can you check this since this seems to be scim related. Since scim doesn't use dbus, it might not related to the initialization problem. I'll try to figure it out, thanks. Tz-Huan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684339: new upstream version (v0.1.99)
Hi Jeff, On Sun, Aug 12, 2012 at 9:13 PM, Jeff Breidenbach j...@jab.org wrote: Pascal, libwebp-0.1.99 bumps the soname from 2 to 3. Are you SURE you want that and are ready for this to ship? Soname changes are a big deal out here in packaging land. well, we must bump it because ABI changed quite a lot (and may change again for 0.2.0). Better be safe... Shawn, I have the package built and ready, awaiting response from Pascal before submitting. As mentioned, we're going to do 0.2.0 very soon after... Pascal (mostly OOO ;)) -Jeff
Bug#684696: apcupsd loses communication with UPS during the power failure
Package: apcupsd Version: 3.14.10-2 Severity: important Hello Sorry my bad English And again found him only after the appearance of voltage in the network. Thus, does not work shutdown of the batteries discharge. APC SUA750 usb -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apcupsd depends on: ii libc6 2.13-33 ii libgcc1 1:4.7.1-2 ii libwrap0 7.6.q-23 Versions of packages apcupsd recommends: pn apcupsd-doc none Versions of packages apcupsd suggests: pn apcupsd-cgi none ii udev 175-3.1 -- Configuration Files: /etc/apcupsd/apcupsd.conf changed: UPSNAME SUA750I UPSCABLE usb UPSTYPE usb DEVICE LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 5 MINUTES 3 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER off EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 50 UPSCLASS standalone UPSMODE disable STATTIME 72200 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 72200 /etc/default/apcupsd changed: APCACCESS=/sbin/apcaccess ISCONFIGURED=yes -- 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#684364: target: reports vfs_writev() returned -28 on iscsi activity
Hello, Dne Sunday 12 August 2012 23:09:35, Ben Hutchings napsal(a): On Thu, 2012-08-09 at 09:40 +0200, root wrote: Package: linux-image-3.2.0-3-amd64 Version: 3.2.21-3 Severity: normal Hello, i'm using this virtual machine to export iscsi targets for windows machines to backup. It has 620GB btrfs partition with 550GB iscsi file_io LUN exported. I'm using btrfs snapshots to transport (consistent copy of) this big file to secondary backup storage (qnap and usb disk) - it takes around 12 hours to transport - thats reason to use snapshots. Everything was working fine, until i run out of space on btrfs (because of snapshot and fullbackup from windows combination). Since than, i have created fresh filesystem and create empty new file to export over iscsi. Now, around 250GB of writen data do iscsi file, kern.log starts to fill with these messages vfs_writev() returned -28 It keeps to show on every access to iscsi (even rescan disk operation in windows triggers it) Any read access may change the image file's access time (atime) if you don't use the 'noatime' mount option. On btrfs, metadata changes may allocate more disk space. You are right, i forgot noatime option on mount I was suspecting btrfs, but there is no oops in kern.log. I tried to google this error and found nothing relevant. Error 28 is ENOSPC: No space left on device. I tried to reset everything (new filesystem, empty file, remove/add target from windows) and this errors comes back after writing approx. 250GB of data. (Before problem, file was filled to around 540GB). Size now: # du -cms iscsiSBS 244561 iscsiSBS [...] What does 'btrfs filesystem df /btrfs' say (substitute the actual mountpoint for the btrfs volume)? It said (i saved this before running balance) Data: total=578.01GB, used=263.03GB System, DUP: total=8.00MB, used=72.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.73GB, used=1.03GB Metadata: total=8.00MB, used=0.00 I tried this - is it ok, it doesn't free used after rm? # dd if=/dev/zero of=/mnt/tmp/1 bs=100M count=10 # rm /mnt/tmp/1 # btrfs filesystem df /mnt/tmp/ Data: total=1.01GB, used=0.00 System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.00GB, used=1.27MB Metadata: total=8.00MB, used=0.00 # dd if=/mnt/backupWin/iscsi/iscsiSBS of=/mnt/tmp/1 bs=100M count=10 10+0 records in 10+0 records out 1048576000 bytes (1.0 GB) copied, 22.0851 s, 47.5 MB/s # btrfs filesystem df /mnt/tmp/ Data: total=1.01GB, used=1000.00MB System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.00GB, used=1.41MB Metadata: total=8.00MB, used=0.00 # rm /mnt/tmp/1 # btrfs filesystem df /mnt/tmp/ Data: total=1.01GB, used=1000.00MB System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.00GB, used=1.41MB Metadata: total=8.00MB, used=0.00 # dd if=/mnt/backupWin/iscsi/iscsiSBS of=/mnt/tmp/1 bs=100M count=90 dd: writing `/mnt/tmp/1': No space left on device 82+0 records in 81+0 records out 8560574464 bytes (8.6 GB) copied, 280.973 s, 30.5 MB/s # btrfs filesystem df /mnt/tmp/ Data: total=7.97GB, used=7.97GB System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.00GB, used=11.39MB Metadata: total=8.00MB, used=0.00 # rm /mnt/tmp/1 # btrfs filesystem df /mnt/tmp/ Data: total=7.97GB, used=5.65GB System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.00GB, used=8.06MB Metadata: total=8.00MB, used=0.00 Ben. Libor signature.asc Description: This is a digitally signed message part.
Bug#682280: sync-ui does not remember the default service
On Sat, 2012-08-11 at 21:34 +0200, Tino Keitel wrote: On Mon, Aug 06, 2012 at 20:47:18 +0200, Tino Keitel wrote: On Mon, Aug 06, 2012 at 17:50:04 +0200, Patrick Ohly wrote: [...] Tino, can you check whether your upcoming update fixes this issue? If it doesn't, then perhaps try switching to GIO D-Bus. Actually, I am surprised that it is not used by default already. configure should pick it when gio-2.0 = 2.30. Do you perhaps configure with --without-gio-dbus? Could it be that this is caused by a missing build depencency? At least the build log looks fine: https://buildd.debian.org/status/fetch.php?pkg=syncevolutionarch=i386ver=1.2.99.1-1stamp=1341042365 The configure summary shows this: GIO GDBus: yes Hi Patrick, did you see something obvious in the build log? I double-checked. Debian's syncevo-dbus-server does use GIO D-Bus; what I saw must have been an indirect call to libdbus (happens later, via gvfs). I think I got the same issue with 1.2.99.4 (can't really check as I'm on vacation). I'll have another look. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684697: clamav: Scan error bad format or broken data
Package: clamav Version: 0.97.5+dfsg-3~squeeze1 Severity: normal clamscan error message display is CL_EFORMAT: Bad format or broken data ERROR. I scanned file. (display error message) /usr/bin/arj /usr/bin/clang /usr/lib/mozc/mozc_server Thanks. Reference: https://bugzilla.clamav.net/show_bug.cgi?id=5252 https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1015405 -- 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 = 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 = 4294967295 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 = 650 VirusEvent disabled ExitOnOOM disabled Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = clamav AllowSupplementaryGroups = yes Bytecode = yes BytecodeSecurity = TrustSigned BytecodeTimeout = 6 BytecodeUnsigned disabled BytecodeMode = Auto DetectPUA = yes ExcludePUA disabled IncludePUA = NetTool, PWTool, Spy, Scanner, RAT, Packed, P2P, IRC, Server, Script, Tool AlgorithmicDetection = yes ScanPE = yes ScanELF = yes DetectBrokenExecutables = yes ScanMail = yes ScanPartialMessages disabled PhishingSignatures = yes PhishingScanURLs = yes PhishingAlwaysBlockCloak = yes PhishingAlwaysBlockSSLMismatch = yes HeuristicScanPrecedence = yes StructuredDataDetection disabled StructuredMinCreditCardCount = 3 StructuredMinSSNCount = 3 StructuredSSNFormatNormal = yes StructuredSSNFormatStripped disabled ScanHTML = yes ScanOLE2 = yes OLE2BlockMacros = yes ScanPDF = yes ScanArchive = yes ArchiveBlockEncrypted = yes MaxScanSize = 104857600 MaxFileSize = 26214400 MaxRecursion = 16 MaxFiles = 1 ClamAuth disabled ClamukoScanOnAccess disabled ClamukoScannerCount = 3 ClamukoScanOnOpen disabled ClamukoScanOnClose disabled ClamukoScanOnExec disabled ClamukoIncludePath disabled ClamukoExcludePath disabled ClamukoExcludeUID disabled ClamukoMaxFileSize = 5242880 DevACOnly disabled DevACDepth disabled DevLiblog disabled Config file: freshclam.conf --- LogFileMaxSize = 4294967295 LogTime = yes LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose = yes 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 = 86 DNSDatabaseInfo = current.cvd.clamav.net DatabaseMirror = db.jp.clamav.net MaxAttempts = 10 ScriptedUpdates = yes 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 = 120 ReceiveTimeout = 120 SubmitDetectionStats disabled DetectionStatsCountry disabled DetectionStatsHostID disabled SafeBrowsing disabled Bytecode = yes Config file: clamav-milter.conf --- LogFile = /var/log/clamav/clamav-milter.log LogFileUnlock disabled LogFileMaxSize = 4294967295 LogTime = yes LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose = yes PidFile = /var/run/clamav/clamav-milter.pid TemporaryDirectory = /var/spool/clamav-milter FixStaleSocket = yes MaxThreads = 10 ReadTimeout = 120 Foreground disabled User = clamav AllowSupplementaryGroups = yes MaxFileSize = 104857600 ClamdSocket = unix:/var/run/clamav/clamd.ctl MilterSocket = /var/spool/postfix/cvrsockd/lvpmqnz.ctl MilterSocketGroup = clamav MilterSocketMode = 666 LocalNet disabled OnClean = Accept OnInfected = Reject OnFail = Defer RejectMsg disabled AddHeader = Replace ReportHostname = UnknownHostName VirusAction disabled Chroot disabled Whitelist disabled SkipAuthenticated disabled LogInfected = Full LogClean = Full Software settings - Version: 0.97.5 Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 JIT Database information Database directory: /var/lib/clamav main.cvd: version 54, sigs: 1044387, built on Tue Oct 11 23:34:20 2011 bytecode.cld: version 188, sigs: 38, built on Fri Jul 13 00:48:52 2012 daily.cld: version 15244,
Bug#684698: ifupdown: ifup incorrectly ups vlan interfaces using ip link
Package: ifupdown Version: 0.7.1 Severity: important Tags: upstream Dear Maintainer, I wrote in my /etc/network/interfaces: auto eth0.0201 iface eth0.0201 inet static address 10.0.1.1 netmask 255.255.0.0 vlan_raw_device eth0 and execute ifup eth0.0201 but after this I have this in /proc/net/vlan/config VLAN Dev name | VLAN ID Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID eth0.0201 | 129 | eth0 This is looks strange for me and after strace ifup I got this call from ifup execve(/sbin/ip, [ip, link, add, link, eth0, name, eth0.0201, type, vlan, id, 0201], [/* 1 var */]) = 0 Obviously, /sbin/ip from iproute package got vlan number 0201 as octal number and after this pre-ip/vlan executes vconfig for the same target, but it can't up vlan interfaces with the same name eth0.0201 and fails. I don't know, which bug is it (ifup or ip) but it is inappropriable. Thank you for responding. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (300, 'oldstable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.4.3 ii initscripts 2.88dsf-29 ii iproute 20120521-3 ii libc62.13-33 ii lsb-base 4.1+Debian7 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5 ii net-tools 1.60-24.1 ii ppp2.4.5-5.1+b1 pn rdnssd none -- 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#684569: linux-image-3.5-trunk-686-pae: microcode module loaded on Celeron CPU
Dear Andi, thank you for your response. Am Sonntag, den 12.08.2012, 06:10 -0700 schrieb Andi Kleen: On Sat, Aug 11, 2012 at 03:17:19PM +0200, Paul Menzel wrote: This really depends on what operations you want to do, and how buggy the CPU microcode installed by the BIOS is. If you care that much about it, you can blacklist it. Understood. Although I do not understand from where the updated microcode is fetched. The only way for desktop users were BIOS upgrades if I remember correctly. Linux does not ship the microcode, does not it. So I do not see what purpose this module has for desktop users. Intel regularly releases microcode updates and distributions are supposed to do regular package updates with the latest microcode file. You should get those with your normal update mechanism. In general it's recommended to run with the latest microcode. Looking into this some more, this seems unlikely in Debian because the microcode packages are in non-free [1] and therefore not available for Debian users not having enabled non-free repositories. Because of that the microcode packages are also non-essential, that means not installed by default even when non-free packages are allowed. And normal users will never install them by themselves. So currently I am pretty sure 99, % of Debian users do not have it installed. With the latest mainline kernel the microcode driver should be automatically loaded by CPUID probing through udev. How can I find out, if the microcode provided by my BIOS is older than the one provided by the processor vendor? I am pretty sure, that for example Intel does not release any updates for the Celeron CPU in my ASUS Eee PC 701 4G. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=intel-microcode;dist=unstable signature.asc Description: This is a digitally signed message part
Bug#684699: pybtex: TypeError: 'NoneType' object is not iterable
Package: pybtex Version: 0.15-1 If python-pkg-resources is not installed, pybtex --help fails with an exception: | $ pybtex --help | Traceback (most recent call last): | File /usr/bin/pybtex, line 27, in module | main() | File /usr/lib/pymodules/python2.7/pybtex/cmdline.py, line 75, in __call__ | self.main() | File /usr/lib/pymodules/python2.7/pybtex/cmdline.py, line 114, in main | options, args = self.opt_parser.parse_args(args) | File /usr/lib/python2.7/optparse.py, line 1399, in parse_args | stop = self._process_args(largs, rargs, values) | File /usr/lib/python2.7/optparse.py, line 1439, in _process_args | self._process_long_opt(rargs, values) | File /usr/lib/python2.7/optparse.py, line 1514, in _process_long_opt | option.process(opt, value, values, self) | File /usr/lib/python2.7/optparse.py, line 788, in process | self.action, self.dest, opt, value, values, parser) | File /usr/lib/python2.7/optparse.py, line 810, in take_action | parser.print_help() | File /usr/lib/python2.7/optparse.py, line 1669, in print_help | file.write(self.format_help().encode(encoding, replace)) | File /usr/lib/python2.7/optparse.py, line 1649, in format_help | result.append(self.format_option_help(formatter)) | File /usr/lib/python2.7/optparse.py, line 1629, in format_option_help | result.append(OptionContainer.format_option_help(self, formatter)) | File /usr/lib/python2.7/optparse.py, line 1073, in format_option_help | result.append(formatter.format_option(option)) | File /usr/lib/python2.7/optparse.py, line 315, in format_option | help_text = self.expand_default(option) | File /usr/lib/pymodules/python2.7/pybtex/cmdline.py, line 51, in expand_default | plugin_choices = self.get_plugin_choices(option.plugin_group) | File /usr/lib/pymodules/python2.7/pybtex/cmdline.py, line 46, in get_plugin_choices | return ', '.join(sorted(enumerate_plugin_names(plugin_group))) | TypeError: 'NoneType' object is not iterable -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pybtex depends on: ii python2.7.3-2 ii python-pyparsing 1.5.6+dfsg1-2 ii python-support1.0.15 Versions of packages pybtex recommends: pn python-yaml none -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684700: clamav: Scan error bad format or broken data
Package: clamav Version: 0.97.5+dfsg-3~squeeze1 Severity: normal clamscan error message display is CL_EFORMAT: Bad format or broken data ERROR. I scanned file. (display error message) /usr/bin/arj /usr/bin/clang /usr/lib/mozc/mozc_server Thanks. Reference: https://bugzilla.clamav.net/show_bug.cgi?id=5252 https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1015405 -- 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 = 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 = 4294967295 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 = 650 VirusEvent disabled ExitOnOOM disabled Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = clamav AllowSupplementaryGroups = yes Bytecode = yes BytecodeSecurity = TrustSigned BytecodeTimeout = 6 BytecodeUnsigned disabled BytecodeMode = Auto DetectPUA = yes ExcludePUA disabled IncludePUA = NetTool, PWTool, Spy, Scanner, RAT, Packed, P2P, IRC, Server, Script, Tool AlgorithmicDetection = yes ScanPE = yes ScanELF = yes DetectBrokenExecutables = yes ScanMail = yes ScanPartialMessages disabled PhishingSignatures = yes PhishingScanURLs = yes PhishingAlwaysBlockCloak = yes PhishingAlwaysBlockSSLMismatch = yes HeuristicScanPrecedence = yes StructuredDataDetection disabled StructuredMinCreditCardCount = 3 StructuredMinSSNCount = 3 StructuredSSNFormatNormal = yes StructuredSSNFormatStripped disabled ScanHTML = yes ScanOLE2 = yes OLE2BlockMacros = yes ScanPDF = yes ScanArchive = yes ArchiveBlockEncrypted = yes MaxScanSize = 104857600 MaxFileSize = 26214400 MaxRecursion = 16 MaxFiles = 1 ClamAuth disabled ClamukoScanOnAccess disabled ClamukoScannerCount = 3 ClamukoScanOnOpen disabled ClamukoScanOnClose disabled ClamukoScanOnExec disabled ClamukoIncludePath disabled ClamukoExcludePath disabled ClamukoExcludeUID disabled ClamukoMaxFileSize = 5242880 DevACOnly disabled DevACDepth disabled DevLiblog disabled Config file: freshclam.conf --- LogFileMaxSize = 4294967295 LogTime = yes LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose = yes 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 = 86 DNSDatabaseInfo = current.cvd.clamav.net DatabaseMirror = db.jp.clamav.net MaxAttempts = 10 ScriptedUpdates = yes 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 = 120 ReceiveTimeout = 120 SubmitDetectionStats disabled DetectionStatsCountry disabled DetectionStatsHostID disabled SafeBrowsing disabled Bytecode = yes Config file: clamav-milter.conf --- LogFile = /var/log/clamav/clamav-milter.log LogFileUnlock disabled LogFileMaxSize = 4294967295 LogTime = yes LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose = yes PidFile = /var/run/clamav/clamav-milter.pid TemporaryDirectory = /var/spool/clamav-milter FixStaleSocket = yes MaxThreads = 10 ReadTimeout = 120 Foreground disabled User = clamav AllowSupplementaryGroups = yes MaxFileSize = 104857600 ClamdSocket = unix:/var/run/clamav/clamd.ctl MilterSocket = /var/spool/postfix/cvrsockd/lvpmqnz.ctl MilterSocketGroup = clamav MilterSocketMode = 666 LocalNet disabled OnClean = Accept OnInfected = Reject OnFail = Defer RejectMsg disabled AddHeader = Replace ReportHostname = UnknownHostName VirusAction disabled Chroot disabled Whitelist disabled SkipAuthenticated disabled LogInfected = Full LogClean = Full Software settings - Version: 0.97.5 Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 JIT Database information Database directory: /var/lib/clamav main.cvd: version 54, sigs: 1044387, built on Tue Oct 11 23:34:20 2011 bytecode.cld: version 188, sigs: 38, built on Fri Jul 13 00:48:52 2012 daily.cld: version 15244,
Bug#661471: bug 661471 gnome-accessibility-themes
On Fri, 27 Jul 2012 15:11:30 Jeremy Bicha jbi...@ubuntu.com wrote: On Tue Jul 10, 2012 at 14:34:34 theppi...@gmail.com wrote: On Tue, Jul 10, 2012 at 8:23 PM, Michael Biebl bi...@debian.org wrote: I think the alternative Martin proposed is to build gnome-accessibility-themes from the gnome-themes-standard source package. I have also tried it already, but it required the outdated gtk-engines-3.pc. See message #28 in the bug log. I believe you misunderstand. In Ubuntu almost a year ago, I split gnome-themes-standard into two binary packages: gnome-themes-standard and gnome-accessibility-themes. We then dropped the abandoned-upstream gnome-themes source package that used to provide gnome-accessibility-themes. It works pretty well for Ubuntu as we want to ship the HighContrast themes but not Adwaita due to space You're right. I missed the from the gnome-themes-standard source package part in Michael's message. Sorry. So, I agree with splitting the gnome-accessibility-themes binary. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684619: [nullmailer] Debconf prompts for info that might contain password, saves to world-readable file
Hi, Thanks for the very good catch on this one. The package is ready to upload but needs a sponsor. Would you be able to spare a bit more time to upload the fix for me, please ? Source is dgettable from http://mentors.debian.net/debian/pool/main/n/nullmailer/nullmailer_1.11-2.dsc If you're busy then thanks for your valuable contribution to the package already, Nick Leverton Debdiff: diff -Nru nullmailer-1.11/debian/changelog nullmailer-1.11/debian/changelog --- nullmailer-1.11/debian/changelog2012-06-16 16:36:28.0 +0100 +++ nullmailer-1.11/debian/changelog2012-08-11 23:55:36.0 +0100 @@ -1,3 +1,9 @@ +nullmailer (1:1.11-2) unstable; urgency=low + + * Make 'remotes' not world-readable (Closes: #684619) + + -- Nick Leverton n...@leverton.org Sat, 11 Aug 2012 23:54:55 +0100 + nullmailer (1:1.11-1) unstable; urgency=low * New upstream release diff -Nru nullmailer-1.11/debian/postinst nullmailer-1.11/debian/postinst --- nullmailer-1.11/debian/postinst 2012-05-16 08:25:36.0 +0100 +++ nullmailer-1.11/debian/postinst 2012-08-12 20:23:46.0 +0100 @@ -24,10 +24,14 @@ fi db_get nullmailer/relayhost + # securely create nullmailer/remotes with mode 0600 + R=$( tempfile -d /etc/nullmailer -p nullm ) echo $RET | sed -r -e ':a s/(\[[^]:]*):/\1=/; ta' \ -e 's/[[:space:]]*:[[:space:]]*/\n/g' \ -e ':b s/(\[[^]=]*)=/\1:/; tb' \ --e 's/[][]//g' /etc/nullmailer/remotes +-e 's/[][]//g' $R + chown mail:mail $R + mv $R /etc/nullmailer/remotes db_get nullmailer/adminaddr if [ $RET ]; then -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Sun, 2012-08-12 at 01:02 +0200, Thomas Maass wrote: Package: syncevolution Version: 1.2.99.1-1 Followup-For: Bug #599247 Hi again! This bug is still there with the latest syncevolution package and horde4. I wonder, that other funambol clients on other devices don't have this problem. Perhaps they don't check the server's anchor. libsynthesis does (as it should). Look at your syncevolution-log.html and search for anchor, it should tell you when it falls back to a slow sync because of a mismatch. Looks like this Horde bug to me: http://bugs.horde.org/ticket/10008 Thomas, can you reassign this bug to the Debian Horde maintainers with information about your installed Horde version? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533287: [PATCH v2] Only the owner of a configuration file should modify it
Jonathan Nieder jrnie...@gmail.com writes: Policy §10.7.4 explains: If it is desirable for [...] packages to share a configuration file and for all of the related packages to be able to modify that configuration file, then the following should be done: [...] ii. The owning package should also provide a program that the other packages may use to modify the configuration file. iii. The related packages must use the provided program to make any desired modifications to the configuration file. [...] This advice suggests a few questions. Are these requirements release-critical? It is in the sense that if there is no such program, you don't get to modify the configuration file. (Item iii says must but the opening to the list says it describes what should be done.) Is it be more important (must vs should) that packages use the provided program than that the program exist? You're misunderstanding the intent. There are two possibilities: a program exists, in which case you must use it, or no such program exists, in which case you're not permitted to modify the configuration file, period. The should is to provide the facility to make modifications; in the absence of that, all other packages are just out of luck. Use should instead of must throughout and state clearly that packagers should not directly modify other packages' configuration files regardless of whether a tool for indirectly modifying is provided. NACK. We may have existing special cases where we've ignored this problem for reasons of expediency, but I don't think that's a good reason to water down the requirement globally. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684029: [Pkg-ia32-libs-maintainers] Bug#684029: ia32-libs-i386: Please, downgrade ldap depends to recommends
On Mon, Aug 06, 2012 at 12:28:35PM +0200, Vincent Danjean wrote: Package: ia32-libs-i386 Version: 20120701 Severity: normal Currently, ia32-libs-i386 depends on libldap-2.4-2 (= 2.4.23-7.2) libnss-ldap (= 264-2.2) libpam-ldap (= 184-8.5) I understand that, on systems where ldap is installed on the main (amd64) architecture, installing the corresponding i386 packages is required. However, when the main architecture does not have any ldap infrastructure installed (most laptops for example), we are required to install packages that ask strange questions (ldap base, ...) and that reconfigure /etc/nsswitch. Would it be possible to downgrade the Depends to a Recommends (at least) with a corresponding Breaks ( old-versions) if needed? If this is possible (I did not test), I think this should be applied to the wheezy package. Regards, Vincent Dear release team, would such a change (moving the 3 packages from Depends to Recommends) be suitable for a freeze exception? MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684123: argyll: dispwin fails to load ICC profile
reassign 684123 nvidia-glx thanks Cyril Soldani cyril.sold...@legiasoft.com writes: On Thu, 09 Aug 2012 12:00:42 +0200 Christian Marillat maril...@debian.org wrote: I see also the same with nvidia driver. Could you do a try with nouveau driver ? After some fiddling, I managed to get nouveau to display something on my screen. With the nouveau driver, I confirm that dispwin (from argyll 1.4.0-6) is still working properly (it loads my monitor ICC profile fine). Bug related to nvidia driver (even with the latest 304.30) : http://www.freelists.org/post/argyllcms/dispwin-fail-to-load-ICC-profile Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684123: argyll: dispwin fails to load ICC profile
reassign 684123 nvidia-glx thanks Cyril Soldani cyril.sold...@legiasoft.com writes: On Thu, 09 Aug 2012 12:00:42 +0200 Christian Marillat maril...@debian.org wrote: I see also the same with nvidia driver. Could you do a try with nouveau driver ? After some fiddling, I managed to get nouveau to display something on my screen. With the nouveau driver, I confirm that dispwin (from argyll 1.4.0-6) is still working properly (it loads my monitor ICC profile fine). Bug related to nvidia driver (even with the latest 304.30) : http://www.freelists.org/post/argyllcms/dispwin-fail-to-load-ICC-profile Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684193: Command names for Simon Tatham's puzzles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/13/2012 01:36 AM, Ben Hutchings wrote: I would be happy to rename the commands like this, but: 1. I would like you to include the command prefix as an option in your own releases, including the documentation change. 2. I would like to get some cross-distribution consensus on this, so that the various packages converge rather than further diverging. Agreed, sounds good. I'm also thinking of renaming the package to sgt-puzzles as soon as this happens. Jakob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQKLm3AAoJEEVsepuRuEKuNg8H/2DPexQ09WeIwsGRSlmAAawL VvjdMZxb4Z8lK5xBLmnLGbmQNE6snRILSvfYI9LPBQK5NqGXcJ11OlFSJI0UWVvt zz4TCaMssu6U7zkEX+QlHem8W5nCvYJHrhIt0ICZX2wmRf0UNaOe1g+IilU69ir5 CAUGz3BOqmpiZWjciKNhyrD1fQqVN4IO6F7F4JjWZwG78vCFYZF7KiZaREp7ZBi2 +LEfUe4jI1VgSbdLN2dsgGAjItOQy0wm+2lYqYK9SSo8X4zAKiJKRFiJjaP0JI83 CnvMrsAVgt1u+KbH6WF/Scwo7dOR2JvX06arxmPZ5hGaXUe3HensrwznYeAvjuw= =NGSq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684701: pommed: Uses what could be considered a lot of CPU
Package: pommed Version: 1.39~dfsg-2+b1 Severity: normal My system is a mid-2011 MBP. I'm leaving it booted for days, and noticed something rather odd, considering the little pommed supposedly does: pommed's cumulative time is awfully high. Right now, on my system that has 9 days and 2 hours of uptime, the cumulative time of cpu used by pommed is 120 minutes. Relative to 9 days+, this is not very much, but still, when compared to the fact that Xorg, which does actively suck CPU at times, like when playing videos, which I did in the past 9 days, has a cumulative time of 127 minutes... I'm inclined to think there's something seriously wrong in pommed. Especially when there is a huge gap between cumulative time for pommed, and other daemons: - ibus-daemon: 25 minutes 24 seconds - /usr/share/ibus/ui/gtk/main.py: 13 minutes 45 seconds - ibus-x11: 12 minutes 38 seconds - dbus-daemon: 8 minutes 44 seconds - awesome: 6 minutes 10 seconds - NetworkManager: 5 minutes 53 seconds - pulseaudio: 5 minutes 46 seconds In fact, the cumulative time of all long-lived processes on my system, except pommed, Xorg and iceweasel, is 141 minutes, which is only 21 minutes more than pommed, for a whole lot of processes. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pommed depends on: ii eject 2.1.5+deb1+cvs20081104-11 ii libasound2 1.0.25-4 ii libaudiofile1 0.3.4-1 ii libc6 2.13-35 ii libconfuse02.7-4 ii libdbus-1-31.6.2-2 ii libpci31:3.1.9-5 Versions of packages pommed recommends: ii dbus 1.6.2-2 pommed suggests no packages. -- 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#684702: fglrx-legacy-driver dispalay a AMD Testing use only watermark on the bottom right corner
Package: fglrx-legacy-driver Version: 8.97.100.3-1 Severity: normal Dear Maintainer, after installing fglrx-legacy-driver on debian wheezy for my radeon mobility hd3471 hybrid x2 and configuring it with aticonfig --initial there is a watermark saying AMD Testing use only which is present everytime on the bottom right corner of the screen (including in the gdm3 logscreen). Either way it works perfectly well. -- Package-specific info: Full fglrx package list: ii fglrx-legacy-a 8.97.100.3-1 legacy events daemon for the non-free AMD Ra ii fglrx-legacy-c 8.97.100.3-1 control panel for the non-free ATI/AMD Radeo ii fglrx-legacy-d 8.97.100.3-1 non-free ATI/AMD RadeonHD display driver (le ii fglrx-legacy-m 8.97.100.3-1 dkms module source for the non-free ATI/AMD ii libfglrx-legac 8.97.100.3-1 non-free ATI/AMD RadeonHD display driver (ru ii libfglrx-legac 8.97.100.3-1 AMD XvBA (X-Video Bitstream Acceleration) ru ii libgl1-fglrx-l 8.97.100.3-1 proprietary libGL for the non-free ATI/AMD R VGA-compatible devices on PCI bus: 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] DRM and fglrx Informations from dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.225070] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] [0.692922] Linux agpgart interface v0.103 [7.686447] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [7.998324] [fglrx] Maximum main memory to use for locked dma buffers: 2561 MBytes. [7.998442] [fglrx] vendor: 1002 device: 9612 count: 1 [7.998784] [fglrx] vendor: 1002 device: 95c4 count: 2 [7.999177] [fglrx] ioport: bar 1, base 0x9000, size: 0x100 [7.999592] [fglrx] ioport: bar 4, base 0xa000, size: 0x100 [7.01] [fglrx] Kernel PAT support is enabled [7.49] [fglrx] module loaded - fglrx 8.97.2 [Jul 4 2012] with 2 minors [ 20.845895] fglrx_pci :02:00.0: irq 46 for MSI/MSI-X [ 20.846687] [fglrx] Firegl kernel thread PID: 1880 [ 20.846971] [fglrx] Firegl kernel thread PID: 1881 [ 20.847069] [fglrx] Firegl kernel thread PID: 1882 [ 20.847405] [fglrx] IRQ 46 Enabled [ 21.191811] [fglrx] GART Table is not in FRAME_BUFFER range [ 23.259806] [fglrx] Gart USWC size:844 M. [ 23.259812] [fglrx] Gart cacheable size:333 M. [ 23.259818] [fglrx] Reserved FB block: Shared offset:0, size:100 [ 23.259822] [fglrx] Reserved FB block: Unshared offset:fd55000, size:2a6000 [ 23.259825] [fglrx] Reserved FB block: Unshared offset:fffb000, size:5000 [ 27.239581] [fglrx:firegl_irq_enable] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) Xorg X server configuration file status: -rw-r--r-- 1 root root 684 Aug 13 00:19 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 EndSection Section Module EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx BusID PCI:2:0:0 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 Monitoraticonfig-Monitor[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 44629 Aug 13 10:20 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: [19.372] X.Org X Server 1.12.3 Release Date: 2012-07-09 [19.372] X Protocol Version 11, Revision 0 [19.372] Build Operating System: Linux 3.2.0-3-amd64 x86_64 Debian [19.372] Current Operating System: Linux Gallarus 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 [19.372] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=UUID=a24ecc6f-f837-45d6-a981-809073ef332f ro quiet [19.372] Build Date: 18 July 2012 08:00:38AM [19.372] xorg-server 2:1.12.3-1 (Julien Cristau jcris...@debian.org) [19.373] Current version of pixman: 0.26.0 [19.373]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [19.373] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [19.373] (==) Log file: /var/log/Xorg.0.log, Time: Mon Aug 13 10:19:33 2012 [19.400] (==) Using
Bug#684703: libpam-modules:amd64: Package can not be re-installed when other architecture is installed
Package: libpam-modules Version: 1.1.3-7.1 Severity: important Dear Maintainer, libpam-modules cannot be reinstalled when it is also installed in another architecture. For example, on my amd64 system with i386 as foreign architecture: $ sudo aptitude install libpam-modules:i386 The following NEW packages will be installed: libpam-modules:i386 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/338 kB of archives. After unpacking 770 kB will be used. Preconfiguring packages ... Selecting previously unselected package libpam-modules:i386. (Reading database ... 227160 files and directories currently installed.) Unpacking libpam-modules:i386 (from .../libpam-modules_1.1.3-7.1_i386.deb) ... Processing triggers for man-db ... Setting up libpam-modules:i386 (1.1.3-7.1) ... $ sudo aptitude reinstall libpam-modules:i386 The following packages will be REINSTALLED: libpam-modules libpam-modules:i386 0 packages upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/686 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 227203 files and directories currently installed.) Preparing to replace libpam-modules:amd64 1.1.3-7.1 (using .../libpam- modules_1.1.3-7.1_amd64.deb) ... Unpacking replacement libpam-modules:amd64 ... Preparing to replace libpam-modules:i386 1.1.3-7.1 (using .../libpam- modules_1.1.3-7.1_i386.deb) ... Unpacking replacement libpam-modules:i386 ... dpkg: error processing /var/cache/apt/archives/libpam- modules_1.1.3-7.1_i386.deb (--unpack): trying to overwrite shared '/etc/security/limits.conf', which is different from other instances of package libpam-modules:i386 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.1.3-7.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up libpam-modules:amd64 (1.1.3-7.1) ... All this is on a completely updated testing installation. This seems to be a general problem with conffiles in MA: same packages, even if these files do not differ between the architectures. See also http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=640499 . I think this may actually be RC, but since it only happens in multiarch setups I was not sure whether that would be appropriate. Kind regards, Ralf -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (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/dash Versions of packages libpam-modules:amd64 depends on: ii debconf [debconf-2.0] 1.5.44 ii libc6 2.13-33 ii libdb5.1 5.1.29-5 ii libpam-modules-bin 1.1.3-7.1 ii libpam0g 1.1.3-7.1 ii libselinux12.1.9-5 libpam-modules:amd64 recommends no packages. libpam-modules:amd64 suggests no packages. -- 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#684193: Command names for Simon Tatham's puzzles
On Mon, Aug 13, 2012 at 10:24:23AM +0200, Jakob Gruber wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/13/2012 01:36 AM, Ben Hutchings wrote: I would be happy to rename the commands like this, but: 1. I would like you to include the command prefix as an option in your own releases, including the documentation change. 2. I would like to get some cross-distribution consensus on this, so that the various packages converge rather than further diverging. Agreed, sounds good. I'm also thinking of renaming the package to sgt-puzzles as soon as this happens. This all sounds fine to me. I have two more requests: Please maintain a NEWS file so that I don't have to trawl the commit logs for changes; and release official tarballs every few months or years, with a proper version number. Thanks, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652443: ioprio_get(2): document who==0
Hi Jens,
Would you be able to comment please...
Thanks,
Michael
On Sun, Jul 29, 2012 at 8:32 AM, Michael Kerrisk (man-pages)
mtk.manpa...@gmail.com wrote:
[CCing Jens because of the discussion below about IOPRIO_WHO_USER
below; he may have a comment]
[CCing Марк, who independently noted the lack of documentation for
IOPRIO_WHO_PROCESS, who==0 .]
[CCing Colin McCabe who sent other recent fixes for the ioprio_set.2 page]
On Sat, Dec 17, 2011 at 11:26 PM, Kalle Olavi Niemitalo k...@iki.fi wrote:
Package: manpages-dev
Version: 3.32-0.2
Severity: wishlist
File: /usr/share/man/man2/ioprio_get.2.gz
The ioprio_get(2) manual page describes the meanings of the which
and who parameters:
IOPRIO_WHO_PROCESS
who is a process ID identifying a single process.
IOPRIO_WHO_PGRP
who is a process group ID identifying all the members of
a process group.
IOPRIO_WHO_USER
who is a user ID identifying all of the processes that
have a matching real UID.
The manual page should mention that IOPRIO_WHO_PROCESS and
IOPRIO_WHO_PGRP also allow who==0.
Yes.
As implemented in
fs/ioprio.c, who==0 means the calling process or its process
group. The ioprio program in util-linux already uses the
feature. This is worth documenting separately because
e.g. tcsetpgrp does not treat pgrp==0 in that way.
Agreed, this should be documented since various APIs interpret pgrp==0
differently. Some (e.g., killpg(2)) are like this syscall, others are
not.
For IOPRIO_WHO_USER, the situation is more complex: who==0 means
the root user in ioprio_set but the current user (I think the
real UID of the calling process) in ioprio_get. (That
inconsistency might even be a bug.)
So, I'm not sure I'm following the kernel code too well here...
@Jens, your comments would be very welovem.
In ioprio_get() (Linux 3.5 kernel source file fs/ioprio.c), I see the
following:
case IOPRIO_WHO_USER:
uid = make_kuid(current_user_ns(), who);
if (!who)
user = current_user();
else
user = find_user(uid);
if (!user)
break;
do_each_thread(g, p) {
if (!uid_eq(task_uid(p), user-uid))
continue;
tmpio = get_task_ioprio(p);
if (tmpio 0)
continue;
if (ret == -ESRCH)
ret = tmpio;
else
ret = ioprio_best(ret, tmpio);
} while_each_thread(g, p);
if (who)
free_uid(user);
break;
In ioprio_set(), I see:
case IOPRIO_WHO_USER:
uid = make_kuid(current_user_ns(), who);
if (!uid_valid(uid))
break;
if (!who)
user = current_user();
else
user = find_user(uid);
if (!user)
break;
do_each_thread(g, p) {
if (!uid_eq(task_uid(p), uid))
continue;
ret = set_task_ioprio(p, ioprio);
if (ret)
goto free_uid;
} while_each_thread(g, p);
free_uid:
if (who)
free_uid(user);
break;
This suggests to me that you are right Kalle, in your interpretation
of who==0 for the IOPRIO_WHO_USER, since ioprio_get() uses
current_iser()-uid for its scan while ioprio_get() uses the UID
returned by make_kuid() (So, to be precise, I think who==0 in this
case means the UID of the uer who is thye super user in this user
namespace). If that's correct, it does of course need to be
documented. I'd be happy to get confirmation from Jens on this point.
I suppose that the differing meaning of who==0 for IOPRIO_WHO_USER in
ioprio_get() versus ioprio_set() is by design. But if so, like you
Kalle, I agree that it's a design point that is likely to surprise
users (and surprises here might have security implications). Again,
I'd like to get input from Jens.
In the meantime, I've applied the patch below to cover the other two cases.
Thanks,
Michael
--- a/man2/ioprio_set.2
+++ b/man2/ioprio_set.2
@@ -56,10 +56,16 @@ is interpreted, and has one of the following values:
.B IOPRIO_WHO_PROCESS
Bug#684702: [Pkg-fglrx-devel] Bug#684702: fglrx-legacy-driver dispalay a AMD Testing use only watermark on the bottom right corner
Am 13.08.2012 10:36, schrieb Adrien Le Guillou: Package: fglrx-legacy-driver Version: 8.97.100.3-1 Severity: normal Dear Maintainer, after installing fglrx-legacy-driver on debian wheezy for my radeon mobility hd3471 hybrid x2 and configuring it with aticonfig --initial there is a watermark saying AMD Testing use only which is present everytime on the bottom right corner of the screen (including in the gdm3 logscreen). Either way it works perfectly well. What is the output of md5sum /etc/ati/signature -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684704: Toolkit for Advanced Optimization (TAO) - Sponsor needed
Package: wnpp Severity: wishlist Package name: libanltao Version : 2.0-p6 Upstream Author : Todd Munson, Jason Sarich, Stefan Wild URL : http://debian.xypron.de/unstable/source/ License : BSD Programming Lang: C Description : Toolkit for Advanced Optimization (TAO) The Toolkit for Advanced Optimization provides a scalable solver for nonlinear programming. It can be applied to unconstrained minimization, bound constrained optimization, and general nonlinear optimization. It is based on the Portable Extensible Toolkit for Scientific Computing (PETSc). I have prepared a Debian package and seek a sponsor for uploading. The package files are available at http://debian.xypron.de/unstable/source/ Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684479: wheezy: Network File Services are major issue in Wheezy.
reassign 684479 general thanks Hughe Chung maildeliverag...@gmail.com writes: Package: wheezy Version: Wheezy When filing bugs, especially with reportbug, please make sure you file it against a package that exist, or a pseudo-package reportbug knows about, otherwise your report will not end up sent to the maintainers. I have reassigned your report to 'general' for now, lacking a better idea. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684705: RM: libumberlog/0.2.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove libumberlog from wheezy, as a new upstream version is about to be released, which will not be backwards compatible. Having an incompatible version in wheezy would be counter productive, and including the new one is far too late already. So the best option is to not ship libumberlog in wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684706: gnomine sometimes registers 0 time in scores for ghost game on new game click
Package: gnomine Version: 1:3.4.2-3 Severity: important Dear Maintainer, Every so often (maybe 1 in 20 games) after finishing a (Large) game and pressing new game, instead of starting a new game gnomine registers a ghost game with zero time in the score table, The score table window pops up showing a zero score first. If it's some kind of double click problem, I can't see it. I click the same way always and no extra game window flashes up when this happens. The only way I have to fix it is to keep a backup of the score file and wipe out the new first line and recover the old last line. Sometimes, on dismissing the scores window popup by pressing new game the same thing happens. I can't swear to it, but I might have seen the same thing happen with quit. This did not use to happen. About a month or two or three back I do not ever recall seeing it. I would guess it started happening a month ago, perhaps when the game started offering one a block of four game sizes after each new game button press (please get rid of that too! If I wanted to change size every game I would justifiably be considered loony. I Don't). -- System Information: Debian Release: wheezy/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'testing'), (100, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.39.4 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages gnomine depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gnome-games-data 1:3.4.2-3 ii libatk1.0-0 2.4.0-2 ii libc62.13-33 ii libcairo21.12.2-2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk-3-0 3.4.2-2 ii libpango1.0-01.30.0-1 ii librsvg2-2 2.36.1-1 gnomine recommends no packages. gnomine suggests no packages. -- 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#684497: desktop-base: please revert Updated GDM KDM's login background to have branding in the lower-right
Please revert this. With GDM, it sometimes happens that I have two Debian logos during session loading — which looks quite ugly. Also, I like the effect of Debian logo appering after logging in. -- Dmitry Shachnev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684670: apport-gtk: no option to send bug report
severity 684670 normal thanks Lowering severity as apport is under experimental and understaffed. On Sunday 12 August 2012 11:50 PM, Tshepang Lekhonkhobe wrote: When an app crashes (in my case, most often with Chromium), I don't get an option to send a bug report. That is, I don't get a 'Continue' after the dialog appears. Can you please provide a screenshot of the problem? -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature
Bug#684702: [Pkg-fglrx-devel] Bug#684702: fglrx-legacy-driver dispalay a AMD Testing use only watermark on the bottom right corner
Le lundi 13 août 2012 à 10:42 +0200, Patrick Matthäi a écrit : Am 13.08.2012 10:36, schrieb Adrien Le Guillou: Package: fglrx-legacy-driver Version: 8.97.100.3-1 Severity: normal Dear Maintainer, after installing fglrx-legacy-driver on debian wheezy for my radeon mobility hd3471 hybrid x2 and configuring it with aticonfig --initial there is a watermark saying AMD Testing use only which is present everytime on the bottom right corner of the screen (including in the gdm3 logscreen). Either way it works perfectly well. What is the output of md5sum /etc/ati/signature # md5sum /etc/ati/signature af36b47f395cd01f48b8fc1013665054 /etc/ati/signature -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684636: CDROM fail to mount
Hi, service hal stop makes that the CD/DVD NEC drive now works fine. But with or without hal, LG drive does not appear in the list of drive of Nautilus. This issue is randomly from one session to another. Perhaps same issue that 620278. mount /dev/sr1 /media/cdrom Without hal, mount command line with LG drive only have the same bug than this : about one minute to work with numbered SCSI errors. After that LG drive works fine with mount only durong this session. -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684707: unattended-upgrades: Add a distro_release macro
Package: unattended-upgrades
Version: 0.79
Severity: wishlist
It was just editing my 50unattended-upgrades file, and ended up wishing
I could just set it up and not change it as the machine moves from
unstable to testing to stable. Then it occurred to me that I probably
could do that if you added ${distro_release} to the macro's
unattended-grade supports.
${distro_release} would expand to
lsb_release.get_distro_information()['RELEASE'].
If you did support if, you could ship a standard 50unattended-upgrades
that worked for all Suite's.
While I'm here I ended up inserting my own documentation into
50unattended-upgrades because the stuff that comes with it omits a few
things. Maybe you could use it:
// Unattended-Upgrade::Origins-Pattern controls which packages are
// upgraded.
//
// Lines below have the format format is keyword=value, A
// package will be upgraded only if the values in its metadata match
// all the supplied keywords in a line. (In other words, omitted
// keywords are wild cards.) The keywords originate from the Release
// file, but several aliases are accepted. The accepted keywords are:
// a,archive,suite (eg, stable)
// c,component (eg, main, crontrib, non-free)
// l,label (eg, Debian, Debian-Security)
// o,origin(eg, Debian, Unofficial Multimedia Packages)
// site (eg, http.debian.net)
// The available values on the system are printed by the command
// apt-cache policy, and can be debugged by running
// unattended-upgrades -d and looking at the log file.
//
// Within lines unattended-upgrades allows 2 macros whose values are
// derived from /etc/debian_version:
// ${distro_id}Installed origin.
// ${distro_codename} Installed codename (eg, squeeze)
Unattended-Upgrade::Origins-Pattern {
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages unattended-upgrades depends on:
ii apt0.9.7.2
ii apt-utils 0.9.7.2
ii debconf [debconf-2.0] 1.5.44
ii lsb-base 4.1+Debian7
ii lsb-release4.1+Debian7
ii python 2.7.3~rc2-1
ii python-apt 0.8.4
ii ucf3.0025+nmu3
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
pn bsd-mailx none
-- debconf information:
unattended-upgrades/enable_auto_updates: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680291: xml2rfc: fails to install, remove, distupgrade, and install again
Hi, On 04/07 10:16, Andreas Beckmann wrote: during a test with piuparts I noticed your package failed to install (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. This seems to be related to the changes introduced to dh_installcatalogs (see #477751). Helmut, I took the liberty to put you in CC as you probably have some hints for how to proceed? Note that other packages might show the same behavior reported here: docbook-website comes to mind. Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681979: python3.3-minimal: fails to purge: subprocess installed post-removal script returned error exit status 1
tags 681979 + moreinfo thanks From the attached log (scroll to the bottom...): Removing python3.3-minimal ... Purging configuration files for python3.3-minimal ... dpkg: error processing python3.3-minimal (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: python3.3-minimal Adding set -x to the postrm: Removing python3.3-minimal ... Purging configuration files for python3.3-minimal ... + [ purge = remove ] + [ purge = purge ] + find /usr/lib/python3.3 -depth -type d -empty + rm -f /etc/python3.3/site.py /etc/python3.3/sitecustomize.py + rmdir --ignore-fail-on-non-empty /etc/python3.3 dpkg: error processing python3.3-minimal (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: python3.3-minimal which files are still left in /etc/python3.3? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
Package: mdadm
Version: 3.2.5-1
Severity: serious
Tags: patch wheezy sid
The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon
is not included in the .udeb for the installer.
This means that if you have an array with external metadata (ddf or,
more widely used, imsm - Intel Matrix Raid) that it will come up
readonly. This causes the installer to hang or the system not being
able to boot if root is on that array.
The attached patch does a couple of things:
- it makes sure mdadm is included in the initramfs and the udeb package
- it adds a mdadm-waitidle script that runs just before reboot/halt. For all
arrays that are still running, it sets safe_mode_delay to a low version,
sets sync_action to idle, and waits for the array(s) to go idle.
This is needed so that the array is clean, otherwise it will start
to resync at the next boot.
- it adds 2 lines of code to mdmon.c so that it symlinks its pidfile
into /run/sendsigs.omit.d - mdmon should not be killed at shutdown,
we still need it after the rootfs has been unmounted.
I have added support for installation on Intel Matrix raid (imsm)
arrays using mdadm to d-i, and I'll be sending patches to the debian-boot
list soon. Please consider this patch for inclusion in wheezy.
Mike.
Binary files orig/mdadm-3.2.5/debian/.rules.swp and mdadm-3.2.5/debian/.rules.swp differ
diff -ruN orig/mdadm-3.2.5/debian/changelog mdadm-3.2.5/debian/changelog
--- orig/mdadm-3.2.5/debian/changelog 2012-05-25 20:05:23.0 +0200
+++ mdadm-3.2.5/debian/changelog 2012-08-06 23:30:04.171100029 +0200
@@ -1,3 +1,14 @@
+mdadm (3.2.5-1+1) unstable; urgency=low
+
+ * also install mdmon in udeb and initramfs, so imsm arrays work
+ * mdmon now automatically makes a symlink in /run/sendsigs.omit.d to its pidfile
+ * create /run/sendsigs.omit.d/ in local-top script
+ * add script mdadm-waitidle that runs just before reboot/halt. For all
+arrays that are still running, it sets safe_mode_delay to a low version,
+sets sync_action to idle, and waits for the array(s) to go idle.
+
+ -- Miquel van Smoorenburg miqu...@debian.org Mon, 06 Aug 2012 23:29:32 +0200
+
mdadm (3.2.5-1) unstable; urgency=low
[ Michael Tokarev ]
diff -ruN orig/mdadm-3.2.5/debian/initramfs/hook mdadm-3.2.5/debian/initramfs/hook
--- orig/mdadm-3.2.5/debian/initramfs/hook 2012-05-25 19:31:37.0 +0200
+++ mdadm-3.2.5/debian/initramfs/hook 2012-08-02 00:32:50.925671675 +0200
@@ -49,6 +49,7 @@
}
MDADM=/sbin/mdadm
+MDMON=/sbin/mdmon
[ -x $MDADM ] || exit 0
[ -r /usr/share/initramfs-tools/hook-functions ] || exit 0
@@ -56,6 +57,7 @@
# copy the binary as early as possible
copy_exec $MDADM /sbin
+copy_exec $MDMON /sbin
# copy all modules into the initramfs, just for safety.
# we copy raid456 / raid5+raid6 because the hook script just won't do
diff -ruN orig/mdadm-3.2.5/debian/initramfs/script.local-top mdadm-3.2.5/debian/initramfs/script.local-top
--- orig/mdadm-3.2.5/debian/initramfs/script.local-top 2012-05-10 22:22:16.0 +0200
+++ mdadm-3.2.5/debian/initramfs/script.local-top 2012-08-06 17:32:30.162720885 +0200
@@ -53,6 +53,9 @@
# handle /dev/md/X nodes
mkdir -p /dev/md
+# mdmon wants this directory to exist
+mkdir -p /run/sendsigs.omit.d
+
CONFIG=/etc/mdadm/mdadm.conf
# in case the hook failed to install a configuration file, this is our last
# attempt... the emergency procedure... drumroll
diff -ruN orig/mdadm-3.2.5/debian/mdadm-waitidle mdadm-3.2.5/debian/mdadm-waitidle
--- orig/mdadm-3.2.5/debian/mdadm-waitidle 1970-01-01 01:00:00.0 +0100
+++ mdadm-3.2.5/debian/mdadm-waitidle 2012-08-06 23:49:22.138176669 +0200
@@ -0,0 +1,76 @@
+#!/bin/sh
+### BEGIN INIT INFO
+# Provides: mdadm-waitidle
+# Required-Start:
+# Required-Stop:
+# Should-Stop: halt reboot kexec
+# X-Stop-After: umountroot
+# Default-Start:
+# Default-Stop: 0 6
+# Short-Description: Wait for MD arrays to become idle
+# Description: This script waits until all MD arrays are
+#in idle and synced state before halt/reboot.
+### END INIT INFO
+#
+set -eu
+
+. /lib/lsb/init-functions
+
+case ${1:-} in
+ start)
+;;
+ stop)
+cd /sys/block
+for md in md*
+do
+ if [ -d $md/md/ ]
+ then
+if [ -w $md/md/safe_mode_delay ]; then
+ echo 0.05 $md/md/safe_mode_delay ||:
+fi
+if [ -w $md/md/sync_action ]; then
+ echo idle $md/md/sync_action ||:
+fi
+array_found=1
+ fi
+done
+[ -z $array_found ] exit 0
+
+log_action_begin_msg Waiting for MD arrays to become idle
+sync
+start=`date +%s`
+secs=0
+while [ $secs -lt 10 ]
+do
+ secs=$((`date +%s` - $start))
+ active=
+ for md in md*
+ do
+# We wait for normal writes, but not too long for resyncs/rebuilds.
+state=`cat $md/md/array_state 2/dev/null || echo unknown`
+sync=`cat $md/md/sync_action 2/dev/null || echo idle`
+
Bug#684636: CDROM fail to mount
OK : mount -t iso9660 /dev/sr1 /media/cdrom works fine ! So the auto mode of mount is the cause of this issue. Is linux-image package or mount package the responsable of this bug ? -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684709: the last line of malformed MIME messages is ignored
Package: spamassassin Version: 3.3.2-3.1 Severity: normal Tags: upstream patch Please backport this upstream change: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6823 This bug is being actively exploited by spammers. -- ciao, Marco signature.asc Description: Digital signature
Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)
Oh, and I should have added, the current documentation in 50unattended-upgrades says this: // Codename based matching: // This will follow the migration of a release through different // archives (e.g. from testing to stable and later oldstable). // o=Debian,n=squeeze; // o=Debian,n=squeeze-updates; // o=Debian,n=squeeze-proposed-updates; // o=Debian,n=squeeze,l=Debian-Security; I think the idea is n=squeeze is supposed to match the Codename attribute in the Release file. It would be great if it worked, but I don't see how it can because the python apt package doesn't include an element describing the codename in apt.Cache()[package].candidate.origins, and neither can I see any code in unattended-upgrades that would match it. It may looks like it works because unattended-upgrade doesn't report an error if you give it a keyword it doesn't understand (like n or codename). A side effect of this is if you included a line like true=true (or any other unknown keyword) every package will always match. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684710: insta: wheezy installer hangs on detectin ethernet card (lenovo think pad x201i)
Package: installation-reports Severity: important File: insta Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: network Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso- cd/debian-testing-i386-kde-CD-1.iso 06-Aug-2012 Date: Date and time of the install Machine: lenovo thinkpad x201i Partitions: df -Tl will do; the raw partition table is preferred $ df -Th Файловая система Тип Размер Использовано Дост Использовано% Cмонтировано в rootfs rootfs 5,5G 4,1G 1,2G 78% / udev devtmpfs10M0 10M0% /dev tmpfstmpfs 588M 772K 588M1% /run /dev/block/8:6 ext3 5,5G 4,1G 1,2G 78% / tmpfstmpfs 1,2G 348K 1,2G1% /run/shm /dev/sda2ext3 5,5G 4,9G 408M 93% /mnt/sda2 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I tried two installation cd-images (buisness card and cd-kde), and both are hanging up at the stage of detecting network card. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123lenny8 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux (none) 2.6.26-2-486 #1 Sat Nov 20 22:54:50 UTC 2010 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:0044] (rev 02) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0046] (rev 02) lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Ibex Peak HECI Controller [8086:3b64] (rev 06) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10ea] (rev 06) lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b3c] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Ibex Peak High Definition Audio [8086:3b56] (rev 06) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 1 [8086:3b42] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 4 [8086:3b48] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 5 [8086:3b4a] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b34] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a6) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Ibex Peak LPC Interface Controller [8086:3b07] (rev 06) lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation Ibex Peak 6 port SATA AHCI Controller [8086:3b2f] (rev 06) lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation Ibex Peak SMBus Controller [8086:3b30] (rev 06) lspci -knn: 00:1f.6 Signal processing controller [1180]: Intel Corporation Ibex Peak Thermal Subsystem [8086:3b32] (rev 06) lspci -knn: 02:00.0 Network controller [0280]: Intel Corporation Device [8086:0084] lspci -knn: ff:00.0 Host bridge [0600]: Intel Corporation Device [8086:2c62] (rev 02) lspci -knn: ff:00.1 Host bridge [0600]: Intel Corporation Device [8086:2d01] (rev 02) lspci -knn: ff:02.0 Host bridge [0600]: Intel Corporation Device
Bug#684711: ITP: nagibot -- Jabber bot to talk to Icinga / Nagios
Package: wnpp Severity: wishlist Owner: Jens Link jensl...@quux.de * Package name: nagibot Version : 0.8.3 Upstream Author : Andreas Jobs, Robin Schroeder * URL : http://nagibot.sourceforge.net/nagibot.html * License : GPL Programming Lang: Perl Description : Jabber bot to talk to Icinga / Nagios From the sourceforge page: Perl extension for Nagios. It logs on to an XMPP/Jabber server and joins a conference room. Nagios can then be configured to log messages to that room or to specific JIDs. With an XMPP client you can ask NagiBot to do something or to give a status. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684712: lvm2: automatically filter imsm and ddf formatted disks
Package: lvm2
Version: 2.02.95-4
Tags: patch wheezy sid
Severity: important
Currently, lvm automatically filters out mdraid devices. That is a
good thing, otherwise it could accidentally activate volume groups
on disks that are part of a mdraid array.
For quite some time now, the mdraid subsystem (mainly through mdadm)
supports more metadata formats than native mdraid only. These are
the 'imsm' (Intel Matrix Raid) and 'ddf' formats.
This patch makes sure that disks with signatures of one of these
metadata formats are also filtered out. To minimize the chance of
regressions, it only does this if md is actually running (i.e.
/proc/mdstat is present).
Background: I have added support for installation on Intel Matrix raid (imsm)
arrays using mdadm to d-i, and I'll be sending patches to the debian-boot
list soon. Please consider this patch for inclusion in wheezy.
Changelog entry:
* lvm already filters disks that have a mdraid signature, now also filter
DDF and IMSM formatted disks as well - but only if MD is actually running.
Mike.
Description: Also automatically filter DDF and IMSM formatted disks
Author: Miquel van Smoorenburg miqu...@debian.org
--- lvm2-2.02.95.orig/lib/device/dev-md.c
+++ lvm2-2.02.95/lib/device/dev-md.c
@@ -16,6 +16,7 @@
#include lib.h
#include metadata.h
#include xlate.h
+#include crc.h
#include filter.h
#ifdef linux
@@ -29,6 +30,18 @@
- MD_RESERVED_SECTORS)
#define MD_MAX_SYSFS_SIZE 64
+#define IMSM_SIGNATURE Intel Raid ISM Cfg Sig.
+#define IMSM_SIG_LEN (strlen(IMSM_SIGNATURE))
+
+#define DDF_MAGIC 0xDE11DE11
+struct ddf_header {
+ uint32_t magic;
+ uint32_t crc;
+ char guid[24];
+ char revision[8];
+ char padding[472];
+};
+
static int _dev_has_md_magic(struct device *dev, uint64_t sb_offset)
{
uint32_t md_magic;
@@ -42,6 +55,34 @@ static int _dev_has_md_magic(struct devi
return 0;
}
+static int _dev_has_imsm_superblock(struct device *dev, uint64_t dev_size)
+{
+ char imsm_signature[IMSM_SIG_LEN];
+
+ if (dev_read(dev, dev_size - 1024, IMSM_SIG_LEN, imsm_signature)
+ memcmp(imsm_signature, IMSM_SIGNATURE, IMSM_SIG_LEN) == 0)
+ return 1;
+
+ return 0;
+}
+
+static int _dev_has_ddf_superblock(struct device *dev, uint64_t dev_size)
+{
+ struct ddf_header hdr;
+ uint32_t crc;
+
+ /* Also calculate CRC so we have at least 8 bytes to check */
+ if (dev_read(dev, dev_size - 512, 512, hdr)
+ (hdr.magic == xlate32(DDF_MAGIC))) {
+ crc = hdr.crc;
+ hdr.crc = 0x;
+ if (xlate32(calc_crc(0, (const uint8_t *)hdr, 512)) == crc)
+ return 1;
+ }
+
+ return 0;
+}
+
/*
* Calculate the position of the superblock.
* It is always aligned to a 4K boundary and
@@ -86,6 +127,7 @@ int dev_is_md(struct device *dev, uint64
int ret = 1;
md_minor_version_t minor;
uint64_t size, sb_offset;
+ struct stat st;
if (!dev_get_size(dev, size)) {
stack;
@@ -114,6 +156,18 @@ int dev_is_md(struct device *dev, uint64
goto out;
} while (++minor = MD_MINOR_VERSION_MAX);
+ /* Only check for ddf/imsm if md is actually running. */
+ if (stat(/proc/mdstat, st) 0)
+ goto out;
+
+ /* Check if it is a ddf container device */
+ if (_dev_has_ddf_superblock(dev, size))
+ goto out;
+
+ /* Check if it is an imsm container device */
+ if (_dev_has_imsm_superblock(dev, size))
+ goto out;
+
ret = 0;
out:
Bug#684089: org-mode: +0d leads to arithmetic error in agenda view
On Aug/06, Jatmin wrote: Package: org-mode Version: 7.01g-1 I just came across a bug(?). When I use an org file with content -- * TODO test SCHEDULED: 2012-08-05 Sun +0d -- and type 'Ctrl-x org-agenda a' to get the agenda view, it exits with error message 'Arithmetic error' without displaying the test TODO item. The reason seems to be the 0 in the +0d. Hi Jatmin, I can't reproduce this behavior with the version of org-mode currently in testing. Could you try that, and let me know ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684463: [Neurodebian-devel] condor fails to install if condor user already exists
Hi! On Sat 11 Aug, 20:59, Michael Hanke wrote: Regarding the actual bug. This issue came up in the early days of this packaging. It essentially happens mostly for people upgrading from existing Condor deployments. While I can't say much about the necessity to have a Condor user in LDAP. I'm pretty sure that the Debian packages cannot work with a non-system user. There are all kinds of problems, but one of them is that the package can't assume that any user named 'condor' is also one that is available for Condor's operations. If a normal user 'condor' exists, IMHO failing is the only option. Otherwise that user would have access to Condor's runtime data (job payload, ...), but we would not know whether there is an actual (human) 'condor' user. The system user that the condor package creates is a dedicated one -- no login, no shell access. I think the current behaviour deviates from upstream in a significant and gratuitous way, making it much harder to deploy on top of an existing condor installation. And, it makes harder or impossible to use a perfectly valid configuration. The condor installation manual in chapter 3.2.2 http://research.cs.wisc.edu/condor/manual/v7.8/3_2Installation.html#SECTION00422000 states that: 5. Will you have a Unix user named condor, and will its home directory be shared? To simplify installation of Condor, create a Unix user named condor on all machines in the pool. The Condor daemons will create files (such as the log files) owned by this user, and the home directory can be used to specify the location of files and directories needed by Condor. The home directory of this user can either be shared among all machines in your pool, or could be a separate home directory on the local partition of each machine. Both approaches have advantages and disadvantages. Having the directories centralized can make administration easier, but also concentrates the resource usage such that you potentially need a lot of space for a single shared home directory. See the section below on machine-specific directories for more details. Note that the user condor must not be an account into which a person can log in. If a person can log in as user condor, it permits a major security breach, in that the user condor could submit jobs that run as any other user, providing complete access to the user's data by the jobs. A standard way of not allowing log in to an account on Unix platforms is to enter an invalid shell in the password file. If you choose not to create a user named condor, then you must specify either via the CONDOR_IDS environment variable or the CONDOR_IDS config file setting which uid.gid pair should be used for the ownership of various Condor files. See section 3.6.13 on UIDs in Condor on page [*] in the Administrator's Manual for details. The only requirement is that there is a user condor on all machines. If the condor user's home directory is to be shared, which is a perfectly valid configuration, the user account creation procedure in the debian package is not going to work, because the probability of getting the same uid and gid on all nodes are pretty low. NFS sharing of the home directory becomes impossible. For security reasons it is important that the condor user does not correspond to someone who can log in, which has nothing to do with the user uid being 1000 (which is the default in adduser.conf for system accounts). If you see a way that is both secure and satisfies your needs, please let me know. Otherwise, I think Evgeni is right: move 'condor' out of LDAP and solve email issues with alternative means. I think that in condor.postinst the call to adduser should be followed by a check: 1. if adduser failed, i.e. there is already a condor user and it is not a system account, then prompt the user to ask if they really want to use the existing account. 1a. if they want to use it, everything is fine 1b. if not, fail For now I am downgrading this bug to 'wishlist' and tag it with 'wontfix' until a more viable solution is found. Well, I think that wishlist is a bit unfair, given that it breaks on upgrade and makes it impossible to use the debian package on a cluster where other condor clients are not debian systems and use the valid configuration of sharing home with NFS and non-system condor account. Ciao, Tiziano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684711: ITP: nagibot -- Jabber bot to talk to Icinga / Nagios
Jens Link schrieb am Monday, den 13. August 2012: Package: wnpp Severity: wishlist Owner: Jens Link jensl...@quux.de * Package name: nagibot Version : 0.8.3 Upstream Author : Andreas Jobs, Robin Schroeder * URL : http://nagibot.sourceforge.net/nagibot.html * License : GPL Programming Lang: Perl Description : Jabber bot to talk to Icinga / Nagios From the sourceforge page: Perl extension for Nagios. It logs on to an XMPP/Jabber server and joins a conference room. Nagios can then be configured to log messages to that room or to specific JIDs. With an XMPP client you can ask NagiBot to do something or to give a status. It would be nice if (you/we) could maintain this within the nagios packaging group. Therefore you are invited to take part in it. If you are interested join us in #nagios@oftc or our alioth project [1]. If you need any help like a repo, review or something else, just ask! Alex [1] https://alioth.debian.org/projects/pkg-nagios/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684713: parted: support for partitioned MD devices
Package: parted Version: 2.3-10 Severity: serious Tags: patch wheezy sid Background: I have added support to the debian installer for installation on Intel Matrix Raid (imsm) arrays as supported by mdadm (I'll be submitting patches to debian-boot soon). When installing on such an array, partitions are created directly on the array (e.g. /dev/md0). Before kernel 2.6.28, partitionable md arrays were seperate from 'normal' md arrays (different dev_t's), but since 2.6.28 that has been consolidated. However, there is one minor oversight/bug in the kernel: the sysfs range key is still set to 1 for md arrays. That means libparted thinks that it's not possible to partition that device, where in fact it is. The attached patch reckognizes that situation: if running on a kernel = 2.6.28, and the device is a PED_DEVICE_MD, and the sysfs 'range' key is set to '1', _device_get_partition_range() returns MAX_NUM_PARTS instead. Please consider this patch for wheezy. Suggested changelog entry: * starting at kernel 2.6.28, MD devices can be partitioned, but the sysfs range key only shows support for one partition/device. Ignore that setting if it's set to 1 and the kernel version is = 2.6.28. Mike. Index: parted-2.3/libparted/arch/linux.c === --- parted-2.3.orig/libparted/arch/linux.c 2010-05-10 10:57:54.0 + +++ parted-2.3/libparted/arch/linux.c 2012-08-05 13:24:14.449768577 + @@ -2415,6 +2415,11 @@ ok = fscanf(fp, %d, range) == 1; fclose(fp); + /* starting at 2.6.28 partitions are OK but range doesn't show it */ + if (dev-type == PED_DEVICE_MD range == 1 + _get_linux_version() = KERNEL_VERSION (2,6,28)) + ok = 0; + /* (range = 0) is none sense.*/ return ok range 0 ? range : MAX_NUM_PARTS; }
Bug#678525: GCC bug
Hi, After further analyzing the problem and with help from Glyph Lefkowitz, Chris Cleeland and Rahul Amaram, I managed to create a test case that proved it is a gcc bug. The included tar file includes a simple testcase that can be run under Debian. The c file that is the base for this bugreport can be found here : http://trac.calendarserver.org/browser/CalendarServer/trunk/twext/python/sendmsg.c tar xvfz gcc-bug.tar.gz make fail python sender.py produces the faulty output : SCM_RIGHTS constant : 1 First call level 1 type 1 2a 00 00 00 (4) Second call level 1 type 0 2a 00 00 00 (4) This is using the current gcc in Debian sid : gcc (Debian 4.7.1-6) 4.7.1 make ok python sender.py produces the correct output : SCM_RIGHTS constant : 1 First call level 1 type 1 2a 00 00 00 (4) Second call level 1 type 1 2a 00 00 00 (4) This using current gcc-4.6 in Debian sid : gcc-4.6 (Debian 4.6.3-8) 4.6.3 The first and the second call should produce the same output but in the faulty run type becomes 0. Due to the 0, the linux kernel check in http://lxr.linux.no/linux+v3.2/net/core/scm.c#L159 fails, and gives the Invalid Argument error. The problem can be worked around in Debian and this bug can be closed once it is has been done. /Fred gcc-bug.tar.gz Description: application/gzip
Bug#684714: lightdm: Please depend on lightdm-greeter
Package: lightdm Version: 1.2.2-3 Severity: minor Dear Maintainer, lightdm currently depends on lightdm-gtk-greeter | lightdm-qt-greeter. As the latter does not exist anymore, this means it unconditionally depends on the GTK greeter. As I am currently preparing the KDE greeter for packaging [1], that should not be the case. Both the GTK greeter and the future KDE greeter provide the virtual lightdm-greeter package, so I think the dependency should actually be lightdm-gtk-greeter | lightdm-greeter. Kind regards, Ralf [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684053 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (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/dash Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.5-3.1 ii dbus 1.6.0-1 ii debconf [debconf-2.0] 1.5.44 ii libc6 2.13-33 ii libglib2.0-0 2.32.3-1 ii libpam0g 1.1.3-7.1 ii libxcb11.8.1-1 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter1.1.6-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+1 Versions of packages lightdm suggests: pn accountsservice none -- Configuration Files: /etc/lightdm/lightdm.conf changed: [SeatDefaults] allow-guest=false autologin-guest=false autologin-user= greeter-hide-users=true greeter-session=lightdm-greeter session-wrapper=/etc/X11/Xsession xserver-allow-tcp=false [VNCServer] enabled=false [XDMCPServer] enabled=false /etc/pam.d/lightdm changed: authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequiredpam_env.so readenv=1 envfile=/etc/default/locale @include common-auth @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_limits.so session requiredpam_loginuid.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open @include common-password -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675410: pdns-server: generates bogus rrsigs
On Mon, Jun 18, 2012 at 11:53:26AM +0200, Florian Obser wrote: ... and I did more tests. pdns-static_3.1.20120511.2617-1_amd64.deb generates correct rrsigs from the keys generated by pdns-server3.1-1 from wheezy. However, if I generate keys with pdns-static_3.1.20120511.2617-1_amd64.deb the wheezy version generates invalid rrsigs. So a recipe to reproduce: 1) install pdns-static_3.1 from upstream, configure mysql backend 2) insert zone example.com into database 3) $ pdnssec secure-zone example.com 4) (optional, check that rrsigs are correct) 5) remove pdns-static_3.1 6) install pdns-backend-mysql pdns-server from wheezy 7) observe that rrsigs are broken Can you retry this with pdns 3.1 from wheezy now? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684712: lvm2: automatically filter imsm and ddf formatted disks
On Mon, Aug 13, 2012 at 12:25:04PM +0200, Miquel van Smoorenburg wrote: This patch makes sure that disks with signatures of one of these metadata formats are also filtered out. To minimize the chance of regressions, it only does this if md is actually running (i.e. /proc/mdstat is present). Is this patch applied upstream? Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, The Omega Glory, stardate unknown -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681036: Patch
tags 681036 + patch thanks Proposed patch to include CDBS buildcore.mk in autoreconf.mk. Tested with gnome-themes-standard rebuilding. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ include-buildcore.patch Description: Binary data
Bug#684715: libclucene-dev: clucene-config.h in /usr/lib/multiarch-triplet?
Package: libclucene-dev Version: 2.3.3.4-1 Severity: normal Dear Maintainer, thanks for fixing 661703 and uploading the new clucene. Though - From LO configure: hecking which clucene to use... external checking for CLUCENE... yes checking for CLucene/analysis/cjk/CJKAnalyzer.h... no configure: error: Your version of libclucene has contribs-lib missing. Error running configure at ./autogen.sh line 187. Checking in config.log: configure:17031: checking for CLUCENE configure:17038: $PKG_CONFIG --exists --print-errors libclucene-core configure:17041: $? = 0 configure:17055: $PKG_CONFIG --exists --print-errors libclucene-core configure:17058: $? = 0 configure:17116: result: yes configure:17131: checking for CLucene/analysis/cjk/CJKAnalyzer.h configure:17131: /usr/bin/ccache g++ -c -g -O2 -I/usr/include/CLucene/ext -I/usr/include/CLucene/ext conftest.cpp 5 In file included from /usr/include/CLucene/StdHeader.h:20:0, from /usr/include/CLucene.h:11, from conftest.cpp:32: /usr/include/CLucene/SharedHeader.h:18:36: fatal error: CLucene/clucene-config.h: No such file or directory compilation terminated. configure:17131: $? = 1 configure: failed program was: [...] But it's there: $ dpkg -L libclucene-dev| grep -i config\.h /usr/lib/x86_64-linux-gnu/CLucene/clucene-config.h /usr/include/CLucene/CLConfig.h /usr/include/CLucene/ext/boost/config/select_compiler_config.hpp /usr/include/CLucene/ext/boost/config/select_platform_config.hpp /usr/include/CLucene/ext/boost/config/select_stdlib_config.hpp /usr/include/CLucene/ext/boost/config.hpp Should CLucene/clucene-config.h really be in /usr/*lib*/multiarch triplet? Will work around with --- configure.in-old2012-08-13 13:19:05.592297194 +0200 +++ configure.in2012-08-13 13:20:34.224736590 +0200 @@ -6189,6 +6189,8 @@ AC_MSG_RESULT([external]) SYSTEM_CLUCENE=YES PKG_CHECK_MODULES(CLUCENE, libclucene-core) +# hack for include in multiarch path... +CLUCENE_CFLAGS=$CLUCENE_CFLAGS -I/usr/lib/`dpkg-architecture -qDEB_HOST_MULTIARCH` AC_LANG_PUSH([C++]) save_CXXFLAGS=$CXXFLAGS for now, but... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libclucene-dev depends on: ii libc6-dev 2.13-35 ii libclucene-contribs1 2.3.3.4-1 ii libclucene-core1 2.3.3.4-1 libclucene-dev recommends no packages. libclucene-dev suggests no packages. -- no debconf information Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684716: gcc-4.7: problem with local variables, works in gcc-4.6
Package: gcc-4.7 Version: 4.7.1-6 Severity: normal Dear Maintainer, While trying to get calendar server to run, I also ran into the Debian bug #678525. I created a simplified test case and could show that it is a gcc bug, using the current gcc in sid (4.7.1-6). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678525 Included is gcc-bug.tar.gz that is a shortened version of the code found in calendarserver : http://trac.calendarserver.org/browser/CalendarServer/trunk/twext/python/sendmsg.c (Revision 8951) To run the example : tar xvfz gcc-bug.tar.gz cd gcc-bug make fail python sender.py produces the faulty output : SCM_RIGHTS constant : 1 First call level 1 type 1 2a 00 00 00 (4) Second call level 1 type 0 2a 00 00 00 (4) This is using the current gcc in Debian sid : gcc (Debian 4.7.1-6) 4.7.1 make ok python sender.py produces the correct output : SCM_RIGHTS constant : 1 First call level 1 type 1 2a 00 00 00 (4) Second call level 1 type 1 2a 00 00 00 (4) This using current gcc-4.6 in Debian sid : gcc-4.6 (Debian 4.6.3-8) 4.6.3 The first and the second call should produce the same output but in the faulty run type becomes 0. Due to the 0, the linux kernel check in http://lxr.linux.no/linux+v3.2/net/core/scm.c#L159 fails, and gives the Invalid Argument error in the Debian bug #678525. If more information is needed let me know. Thank you, Fredrik Unger -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gcc-4.7 depends on: ii binutils 2.22-7.1 ii cpp-4.7 4.7.1-6 ii gcc-4.7-base 4.7.1-6 ii libc6 2.13-35 ii libgcc1 1:4.7.1-6 ii libgmp10 2:5.0.5+dfsg-2 ii libgomp1 4.7.1-6 ii libitm1 4.7.1-6 ii libmpc2 0.9-4 ii libmpfr4 3.1.0-5 ii libquadmath0 4.7.1-6 ii zlib1g1:1.2.7.dfsg-13 Versions of packages gcc-4.7 recommends: ii libc6-dev 2.13-35 Versions of packages gcc-4.7 suggests: pn binutils-goldnone pn gcc-4.7-doc none pn gcc-4.7-locales none pn gcc-4.7-multilib none pn libgcc1-dbg none pn libgomp1-dbg none pn libitm1-dbg none pn libmudflap0-4.7-dev none pn libmudflap0-dbg none pn libquadmath0-dbg none -- no debconf information gcc-bug.tar.gz Description: application/gzip
Bug#684364: target: reports vfs_writev() returned -28 on iscsi activity
Hello, i have just noticed oops, which happend during experiments this morning Libor [141443.054425] btrfs: block rsv returned -28 [141443.054428] [ cut here ] [141443.054466] WARNING: at /build/buildd-linux_3.2.21-3-amd64- l_qIBB/linux-3.2.21/fs/btrfs/extent-tree.c:5985 btrfs_alloc_free_block+0xd7/0x284 [btrfs]() [141443.054470] Hardware name: VMware Virtual Platform [141443.054472] Modules linked in: autofs4 tcm_loop tcm_fc iscsi_target_mod target_core_pscsi target_core_file target_core_iblock target_core_mod des_generic ecb md4 hmac nls_utf8 cifs libfc scsi_transport_fc scsi_tgt configfs vmsync(O) vmhgfs(O) nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc dm_multipath scsi_dh loop coretemp crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 parport_pc joydev parport usbhid snd_pcm snd_page_alloc snd_timer snd vmw_balloon soundcore hid aes_generic cryptd psmouse serio_raw pcspkr processor ac evdev power_supply thermal_sys i2c_piix4 i2c_core container shpchp vmci(O) button ext4 crc16 jbd2 mbcache btrfs crc32c libcrc32c zlib_deflate dm_mod sr_mod cdrom ata_generic sd_mod crc_t10dif uhci_hcd floppy ehci_hcd usbcore usb_common e1000 ata_piix mptspi scsi_transport_spi mptscsih mptbase libata scsi_mod [last unloaded: autofs4] [141443.054526] Pid: 28983, comm: btrfs-transacti Tainted: G O 3.2.0-3-amd64 #1 [141443.054529] Call Trace: [141443.054537] [81046901] ? warn_slowpath_common+0x78/0x8c [141443.054550] [a01441fe] ? btrfs_alloc_free_block+0xd7/0x284 [btrfs] [141443.054566] [a01690fe] ? read_extent_buffer+0x94/0xed [btrfs] [141443.054575] [a01377bf] ? __btrfs_cow_block+0x102/0x33a [btrfs] [141443.054585] [a0137aee] ? btrfs_cow_block+0xf7/0x143 [btrfs] [141443.054595] [a013a546] ? btrfs_search_slot+0x225/0x64e [btrfs] [141443.054608] [a0148750] ? btrfs_del_csums+0xc8/0x252 [btrfs] [141443.054618] [a013ff9c] ? __btrfs_free_extent+0x54f/0x5c8 [btrfs] [141443.054630] [a0142fc9] ? run_clustered_refs+0x65e/0x6aa [btrfs] [141443.054642] [a01430de] ? btrfs_run_delayed_refs+0xc9/0x176 [btrfs] [141443.054647] [8134a0a0] ? mutex_lock+0xd/0x2d [141443.054661] [a0150153] ? btrfs_commit_transaction+0x8f/0x6f9 [btrfs] [141443.054667] [8105f5f3] ? add_wait_queue+0x3c/0x3c [141443.054679] [a014faba] ? join_transaction.isra.24+0x5a/0x1f3 [btrfs] [141443.054692] [a0150bd5] ? start_transaction+0x1ed/0x242 [btrfs] [141443.054705] [a014a7ad] ? transaction_kthread+0x156/0x20f [btrfs] [141443.054717] [a014a657] ? btrfs_congested_fn+0x7b/0x7b [btrfs] [141443.054720] [8105efad] ? kthread+0x76/0x7e [141443.054725] [81351cf4] ? kernel_thread_helper+0x4/0x10 [141443.054729] [8105ef37] ? kthread_worker_fn+0x139/0x139 [141443.054732] [81351cf0] ? gs_change+0x13/0x13 [141443.054734] ---[ end trace 2684d70a838e2d6c ]--- signature.asc Description: This is a digitally signed message part.
Bug#684715: pkg-config...
retitle 684715 needs to add -I/usr/lib/`dpkg-architecture -qDEB_HOST_MULTIARCH` to pkg-config output thanks Hi, quick discussion on #debian-devel suggests that this is common in multiarch-times, but then pkg-config should add the location: 13:15 noshadow _rene_: I think having headers in lib is a fashion pioneered by gtk. 13:17 algernon well, config.h-like stuff is often arch specific, so the triplet makes sense. it is also not something users ever need to directly include, so /usr/include is probably not the best place for it, either 13:18 * _rene_ works around it in configure.in with 13:18 -!- linuxmaniac [~man...@162.red-80-26-187.adsl.dynamic.ccgg.telefonica.net] has quit [Read error: Connection reset by peer] 13:18 _rene_ +CLUCENE_CFLAGS=$CLUCENE_CFLAGS -I/usr/lib/`dpkg-architecture -qDEB_HOST_MULTIARCH` 13:18 _rene_ but I don't really like it 13:19 -!- linuxmaniac [~man...@162.red-80-26-187.adsl.dynamic.ccgg.telefonica.net] has joined #debian-devel 13:19 algernon (gcc also has a bunch of headers in /usr/lib, fwiw) 13:19 noshadow _rene_: people placing stuff there usually insist on all users using pkg-config. does that list the correct dir? 13:19 _rene_ most probably not, otherwise it would be in CLUCENE_CFLAGS in the first place 13:19 _rene_ so clucene needs -I/usr/lib/`dpkg-architecture -qDEB_HOST_MULTIARCH` in it's pkg-config output= also fine by me. 13:20 noshadow algernon: though gcc also automatically adds them to the seach path. 13:20 -!- terceiro [~terceiro@177.42.225.39] has quit [Quit: Ex-Chat] 13:21 * _rene_ writes follow-up to 684715 Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683751: gettext: Please mark gettext M-A: allowed
On Thu, 9 Aug 2012, P. J. McDermott wrote: I wonder if the gettext binary package should instead be split. Perhaps gettext-runtime (M-A: same) should provide the libraries, gettext-tools (M-A: foreign) should provide the tools, and gettext should be a metapackage that depends on both of the former packages? Please note that the Debian gettext source package currently in wheezy/sid generates all the following binary packages: gettext-base gettext gettext-el gettext-doc autopoint libgettextpo0 libasprintf0c2 Moreover, all the libraries which are meant to be used by other packages are already multi-arched and they are in their own package (the last two in the list above). So: What exactly did you mean by split? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 13.08.2012 14:10, Miquel van Smoorenburg wrote: Package: mdadm Version: 3.2.5-1 Severity: serious Tags: patch wheezy sid The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon is not included in the .udeb for the installer. This means that if you have an array with external metadata (ddf or, more widely used, imsm - Intel Matrix Raid) that it will come up readonly. This causes the installer to hang or the system not being able to boot if root is on that array. I'm not sure this is the right course of actions -- speaking of the initramfs part, not about the d-i part. What's wrong with the array being started read-only? Root filesystem has always been mounted readonly in initrd/initramfs. There's no fsck tool included in initramfs. Once we switch to real root, we may start mdmon and remount filesystem(s) read-write as appropriate, after fsck'ing them etc. Why the system is not being able to boot if root is on such an array? The attached patch does a couple of things: - it makes sure mdadm is included in the initramfs and the udeb package Sure it is needed in the d-i (udeb), because d-i have to write the system to it. But I'm not convinced it is needed in the initramfs. - it adds a mdadm-waitidle script that runs just before reboot/halt. For all arrays that are still running, it sets safe_mode_delay to a low version, sets sync_action to idle, and waits for the array(s) to go idle. This is needed so that the array is clean, otherwise it will start to resync at the next boot. This is risky - we may never finish shutdown. This is especially risky for things like raid - eg, stalled raid (resync) thread (we've seen these more than once) -- in such cases current code will shut down, but with this wait it wont anymore. Especially useful for remote systems. Such an approach should be tested with extra care, I'm not sure we have resources to do that for wheezy. Generally it is a good idea I think. - it adds 2 lines of code to mdmon.c so that it symlinks its pidfile into /run/sendsigs.omit.d - mdmon should not be killed at shutdown, we still need it after the rootfs has been unmounted. And I'm not sure this is needed, either: it can trivially be done in the initscript. I have added support for installation on Intel Matrix raid (imsm) arrays using mdadm to d-i, and I'll be sending patches to the debian-boot list soon. Please consider this patch for inclusion in wheezy. So far I think the only real change there is the inclusion of mdmon to the udeb, the other changes are a bit questionable for wheezy. Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680244: xpra: consider adding bug fixes from the upstream stable branch 0.3.x before release?
Hi, أحمد المحمودي aelmahmo...@sabily.org writes: On Thu, Jul 19, 2012 at 01:03:45PM +0300, Timo Juhani Lindfors wrote: I see you uploaded 0.3.3 to unstable. I have been using it for a week now without problems. Thanks! ---end quoted text--- Please do. Today upstream backported https://www.xpra.org/trac/ticket/162 to the 0.3.x branch. I went to look at the branch but I'm bit worried that we already have too many changes that are not critical bug fixes. Maybe we should just upload new version to unstable and then do backports for wheezy users? -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684717: debian-installer-7.0-netboot-amd64: Relative paths in syslinux configuration interact badly with TFTP prefix
Package: debian-installer-7.0-netboot-amd64 Version: 20120712 Severity: wishlist I tried to make the d-i files available under the /debian-installer path of my TFTP server with a bind mount: $ findmnt /srv/tftp/debian-installer/ TARGET SOURCE FSTYPE OPTIONS /srv/tftp/debian-installer /dev/mapper/thoth-root[/usr/lib/debian-installer/images] ext4 rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered However the use of relative paths in the syslinux config files make this difficult. My PXE-booted client displays the following: BOOT SERVER IP: 10.0.0.1 !PXE entry point found (we hope) at 9E1C:0104 via plan A UNDI code segment at 9E1C len 199E UNDI data segment at 9C99 len 1830 Getting cached packet 01 02 03 My IP address seems to be 0A00010B 10.0.1.11 ip:10.0.1.11:109.0.0.1:10.0.0.1:255.255.0.0 BOOTIF=01-08-00-27-96-86-ec SYSUUID=blah TFTP prefix: debian-installer/amd64/text/ Trying to load: pxelinux.cfg/default Could not find kernel image: debian-installer/amd64/boot-screens/vesamenu.c32 boot: Looking at what's going over the network: # tshark -i eth0 -R tftp Capturing on eth0 6.25462810.0.1.11 - 10.0.0.1 TFTP 97 Read Request, File: debian-installer/amd64/text/pxelinux.0, Transfer type: octet, tsize\000=0\000 6.259698 10.0.0.1 - 10.0.1.11TFTP 1502 Data Packet, Block: 2 ... ... data packets and requests for mac-address-specific pxelinux.cfg elided ... ... 6.49234810.0.1.11 - 10.0.0.1 TFTP 120 Read Request, File: debian-installer/amd64/text/pxelinux.cfg/default, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.492898 10.0.0.1 - 10.0.1.11TFTP 67 Option Acknowledgement, tsize\000=154\000, blksize\000=1408\000 6.49627010.0.1.11 - 10.0.0.1 TFTP 60 Acknowledgement, Block: 0 6.496343 10.0.0.1 - 10.0.1.11TFTP 200 Data Packet, Block: 1 (last) 6.49701110.0.1.11 - 10.0.0.1 TFTP 60 Acknowledgement, Block: 1 6.49765510.0.1.11 - 10.0.0.1 TFTP 144 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/menu.cfg, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.498214 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.49941710.0.1.11 - 10.0.0.1 TFTP 148 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.499975 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50129910.0.1.11 - 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.cbt, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.501857 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50330510.0.1.11 - 10.0.0.1 TFTP 150 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.0, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.503862 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50543110.0.1.11 - 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.com, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.505995 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50723710.0.1.11 - 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.507794 10.0.0.1 - 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found menu.cfg can't be loaded, because the TFTP prefix 'debian-installer/amd64/text' is prepended to the path in the config file of 'debian-installer/amd64/boot-screens/menu.cfg'. If the config file used paths relative to the pxelinux.0 file then I think booting would work correctly. Additionally the assumed prefix path written into the config files doesn't let the 'text' and 'gtk' versions of the installers co-exist in the same TFTP root, because the paths are missing the text/gtk element. Once the various debian-installer-$VERSION-netboot-$ARCH packages are co-installable, this will prevent different versions from being accessible from the same TFTP server as well. My workaround configuration involves bind-mounting /usr/lib/debian-installer/images/amd64/text to
Bug#684463: [Neurodebian-devel] condor fails to install if condor user already exists
severity 684463 normal tag 684463 - wontfix thanks On Mon, Aug 13, 2012 at 12:28:17PM +0200, Tiziano Zito wrote: If you see a way that is both secure and satisfies your needs, please let me know. Otherwise, I think Evgeni is right: move 'condor' out of LDAP and solve email issues with alternative means. I think that in condor.postinst the call to adduser should be followed by a check: 1. if adduser failed, i.e. there is already a condor user and it is not a system account, then prompt the user to ask if they really want to use the existing account. 1a. if they want to use it, everything is fine 1b. if not, fail This seems good at first glance. However, it is a bit tricky to implement, because of the way the debconf interface works. Essentially the postinst script (with the failing adduser call) runs last and it seems quite cumbersome to implement what you suggesti, as it would need to be done in the config script. Maybe it could be: 1. Add a low-priority debconf question whether to use a non-system account named 'condor' if one is available. [I18N won't be happy about adding a template so late in the release cycle and I'm not sure whether we can get such change into the frozen wheezy] 2. Check the choice from (1) if adduser --system fails in the postinst and act accordingly. However, it would be much nicer if we could find a way to deal with this scenario without having to use debconf. Maybe we could try to check the validity of the requirements: there is a 'condor' user and it can't be used to log in. If there is a reliable way to verify this in the case that adduser --system fails (and the user comes from LDAP, or whatever other possible auth method), we could maybe issue a warning message and proceed without manual approval. Opinions? For now I am downgrading this bug to 'wishlist' and tag it with 'wontfix' until a more viable solution is found. Well, I think that wishlist is a bit unfair, given that it breaks on upgrade and makes it impossible to use the debian package on a cluster where other condor clients are not debian systems and use the valid configuration of sharing home with NFS and non-system condor account. ;-) you're arguments are valid, so let it be a 'normal' bug that needs fixing... Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684718: Debian-installer fails
Package: Debian-installer I have try to install wheezy twice, either by upgrading from squeeze or direct installation from internet In the case of upgrading the system works but after I restart the pc after the first screen showing the kernels, my screen goes gray and there is no responsee from the keyboard. The same holds when I try to install wheezy from the internet. I have attach the sysinfo. Please ask me any other information you need. Regards Antonis Manoussakis sysinfo Description: Binary data
Bug#684607: Chroot setup failed: stage=setup-start
retitle 684607 schroot could give usefull errormessages on ENOSPC severity 684607 whishlist kthxbye Hi! This was indeed lack of disk-space on the partition the chroots live on, sorry for the confusion. Might however be usefull to give a more concrete hint on what is failing ;-) Regards Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684719: Too restrictive permissions on the log directory used by mod_muc_log
Package: ejabberd Version: 2.1.11 Severity: wishlist As reported upstream in [1], our permission model makes log files created by the mod_muc_log module unreadable by any process not included in the ejabberd system group or having UID of the ejabberd system user. Supposedly, we should do two things to improve the situation: 1) Set the mod_muc_log's directory up in the same way we do for regular logs: by setting its group to adm and setting the SGID bit on it. 2) Allowing the user to use stat override mechanism to maintain more suitable permissions/access rights (such as 2750 ejabberd:www-data). 1. https://support.process-one.net/browse/EJAB-1588 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684720: apt-mirror crashes on line 473
Package: apt-mirror Version: 0.4.8-3 Severity: grave Justification: renders package unusable Apt-mirror crashes every time I run it. I have reinstalled the package and installed it on a different machine with default mirrors.list but I still get the same error. The output is: $ sudo -u apt-mirror /usr/bin/apt-mirror Downloading 22 index files using 20 threads... Begin time: Mon Aug 13 13:27:14 2012 [20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... [10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]... End time: Mon Aug 13 13:27:14 2012 Proceed indexes: [Sapt-mirror: invalid Sources format at /usr/bin/apt-mirror line 473, STREAM line 6920. It does not matter if I'm running as root, normal user or the apt-mirror user. regards //Rikard -- Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt-mirror depends on: ii adduser3.112+nmu2add and remove users and groups ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii perl-modules 5.10.1-17squeeze3 Core Perl modules ii wget 1.12-2.1 retrieves files from the web apt-mirror recommends no packages. apt-mirror suggests no packages. -- 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#684463: [Neurodebian-devel] condor fails to install if condor user already exists
severity 684463 normal thank you! However, it would be much nicer if we could find a way to deal with this scenario without having to use debconf. Maybe we could try to check the validity of the requirements: there is a 'condor' user and it can't be used to log in. If there is a reliable way to verify this in the case that adduser --system fails (and the user comes from LDAP, or whatever other possible auth method), we could maybe issue a warning message and proceed without manual approval. Opinions? What about this in condor.postinst:: SH=$(getent passwd | egrep '^condor:'| cut -d : -f 7) if [ $SH = /bin/false -o $SH = /usr/sbin/nologin ]; then # condor user exists and it is a locked user else adduser --system ... fi getent gets is info from the nss libraries, so it is independent of auth method. So no need to use new dpkg questions. Could this warrant a freeze exception? Ciao, Tiziano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#361328: Closing: Transparent SVG wallpaper featuring Debian logo
tag 361328 wontfix thanks This bug is old and will not be fixed in future. -- eshat cakar web: www.eshat.de gpg-id: 799B 95D5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660419: /etc/init.d/nsd3 restart fails everytime
Hello, Thanks for your report, and sorry for the late reply. I hope you can provide us with some extra information. You have reported this bug against version 3.2.9-3, but from your log excerpt it looks like version 3.2.8 is installed. Which one is it? How many primary and secondary zones do you have configured? Would it also be possible to send (perhaps privately) a copy of you /etc/nsd3/nsd.conf file to me? Kind regards, Jeroen Schot -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684607: [buildd-tools-devel] Bug#684607: Chroot setup failed: stage=setup-start
On Mon, Aug 13, 2012 at 01:37:38PM +0200, Christoph Egger wrote: This was indeed lack of disk-space on the partition the chroots live on, sorry for the confusion. Might however be usefull to give a more concrete hint on what is failing ;-) OK, no worries. The stderr of the setup scripts /should/ be being logged on stderr already, unless the shell isn't logging for some reason in this case (the script isn't interactive?) I'll look into it more closely anyway. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684721: snmpd: Lots of errors in syslog : error on subcontainer 'ia_addr' insert (-1)
Package: snmpd Version: 5.4.3~dfsg-2.5 Hi, The bug #559109 is not fixed in the snmpd package for wheezy. I have installed 3 wheezy installations. Two of them are physical machines. One is a VM. Both physical machines have a bonding configured. The error described here seems to only affect the 2 physical machines. The VM is not affected but has the same snmpd version installed. After applying the steps mentioned by Chris Zubrzycki in the bug #559109 the problem seems to be fixed. I created a patch and attached it to this email. Please reopen the bug #559109 because the bug seems not to be fixed in the version installed in wheezy. Thanks Mario Koppensteiner diff -Naur orig/etc/default/snmpd new/etc/default/snmpd --- orig/etc/default/snmpd 2011-01-05 12:12:04.0 + +++ new/etc/default/snmpd 2012-08-13 11:24:14.0 + @@ -8,7 +8,7 @@ SNMPDRUN=yes # snmpd options (use syslog, close stdin/out/err). -SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -g snmp -I -smux -p /var/run/snmpd.pid' +SNMPDOPTS='-LS6d -Lf /dev/null -u snmp -g snmp -I -smux -p /var/run/snmpd.pid' # snmptrapd control (yes means start daemon). As of net-snmp version # 5.0, master agentx support must be enabled in snmpd before snmptrapd @@ -16,7 +16,7 @@ TRAPDRUN=no # snmptrapd options (use syslog). -TRAPDOPTS='-Lsd -p /var/run/snmptrapd.pid' +TRAPDOPTS='-LS6d -p /var/run/snmptrapd.pid' # create symlink on Debian legacy location to official RFC path SNMPDCOMPAT=yes signature.asc Description: Digital signature
Bug#683126: icinga-web: simplify RewriteRules
tags 683126 + pending thanks Hello Chris, thanks, should be included in the first after-wheezy release. Regards Markus -- Markus Frosch mar...@lazyfrosch.de http://www.lazyfrosch.de
Bug#676629: unblock: guake/0.4.3-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package guake. This release fixes #676629. unblock guake/0.4.3-3 Thanks, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682857: console-setup-udeb: can't preseed keyboard layout=de variant=nodeadkeys
On Fri, Aug 10, 2012 at 11:36:28AM +0200, Samuel Thibault wrote: What about introducing new templates of string type that can be used in order to preseed arbitrary values in them? Then they'd appear in the user-presented choices, which we don't want to clutter. Another way actually might be to skip the keymap question when layout and variant are already provided. That'd however need careful tinkering in the .config script. Well, my idea was not to ask questions when keyboard-configuration/modelcode, keyboard-configuration/layoutcode, keyboard-configuration/variantcode and keyboard-configuration/optionscode are preseeded. I suppose this is analogous to what already exists in the config script and is used by keyboard-configuration in order to avoid asking questions when /etc/default/keyboard contains unsupported by the config script configuration. I haven't looked carefully into specifics of the code used only by the udeb, but can't you simply use the variable $unsupported_layout even when $is_not_debian_installer is false? Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684722: w3af: Does not start : pybloomfiltermmap is a required dependency
Package: w3af Version: 1.1svn5547-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, When I launch w3af I get the following messages : Additional information: pybloomfiltermmap is a required dependency in *nix systems,in order to install it please run the following commands:sudo apt-get install python2.6-dev sudo easy_install pybloomfiltermmap System stats : - Python-2.6-dev is installed OK apt-get install python2.6-dev Reading package lists... Done Building dependency tree Reading state information... Done python2.6-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. - easy_install pybloomfiltermmap is OK : easy_install pybloomfiltermmap Searching for pybloomfiltermmap Best match: pybloomfiltermmap 0.3.2 Processing pybloomfiltermmap-0.3.2-py2.6-linux-x86_64.egg pybloomfiltermmap 0.3.2 is already the active version in easy-install.pth Using /usr/local/lib/python2.6/dist-packages/pybloomfiltermmap-0.3.2-py2.6 -linux-x86_64.egg Processing dependencies for pybloomfiltermmap Finished processing dependencies for pybloomfiltermmap Regards JP P -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-x (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages w3af depends on: ii graphviz 2.26.3-12 ii python 2.7.3-2 ii python-gtk22.24.0-3 ii python-gtksourceview2 2.10.1-2 ii python-support 1.0.15 ii w3af-console 1.1svn5547-1 w3af recommends no packages. w3af suggests no packages. -- 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#684618: linux-image-3.2.0-3-686-pae: e1000 wake-on-lan does not work
On 08/12/2012 04:22 PM, Ben Hutchings wrote: On Sun, 2012-08-12 at 22:16 +0100, Ben Hutchings wrote: On Sun, 2012-08-12 at 00:01 +0200, Richard Kojedzinszky wrote: Package: src:linux Version: 3.2.23-1 Severity: important Tags: patch upstream In linux kernel commit d5bc77a223b0e9b9dfb002048d2b34a79e7d0b48 made wol does not work on e1000 cards. Later, in b868179c47e9e8eadcd04c1f3105998e528988a3 it has been fixed, but has not been ported back to 3.2 series, but that would be nice to include it in debian. [...] Can I queue this up for 3.2.y? Hmm, since this already had a 'Cc: stable', and applies cleanly, I wonder why it wasn't added earlier. Did it cause a regression that requires a further fix-up? I don't see anything like that in mainline. I'm not aware of any regression caused by this patch. It is addressing a regression that was introduced by commit d5bc77a223b0e9b9, which has been added to 3.2.y. So in my opinion this patch should definitely go into 3.2.y as well. (I don't know why it wasn't added earlier.) Dean -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684723: xauth: Some times corrupts my .Xauthority file when disk quota is exceeded
Package: xauth Version: 1:1.0.4-1 Some times my home directory is unwritable because my user exceed the disk quota set on it. And some times when this happen, I loose my Xauthority key needed to run X programs. The sad end result can be verified like this: % xhost No protocol specified xhost: unable to open display :0 % Can xauth be made more robust, to make sure it do not kill my .Xauthority file when I exceed my disk quota? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682358: icinga-web: make the documentation cronks working
tags 682358 + pending thanks Hello Chris, thanks for the bug. Icinga Web now utilizes the docs directly and suggests them for use. This is done via aliasing in the apache2.conf, so the user can disable it there. The change should be included in the first after-wheezy release of 1.7.2. Regards Markus -- Markus Frosch mar...@lazyfrosch.de http://www.lazyfrosch.de
Bug#684724: drawmap: invalid output file
Package: drawmap Version: 2.5-3 Severity: important Dear Maintainer, following one of the examples reported in the man page I obtain a drawmap.sun file executing file on it gives: drawmap.sun: Sun raster image data 1020, old format, executing convert drawmap.sun drawmap.jpg gives: convert.im6: improper image header `drawmap.sun' @ error/sun.c/ReadSUNImage/313. convert.im6: no images defined `drawmap.jpg' @ error/convert.c/ConvertImageCommand/3044. for which I assume the first error message (improper header) is the important one. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages drawmap depends on: ii libc6 2.13-35 drawmap recommends no packages. drawmap suggests no packages. -- 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#684725: virt-viewer cannot connect to remote VMs
Package: virt-viewer Version: 0.5.3-1 Severity: important Dear Maintainer, after upgrade from squeeze to wheezy virt-viewer cannot connect to remote VMs anymore: $ virt-viewer -v -c qemu+ssh://vir/system centos Opening connection to libvirt with URI qemu+ssh://vir/system Guest centos is running, determining display Guest centos has a vnc display Opening indirect TCP connection to display at vir:5901 Setting up SSH tunnel via vir Guest centos display has disconnected, shutting down$ Installing the virt-viewer locally on the VM host and starting it there works: $ virt-viewer -v -c qemu:///system centos Opening connection to libvirt with URI qemu:///system Guest centos is running, determining display Guest centos has a vnc display Opening direct TCP connection to display at localhost:5901:-1 (virt-viewer:24900): Gtk-WARNING **: Could not find the icon 'preferences-desktop-keyboard-shortcuts'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://icon-theme.freedesktop.org/releases Remote access by forwarding the VNC port manually with ssh and using a VNC viewer also works: $ ssh -R 5901:localhost:5901 vir $ xvncviewer localhost:1 VNC Viewer Free Edition 4.1.1 for X - built Mar 10 2010 21:40:13 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Mon Aug 13 15:04:51 2012 CConn: connected to host localhost port 5901 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Regards, Uwe -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virt-viewer depends on: ii libc6 2.13-33 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk-3-0 3.4.2-2 ii libgtk-vnc-2.0-00.5.0-3 ii libvirt00.9.12-3 ii libxml2 2.8.0+dfsg1-5 virt-viewer recommends no packages. Versions of packages virt-viewer suggests: ii netcat-openbsd [netcat] 1.105-7 ii netcat-traditional [netcat] 1.10-40 -- 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#684193: Command names for Simon Tatham's puzzles
On 08/13/2012 05:24 AM, Jakob Gruber wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/13/2012 01:36 AM, Ben Hutchings wrote: I would be happy to rename the commands like this, but: 1. I would like you to include the command prefix as an option in your own releases, including the documentation change. 2. I would like to get some cross-distribution consensus on this, so that the various packages converge rather than further diverging. Agreed, sounds good. I'm also thinking of renaming the package to sgt-puzzles as soon as this happens. Jakob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQKLm3AAoJEEVsepuRuEKuNg8H/2DPexQ09WeIwsGRSlmAAawL VvjdMZxb4Z8lK5xBLmnLGbmQNE6snRILSvfYI9LPBQK5NqGXcJ11OlFSJI0UWVvt zz4TCaMssu6U7zkEX+QlHem8W5nCvYJHrhIt0ICZX2wmRf0UNaOe1g+IilU69ir5 CAUGz3BOqmpiZWjciKNhyrD1fQqVN4IO6F7F4JjWZwG78vCFYZF7KiZaREp7ZBi2 +LEfUe4jI1VgSbdLN2dsgGAjItOQy0wm+2lYqYK9SSo8X4zAKiJKRFiJjaP0JI83 CnvMrsAVgt1u+KbH6WF/Scwo7dOR2JvX06arxmPZ5hGaXUe3HensrwznYeAvjuw= =NGSq -END PGP SIGNATURE- It's fine for me too. When this is agreed I'll do my best to do it as soon as possible. I'll also add my vote for better release versions and news file. :-) Victor Bogado. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684726: ITP: check_v46 -- Icinga / Nagios plugin for dual stacked (IPv4 / IPv6) hosts
Package: wnpp Severity: wishlist Owner: Jens Link jensl...@quux.de * Package name: check_v46 Version : Upstream Author : Ville Mattila * URL : http://gitorious.org/nagios-monitoring-tools * License : GPL Programming Lang: Perl Description : Icinga / Nagios plugin for monitoring dual stacked (IPv4 / IPv6) hosts check_v46 makes it easy to monitor dual stacked hosts and services. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684727: python-scapy: sendpfast(..) call depends on missing binary 'tcprelay'
Package: python-scapy Version: 2.2.0-1 Severity: normal Scapy's sendpfast(..) call depends on a 'tcprelay' binary which isn't installed as dependency. # sudo python -c from scapy.all import *; sendpfast(Ether()) WARNING: No route found for IPv6 destination :: (no default route?) WARNING: Mac address to reach destination not found. Using broadcast. ERROR: while trying to exec [tcpreplay]: [Errno 2] No such file or directory -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684728: iozone3: Error when running Generate_Graphs script
Package: iozone3 Version: 397-2 Severity: normal Hello, I get the following error when running the Generate_Graphs script: --- set terminal x11 ^ gnu3d.dem, line 9: unknown or ambiguous terminal type; type just 'set terminal' for a list --- I tried commending that line out in the gnu3d.dem file and it appears to have worked - I know very little about gnuplot, so can't be sure. Thanks, George -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (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/dash Versions of packages iozone3 depends on: ii libc6 2.13-35 iozone3 recommends no packages. iozone3 suggests no packages. -- 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#684729: python-scapy: Upstream patch: sendpfast(..) call fails, missing import
Package: python-scapy Version: 2.2.0-1 Severity: normal sendpfast(..) calls fail because a missing import in scapy/sendrecv.py. Upstream Patch: http://trac.secdev.org/scapy/ticket/634 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684730: keepnote: Broken help dialog, broken dependency
Package: keepnote Version: 0.7.8-1 Severity: important I was looking for outliner program and this new package looked good at first. Thanks for packaging this interesting program. But as I started to test this ... it is not in the best shape for me to try. Help dialog say Veiw error log. Also, recommended python-gnome2-extras package is not available. What is going on... I got scared to spend more time on this package. But di spend a bit more time Upstream has prerelease of 0.7.9 ... are these bug fixed there. Are you going to fix them by backporting. Without such care by the maintainer, this package seems to be too premature to be in release. I also see upstream suggest aspell aspell-en ... but you did not add them to suggest. Why? Anyway, this was first iteration of Debian package so I can expect a bit of rough edges... but it has been some months since then... Aren't you using this package. There is no bug like this obvious ones from you. As far as software goes, this is pretty good one. With few more iteration to support better export features, this one looks promising in near future but the way it is now, it is not really ready for wheezy. I am curious what is your plan on this package for wheezy? Osamu -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keepnote depends on: ii libsqlite3-0 3.7.13-1 ii python 2.7.3-2 ii python-glade2 2.24.0-3 ii python-gtk22.24.0-3 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3-2 keepnote recommends no packages. Versions of packages keepnote suggests: pn python-gnome2-extras none -- 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#678525: GCC bug
On 08/13/2012 02:58 PM, Rahul Amaram wrote: Thanks for the additional information Fredrik. Your analysis was really helpful. Could you please raise a new Debian GCC bug? If they fix it, then we'll have no need to make any changes in calendarserver Debian. Else we will have to force compilation of the package with gcc 4.6. I opened a new bug towards the gcc package. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684716 Maybe you can make this bug depend on that bug, or just have a temporary patch until the problem with GCC have been solved. /Fred -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684731: rubber: Broken image conversion
Package: rubber Version: 1.1+20100306-1 Severity: important I've attached a tarball with a minimal example that shows the failure. First, rubber is unable to use more than 1 rule for converting an image (dia - eps - pdf). This has not been working for quite some time, so this is probably not the place to discuss it (besides, I have some rules of my own to fix that). The new breakage appears to incorrectly infer the source and destination paths for files (example building article.ps): `here' is `/home/lluis/Projects/rubber-test/here.eps', made from `/home/lluis/Projects/rubber-test/here.dia' by rule `dia' `here2' is `/home/lluis/Projects/rubber-test/here2.eps', made from `/home/lluis/Projects/rubber-test/here.dia' by rule `dia' `there' is `/home/lluis/Projects/rubber-test/there.eps', made from `/home/lluis/Projects/rubber-test/here.dia' by rule `dia' As you can see, 'here2' is produces from the wrong source, and 'there2' should be found in the 'figures/' subdir when scanning the 'graphicspath' directive in the article. To be honest, I don't know when this broke, but makes rubber quite unusable at least for me. I tried to follow the error, and it looks like the routine doing the path expansion returns incorrect results. I've attached a simple example that exemplifies the error. Thanks, Lluis -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.utf8, LC_CTYPE=ca_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rubber depends on: ii dpkg1.16.4.3 ii install-info4.13a.dfsg.1-10 ii python 2.7.3~rc2-1 ii python-support 1.0.15 ii texlive-latex-base 2012.20120611-3 rubber recommends no packages. Versions of packages rubber suggests: ii imagemagick 8:6.7.7.10-3 ii sam2p0.49.1-1 ii transfig 1:3.2.5.d-3 -- no debconf information rubber-test.tgz Description: application/gtar-compressed
Bug#683751: gettext: Please mark gettext M-A: allowed
Hi, On Mon, Aug 13, 2012 at 01:30:12PM +0200, Santiago Vila wrote: On Thu, 9 Aug 2012, P. J. McDermott wrote: I wonder if the gettext binary package should instead be split. Perhaps gettext-runtime (M-A: same) should provide the libraries, gettext-tools (M-A: foreign) should provide the tools, and gettext should be a metapackage that depends on both of the former packages? So: What exactly did you mean by split? Steve made the gettext binary package M-A: allowed so that packages depending on it can choose (using the :any qualifier in their dependencies) whether they need a native version of the gettext binary package or if a foreign version will do as well. Patrick's idea was to split the gettext binary package into two packages: one package that would contain those parts that satisfy dependencies of packages of every other architecture (this package would be M-A: foreign) and one package that would only allow to satisfy dependencies of packages of the same architecture (this package would be M-A: same). Looking at the content of the gettext binary package, the following files would surely go into the M-A: same package as they differ between architectures: /usr/lib/gettext/hostname /usr/lib/gettext/urlget /usr/lib/libasprintf.a /usr/lib/libgettextlib-0.18.1.so /usr/lib/libgettextlib.so /usr/lib/libgettextpo.a /usr/lib/libgettextsrc-0.18.1.so /usr/lib/libgettextsrc.so /usr/lib/preloadable_libintl.so /usr/share/java/gettext.jar The following binaries also differ across architectures but those executables might be able to fulfill dependencies on them even for foreign architectures? /usr/bin/gettextize /usr/bin/msgattrib /usr/bin/msgcat /usr/bin/msgcmp /usr/bin/msgcomm /usr/bin/msgconv /usr/bin/msgen /usr/bin/msgexec /usr/bin/msgfilter /usr/bin/msgfmt /usr/bin/msggrep /usr/bin/msginit /usr/bin/msgmerge /usr/bin/msgunfmt /usr/bin/msguniq /usr/bin/recode-sr-latin /usr/bin/xgettext I'm not familiar with gettext so I couldnt tell which of above binaries would satisfy foreign dependencies on them and which do not. IMHO, if possible, then compared with making the gettext binary package M-A: foreign, splitting the gettext binary package into a M-A: foreign and a M-A: same package would be the preferred option. One reason for that is, that the :any qualifier is not yet allowed to be used in Debian because wanna-build doesnt understand it yet. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683807: bbswitch
Hi Ben, I've seen the title has changed. The first title (segfault while using mv ... ) was chaotic , i know. But bbswitch causes instability is not a correct title. Indeed i tried: a) use with nvidia driver + bbswitch . This lead to a crash. b) i tried uninstalling nvidia stuff, bbswitch and bumblebee (aka normal system. It's like a fresh installation). It crashed. c) i tried reinstalling bumblebee but disabling bbswitch (aka always use nvidia driver without the auto-remove-driver feature known as bbswitch). It crashed again. then, d) i tried to use debian stable (i installed it on another partition on the very same hard disk). It still crashes. So i think the problem is *not* bbswitch. The problem must be something hardware related. My notebook (Asus K52jc) must have some bad supported piece of hardware, i think that the problem is in some module(s). This/these module/s is/are part of either 3.2.x kernels and 2.6.x kernels. Atm this notebook is almost inusable :( I really appreciate your activity here, please tell me if more information is needed to find where the bug is. Thanks, Asdrubale -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684732: unblock: nut/2.6.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, Please unblock package nut This upload fixes several RC bugs and should make the package fit for the upcoming release. nut (2.6.4-2) unstable; urgency=low * debian/rules: Stop the nut-client before nut-server on systems using static boot ordering (Closes: #679451) * debian/nut-server.postinst: Remove /etc/init.d/nut on upgrade (Closes: #677822) * Rename nut-server.lintian-overrides to nut-client.lintian-overrides and adjust overrides now that ups-monitor is shipped in nut-client package (Closes: #677947) * Add debian/patches/0001-fix-upsmon-regression.patch: Fix upsmon/upssched regression (Taken from upstream) (Closes: #679513) * Move nut metapackage to Section: metapackages * Also create nut user when installing nut-client package and do not delete it on purge anymore (Closes: #682000) * Drop /etc/default/nut → /etc/nut/nut.conf migration code, migration happends before squeeze release and this was against policy to have a maintainer script modifying a conffile in the first place (Closes: #684392) * Add dependency against adduser and lsb-base on nut-client package * Be sure that client is stopped before the server also when using dependencies based boot * Fix package descriptions (Closes: #678068) * Also install /bin/upssched-cmd in nut-client package as this script is referenced in default upssched.conf config file * debian/watch: Update watch file * Be sure that all maintainer scripts are returning 0 at their end -- Laurent Bigonville bi...@debian.org Sun, 12 Aug 2012 20:38:52 +0200 changelog| 28 control |9 ++-- gbp.conf |4 - nut-cgi.postrm |1 nut-client.install |1 nut-client.lintian-overrides |1 nut-client.postinst | 63 nut-server.init |2 nut-server.lintian-overrides |2 nut-server.postinst | 68 ++- nut-server.postrm|7 --- nut-server.preinst |9 patches/0001-fix-upsmon-regression.patch | 15 ++ patches/series |1 rules|4 - watch|2 16 files changed, 130 insertions(+), 87 deletions(-) unblock nut/2.6.4-2 Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash nut_wheezy.diff.gz Description: GNU Zip compressed data
Bug#684636: CDROM fail to mount
I found that is blkid_do_safeprobe(blprobe) function (line 147) in fsprobe.c in mount package (util-linux-2.17.2) that triggers I/O errors. -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684654: [fglrx-legacy-driver] Xorg shows blank screen with fglrx legacy driver
Control: severity 684654 important Hi Beojan, On 2012-08-12 20:03, Beojan Stanislaus wrote: On Sunday 12 August 2012 19:12:04 Andreas Beckmann wrote: Please try the 3.2 kernel from wheezy/sid and the non-rt flavor. I have, and the bug described persists. Please report this problem to AMD: http://ati.cchtml.com/ This does not look like a packaging problem, so there is not much we can do about this in Debian. On the other hand we got several reports of people successfully running the legacy driver, so I'm downgrading the severity of this bug to important. You might also try the older Xorg versions available in squeeze-backports (or even squeeze). Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684734: pyhoca-cli: ImportError: No module named pyhoca.cli
Package: pyhoca-cli Version: 0.2.0.3-1 Severity: grave Justification: renders package unusable pyhoca-cli doesn't start: $ pyhoca-cli /usr/lib/python2.7/dist-packages/x2go/__init__.py:183: UserWarning: libevent version mismatch: system version is '2.0.19-stable' but this gevent is compiled against '2.0.16-stable' from gevent import monkey Traceback (most recent call last): File /usr/bin/pyhoca-cli, line 105, in module from pyhoca.cli import current_home, PyHocaCLI, runtime_error ImportError: No module named pyhoca.cli -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pyhoca-cli depends on: ii python 2.7.3-2 ii python-setproctitle 1.0.1-1+b1 ii python-x2go 0.2.0.8-1 ii python2.7 [python-argparse] 2.7.3-2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
