Bug#699134: /usr/bin/qemu-system-x86_64: can not detect hdd images (-drive) with unprivleged users
28.01.2013 04:09, skeksix wrote: Please, can you close this bug report? I am sorry with my lser bug report xDD There's no problem with qemu-system-x86_64, there's a problem with a luser :D I have used network install isos, which by default did not use virtio modules. Well, maybe this bug should be filed against the debian installer instead, because the network install ISOs should contain these modules? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698946: Security update broke php-cas, wrong call to setSslCaCert()
On Sat, January 26, 2013 16:05, Olivier Berger wrote: As you can see in [0], I've integrated the full upstream commit [1] and not just the change on Client.php. Hope this helps. The updated package indeed fixes the problem and works fine. Thanks! Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691710: unblock: mdadm/3.2.5-4 (pre-upload)
28.01.2013 05:07, Cyril Brulebois wrote: Julien Cristau jcris...@debian.org (26/01/2013): 3.2.5-5 unblocked. unblock-udeb pending d-i ack, probably post-rc1. Looks like post-rc1 material to me indeed. FWIW (not insisting for earlier inclusion, just noting), for the d-i, the noticeable change is the inclusion of an extra binary, mdmon, which is unused on all currently working setups and is only used internally by mdadm when it tries to assemble a fakeraid IMSM array. The bugfixes (code fixes) included in this release does^Wshould not affect d-i, these are mostly about routine array maintenance which isn't done in d-i. A bit wider testing, however, is veery welcome, -- for one, I don't know whenever it will work in d-i or not, because I don't have hardware where I can test it. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681197: grub2: grub-mklayout and at_keyboard.mod have problem with jp keyboard
On 10.07.2012 13:48, Hiroyuki YAMAMORI wrote: +GRUB_KEYBOARD_KEY_JPBACKSLASH = 0x70, +GRUB_KEYBOARD_KEY_JPYEN = 0x71, Where do these codes come from? According to USB specifications those codes are keyboard F21 and F22 respectively. -- Regards Vladimir 'φ-coder/phcoder' Serbinenko signature.asc Description: OpenPGP digital signature
Bug#699149: bacula-fd: should not run as 'root' by default
Package: bacula-fd Version: 5.2.6+dfsg-7 Severity: normal Hi, The other Bacula services are started by 'bacula' user. Only bacula-fd is started as 'root'. However, I've just discovered that it can function properly with limited privileges too. For this one must edit /etc/default/bacula-df to contain: ARGS=-u bacula -g bacula -k I think that from a security perspective this should be the default on package installation. Also, the init script file should work with defaults even if there is no content on /e/d/bacula-fd or is completely missing. This means that at install all default options should be provided as a comment/example: #ENABLED=yes #ARGS=-u bacula -g bacula -k #CONFIG=/etc/bacula/bacula-fd.conf Cheers -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 bacula-fd depends on: ii bacula-common 5.2.6+dfsg-7 ii libacl12.2.51-8 ii libc6 2.13-37 ii libcap21:2.22-1.2 ii libgcc11:4.7.2-5 ii libpython2.7 2.7.3-6 ii libssl1.0.01.0.1c-4 ii libstdc++6 4.7.2-5 ii libwrap0 7.6.q-24 ii lsb-base 4.1+Debian8 ii ucf3.0025+nmu3 ii zlib1g 1:1.2.7.dfsg-13 bacula-fd recommends no packages. Versions of packages bacula-fd suggests: pn bacula-traymonitor 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#699034: similar bug report
you may find interesting this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640501 that was fixed downgrading libgcrypt11 to the 1.4.6-9 version from: http://snapshot.debian.org/archive/debian/20110807T212024Z/pool/main/libg/libgcrypt11/ may be it is the same bug? Ciao -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699150: RFS: begin/0.1.1-1 (ITP #699113)
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package begin * Package name: begin Version : 0.1.1-1 Upstream Author : Mikael Nordin * URL : https://github.com/mickenordin/begin * License : GPL-2+ Section : text It builds those binary packages: begin - This is an output modifier To access further information about this package, please visit the following URL: http://mentors.debian.net/package/begin Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/begin/begin_0.1.1-1.dsc More information about begin can be obtained from https://github.com/mickenordin/begin Changes since the last upload: This is the initial upload Regards, Mikael Nordin
Bug#698917: [wheezy] cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410
Florian Lohoff wrote: Opened a bug in the Kernel Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=53101 Thanks! If I have any more questions, I'll ask them upstream. Ciao, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681830: Reproduced
Le dimanche 27 janvier 2013 à 19:42 +, Neil Williams a écrit : gdm3 was stopped over an SSH connection using invoke-rc.d. Then I started gdm3 from the command line (on a directly connected keyboard) to generate endless lists of: gdm3[17041]: WARNING: GdmDisplay: display lasted 1.681562 seconds gdm3[17041]: WARNING: GdmDisplay: display lasted 1.687131 seconds gdm3[17041]: WARNING: GdmDisplay: display lasted 1.693576 seconds daemon/gdm-display.c : 725 g_warning (GdmDisplay: display lasted %lf seconds,elapsed); I changed the shell script to avoid the 3 second timeout (which makes this much more manageable) and gdm3 just keeps respawning using gdm-simple-slave, incrementing the --display-id each time. As mentioned on IRC, there is already some code to handle GdmDisplay respawning too fast. See on_display_status_changed() in gdm-local-display-factory.c. I’m interested in logs with debugging enabled, especially stuff like “GdmLocalDisplayFactory: display status changed”. Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699049: [Pkg-telepathy-maintainers] Bug#699049: libfarstream-0.1-0: seems farstream not detecting audiocodecs
On 26/01/13 18:29, Vladimir Berezenko wrote: on powerpc seems that farstream is not seing any audiocodecs. This is likely to be caused by http://bugs.debian.org/674156, for which powerpc is one of the affected architectures. Please try upgrading to libgstreamer0.10-0 (= 0.10.36-1.1) from unstable - that version should be available on powerpc now (or within a couple of days if your Debian mirror is slow). The ~/.cache/farstream contains 2 files: codecs.audio.powerpc.cache 12 bytes long 46 53 41 43 31 31 00 00 00 00 00 00 |FSAC11..| 000c If codec detection works correctly, I would expect this file to be considerably larger and contain some audio MIME types, similar to the video file you also quoted. If you upgrade libgstreamer0.10-0 and start a Farstream application like empathy-call or Pidgin, the cache file should hopefully be regenerated automatically. If not, try deleting it and restarting the application. Regards, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692821: gnome-shell: defines wrong pam service for gdm greeter
On Tue, Dec 4, 2012 at 3:12 AM, Josselin Mouette j...@debian.org wrote: You might want to search for other instances of this string. I find it flabbergasting that the PAM service is used in the UI rather than only in the slave, but upstream works in mysterious ways… I've done this myself, and also found occurance of that string in begin_other_verification() function of the gdm's simple greeter (aka gdm-fallback), file gui/simple-greeter/gdm-greeter-login-window.c (yes, UI code again). I can provide patches for both gnome-shell and gdm3, if needed. -- 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#699109: unblock (pre-approval): initramfs-tools-tcos/0.89.91
2013/1/27 Julien Cristau jcris...@debian.org: On Sun, Jan 27, 2013 at 17:42:48 +, Manuel A. Fernandez Montecelo wrote: Could Release Team please say if the changes proposed in #694870 to fix an RC bug are OK to go? Please include an actual diff in this bug instead of a pointer to $somewhere_else. Attached. According to the discussion in that bug report, the patch does need to be so big to fix three separate issues, and without the fixes it seems that the software will not be functional. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com bd77023afadfe96a0c6ab86343b02b695567439f.patch Description: Binary data
Bug#699150: RFS: begin/0.1.1-1 (ITP #699113)
Micke Nordin m...@elnord.in writes: dget -x http://mentors.debian.net/debian/pool/main/b/begin/begin_0.1.1-1.dsc It seems that your source package by mistake includes binaries. Unpack http://mentors.debian.net/debian/pool/main/b/begin/begin_0.1.1-1.tar.gz and see the file pkg/begin_0.1.1-1_amd64.deb. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699096: gpa: Segmentation fault in _assuan_socket due to missing assuan_sock_init() call
Hi Michael, The segfault during `gpa -d' got fixed in the recent upload of gpa/0.9.0-4. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674156: glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips
On Fri, 11 Jan 2013 at 18:39:24 +, Simon McVittie wrote: By making a sourceful upload of gstreamer0.10, together with the sourceful upload of swami that has already happened and a pile of 14 binNMUs (see 694525#59), we can get full upgrades into a consistent state. Julien has NMU'd gstreamer0.10 and scheduled some binNMUs, and swami has migrated, so all we're waiting for to achieve this is for gstreamer0.10 to migrate. (This can be tracked by waiting for #697025, which is also RC, to migrate.) So, assuming no serious problems with the NMU, it's only a matter of time before full upgrades are OK. Regarding the original bug, gnome-dvb-daemon was recently built on the affected architectures; it is now built on all Linux architectures. So, from that point of view, job done. As for partial upgrades: Julien's NMU of gstreamer0.10 bumped the shlibs, so if dependent packages are rebuilt (up to 22 source NMUs of Multi-arch: same packages, and up to 38 binNMUs of other packages, see http://bugs.debian.org/694525#59), certain broken combinations (namely: new dependent package, old gstreamer0.10) will be prevented. There hasn't been any systematic upload of these; it's an open question whether it's worthwhile to do all of these, or just the binNMUs, or neither. The other broken combination (new gstreamer0.10, old dependent package) can only be addressed via Breaks relations. I think Julien's conclusion was that this has an unacceptable risk of introducing weird upgrade bugs where apt fails to find a solution, similar to http://bugs.debian.org/676485? Regards, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698945: [Pkg-ia32-libs-maintainers] Bug#698945: ia32-libs(20120926) works - ia32-libs1.0:4 does not !
On Fri, Jan 25, 2013 at 03:14:57PM +, Holger Weiss wrote: Package: ia32-libs Version: 1:0.4 Severity: important Dear Maintainer, I have 2 machine with identical hardware: machine1 and machine2, both with the Debian wheezy amd64 release. Machine1 got the last update in October 2012 and it is using ia32-libs Version 20120926. On this machine the software works ! Machine 2 was reinstalled 2 days ago and uses ia32-libs in Version 1:0.4. This machine shows the error: hpeesofhelp: error while loading shared libraries: libXm.so.3: wrong ELF class: ELFCLASS64 Gemx error, error code = 11 Did you link the 64bit libXm instead of the 32bit one? On both machines I need to run the software which is using both 32bit and 64bit libmotif libs. Especially the libXm.so.3 (I had to create a symbolic link to libXm.so.4 on both machines to make it work, because the file did not exist!). I also found that the folder /usr/lib32 doesnot exist on machine 2 ! I expected the software to work as smooth as on machine 1. Is there any significant change in handling the ia32-libs between this versions ? Ia32-libs uses multiarch now. How can I make my software working with ia32-libs (1:0.4) ? The software I am using is ADS2012 (and ADS2011) from Agilent. Ia32-libs is only a transitional meta package. You shouldn't need that at all. What you need are the 32bit libraries that ADS2012 requires. The simplest would be to simply install an ADS2012 debian package for i386. If that doesn't exist then you need to install the i386 package for required libraries. You can do that under multiarch by appending :i386 to the package name. 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#699151: gnus: batch download of virtual groups causes error: Creating director long
Package: gnus Version: 5.11+v0.10.dfsg-3 Severity: normal A virtual group (named shopping) was created and agentified. These were the natural groups that composed the shopping group: alt.consumers.free-stuff alt.consumers.uk-freebies gwene.com.dealbreaker gwene.com.feedburner.mydealz gwene.com.fatwallet.hotdeals The download agent was executed as follows: emacs -batch -l ~/.gnus.el -f gnus-agent-batch-fetch It works up until it came time to process the new virtual group, at which point this error resulted: Creating directory: file name too long, /home/blee/news/agent/nnvirtual/^$\|\(^nntp\+news\.gmane\.org:gwene\.com\.feedburner\.mydealz$\)\|\(^alt\.consumers\.free-stuff$\)\|\(^alt\.consumers\.uk-freebies$\)\|\(^nntp\+news\.gmane\.org:gwene\.com\.dealbreaker$\)\|\(^nntp\+news\.gmane\.org:gwene\.com\.feedburner\.mydealz$\)\|\(^alt\.consumers\.free-stuff$\)\|\(^alt\.consumers\.uk-freebies$\)\|\(^nntp\+news\.gmane\.org:gwene\.com\.dealbreaker$\) The download terminated at that point. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 gnus depends on: ii dpkg 1.15.8.13 Debian package management system ii install-info 4.13a.dfsg.1-6 Manage installed documentation in ii make 3.81-8 An utility for Directing compilati ii ucf 3.0025+nmu1Update Configuration File: preserv ii xemacs21 21.4.22-3.1highly customizable text editor ii xemacs21-mule [xemacs21] 21.4.22-3.1highly customizable text editor -- Versions of packages gnus recommends: ii idn1.15-2Command line and Emacs interface t ii openssl0.9.8o-4squeeze13 Secure Socket Layer (SSL) binary a Versions of packages gnus suggests: ii netpbm2:10.0-12.2+b1 Graphics conversion tools between pn w3m-elnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699152: notmuch-mutt: Please document the fact that extra terms can be passed by the macro
Package: notmuch-mutt Version: 0.13.2-1 Severity: minor Tags: patch Dear Maintainers, I was about hacking notmuch-mutt to make it possible to restrict the search to the last month only when I discovered in the source code that this was already very possible, but simply badly documented. So, instead of a perl patch, I provide a documentation one. I hope you'll find it useful, Mt --- /home/mquinson/lab/130128-notmuch-mutt.orig 2013-01-28 10:09:48.722323565 +0100 +++ /usr/bin/notmuch-mutt 2013-01-28 10:29:26.374270563 +0100 @@ -213,13 +213,19 @@ macro index F6 \ enter-commandunset wait_keyenterpipe-messagenotmuch-mutt tag -inboxenter \ notmuch: remove message from inbox +macro index F7 \ + enter-commandunset wait_keyentershell-escapenotmuch-mutt --prompt search $(date +%s --date='last month')..$(date +%s) enterchange-folder-readonly~/.cache/notmuch/mutt/resultsenter \ + notmuch: search mail (last month) The first macro (activated by F8) prompts the user for notmuch search terms and then jump to a temporary maildir showing search results. The second macro (activated by F9) reconstructs the thread corresponding to the current mail and show it as search results. The third macro (activated by F6) removes the tag Cinbox from the current message; by changing C-inbox this macro may be -customised to add or remove tags appropriate to the users notmuch work-flow. +customised to add or remove tags appropriate to the users notmuch work-flow. +The fourth macro demonstrates how notmuch-mutt forwards any additional terms +to notmuch. Here, this is used to limit the search to mails which age is not +more than one month. To keep notmuch index current you should then periodically run Cnotmuch new. Depending on your local mail setup, you might want to do that via cron,
Bug#699153: unblock: gnunet/0.9.3-6
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Dear release team, I prepared a new revision of GNUnet fixing 2 bugs (wich were fixed in 0.9.3-4) to make gnunet build and install on kfreebsd. Here is the changelog (the complete debdiff is attached): * Fix build on kfreebsd, thanks to Christoph Egger (Closes: #688486). * gnunet-server.postinst: check the existence of a binary before changing its permissions (Closes: #688484). Would you consider to give gnunet 0.9.3-6 a freeze exception ? Cheers, Bertrand unblock gnunet/0.9.3-6 gnunet.diff Description: Binary data
Bug#698945: [Pkg-ia32-libs-maintainers] Bug#698945: The working settings on machine 1
On Fri, Jan 25, 2013 at 04:00:47PM +, Holger Weiss wrote: What I did to make the software work on machine1 with ia32-libs (20120926) is, that I had to create the following links: mv /usr/lib/libXm.so.3 /usr/lib/libXm.so.3.off #this deactivates actual libXm.so.3 ln -s /usr/lib/libXm.so.4 /usr/lib/libXm.so.3 #create link to libXm.so.4 for 64Bit ln -s /usr/lib32/libXm.so.2 /usr32/lib/libXm.so.3 #create link to libXm.so.2 for 32Bit How can I do the equal thing on machine2 with ia32-libs (1:0.4) ? Debian does not have a libXm.so.3 at all, only libXm.so.2 and libXm.so.4, which are in lesstif2 and libmotif4 respectively. 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#690092: scli: FTBFS due to glib changes
retitle 690092 scli: FTBFS due to glib changes # justification: FTBFS severity 690092 serious thanks Hi, this has begun FTBFSing in Debian sid, too. As IIRC the glib from sid is transitioning to wheezy, this is an RC bug, since it prevents rebuilding scli. […] gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stub -I../proc -pthread -I/usr/include/glib-2.0 -I/usr/lib/m68k-linux-gnu/glib-2.0/include -I/usr/include/gsnmp -I/usr/include/gnet-2.0 -I/usr/lib/gnet-2.0/include/ -pthread -I/usr/include/glib-2.0 -I/usr/lib/m68k-linux-gnu/glib-2.0/include -I/usr/include/gnet-2.0 -I/usr/lib/gnet-2.0/include/ -I/usr/include/libxml2 -g -O2 -c sflow.c gcc -g -O2 -o scli scli.o vendors.o basic.o monitor.o cmds.o thread.o fmt.o xml.o netconf.o system.o entity.o interface.o disman.o snmp.o ip.o udp.o tcp.o bridge.o atm.o ether.o ospf.o printer.o isdn.o rs232.o sonet.o cisco.o nortel.o netsnmp.o 3com.o hp.o sflow.o ../proc/libproc.a ../stub/libstub.a -lgsnmp -lgnet-2.0 -lgnet-2.0 -Wl,--export-dynamic -pthread -lgmodule-2.0 -lrt -lglib-2.0 -L/usr/lib -lxml2 -lreadline -lncurses scli.o: In function `main': /«PKGBUILDDIR»/scli/scli.c:383: undefined reference to `g_thread_init' collect2: ld returned 1 exit status make[3]: *** [scli] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/scli' […] bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699088: RM: gnunet-dev gnunet-dbg gnunet-client gnunet-common gnunet-server [kfreebsd-amd64 kfreebsd-i386] -- RoRM; porting changes reverted for wheezy
Hi, I prepared a new revision of gnunet providing the missing binaries for kfreebsd. I already filled an unblock request in #699153 [1]. Would you consider unblocking this new revision instead of removing gnunet from kfreebsd ? Cheers, Bertrand [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699153 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698945: [Pkg-ia32-libs-maintainers] Bug#698945: ia32-libs(20120926) works - ia32-libs1.0:4 does not !
Hi, I see that I have a hard time to understand the new multiarch usage/architecture. I searche the web for some information about it, but did not find good descriptions. Previously, the /usr/lib32 contained all 32-bit libs. I think I need a liitle support from you to understand the new multiarch: Ia32-libs is only a transitional meta package. You shouldn't need that at all. What you need are the 32bit libraries that ADS2012 requires. The simplest would be to simply install an ADS2012 debian package for i386. That does not exist ! Its a proprietary installer using java. If that doesn't exist then you need to install the i386 package for required libraries. You can do that under multiarch by appending :i386 to the package name. What do you mean with using multiarch ? Is this a special program ? So far I understood, that multiarch is just a package containing libraries only ? Can you give me a short example please. Debian does not have a libXm.so.3 at all, only libXm.so.2 and libXm.so.4, which are in lesstif2 and libmotif4 respectively. MfG Goswin That is correct, but so far a symbolic link to the existing libs made it work ! Lets get the problem solved - I will be online !
Bug#699088: RM: gnunet-dev gnunet-dbg gnunet-client gnunet-common gnunet-server [kfreebsd-amd64 kfreebsd-i386] -- RoRM; porting changes reverted for wheezy
On Mon, Jan 28, 2013 at 10:50:08 +0100, Bertrand Marc wrote: Hi, I prepared a new revision of gnunet providing the missing binaries for kfreebsd. I already filled an unblock request in #699153 [1]. Would you consider unblocking this new revision instead of removing gnunet from kfreebsd ? I would prefer not to. Has the package been actually tested to *work*, not just build, on kfreebsd? Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660425: Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)
Thanks Ben, not sure how I missed 660425 the first time around. On Wed, 2013-01-23 at 14:50 +, Ben Hutchings wrote: On Tue, 2013-01-22 at 10:15 +0100, Mattias Eriksson wrote: Hi! I have switched back to the current stable kernel in squeeze, 2.6.32-46, since I need the machine to be up and running. And now it is just as stable as it was before. Even though I have never had any real issues using xen and VIA nano (64bit), the CPU is officially not supported by xen, as far as I can see: (XEN) Domain heap initialised (XEN) CPU: Vendor unknown, using generic init. (XEN) CPU: Your system may be unstable. (XEN) Processor #0 6:15 APIC version 20 So, I think there are to many uncertainties for me to dig into this further. [...] Yes, there may be quirks and bugs in VIA/Centaur processors that Xen should handle (which I couldn't find any documentation about). There was a bit of work done to support VIA stuff in, I think, the 4.2 release. I think it is probably not relevant to this specific EFLAGS.AC issue, although it may cause other problems of course. However: http://bugs.debian.org/660425 is a report of an alignment check under Xen while running Linux 2.6.32, and Jonathan Nieder found (message #17) more reports of this - on Intel and AMD processors. In all these cases (and yours) the AC flag is shown as enabled, so alignment checks should be expected. The connection to Xen is this: the AC flag can be set by any program, but the processor ignores it when running code at the maximum privilege level. So normally the kernel is not affected, but under Xen it is running at lower privilege and therefore it is affected. Xen has to clear the AC flag whenever it switches from user mode to a (PV) guest kernel. A bug of this type was fixed in the 4.0.0-rc9 timeframe, but that is before the version of Xen being used here. It's interesting that the kernel version appears to be a relevant factor, but I expect it is simply exposing a hypervisor bug. It seems that the new SMAP (Supervisor Mode Access Prevention) CPU feature reuses the EFLAGS.AC bit, that might explain why we are seeing this bit set in kernel mode with newer kernels. However it looks like this was added in 3.7 and I can't see it backported in either the kernel.org 3.2.y stable kernels or Debian's patch queue. SMEP is in 3.2 but I don't think that involves EFLAGS.AC. It would be great if you could try the 3.2.0 kernel again with the nosmap kernel option though. I don't think the guest kernel itself needs to be aware of this because there is never a direct transition from user mode to kernel mode. Agreed, with a 64-bit PV kernel you always have to pass through the hypervisor when transitioning from user to supervisor mode (which both run in Ring 3 under Xen) Ian. -- Ian Campbell Current Noise: Isis - Threshold Of Transformation Be incomprehensible. If they can't understand, they can't disagree. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687988: blender: Fails to display solid objects with r600/gallium3D
Hi Roger! Since I can't reproduce this issue on my box, could you possibly test the actual version in experimental suite, based on 2.65a release? And please let me know if the issue still persists; otherwise, I'd like to close this bug report in next revision (almost ready to go). Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 83B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
Package: src:hdf5 Version: 1.8.8-9 Severity: serious In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4, libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | libhdf5-1.8.4) In Wheezy those libraries are not longer ABI compatible, therefore the serial version was renamed libhdf5-7 and also the packages of the others versions, for example libhdf5-openmpi-7, has a provides line: Provides: libhdf5-1.8, libhdf5-7 So you can install for example, r-cran-hdf5 and it will install by default the serial version (libhdf5-7), but you can also install it at the same time than libhdf5-openmpi-7 (or you might have it installed already) and then you will get it installed with the openMPI version despite being built against the serial version, that as said isn't ABI compatible. Some packages, such as slepc, have their build dependencies explicitly against the openMPI version and those are OK. Due the ABI incompatibility we can not longer use the same scheme than in Squeeze, but I think having the serial version named libhdf5-7 is confusing. Possible solutions... given the proximity of the release I'm aware some of them might not be possible but I'm listing everything for the sake of completeness, don't jump in your chair when reading some of the possibilities listed :-) a) Have libhdf5-7 renamed back with the *serial* label (libhdf5-serial-1.8.4) and also the -dev packages. Then have the packages using hdf5 depending on the supported implementation(s), that is if they support several implementation provide a binary for implementation: r-cran-hdf5-serial r-cran-hdf5-openMPI b) Switch all the packages to use only one of the implementation except those that only work in of the implementations, depending explicitly in *-serial-* or *-openmpi-* (or mpich in those archs that don't support openMPI). b.1) make this implementation by default to be the serial version b.2) make this implementation by default to be the openMPI version. Which doesn't sound like a crazy idea if you look at the popcon [1] and think the context hdf5 is widely used (supercomputing). c) Remove the provides from libhdf5-openmpi-7 and libhdf5-mpich-7 and keep the status quo. You either install libhdf5-openmpi-7 with the packages needing this implementation or you install libhdf5-7 with the packages depending on this one. If you go to decide for the openmpi version and you need a package only built for the serial version, you would need to rebuild it. (This is somehow a variation of b.1) because all the stuff is built against the serial version unless the maintainer explicitily puts the openmpi one ) d) ? :) In any case, how to switch or handle the different implementation would be nice to have documented in a README file. Ana [1] http://qa.debian.org/popcon.php?package=hdf5 If you look at the amout of installations of libhdf5-openmpi-dev installations it is the same that libhdf5-dev and growing faster. As curiosity note: after the rename of the serial version to be the *default* version was uploaded to unstable around January 2012, you can see libhdf5-7 rocketed in the popcon graph. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699154: Sorry for mistake.
I am very sorry. It was my mistake. I saw into strace and revealed that I forgot to mount /proc and /dev into my schroot sandbox for chromium. Sorry. Just close it. -- ** * jabber: free...@jabber.mipt.ru * * Registered linux user #546240* ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656222: uzbl: does not remove /usr/bin/x-www-browser alternative on uninstallation
Andreas Beckmann scrisse: I intend to NMU uzbl to fix the alternative handling with the previously posted patch and hope that we can still get this fix into wheezy. Sorry for the delay and thanks for the patch. It was not on my ToDo list for Wheezy at this point, but if it's ok for the release team, please go ahead. uzbl is in collab-maint git, you may also want to push it there. Cheers, Luca -- .''`. | ~[ Luca BRUNO ~ (kaeso) ]~ : :' : | Email: lucab (AT) debian.org ~ Debian Developer `. `'` | GPG Key ID: 0x3BFB9FB3 ~ Free Software supporter `-| HAM-radio callsign: IZ1WGT ~ Networking sorcerer signature.asc Description: PGP signature
Bug#687988: blender: Fails to display solid objects with r600/gallium3D
On Mon, Jan 28, 2013 at 10:58:07AM +0100, Matteo F. Vescovi wrote: Since I can't reproduce this issue on my box, could you possibly test the actual version in experimental suite, based on 2.65a release? And please let me know if the issue still persists; otherwise, I'd like to close this bug report in next revision (almost ready to go). Sorry, I should have replied sooner. I did some more testing here on Windows and Mac in addition to Linux, and couldn't reproduce it. It turned out to be a bug in the Mesa software rendering--installing the Radeon proprietary driver fixed things. For some reason my Radeon HD6970 was defaulting to use software rendering with Xorg and there was some other issue with the ati/radeon driver. Whatever the cause here, it's definitely not a bug in blender, so I would suggest reassigning it to Mesa. Thanks, 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#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
tags 699155 help thanks On 28/01/2013 11:04, Ana Guerrero wrote: Package: src:hdf5 Version: 1.8.8-9 Severity: serious In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4, libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | libhdf5-1.8.4) Merci Ana for this full bug. It would be nice to have some help here. I must admit that I don't know what would be the best solution... 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#631729: irssi-plugin-xmpp: Memory corruption and crash with /xmppconnect
tags 631729 + patch
thanks
Hi,
I used “nc -4 -l -p 5222” to simulate a local jabber server, then
started irssi, used /load xmpp and /xmppconnect -h localhost f@b to
trigger the issue.
Attached you can find the patch with which I have come up. Here is the
description:
Previously, loudmouth would set socket-watch_connect to NULL when
encountering an error. When the connection attempt (to a different
IPv6) succeeded later on, _lm_socket_succeeded would therefore not
remove the socket_connect_cb watcher, leading to socket_connect_cb
being called upon socket activity and segfaulting the program.
This patch fixes the issue for me, but I don’t use irssi-plugin-xmpp
normally, so testing/review is welcome.
--
Best regards,
Michael
Description: fix crash when falling back from IPv6 to IPv4
Previously, loudmouth would set socket-watch_connect to NULL when
encountering an error. When the connection attempt (to a different IPv6)
succeeded later on, _lm_socket_succeeded would therefore not remove the
socket_connect_cb watcher, leading to socket_connect_cb being called upon
socket activity and segfaulting the program.
Author: Michael Stapelberg stapelb...@debian.org
Bug-Debian: http://bugs.debian.org/631729
Last-Update: 2013-01-28
--- loudmouth-1.4.3.orig/loudmouth/lm-socket.c
+++ loudmouth-1.4.3/loudmouth/lm-socket.c
@@ -529,7 +529,6 @@ socket_connect_cb (GIOChannel *source,
/* error condition, but might be possible to recover
* from it (by connecting to the next host) */
if (!_lm_socket_failed_with_error (connect_data, err)) {
-socket-watch_connect = NULL;
goto out;
}
}
@@ -560,7 +559,6 @@ socket_connect_cb (GIOChannel *source,
_lm_sock_close (connect_data-fd);
_lm_socket_failed_with_error (connect_data, err);
-socket-watch_connect = NULL;
goto out;
}
}
Bug#699156: debian-installer: d-i should offer users the installation of backported packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: debian-installer Version: 20110106+squeeze4+b2 Severity: wishlist *** Please type your report below this line *** When I set up a new i486-system (i.e.32-bit-PC) yesterday, I had to add backported packages manually and take care about pinning the backports correctly, so that they are prioritzed over normal otherwise stable packages. When using Xubuntu 12.04.1-alternate in expert-mode, the user is asked, If backported software should be included in the installation, in fact this is even the default there, if you just press 'Enter' at every question asked. Probably using backported packages should not be the default in debian, but at least for expert-installations the user should be asked wether backported packages should be included or not and there should be taken care about appropriate pinning of those packages, I set them to a priority of 1001, which was fine. In Ubuntu LTS the 3.5-series Quantal-kernel will even be made the default in favour of 3.2 and it will be distributed as a security/stability update. - -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.23ldt (SMP w/3 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlEGUHcACgkQ5+rBHyUt5wuJTgCgrVxn/H5lB6MiFX8iTAIlV0kK T7cAnjfIK5uaJ2izT5hLhYjfZmGjRD1l =tdJM -END PGP SIGNATURE-
Bug#698985: alsa-utils: alsamixer does not work. Broken pipe.
* Azuki eml9...@email.com [2013-01-28 03:50 -0500]: It turns out that pulse doesn't cooperate with your soundcard. As told before stop the pulsedaemon and prevent it for restarting. Else mv /etc/asound.conf /etc/asound.conf.save and run alsamixer again. It would be great if you answer always to 698...@bugs.debian.org as well. Other users may be interested for similar probs. I tried the following. $ mv /etc/asound.conf /etc/asound.conf.save I confirmed that .asoundrc does not exist in HOME directory. Then I completely deleted pulseaudio. And I confirmed .pulse directory and .pulse-cookie does not exist in HOME. $ apt-get --purge autoremove pulseaudio After having confirmed that pulseaudio does not run, I ran alsamixer. $ alsamixer cannot load mixer controls: Broken pipe $ amixer -c 0 amixer: Mixer hw:0 load error: Broken pipe Try a newer kernel as 2.6.32 alsa-drivers seems to be too old for your card. Again: Please reply tё 698...@bugs.debian.org as well. Elimar -- We all know Linux is great... it does infinite loops in 5 seconds. -Linus Torvalds -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667599: hdf5 upgrade Squeeze- Wheezy (#667599, #667526)
Hi! There are *two* problems with the upgrade of hdf5 from Squeeze to Wheezy that are a consequence of the problem of the fix for #566541. One of then, reported in (#667599, #667526), can be solved easily as explained by marga at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667599#62 and others have hinted before. The second problem is related with this one and more complicated to solve. I haved filed the bug report #699155 for this. About this problem, in short, if you have installed the openmpi version, the upgrade will install you the serial implementation, and remove the openmpi implementation. E.g. minimal installation of squeeze where libhdf5-openmpi-1.8.4 and hdf5-tools are installed: ii hdf5-tools 1.8.4-patch1-2 Hierarchical Data Format 5 (HDF5) - Runtime tools ii libhdf5-openmpi-1.8.4 1.8.4-patch1-2 Hierarchical Data Format 5 (HDF5) - runtime files - OpenMPI version ii libhdf5-serial-1.8.41.8.4-patch1-2 Hierarchical Data Format 5 (HDF5) - runtime files - serial version ii r-cran-hdf5 1.6.9-2+b1 GNU R package interfacing the NCSA HDF5 library If we update this system to Wheezy, you'll get: # apt-get -u dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: console-terminus defoma libept1 libhdf5-openmpi-1.8.4 libpango1.0-common libperl5.10 portmap x-ttcidfont-conf The following NEW packages will be installed: [...] libhdf5-7 [...] hdf5-tools [...] 368 upgraded, 174 newly installed, 8 to remove and 0 not upgraded. Need to get 252 MB of archives. After this operation, 302 MB of additional disk space will be used. Do you want to continue [Y/n]? The openmpi version is upgraded with the serial version instead of being replaced with libhdf5-openmpi-7. In the case of dolfin-dev (#667599) in Squeeze, the package has the following dependency chain to hdf5 (as somebody else has analyzed already in the bug report): dolfin-dev - libdolfin1.0-dev - libslepc3.0.0-dev - libslepc3.0.0 - libhdf5-openmpi-1.8.4 and when upgraded, we have the reported problem. In wheezy, libslepc3.2 depends explicitiy on the openmpi version only. This means if we install libslepc3.0.0 in wheezy we must switch all our system to use the openmpi library. For simgear-dev (#667526), the chain dependency in Squeeze is: simgear-dev - simgear1.9.1 - libopenscenegraph65 - libgdal1-1.6.0 - libhdf5-serial-1.8.4 | libhdf5-1.8.4 Where libhdf5-1.8.4 could be provided by libhdf5-openmpi-1.8.4 and we have the same problem that with dolfin-dev. Although in this case the dependency can be satisfied both by the serial and the openmpi packages in Wheezy. This is wrong because both libraries provided different ABIs as reported in bug #699155 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696650: [PATCH v2] md: protect against crash upon fsync on ro array
Subject was: Re: fsync() on read-only RAID triggers BUG
On 27.01.2013 17:39, Christoph Hellwig wrote:
On Sat, Jan 26, 2013 at 07:44:40PM +, Ben Hutchings wrote:
I applied this on top of 3.2.37 and it certainly fixes the crash.
However I wonder whether fsync() should fail or should immediately
succeed. I don't know whether the installer expects it to succeed.
It should succeed.
O.K., then I hope Neil applies the attached patch. I've changed the
return value to success.
This is also something for linux-stable and should apply to many kernel
versions without an issue.
From fe0357344877c9b9cc623fd582a4e0670e448317 Mon Sep 17 00:00:00 2001
From: Sebastian Riemer sebastian.rie...@profitbricks.com
Date: Fri, 25 Jan 2013 12:46:59 +0100
Subject: [PATCH v2] md: protect against crash upon fsync on ro array
If an fsync occurrs on a read-only array, we need to send a
completion for the IO and may not increment the active IO count.
Otherwise, we hit a bug trace and can't stop the MD array anymore.
By advice of Christoph Hellwig we silently return success.
Cc: Christoph Hellwig h...@infradead.org
Cc: Ben Hutchings b...@decadent.org.uk
Cc: NeilBrown ne...@suse.de
Signed-off-by: Sebastian Riemer sebastian.rie...@profitbricks.com
Reported-by: Ben Hutchings b...@decadent.org.uk
---
drivers/md/md.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 3db3d1b..475e0be 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -322,6 +322,11 @@ static void md_make_request(struct request_queue *q,
struct bio *bio)
}
finish_wait(mddev-sb_wait, __wait);
}
+ if (mddev-ro == 1 unlikely(rw == WRITE)) {
+ rcu_read_unlock();
+ bio_endio(bio, 0);
+ return;
+ }
atomic_inc(mddev-active_io);
rcu_read_unlock();
--
1.7.1
Bug#699157: linux-image-3.2.0-4-amd64: mount -o remount, ro on bind mount causes source filesystem to become read-only
Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I'm experiencing what seems to be a kernel bug with read-only remounting of a bind mount (creating a read-only bind mount). After running the following commands, both /foo/dir_ro *and* /foo/dir become read-only: mount --bind /foo/dir /foo/dir_ro mount -o remount,ro /foo/dir_ro Running 'mount -o remount,rw /foo/dir' rectifies the situation, leaving it as I intended (/foo/dir writable, /foo/dir_ro read-only). Thanks, Zev Weiss -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/vg--ssd-sysroot ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [3.010929] Console: switching to colour frame buffer device 240x75 [3.013438] fb0: nouveaufb frame buffer device [3.013440] drm: registered panic notifier [3.013445] [drm] Initialized nouveau 1.0.0 20120316 for :01:00.0 on minor 0 [3.799556] md: md0 stopped. [3.800607] md: bindsdb [3.800731] md: bindsde [3.807141] md: raid1 personality registered for level 1 [3.807458] bio: create slab bio-1 at 1 [3.807521] md/raid1:md0: active with 2 out of 2 mirrors [3.807541] md0: detected capacity change from 0 to 2000264560640 [3.835885] md0: unknown partition table [3.962862] md: md1 stopped. [3.965536] md: bindsdd [3.965706] md: bindsda [3.967957] md/raid1:md1: active with 2 out of 2 mirrors [3.967976] md1: detected capacity change from 0 to 500106674176 [4.024324] EXT4-fs (dm-0): re-mounted. Opts: (null) [4.031249] md1: unknown partition table [4.251852] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro,discard [4.295424] loop: module loaded [4.959331] Adding 4194300k swap on /dev/mapper/vg--ssd-swap. Priority:-1 extents:1 across:4194300k SS [6.045526] kjournald starting. Commit interval 5 seconds [6.045628] EXT3-fs (sdc1): using internal journal [6.045632] EXT3-fs (sdc1): mounted filesystem with ordered data mode [6.047893] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [6.050170] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [6.122924] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null) [6.236900] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null) [6.293508] kjournald starting. Commit interval 5 seconds [6.293634] EXT3-fs (dm-5): mounted filesystem with ordered data mode [6.331067] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [6.780483] r8169 :04:00.0: eth0: link down [6.780490] r8169 :04:00.0: eth0: link down [6.781506] ADDRCONF(NETDEV_UP): eth0: link is not ready [9.163430] r8169 :04:00.0: eth0: link up [9.164417] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.737732] RPC: Registered named UNIX socket transport module. [ 16.737736] RPC: Registered udp transport module. [ 16.737738] RPC: Registered tcp transport module. [ 16.737740] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.749189] FS-Cache: Loaded [ 16.759249] FS-Cache: Netfs 'nfs' registered for caching [ 16.768939] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 17.790334] ip_tables: (C) 2000-2006 Netfilter Core Team [ 17.822734] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 17.925057] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 18.898599] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 18.898908] NFSD: starting 90-second grace period [ 20.112007] eth0: no IPv6 routers present [ 242.431813] Kprobes globally unoptimized [ 242.468323] stap_7a30e3695e76472eb616ead2970b485_4039: systemtap: 1.7/0.152, base: a057e000, memory: 14data/16text/1ctx/2058net/18alloc kb, probes: 1 [ 255.614619] stap_df243a220556068fca70eedb018891c_4194: systemtap: 1.7/0.152, base: a0587000, memory: 14data/16text/1ctx/2058net/18alloc kb, probes: 1 [ 337.753052] stap_7dc557923d2612917434539e96d25458_4407: systemtap: 1.7/0.152, base: a059, memory: 18data/16text/1ctx/2058net/18alloc kb, probes: 1 [ 5682.988021] usb 1-1.1: USB disconnect, device number 3 [ 5687.028095] usb 1-1.1: new low-speed USB device number 5 using ehci_hcd [ 5687.124839] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c016 [ 5687.124843] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 5687.124846] usb 1-1.1: Product: Optical USB Mouse [ 5687.124849] usb 1-1.1: Manufacturer: Logitech [ 5687.127314] input: Logitech Optical USB Mouse as /devices/pci:00/:00:1a.7/usb1/1-1/1-1.1/1-1.1:1.0/input/input6 [ 5687.127474] generic-usb 0003:046D:C016.0004: input,hidraw0: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on
Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
On Mon, Jan 28, 2013 at 11:04:09 +0100, Ana Guerrero wrote: Package: src:hdf5 Version: 1.8.8-9 Severity: serious In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4, libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | libhdf5-1.8.4) In Wheezy those libraries are not longer ABI compatible, therefore the serial version was renamed libhdf5-7 and also the packages of the others versions, for example libhdf5-openmpi-7, has a provides line: Provides: libhdf5-1.8, libhdf5-7 So you can install for example, r-cran-hdf5 and it will install by default the serial version (libhdf5-7), but you can also install it at the same time than libhdf5-openmpi-7 (or you might have it installed already) and then you will get it installed with the openMPI version despite being built against the serial version, that as said isn't ABI compatible. do you have pointers/details about that ABI incompatibility? I'm pretty sure I looked through exported symbols and headers from hdf5 a year ago, and didn't see anything that would break when building against the serial version and running against openmpi, but I may have missed something. Cheers, Julien -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687988: blender: Fails to display solid objects with r600/gallium3D
reassign 687988 src:mesa 8.0.5-3 thanks Hi Roger! On Mon, Jan 28, 2013 at 11:10 AM, Roger Leigh rle...@codelibre.net wrote: Sorry, I should have replied sooner. I did some more testing here on Windows and Mac in addition to Linux, and couldn't reproduce it. It turned out to be a bug in the Mesa software rendering--installing the Radeon proprietary driver fixed things. For some reason my Radeon HD6970 was defaulting to use software rendering with Xorg and there was some other issue with the ati/radeon driver. OK. Good to know. ;-) Whatever the cause here, it's definitely not a bug in blender, so I would suggest reassigning it to Mesa. Doing it right now. Thanks for your efforts in sorting this out. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 83B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698102: eglibc: initgroups changes egid on kfreebsd
Unfortuantely, POSIX declined to specify setgroups() and initgroups() is not in any standard, so it's hard to say which behavior is right and which is wrong. It seems possible to argue any of the following: 1. The bug is in kFreeBSD's implementation of setgroups(), which must be fixed so that eglibc's initgroups() implementation works as expected. 2. The bug is in eglibc's implementation of initgroups(), which must be fixed so that it works properly with kFreeBSD's setgroups(). 3. Since both behaviors of setgroups() and initgroups() are seen in the wild, programs that depend on the linux kernel behavior are broken and should be fixed as they become known. Personally I'm leaning towards 3 here, since these are buggy not only on debian/kFreeBSD but on real FreeBSD as well. Even POSIX point out that egid might be somewhere in supplementary groups http://pubs.opengroup.org/onlinepubs/9699919799/functions/getgroups.html The getgroups() function shall fill in the array grouplist with the current supplementary group IDs of the calling process. It is implementation-defined whether getgroups() also returns the effective group ID in the grouplist array. Under FreeBSD kernel, the egid is groups[0], see http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_prot.c IMO, there is no bug, the behaviour is implementation-defined. Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699158: ITP: squishyball -- audio sample comparison testing tool
Package: wnpp Severity: wishlist Owner: Jon Dowland j...@debian.org * Package name: squishyball Version : 0.1~svn18785 Upstream Author : Monty mo...@xiph.org * URL : http://svn.xiph.org/trunk/squishyball/ * License : GPL Programming Lang: C Description : audio sample comparison testing tool squishyball is a simple command-line utility for performing double-blind A/B, A/B/X or X/X/Y (A/B/X with additional sample order randomisation) testing of audio samples on the command line. . The user specifies two input files to be compared and uses the keyboard during playback to flip between the randomized samples to perform on-the-fly comparisons. After a predetermined number of trials, squishyball prints the trial results to stdout and exits. . squishyball can be used to help establish what lossy audio codec settings are optimal for a particular combination of user and audio equipment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656835: cron: align /etc/cron.{daily, hourly, monthly, weekly} with @daily, @hourly, @monthly, @weekly
I believe this is done to not race with another periodic job. I.e. the jobs in /etc/cron.daily should not be executed at the same time as /etc/cron.weekly. See #23023 for a real-world example on this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690127: release-notes: Issues: switch dm to get an active consolekit session
On Sun, Jan 27, 2013 at 12:05 +0100, Joost van Baal-Ilić wrote: Hi Wolodja, Thanks a lot for your helpful suggestion! I agree with you :) Could you please do a svn co svn://svn.debian.org/svn/ddp/manuals/trunk/release-notes/en and hack up some DocBook XML code to get your text in? That'd allow me to fix this issue even more soon. If not, I'll get to this issue within about a week, I hope. I'll happily do that once I am sure that the actual solution is indeed the correct one. I am not convinced of that yet and investigated a bit further. I successfully reproduced #598150 here. That is that sessions listed by ck-list-sessions are still marked as active = FALSE (but is-local = TRUE) even if I try the workaround in [0] and use an ~/.xsessions file such as exec ck-launch-session dbus-launch awesome I am not sure which workaround was being referred to in the initially suggested text and I haven't tested if there are actually any problems that arise from the fact that the session is being as inactive. I might find some time to investigate this later though. So far my understanding was that the way I start sessions in ~/.xsession is the correct one and that this method /should/ work, but it looks as if the only sensible recommendation regarding this issue we can give right now is Just switch to gdm, kdm or lightdm. I don't think that this would be acceptable and copied in pkg-utopia-maintainers in the hope that they can provide some authorative feedback on the right way to deal with this. In particular we need authorative advice for users of: 1. startx How should startx users start their sessions? Is the aforementioned way sufficient? What other changes have to be made in order to ensure a correctly working system in the sense that system services like automounting and autoconfiguring network interfaces work as expected? That is: How to fix #598150 and which workaround is being referred to? Please clarify if it is indeed enough to make the changes to ~/.xsession that I suggest below /and/ remove the nox11 in /etc/pam.d/common-session 2. xdm It sounds that xdm users should be encouraged to switch to a supported display manager or asked to start their session via ~/.xsession from xdm as suggested in [1]. (which also means that nox11 has to be removed IIRC) 3. wdm What about wdm and other display managers? On Sat, Jan 26, 2013 at 04:45:57PM +, Wolodja Wentland wrote: Hello, I've just stumbled over this report and have to say that the proposed section in the release notes is suboptimal. This is mainly due because it is unclear which workaround is actually being referred to in the linked bug reports. I would prefer it if the actual changes that are needed are documented in the release notes which would (for startx users) lead to something like: --- snip --- Users of display managers other than kdm, gdm and lightdm (e.g. the xdm and slim display managers) as well as users who start their X session by manually calling startx from a virtual console will likely be hit by problems with system services like automounting devices and autoconfiguring network interfaces. Due to changes in consolekit, display managers need to update their consolekit interaction. The displaymanagers kdm, gdm and lightdm in wheezy have been updated. Others (xdm, slim, a.o.) have not yet been updated. If you're using a not-yet updated display manager, either switch to an updated one before starting to upgrade your system, or make sure to apply the following changes to your configuration (as applicable): startx -- Please make sure that the `consolekit` and `dbus-x11` packages are installed and that both `ck-launch-session` and `dbus-launch` are called in all $HOME/.xsession files as in: exec ck-launch-session dbus-launch $WM That means that if, for example, a user started the awesome window manager with: exec awesome it should be ensured to change this line to: exec ck-launch-session dbus-launch awesome to ensure that the aforementioned system services work correctly. slim ... xdm --- ... --- snip --- I know that the actual text needs to be amended and polished, but I simply wanted to point out that actual instructions in the release notes are much more helpful than just references to (long!) bug reports. Have a wonderful day! [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598150#134 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615020#36 -- Wolodja deb...@babilen5.org 4096R/CAF14EFC 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC signature.asc Description: Digital signature
Bug#699150: RFS: begin/0.1.1-1 (ITP #699113)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mikael, As I mentioned in #debian-mentors yesterday, I find it difficult to justify a Debian package for a tool that could be replaced by existing tools like awk /foo/,EOF much less a package and binary name that are so generic. We try to avoid generic program names in the $PATH namespace (like node, for instance...). I realise that you've done a lot of work learning how to package this and you'd like to see your work included in Debian. Perhaps I could encourage you to contribute to existing packaging teams where you can see packages already in (hopefully) good shape from which you can learn. Working within a team can also help you be more productive in a shorter time. If you're not sure where to look for teams that want help, the rc-alert or wnpp-alert commands can give you a list of packages and bugs that pertain to what is installed on your system. cheers Stuart - -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEGVuEACgkQn+i4zXHF0ai/DwCgrciD5+w5PFr4hQaiNEBOc5+j GpYAn2gyx+OEd5jCdVQnRMcNVBqW5EcM =oozT -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#698945: [Pkg-ia32-libs-maintainers] Bug#698945: The working settings on machine 1
Debian does not have a libXm.so.3 at all, only libXm.so.2 and libXm.so.4, which are in lesstif2 and libmotif4 respectively. I understand, that using multiarch is refering to apt-get and can be used as apt-get install package:arch . Here is what happens with multiarch: # dpkg --print-foreign-architectures i386 # dpkg --print-architecture amd64 # apt-get install libmotif4:i386 . Die folgenden Pakete werden ENTFERNT: (removed) libmotif4 Die folgenden NEUEN Pakete werden installiert: (installed) libmotif4:i386 0 aktualisiert, 1 neu installiert, 1 zu entfernen und 24 nicht aktualisiert. Es müssen noch 0 B von 1.332 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 602 kB Plattenplatz freigegeben. Möchten Sie fortfahren [J/n]? I cannot have both versions i386 and amd64 libs at the same time on my system, is this correct ?
Bug#686376: application can be terminated after closing all tabs
As Karsten Hilbert highlighted in [1] ginkgocadx can be closed after all tabs (including Start page) are closed. Of course this is extremely counter-intuitive but shouldn't be too annoying after user(s) learn how to close it. [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686376#25 -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- If any remedy is tested under controlled scientific conditions and proved to be effective, it will cease to be alternative and will simply become medicine. So-called alternative medicine either hasn't been tested or it has failed its tests. -- Richard Dawkins, 2007 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699002: grub: grub 2.00 in experimental may be missing kfreebsd = 9.1 amd64 fix
Control: tags -1 pending On Sat, Jan 26, 2013 at 04:12:57AM +0100, Juergen Lock wrote: [This is not the version I'm reporting the bug against, I'm using a livecd just to run reportbug...] It's OK (and indeed encouraged) to edit the Version field manually in such cases. I'm not using debian kfreebsd myself here (just plain FreeBSD), but I noticed debian now has grub 2.00 in experimental so I checked if the bugfix patch to boot (k)freebsd = 9.1 amd64 kernels has been merged and it seems to me it's not. The original thread is here: http://lists.freebsd.org/pipermail/freebsd-stable/2012-July/068924.html The pastebin link for the grub maintainer's patch in that post expired so I meanwhile also mirrored it here: http://people.freebsd.org/~nox/tmp/grub2-paste_180121.patch The upstream grub bzr commit link is: http://bzr.savannah.gnu.org/lh/grub/trunk/grub/revision/4556 Thanks. I've backported this for my next upload to experimental. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698985: alsa-utils: alsamixer does not work. Broken pipe.
Try a newer kernel as 2.6.32 alsa-drivers seems to be too old for your card. Again: Please reply tё 698...@bugs.debian.org as well. The former reports are results using 3.2.0-0.bpo.4-rt-amd64. And I tried with the Ubuntu 13.04 (Raring Ringtail) LiveDVD, but was a result same as what I reported so far. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699159: Enable pam_tty_audit module
Source: pam Version: 1.1.3-7.1 Severity: wishlist Dear maintainer, PAM is built with with the --disable-audit configure option, so the pam_tty_audit module is not included libpam-modules or other binary packages. Said module is useful in high-security environments requiring an audit trail of administrator activities. Please consider including the module either in libpam-modules, or creating a separate binary package (libpam-tty-audit?) to avoid dependency to libaudit0. I have manually tested compiling the module in Squeeze and it appears to work just fine. I have not yet tested it in Wheezy. Best regards, Henrik Ahlgren -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697101: tpu: freerdp/1.0.1-1.1+deb7u1 (pre-approval)
Oops, I somehow missed the previous mail. I just uploaded a fixed revision to t-p-u with wrapper functions marked as static and symbols file change reverted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote: On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote: do you have pointers/details about that ABI incompatibility? I'm pretty sure I looked through exported symbols and headers from hdf5 a year ago, and didn't see anything that would break when building against the serial version and running against openmpi, but I may have missed something. I didn't check further than the attached diff, there are mostly symbols being added in the openMPI version but also some symbols dissapearing. OK. So you didn't get any runtime issues with this? -H5E_get_stack declared in src/H5Epkg.h, which doesn't seem to be in libhdf5-dev. -H5TS_cancel_count_dec -H5TS_cancel_count_inc -H5TS_create_thread declared in src/H5TSprivate.h, probably not intended to be public (and not installed in the -dev package). -H5TS_mutex_lock -H5TS_mutex_unlock same here. -H5TS_pthread_first_thread_init and again. Unless you have evidence of an actual problem with software using hdf5 I'm tempted to close this as a non-bug... Cheers, Julien -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699160: piuparts: .udeb handling
Package: piuparts Severity: minor Hi, piuparts.debian.org is quite useful, but it seems to be not able to handle .udeb packages. I'm maintain ttf-cjk-compact package and piuparts.d.o reports unknown status thus it only produce udeb. Binary:ttf-cjk-compact-udeb and see also http://piuparts.debian.org/sid/maintainer/d/debian-b...@lists.debian.org.html If piuparts don't want to handle .udeb files, just report as pass seems to be better. Could you check it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote: do you have pointers/details about that ABI incompatibility? I'm pretty sure I looked through exported symbols and headers from hdf5 a year ago, and didn't see anything that would break when building against the serial version and running against openmpi, but I may have missed something. I didn't check further than the attached diff, there are mostly symbols being added in the openMPI version but also some symbols dissapearing. Ana --- libhdf5-7/libhdf5_fortran.so.7 +++ libhdf5-openmpi-7/libhdf5_fortran.so.7 @@ -395,6 +395,12 @@ h5eset_auto_c_ h5fclose_c_ h5fcreate_c_ +__h5fdmpio_MOD_h5pget_dxpl_mpio_f +__h5fdmpio_MOD_h5pget_fapl_mpio_f +__h5fdmpio_MOD_h5pget_fapl_mpiposix_f +__h5fdmpio_MOD_h5pset_dxpl_mpio_f +__h5fdmpio_MOD_h5pset_fapl_mpio_f +__h5fdmpio_MOD_h5pset_fapl_mpiposix_f h5fflush_c_ h5fget_access_plist_c_ h5fget_create_plist_c_ @@ -553,6 +559,7 @@ h5pget_data_transform_c_ h5pget_double_c_ h5pget_driver_c_ +h5pget_dxpl_mpio_c_ h5pget_edc_check_c_ h5pget_est_link_info_c_ h5pget_external_c_ @@ -560,6 +567,8 @@ h5pget_fapl_core_c_ h5pget_fapl_direct_c_ h5pget_fapl_family_c_ +h5pget_fapl_mpio_c_ +h5pget_fapl_mpiposix_c_ h5pget_fapl_multi_c_ h5pget_fclose_degree_c_ h5pget_fill_time_c_ @@ -758,6 +767,7 @@ h5pset_data_transform_c_ h5pset_deflate_c_ h5pset_double_c_ +h5pset_dxpl_mpio_c_ h5pset_edc_check_c_ h5pset_est_link_info_c_ h5pset_external_c_ @@ -765,6 +775,8 @@ h5pset_fapl_core_c_ h5pset_fapl_direct_c_ h5pset_fapl_family_c_ +h5pset_fapl_mpio_c_ +h5pset_fapl_mpiposix_c_ h5pset_fapl_multi_c_ h5pset_fapl_multi_sc_ h5pset_fapl_sec2_c_ --- libhdf5-7/libhdf5_fortran.so.7.0.2 +++ libhdf5-openmpi-7/libhdf5_fortran.so.7.0.2 @@ -395,6 +395,12 @@ h5eset_auto_c_ h5fclose_c_ h5fcreate_c_ +__h5fdmpio_MOD_h5pget_dxpl_mpio_f +__h5fdmpio_MOD_h5pget_fapl_mpio_f +__h5fdmpio_MOD_h5pget_fapl_mpiposix_f +__h5fdmpio_MOD_h5pset_dxpl_mpio_f +__h5fdmpio_MOD_h5pset_fapl_mpio_f +__h5fdmpio_MOD_h5pset_fapl_mpiposix_f h5fflush_c_ h5fget_access_plist_c_ h5fget_create_plist_c_ @@ -553,6 +559,7 @@ h5pget_data_transform_c_ h5pget_double_c_ h5pget_driver_c_ +h5pget_dxpl_mpio_c_ h5pget_edc_check_c_ h5pget_est_link_info_c_ h5pget_external_c_ @@ -560,6 +567,8 @@ h5pget_fapl_core_c_ h5pget_fapl_direct_c_ h5pget_fapl_family_c_ +h5pget_fapl_mpio_c_ +h5pget_fapl_mpiposix_c_ h5pget_fapl_multi_c_ h5pget_fclose_degree_c_ h5pget_fill_time_c_ @@ -758,6 +767,7 @@ h5pset_data_transform_c_ h5pset_deflate_c_ h5pset_double_c_ +h5pset_dxpl_mpio_c_ h5pset_edc_check_c_ h5pset_est_link_info_c_ h5pset_external_c_ @@ -765,6 +775,8 @@ h5pset_fapl_core_c_ h5pset_fapl_direct_c_ h5pset_fapl_family_c_ +h5pset_fapl_mpio_c_ +h5pset_fapl_mpiposix_c_ h5pset_fapl_multi_c_ h5pset_fapl_multi_sc_ h5pset_fapl_sec2_c_ diff -Nurd libhdf5-7/libhdf5.so.7 --- libhdf5-7/libhdf5.so.7 +++ libhdf5-openmpi-7/libhdf5.so.7 @@ -3,6 +3,7 @@ H5A_attr_iterate_table H5A_attr_post_copy_file H5A_attr_release_table +H5AC_add_candidate H5AC_close_trace_file H5AC_create H5AC_dest @@ -30,7 +31,13 @@ H5Acreate_by_name H5AC_reset_cache_hit_rate_stats H5AC_resize_entry +H5AC_rsp__dist_md_write__flush +H5AC_rsp__dist_md_write__flush_to_min_clean +H5AC_rsp__p0_only__flush +H5AC_rsp__p0_only__flush_to_min_clean H5AC_set_cache_auto_resize_config +H5AC_set_sync_point_done_callback +H5AC_set_write_done_callback H5AC_stats H5AC_term_interface H5AC_unpin_entry @@ -153,6 +160,9 @@ H5_buffer_dump H5_build_extpath H5B_valid +H5C_apply_candidate_list +H5C_construct_candidate_list__clean_cache +H5C_construct_candidate_list__min_clean H5C_create H5C_def_auto_resize_rpt_fcn H5C_dest @@ -174,6 +184,7 @@ H5check_version H5C_insert_entry H5close +H5C_mark_entries_as_clean H5C_mark_entry_dirty H5C_move_entry H5C_pin_protected_entry @@ -192,11 +203,14 @@ H5D_alloc_storage H5D_btree_debug H5D_check_filters +H5D_chunk_addrmap H5D_chunk_allocate H5D_chunk_allocated H5D_chunk_bh_info H5D_chunk_cacheable H5D_chunk_cinfo_cache_reset +H5D_chunk_collective_read +H5D_chunk_collective_write H5D_chunk_copy H5D_chunk_create H5D_chunk_delete @@ -216,6 +230,8 @@ H5D_compact_copy H5D_compact_fill H5D_contig_alloc +H5D_contig_collective_read +H5D_contig_collective_write H5D_contig_copy H5D_contig_delete H5D_contig_fill @@ -263,6 +279,9 @@ H5D_layout_set_io_ops H5D_layout_version_test H5D_mark +H5D_mpio_opt_possible +H5D_mpio_select_read +H5D_mpio_select_write H5D_nameof H5D_oloc H5dont_atexit @@ -304,7 +323,6 @@ H5E_get_msg H5Eget_msg H5Eget_num -H5E_get_stack H5E_init H5Epop H5E_pop @@ -385,6 +403,19 @@ H5FD_init H5FD_log_init H5FD_log_term +H5FD_mpi_comm_info_dup +H5FD_mpi_comm_info_free +H5FD_mpi_get_comm +H5FD_mpi_get_rank +H5FD_mpi_get_size +H5FD_mpi_haddr_to_MPIOff +H5FD_mpi_MPIOff_to_haddr +H5FD_mpio_init +H5FD_mpio_term +H5FD_mpiposix_init +H5FD_mpiposix_term +H5FD_mpi_setup_collective +H5FD_mpi_teardown_collective H5FD_multi_init
Bug#699161: iceweasel: Fonts pixelated after pressing back until redraw is forced
Package: iceweasel
Version: 18.0.1-1~bpo60+1
Severity: normal
On certain websites, for example: news.ycombinator.com whenever I press the
back button, then the fonts are afterward pixelated. Or maybe not anti-aliased
or smoothed.
The moment iceweasel does redraw the font smoothing is used again (for example
by clicking the website itself once).
To reproduce: Visit news.ycombinator.com then for example click on any
comments link. Then press the back button (you have to enable navigation
toolbar if you don't have it enabled). The main page should now be looking
pixelated.
-- Package-specific info:
-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled
Name: Add Bookmark Here ?
Location: ${PROFILE_EXTENSIONS}/abhe...@moztw.org.xpi
Status: enabled
Name: Bookmark All
Location: ${PROFILE_EXTENSIONS}/{a76cd07b-f0d7-4ef9-9566-8faef6e290e4}
Status: enabled
Name: British English Dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: enabled
Name: CheckPlaces
Location: ${PROFILE_EXTENSIONS}/checkpla...@andyhalford.com.xpi
Status: enabled
Name: Default theme
Location: /usr/lib/iceweasel/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: Download Statusbar
Location: ${PROFILE_EXTENSIONS}/{D4DD63FA-01E4-46a7-B6B1-EDAB7D6AD389}
Status: enabled
Name: FireFTP
Location: ${PROFILE_EXTENSIONS}/{a7c6cf7f-112c-4500-a7ea-39801a327e5f}.xpi
Status: enabled
Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled
Name: German Dictionary
Location: ${PROFILE_EXTENSIONS}/de...@dictionaries.addons.mozilla.org
Status: enabled
Name: HttpFox
Location: ${PROFILE_EXTENSIONS}/{4093c4de-454a-4329-8aff-c6b0b123c386}.xpi
Status: enabled
Name: Japanese Language Pack locale
Location: /usr/lib/iceweasel/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-ja
Status: enabled
Name: LeechBlock
Location: ${PROFILE_EXTENSIONS}/{a95d8332-e4b4-6e7f-98ac-20b733364387}.xpi
Status: enabled
Name: ProxTube - Unblock YouTube
Location: ${PROFILE_EXTENSIONS}/i...@maltegoetz.de
Status: enabled
Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: enabled
Name: UpdateBookmark
Location: ${PROFILE_EXTENSIONS}/updatebookm...@irian.de.xpi
Status: enabled
Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: enabled
Name: no_bookmark_star userstyle
Status: enabled
-- Plugins information
Name: DivX?? Web Player
Location: /usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Package: totem-mozilla
Status: enabled
Name: QuickTime Plug-in 7.6.6
Location: /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so
Package: totem-mozilla
Status: enabled
Name: Shockwave Flash
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled
Name: VLC Multimedia Plugin (compatible Totem 2.30.2)
Location: /usr/lib/mozilla/plugins/libtotem-cone-plugin.so
Package: totem-mozilla
Status: enabled
Name: Windows Media Player Plug-in 10 (compatible; Totem)
Location: /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so
Package: totem-mozilla
Status: enabled
Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: enabled
-- Addons package information
ii iceweasel 18.0.1-1~bpo60 Web browser based on Firefox
ii iceweasel-l10n 1:18.0.1-1~bpo Japanese language package for Iceweasel
ii rhythmbox-plug 0.12.8-3 plugins for rhythmbox music player
ii totem-mozilla 2.30.2-6 Totem Mozilla plugin
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages iceweasel depends on:
ii debianutils3.4 Miscellaneous utilities specific t
ii fontconfig 2.8.0-2.1 generic font configuration library
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface
ii libnspr4 2:4.9.3-1~bpo60+1 NetScape Portable Runtime Library
ii libnspr4-0d2:4.9.3-1~bpo60+1 NetScape Portable Runtime Library
ii libsqlite3-0 3.7.13-1~bpo60+1 SQLite 3 shared library
ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3
ii procps 1:3.2.8-9squeeze1 /proc file system utilities
ii xulrunner-18.0 18.0.1-1~bpo60+1 XUL + XPCOM application runner
iceweasel recommends no packages.
Versions of packages iceweasel suggests:
pn fonts-stix
Bug#699162: New upstream snapshot
Package: portmidi Severity: wishlist Hi Paul, a new upstream snapshot is available: http://qa.debian.org/watch/sf.php/portmedia/portmidi-src-217.zip Would you mind to update the packaging? As it's a couple of years circa you don't touch the package, what do you think about bringing it into team maintenance? Hope to hear from you soon, and cheers! -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699152: notmuch-mutt: Please document the fact that extra terms can be passed by the macro
Martin Quinson martin.quin...@loria.fr writes: +macro index F7 \ + enter-commandunset wait_keyentershell-escapenotmuch-mutt --prompt search $(date +%s --date='last month')..$(date +%s) enterchange-folder-readonly~/.cache/notmuch/mutt/resultsenter \ + notmuch: search mail (last month) Hi Martin; Thanks for the patch! As it turns out, from notmuch 0.15 (currently in experimental because of the freeze) there is actually built in date parsing in notmuch. I'm not sure if this simplifies this search with notmuch-mutt or not. d -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699161: iceweasel: Fonts pixelated after pressing back until redraw is forced
tag 699161 unreproducible thanks On Mon, Jan 28, 2013 at 12:31:39PM +0100, Michael Zeilfelder wrote: Package: iceweasel Version: 18.0.1-1~bpo60+1 Severity: normal On certain websites, for example: news.ycombinator.com whenever I press the back button, then the fonts are afterward pixelated. Or maybe not anti-aliased or smoothed. The moment iceweasel does redraw the font smoothing is used again (for example by clicking the website itself once). To reproduce: Visit news.ycombinator.com then for example click on any comments link. Then press the back button (you have to enable navigation toolbar if you don't have it enabled). The main page should now be looking pixelated. Can you attach screenshots, I can't reproduce. Have you also tried disabling all addons and plugins? Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699163: O: bup -- highly efficient file backup system based on git
Package: wnpp Severity: normal signature.asc Description: Digital signature
Bug#699164: tftpd-hpa: inetd configuration via debconf
Package: tftpd-hpa Version: 5.2-5 Severity: wishlist Hello. What do you think about to add configuration option to choose how to run tftpd-hpa, standalone or via inetd. Like proftpd for exmaple. -- sergio. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696068: Please add a note about slapd
On Sun, Jan 27, 2013 at 12:33:49PM +0100, Wouter Verhelst wrote: On Sun, Jan 27, 2013 at 11:57:05AM +0100, Joost van Baal-Ilić wrote: Just did some investigating of this issue. In squeeze (stable) we have OpenLDAP server (slapd) 2.4.23-7.2, while wheezy (testing) has 2.4.31-1. That one is from Steve Langasek vorlon Wed, 27 Jun 2012 03:27:34 +; it contains no fix for #665199. The upload was 2.4.23-7.3, targetted for stable. It's been accepted, but won't be visible until the next point release. OK, thanks; I'll get to it. Bye, Joost -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs
On Mon, Jan 28, 2013 at 12:26:18PM +0100, Julien Cristau wrote: On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote: On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote: do you have pointers/details about that ABI incompatibility? I'm pretty sure I looked through exported symbols and headers from hdf5 a year ago, and didn't see anything that would break when building against the serial version and running against openmpi, but I may have missed something. I didn't check further than the attached diff, there are mostly symbols being added in the openMPI version but also some symbols dissapearing. OK. So you didn't get any runtime issues with this? I haven't tried :) I only checked the symbols diff quickly as said. If you're fully sure we won't run in any runtime problems, then why hdf5 doesn't use the same scheme than in Squeeze? The problem with the upgrades still stands. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699038: grub-efi-amd64-bin: Transition grub-pc - grub-efi fails due to missing FS driver module
On Sat, Jan 26, 2013 at 05:56:02PM +0100, Jens G wrote: I recently moved from grub-pc/GPT to grub-efi/GPT (dual boot with Win 8). After successfully installing Grub to the ESP and getting the UEFI to run grubx64.efi Grub (after welcomming me) complained: | error: invalid arch independent ELF magic. | grub rescue This probably means that it's trying to load modules from /boot/grub/ and they're actually for grub-pc rather than grub-efi-amd64. What is $prefix set to? (You can inspect it in the rescue shell using 'set'.) This happend when running grubx64.efi from an EFI-shell (v1) and with the normal UEFI boot sequence. However, when I used the previously installed rEFInd boot manager to launch grubx64.efi, Grub worked just fine. That's a little mysterious. AFAIK rEFInd contains some file system drivers. So I installed Grub under a second label and added | --modules=part_gpt ext2 to the grub-install invocation. This produced a different grubx64.efi but with the same size as the first one. I doubt this was necessary. grub-install autodetects the necessary modules already, and this is confirmed by the fact that your core image was the same size both times round. GRUB does not know about or use rEFInd's file system drivers. Accidently running the FIRST grubx64.efi, it now worked using either UEFI boot or EFI-shell! grub-install copies modules into /boot/grub/, which probably explains the change in behaviour. Perhaps you constructed the first grubx64.efi using some mechanism other than grub-install, or perhaps grub-pc is still installed and some bit of packaging called grub-install for the BIOS platform without you noticing? Does grub-efi use the GPT boot partition similar to grub-pc? If so, did grub-install add the ext2.mod there so that both Grub instances can now access the remaining modules on the (separate) ext3 /boot partition? grub-pc and grub-efi-amd64 both use /boot/grub/. (In GRUB 2.00 this is clarified by moving the modules to /boot/grub/i386-pc/ and /boot/grub/x86_64-efi/ respectively; but in 1.99 they shared a single /boot/grub/ directory.) The GRUB core image (which typically resides in the BIOS Boot Partition with grub-pc on GPT, or in the EFI System Partition with grub-efi-amd64) is required to contain all the modules that are necessary to access /boot/grub/, much as a Linux kernel + initramfs are together required to contain all modules necessary to access /. Once the core image has started up to roughly the point where it could execute a rescue shell, it does not normally access the BIOS Boot Partition / EFI System Partition any further. Just for reference, what is your partition layout (e.g. 'parted -l')? If more information is needed I'll try to help but I tried an awful lot of things to get the UEFI/Win8/GPT/Linux/Grub thingy working, may not remember /all/ of it and am loth to do anything disruptive at this point. The evidence suggests that, on your first attempt, the GRUB core image and the modules it found were built for different platforms, but that your second attempt installed the correct set of modules. Unfortunately, if you didn't take detailed notes, we may not be able to progress this bug any further because it's pretty hard to guess at what point things went wrong. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699066: xgks: Contains code preventing commercial distribution
Ok, I am contacting the original author of this code, to see if he is willing to make a change. The code was written in 1990 or so, and he may not have been aware of the consequences of his actions. Annoying that the Small print appeared so far down in the file and was missed during the original licensing checks. I will investigate if ferret-vis can be built without this, just in case. regards Alastair (Maintainer of xgks and ferret). On 2013-01-27 11:50, Francesco Poli wrote: On Sat, 26 Jan 2013 19:31:33 -0500 Luke Faraone wrote: [...] src/port/misc/config.c: [...] and cause the whole of any work that you distribute or publish, that in whole or in part contains or is a derivative of this program or any part thereof, to be licensed at no charge to all third parties on terms identical to those here. [...] The text to be licensed at no charge sounds like it forbids commercial distribution. Mmmmh, I am not too convinced. It says licensed at no charge, not distributed at no charge. Please compare with clause 2b of the GNU GPL v2: | b) You must cause any work that you distribute or publish, that in | whole or in part contains or is derived from the Program or any | part thereof, to be licensed as a whole at no charge to all third | parties under the terms of this License. It seems to be pretty equivalent... The license of src/port/misc/config.c looks like a not-too-strong copyleft (GPL-incompatible) license. I haven't spotted any DFSG-freeness issues. As far as the other additional violations (pointed out in message #10 [1]) are concerned, I have nothing to comment... [1] http://bugs.debian.org/699066#10 N.B.: I am not a maintainer of this package and I know nothing about it; I am just a debian-legal regular who happened to notice this RC bug... I hope my comment helps a little. -- Alastair McKinstry , alast...@sceal.ie , mckins...@debian.org http://blog.sceal.ie Anyone who believes exponential growth can go on forever in a finite world is either a madman or an economist - Kenneth Boulter, Economist. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699165: rsync: debian/rules using ` instead of $(shell
Package: rsync Version: 3.0.9-4 Severity: serious Tags: patch Justification: fails to build from source On squeeze, I failed to compile rsync/unstable from source: dpkg-source -x rsync_3.0.9-4.dsc cd rsync-3.0.9 dpkg-buildpackage -rfakeroot -b [...] errors related to compiler not found.. but after a look at config.log it was because not expanding `dpkg-buildflags --get CFLAGS`. I traced that back to debian/rules, where for CFLAGS/LDFLAGS: CFLAGS += `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` while for CPPFLAGS: CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) The following patch for debian/rules solved the issue: -CFLAGS += `dpkg-buildflags --get CFLAGS` -LDFLAGS = `dpkg-buildflags --get LDFLAGS` +CFLAGS += $(shell dpkg-buildflags --get CFLAGS) +LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS) Cheers, StalkR -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (800, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rsync depends on: ii base-files 6.0squeeze6 Debian base system miscellaneous f ii libacl1 2.2.49-4 Access control list shared library ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libpopt01.16-1 lib for parsing cmdline parameters ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip Other: ii gcc 4:4.4.5-1The GNU C compiler ii gcc-4.4 4.4.5-8 The GNU C compiler ii gcc-4.4-base4.4.5-8 The GNU Compiler Colle -- 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#521426: mobiperl: unofficial packages of version 0.0.43
Hi folks, Based on the work Eugenio Cutolo e.cut...@gmail.com did for Ubuntu in 2008 I just buildt unofficial packages of mobiperl 0.0.43 for wheezy/testing. Maybe they are usefull for others. You can find them at: http://apt.klaumikli.de/testing The packages work, but to get them into official Debian there remains a lot to do: * debian/rules: has be be rewritten totally to make use of dh_make * convert the upstream html-man pages in real manpages * add all binaries to the menu-file * fix upstream makefile So it's only the first step of a long and winding road ;-) Klaumi --- Klaus-Michael Klingsporn mail: klaumi...@gmx.de web: www.klaumikli.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698802: release-notes: NSCA compatibility problems should be described
On Mon, Jan 28, 2013 at 01:10:19AM +0100, Hilko Bengen wrote: * Julien Cristau: On Sun, Jan 27, 2013 at 19:19:48 +0100, Hilko Bengen wrote: I agree. Feel free to use the text I provided. Well I'm not the maintainer for those packages. You should talk to them about that, I think. Right. Would a package update that adds a NEWS.Debian file be accepted into wheezy at this point? I'd guess yess: documentation fixes are ok for freeze exception Bye, Joost -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699166: unblock: accessodf/0.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock the package accessodf.
The application to be unblocked is a Libreoffice extension. Currently it is
installed using unopkg, the Libreoffice extension manager. Using unopkg
directly has bad side effects, see bug #679717, it leaves files behind after
purge.
The new version extract the files from the OXT-file (a zip file containing the
extension) to /usr/lib/libreoffice/share/extensions. The old version installs
the package with maintainer scripts, the new is therefore easier and more
fault-tolerant.
Just the rules and the install-file needs to be changed.
Since now the files are directly in /usr/lib, two files have to be added for the
package to be Lintian-clean:
* First a links-file, since the jar of the extension is moved to
/usr/share/accessodf.
* An override-file, since there are some thumbnails in the extension which the
application expects there but are in /usr/lib/.../extensions/accessodf.
Here is the debdiff output:
===
diff -Nru accessodf-0.1/debian/accessodf.lintian-overrides
accessodf-0.1/debian/accessodf.lintian-overrides
--- accessodf-0.1/debian/accessodf.lintian-overrides1970-01-01
01:00:00.0 +0100
+++ accessodf-0.1/debian/accessodf.lintian-overrides2013-01-23
17:25:54.0 +0100
@@ -0,0 +1 @@
+accessodf binary: image-file-in-usr-lib
diff -Nru accessodf-0.1/debian/changelog accessodf-0.1/debian/changelog
--- accessodf-0.1/debian/changelog 2012-11-02 12:33:21.0 +0100
+++ accessodf-0.1/debian/changelog 2013-01-23 17:25:54.0 +0100
@@ -1,8 +1,16 @@
+accessodf (0.1-2) unstable; urgency=low
+
+ * {pre,post}{inst|rm}: removed. The cleaner (now working) solution is to
+just unzip the package. This method won't leave unowned files behind.
+(Closes: #679717)
+
+ -- Sebastian Humenda shume...@gmx.de Mon, 21 Jan 2013 19:01:52 +0200
+
accessodf (0.1-1.3) unstable; urgency=low
* Non-maintainer upload.
* oops, forgot a unopkg in preinst, thanks Andreas Beckmann
-(closes: #679717)
+(closes: #679717)
-- Rene Engelhard r...@rene-engelhard.de Fri, 02 Nov 2012 12:32:50 +0100
diff -Nru accessodf-0.1/debian/control accessodf-0.1/debian/control
--- accessodf-0.1/debian/control2012-06-30 05:23:20.0 +0200
+++ accessodf-0.1/debian/control2013-01-23 17:25:54.0 +0100
@@ -4,7 +4,7 @@
Maintainer: Sebastian Humenda shume...@gmx.de
Build-Depends: debhelper (= 7.0.50~), ant (= 1.8~), ant-optional,
default-jdk, openjdk-6-jre-headless | openjdk-7-jre-headless,
- libcommons-collections3-java, libreoffice-java-common (= 1:3.5.0~)
+ libcommons-collections3-java, libreoffice-java-common (= 1:3.5.0~),
unzip
Standards-Version: 3.9.2
Homepage: http://sourceforge.net/p/accessodf
diff -Nru accessodf-0.1/debian/install accessodf-0.1/debian/install
--- accessodf-0.1/debian/install2012-04-10 00:36:53.0 +0200
+++ accessodf-0.1/debian/install2013-01-26 19:18:03.0 +0100
@@ -1,2 +1,3 @@
-dist/AccessODF.oxt usr/share/accessodf
dist/lib/accessodf.jar usr/share/java
+debian/tmp/usr/lib/libreoffice/share/extensions/accessodf/*
+debian/tmp/usr/share/accessodf/*
diff -Nru accessodf-0.1/debian/links accessodf-0.1/debian/links
--- accessodf-0.1/debian/links 1970-01-01 01:00:00.0 +0100
+++ accessodf-0.1/debian/links 2013-01-26 19:08:18.0 +0100
@@ -0,0 +1 @@
+/usr/share/accessodf/accessodf-addon.jar
/usr/lib/libreoffice/share/extensions/accessodf/accessodf-addon.jar
diff -Nru accessodf-0.1/debian/postinst accessodf-0.1/debian/postinst
--- accessodf-0.1/debian/postinst 2012-10-23 19:53:33.0 +0200
+++ accessodf-0.1/debian/postinst 1970-01-01 01:00:00.0 +0100
@@ -1,25 +0,0 @@
-#!/bin/sh
-# This maintainer script was originally written by Harri Pitkänen, Teemu
Likonen
-# and Timo Jyrinki and was adopted from the openoffice.org-voikko package. It
-# was modified by Sebastian Humenda to fit for the AccessODF package.
-
-PATH=/bin:/usr/bin
-
-set -e
-
-add_extension() {
-echo -n Adding extension $1...
-INSTDIR=`mktemp -d`
-HOME=$INSTDIR unopkg add --shared $1 \
--env:UserInstallation=file:///$INSTDIR \
-
'-env:UNO_JAVA_JFW_INSTALL_DATA=$ORIGIN/../share/config/javasettingsunopkginstall.xml'
\
--env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1
-if [ -n $INSTDIR ]; then rm -rf $INSTDIR; fi
-echo done.
-}
-
-if [ $1 = configure -o $1 = upgrade ]; then
-add_extension /usr/share/accessodf/AccessODF.oxt
-fi
-
-#DEBHELPER#
diff -Nru accessodf-0.1/debian/preinst accessodf-0.1/debian/preinst
--- accessodf-0.1/debian/preinst2012-11-02 12:32:32.0 +0100
+++ accessodf-0.1/debian/preinst1970-01-01 01:00:00.0 +0100
@@ -1,41 +0,0 @@
-#!/bin/sh
-# This maintainer script was originally written by Harri Pitkänen, Teemu
Likonen
-# and Timo Jyrinki and
Bug#692358: Review php5-midgard2 package
Also, you should include the debdiff between both versions in this bug
report.
Attached dsc files diff.
Piotras
diff -Nru php5-midgard2-10.05.6/debian/changelog php5-midgard2-10.05.7/debian/changelog
--- php5-midgard2-10.05.6/debian/changelog 2012-03-09 07:56:53.0 +0100
+++ php5-midgard2-10.05.7/debian/changelog 2012-06-16 00:06:45.0 +0200
@@ -1,6 +1,13 @@
+php5-midgard2 (10.05.7-1) unstable; urgency=low
+
+ * New upstream
+ * Use php5en(dis)mod in prerm and postinst. Closes: #667785
+
+ -- Piotr Pokora piotrek.pok...@gmail.com Wed, 13 Jun 2012 21:34:29 +0200
+
php5-midgard2 (10.05.6-1) unstable; urgency=low
- * New upstream. Closes: #656484
+ * New upstream. Closes #656484
-- Piotr Pokora piotrek.pok...@gmail.com Tue, 06 Mar 2012 20:00:22 +0100
diff -Nru php5-midgard2-10.05.6/debian/control php5-midgard2-10.05.7/debian/control
--- php5-midgard2-10.05.6/debian/control 2012-03-06 20:04:12.0 +0100
+++ php5-midgard2-10.05.7/debian/control 2012-06-16 00:06:45.0 +0200
@@ -5,11 +5,11 @@
Uploaders:
Standards-Version: 3.9.3
Homepage: http://www.midgard-project.org
-Build-Depends: debhelper (=7.0), php5-dev, libmidgard2-dev(=10.05.6)
+Build-Depends: debhelper (=7.0), php5-dev, libmidgard2-dev(=10.05.7)
Package: php5-midgard2
Architecture: any
-Depends: php5-cli (=5.2.0) | php5-cgi (=5.2.0), midgard2-common (=10.05.6), ucf, ${shlibs:Depends}, ${misc:Depends}, ${php:Depends}
+Depends: php5-cli (=5.2.0) | php5-cgi (=5.2.0), midgard2-common (=10.05.7), ucf, ${shlibs:Depends}, ${misc:Depends}, ${php:Depends}
Suggests: libapache2-mod-php5 (=5.2.0) | lighttpd | nginx, php5-memcache
Replaces:
Conflicts:
diff -Nru php5-midgard2-10.05.6/debian/php5-midgard2.postinst php5-midgard2-10.05.7/debian/php5-midgard2.postinst
--- php5-midgard2-10.05.6/debian/php5-midgard2.postinst 2012-03-06 20:00:11.0 +0100
+++ php5-midgard2-10.05.7/debian/php5-midgard2.postinst 2012-06-16 00:06:45.0 +0200
@@ -1,11 +1,16 @@
#!/bin/sh
+set -e
-#DEBHELPER#
+[ -x /usr/bin/dpkg-maintscript-helper ] \
+ dpkg-maintscript-helper rm_conffile /etc/php5/conf.d/midgard2.ini 10.05.6~ -- $@
-set -e
+#DEBHELPER#
if test $1 = configure; then
- ucf /usr/share/doc/php5-midgard2/midgard2.ini /etc/php5/conf.d/midgard2.ini
+ ucf /usr/share/doc/php5-midgard2/midgard2.ini /etc/php5/mods-available/midgard2.ini
+ php5enmod midgard2
fi
+#DEBHELPER#
+
exit 0
diff -Nru php5-midgard2-10.05.6/debian/php5-midgard2.postrm php5-midgard2-10.05.7/debian/php5-midgard2.postrm
--- php5-midgard2-10.05.6/debian/php5-midgard2.postrm 2012-03-06 20:00:11.0 +0100
+++ php5-midgard2-10.05.7/debian/php5-midgard2.postrm 2012-06-16 00:06:45.0 +0200
@@ -1,14 +1,20 @@
#!/bin/sh
-
set -e
+[ -x /usr/bin/dpkg-maintscript-helper ] \
+ dpkg-maintscript-helper rm_conffile /etc/php5/conf.d/midgard2.ini 10.05.6~ -- $@
+
#DEBHELPER#
if test $1 = purge; then
if which ucf /dev/null 21; then
- ucf --purge /etc/php5/conf.d/midgard2.ini
+ ucf --purge /etc/php5/mods-available/midgard2.ini
fi
- rm -f /etc/php5/conf.d/midgard2.ini
+ rm -f /etc/php5/mods-available/midgard2.ini
+fi
+
+if test $1 = remove; then
+ php5dismod midgard2
fi
exit 0
diff -Nru php5-midgard2-10.05.6/docs/midgard_documentor.php php5-midgard2-10.05.7/docs/midgard_documentor.php
--- php5-midgard2-10.05.6/docs/midgard_documentor.php 2012-03-06 12:08:19.0 +0100
+++ php5-midgard2-10.05.7/docs/midgard_documentor.php 2012-03-14 11:46:56.0 +0100
@@ -113,6 +113,44 @@
return $classes;
}
+public static function get_midgard_abstract_classes()
+{
+$classes = array();
+
+$all_classes = self::get_classes();
+
+if (empty($all_classes))
+return $classes;
+
+foreach ($all_classes as $refclass)
+{
+if ($refclass-isAbstract() === false) {
+continue;
+}
+$classes[] = $refclass;
+}
+return $classes;
+}
+
+public static function get_midgard_interfaces()
+{
+$classes = array();
+
+$all_classes = self::get_classes();
+
+if (empty($all_classes))
+return $classes;
+
+foreach ($all_classes as $refclass)
+{
+if ($refclass-isInterface() === false) {
+continue;
+}
+$classes[] = $refclass;
+}
+return $classes;
+}
+
public function create_footer()
{
@@ -133,6 +171,22 @@
{
$this-add_to_index($refclass);
}
+
+$this-index_buffer .= h2 Abstract classes /h2;
+$midgard_abstract_classes = self::get_midgard_abstract_classes();
+
+foreach ($midgard_abstract_classes as $refclass)
+{
+$this-add_to_index($refclass);
+}
+
+$this-index_buffer .= h2 Interfaces /h2;
+$midgard_interfaces =
Bug#699165: rsync: debian/rules using ` instead of $(shell
Hi Paul, Thanks for the quick reply. Strange then something must be wrong with my config. $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 May 14 2010 /bin/sh - bash* $ dpkg -l bash ii bash 4.1-3 The GNU Bourne Again SHell Attached dpkg-buildpackage stdout log and debian/buildtree/config.log Thanks for your help, StalkR On Mon, Jan 28, 2013 at 1:19 PM, Paul Slootman p...@debian.org wrote: On Mon 28 Jan 2013, StalkR wrote: On squeeze, I failed to compile rsync/unstable from source: dpkg-source -x rsync_3.0.9-4.dsc cd rsync-3.0.9 dpkg-buildpackage -rfakeroot -b [...] errors related to compiler not found.. but after a look at config.log it was because not expanding `dpkg-buildflags --get CFLAGS`. I traced that back to debian/rules, where for CFLAGS/LDFLAGS: CFLAGS += `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` while for CPPFLAGS: CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) Can you send the complete buildlog? I have no problem whatsoever with building on squeeze. What is your default /bin/sh ? Paul config.log Description: Binary data dpkg-buildpackage.log Description: Binary data
Bug#699165: rsync: debian/rules using ` instead of $(shell
You can ignore the DEBUG lines in config.log, it was me trying to trace the problem by editing configure.sh. The issue happened here: configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get CFLAGS` -g -O2 conftest.c 5 x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory x86_64-linux-gnu-gcc: CFLAGS`: No such file or directory cc1: error: unrecognized command line option -fget On Mon, Jan 28, 2013 at 1:26 PM, StalkR sta...@stalkr.net wrote: Hi Paul, Thanks for the quick reply. Strange then something must be wrong with my config. $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 May 14 2010 /bin/sh - bash* $ dpkg -l bash ii bash 4.1-3 The GNU Bourne Again SHell Attached dpkg-buildpackage stdout log and debian/buildtree/config.log Thanks for your help, StalkR On Mon, Jan 28, 2013 at 1:19 PM, Paul Slootman p...@debian.org wrote: On Mon 28 Jan 2013, StalkR wrote: On squeeze, I failed to compile rsync/unstable from source: dpkg-source -x rsync_3.0.9-4.dsc cd rsync-3.0.9 dpkg-buildpackage -rfakeroot -b [...] errors related to compiler not found.. but after a look at config.log it was because not expanding `dpkg-buildflags --get CFLAGS`. I traced that back to debian/rules, where for CFLAGS/LDFLAGS: CFLAGS += `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` while for CPPFLAGS: CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) Can you send the complete buildlog? I have no problem whatsoever with building on squeeze. What is your default /bin/sh ? Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699165: rsync: debian/rules using ` instead of $(shell
On Mon 28 Jan 2013, StalkR wrote: On squeeze, I failed to compile rsync/unstable from source: dpkg-source -x rsync_3.0.9-4.dsc cd rsync-3.0.9 dpkg-buildpackage -rfakeroot -b [...] errors related to compiler not found.. but after a look at config.log it was because not expanding `dpkg-buildflags --get CFLAGS`. I traced that back to debian/rules, where for CFLAGS/LDFLAGS: CFLAGS += `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` while for CPPFLAGS: CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) Can you send the complete buildlog? I have no problem whatsoever with building on squeeze. What is your default /bin/sh ? Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696650: [PATCH v3] md: protect against crash upon fsync on ro array
On 28.01.2013 11:32, Sebastian Riemer wrote:
O.K., then I hope Neil applies the attached patch. I've changed the
return value to success.
This is also something for linux-stable and should apply to many kernel
versions without an issue.
I've tried to race with continuous fsyncs against continuous mdadm -o
/dev/md0; mdadm -w /dev/md0; in parallel but couldn't break it.
Therefore, no additional locking is required and this part can be put
directly before the RCU locking stuff and the suspended handling.
I've attached version 3 of the patch.
From fe0357344877c9b9cc623fd582a4e0670e448317 Mon Sep 17 00:00:00 2001
From: Sebastian Riemer sebastian.rie...@profitbricks.com
Date: Fri, 25 Jan 2013 12:46:59 +0100
Subject: [PATCH v3] md: protect against crash upon fsync on ro array
If an fsync occurrs on a read-only array, we need to send a
completion for the IO and may not increment the active IO count.
Otherwise, we hit a bug trace and can't stop the MD array anymore.
By advice of Christoph Hellwig we silently return success.
Cc: Christoph Hellwig h...@infradead.org
Cc: Ben Hutchings b...@decadent.org.uk
Cc: NeilBrown ne...@suse.de
Signed-off-by: Sebastian Riemer sebastian.rie...@profitbricks.com
Reported-by: Ben Hutchings b...@decadent.org.uk
---
drivers/md/md.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 3db3d1b..6ba20f7 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -307,6 +307,10 @@ static void md_make_request(struct request_queue *q,
struct bio *bio)
bio_io_error(bio);
return;
}
+ if (mddev-ro == 1 unlikely(rw == WRITE)) {
+ bio_endio(bio, 0);
+ return;
+ }
smp_rmb(); /* Ensure implications of 'active' are visible */
rcu_read_lock();
if (mddev-suspended) {
Bug#699165: rsync: debian/rules using ` instead of $(shell
Control: severity -1 normal On 28.01.2013 12:29, StalkR wrote: You can ignore the DEBUG lines in config.log, it was me trying to trace the problem by editing configure.sh. The issue happened here: configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get CFLAGS` -g -O2 conftest.c 5 x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory This means you don't have a sufficiently new version of dpkg-dev installed which supports dpkg-buildflags. Whilst rsync's build-dependencies should ideally reflect this via a versioned dependency relation, failure of a package from testing / unstable to build on a stable system is not release critical; I'm therefore downgrading the bug. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698802: release-notes: NSCA compatibility problems should be described
clone 698802 -1 reassign -1 nsca retitle -1 Please add NEWS.Debian documenting various nsca 2.7 vs. 2.9 incompatibilities tags -1 +patch thank you * Joost van Baal-Ilić: On Mon, Jan 28, 2013 at 01:10:19AM +0100, Hilko Bengen wrote: * Julien Cristau: On Sun, Jan 27, 2013 at 19:19:48 +0100, Hilko Bengen wrote: I agree. Feel free to use the text I provided. Well I'm not the maintainer for those packages. You should talk to them about that, I think. Right. Would a package update that adds a NEWS.Debian file be accepted into wheezy at this point? I'd guess yess: documentation fixes are ok for freeze exception Okay, so I am cloning this bug. I think that the paragraphs I submitted for the release notes can be pretty much used as-is, thus the patch tag. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699150: RFS: begin/0.1.1-1 (ITP #699113)
Hi all, Thanks for the input on this. Timo: I have fixed that issue now along with (almost) all other warnings from lintian. Stuart: I appreciate your input, and if this is the consensus of the Debian Community I will of course abide by it. However I have a few arguments for my case :) 1. There are always a lot of ways to do stuff in the *nix world. I this case you could use egrep, awk or I am sure some other tool as well. However I think those ways of doing it is more complex and not as easily accesible as with begin. I have writen a program that does one thing (and I think that it does it well) because I had a need for it. I work a lot with config-files in my day to day work and I always find it easier to find stuff in the config when I am on a cisco-box then when I am on the servers. I had an itch so I scratched it and I figured someone else might have that itch too. 2. The name is taken from the cisco command that I have have reimplemented. I think it is a good name as it describes the function of the program and it is well known for those who do work on network equipment. That being said, I wouldn't mind changing the name of the package/binary to something else, say mbegin or something if the consensus is that the name is an issue. I am more interested in the function than the name. I might well look into joining a team no matter what happens to this package. I think it would be fun to be more involved in my favorite distro (which is why I started packing this utilty for Debian). Best regards, Micke 2013/1/28 Stuart Prescott stu...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mikael, As I mentioned in #debian-mentors yesterday, I find it difficult to justify a Debian package for a tool that could be replaced by existing tools like awk /foo/,EOF much less a package and binary name that are so generic. We try to avoid generic program names in the $PATH namespace (like node, for instance...). I realise that you've done a lot of work learning how to package this and you'd like to see your work included in Debian. Perhaps I could encourage you to contribute to existing packaging teams where you can see packages already in (hopefully) good shape from which you can learn. Working within a team can also help you be more productive in a shorter time. If you're not sure where to look for teams that want help, the rc-alert or wnpp-alert commands can give you a list of packages and bugs that pertain to what is installed on your system. cheers Stuart - -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEGVuEACgkQn+i4zXHF0ai/DwCgrciD5+w5PFr4hQaiNEBOc5+j GpYAn2gyx+OEd5jCdVQnRMcNVBqW5EcM =oozT -END PGP SIGNATURE-
Bug#699165: rsync: debian/rules using ` instead of $(shell
Wierd, your build log shows different lines for the patch output than my build log: applying misc Debian patches for i in debian/patches/*.patch debian/patches/*.diff; do if [ -s $i ]; then echo $i ...; cat $i | (cd debian/buildtree; patch -p1) || exit 1; fi; done debian/patches/cast--1-size_t.diff ... patching file flist.c -Hunk #1 succeeded at 726 (offset 37 lines). +Hunk #1 succeeded at 684 (offset -5 lines). patching file io.c Hunk #1 succeeded at 483 (offset -28 lines). Hunk #2 succeeded at 1068 (offset -25 lines). @@ -43,12 +36,11 @@ Hunk #1 succeeded at 882 (offset 31 lines). debian/patches/delete-delay.diff ... patching file flist.c -Hunk #1 succeeded at 1838 (offset 47 lines). +Hunk #1 succeeded at 1796 (offset 5 lines). debian/patches/logdir.diff ... patching file support/rsyncstats debian/patches/manpages.GPL.diff ... patching file rsync.1 -Hunk #1 succeeded at 3564 (offset 17 lines). patching file rsyncd.conf.5 debian/patches/partial-timestamp.diff ... patching file cleanup.c @@ -60,7 +52,7 @@ Hunk #1 succeeded at 323 (offset 2 lines). Hunk #2 succeeded at 331 (offset 2 lines). patching file options.c -Hunk #1 succeeded at 1546 (offset 14 lines). +Hunk #1 succeeded at 1543 (offset 11 lines). patching file progress.c debian/patches/rsyncd.conf.5.comment.diff ... patching file rsyncd.conf.5 This might suggest that your sources are not in fact the original ones?! $ md5sum rsync_3.0.9-4.diff.gz rsync_3.0.9-4.dsc rsync_3.0.9.orig.tar.gz b14387d385cd0e74b06867b9512a9dfe rsync_3.0.9-4.diff.gz 23411adc42b0a6e901f4e8497f8d7b71 rsync_3.0.9-4.dsc 5ee72266fe2c1822333c407e1761b92b rsync_3.0.9.orig.tar.gz Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699165: rsync: debian/rules using ` instead of $(shell
Ok, thanks Adam, noted. Paul, yes sorry for the confusion, after that I was trying upstream's patches/detect-renamed.diff. I confirm I have the same sources and same output as you without this patch. On Mon, Jan 28, 2013 at 1:47 PM, Paul Slootman p...@debian.org wrote: Wierd, your build log shows different lines for the patch output than my build log: applying misc Debian patches for i in debian/patches/*.patch debian/patches/*.diff; do if [ -s $i ]; then echo $i ...; cat $i | (cd debian/buildtree; patch -p1) || exit 1; fi; done debian/patches/cast--1-size_t.diff ... patching file flist.c -Hunk #1 succeeded at 726 (offset 37 lines). +Hunk #1 succeeded at 684 (offset -5 lines). patching file io.c Hunk #1 succeeded at 483 (offset -28 lines). Hunk #2 succeeded at 1068 (offset -25 lines). @@ -43,12 +36,11 @@ Hunk #1 succeeded at 882 (offset 31 lines). debian/patches/delete-delay.diff ... patching file flist.c -Hunk #1 succeeded at 1838 (offset 47 lines). +Hunk #1 succeeded at 1796 (offset 5 lines). debian/patches/logdir.diff ... patching file support/rsyncstats debian/patches/manpages.GPL.diff ... patching file rsync.1 -Hunk #1 succeeded at 3564 (offset 17 lines). patching file rsyncd.conf.5 debian/patches/partial-timestamp.diff ... patching file cleanup.c @@ -60,7 +52,7 @@ Hunk #1 succeeded at 323 (offset 2 lines). Hunk #2 succeeded at 331 (offset 2 lines). patching file options.c -Hunk #1 succeeded at 1546 (offset 14 lines). +Hunk #1 succeeded at 1543 (offset 11 lines). patching file progress.c debian/patches/rsyncd.conf.5.comment.diff ... patching file rsyncd.conf.5 This might suggest that your sources are not in fact the original ones?! $ md5sum rsync_3.0.9-4.diff.gz rsync_3.0.9-4.dsc rsync_3.0.9.orig.tar.gz b14387d385cd0e74b06867b9512a9dfe rsync_3.0.9-4.diff.gz 23411adc42b0a6e901f4e8497f8d7b71 rsync_3.0.9-4.dsc 5ee72266fe2c1822333c407e1761b92b rsync_3.0.9.orig.tar.gz Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699168: maint-guide: debhelper v9 is the recommended mode
Package: maint-guide Version: 1.2.31 Severity: important This was completely my oversight... On Sun, Jan 27, 2013 at 05:40:31PM +0100, Maykel Moya wrote: El 27/01/13 15:03, Osamu Aoki escribió: ... Well, I'm packaging this[1]. Last time I uploaded it to mentors, in QA information I got a notice that compat-level was outdated (I was using 7 while current is 9). debhelper was 7 when squeeze freeze was going on. This came from those days :-) Yep, someone should have bugged me for wheezy. You are the first! This is worth to record in BTS. Maint-guide specify to set compat-level to 7[2]. It's understandable that 7 is the current level at the time of writing and it makes no sense was to update maint-guide in sync with debhelper major version updates. Yes, you are absolutely right. Given that, I suggest to add to maint-guide a statement saying that canonical source of 'last compat-level' is the manpage of current debhelper in sid (or the dist you're targeting in case of backports of stable updates). Something like: 'Currently, you should set it to the debhelper v7 as follows:' '$ echo 7 debian/compat' 'Note that debhelper is a moving target. The last compat-level is blah blah blah...' (sorry, I'm not a native english speaker but I think you can get the idea) Well ... you are more qualified than me ... I am a Japanese speaker. I'd even add the info that compat-level is actually the debhelper major version, with a link to http://packages.debian.org/sid/debhelper so people don't have to bother looking for the 'compat level' thing in the manpage. I propose to fix this in 2 steps. Step 1 possibly for wheezy:s/7/9/g (including translations) Step 2 for post-wheezy: add reminder to check the current recommended debhelper version in debhelper(8) manpage. Osamu Kind regards, maykel Mucho gracias. [1] https://mentors.debian.net/package/pyxs [2] http://www.debian.org/doc/manuals/maint-guide/dother.en.html#compat Osamu -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-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 maint-guide depends on no packages. maint-guide recommends no packages. Versions of packages maint-guide suggests: ii debian-policy 3.9.4.0 ii developers-reference 3.4.9 ii devscripts2.12.6 ii dh-make 0.61 ii doc-base 0.10.4 ii dput 0.9.6.3+nmu1 ii fakeroot 1.18.4-2 ii lintian 2.5.10.3 ii pbuilder 0.213 ii quilt 0.60-7 -- 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#687442: My testresult so far
self-compiled version of http://people.debian.org/~jcristau/wheezy-drm34/ with headers uptime 1day 11 hours (24 hours running) tested: Intel(R) Core(TM) i5-3450 Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 7 Series/C210 Series Chipset Family High Definition Audio Controller RTL8111/8168B PCI Express Gigabit Ethernet controller video-out: DVI OK multiple suspend-resume cycles OK virtualbox up/downs OK audio OK network OK no freezes probably unrelated problems: 1x no response to clicks of external mouse for 15+ sec. (psmouse serio1: logips2pp) will report back on problems
Bug#694286: fstrcmp: missing Breaks+Replaces: libfstrcmp-dev ( 0.4)
Hi, I wonder why the man pages for library functions were moved from the -dev package to the utility package at all? It seems stange for a package with the description [...] provides a command to make fuzzy string comparisons to include the library documentation. Sadly the changelog isn't really informative, though #694939 suggests the man pages were moved back and forth multiple times... Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699091: linux-image-3.2.0-4-amd64: kernel BUG: Bad page map in process udevd
On Sun, 27 Jan 2013 14:10:49 +, Jules Villard wrote: On Sun, 27 Jan 2013 12:52:26 +, Ben Hutchings wrote: On Sun, 2013-01-27 at 12:37 +, Jules Villard wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I hit a few BUGs at the end of boot time (see dmesg). They do not seem to visibly affect the stability of the system. There's also a swap_free: Bad swap offset entry 7fffc4010a6aa0 in the mix... [...] Please use memtest86+ to test the memory in this system. No errors in 1 pass. I will test again more thoroughly tonight. No errors in 9 passes (9 hours) either. Jules -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687442: [Backport] Use DRM/KMS subsystem from Linux 3.4 in wheezy
Le samedi 12 janvier 2013 à 21:54 +0100, Vincent Blut a écrit :
Le lundi 07 janvier 2013 à 23:55 +0100, Vincent Blut a écrit :
Le samedi 05 janvier 2013 à 17:25 +0100, Julien Cristau a écrit :
On Fri, Jan 4, 2013 at 17:13:35 +0100, Julien Cristau wrote:
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-686-pae_3.2.35-3~jcristau.1_i386.deb
sha1sum 17980ee5bafc40bb4e7bf42576ce40ac81c75833
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb
sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32
Hi Julien et al.
I tested with an Asus UX31A (Ivybridge Mobile GT2, eDP1 display), using
2D and 3D drivers from Wheezy (respectively versions 2.19.0-6 and
8.0.5-3).
On the DE side, I used GNOME Shell and Cinnamon (both need 3D
acceleration).
On the kernel side, I used:
i915.i915_enable_rc6={0, 1, 3} → no issue (don't know if it worth to
test RC6pp)
i915.semaphores=1 → ditto
In order to stress the GPU, I played some video bits in 1080p mostly
using VAAPI, played video games (native and emulated), and the usual
glxgear to see if all went well, and that's a *success*, the kernel is
pretty stable (contrary to the raw 3.2 series which causes some
freezes on this system, but that's another story I need to
investigate ;-)).
Voilà, to me this kernel is in really good shape, so thank you Julien
for backporting this stuff!
TODO:
- Testing VGA and HDMI outputs
I tested the HDMI output on two external screens (TV and 'standard'
display). Suspending/resuming with external display attached shows no
regressions, as well as sound through HDMI, which is handled by
'drm/i915' IIRC.
To conclude, those 'HDMI output' tests have shown neither new bugs nor
regressions (at least on my system).
Cheers,
Vincent
- Testing my old GPUs to prevent regressions (Radeon X800XL and Nvidia
7600GS)
Hi,
Finally had time to test those old cards, as expected absolutely all
went well.
Concerned devices:
$ lspci -nnv | grep VGA
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD]
nee ATI R430 [Radeon X800 XL] (PCIe) [1002:554d] (prog-if 00 [VGA
controller])
$ lspci -nnv | grep VGA
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation G73
[GeForce 7600 GS] [10de:0392] (rev a1) (prog-if 00 [VGA controller])
libdrm, 2D and 3D drivers from Wheezy.
Tested using glxgear, playing 720p videos (with Xvideo and Opengl video
output), playing some basic games, google earth…
Cheers,
Vincent
- Testing SNA (?)
- Advertising about this kernel (I found it haphazardly by diving in the
BTS)
Added
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-486_3.2.35-3~jcristau.1_i386.deb
sha1sum 76f67adbed522f8e42216f8595c8b5d1699af9ec
Cheers,
Julien
Regards,
Vincent
PS: By the way if Greg KH tags a new longterm kernel, will there be a
chance to see the DRM subsystem backported in Wheezy or that's
definitely too invasive and we'll stay with 3.4 (I don't have any issue
with that, I'm just curious).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699026: claws-mail: german translation at debian incomplete
Ricardo Mones schrieb am Mon, 28 Jan 2013 02:54:07 +0100: You have installed an old -i18n package, have you tried to upgrade it to 3.9.0-1 ? Sorry, mea culpa. As I updated claws-mail by hand I did so only for the main package... After doing so for the il8n-package fixed the bug. This issue can be closed. Sorry for the inconveniences, malenki -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698543: qcontrol: Sanitize input from lua scripts
On Sun, 2013-01-20 at 10:10 +0100, Hanno Hecker wrote: when passing a lua nil (or anything not a string or a number) value as second (or higher) arg to piccmd() qcontrol dies. Oops! This is because piccmd()s lcd-line0 / lcd-line1 commands do a strlen() on a NULL value. get_args() calls lua_tostring(), but this returns NULL for anything not a number or a string... Right, thanks. This issue isn't exposed on Wheezy (no LCD support) but I'll look into fixing this in Sid (bit busy right now, but I'll get to it). Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699157: linux-image-3.2.0-4-amd64: mount -o remount, ro on bind mount causes source filesystem to become read-only
Control: reassign -1 mount On Mon, 2013-01-28 at 04:37 -0600, Zev Weiss wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I'm experiencing what seems to be a kernel bug with read-only remounting of a bind mount (creating a read-only bind mount). After running the following commands, both /foo/dir_ro *and* /foo/dir become read-only: mount --bind /foo/dir /foo/dir_ro mount -o remount,ro /foo/dir_ro Running 'mount -o remount,rw /foo/dir' rectifies the situation, leaving it as I intended (/foo/dir writable, /foo/dir_ro read-only). [...] A bind mount is an alias for the same mount, and shares its options. This is similar too: touch foo ln foo bar chmod a-r bar # affects foo as well, because it is the same file But somewhat confusingly, there is an entirely separate un-shared read-only flag, which can you set when creating a bind-mount or when remounting. The mount command maps the 'ro' option to one of these depending on context. This is documented in mount(8) thus: Note that behavior of the remount operation depends on the /etc/mtab file. The first command stores the 'bind' flag to the /etc/mtab file and the second command reads the flag from the file. If you have a system without the /etc/mtab file or if you explicitly define source and target for the remount command (then mount(8) does not read /etc/mtab), then you have to use bind flag (or option) for the remount command too. For example: mount --bind olddir newdir mount -o remount,ro,bind olddir newdir I'm reassigning this to the mount package: the documentation is not as clear as it could be, and I think it should provide explicit names for the two different flags. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Bug#699165: rsync: debian/rules using ` instead of $(shell
On Mon 28 Jan 2013, StalkR wrote: Paul, yes sorry for the confusion, after that I was trying upstream's patches/detect-renamed.diff. I confirm I have the same sources and same output as you without this patch. OK, I think the problem lies there: you're applying patches and confusing configure somehow. There should be no need to run configure, even with that patch applied. Please verify that a fresh download and unpack of the rsync sources also give the same error. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698945: [Pkg-ia32-libs-maintainers] Bug#698945: Problem solved !!!
Dear maintainer, thanks for your help ! I found the problem and resolved it - the bug can be closed ! The problem was, that I did not realize (and no one told me - even not the maintainers after the explizit question why /usr/lib32/ is not existent ;-) that during an update of multiarch and the ia32-libs.. the folder /usr/lib32/ moved to /usr/lib/i386/linux-gnu/ After realizing this, it was very easy to set the correct links to make ADS2012 work again ! ln -s /usr/lib/i386-linux-gnu/libXm.so.2 /usr/lib/i386-linux-gnu/libXm.so.3 ln -s /usr/lib/libXm.so.4 /usr/lib/libXm.so.3 did it. Dear Goswin, one last question on this topic: When (version or date) was /usr/lib32 replaced by /usr/lib/i386-linux-gnu ? Best regards Holger
Bug#690127: [Pkg-utopia-maintainers] Bug#690127: release-notes: Issues: switch dm to get an active consolekit session
Hi, I probably won't get around to it sending you a detailed answer this week. Hopefully next week. Please poke me again if you haven't heard from me until then. If my memory serves me well, the workaround/solution for using startx from the console involves adding pam_loginuid/pam_ck_connector to your PAM stack. As for display manager like xdm or wdm, they are not really supported in the sense that they don't have native ConsoleKit support. So the easiest way there is indeed to either use gdm3, kdm or lightdm. I'd need to check if pam_ck_connector without nox11 can be forced into getting a working CK session with those types of display managers. But that needs some more time to investigate which I don't have atm. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#696993: vsftpd: Problem in install when vsftp is configured with listen=no
Package: vsftpd Version: 3.0.2-2 Followup-For: Bug #696993 Hi, I have a similar situation here: listen=NO, I change it to listen=YES onyl if I want to use the server, which is not very often. IMHO the prerm script should check whether the server was actually running at the time of upgrade and/or listen is set to yes/no in the config file before command: invoke-rc.d vsftpd stop || exit $? is executed and postinst should check for listen set to yes/no before running: invoke-rc.d vsftpd start || exit $? A bit of grep with some if statememnts hould do the trick but I'm not sure what Debian Policy has to say about situations like that. Kind regards, rjc -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (999, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 3.2.0-4-powerpc 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 vsftpd depends on: ii adduser 3.113+nmu3 ii cdebconf [debconf-2.0] 0.181 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libpam-modules 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii libssl1.0.0 1.0.1c-4 ii libwrap07.6.q-24 ii netbase 5.0 Versions of packages vsftpd recommends: ii logrotate 3.8.3-3 vsftpd suggests no packages. -- Configuration Files: /etc/vsftpd.conf changed [not included] -- debconf information: * vsftpd/username: ftp * vsftpd/directory: /srv/ftp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699169: [reportbug-ng] Calling the MUA failed: Syntax error: EOF in backquote substitution
Package: reportbug-ng Version: 1.27 Severity: normal reportbug-ng fails to open mail window (using claws-mail) with both 'miscellaneous' activated. After multiple tries it works. sh: 90: Syntax error: EOF in backquote substitution ReportbugNG WARNING Grr! Calling the MUA failed. Status and output was: 512, . Length of the command is: 3959 sh: 92: Syntax error: EOF in backquote substitution ReportbugNG ERRORCalling the MUA a second time with an even shorter message failed. Giving up. $ reportbug-ng sh: 39: Syntax error: EOF in backquote substitution ReportbugNG WARNING Grr! Calling the MUA failed. Status and output was: 512, . Length of the command is: 1046 sh: 41: Syntax error: EOF in backquote substitution ReportbugNG ERRORCalling the MUA a second time with an even shorter message failed. Giving up. --- System information. --- Architecture: i386 Kernel: Linux 3.2.0-4-686-pae Debian Release: 7.0 500 testing 127.0.0.1 --- Package information. --- Depends(Version) | Installed -+- python | 2.7.3~rc2-1 python-support (= 0.90.0) | 1.0.15 python-debianbts(= 1.0) | 1.11 python-qt4 | 4.9.3-4 xdg-utils| 1.1.0~rc1+git20111210-6 xterm| 278-4 python-apt (= 0.7.93) | 0.8.8.1 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699170: [gimp] Segfault on .png eport
Package: gimp Version: 2.8.2-2 Severity: normal I exported multiple files to .png and every time gimp segfaulted: $ gimp (gimp:24139): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed (script-fu:24149): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error Segmentation fault Calling the MUA failed: Syntax error: EOF in backquote substitution --- System information. --- Architecture: i386 Kernel: Linux 3.2.0-4-686-pae Debian Release: 7.0 500 testing 127.0.0.1 --- Package information. --- Depends (Version) | Installed ===-+-= libgimp2.0 (= 2.8.2) | 2.8.2-2 libgimp2.0 (= 2.8.2-z) | 2.8.2-2 gimp-data(= 2.8.2) | 2.8.2-2 gimp-data (= 2.8.2-z) | 2.8.2-2 python-gtk2 (= 2.8.0) | 2.24.0-3 libaa1 (= 1.4p5) | 1.4p5-40 libatk1.0-0 (= 1.12.4) | 2.4.0-2 libbabl-0.1-0 (= 0.1.10) | 0.1.10-1 libbz2-1.0 | 1.0.6-4 libc6 (= 2.11) | 2.13-37 libcairo2 (= 1.10.2) | 1.12.2-2 libdbus-1-3 (= 1.0.2) | 1.6.8-1 libdbus-glib-1-2 (= 0.88) | 0.100-1 libexif12 | 0.6.20-3 libexpat1(= 2.0.1) | 2.1.0-1 libfontconfig1 (= 2.9.0) | 2.9.0-7.1 libfreetype6 (= 2.2.1) | 2.4.9-1.1 libgdk-pixbuf2.0-0 (= 2.22.0) | 2.26.1-1 libgegl-0.2-0(= 0.2.0) | 0.2.0-2+nmu1 libglib2.0-0(= 2.31.8) | 2.33.12+really2.32.4-3 libgs9 (= 8.61.dfsg.1) | 9.05~dfsg-6.3 libgtk2.0-0(= 2.24.10) | 2.24.10-2 libgudev-1.0-0 (= 146) | 175-7 libice6(= 1:1.0.0) | 2:1.0.8-2 libjasper1 | 1.900.1-13 libjavascriptcoregtk-1.0-0 (= 1.5.1) | 1.8.1-3.3 libjpeg8(= 8c) | 8d-1 liblcms1(= 1.15-1) | 1.19.dfsg-1.2 libmng1 (= 1.0.10) | 1.0.10-3 libpango1.0-0 (= 1.29.4) | 1.30.0-1 libpng12-0(= 1.2.13-4) | 1.2.49-1 libpoppler-glib8 (= 0.18) | 0.18.4-4 librsvg2-2 (= 2.14.4) | 2.36.1-1 libsm6 | 2:1.2.1-2 libsoup2.4-1 (= 2.4.0) | 2.38.1-2 libtiff4 ( 3.9.5-3~) | 3.9.6-10 libwebkitgtk-1.0-0 (= 1.3.10) | 1.8.1-3.3 libwmf0.2-7(= 0.2.8.4) | 0.2.8.4-10.2 libx11-6| 2:1.5.0-1 libxcursor1 ( 1.1.2) | 1:1.1.13-1 libxext6| 2:1.3.1-2 libxfixes3 | 1:5.0-4 libxmu6 | 2:1.1.1-1 libxpm4 | 1:3.5.10-1 libxt6 | 1:1.1.3-1 zlib1g (= 1:1.1.4) | 1:1.2.7.dfsg-13 python(= 2.6.6-7~) | 2.7.3~rc2-1 python2.7 | 2.7.3-6 Recommends (Version) | Installed ==-+-=== ghostscript| 9.05~dfsg-6.3 Suggests (Version) | Installed ===-+-=== gimp-help-en| OR gimp-help | gimp-data-extras| gvfs-backends | 1.12.3-3 libasound2 | 1.0.25-4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699171: Pre-Approval: capi4hylafax/1:01.03.00.99.svn.300-19
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pre-approval Hello release team, I ask for pre-approval for package capi4hylafax. There is a difficult RC bug (#661482) which mention also package hylafax. To resolve this RC bug a bugfix for hylafax and capi4hylafax is needed. As first step here is the bugfix of capi4hylafax: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697733 The updated capi4hylafax 1:01.03.00.99.svn.300-19 fixes a part of RC bug #661482: * Optimize postrm script and add new postinst script to work together with hylafax-server and its 'mountbind'. (See: #661482) Details are in the attached debdiff. Many thanks for your work, --- Have a nice day. Joachim (Germany) debdiff_capi4hylafax_300-19.diff.gz Description: GNU Zip compressed data
Bug#699165: rsync: debian/rules using ` instead of $(shell
No I reported the bug before applying any patch. After I moved on with my stuff, which is unrelated. Fresh download and unpack of rsync debian sources give the same error: $ rm -rf rsync-3.0.9 $ dpkg-source -x rsync_3.0.9-4.dsc $ cd rsync-3.0.9 $ dpkg-buildpackage -rfakeroot -b [...] dpkg-buildpackage: error: debian/rules build gave error exit status 2 When you say you have no problem compiling on squeeze, do you compile rsync/unstable on squeeze too? - build rsync/squeeze on squeeze works because debian/rules do not have the backticks `` lines - build rsync/unstable on unstable works, backticks `` get expanded before passed to configure.sh - not sure how - build rsync/unstable on squeeze does not work, backticks `` do not get expanded and configure.sh complains This does not seem to be an sh - bash/dash issue, I've tried both. What do you think of my proposed debian/rules patch replacing backticks `` with $()? In addition to fixing build on squeeze, it will make these 2 lines consistent with the rest of the file (CPPFLAGS, DEB_BUILD_ARCH, DEB_BUILD_GNU_TYPE, DEB_HOST_GNU_TYPE). Thanks, StalkR On Mon, Jan 28, 2013 at 2:11 PM, Paul Slootman p...@debian.org wrote: On Mon 28 Jan 2013, StalkR wrote: Paul, yes sorry for the confusion, after that I was trying upstream's patches/detect-renamed.diff. I confirm I have the same sources and same output as you without this patch. OK, I think the problem lies there: you're applying patches and confusing configure somehow. There should be no need to run configure, even with that patch applied. Please verify that a fresh download and unpack of the rsync sources also give the same error. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699165: rsync: debian/rules using ` instead of $(shell
On Mon, Jan 28, 2013 at 1:40 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory This means you don't have a sufficiently new version of dpkg-dev installed which supports dpkg-buildflags. What do you mean exactly by supports dpkg-buildflags? Note the ` before dpkg-buildflags: it's a shell issue, the `` part was not evaluated somewhere before. Also, dpkg-dev/squeeze provides dpkg-buildflags: $ dpkg -S /usr/bin/dpkg-buildflags dpkg-dev: /usr/bin/dpkg-buildflag -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699172: vim: Shell syntax does not know dash and so uses error highlighting everywhere
Package: vim
Version: 2:7.3.547-6
Severity: normal
Dear Maintainer,
The .sh syntax file in vim 7.3 tries to find out which shell /bin/sh
points at and adapts appropriately. It does not know dash, and so it
falls back to some ground state where a lot of POSIX shell syntax is
marked with 'Error' highlighting.
Reproduce:
vim -u NORC -U NORC --cmd 'filetype plugin indent on' -N /etc/init.d/rc
:syntax on
vim will mark constructs like $(uname) and ${s#/etc/rc$runlevel.d/K} as
errors.
the sh syntax file should be adapted to know that dash is a posix shell.
regards,
-- Package-specific info:
--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 3.2.0-4-powerpc
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages vim depends on:
ii libacl1 2.2.51-8
ii libc62.13-37
ii libgpm2 1.20.4-6
ii libselinux1 2.1.9-5
ii libtinfo55.9-10
ii vim-common 2:7.3.547-6
ii vim-runtime 2:7.3.547-6
vim recommends no packages.
Versions of packages vim suggests:
pn ctagsnone
ii vim-doc 2:7.3.547-6
pn vim-scripts 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#620825: bacula-director-common: wrong email From address
Hi, I'm using this configuration in Messages: mailcommand = /usr/sbin/bsmtp -h SMTPHOST -f \Bacula \bac...@host.domain.tld\\ -s [..] The main reason is to have the real address instead of the fake %r which could be rejected at the destination. This same address is added automatically by 'bsmtp' on Sender: header. What I would like is to have a parameter (like %r) for the local host name that I could use instead of specifying the FQDN. Regarding this is mandated by strict RFC email rules. It's probably common to activate 'strict_rfc821_envelopes = yes' in Postfix to block unsolicited messages. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699165: rsync: debian/rules using ` instead of $(shell
On 28.01.2013 14:44, StalkR wrote: On Mon, Jan 28, 2013 at 1:40 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory This means you don't have a sufficiently new version of dpkg-dev installed which supports dpkg-buildflags. What do you mean exactly by supports dpkg-buildflags? Note the ` before dpkg-buildflags: it's a shell issue, the `` part was not evaluated somewhere before. Also, dpkg-dev/squeeze provides dpkg-buildflags: $ dpkg -S /usr/bin/dpkg-buildflags dpkg-dev: /usr/bin/dpkg-buildflag Ah, it's possible I misread the message in that case. If so, apologies for the confusion. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693666: NMU diff for dahdi-linux/1:2.6.1+dfsg2-0.1
On Sun, Jan 27, 2013 at 04:23:05PM +, Ben Hutchings wrote: I've uploaded the attached changes to DELAYED/5, and will follow this with an upload of dahdi-firmware. Thanks for your fixes. Applied them in SVN. I don't have the hardware and thus I'll try to get someone to test the patch. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699173: bsmtp: missing Message-Id: header on notifications
Package: bacula-common
Version: 5.2.6+dfsg-7
Severity: normal
Hi,
I've noticed that Message-Id: header is missing on notifications.
This could cause the notifications to be rejected by some SMTP servers.
Cheers
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 bacula-common depends on:
ii adduser 3.113+nmu3
ii libc6 2.13-37
ii libcap2 1:2.22-1.2
ii libgcc1 1:4.7.2-5
ii libpython2.7 2.7.3-6
ii libssl1.0.0 1.0.1c-4
ii libstdc++64.7.2-5
ii libwrap0 7.6.q-24
ii zlib1g1:1.2.7.dfsg-13
bacula-common recommends no packages.
Versions of packages bacula-common suggests:
pn bacula-doc none
-- Configuration Files:
/etc/logrotate.d/bacula-common changed:
/var/log/bacula/log {
create 0640 bacula adm
compress
delaycompress
missingok
notifempty
rotate 12
monthly
}
-- 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#696312: evince: print PDF ends in segfault and no printing
# Match tags with merge target
reassign 696312 libcairo2
found 696312 1.12.2-2
severity 696312 important
tags 696312 = fixed-upstream patch
merge 672336 696312
# Additional info
found 696312 1.12.2-2.1
affects 696312 + evince
#fixed 696312 1.12.2-2+deb7u2 (UNRELEASED)
thanks
Hi Michael,
I'm quite sure bug #696312 is a duplicate of #672336, #680277, #682673
and #687783 (and is perhaps related to embedded fonts). This is
definitely separate from #690799 (polygon intersection).
I first hit this problem using 1.12.2-2 printing a completely new PDF
from evince (my tax return!). A gdb backtrace is attached, and it
matches this one.
First I tried Neil's libcairo2, libcairo-gobject2 1.12.2-2.1 packages
from sid, but with no change.
Then I tried the libcairo2, libcairo-gobject2 1.12.2-2+deb7u2 packages,
and it successfully printed. Vytautas, you may like to try these too:
http://people.debian.org/~biebl/cairo/amd64/
Thank you!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Program terminated with signal 11, Segmentation fault.
#0 decode_integer (p=0x0, integer=integer@entry=0x7fff81597b20) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:241
241 /home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:
No such file or directory.
(gdb) bt full
#0 decode_integer (p=0x0, integer=integer@entry=0x7fff81597b20) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:241
No locals.
#1 0x7fbe2900ebda in cairo_cff_font_read_top_dict (font=0x7fbe2d9ba3c0) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:1185
index = {size = 1, num_elements = 1, element_size = 24, elements =
0x7fbe2d833fc0 }
element = optimized out
buf = `m'\276\177\000\000\025\000\000\000\000\000\000\000\220\036j-
operand = optimized out
status = CAIRO_INT_STATUS_SUCCESS
p = 0x7fbe2d6a1f2c
\203\223\370\263\223\367T\223\006\373\206\221\aY\240(\276\177
size = optimized out
offset = 160
#2 0x7fbe290102d2 in cairo_cff_font_read_font (font=0x7fbe2d9ba3c0) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:1321
i = optimized out
status = optimized out
#3 cairo_cff_font_generate (length=synthetic pointer, data=synthetic
pointer, font=0x7fbe2d9ba3c0)
at /home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:2545
status = optimized out
#4 _cairo_cff_subset_init (cff_subset=cff_subset@entry=0x7fff81597dd0,
subset_name=subset_name@entry=0x7fff81597e40 CairoFont-2-1,
font_subset=font_subset@entry=0x7fff81597f40) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-cff-subset.c:2928
font = optimized out
status = optimized out
data = 0x0
length = 0
i = optimized out
#5 0x7fbe2904bb72 in _cairo_pdf_surface_emit_cff_font_subset
(font_subset=0x7fff81597f40, surface=0x7fbe2d93a6e0)
at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-pdf-surface.c:4884
status = optimized out
subset = {family_name_utf8 = 0x0, ps_name = 0x7fbe2d73df20
\020Ï-\276\177, widths = 0x7fbe2d96cf20, x_min = -0.115, y_min =
-0.23599,
x_max = 0.94595, y_max = 0.96697, ascent =
0.96697, descent = -0.23599, data = 0x7fbe2d5e8700
\360Ë-\276\177,
data_length = 238}
name =
CairoFont-2-1\000\000\000\060\b\000\000\000\000\000\000Å\377)\201\000\000\000\340\263\371(\276\177\000\000\320\362i-\276\177\000\000`m'\276\177\000\000\000\b\000\000\000\000\000
#6 _cairo_pdf_surface_emit_unscaled_font_subset (font_subset=0x7fff81597f40,
closure=0x7fbe2d93a6e0)
at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-pdf-surface.c:5596
surface = 0x7fbe2d93a6e0
status = CAIRO_INT_STATUS_SUCCESS
#7 0x7fbe290119be in _cairo_sub_font_collect (closure=0x7fff81597ef0,
entry=0x7fbe2d506fa0)
at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-scaled-font-subsets.c:751
sub_font = 0x7fbe2d506fa0
collection = 0x7fff81597ef0
subset = {scaled_font = 0x7fbe2d519200, font_id = 2, subset_id = 1,
glyphs = 0x7fbe2d78a0e0, utf8 = 0x7fbe2d78a590, glyph_names = 0x0,
to_latin_char = 0x0,
latin_to_subset_glyph_index = 0x0, num_glyphs = 2, is_composite = 1,
is_scaled = 0, is_latin = 0}
i = optimized out
j = optimized out
#8 _cairo_scaled_font_subsets_foreach_internal (font_subsets=optimized out,
font_subset_callback=font_subset_callback@entry=0x7fbe2904baf0
_cairo_pdf_surface_emit_unscaled_font_subset,
closure=closure@entry=0x7fbe2d93a6e0,
type=type@entry=CAIRO_SUBSETS_FOREACH_UNSCALED) at
/home/neil/code/debian/src/cairo/cairo-1.12.2/src/cairo-scaled-font-subsets.c:1072
collection = {glyphs = 0x7fbe2d78a0e0, utf8 = 0x7fbe2d78a590,
glyphs_size = 71, to_latin_char = 0x7fbe2d69f2d0, latin_to_subset_glyph_index =
