Bug#688151: fwknop: Multiple security issues
Hi Luciano, Le 19/09/2012 22:40, Luciano Bello a écrit :[...] The new fwknop fixes many security problems: http://seclists.org/oss-sec/2012/q3/509 It's fixed in 2.0.3. The link include the patches too. I have upgraded my working copy with the latest 2.0.3 but I was working on the perl binding, so I did not upload it by now. I am going to upload it to fix theses issues. Regards, -- Franck -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688190: ssvnc: vncviewer fails to nudge gnome screensaver in fullscreen mode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: ssvnc Version: 1.0.29-2 Severity: normal Dear Maintainer, I use ssvnc to access my desktop, and often work in fullscreen mode for extended periods of time (more than 10 minutes). After pressing F9 to disable fullscreen mode (to access my laptop's Gnome desktop again), i am presented with a locked desktop, which i have to unlock. My understanding is that vncviewer does not report my activity to Gnome, Gnome thinks that i'm AFK, fires up gnome-screensaver, which then locks my screen - all the while i'm working in a fullscreen VNC session, and when i interrupt this session, i find my screen locked. - -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.0-rc3-custom+ (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ssvnc depends on: ii bind9-host [host] 1:9.8.1.dfsg.P1-4.2 ii host 1:9.8.1.dfsg.P1-4.2 ii libc6 2.13-35 ii libice62:1.0.8-2 ii libjpeg8 8d-1 ii libsm6 2:1.2.1-2 ii libssl1.0.01.0.1c-4 ii libx11-6 2:1.5.0-1 ii libxaw72:1.0.10-2 ii libxext6 2:1.3.1-2 ii libxmu62:1.1.1-1 ii libxpm41:3.5.10-1 ii libxt6 1:1.1.3-1 ii openssh-client 1:6.0p1-3 ii openssl1.0.1c-4 ii procps 1:3.3.3-2 ii psmisc 22.19-1 ii stunnel4 3:4.53-1 ii tk 8.5.0-2 ii xterm 278-2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages ssvnc recommends: ii default-jre [java5-runtime]1:1.6-47 ii gcj-4.4-jre [java5-runtime]4.4.5-2 ii gcj-4.7-jre [java5-runtime]4.7.1-3 ii gcj-jre [java5-runtime]4:4.7.1-1 ii openjdk-6-jre [java5-runtime] 6b24-1.11.4-3 ssvnc suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQWsR+AAoJEOs4Jb6SI2CwYU8IAMxCYcEDy+94mro4IxOj3y9t vty42T9cLqzLy7o2f6bgYT3VVclWr+ddRW/JhLXcCbKzUsXOPNI3C8ratxOZnNuY g6UDQXgoG43AR8JW9cGyd9b7jUhq0EOSKhtxo7J2oGOKYlN9wITbT4sjJ2Juf6oL iHctYCJDTqx6TQHfqqzIF39zEpqjWeq4iCW3vjRk31Dys2iuWT4+rrZWWeARjzcL GYj7n3KckMiJiU8kfJLqR5UBxIG0pf794AkZF2xQBkzAtWNh6NGDgLszhtnK2D7m E7O+fHcejywTgSVBtmEAbKU1e6koAB0pMM6FHPiygLV0rljT7wcyEzSMqZHMm0E= =ebSr -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#688100: unblock: fglrx-driver/1:12-6+point-2
On 2012-09-20 07:30, Christian PERRIER wrote: > Quoting Andreas Beckmann (deb...@abeckmann.de): >> Please unblock package fglrx-driver > > I very strongly object to this. > I appreciate the effort you have put up to now in maintaining this > package in an l10n-friendly way so I think we can easily reach an agreement. > > I can for instance make sure you get these 8 needed updates (among > others probably). I can even "shake" the late comers (there will be some). That would be great. Let's see how the situation looks on October 1st. > Many thanks in advance for considering my objection, still..:-) >From my experience, it takes time to get non-translation updates approved, therefore I wanted to send the unblock request as early as possible so that the changes can be reviewed while I'm waiting for translations to come in. Translation-only updates seem to get accepted quickly (cf. nvidia-support, nvidia-graphics-drivers-legacy-96xx). And I want to get this update in wheezy quickly to avoid collecting a lot of duplicates of the "on amd64, wine 32bit opengl does not work any more" bug (due to having the old monolithic ia32-libs installed). Furthermore it contains wrong or missing information - that was not yet available during the previous translation round. So while I appreciate your i18n efforts (and try to make my packages translation friendly), I think it would be better to temporarily have a partially translated fglrx-driver package in wheezy. And we are talking about non-free here. So hopefully once the package migrates, I can make another i18n upload with all the translations (that could even be aged to get in more quickly). Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613610: xburst-tools at mentors
On Thu, 2012-09-20 at 07:06 +, Bart Martens wrote: > I don't find version 201206 on the upstream website. Where did you > get it ? He is upstream, I expect he created it and uploaded it to mentors but forgot to upload it to the website. > How is progress on donating/lending a suitable device to a sponsor for > getting bug 613610 fixed ? Unfortunately lending/donating a NanoNote isn't currently possible. I think we came to the conclusion that a sponsor should build it in qemu, send xiangfu the unsigned binary package for testing and only sign and upload it after xiangfu has successfully tested it. Once we get MIPS cross-compilers[1] in Debian it could simply be cross-compiled instead. 1. http://gsoc.sitedethib.com/posts/State_of_Multiarch_Cross-toolchains_three_weeks_after_GSoC/ -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#688191: msmtp: Please update to 1.4.29 (2012-09-04)
Package: msmtp Severity: wishlist Please update to 1.4.29 released 2012-09-04 according to https://freecode.com/projects/msmtp -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613610: xburst-tools at mentors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/20/2012 03:31 PM, Paul Wise wrote: > On Thu, 2012-09-20 at 07:06 +, Bart Martens wrote: > >> > I don't find version 201206 on the upstream website. Where did you >> > get it ? Here it is: http://projects.qi-hardware.com/index.php/p/xburst-tools/downloads/86/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBCAAGBQJQWsiRAAoJEN455DfyzFOYQhIP/RVhA1YV23k1sZl17LiCWib1 1l/poY+87HZg30zUcGjttVEcHZMIoxiw/BQVMYODZ9ovTLIxD7wy0gdC3hB2Rm9S g0O697glhkLrFgxqPFH7RVsDg5AfJW1ZwZIgjfvub1R0Jq7m0p7nMABTAKrkcBWS dq0HZOM4bMR7/sAvDMTlqDQj4a8pNP7I9/CvTGqjn7HnAvMtTVg0zVIk5Li2brVT 3zCuaq5n5bZcEcB07WTXfmXQWHFjWxl8DAyUXLIGgetW8Hp5j27Q1p5Ngo9zILer 8yXAsZDavvFy7pbu9MNCwmLeaUccV+BoTeaktmHnfzPkJP++lJYRiopcxYGR8uL2 ruWCC5TcKjnO2NCNV/tRimltc0q+0P1nJ7PBkwKAMaGo1+H6rDowywVOehNnlv94 5WecLX21QJ4M13QAR+RKrxrBJrNoSMTDfjTpVeZJKdqcrjYe1kANdiaYo1UZlJoX InLlPcpZiZvrE+PmviiVnTM2fAdCw2zkvMYa451xZvccphWeZKh/GW4XT0d9w08+ 6zqwfiNl3lyk5SOyKvjo64lDC+u0aUygY+1WBMCj6cnIZqmf9kQj4cZtSBWknyVE /sE05p7JXm/OzTNqQ2dWoph26VktI7MJ6wRmtOSLIGEJXkxmq1qcyHK+FNIndP5K 09wzQovMwJA1Cpyhlg74 =9KeL -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#603036: Fwd: pu: package lvm/2.02.66-5.1
The pu request is #687761
http://bugs.debian.org/687761
Original Message
Subject: pu: package lvm/2.02.66-5.1
Date: Sat, 15 Sep 2012 17:03:48 +0200
From: Andreas Beckmann
To: Debian Bug Tracking System
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I've prepared a NMU for lvm that fixes #603036: "lvm2: fails to install
due to incorrect dependencies in init.d LSB header"
The bug is tagged squeeze-ignore:
On Monday, 27. December 2010 00:06:20 Julien Cristau wrote:
> On Mon, Dec 13, 2010 at 21:35:36 +0100, Petter Reinholdtsen wrote:
> > Given that udev is installed on most Debian systems, it can be
> > argued
> > that this issue is not release critical. I expect incorrect udev
> Agreed, I won't make this a blocker for squeeze. A fix would still be
> welcome though.
I'm just adding the udev dependency to the lvm2 package, not touching
the initscript (which has been updated for wheezy to make udev
optional). This just makes the current situation (udev has to be
installed for lvm to work) explicit.
This bug is a bit annoying for piuparts because we need to work around
this for lvm2 and its rdepends, therefore I'd like to see this fixed.
If this request is confirmed, I'll go looking for a sponsor.
Andreas
PS: I just noticed, the version should probably be 2.02.66-5+squeeze1
diffstat for lvm2-2.02.66 lvm2-2.02.66
changelog | 12
control |2 +-
2 files changed, 13 insertions(+), 1 deletion(-)
diff -Nru lvm2-2.02.66/debian/changelog lvm2-2.02.66/debian/changelog
--- lvm2-2.02.66/debian/changelog 2011-01-23 18:30:34.0 +0100
+++ lvm2-2.02.66/debian/changelog 2012-09-15 16:39:47.0 +0200
@@ -1,3 +1,15 @@
+lvm2 (2.02.66-5.1) stable; urgency=low
+
+ * Non-maintainer upload.
+ * lvm2: add Depends: udev. (Closes: #603036)
+This is a workaround for the initscript depending on udev. For wheezy,
+this has been fixed by updating the initscript dependencies, but for
+squeeze let's just depend on the udev package.
+There is no need to restrict this change to [linux-any] since lvm has an
+unrestricted B-D: libudev-dev.
+
+ -- Andreas Beckmann Sat, 15 Sep 2012 16:27:27 +0200
+
lvm2 (2.02.66-5) unstable; urgency=low
* Remove old libdevmapper1.02 init script on upgrade. (closes: #549316)
diff -Nru lvm2-2.02.66/debian/control lvm2-2.02.66/debian/control
--- lvm2-2.02.66/debian/control 2011-01-23 18:29:31.0 +0100
+++ lvm2-2.02.66/debian/control 2012-09-15 16:34:43.0 +0200
@@ -11,7 +11,7 @@
Package: lvm2
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base, dmsetup (>> 2:1.02.47)
+Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base, dmsetup (>> 2:1.02.47), udev
Breaks: grub-common (<<1.98+20100527-1)
Conflicts: lvm-common
Replaces: lvm-common
Bug#686949: ITP: fpgatools -- tool to program flexible programmable gate arrays.
On 09/11/2012 04:03 PM, Timo Juhani Lindfors wrote: > I am not very familiar with FPGA concepts since I have not used them yet > so my questions might be bit stupid. I have not used them yet because I > thought they always required non-free tools. > > Don't you normally use VHDL or Verilog to describe the models? Is C used > here instead? Hi Timo Using C here. Checkout the source code of hello_world.c: https://github.com/Wolfgang-Spraul/fpgatools/blob/master/hello_world.c >> > https://github.com/Wolfgang-Spraul/fpgatools > Thanks for the link, I'll pass it on to friends who know about FPGAs :) Thanks for that Xiangfu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603036: Bug#687761: pu: package lvm/2.02.66-5.1
On 2012-09-19 22:55, Adam D. Barratt wrote: > Please could you expand a little on why you feel adding the dependency > would be a better solution than making the use of udev optional via the > LSB headers as (as you noted) was done for wheezy? I do not know the lvm2 package well enough to judge whether "fixing the initscript" is a safe solution for squeeze (or if there are some other implicit dependencies relying on the current setup) and if there may have been other related fixes in wheezy. So I did not want to touch the initscript dependency graph in squeeze (i.e. removing an edge). Instead I thought explicitly adding the package dependency that currently makes lvm2 "just work" out of the box should have less potential to cause problems. I just forwarded the thread to #603036 (that I want to get fixed), perhaps the maintainers have some more input on this. Looks like I missed to set a proper X-Debbugs-Cc initially ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668354: Downgrading
2012/9/19 Marcin Owsiany : > severity 668354 wishlist > thanks > > I had a look at LSB and it agrees with Debian policy in that it also > requires calling a command rather than manipulating symlinks directly. > [..] That's the requirement for Debian packages only. Also, «install_initd» is provided by lsb-core which is not guaranteed to be installed. > As such I don't think this warrants an RC bug. I'm downgrading it to > wishlist. Personally I'd close or mark it wontfix, but I'll leave that > up to the maintainer. Are you serious?! Are you expecting a multi-platform product to do a dozen of checks for each system type and execute update-rc.d/chkconfig/whatever based on that? Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688107: ITP: casa -- The Common Astronomy Software Applications package
Hi Julian, On 19.09.2012 19:46, Julian Taylor wrote: > from a brief look through the source it seems it is still using ipython > <= 0.10 and thus incompatible with debians ipython >= 0.13. What concrete problems should I expect here? And do you have a feeling how much work it would be to push the source to 0.13 compatibility? Best regards Ole -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668354: /etc/rcN.d/[SK]* symlinks are ignored if not mentioned on the /etc/init.d/.depend.* TARGETS
2012/9/19 Marcin Owsiany : > AFAICT the issue is that: > - muse creates symlinks in /etc/rcN.d directly, rather than using >update-rc.d, thus insserv never learns about it, > - when insserv is installed and not explicitly disabled, the symlinks >are completely ignored No, insserv does learn about them after the first execution (insserv command or any update-rc.d) because the init script has LSB headers. > I think this title summarizes the issue much better. A more correct title would be "/etc/rcN.d/[SK]* symlinks are ignored if not mentioned on the /etc/init.d/.depend.* TARGETS". > Now, whether this is actually an RC bug is unclear to me. The Debian > policy mandates that init scripts are installed using update-rc.d. > One might say that if muse does not follow Debian policy, it does not > seem fair to claim that sysvinit has a bug... The bug is that the boot process should not depend on the insserv internals (/etc/init.d/.depend.*). You have a S/K??service link than execute it accordingly. > If sysvinit cared about compatibility with products such as muse, it > could use the following approach: > - scan all symlinks for runlevel N > - strip the [SK]XX prefix > - filter away the names which are in /etc/init.d/.depend.* $TARGETS > - if any names remain, they must be such legacy scripts - run them > However this procedure would not preserve the correct ordering of > scripts.. I think you are talking here about the re-ordering of symlinks on insserv or update-rc.d executions. Maybe I wasn't clear, but I was not arguing about this ordering which is fine as it is now. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688192: db5.3: Ensure backwards compatible Java bytecode is built
Package: db5.3 Version: 5.3.15-4 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu quantal ubuntu-patch openjdk-7-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Ensure backwards compatible Java bytecode is built (LP: #1049766): - d/rules: Specify JAVACFLAGS (source/target = 1.5) and pass to dh_auto_configure. This ensures that libdb5.3-java is compatible will all java runtime environments supported in Debian. Thanks for considering the patch. - -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-15-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQWs6hAAoJEL/srsug59jDnL4QAJarlMedMy67RZmqWrHQf7nr ++bfAFuu5PnOcDQgD2qZji1khh4Vj8IzOhuGRd+VKkUOOlwMD3oSO2GmV6bJrmi7 qb/dGNvPUrnINj9H7/3NY8cpSIigUUjUSatxzAlu29yoquKBc6xkk1UEdipGE5kK Vzx+kfS9TrIIjSgzQjIUmozQ+cDmCRXcO/RMZk/rirgIzUexK1wOLJw5hmv5KdXm Vgdgz3Qh6FDsTpoT2yW7wAyMYAG9yamJgv5YfjjbnLxO/Q6aSAjshXR3O9f3YW3F aWqHJRQ1e8LJsWhZeEGqv7OvrtImmuYufl2xQyQ9pPi56xD3p/2g/AdVAFvLOjL+ 4YB8Tpmg4pienFS8S2YAKe9IcSAArjCOC+VWi9/5D7PzxuTo4FFU7A/SBjbYo/6D zYcTZW+Kr+oxgqsESmmN0T/F4GCYMoPTfSheFhbzexrzC0jI0k4MwC2H7nwVteaf 37eE5z+DkZZdcLHOTxXxcuHijxgQjq2PUvZMba76beAQ79Rg49pzLCWgt155G0yD viq82Qtm8FoCib+TK3AQAoMtXZk5y4BxzV4SD90waoy84CQkWywHtxHzwH8eWZ1D wsuxUXlSdIK92ajgl2R7KifW93sTr/wPWW88DdtnZGGCPtials5e6mgUpLnR6ZYI m1s7DZLxQ/9JHy3xinLq =xrEU -END PGP SIGNATURE- diff -Nru db5.3-5.3.15/debian/changelog db5.3-5.3.15/debian/changelog diff -Nru db5.3-5.3.15/debian/rules db5.3-5.3.15/debian/rules --- db5.3-5.3.15/debian/rules 2012-05-11 13:30:04.0 +0100 +++ db5.3-5.3.15/debian/rules 2012-09-19 19:17:21.0 +0100 @@ -62,6 +62,7 @@ endif ifeq (yes,$(ENABLE_JAVA)) +JAVACFLAGS=-source 1.5 -target 1.5 JAVA_HOME ?= /usr/lib/jvm/default-java CFLAGS += -I$(JAVA_HOME)/include -I$(JAVA_HOME)/include/linux CONFIGURE_SWITCHES += --enable-java @@ -96,9 +97,9 @@ override_dh_auto_configure: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) - dh_auto_configure -Ddist -Bbuild-test -- $(CONFIGURE_SWITCHES) --enable-test + JAVACFLAGS="$(JAVACFLAGS)" dh_auto_configure -Ddist -Bbuild-test -- $(CONFIGURE_SWITCHES) --enable-test endif - dh_auto_configure -Ddist -Bbuild-production -- $(CONFIGURE_SWITCHES) --disable-test + JAVACFLAGS="$(JAVACFLAGS)" dh_auto_configure -Ddist -Bbuild-production -- $(CONFIGURE_SWITCHES) --disable-test override_dh_auto_clean: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
Bug#688193: lsh-utils: [INTL:sk] Slovak po-debconf translation
Package: lsh-utils Severity: wishlist Tags: l10n patch Version: 2.0.4-dfsg-11 The sk.po attached. regards # Slovak translations for lsh-utils package # Slovenské preklady pre balík lsh-utils. # Copyright (C) 2012 THE lsh-utils'S COPYRIGHT HOLDER # This file is distributed under the same license as the lsh-utils package. # Slavko , 2012. # msgid "" msgstr "" "Project-Id-Version: lsh-utils 2.0.4-dfsg-11\n" "Report-Msgid-Bugs-To: lsh-ut...@packages.debian.org\n" "POT-Creation-Date: 2012-09-09 11:31-0400\n" "PO-Revision-Date: 2012-09-20 10:09+0200\n" "Last-Translator: Slavko \n" "Language-Team: slovenčina \n" "Language: sk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" "X-POFile-SpellExtra: default 22 lshd openssh-server OpenSSH lsh sftp purge\n" "X-POFile-SpellExtra: etc SSH lsh-server SFTP\n" #. Type: string #. Description #: ../lsh-server.templates:2001 msgid "lsh server port:" msgstr "Port servera lsh:" #. Type: string #. Description #: ../lsh-server.templates:2001 msgid "" "The default port for lshd is 22. If lshd should run on a different port, " "please specify the alternative port here. If you specify 22, you will need " "to manually disable any other SSH servers running on port 22, other than " "OpenSSH (from the package openssh-server), which will be disabled " "automatically if you choose 22 here." msgstr "" "Predvolený port pre lshd je 22. Ak má byť lshd spustený na inom porte, " "prosím, zadajte tu alternatívny port. Ak zadáte 22, budete musieť manuálne " "vypnúť všetky ostatné servery SSH, ktoré bežia na porte 22, okrem OpenSSH (z " "balíka openssh-server), ktorý bude vypnutý automaticky, ak tu zvolíte 22." #. Type: boolean #. Description #: ../lsh-server.templates:3001 msgid "Enable the sftp subsystem?" msgstr "Zapnúť subsystém sftp?" #. Type: boolean #. Description #: ../lsh-server.templates:3001 msgid "" "Please choose whether you want to use the EXPERIMENTAL lsh SFTP support." msgstr "Prosím, zvoľte, či chcete v lsh používať EXPERIMENTÁLNU podporu SFTP." #. Type: boolean #. Description #: ../lsh-server.templates:3001 msgid "" "Since it is experimental, the default is for it to be disabled, but it can " "be enabled now or later by manually changing /etc/default/lsh-server." msgstr "" "Pretože je táto podpora experimentálna, je predvolene vypnutá, ale môžete ju " "zapnúť teraz alebo neskôr manuálne, zmenou /etc/default/lsh-server." #. Type: boolean #. Description #: ../lsh-server.templates:4001 msgid "Remove host key on purge?" msgstr "Odstrániť kľúč hostiteľa pri vyčistení (purge)?" #. Type: boolean #. Description #: ../lsh-server.templates:4001 msgid "" "When this package is installed, a host key is generated to authenticate your " "host." msgstr "" "Pri inštalácii tohoto balíka je vygenerovaný kľúč hostiteľa, na " "autentifikáciu vášho hostiteľa." #. Type: boolean #. Description #: ../lsh-server.templates:4001 msgid "" "Please choose whether you want to purge the host key when the package is " "removed." msgstr "" "Prosím, zvoľte, či chcete pri odstránení balíka odstrániť aj kľúč hostiteľa." #. Type: string #. Description #: ../lsh-server.templates:5001 msgid "Additional arguments to pass to lshd:" msgstr "Doplnkové argumenty pre lshd:"
Bug#675039: second this
I would like to wake up this thread. libslepc3.2-dev is pretty useless without the patch since no program compiles which includes slepc's headers. The patch is easy to apply and seems to have no negative side effects. Please integrate! Best, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675039: second this
I would like to wake up this thread. libslepc3.2-dev is pretty useless without the patch since no program compiles which includes slepc's headers. The patch is easy to apply and seems to have no negative side effects. Please integrate! Best, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685375: Breaks booting with nfsroot
Package: live-boot
Version: 3.0~b1-1
Followup-For: Bug #685375
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch
*** /tmp/tmpEQf01u/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
* ensure that a potentially stray tmpfs gets removed
otherways, initramfs-tools is unable to remove /live
and fails to boot. Closes: #685375, LP: #1043834
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise-proposed'), (500, 'precise')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru live-boot-3.0~b1/debian/changelog live-boot-3.0~b1/debian/changelog
--- live-boot-3.0~b1/debian/changelog 2012-08-16 12:27:22.0 +0200
+++ live-boot-3.0~b1/debian/changelog 2012-09-20 09:43:51.0 +0200
@@ -1,3 +1,11 @@
+live-boot (3.0~b1-1ubuntu1) quantal; urgency=low
+
+ * ensure that a potentially stray tmpfs gets removed
+ otherways, initramfs-tools is unable to remove /live
+ and fails to boot. LP: #1043834
+
+ -- Reinhard Tartler Thu, 20 Sep 2012 09:37:53 +0200
+
live-boot (3.0~b1-1) unstable; urgency=low
[ chals ]
diff -Nru live-boot-3.0~b1/debian/patches/series live-boot-3.0~b1/debian/patches/series
--- live-boot-3.0~b1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ live-boot-3.0~b1/debian/patches/series 2012-09-20 09:40:23.0 +0200
@@ -0,0 +1 @@
+unbreak-booting
diff -Nru live-boot-3.0~b1/debian/patches/unbreak-booting live-boot-3.0~b1/debian/patches/unbreak-booting
--- live-boot-3.0~b1/debian/patches/unbreak-booting 1970-01-01 01:00:00.0 +0100
+++ live-boot-3.0~b1/debian/patches/unbreak-booting 2012-09-20 09:43:25.0 +0200
@@ -0,0 +1,22 @@
+Description: Ensure that stray /live/overlay gets unmounted
+ ensure that a potentially stray tmpfs gets removed
+ otherways, initramfs-tools is unable to remove /live
+ and fails to boot. LP: #1043834
+Author: Reinhard Tartler
+
+---
+Origin: Ubuntu
+Bug-Ubuntu: https://launchpad.net/bugs/1043834
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685375
+
+--- live-boot-3.0~b1.orig/scripts/boot/9990-overlay.sh
live-boot-3.0~b1/scripts/boot/9990-overlay.sh
+@@ -412,4 +412,8 @@ setup_unionfs ()
+ mkdir -p "${rootmnt}/live/overlay"
+ mount -o move /live/overlay "${rootmnt}/live/overlay" >/dev/null 2>&1 || mount -o bind /overlay "${rootmnt}/live/overlay" || log_warning_msg "Unable to move or bind /overlay to ${rootmnt}/live/overlay"
+
++# ensure that a potentially stray tmpfs gets removed
++# otherways, initramfs-tools is unable to remove /live
++# and fails to boot
++umount /live/overlay || :
+ }
Bug#688194: prewikka: modifies conffiles (policy 10.7.3): /etc/prewikka/prewikka.conf
Package: prewikka Version: 1.0.0-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/prewikka/prewikka.conf cheers, Andreas prewikka_1.0.0-1.1.log.gz Description: GNU Zip compressed data
Bug#688195: Missing import of errno in runcmd.py
Package: python-cliapp Version: 1.20120630-1 Severity: important Tags: patch runcmd.py uses the errno module in line 93 without first importing it. The patch below adds the missing import. It would be nice if this bug could be fixed for wheezy. As it only affects an error path it does not render the package unusable in most cases. Thus I was a bit reluctant to set a RC severity myself. I can also prepare an upload if you don't have the time to fix the issue at the moment. Gaudenz --- python-cliapp-1.20120630.orig/cliapp/runcmd.py +++ python-cliapp-1.20120630/cliapp/runcmd.py @@ -20,6 +20,7 @@ import os import select import subprocess +import errno import cliapp -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-cliapp depends on: ii python 2.7.3~rc2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 python-cliapp recommends no packages. Versions of packages python-cliapp suggests: pn libjs-query ii libjs-underscore 1.1.6-1 -- 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#653186: Reopen, because still affecting wheezy
Ok, but it is the only way to make it show up as blocking bug (of 677741). Best, Tobias Hansen "Adam D. Barratt" schrieb: >Version: 1:2.22-1.1 > >On 04.09.2012 17:33, Tobias Hansen wrote: >> reopen 653186 > >Please don't. The bug is resolved and the BTS is quite capable of >determining which suites contain a fixed version without artificially >fiddling with the bug state. > >Regards, > >Adam
Bug#688197: dovecot-managesieved: managesieve segfault in libc
Package: dovecot-managesieved
Version: 1:2.1.7-2
Severity: important
Dear Maintainer,
managesieve (Dovecot) fails with a segfault in libc when using the
CHECKSCRIPT Command. I was able to reproduce the error using the "Sieve
Filter"-Addon for Thunderbird. If "Check Syntax" is enabled the
connection drops after editing the filter script. If "Check Syntax" is
disabled everything works fine.
Here's the logfile entry:
Sep 14 13:09:14 pdc kernel: [2937237.530373] managesieve[10194]:
segfault at 0 ip 7fe185011664 sp 7fffc8118ad8 error 4 in
libc-2.13.so[7fe184f01000+17d000]
See http://dovecot.org/pipermail/dovecot/2012-September/068130.html
Best regards
Denis Witt
-- Package-specific info:
dovecot configuration
-
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-3-amd64 x86_64 Debian wheezy/sid ext4
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
listen = *
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_location = maildir:/var/mail/%u
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date ihave passdb { driver = pam }
passdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
plugin {
quota = maildir
quota_rule = *:storage=10G
quota_rule2 = Trash:storage=+500M
quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
trash = /etc/dovecot/dovecot-trash.conf
}
protocols = imap sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
user = root
}
service imap-login {
chroot = login
user = dovecot
}
service managesieve-login {
chroot = login
user = dovecot
}
service pop3-login {
chroot = login
user = dovecot
}
ssl_cert =
ii dovecot-dev1:2.1.7-2
ii dovecot-gssapi 1:2.1.7-2
ii dovecot-imapd 1:2.1.7-2
ii dovecot-ldap 1:2.1.7-2
pn dovecot-lmtpd
ii dovecot-managesieved 1:2.1.7-2
ii dovecot-mysql 1:2.1.7-2
ii dovecot-pgsql 1:2.1.7-2
pn dovecot-pop3d
ii dovecot-sieve 1:2.1.7-2
ii dovecot-sqlite 1:2.1.7-2
-- 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#688196: mimedefang: modifies conffiles (policy 10.7.3): /etc/default/mimedefang
Package: mimedefang Version: 2.73-1 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 mimedefang/2.69-1 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/mimedefang cheers, Andreas mimedefang_2.73-1.log.gz Description: GNU Zip compressed data
Bug#658252: libcairo2: Text quickly becomes rectangles
Seems fixed here too. I'm running testing on a Quadro NVS 135M. I unhold libcairo2:i386 1.10.2-7 -> 1.12.2-2 last week and I did not experienced the reported problem since then. pp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688199: bacula-director-sqlite3: modifies conffiles (policy 10.7.3): /etc/bacula/scripts/delete_catalog_backup
Package: bacula-director-sqlite3 Version: 5.2.6+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/bacula/scripts/delete_catalog_backup cheers, Andreas bacula-director-sqlite3_5.2.6+dfsg-3.log.gz Description: GNU Zip compressed data
Bug#688200: fprobe: modifies conffiles (policy 10.7.3): /etc/default/fprobe
Package: fprobe Version: 1.1-7.2 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/fprobe cheers, Andreas fprobe_1.1-7.2.log.gz Description: GNU Zip compressed data
Bug#688083: xrdp: no normal edit possible in remote session UP key disfunctional
❦ 19 septembre 2012 08:27 CEST, Joachim Schmidt : > remote session per rdesktop (squeeze) and xrdp (wheezy) on the server: I can > not get old commands in terminal (terminal switches between full and small > size > instead), can not edit in vim (previous/next line not reachable) and can not > edit in eclipse without mouse clicks. > Terminal session per ssh works normal. How do you connect to xrdp? If you use rdesktop, do you specify a keyboard map (with -k)? If not, could you try to specify "-k de". -- Use library functions. - The Elements of Programming Style (Kernighan & Plauger) pgppTxJwJMDG1.pgp Description: PGP signature
Bug#688201: gcl: modifies conffiles (policy 10.7.3): /etc/default/gcl
Package: gcl Version: 2.6.7-103 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 gcl/2.6.7-62 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/gcl cheers, Andreas gcl_2.6.7-103.log.gz Description: GNU Zip compressed data
Bug#688202: jackd2: error output from postinst: jackd2.postinst: line 15: [: =: unary operator expected
Package: jackd2 Version: 1.9.8~dfsg.4+20120529git007cdc37-4 Severity: normal Hi, I just noticed this while installing jackd2 in a sid chroot: Setting up jackd2 (1.9.8~dfsg.4+20120529git007cdc37-4) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline /var/lib/dpkg/info/jackd2.postinst: line 15: [: =: unary operator expected # echo $? 0 While there was a debconf prompt earlier I just pressed Ctrl-D ... This error looks like a variable needs to be quoted. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688197: dovecot-managesieved: managesieve segfault in libc
tags 688197 + pending confirmed thanks It's a known bug and it's already fixed in the package git repository. The next upload will contain the fix. Regards, Marco -- Marco Nenciarini mnen...@kcore.it signature.asc Description: This is a digitally signed message part
Bug#688181: xserver-xorg-input-synaptics: FN+F3 won't disable/enable Touchpad
On Wed, Sep 19, 2012 at 20:59:05 -0300, Dr Beco wrote: > KeyPress event, serial 41, synthetic NO, window 0x541, > root 0xaf, subw 0x0, time 5589758, (607,535), root:(609,558), > state 0x0, keycode 199 (keysym 0x1008ffa9, XF86TouchpadToggle), > same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False > > KeyRelease event, serial 41, synthetic NO, window 0x541, > root 0xaf, subw 0x0, time 5589764, (607,535), root:(609,558), > state 0x0, keycode 199 (keysym 0x1008ffa9, XF86TouchpadToggle), > same_screen YES, > XLookupString gives 0 bytes: > XFilterEvent returns: False > So the event gets sent. It's probably up to userspace (ie your desktop environment) to turn that key event into a 'go disable the touchpad' request. Cheers, Julien signature.asc Description: Digital signature
Bug#668354: /etc/rcN.d/[SK]* symlinks are ignored if not mentioned on the /etc/init.d/.depend.* TARGETS
[Teodor MICU] > The bug is that the boot process should not depend on the insserv > internals (/etc/init.d/.depend.*). You have a S/K??service link than > execute it accordingly. Note that the /etc/init.d/.depend.* files are the method used to communicate dependencies between insserv and startpar, which is the tool used to start init.d scripts in parallell. Thus the issue at hand is not really with insserv, but with startpar. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688203: logwatch: http_rc_detail_rep-$code facility broken-as-designed
Package: logwatch Version: 7.4.0+svn20120502rev103-1 Severity: important Hi, /usr/share/logwatch/scripts/services/http wants to read an environment variable "http_rc_detail_rep-$code", but this variable is not passed on through the environment because it doesn’t match the allowed syntax. Changing the hyphen-minus into an underscore makes things work. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static Versions of packages logwatch depends on: ii perl5.14.2-13 ii postfix [mail-transport-agent] 2.9.3-2.1 Versions of packages logwatch recommends: pn libdate-manip-perl Versions of packages logwatch suggests: pn fortune-mod -- 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#688203: logwatch: http_rc_detail_rep-$code facility broken-as-designed
tags 688203 + patch
thanks
Hi,
logwatch-7.4.0+svn20120502rev103/debian/patches/0007-fix-http_rc_detail_rep.patch
attached, “should” fix the issue.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian ManckeDescription: Unbreak and document http_rc_detail_rep
The http_rc_detail_rep facility was never documented and does
not work anyway because it uses a hyphen-minus in an environment
variable which is not allowed syntax in many environments.
Author: Thorsten Glaser
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688203
Last-Update: 2012-09-20
Index: logwatch-7.4.0+svn20120502rev103/conf/services/http.conf
===
--- logwatch-7.4.0+svn20120502rev103.orig/conf/services/http.conf 2011-08-13 11:37:02.0 +0200
+++ logwatch-7.4.0+svn20120502rev103/conf/services/http.conf 2012-09-20 11:04:46.0 +0200
@@ -68,5 +68,13 @@
# To display all user accesses except "Unauthorized":
# $HTTP_USER_DISPLAY = "$field{http_rc} != 401"
+# To raise the needed level of detail for one or more specific
+# error codes to display a summary instead of listing each
+# occurrence, set a variable like the following ones:
+# Raise 403 codes to detail level High
+#$http_rc_detail_rep_403 = 10
+# Always show only summary for 404 codes
+#$http_rc_detail_rep_404 = 20
+
# vi: shiftwidth=3 tabstop=3 et
Index: logwatch-7.4.0+svn20120502rev103/scripts/services/http
===
--- logwatch-7.4.0+svn20120502rev103.orig/scripts/services/http 2012-05-04 20:42:37.0 +0200
+++ logwatch-7.4.0+svn20120502rev103/scripts/services/http 2012-09-20 11:04:47.0 +0200
@@ -735,7 +735,7 @@
if (not defined $StatusCode{$code}) {
$StatusCode{$code} = "\(undefined\)";
}
- if( ($ENV{"http_rc_detail_rep-$code"} || $detail) > $detail ) {
+ if( ($ENV{"http_rc_detail_rep_$code"} || $detail) > $detail ) {
# only display summary for this code
my $t = 0;
my $u = 0;
Bug#688204: jackd2: modifies conffiles (policy 10.7.3): /etc/security/limits.d/audio.conf
Package: jackd2 Version: 1.9.8~dfsg.4+20120529git007cdc37-4 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 1.9.6~dfsg.1-2 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): debsums: missing file /etc/security/limits.d/audio.conf (from jackd2 package) Looking at the maintainer scripts, they already DTRT: initially get the file from /usr/share and delete it in postrm purge (trying both possible names). So just stop shipping the conffile, too. cheers, Andreas PS: Manually running db_purge in postrm is not needed, dh_installdebconf installs exactly the same code snippet. jackd2_1.9.8~dfsg.4+20120529git007cdc37-4.log.gz Description: GNU Zip compressed data
Bug#688205: mono-xsp2: modifies conffiles (policy 10.7.3): /etc/default/mono-xsp2
Package: mono-xsp2 Version: 2.10-2.1 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 mono-xsp2/2.6.5-3 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/mono-xsp2 cheers, Andreas mono-xsp2_2.10-2.1.log.gz Description: GNU Zip compressed data
Bug#687667: lintian: check dpkg version for "-Sextreme" option
Control: tags -1 moreinfo On 2012-09-14 23:22, Hideki Yamane wrote: > Package: lintian > Version: 2.5.10.1 > Severity: normal > > Hi, > > As Bug#677003, package building (dh_builddeb) with "-Sextreme" option > needs newer dpkg version than 1.16.2~ . see http://bugs.debian.org/677003 > > I hope lintian would warn this. > > Hi, Thanks for the suggestion. However, I am inclined to tag this wontfix. Not because the idea is wrong, but because the check will be obsolete the minute the freeze is over. Both Wheezy and Quantal have dpkg/1.16.7 (or newer) now... ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687461: xserver-xorg-video-radeon: HD 6310 video gives only colored snow/black screen
On Mit, 2012-09-19 at 19:09 +0200, Patrice Pillot wrote: > > Last weekend I experienced the same problem as described by original > reporter while installing wheezy on an Asus K53E with an HD6320 (please note > that it is not the same card while probably similar enough according to what > I could read on the internet). > > While during installation (squeeze base system, dist-upgraded to wheezy, > then xorg et al.) the kernel modules were configured so that the radeon > module be loaded (confirmed by lsmod). > > All of the console/CLI only process went fine and, upon wheezy install, I > noticed the usual modeset display changing (thiner fonts, ...) > > Yet, on first X run I got the wrong screen resolution (1024 instead of 1366) > as reported here and I noticed that some vesafb (IIRC) was used with a > message in xorg logs about failing to load radeon module (I don't have the > box at hand to check more precisely, have to wait for this week-end for this). > > I then stopped X and forced the use of the radeon driver by editing > xorg.conf which lead me to the garbage screen on the next X run. > > I then added the radeon.modeset=0 stanza to my grub configuration and this > seemed to make the trick. > > Yet there are still some very annoying (and somehow scary) side effects : Those are all due to your card not being fully supported without KMS (modeset=0). We need to focus on solving the issues with KMS. Please provide logs for the issues described above. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688206: pure-ftpd-common: modifies conffiles (policy 10.7.3): /etc/default/pure-ftpd-common
Package: pure-ftpd-common Version: 1.0.36-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/pure-ftpd-common cheers, Andreas pure-ftpd-common_1.0.36-1.log.gz Description: GNU Zip compressed data
Bug#688195: Missing import of errno in runcmd.py
On Thu, Sep 20, 2012 at 10:28:31AM +0200, Gaudenz Steinlin wrote: > Package: python-cliapp > Version: 1.20120630-1 > Severity: important > Tags: patch > > runcmd.py uses the errno module in line 93 without first importing it. > The patch below adds the missing import. Already fixed upstream. > I can also prepare an upload if you don't have the time to fix the issue > at the moment. I hope to get my Debian package building workflow working again this weekend, and soon after that there'll be a new cliapp in unstable. -- I wrote a book: http://gtdfh.branchable.com/ signature.asc Description: Digital signature
Bug#688179: libvirt: Please enable selinux security driver
Le Thu, 20 Sep 2012 07:30:01 +0200, Guido Günther a écrit : > Hi Laurent, Hey, > > Somebody with interest in SELinux would need to fix up the necessary > policies (as you noted). Are you in any way interested to do this? I'd > be happy to do so but I'm lacking the time for any serioius Debian > work at the moment. Yeah, I'm already more or less busy with this :) I'm trying to get the specific debian patches we have merged upstream when they are relevant. On my laptop I have libvirt starting with the selinux security driver enabled and the git HEAD of the refpolicy. KVM seems started in the right context and the right category, but virt-manager is not showing me that the selinux security driver is being used (only showing me DAC). So I guess everything is not perfect yet. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683360: [Pkg-xfce-devel] Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
How is this not fixed yet? It means xfce 4.10 cannot be installed, and thus cannot receive proper testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688208: libxalan2-java: Ensure backwards compatible bytecode is built
Package: libxalan2-java Version: 2.7.1-7 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu quantal ubuntu-patch openjdk-7-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Ensure backwards compatible bytecode is build (LP: #1049794): - d/ant.properties: Specify source/target = 1.5 when compiling Java source code. Thanks for considering the patch. - -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-15-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQWuvhAAoJEL/srsug59jDbhAQAI+YsANBwwR9fm+2jbrJuQ1j ydZ/P4ALmMgYL/cAA4eTdwYo6Zq9YDrxRNmd1yl/BxPKGzpoHIrqiIGkC20qFBri oM4+W90OMb4BaIQUytnt2+mAOrSuqS0KhUAFMIgZe3gCC3FQ0kTVeyBerFfO6nPU r+h6XWsUU5eKSMEH1ytkaxw8jo9R4kATkvucMj9BkxHLXOpDqGTFJjUoXGRYxTAk vYJP5lEvIjWzjL0R9UTBHwg47Q8HIRDl92AzBGKunWqK0A3kW/34ZOcdFjKH4gNB eddL84rQoXEQcquikFtdzXfQcjQ7we/X1sozJtjIpiOSfz3iNc+e8hrrpYKOsHX2 D+5KPsDbZ8Keffe/TWyGcEpA4PMDjFo5OzIUTxXIvz7ExTkEU/CSNPp17P3w0/7A AH45vzs39wWMC3ki659apBXHq8crNpJod1yfALW5TB7s0okdndlenmpQV+5hrDxz ifLwS39jRcSA/p8qnv18PYvroXqEGk/RSPLCu5wXpSyysR1ZsBg8b/Rxa8G9Kkhp mBhonRpeJ0KG2DZO+qolbPezFuzfWTZE8gt7QESyxqU49fGn4HSfc0j/z8YZS4kF aIz2f8vTuGzjWFhn8POEDqs5hxYItnlhkBlj+pseCm9a8+t/krDCpG2Yu7GTmzYO iBa2jewp16a8dNvhtuac =eS9I -END PGP SIGNATURE- diff -Nru libxalan2-java-2.7.1/debian/ant.properties libxalan2-java-2.7.1/debian/ant.properties --- libxalan2-java-2.7.1/debian/ant.properties 2008-01-03 19:41:09.0 + +++ libxalan2-java-2.7.1/debian/ant.properties 2012-09-20 10:47:22.0 +0100 @@ -7,3 +7,7 @@ runtime.jar=/usr/share/java/cup.jar regexp.jar=/usr/share/java/regexp.jar build.boot.class.path=/usr/share/java/jaxp-1.3.jar +# Ensure that source and target are 1.5 +# For backwards compat on Java 7 +ant.build.javac.source=1.5 +ant.build.javac.target=1.5 diff -Nru libxalan2-java-2.7.1/debian/changelog libxalan2-java-2.7.1/debian/changelog
Bug#680822: aptitude install libphonon-dev phonon-backend-gstreamer fails
On Thursday 20 September 2012 05:36:56 Hideki Yamane wrote: > Hi, > > It seems that clear for me, "phonon-backend-null | phonon" is odd and it > should be "phonon-backend-null | phonon-backend" since phonon-backend-null > provides phonon-backend virtual package and pulls phonon package causes > just a confuse. > > I'll upload package include this change with 10days/delayed (safe side). > If you want to cancel it, please tell me. please cancel it. The dependency on phonon *is* correct. Either you want phonon-backend-null *or* a working phonon. Phonon is the package to depend on to get a working phonon. if you want a working phonon, you must depend on phonon. The bug is not in the phonon package. /Sune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687942: fprobe-ulog: modifies conffiles (policy 10.7.3): /etc/default/fprobe-ulog
Package: fprobe-ulog Followup-For: Bug #687942 [resending with the new bug template which contains more hints] Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/fprobe-ulog cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687943: gnarwl: modifies conffiles (policy 10.7.3): /etc/gnarwl.cfg
Package: gnarwl Followup-For: Bug #687943 [Resending with the new bug template that contains more information.] Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/gnarwl.cfg cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687944: mason: modifies conffiles (policy 10.7.3): /etc/masonrc
Package: mason Followup-For: Bug #687944 [resending with the updated bug template that contains more hints] Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/masonrc cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688209: open-iscsi: invalid usage of "break" statement in init script
Package: open-iscsi Version: 2.0.873-3 Severity: normal The "break" statement in /etc/init.d/open-iscsi is misplaced as it is used inside an 'if' statement inside a function: | # Now let's mount | log_daemon_msg "Mounting network filesystems" | MOUNT_RESULT=1 | if mount -a -O _netdev >/dev/null 2>&1; then | MOUNT_RESULT=0 | break | fi | log_end_msg $MOUNT_RESULT Which results in: | /etc/init.d/open-iscsi: line 129: break: only meaningful in a `for', `while', or `until' loop Maybe it's worth using something like: | # Now let's mount | log_daemon_msg "Mounting network filesystems" | mount -a -O _netdev >/dev/null 2>&1 | log_end_msg $? instead? regards, -mika- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012-09-20t12-28...@devnull.michael-prokop.at
Bug#561970: libdate-manip-perl: cannot be used in taint (-T) mode
Control: found 561970 libdate-manip-perl/6.32-1
Control: notfound 561970 libdate-manip-perl/6.34-1
Thanks for pinging me on this issue.
On Wed, Sep 19, 2012 at 06:34:27PM +0200, gregor herrmann wrote:
> On Thu, 12 Apr 2012 17:05:27 +0200, Helmut Grohne wrote:
>
> > $ perl -T -e 'use Date::Manip; print Date::Manip::ParseDateString("10:20");'
> > Undefined subroutine &Date::Manip::ParseDateString called at -e line 1,
> > line 429.
> > $ perl -e 'use Date::Manip; print Date::Manip::ParseDateString("10:20");'
> > 2012041210:20:00$
>
> Works for me (with 6.32-1):
>
> % perl -T -e 'use Date::Manip; print Date::Manip::ParseDateString("10:20");'
> 2012091910:20:00
> % perl -e 'use Date::Manip; print Date::Manip::ParseDateString("10:20");'
> 2012091910:20:00
Interesting. For me 6.32-1 is still broken. However I cannot reproduce
it with 6.34-1. I really have no clue what could make up the difference
between our 6.32 versions.
> > This issue shows up with munin as entries in /var/log/apache2/error.log:
> >
> > [Thu Apr 12 15:56:01 2012] munin-cgi-graph: Undefined subroutine
> > &Date::Manip::ParseDateString called at /usr/lib/cgi-bin/munin-cgi-graph
> > line 407.
>
> And I also don't have entries like this (hm, maybe because I'm not
> using the cgi version in munin).
>
> Can somebody reproduce the bug?
Probably not. Or at least anyone who can, can reproduce the oneliner as
well.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688210: condor: Multiple security issues
Package: condor Severity: grave Tags: security Justification: user security hole Please see here for details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3490 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3491 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3492 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3493 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688177: [Pkg-libvirt-maintainers] Bug#688177: libvirt: Please enable audit feature
Le Thu, 20 Sep 2012 07:26:29 +0200, Guido Günther a écrit : > Did you test libvirt with audit support enabled? Yes I've it running on my machine. I've just tested without auditd daemon running and it still working, the only thing you get is extra logging in dmesg about vm being started and stopped. Maybe libvirt-bin package could also suggest/recommends auditd package? Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#321447: xbase-clients: Insecure usage of temporary files in x11perfcomp and other security issues
Package: x11-apps Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.6) - use target "stable" Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. I will happily assist you at any stage if the patch is straightforward and you need help. Please keep me in CC at all times so I can track [1] the progress of this request. For details of this process and the rationale, please see the original announcement [2] and my blog post [3]. 0: debian-rele...@lists.debian.org 1: http://prsc.debian.net/tracker/321447/ 2: <201101232332.11736.th...@debian.org> 3: http://deb.li/prsc Thanks, with his security hat on: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688212: fonts-inconsolata: Please update Inconsolata to version 1.011
Package: fonts-inconsolata Version: 001.010-4 Severity: normal Hi, I've noticed that in a few cases rxvt-unicode has problems with font fallback for some unicode characters with Inconsolata 1.010. You can reproduce the problem as follows: 1. open a terminal and run "urxvt -fn xft:inconsolata:medium:size=12" 2. execute: LANG="en_US.utf8" man groff | less -p bug-groff Have a look at the borked characters surrounding email-addresses and urls. With Inconsolata 1.011 everything seems to be fine. I'm running rxvt-unicode-256color (version 9.15) and my .fonts.conf looks like this: Inconsolata true true true hintslight none cheers, erik -- Package-specific info: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===--- ii fontconfig 2.9.0-7 amd64generic font configuration library - support binarie ii libfreetype6:amd64 2.4.9-1 amd64FreeType 2 font engine, shared library files ii libxft2:amd64 2.3.1-1 amd64FreeType-based font drawing library for X -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#687667: lintian: check dpkg version for "-Sextreme" option
Hi, On Thu, 20 Sep 2012 11:26:30 +0200 Niels Thykier wrote: > > As Bug#677003, package building (dh_builddeb) with "-Sextreme" option > > needs newer dpkg version than 1.16.2~ . see http://bugs.debian.org/677003 > > > > I hope lintian would warn this. > However, I am inclined to tag this wontfix. Not because the idea is > wrong, but because the check will be obsolete the minute the freeze is > over. Both Wheezy and Quantal have dpkg/1.16.7 (or newer) now... Well, "backport" issue still exists, it's rare but for example, Ubuntu8.04 is still alive until 2013, Ubuntu10.04 is until 2015 too. However, it's okay to tag this wontfix since it's reasonable. -- 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#688169: lowpan-tools: Please port to libnl-3.x
Source: lowpan-tools Followup-For: Bug #688169 I have released (the long-awaiten) lowpan-tools 0.3. An updated packages are uploaded the mentors.debian.net. Luca, could you please check those packages and possibly sponsor them into unstable. I understand that testing is currently frozen, but I would like to have fresh package with no oldlibs dependencies at least inside unstable. -- With best wishes Dmitry -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680822: aptitude install libphonon-dev phonon-backend-gstreamer fails
Hi, On Thu, 20 Sep 2012 12:13:22 +0200 Sune Vuorela wrote: > please cancel it. Okay, canceled. Thanks. > The dependency on phonon *is* correct. Either you want phonon-backend-null > *or* a working phonon. Phonon is the package to depend on to get a working > phonon. > > if you want a working phonon, you must depend on phonon. Hmm, just a question. phonon package contains no files $ dpkg -L phonon /. /usr /usr/share /usr/share/doc /usr/share/doc/phonon /usr/share/doc/phonon/copyright /usr/share/doc/phonon/changelog.Debian.gz and just has a dependency for some packages. $ dpkg -s phonon Package: phonon (snip) Version: 4:4.6.0.0-2 Depends: libphonon4 (>= 4:4.6.0.0-2), debconf (>= 0.5) | debconf-2.0, phonon-backend-vlc | phonon-backend Well, if above dependency would be filled, it seems that specify phonon-backend will be appropriate option and it is. Why we need to specify phonon as Depends:? -- 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#688213: fontforge: Why "--with-freetype-bytecode" only in Ubuntu?
Package: fontforge Version: 0.0.20120101+git-2 Severity: minor Hi, I wonder why the fontforge build is configured "--with-freetype-bytecode" only for Ubuntu. It seems this was introduced on purpose in GIT commit 84e75ad "Updated to version 0.0.20080828." but it is nowhere documented why only Ubuntu should get the bytecode interpreter but not Debian. Please consider enabling this option for Debian as well, escpecially since the bytecode interpreter has been enabled by default by freetype upstream since version 2.4. - Fabian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (901, 'testing'), (501, 'unstable'), (401, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fontforge depends on: ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libfontconfig12.9.0-7 ii libfontforge1 0.0.20120101+git-2 ii libfreetype6 2.4.9-1 ii libgdraw4 0.0.20120101+git-2 ii libgif4 4.1.6-9.1 ii libglib2.0-0 2.32.3-1 ii libice6 2:1.0.8-2 ii libjpeg8 8d-1 ii libpango1.0-0 1.30.0-1 ii libpng12-01.2.49-1 ii libpython2.7 2.7.3~rc2-2.1 ii libsm62:1.2.1-2 ii libspiro0 20071029-2 ii libtiff4 3.9.6-7 ii libuninameslist0 0.0.20091231-1.1 ii libx11-6 2:1.5.0-1 ii libxft2 2.3.1-1 ii libxml2 2.8.0+dfsg1-5 ii zlib1g1:1.2.7.dfsg-13 fontforge recommends no packages. Versions of packages fontforge suggests: pn autotrace pn fontforge-doc pn fontforge-extras pn potrace pn python-fontforge -- 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#576611: konqueror handles backward navigation within a document unconfortably
Hi, This bug is rather old, so could you please confirm the behaviour with the testing version of KDE (4.8.4) ? On my PC it just behaves as you would like (the position is keeping when I go back to the first page). Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680822: aptitude install libphonon-dev phonon-backend-gstreamer fails
On Thursday 20 September 2012 13:47:17 Hideki Yamane wrote: > Why we need to specify phonon as Depends:? if you want a working phonon, you need to depend on phonon. that's just how it is. /Sune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#595721: konqueror: does not connect to secure websites using https
Hi, The bug is a bit old, so could you please confirm the behaviour is still present with the testing version of KDE (4.8.4) ? On my PC I can reach the page without SSL error. I just got a warning about the insecure certificate, but it is normal. Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688160: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688158: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688161: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688162: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688164: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688163: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688165: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688167: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688166: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688170: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688169: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688171: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688168: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688172: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688173: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688174: libnl1 removal not targetted at wheezy
Hi, since this question came up, I wanted to clarify that removing libnl1 is not a release goal for wheezy and wheezy will definitely ship with libnl1! Unstable is currently frozen in preparation for wheezy. I don't consider updating to libnl-3.x as important enough which would warrant a freeze exception by the release team. So please wait with such an upload to unstable until jessie is open for development. An upload to experimental while wheezy is frozen would be appreciated though. I'm sorry if this caused any confusion. I just wanted to give you an early heads-up. My plan is to remove libnl1 early during the jessie release cycle. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659012: Segfaults shortly after start
Package: powertop
Version: 1.11-1
Severity: normal
Problem persists.
screen output:
-
PowerTOP version 1.11 (C) 2007 Intel Corporation
CnAvg residency P-states (frequencies)
C0 (cpu running)( 0.5%) 1.60 Ghz 0.2%
polling 0.0ms ( 0.0%) 1333 Mhz 0.0%
C1 mwait 3.1ms ( 0.0%) 1067 Mhz 0.2%
C2 mwait 8.1ms ( 1.3%) 800 Mhz99.6%
C4 mwait 6.0ms (98.2%)
Wakeups-from-idle per second : 166.3interval: 5.0s
no ACPI power usage estimate available
Top causes for wakeups:
35.8% ( 31.4): uhci_hcd:usb3
35.8% ( 31.4) USB device 3-2 : USB-Ampel (Cleware GmbH)
9.1% ( 8.0) swapper/0 : mod_timer (rh_timer_func)
4.8% ( 4.2) swapper/0 : hrtimer_start (tick_sched_timer)
4.6% ( 4.0) swapper/0 : hrtimer_start_range_ns (tick_sched_timer)
2.3% ( 2.0) nrpe : hrtimer_start_range_ns (hrtimer_wakeup)
2.1% ( 1.8): eth0
2.1% ( 1.8) swapper/1 : hrtimer_start_range_ns (tick_sched_timer)
1.1% ( 1.0) ntpd : hrtimer_start_range_ns (posix_timer_fn)
1.1% ( 1.0) tincd : hrtimer_start_range_ns (hrtimer_wakeup)
0.5% ( 0.4) swapper/1 : hrtimer_start (tick_sched_timer)
0.2% ( 0.2)kerneloops : hrtimer_start_range_ns (hrtimer_wakeup)
0.2% ( 0.2) swapper/0 : mod_timer (dev_watchdog)
0.2% ( 0.2) init : hrtimer_start_range_ns (hrtimer_wakeup)
Segmentation fault
root@ieieie:~#
strace:
--
write(1, "\33[1BTop causes for wakeups:\r\33[1B"..., 1340) = 1340
rt_sigaction(SIGTSTP, {0xb76ad810, [], SA_RESTART}, NULL, 8) = 0
access("/proc/config.gz", R_OK) = -1 ENOENT (No such file or directory)
open("/proc/sys/kernel/osrelease", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb76e5000
read(3, "3.2.0-3-686-pae\n", 1024) = 16
close(3)= 0
munmap(0xb76e5000, 4096)= 0
open("/boot/config-3.2.0-3-686-pae", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=134558, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb76e5000
read(3, "#\n# Automatically generated file"..., 1024) = 1024
...
read(3, "ND_IPOIB=m\nCONFIG_INFINIBAND_IPO"..., 1024) = 1024
read(3, "V_DS3232 is not set\nCONFIG_RTC_D"..., 1024) = 1024
read(3, "01=m\nCONFIG_RTC_DRV_V3020=m\nCONF"..., 1024) = 1024
read(3, "NG=y\nCONFIG_ET131X=m\n# CONFIG_SL"..., 1024) = 1024
read(3, "DT282X=m\nCONFIG_COMEDI_DMM32AT=m"..., 1024) = 1024
read(3, "CI9111=m\nCONFIG_COMEDI_ADL_PCI91"..., 1024) = 1024
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages powertop depends on:
ii libc6 2.13-35Embedded GNU C Library: Shared lib
ii libncursesw5 5.7+20100313-5 shared libraries for terminal hand
powertop recommends no packages.
Versions of packages powertop suggests:
ii cpufrequtils 007-1 utilities to deal with the cpufreq
pn laptop-mode-tools (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#688166: closed by Joachim Breitner (Bug#688166: fixed in libnss-gw-name 0.3-1)
Hi Joachim, that was super-quick! Thanks! 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#688214: linux-image-3.2.0-3-rt-amd64: please add detection for device 0b05:179d in rt2800usb
Package: src:linux Version: 3.2.23-1 Severity: normal The module rt2800usb didn't get loaded when I plugged in my Asus USB-N53 wifi dongle. Also loading it manually with modbrobe didn't help. I had to set the option "rt2800usb - Include support for unknown (USB) devices (RT2800USB_UNKNOWN)" in the kernel to get it working. You'll find information from lsusb -v below. I wasn't sure if I had to report this against the kernel package or somewhere else, sorry if it's in the wrong place. Thanks, Sylvain ** lsusb -v output: Bus 002 Device 005: ID 0b05:179d ASUSTek Computer, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0b05 ASUSTek Computer, Inc. idProduct 0x179d bcdDevice1.01 iManufacturer 1 Ralink iProduct2 802.11 n WLAN iSerial 3 1.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 450mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 7 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 1.0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) -- Package-specific info: ** Version: Linux version 3.2.0-3-rt-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-3-rt-amd64 root=/dev/mapp
Bug#688158: unused Build-Depends on obsolete libnl-dev
tags 688158 + patch thanks trivial patch attached -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/debian/control b/debian/control index b78effd..38e5ade 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: optional Maintainer: Carlos Alberto Lopez Perez Homepage: http://www.aircrack-ng.org/ Build-Depends: debhelper (>= 8.0.0), libpcap0.8-dev, libgcrypt11-dev, - libsqlite3-dev (>= 3.4), libnl-dev (>= 1.1) [linux-any], zlib1g-dev, + libsqlite3-dev (>= 3.4), zlib1g-dev, python (>= 2.6.6-3~), hardening-includes Standards-Version: 3.9.3 signature.asc Description: OpenPGP digital signature
Bug#688160: unused Build-Depends on obsolete libnl-dev
tags 688160 + patch thanks trivial patch attached -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/debian/control b/debian/control index 9077a07..11c12bd 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,6 @@ Build-Depends: debhelper (>= 8.1.3), cdbs (>= 0.4.97), quilt, libglib2.0-dev (>= 2.16), libgstreamer0.10-dev (>= 0.10.30), libgstreamer-plugins-base0.10-dev (>= 0.10.30), - libnl-dev, libsndfile1-dev, libusb-dev, libcap-ng-dev, signature.asc Description: OpenPGP digital signature
Bug#664789: [Pkg-fonts-devel] Bug#664789: [Fontforge-devel] Segmentation Fault after Hitting 'a' as Test Pattern in the Kerning Metrics Window
Am 20.03.2012 22:27, schrieb Daniel Kahn Gillmor: Steps to repeat: From the menu, choose Window > New Metrics Window In the field with the text to display, type any character and then the Tab key (or press the tab key and then any other character). I was also able to reproduce this. The backtrace i get during the crash is: #0 u_strncmp (str1=0x0, str2=0x87f6b90, n=0) at ustring.c:97 #1 0xb7baeb12 in GListField_NameCompletion (t=0x87f6930, from_tab=1) at gtextfield.c:3150 The problem seems to be that GListField_NameCompletion() dereferences ti[i]->text, which might be NULL. I have, however, no idea why this is so. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688163: ipvsadm: Please port to libnl-3.x
tags 688163 + patch
thanks
Hi Alexander,
I've attached the full debdiff from the Ubuntu 1.26-1ubuntu1 version and
also the patch itself.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
#! /bin/sh /usr/share/dpatch/dpatch-run
## 99_ubuntu_libnl-3-linking.dpatch by Andres Rodriguez
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
@DPATCH@
diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch'
'--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' ipvsadm-1.26~/Makefile
ipvsadm-1.26/Makefile
--- ipvsadm-1.26~/Makefile 2012-05-31 18:22:39.0 -0400
+++ ipvsadm-1.26/Makefile 2012-05-31 18:22:39.0 -0400
@@ -82,7 +82,8 @@
OBJS = ipvsadm.o config_stream.o dynamic_array.o
LIBS = $(POPT_LIB)
ifneq (0,$(HAVE_NL))
-LIBS += -lnl
+INCLUDE+= $(shell pkg-config --cflags libnl-3.0 libnl-genl-3.0)
+LIBS += $(shell pkg-config --libs libnl-3.0 libnl-genl-3.0)
endif
DEFINES= -DVERSION=\"$(VERSION)\"
-DSCHEDULERS=\"$(SCHEDULERS)\" \
-DPE_LIST=\"$(PE_LIST)\" $(POPT_DEFINE)
diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch'
'--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr'
ipvsadm-1.26~/libipvs/Makefile ipvsadm-1.26/libipvs/Makefile
--- ipvsadm-1.26~/libipvs/Makefile 2008-09-21 06:02:03.0 -0400
+++ ipvsadm-1.26/libipvs/Makefile 2012-05-31 18:22:39.0 -0400
@@ -4,6 +4,7 @@
CFLAGS = -Wall -Wunused -Wstrict-prototypes -g -fPIC
ifneq (0,$(HAVE_NL))
CFLAGS += -DLIBIPVS_USE_NL
+INCLUDE += $(shell pkg-config --cflags libnl-3.0 libnl-genl-3.0)
endif
INCLUDE+= $(shell if [ -f ../../ip_vs.h ]; then\
diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch'
'--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr'
ipvsadm-1.26~/libipvs/libipvs.c ipvsadm-1.26/libipvs/libipvs.c
--- ipvsadm-1.26~/libipvs/libipvs.c 2011-02-06 21:38:57.0 -0500
+++ ipvsadm-1.26/libipvs/libipvs.c 2012-05-31 18:24:11.176032999 -0400
@@ -32,7 +32,7 @@
struct ip_vs_getinfo ipvs_info;
#ifdef LIBIPVS_USE_NL
-static struct nl_handle *sock = NULL;
+static struct nl_sock *sock = NULL;
static int family, try_nl = 1;
#endif
@@ -73,7 +73,7 @@
{
int err = EINVAL;
- sock = nl_handle_alloc();
+ sock = nl_socket_alloc();
if (!sock) {
nlmsg_free(msg);
return -1;
@@ -88,7 +88,7 @@
/* To test connections and set the family */
if (msg == NULL) {
- nl_handle_destroy(sock);
+ nl_socket_free(sock);
sock = NULL;
return 0;
}
@@ -104,12 +104,12 @@
nlmsg_free(msg);
- nl_handle_destroy(sock);
+ nl_socket_free(sock);
return 0;
fail_genl:
- nl_handle_destroy(sock);
+ nl_socket_free(sock);
sock = NULL;
nlmsg_free(msg);
errno = err;
diff -u ipvsadm-1.26/debian/changelog ipvsadm-1.26/debian/changelog
--- ipvsadm-1.26/debian/changelog
+++ ipvsadm-1.26/debian/changelog
@@ -1,3 +1,15 @@
+ipvsadm (1:1.26-1ubuntu1) quantal; urgency=low
+
+ * Merge from Debian testing (LP: #1007160). Remaining changes:
+- Build-depend on pkg-config.
+- Port to libnl3.
+ + debian/control: update Build-Depends libnl3-dev -> libnl-3-dev,
+libnl-genl-3-dev.
+ * debian/patches/99_ubuntu_libnl-3-linking.dpatch: Convert quilt patch
+'libnl-3-linking.patch' to dpatch.
+
+ -- Andres Rodriguez Thu, 31 May 2012 18:05:42 -0400
+
ipvsadm (1:1.26-1) unstable; urgency=low
* [084f2b6] Imported Upstream version 1.26
@@ -16,6 +28,55 @@
-- Alexander Wirt Wed, 22 Feb 2012 22:03:47 +0100
+ipvsadm (1:1.25.clean-1ubuntu5) precise; urgency=low
+
+ * debian/control: update Build-Depends: libnl3-dev -> libnl-3-dev,
+libnl-genl-3-dev.
+ * debian/patches/libnl-3-linking.patch: fix linking (and cflags) to properly
+build against libnl3 now that the modules are split.
+
+ -- Mathieu Trudel-Lapierre Wed, 21 Dec 2011 15:26:24 -0500
+
+ipvsadm (1:1.25.clean-1ubuntu4) precise; urgency=low
+
+ * Makefile: test for poptGetContext by piping some test C code using
+poptGetContext to $(CC) -include popt.h rather than searching for
+libpopt.a in a set of hardcoded directories as that didn't work with
+multiarch anymore and caused the package to FTBFS.
+
+ -- Loïc Minier Thu, 01 Dec 2011 17:21:44 +0100
+
+ipvsadm (1:1.25.clean-1ubuntu3) oneiric; urgency=low
+
+ * Build-depend on pkg-config.
+
+ -- Colin Watson Tue, 09 Aug 2011 14:16:09 +0100
+
+ipvsadm (1:1.25.clean-1ubuntu2) oneiric; urgency=low
+
+ * Port to libnl3.
+
+ -- Colin Watson Mon, 08 Aug 2011 17:23:22 +0100
+
+ipvsadm (1:1.25.clean-1ubuntu1) natty; urgency=low
+
+ * libipvs/libipvs.c: upstrea
Bug#688011: fcitx-m17n : no pinyin input window
Hi, I would like suggest you to use another input method engine if you'd like to input Chinese, for example fcitx-libpinyin and fcitx-sunpinyin, that will improve your experience significantly. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688164: keepalived: Please port to libnl-3.x
tags 688164 + patch thanks Hi Alexander, the Ubuntu package has a patch for this issue. I've attached the full debdiff and the patch itself. The patch seems to also work with the experimental version of keepalived. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff -u keepalived-1.2.2/debian/init.d keepalived-1.2.2/debian/init.d --- keepalived-1.2.2/debian/init.d +++ keepalived-1.2.2/debian/init.d @@ -9,7 +9,7 @@ # Required-Start:$syslog $network $remote_fs # Required-Stop: $syslog $network $remote_fs # Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 +# Default-Stop: 1 # Short-Description: Starts keepalived # Description: Starts keepalived lvs loadbalancer ### END INIT INFO diff -u keepalived-1.2.2/debian/changelog keepalived-1.2.2/debian/changelog --- keepalived-1.2.2/debian/changelog +++ keepalived-1.2.2/debian/changelog @@ -1,9 +1,35 @@ +keepalived (1:1.2.2-3ubuntu1) precise; urgency=low + + * Merge with Debian unstable. Remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := explicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links +- Build with libnl3, thanks to a patch from Marc - A. Dahlhaus. + * debian/control: in Build-Depends: libnl3-dev -> libnl-3-dev, +libnl-genl-3-dev. + * debian/patches/ubuntu_libnl3.patch: update patch, make sure it works for +libnl3 3.2.x. + + -- Mathieu Trudel-Lapierre Fri, 23 Dec 2011 09:18:50 -0500 + keepalived (1:1.2.2-3) unstable; urgency=low * [c28d5f0] Readd ip_vs.h - this reenables ipvs (Closes: #649778) -- Alexander Wirt Sun, 18 Dec 2011 16:18:06 +0100 +keepalived (1:1.2.2-2ubuntu1) precise; urgency=low + + * Resynchronise with Debian. Remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := explicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links +- Build with libnl3, thanks to a patch from Marc - A. Dahlhaus. + + -- Colin Watson Mon, 28 Nov 2011 15:48:05 + + keepalived (1:1.2.2-2) unstable; urgency=low * [9db4134] Fix override disparity @@ -18,6 +44,17 @@ -- Alexander Wirt Thu, 10 Nov 2011 08:38:47 +0100 +keepalived (1:1.2.2-1ubuntu1) precise; urgency=low + + * Resynchronise with Debian. Remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := explicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links + * Build with libnl3, thanks to a patch from Marc - A. Dahlhaus. + + -- Colin Watson Tue, 25 Oct 2011 16:10:58 +0100 + keepalived (1:1.2.2-1) unstable; urgency=low * New upstream version @@ -27,6 +64,22 @@ -- Alexander Wirt Sun, 06 Mar 2011 17:43:35 +0100 +keepalived (1:1.1.20-1ubuntu2) oneiric; urgency=low + + * Rebuild for OpenSSL 1.0.0. + + -- Colin Watson Tue, 17 May 2011 11:32:05 +0100 + +keepalived (1:1.1.20-1ubuntu1) natty; urgency=low + + * Merge from debian unstable (LP: #668818), remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := expicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links + + -- Lorenzo De Liso Sat, 30 Oct 2010 20:01:07 +0200 + keepalived (1:1.1.20-1) unstable; urgency=low * Go back to 1.1.20 since 1.2.0 is not ready for release @@ -61,6 +114,16 @@ -- Alexander Wirt Fri, 23 Apr 2010 13:17:53 +0200 +keepalived (1.1.17-2ubuntu1) lucid; urgency=low + + * Merge from debian testing (LP: #519940), remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := expicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links + + -- Andres Rodriguez Wed, 10 Feb 2010 13:35:16 -0500 + keepalived (1.1.17-2) unstable; urgency=low * Reenable ipvs support thanks to Vincent Bernat for the hint @@ -68,6 +131,16 @@ -- Alexander Wirt Thu, 28 May 2009 09:55:52 +0200 +keepalived (1.1.17-1ubuntu1) karmic; urgency=low + + * Merge from debian unstable, remaining changes: +- debian/rules: DEB_UPDATE_RCD_PARAMS := expicit init start/stop + parameters (don't stop at 0 and 6) +- debian/init.d: init script header adapted to stop rule +- debian/keepalived.postinst: Remove shutdown and reboot links + + -- Didier Roche Tue, 12 May 2009 20:26:15 +0200 + keepalived (1.1.17-1) unstable; urgency=low * New upstream release (Closes: #516102). @@ -80,6 +153,24 @@ -- Alexander Wirt Sun, 26 Apr 2009 19:41:12
Bug#680433: check with upstream
Hi gonna contact upstream author to see if they can autodetect (with correct configure etc...) Olivier -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688216: xen-utils-4.2: xl does not work
Package: xen-utils-4.2 Version: 4.2.0-1 Severity: normal Hello, xl is supposed to be current tool for managing virtual machines on xen (in absence of any working GUI for that in Debian). However, xl produces this: # xl list ERROR: A different toolstack (xm) have been selected! There is no info in README.Debian I could find how to cahnge this selection. Reportedly both xl and xm work flawlessly on RedHat. Running the rc3 hypervisor atm. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (111, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xen-utils-4.2 depends on: ii e2fslibs 1.42.5-1 ii libc6 2.13-35 ii libncurses5 5.9-10 ii libtinfo5 5.9-10 ii libuuid1 2.20.1-5.1 ii libxen-4.24.2.0-1 ii libxenstore3.04.2.0-1 ii libyajl2 2.0.4-2 ii python2.7.3~rc2-1 ii python2.7 2.7.3~rc2-2.1 ii xen-utils-common 4.2.0-1 Versions of packages xen-utils-4.2 recommends: ii bridge-utils 1.5-4 ii qemu-keymaps 1.1.0+dfsg-1 ii qemu-utils 1.1.0+dfsg-1 ii xen-hypervisor-4.2-amd64 [xen-hypervisor-4.2] 4.2.0-1 Versions of packages xen-utils-4.2 suggests: pn xen-docs-4.2 -- 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#688173: Reported to upstream
Reported to upstream. David is on PTO till Oct-11. He will address it after this date. As Fedora is his primary platform, he asked me to file Fedora BZ: https://bugzilla.redhat.com/show_bug.cgi?id=859042 Mirek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688173: Reported to upstream
forwarded 688173 https://bugzilla.redhat.com/show_bug.cgi?id=859042 thanks On 20.09.2012 14:56, Miroslav Suchý wrote: > Reported to upstream. David is on PTO till Oct-11. He will address it > after this date. Thanks, marking the issue as forwarded upstream. Cheers, 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#688217: Failure to create username with UTF-8 symbol
Package: wiki.debian.org Severity: important Tried to create a new user account with a UTF-8 character (e.g. Flürble). This failed. Log excerpt: mod_wsgi (pid=29720): Exception occurred processing WSGI script '/srv/wiki.debian.org/bin/moin.wsgi'. Traceback (most recent call last): File "/usr/lib/pymodules/python2.5/werkzeug/wsgi.py", line 406, in __call__ return self.app(environ, start_response) File "/usr/lib/pymodules/python2.5/MoinMoin/wsgiapp.py", line 282, in __call__ response = run(context) File "/usr/lib/pymodules/python2.5/MoinMoin/wsgiapp.py", line 88, in run response = dispatch(request, context, action_name) File "/usr/lib/pymodules/python2.5/MoinMoin/wsgiapp.py", line 136, in dispatch response = handle_action(context, pagename, action_name) File "/usr/lib/pymodules/python2.5/MoinMoin/wsgiapp.py", line 195, in handle_action handler(context.page.page_name, context) File "/usr/lib/pymodules/python2.5/MoinMoin/action/newaccount.py", line 256, in execute request.theme.add_msg(_create_user(request), "dialog") File "/usr/lib/pymodules/python2.5/MoinMoin/action/newaccount.py", line 140, in _create_user theuser.account_creation_host], shell=False, stdin=None, stdout=subprocess.PIPE, stderr=subprocess.PIPE) File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/lib/python2.5/subprocess.py", line 1153, in _execute_child raise child_exception TypeError: execv() arg 2 must contain only strings Looks like a bug in the interface to account creation checking. Sigh. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688218: unblock: busybox/1:1.20.0-7
(m->flags & MODULE_FLAG_FOUND_IN_MODDEP)) {
+ if (!(option_mask32 & INSMOD_OPT_SILENT))
+- bb_error_msg("module %s not found in modules.dep",
+- humanly_readable_name(m));
++ bb_error_msg((m->flags & MODULE_FLAG_BUILTIN) ?
++ "module %s is builtin" :
++ "module %s not found in modules.dep",
++ humanly_readable_name(m));
+ return -ENOENT;
+ }
+ DBG("do_modprob'ing %s", m->modname);
+@@ -595,6 +598,11 @@ int modprobe_main(int argc UNUSED_PARAM,
+ while (config_read(parser, &s, 1, 1, "# \t", PARSE_NORMAL &
~PARSE_GREEDY))
+ get_or_add_modentry(s)->flags |= MODULE_FLAG_LOADED;
+ config_close(parser);
++
++ parser = config_open2("modules.builtin", fopen_for_read);
++ while (config_read(parser, &s, 1, 1, "# \t", PARSE_NORMAL))
++ get_or_add_modentry(s)->flags |= MODULE_FLAG_BUILTIN;
++ config_close(parser);
+ }
+
+ if (opt & (OPT_INSERT_ALL | OPT_REMOVE)) {
diff -Nru busybox-1.20.0/debian/patches/series
busybox-1.20.0/debian/patches/series
--- busybox-1.20.0/debian/patches/series2012-07-22 11:59:35.0
+0400
+++ busybox-1.20.0/debian/patches/series2012-09-20 00:58:00.0
+0400
@@ -19,5 +19,9 @@
u-mount-FreeBSD-support.patch
swaponoff-FreeBSD-support.patch
+modprobe-read-modules-builtin.patch
+
# http://bugs.debian.org/681760
dont-force-no-alignment-for-s390.patch
+
+stop-checking-ancient-kernel-version.patch
diff -Nru
busybox-1.20.0/debian/patches/stop-checking-ancient-kernel-version.patch
busybox-1.20.0/debian/patches/stop-checking-ancient-kernel-version.patch
--- busybox-1.20.0/debian/patches/stop-checking-ancient-kernel-version.patch
1970-01-01 03:00:00.0 +0300
+++ busybox-1.20.0/debian/patches/stop-checking-ancient-kernel-version.patch
2012-09-20 00:57:42.0 +0400
@@ -0,0 +1,54 @@
+From: Michael Tokarev
+Subject: stop checking ancient kernel version for NFS mount
+Forwarded: no
+Bug-Debian: http://bugs.debian.org/684611
+
+The nfs mount code checks for ancient kernel 2.2.18 (!) to determine
+which mount protocol to use (v3 or v4). Stop doing this, and always
+use v4.
+
+This is the only place in debian busybox which uses get_linux_version_code()
+function which can't deal with less-than-3-component kernel version numbers
+(#684611). (Other places are in modutils/ to determine whenever to use
+pre-2.4 module loading way, which is disabled in debian build).
+
+This is a band-aid patch, to minimize changes, more complete cleanup
+is needed for all this code upstream.
+
+--- a/util-linux/mount.c
b/util-linux/mount.c
+@@ -285,9 +285,6 @@
+
+
+ struct globals {
+-#if ENABLE_FEATURE_MOUNT_NFS
+- smalluint nfs_mount_version;
+-#endif
+ #if ENABLE_FEATURE_MOUNT_VERBOSE
+ unsigned verbose;
+ #endif
+@@ -296,7 +293,7 @@
+ } FIX_ALIASING;
+ enum { GETMNTENT_BUFSIZE = COMMON_BUFSIZE - offsetof(struct globals,
getmntent_buf) };
+ #define G (*(struct globals*)&bb_common_bufsiz1)
+-#define nfs_mount_version (G.nfs_mount_version)
++#define nfs_mount_version 4 /* assume kernel>= 2.4, use v4 nfs mount protocol
*/
+ #if ENABLE_FEATURE_MOUNT_VERBOSE
+ #define verbose (G.verbose )
+ #else
+@@ -937,6 +934,7 @@
+ static void
+ find_kernel_nfs_mount_version(void)
+ {
++#if 0
+ int kernel_version;
+
+ if (nfs_mount_version)
+@@ -950,6 +948,7 @@
+ nfs_mount_version = 3;
+ /* else v4 since 2.3.99pre4 */
+ }
++#endif
+ }
+
+ static void
diff -Nru busybox-1.20.0/debian/udeb-sizes busybox-1.20.0/debian/udeb-sizes
--- busybox-1.20.0/debian/udeb-sizes2012-07-06 19:21:26.0 +0400
+++ busybox-1.20.0/debian/udeb-sizes2012-09-20 00:32:27.0 +0400
@@ -94,3 +94,17 @@
ping applet, useful for basic network debugging/testing, +613 bytes.
Enable it.
+20120917 mjt i386 increase FEATURE_COPYBUF_KB from 4 to 64
+ textdata bss dec hex filename
+ 31271616698712 323097 4ee19 busybox+
+ 31295316778712 323342 4ef0e busybox+buf64k
+Icreases copy (cp, wget, ...) speed dramatically.
+
+20120920 mjt i386 PING6 and FEATURE_FANCY_PING
+ textdata bss dec hex filename
+ 31295316778712 323342 4ef0e busybox+
+ 31538016818712 325773 4f88d busybox+fancyping
+ 31344116778712 323830 4f0f6 busybox+ping6
+ 31700516858712 327402 4feea busybox+fancyping+ping6
+4Kb code and 8b data increase for more useful ping and ping6,
+both useful for initial network debugging, especially ping6.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686312: kdbg can't start app
On Wed, Sep 19, 2012 at 11:26:53PM +0100, Philip Ashmore wrote: > It went away shortly after I reported the bug - now it's back. > > I'm using Debian/Sid and keep my packages current daily so I think > one update fixed it and then another one broke it again. > > I now wish I had reported it as fixed so that the problem package(s) > could have been pinned down more easily. > > I'm pretty sure that a package caused (then fixed, then caused) this > problem. > Thanks Philip. The bug was filed while I was in holidays and I still haven't gotten the chance to look at it. I will try in the next 2 weeks. Ana -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688219: devscripts: [debdiff] optionally apply 3.0 (quilt) patches before diffing
Package: devscripts
Version: 2.12.3
Severity: wishlist
Suppose you have this version sequence:
foo 1.2.3-1 (upstream release)
foo 1.2.3-2 (Debian maintainer applies patches)
foo 1.2.4-1 (upstream applies our patches, and makes more fixes)
and now you want to get 1.2.3-2 -> 1.2.4-1 reviewed by the release team,
or read its diff yourself for QA, or whatever. The most representative diff
to use is between the patched source trees that we compile: it's distracting
for the diffstat to include a bunch of changes that were accepted upstream
moving from debian/patches/foo to upstream source changes.
(More concretely, telepathy-mission-control-5 1:5.12.1-1, 1:5.12.1-3 and
1:5.12.3-1 had this happen.)
I attach a crude version of this change.
--- /usr/bin/debdiff 2012-09-15 20:26:37.0 +0100
+++ /home/smcv/bin/debdiff 2012-09-20 14:13:45.248516568 +0100
@@ -108,6 +108,7 @@
# Start by setting default values
my $ignore_dirs = 1;
+my $apply_patches = 0;
my $compare_control = 1;
my $controlfiles = 'control';
my $show_moved = 0;
@@ -138,6 +139,7 @@
'DEBDIFF_WDIFF_SOURCE_CONTROL' => 'no',
'DEBDIFF_AUTO_VER_SORT' => 'no',
'DEBDIFF_UNPACK_TARBALLS' => 'yes',
+ 'DEBDIFF_APPLY_PATCHES' => 'no',
);
my %config_default = %config_vars;
@@ -183,6 +185,7 @@
$show_moved = $config_vars{'DEBDIFF_SHOW_MOVED'} eq 'yes' ? 1 : 0;
$wdiff_opt = $config_vars{'DEBDIFF_WDIFF_OPT'} =~ /^-([plt])$/ ? $1 : '';
$show_diffstat = $config_vars{'DEBDIFF_SHOW_DIFFSTAT'} eq 'yes' ? 1 : 0;
+$apply_patches = $config_vars{'DEBDIFF_APPLY_PATCHES'} eq 'yes' ? 1 : 0;
$wdiff_source_control = $config_vars{'DEBDIFF_WDIFF_SOURCE_CONTROL'}
eq 'yes' ? 1 : 0;
$auto_ver_sort = $config_vars{'DEBDIFF_AUTO_VER_SORT'} eq 'yes' ? 1 : 0;
@@ -269,6 +272,7 @@
shift;
}
elsif ($ARGV[0] eq '--diffstat') { $show_diffstat = 1; shift; }
+elsif ($ARGV[0] eq '--apply-patches') { $apply_patches = 1; shift; }
elsif ($ARGV[0] =~ /^--no-?diffstat$/) { $show_diffstat = 0; shift; }
elsif ($ARGV[0] eq '--wdiff-source-control') { $wdiff_source_control = 1; shift; }
elsif ($ARGV[0] =~ /^--no-?wdiff-source-control$/) { $wdiff_source_control = 0; shift; }
@@ -580,7 +584,7 @@
for my $i (1,2) {
no strict 'refs';
my @opts = ('-x');
- push (@opts, '--skip-patches') if $dscformats[$i] eq '3.0 (quilt)';
+ push (@opts, '--skip-patches') if $dscformats[$i] eq '3.0 (quilt)' && ! $apply_patches;
my $diri = ${"dir$i"};
eval {
spawn(exec => ['dpkg-source', @opts, $dscs[$i]],
Bug#687304: plymouth: hardcoded text theme color
retitle 687304 update default text colors thanks if you provide a patch with a suitable default color selection, i'm happy to apply it. note that the default, as it's hardcoded, should match the default artwork from desktop-base package (so red/purple isn't a good choice). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688220: debian-policy: Typo in path to shlibs files in /var/lib/dpkg/info (8.6.4.1)
Source: debian-policy Version: 3.9.4.0 Severity: minor Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi There seems to be a small typo in 8.6.4.1 refering to the path where *.shlibs files are located? It says currently: The shlibs control files for all the packages currently installed on the system. These are normally found in /var/lib/dpkg/info/*.symbols, but packages should not rely on this and instead should use dpkg-query - --control-path package shlibs if for some reason these files need to be examined. Should that be /var/lib/dpkg/info/*.shlibs? Regards, Salvatore - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQWx1PAAoJEHidbwV/2GP+EccP/iCfkv/W9dDhboerLhWaMDfR xmgkksdouDFzCmSvPy68eoMtCQXwao5Sqm0ILeF2EPfRS5MPIGfXlP1X7Rhodr5U qx7fzPZiQn1KgnQWjy6FpeEDcGQtlTiSV8ONeKungUDMALUEPp5QZkmJXV/D5+pZ TWp/yGHqIKHT0nJD2vaE7snV9GV5u/9iA3v3XWbQac4VdF4KY2U54U5MeGgdVmmE 0uR9HUKDUvM9DE5FPw40nKkqjaP2B/AlubtTzmubJ0XSFHvzTtZYD3DcO/oN/WSV Tw+/AeALsK7R3BDIcUxQj9+CSaqS3fiMlKyylijK5K/EqDHrG4L98lr829WIPOGR /EMntYbcCB01X6LCUp0WfQi0bQbHLk8syhN+fxN4PLjxVXZezshRM5mBE3CGO1l6 aA0H9bRdOtJOOb8qutApv7M9RMNdytVBH13W+YsnhUumXtFGjd/vSAi1IWOuMCJ0 XCK7Z/Dw8plKEm99+F2no9N26czssfD/AxSqWk0IG9q9D+wgYE/CQmkCvWNH77Jq 6y/bQA2ZKImJB79EsKsh5IKGVfdH8PNmT/P8xuC6liJRqzr3JGZqB5OetEcbBVzR 4umU3fwJXPwJ0qevpjwsL01W5Wb0/8JX7oXeFjTnRNcn50u+4QA3TYhZw/9bvEdJ TWVD3wkHWW/csJ9dbJks =/mA0 -END PGP SIGNATURE- >From 93c9fec9e9dc8af19ed84e16c7b054254cbfb191 Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Thu, 20 Sep 2012 15:36:58 +0200 Subject: [PATCH] Fix typo to path to shlibs files Fix typo in "8.6.4.1 The shlibs files present on the system". Refer to /var/lib/dpkg/info/*.shlibs for the location of the shlibs files. --- policy.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/policy.sgml b/policy.sgml index 5760a3f..ba217e5 100644 --- a/policy.sgml +++ b/policy.sgml @@ -6694,7 +6694,7 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) The shlibs control files for all the packages currently installed on the system. These are normally found - in /var/lib/dpkg/info/*.symbols, but + in /var/lib/dpkg/info/*.shlibs, but packages should not rely on this and instead should use dpkg-query --control-path package shlibs if for some reason these files need to be -- 1.7.10.4
Bug#681796: bug 681796, that patch does not work here..
On Wed, 19 Sep 2012, Gijs Hillenius wrote: > [ 59865.601] 0: /usr/bin/X (xorg_backtrace+0x49) [0xb778d739] > [ 59865.601] 1: /usr/bin/X (0xb761+0x181156) [0xb7791156] > [ 59865.602] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb75f140c] > [ 59865.602] 3: /usr/bin/X (MakeAtom+0x5f) [0xb763a36f] > [ 59865.602] 4: /usr/lib/libXfont.so.1 (0xb7448000+0x207cb) [0xb74687cb] > [ 59865.602] 5: /usr/lib/libXfont.so.1 (pcfReadFontInfo+0xa5) [0xb74695c5] > [ 59865.602] 6: /usr/lib/libXfont.so.1 (0xb7448000+0x1a900) [0xb7462900] > [ 59865.602] 7: /usr/lib/libXfont.so.1 (0xb7448000+0xb100) [0xb7453100] > [ 59865.602] 8: /usr/lib/libXfont.so.1 (0xb7448000+0xc1c0) [0xb74541c0] > [ 59865.602] 9: /usr/lib/libXfont.so.1 (FontFileListNextFontWithInfo+0x4d) > [0xb74543bd] > [ 59865.602] 10: /usr/bin/X (doListFontsWithInfo+0x15c) [0xb764c98c] > [ 59865.602] 11: /usr/bin/X (0xb761+0x3f339) [0xb764f339] > [ 59865.602] 12: /usr/bin/X (0xb761+0x37313) [0xb7647313] > [ 59865.602] 13: /usr/bin/X (0xb761+0x3c375) [0xb764c375] > [ 59865.602] 14: /usr/bin/X (0xb761+0x29e95) [0xb7639e95] So above suggests that this is some other issue... and probably has to do with fonts handling, thus: > Now, I don't actually use the trackpad. So, you know what? I'll apt-get > remove xserver-xorg-input-synaptics and see if that solves it. indeed would be interesting to see if any effect. But once again -- this seems to be a different issue. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688187: unblock: scim/1.4.14-2
On 20.09.2012 14:52, Hideki Yamane wrote: > The reason is scim-anthy was unblocked (Bug#685036) and migrated to > testing but scim (1.4.14-2) still stops in unstable. So, release > managers, can you consider to unblock scim to fix RC as well? Yamane-San, thank you for your report. Hello from Tokyo, how are you? Your analysis is spot on, scim-anthy fails to build from scratch due to a newer scim version not having migrated yet from unstable to testing. I'll answer here hoping to save the release team a bit of time. Scim already has an unblock request open for a while (bug 680335 which also has some background information) . The problem was externally induced by a concurrent upload of a build dependency just before the freeze, leading to an FTBFS for the version we uploaded just before the deadline. The fix for this was simple enough yet it went in after the freeze, meaning that the release team now needs to review not only this small fix but the changes we uploaded just before the freeze as well :-( For this they need more time, but I can assure you that they are aware of the situation. Regards Rolf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688221: unblock: telepathy-mission-control-5/1:5.12.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider: unblock telepathy-mission-control-5/1:5.12.3-1 for which the changelog is: telepathy-mission-control-5 (1:5.12.3-1) unstable; urgency=low * New upstream stable release - remove all patches: all applied upstream - if the user upgraded to Empathy 3 while running MC << 1:5.12.1-3 (most wheezy-as-testing users will fall into this category), complete Empathy's password migration, avoiding inability to change the account's password in future (Closes: #687933) - fix a race condition in starting Mission Control from D-Bus (Closes: #688215) -- Simon McVittie Thu, 20 Sep 2012 13:42:01 +0100 As OK'd by Adam on #687635, this syncs up with the upstream stable branch, rather than applying a bunch of patches to an older stable-branch release. Because we were previously applying patches, the most representative diff is between the patched tree arrived at by applying 1:5.12.1-3's patches, and the (unpatched) source from 1:5.12.3-1. I used a patched debdiff which applies 3.0 (quilt) patches before diffing (wishlist bug filed), and filtered the diff to omit autotools-generated files, gtk-doc documentation (which is rebuilt in Debian anyway), regression tests (which are not run in Debian), and the patches themselves. Regards, S diffstat for telepathy-mission-control-5-5.12.1 telepathy-mission-control-5-5.12.3 .pc/applied-patches |7 ChangeLog | 270 NEWS| 38 + configure.ac|5 debian/changelog| 13 debian/patches/series |7 mission-control-plugins/Makefile.am |6 mission-control-plugins/account-storage.c |2 mission-control-plugins/mcp-signals-marshal.h | 28 - server/Makefile.am |5 server/org.freedesktop.Telepathy.MissionControl5.service.in |2 src/connectivity-monitor.c |2 src/mcd-account-manager-default.c | 55 ++ tools/Makefile.am | 10 util/wait-for-name.c| 87 +++ 15 files changed, 477 insertions(+), 60 deletions(-) diff -Nru --exclude aclocal.m4 --exclude config.sub --exclude config.guess --exclude configure --exclude depcomp --exclude ltmain.sh --exclude libtool.m4 --exclude tests --exclude doc --exclude Makefile.in --exclude '*.patch' telepathy-mission-control-5-5.12.1/ChangeLog telepathy-mission-control-5-5.12.3/ChangeLog --- telepathy-mission-control-5-5.12.1/ChangeLog 2012-07-11 11:56:17.0 +0100 +++ telepathy-mission-control-5-5.12.3/ChangeLog 2012-09-20 13:22:00.0 +0100 @@ -1,3 +1,273 @@ +commit 010ab4ba86f557f89e1ec2045dc9fc5ae71513ad +Author: Simon McVittie +Date: 2012-09-20 13:21:47 +0100 + +Prepare version 5.12.3 + +commit 17965ae51796f93771a6444e90f6846639b68a9b +Author: Simon McVittie +Date: 2012-09-20 13:21:31 +0100 + +Do not distribute mcp-signals-marshal.h, which is generated at build-time + +Signed-off-by: Simon McVittie +Reviewed-by: Guillaume Desmottes + +commit eaefb264316f206186b2ac7f1f36e6a4692deb3d +Author: Simon McVittie +Date: 2012-09-20 12:28:59 +0100 + +Default accounts backend: finish password migrations that Empathy 3.0 started + +Signed-off-by: Simon McVittie +Bug: https://bugs.freedesktop.org/show_bug.cgi?id=42088 +Bug-Debian: http://bugs.debian.org/687933 +Reviewed-by: Guillaume Desmottes + +commit 5c89fe0b540eaeecd72379f1f2b9da07883425e9 +Author: Simon McVittie +Date: 2012-08-30 16:53:36 +0100 + +Make the gnome-keyring test work again, with modern gnome-keyring + +Signed-off-by: Simon McVittie +Reviewed-by: Jonny Lamb +Bug: https://bugs.freedesktop.org/show_bug.cgi?id=42088 +Cherry-picked-from: c21e2b09bf4cdda6fb05d64f9198f6db7b776c76 + +commit dd0eb39c5da72f5f0fae9bfc28072b001044b7bd +Author: Simon McVittie +Date: 2012-09-06 18:05:24 +0100 + +tools/Makefile.am: be careful not to create empty files in the builddir + +"make distcheck" in an already-out-of-tree build turns out not to +work because of this. + +This corresponds to commit beb2d971 in telepathy-glib. + +commit 073c5898443755d64752d92b2ac0c1f94581f3e9 +Author: Simon McVittie +Date: 2012-09-06 18:00:05 +0100 + +post-release version bump + +commit e37277d17d9c7cbbb519e9e881d1582727b3acb2 +Author: Simon McVittie +Date: 2012-09-06 16:59:40 +0100 + +Prepare release + +commit 5e1bbe8f891af4d86cb9dfd2f0b36fdfbbb7b2ef +Author: Simon McVitt
Bug#686867: jruby: CVE-2011-4838
On Wed, 19 Sep 2012 21:16:51 -0700 tony mancill wrote: > Thank you for attaching the patch. I have it applying cleanly and am in > the process of preparing an upload. However, currently the jruby > package is FTBFS due to an issue with one of its build-deps, nailgun, > which is installing a bad symlink. > > > $ ls -al /usr/share/java/nailgun* > > -rw-r--r-- 1 root root 25607 Jul 18 22:54 /usr/share/java/nailgun-0.9.0.jar > > -rw-r--r-- 1 root root 7048 Jul 18 22:54 > > /usr/share/java/nailgun-examples-0.9.0.jar > > lrwxrwxrwx 1 root root17 Jul 18 22:54 /usr/share/java/nailgun.jar -> > > nailgun-0.7.1.jar It's my mistake that using static version for symlink... sorry for the mess. And a bit confusion for versioning, so prepared fix as below. If it seems to be okay, I'll upload to unstable. diff -Nru nailgun-0.7.1+trunk95/debian/changelog nailgun-0.9.0+trunk95/debian/changelog --- nailgun-0.7.1+trunk95/debian/changelog 2012-07-19 07:54:01.0 +0900 +++ nailgun-0.9.0+trunk95/debian/changelog 2012-09-20 23:01:12.0 +0900 @@ -1,3 +1,12 @@ +nailgun (0.9.0+trunk95-1) unstable; urgency=low + + * Bump up version number since it produces jar files with version as +0.9.0. Nothing changed in upstream source. + * debian/nailgun.links +- fix symlink, don't use static version number. + + -- Hideki Yamane Thu, 20 Sep 2012 22:58:48 +0900 + nailgun (0.7.1+trunk95-1) unstable; urgency=medium * Taken from Subversion repository @@ -8,7 +17,7 @@ * debian/patches - refresh all two patches - add "name_define_as_ng-nailgun_ng.c.patch" to avoid - ClassNotFoundException (Closes: LP#793859) + ClassNotFoundException (LP: #793859) - add "Makefile_enable_hardening.patch" to enable hardening * debian/rules - enable hardening diff -Nru nailgun-0.7.1+trunk95/debian/nailgun.links nailgun-0.9.0+trunk95/debian/nailgun.links --- nailgun-0.7.1+trunk95/debian/nailgun.links 2010-08-23 04:33:49.0 +0900 +++ nailgun-0.9.0+trunk95/debian/nailgun.links 2012-09-20 22:57:45.0 +0900 @@ -1 +1 @@ -usr/share/java/nailgun-0.7.1.jar usr/share/java/nailgun.jar +usr/share/java/nailgun-*.jar usr/share/java/nailgun.jar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688222: needs update for 3.2.29-4
Package: linux-latest Severity: serious needs update for abi 4 of 3.2.29. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688223: emacspeak: modifies conffiles (policy 10.7.3): /etc/emacspeak.conf
Package: emacspeak Version: 29.0-8 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 emacspeak/29.0-6 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/emacspeak.conf cheers, Andreas emacspeak_29.0-8.log.gz Description: GNU Zip compressed data
