Bug#738789: libhamcrest-java: FTBFS: bad class file: hamcrest-core-1.3.jar(org/hamcrest/Description.class)
On 03/25/2014 04:07 PM, Emmanuel Bourg wrote: > This issue is really intriguing. When the build fails > hamcrest-core-1.3.jar is not corrupted (verified with zip --test) and > the compiled Description.class file is always the same (the md5sum is > constant in all cases). > > The random aspect of this bug leads me to think it's a kind of race > condition between the part of the build that writes the jar and the part > that reads it, but everything is executed sequentially so I'm not sure > how this could actually happen. > > On Googling the error message I found this interesting bit in a python > script used by Assembla to build Ant projects: > > http://subversion.assembla.com/svn/sivanea/trunk/src/buildscripts/antmake.py > > # Experience has shown that occasionally an ant build will cause an error > # like the following: > ''' > [javac] DellDXConnector.java:14: cannot access > com.perfectsearchcorp.feed.Connector > [javac] bad class file: > com/perfectsearchcorp/feed/Connector.class(com/perfectsearchcorp/feed:Connector.class) > [javac] unable to access file: corrupted zip file > [javac] Please remove or make sure it appears in the correct > subdirectory of the classpath. > [javac] import com.perfectsearchcorp.feed.Connector; > [javac] ^ > ''' > # This error appears to be caused by a bug in how either ant or java itself > # manages file handles for zip files on some platforms -- I think java is > # sometimes opening the file for read before the handle for write is fully > # released and flushed. > > > So it may be either an Ant bug (but I reviewed the jar task code and the > files seem to be properly closed) or a JVM bug on Linux. > > A simple workaround would be to mount the directory containing the > hamcrest-core classes into the classpath instead of using the generated jar. Just for curiosity (and because it recently came up with another package, although I don't currently remember which one), I tried building in a single processor, single core virtual machine, and wasn't able to observe a failure in 25 consecutive builds. For grins, I went back and renabled all of the tests for c3p0, which was consistently hanging during builds, and have been able to build it three times so far without any hangs. Both of these lend support to the hypothesis of this being a race - more specifically, a race that can occur when the JDK/JVM takes advantage of multiple threads of execution. (Or as Emmanuel said, a JVM bug on Linux.) Hmmm tony signature.asc Description: OpenPGP digital signature
Bug#742674: kernel-package: "bc" should be added to the dependencies
Package: kernel-package Version: 12.036+nmu3 Severity: minor Dear Maintainer, not really a problem: in a fresh install with only a few standard packages and the kernel-package, compiling a kernel aborts: ~/linux-3.13.5# make deb-pkg LOCALVERSION=-test.1 […] BC kernel/timeconst.h /bin/sh: 1: bc: not found make[3]: *** [kernel/timeconst.h] Error 127 make[2]: *** [kernel] Error 2 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (80, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kernel-package depends on: ii binutils 2.24-4 ii build-essential11.6 ii debianutils4.4 ii file 1:5.14-2 ii gettext0.18.3.1-2 ii make 3.81-8.3 ii module-init-tools 16-2 ii po-debconf 1.0.16+nmu2 ii util-linux 2.20.1-5.5 Versions of packages kernel-package recommends: ii cpio 2.11+dfsg-1 Versions of packages kernel-package suggests: pn btrfs-tools ii bzip2 1.0.6-5 pn docbook-utils ii e2fsprogs 1.42.9-2 pn grub | grub2 ii initramfs-tools [linux-initramfs-tool] 0.115 pn jfsutils ii libncurses5-dev [libncurses-dev]5.9+20130608-1 pn linux-source | kernel-source pn mcelog pn oprofile pn pcmciautils ii ppp 2.4.5+git20130610-3 ii procps 1:3.3.4-2 pn quota pn reiserfsprogs pn squashfs-tools ii udev204-6 pn xfsprogs pn xmlto -- 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#742673: libplist: FTBFS on mips/s390x/sparc (test failures)
Source: libplist Version: 1.11-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on mips, s390x and sparc, see the build logs at https://buildd.debian.org/status/logs.php?pkg=libplist&ver=1.11-2&suite=sid Cheers, Julien signature.asc Description: Digital signature
Bug#735447: in vlc audio is sometimes there, sometimes not there
Rémi Denis-Courmont says :- > PulseAudio keeps going into underflow. Do you hear any audio at all (with > silences) or do you hear nothing? It seems like the PulseAudio daemon is > acting up, but it could also be something wrong with the source file. Dear Remi, Thank you for following it up. This is not just with one source file but with many. The best way for me to reproduce this is to load any video media file in vlc, forward the media file sometime and then see pulseaudio lose the audio. This has been happening for months. I am on testing with all updates and still have the issue. P.S. :- For some reason the bts didn't tell me that somebody has responded to the bug hence NOW subscribing to my own bug report. I just got to my bug-report on the off-chance that there might be something I might have left out. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu3 ii consolekit0.4.6-4 ii libasound21.0.27.2-3 ii libasound2-plugins1.0.27-2+b1 ii libc6 2.18-4 ii libcap2 1:2.22-1.2 ii libdbus-1-3 1.8.0-2 ii libfftw3-single3 3.3.3-7 ii libgcc1 1:4.8.2-16 ii libice6 2:1.0.8-2 ii libltdl7 2.4.2-1.7 ii liborc-0.4-0 1:0.4.18-1 ii libpulse0 4.0-6+b1 ii libsamplerate00.1.8-7 ii libsm62:1.2.1-2 ii libsndfile1 1.0.25-9 ii libspeexdsp1 1.2~rc1.1-1 ii libstdc++64.8.2-16 ii libsystemd-login0 204-8 ii libtdb1 1.2.12-1 ii libudev1 204-8 ii libwebrtc-audio-processing-0 0.1-2 ii libx11-6 2:1.6.2-1 ii libx11-xcb1 2:1.6.2-1 ii libxcb1 1.10-2 ii libxtst6 2:1.2.2-1 ii lsb-base 4.1+Debian12 ii udev 204-8 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-3+nmu2 ii pulseaudio-module-x11 4.0-6+b1 ii rtkit 0.10-3 Versions of packages pulseaudio suggests: pn paman pn paprefs pn pavucontrol pn pavumeter ii pulseaudio-utils 4.0-6+b1 -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741792: [Pkg-pascal-devel] Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
On 17 March 2014 21:45, Paul Gevers wrote: > If I am not much mistaken, you need to fix src/doublecmd.lpi for the new > location of the units. I think line 43, but there are better experts on > this mail-list. Thanks Paul. I did try changing src/doublecmd.lpi in various ways but was not successful. Alexander (doublcmd's upstream) suggested changing components/build.sh, which I did as follows: --- a/components/build.sh +++ b/components/build.sh @@ -9,7 +9,7 @@ then $lazbuild /usr/lib/lazarus/default/compo nents/lazcontrols/lazcontrols.lpk $DC_ARCH -B $lazbuild /usr/lib/lazarus/default/components/synedit/synedit.lpk $DC_ARCH -B - $lazbuild /usr/lib/lazarus/default/ideintf/ideintf.lpk $DC_ARCH -B + $lazbuild /usr/lib/lazarus/default/components/ideintf/ideintf.lpk $DC_ARCH -B fi # Build components That solved the problem with zvdatetimepickerpropedit.pas but then I got a different error: objectinspector.pp(37,45) Fatal: Can't find unit TreeFilterEdit used by ObjectInspector TExternalToolList.Run Exception: /usr/lib/lazarus/default/components/ideintf/objectinspector.pp(37,45) Fatal: Can't find unit TreeFilterEdit used by ObjectInspector and the problem with gifanim.pas remains. Alexander then replied as follows: > The real problem in lazarus package. Lazarus can not build any LCL-Qt > application that uses controls from "lazarus/components" directory. It is > because this components marked as "manually build" in lazarus debian package > (lazarus debian rules file manually change it). In RPM distros (Fedora for > example) they marked as "automatically build" (that is upstream default > behavior) so there are no such problem. I make a workaround that worked in > previous lazarus versions (forced build of some components from lazarus > directory, that you can see in "components/build.sh"). But now it does not > work because they depends on each other. I have confirmed this by simply commenting out the section that builds doublecmd-qt in debian/rules and the doublecmd-gtk package builds without problem. Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742672: allow debootstrap to take a bare codename as the script parameter
Package: debootstrap Version: 1.0.59 Very closely related to #742671 (in which supplying "sid" for "base-installer/debootstrap_script" causes an error), I realized it might be ideal if the fix came in both directions. I've attached a patch that allows $4 (script) to be either an absolute path or a path/file within /usr/share/debootstrap/scripts, so that values like "sid" or "wheezy" can be supplied as the "script" argument and DWIM. Here's some proposed d/changelog text: [ Tianon Gravi ] * Allow "script" argument to be specified as either an absolute path as before, or as a raw codename such as "sid", assumed to be relative to "/usr/share/debootstrap/scripts". Of course, as I noted on #742671, I'm very happy to adapt this to better match expected contribution style or scripting style. :) ♥, - Tianon diff --git a/debootstrap b/debootstrap index fef1ab5..125e8bc 100755 --- a/debootstrap +++ b/debootstrap @@ -391,7 +391,11 @@ else SUPPORTED_VARIANTS="$VARIANT" fi if [ "$4" != "" ]; then - SCRIPT="$4" + if [ -e "$DEBOOTSTRAP_DIR/scripts/$4" ]; then + SCRIPT="$DEBOOTSTRAP_DIR/scripts/$4" + else + SCRIPT="$4" + fi fi fi
Bug#742392: hurd: Hang during apt-get upgrade from last image release
[Samuel Thibault] > Peter, could you try to put > http://dept-info.labri.fr/~thibault/tmp/vga.so.0.3 > into /usr/lib/hurd/console/ and start your Hurd console? That one does > work for me and on Richard's VMs. I tested, and it solved the hang for me too. :) -- 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#742671: seeding base-installer/debootstrap_script with an absolute path emits a warning, and just a codename results in an error
Package: base-installer Version: 1.145 While reading through the code to figure out the format of the values expected for "base-installer/debootstrap_script", I noticed that the code in base-installer prepends "/usr/share/debootstrap/scripts" when it checks this value, so I assumed the expected format must be something like "sid". When something like "sid" is sent, base-installer doesn't complain, but debootstrap fatal errors because it can't find the script. When something like "/usr/share/debootstrap/scripts/sid" is given, base-installer throws a warning (which I can't figure out why it's a warning and not an error, since the code uses the "error" helper), but debootstrap is happy and the install continues successfully. I've attached a patch that makes either of these values work as expected by prepending "/usr/share/debootstrap/scripts" if the given value exists within that directory, and only throwing a warning if the value given either isn't an absolute path that exists or isn't inside the debootstrap scripts directory. My proposed d/changelog update is as follows: [ Tianon Gravi ] * Fix warning given for absolute path "debootstrap_script" values. * Update "debootstrap_script" logic to allow bareword script names like "sid" as well as absolute paths. Of course, I'm open to tweaking any aspect of this, especially to better fit the expected contribution style or scripting preferences. :) ♥, - Tianon diff --git a/debian/bootstrap-base.postinst b/debian/bootstrap-base.postinst index ed2e0ab..7e12a5f 100755 --- a/debian/bootstrap-base.postinst +++ b/debian/bootstrap-base.postinst @@ -23,7 +23,9 @@ EXCLUDES="$(printf '%s' "$RET" | sed 's/ /,/g')" || true # Check if a specific script should be used db_get base-installer/debootstrap_script DEBOOTSTRAP_SCRIPT="$RET" -if [ ! -e /usr/share/debootstrap/scripts/"$DEBOOTSTRAP_SCRIPT" ]; then +if [ -e /usr/share/debootstrap/scripts/"$DEBOOTSTRAP_SCRIPT" ]; then + DEBOOTSTRAP_SCRIPT=/usr/share/debootstrap/scripts/"$DEBOOTSTRAP_SCRIPT" +elif [ ! -e "$DEBOOTSTRAP_SCRIPT" ]; then error "debootstrap script '$DEBOOTSTRAP_SCRIPT' doesn't exist" fi
Bug#742670: Critical bug fixes to be2net driver
Package: src:linux Version: 3.13.6-1 4 Severity: important X-Debbugs-CC: debian-ker...@lists.debian.org Opening Bug to submit certain 17 critical fixes to be2net driver. These patches have been accepted upstream. These fixes required in driver for Skyhawk-R. debain_8.0_patches.tgz Description: debain_8.0_patches.tgz
Bug#740835: docker.io: Move source package related docs to README.source instead of README.Debian
fixed 740835 0.9.0+dfsg1-1 kthxbye I forgot that there were two README.Debian bugs that were fixed by the updates that were in 0.9.0+dfsg1-1, not just the one; that's my bad. ♥, - Tianon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742669: mirror submission for mirrors.aliyun.com
Package: mirrors Severity: wishlist Submission-Type: new Site: mirrors.aliyun.com Type: leaf Archive-architecture: amd64 i386 Archive-http: /debian/ Backports-http: /debian-backports/ CDImage-http: /debian-cd/ IPv6: no Archive-upstream: mirrors.kernel.org Backports-upstream: ftp.us.debian.org CDImage-upstream: cdimage.debian.org Updates: once Maintainer: Min Peng Country: CN China Location: Zhe Jiang Sponsor: Alibaba cloud computing http://www.aliyun.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742668: cups: Fails to install because can't listen to sockets
Package: cups Version: 1.7.1-10 Severity: important Dear Maintainer, * What led up to the situation? Upgrading system * What exactly did you do (or not do) that was effective (or ineffective)? apt-get -u dist-upgrade * What was the outcome of this action? New cups version can't be installed, cups service no more running * What outcome did you expect instead? Working cups service by upgrading Debian/testing this day I get the following error: Do you want to continue? [Y/n] Y Setting up cups-daemon (1.7.1-10) ... A dependency job for cups.service failed. See 'journalctl -xn' for details. invoke-rc.d: initscript cups, action "start" failed. configured to not write apport reports configured to not write apport reports configured to not write apport reports dpkg: error processing package cups-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of cups-core-drivers: cups-core-drivers depends on cups-daemon (>= 1.7.1-10); however: Package cups-daemon is not configured yet. dpkg: error processing package cups-core-drivers (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of cups: cups depends on cups-core-drivers (>= 1.7.1-10); however: Package cups-core-drivers is not configured yet. cups depends on cups-daemon (>= 1.7.1-10); however: Package cups-daemon is not configured yet. dpkg: error processing package cups (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: cups-daemon cups-core-drivers cups E: Sub-process /usr/bin/dpkg returned an error code (1) journalctl -xn shows: Mar 26 05:10:16 g6 systemd[1]: Starting CUPS Printing Service Sockets. -- Subject: Unit cups.socket has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cups.socket has begun starting up. Mar 26 05:10:16 g6 systemd[1]: cups.socket failed to listen on sockets: Address already in use Mar 26 05:10:16 g6 systemd[1]: Failed to listen on CUPS Printing Service Sockets. -- Subject: Unit cups.socket has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0 3d -- -- Unit cups.socket has failed. -- -- The result is failed. Mar 26 05:10:16 g6 systemd[1]: Dependency failed for CUPS Printing Service. -- Subject: Unit cups.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0 3d -- -- Unit cups.service has failed. -- -- The result is dependency. Cups can't listen to default sockets (ports) but no other process is listening there. I guess this is a bug. Because of this, cups is no more working. Thanks for your efforts, Adrian Immanuel KIESS -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-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 Versions of packages cups depends on: ii cups-client1.7.1-10 ii cups-common1.7.1-10 iu cups-core-drivers 1.7.1-10 ih cups-daemon1.7.1-10 ii cups-filters 1.0.47-2 ii cups-ppdc 1.7.1-10 ii cups-server-common 1.7.1-10 ii debconf [debconf-2.0] 1.5.52 ii ghostscript9.05~dfsg-8+b1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libc-bin 2.18-4 ii libc6 2.18-4 ii libcups2 1.7.1-10 ii libcupscgi11.7.1-10 ii libcupsimage2 1.7.1-10 ii libcupsmime1 1.7.1-10 ii libcupsppdc1 1.7.1-10 ii libgcc11:4.8.2-16 ii libstdc++6 4.8.2-16 ii libusb-1.0-0 2:1.0.17-1+b1 ii lsb-base 4.1+Debian12 ii poppler-utils 0.22.5-4 ii procps 1:3.3.9-2 Versions of packages cups recommends: ii avahi-daemon 0.6.31-4 ii colord 1.0.6-1 ii cups-filters [ghostscript-cups] 1.0.47-2 ii printer-driver-gutenprint5.2.9-1 Versions of packages cups suggests: ii cups-bsd 1.7.1-10 ii cups-pdf 2.6.1-9 ii foomatic-db20140218-1 pn hplip ii printer-driver-hpcups 3.14.1-1 pn smbclient ii udev 204-8 -- debconf information: cupsys/backend: lpd, socket, usb, snmp, dnssd cupsys/raw-print: true -- To UNSUBSCRIBE, email t
Bug#742462: kde-workspace-bin: ksystraycmd has no man page
> The bug is reported to stable, Of course, because that's what I use because I use my computer for real work and have important data stored. Debian itself recommends: "If you want to have a secure (and stable) server you are strongly encouraged to stay with stable." (https://www.debian.org/security/faq.en.html) Maybe that's the core of the problem why so many bugs reported to Debian seem to get ignored. You can't really recommend users to use stable and report bugs against testing (or unstable?), can't you? Just for reference, I'm just now upgrading from squeeze to wheezy! (I planned to do this last year, but I was too lazy, turns out it was a good decision.) Even now, at 7.4(!), I keep finding new regressions on a daily basis. (This one, of course, is a minor one, and probably not a regression, but you asked for it. You can search for my other reports in the BTS if you want to know. And there are further issues that I found were already reported and more I'm just investigating.) All in all, it's been almost a disaster to me, few bugs (that concern me) were fixed and many new regressions. To think of trying testing in these circumstances seems absurd to me. (I'm a developer, but I also need a stable system to use and work on.) At most, I'll try a few selected packages from testing later this year, but of course not before I've actually finished upgrading to stable. > A manpage written in docbook would be welcome, Well, you know, the reason I was looking for the man page was that I wanted to find out how to use the program. That hardly puts me in a position to write one. FWIW, for my particular use case I found what I needed on the net and using the "--help" output, but that still doesn't qualify me to document the whole program, don't you think? Maybe the "--help" output is sufficient. In this case, there's a useful little too called "help2man". (It even has a Debian package!) I use it myself for many of my programs since I'm too lazy to write and maintain separate man pages. Maybe you can use it here too. > Feel free to forward the bug upstream [1], Sorry, but isn't this your job as the Debian maintainer? I thought the workflow was: * user finds a bug using Debian * user reports it to the Debian BTS * Debian maintainer checks whether the bug is due to Debian's modifications (this happens, not only in ssh ;) * If so, they fix their patches * If not, they forward it to upstream If I'm supposed to forward it to upstream myself why should I use the DBTS in the first place? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742667: libsyntax-highlight-engine-kate-perl: case-sensitive matching cause "undefined language: python"
Package: libsyntax-highlight-engine-kate-perl Version: 0.08+dfsg-1 Severity: wishlist Dear Maintainer, When build publican docs, I encountered the following error: undefined language: python at /usr/share/perl5/Syntax/Highlight/Engine/Kate.pm line 621. I checked Kate.pm, python support is included, but the first letter of the name is capitalized. When I changed "python" to "Python" in document xml file, building succeeded. It's clear the kate engine match programming language case-sensitively, upstream has a patch already: https://rt.cpan.org/Public/Bug/Display.html?id=84982 I've tested the patch, it works fine. Will it applied in the next update? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsyntax-highlight-engine-kate-perl depends on: ii perl 5.18.2-2+b1 libsyntax-highlight-engine-kate-perl recommends no packages. libsyntax-highlight-engine-kate-perl suggests no packages. -- no debconf information -- To be free as in freedom.
Bug#742666: Sorry, I had a small mistake on the last diff
I have attached the new, corrected diff.
diff -Nru cups-1.7.1/debian/changelog cups-1.7.1/debian/changelog
--- cups-1.7.1/debian/changelog 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/changelog 2014-03-25 19:41:34.0 -0700
@@ -1,3 +1,10 @@
+cups (1.7.1-10.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Added Upstart support
+
+ -- Cameron Norman Tue, 25 Mar 2014 19:06:28 -0700
+
cups (1.7.1-10) unstable; urgency=medium
[ Till Kamppeter ]
diff -Nru cups-1.7.1/debian/control cups-1.7.1/debian/control
--- cups-1.7.1/debian/control 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/control 2014-03-25 19:41:34.0 -0700
@@ -203,7 +203,7 @@
Depends: ${shlibs:Depends},
${misc:Depends},
procps,
- lsb-base (>= 3),
+ lsb-base (>= 4.1+Debian3),
libcups2 (= ${binary:Version}),
ssl-cert (>= 1.0.11),
adduser,
diff -Nru cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart
--- cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart 1969-12-31 16:00:00.0 -0800
+++ cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart 2014-03-25 19:41:34.0 -0700
@@ -0,0 +1,8 @@
+description "Reload CUPS to ensure remote queues are populated"
+author "Dimitri John Ledkov "
+
+start on started avahi-daemon
+
+task
+
+exec reload cups
diff -Nru cups-1.7.1/debian/cups-daemon.cups.init cups-1.7.1/debian/cups-daemon.cups.init
--- cups-1.7.1/debian/cups-daemon.cups.init 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/cups-daemon.cups.init 2014-03-25 19:41:34.0 -0700
@@ -53,6 +53,17 @@
fi
}
+if init_is_upstart; then
+case "$1" in
+stop)
+exit 0
+;;
+*)
+exit 1
+;;
+esac
+fi
+
case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
diff -Nru cups-1.7.1/debian/cups-daemon.cups.upstart cups-1.7.1/debian/cups-daemon.cups.upstart
--- cups-1.7.1/debian/cups-daemon.cups.upstart 1969-12-31 16:00:00.0 -0800
+++ cups-1.7.1/debian/cups-daemon.cups.upstart 2014-03-25 19:41:34.0 -0700
@@ -0,0 +1,19 @@
+description "CUPS - Common Unix Printing Service"
+
+start on remote-filesystems
+stop on runlevel [016]
+
+expect fork
+respawn
+
+pre-start script
+[ -x /usr/sbin/cupsd ] || { stop; exit 0; }
+
+mkdir -p /var/run/cups/certs
+
+if [ -x /lib/init/apparmor-profile-load ]; then
+/lib/init/apparmor-profile-load usr.sbin.cupsd
+fi
+end script
+
+exec cupsd
diff -Nru cups-1.7.1/debian/rules cups-1.7.1/debian/rules
--- cups-1.7.1/debian/rules 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/rules 2014-03-25 19:41:34.0 -0700
@@ -71,8 +71,8 @@
override_dh_install:
ifeq ($(derives_from_ubuntu),yes)
- # Use upstart script on Ubuntu; we need to hide it away for Debian
- # builds, as dh_installinit does not have a --sysvinit-only
+ # Delete Debian's Upstart jobs and copy Ubuntu's over
+ rm -f debian/*.upstart
cp debian/local/*.upstart debian
endif
dh_install
@@ -133,7 +133,8 @@
ifeq ($(derives_from_ubuntu),yes)
dh_installinit --name=cups --upstart-only
else
- dh_installinit --name=cups
+ # avahi-reload-cups used by Upstart to avoid waiting for Avahi before starting
+ dh_installinit --name=cups --name=avahi-reload-cups
endif
override_dh_fixperms:
@@ -164,7 +165,6 @@
rm -f man/client.conf.man packaging/cups.list
rm -f conf/mime.convs conf/snmp.conf init/org.cups.cups-lpd.plist
[ ! -f Makedefs ] || make distclean
- rm -f debian/*.upstart # master copy is in debian/local
override_dh_installdocs:
dh_installdocs -plibcupsimage2-dev --link-doc=libcupsimage2
Bug#742666: No Upstart support
Package: cups-daemon
Version: 1.7.1-10
Attached is a debdiff that provides two Upstart jobs (one to start
cups, another to reload it when avahi is started) and makes the
necessary changes to the init script, rules file (the upstart jobs in
debian/ were being deleted), as well as the control file (to bump the
lsb dependency to a version with "init_is_upstart").
Thank you for considering the patch,
--
Cameron Norman
diff -Nru cups-1.7.1/debian/changelog cups-1.7.1/debian/changelog
--- cups-1.7.1/debian/changelog 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/changelog 2014-03-25 19:41:34.0 -0700
@@ -1,3 +1,10 @@
+cups (1.7.1-10.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Added Upstart support
+
+ -- Cameron Norman Tue, 25 Mar 2014 19:06:28 -0700
+
cups (1.7.1-10) unstable; urgency=medium
[ Till Kamppeter ]
diff -Nru cups-1.7.1/debian/control cups-1.7.1/debian/control
--- cups-1.7.1/debian/control 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/control 2014-03-25 19:41:34.0 -0700
@@ -203,7 +203,7 @@
Depends: ${shlibs:Depends},
${misc:Depends},
procps,
- lsb-base (>= 3),
+ lsb-base (>= 4.1+Debian3),
libcups2 (= ${binary:Version}),
ssl-cert (>= 1.0.11),
adduser,
diff -Nru cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart
--- cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart 1969-12-31 16:00:00.0 -0800
+++ cups-1.7.1/debian/cups-daemon.avahi-reload-cups.upstart 2014-03-25 19:41:34.0 -0700
@@ -0,0 +1,8 @@
+description "Reload CUPS to ensure remote queues are populated"
+author "Dimitri John Ledkov "
+
+start on started avahi-daemon
+
+task
+
+exec reload cups
diff -Nru cups-1.7.1/debian/cups-daemon.cups.init cups-1.7.1/debian/cups-daemon.cups.init
--- cups-1.7.1/debian/cups-daemon.cups.init 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/cups-daemon.cups.init 2014-03-25 19:41:34.0 -0700
@@ -53,6 +53,17 @@
fi
}
+if init_is_upstart; then
+case "$1" in
+stop)
+exit 0
+;;
+*)
+exit 1
+;;
+esac
+fi
+
case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
diff -Nru cups-1.7.1/debian/cups-daemon.cups.upstart cups-1.7.1/debian/cups-daemon.cups.upstart
--- cups-1.7.1/debian/cups-daemon.cups.upstart 1969-12-31 16:00:00.0 -0800
+++ cups-1.7.1/debian/cups-daemon.cups.upstart 2014-03-25 19:41:34.0 -0700
@@ -0,0 +1,19 @@
+description "CUPS - Common Unix Printing Service"
+
+start on remote-filesystems
+stop on runlevel [016]
+
+expect fork
+respawn
+
+pre-start script
+[ -x cupsd ] || { stop; exit 0; }
+
+mkdir -p /var/run/cups/certs
+
+if [ -x /lib/init/apparmor-profile-load ]; then
+/lib/init/apparmor-profile-load usr.sbin.cupsd
+fi
+end script
+
+exec cupsd
diff -Nru cups-1.7.1/debian/rules cups-1.7.1/debian/rules
--- cups-1.7.1/debian/rules 2014-03-25 18:45:37.0 -0700
+++ cups-1.7.1/debian/rules 2014-03-25 19:41:34.0 -0700
@@ -71,8 +71,8 @@
override_dh_install:
ifeq ($(derives_from_ubuntu),yes)
- # Use upstart script on Ubuntu; we need to hide it away for Debian
- # builds, as dh_installinit does not have a --sysvinit-only
+ # Delete Debian's Upstart jobs and copy Ubuntu's over
+ rm -f debian/*.upstart
cp debian/local/*.upstart debian
endif
dh_install
@@ -133,7 +133,8 @@
ifeq ($(derives_from_ubuntu),yes)
dh_installinit --name=cups --upstart-only
else
- dh_installinit --name=cups
+ # avahi-reload-cups used by Upstart to avoid waiting for Avahi before starting
+ dh_installinit --name=cups --name=avahi-reload-cups
endif
override_dh_fixperms:
@@ -164,7 +165,6 @@
rm -f man/client.conf.man packaging/cups.list
rm -f conf/mime.convs conf/snmp.conf init/org.cups.cups-lpd.plist
[ ! -f Makedefs ] || make distclean
- rm -f debian/*.upstart # master copy is in debian/local
override_dh_installdocs:
dh_installdocs -plibcupsimage2-dev --link-doc=libcupsimage2
Bug#739068: megaglest is marked for autoremoval from testing
Control: tags -1 + patch
On Wed, Mar 26, 2014 at 9:19 AM, Paul Wise wrote:
> On Wed, Mar 26, 2014 at 4:54 AM, Vincent Cheng wrote:
>> On Sat, Mar 22, 2014 at 5:51 AM, Debian testing autoremoval watch wrote:
>>> megaglest 3.7.1-2.1 is marked for autoremoval from testing on 2014-04-06
>>>
>>> It is affected by these RC bugs:
>>> 739068: megaglest: Current package is unusable, but a few tricks can fix it
>
> I'll fix the RC bug today, thanks for the ping.
Tom, Mark, please use git am to apply the attached fix to git.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From dce61e29ba5f97bbe4c319cec7c6fd370c660971 Mon Sep 17 00:00:00 2001
From: Paul Wise
Date: Wed, 26 Mar 2014 10:26:53 +0800
Subject: [PATCH] Also support -DCMAKE_BUILD_TYPE=None which is used by Debian
---
CMakeLists.txt | 9 -
source/glest_game/CMakeLists.txt | 1 +
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 48e4bea..77b67e4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -188,6 +188,9 @@ IF(CMAKE_COMPILER_IS_GNUCXX OR MINGW)
message(STATUS "**WARNING DID NOT Find GCC backtrace lib")
ENDIF()
+ # Default compiler flags
+ SET(CMAKE_CXX_FLAGS_NONE "${CMAKE_CXX_FLAGS_NONE}")
+
# Debug compiler flags
SET(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -g3")
@@ -280,6 +283,7 @@ IF(CMAKE_COMPILER_IS_GNUCXX OR MINGW)
MESSAGE(STATUS "*NOTE: Custom Data Install Path is [${CUSTOM_DATA_INSTALL_PATH}]")
ENDIF()
+ SET(CMAKE_CXX_FLAGS_NONE "${CMAKE_CXX_FLAGS_NONE} ${GIT_VERSION_CMD} ${CUSTOM_DATA_INSTALL_PATH_VALUE}")
SET(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} ${GIT_VERSION_CMD} ${CUSTOM_DATA_INSTALL_PATH_VALUE}")
SET(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} ${GIT_VERSION_CMD} ${CUSTOM_DATA_INSTALL_PATH_VALUE}")
SET(CMAKE_CXX_FLAGS_RELWITHDEBINFO "${CMAKE_CXX_FLAGS_RELWITHDEBINFO} ${GIT_VERSION_CMD} ${CUSTOM_DATA_INSTALL_PATH_VALUE}")
@@ -287,12 +291,15 @@ IF(CMAKE_COMPILER_IS_GNUCXX OR MINGW)
# We do some funky character escaping to get the right stuff written out to
# the final Makefile so we get the GIT Global Revsion #
+ string(REPLACE "'" "\"" CMAKE_CXX_FLAGS_NONE "${CMAKE_CXX_FLAGS_NONE}")
string(REPLACE "'" "\"" CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG}")
string(REPLACE "'" "\"" CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE}")
string(REPLACE "'" "\"" CMAKE_CXX_FLAGS_RELWITHDEBINFO "${CMAKE_CXX_FLAGS_RELWITHDEBINFO}")
string(REPLACE "'" "\"" CMAKE_CXX_FLAGS_MINSIZEREL "${CMAKE_CXX_FLAGS_MINSIZEREL}")
- IF( CMAKE_BUILD_TYPE STREQUAL Debug )
+ IF( CMAKE_BUILD_TYPE STREQUAL None )
+ message("CMAKE_CXX_FLAGS_NONE: ${CMAKE_CXX_FLAGS_NONE}")
+ ELSEIF( CMAKE_BUILD_TYPE STREQUAL Debug )
message("CMAKE_CXX_FLAGS_DEBUG: ${CMAKE_CXX_FLAGS_DEBUG}")
ELSEIF( CMAKE_BUILD_TYPE STREQUAL Release )
message("CMAKE_CXX_FLAGS_RELEASE: ${CMAKE_CXX_FLAGS_RELEASE}")
diff --git a/source/glest_game/CMakeLists.txt b/source/glest_game/CMakeLists.txt
index 1c94df6..eabc866 100644
--- a/source/glest_game/CMakeLists.txt
+++ b/source/glest_game/CMakeLists.txt
@@ -208,6 +208,7 @@ IF(BUILD_MEGAGLEST)
ENDIF()
IF(WIN32)
+ SET(CMAKE_CXX_FLAGS_NONE "${CMAKE_CXX_FLAGS_NONE} -Wl,-subsystem,console -mconsole")
SET(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -Wl,-subsystem,console -mconsole")
SET(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} -Wl,-subsystem,console -mconsole")
SET(CMAKE_CXX_FLAGS_RELWITHDEBINFO "${CMAKE_CXX_FLAGS_RELWITHDEBINFO} -Wl,-subsystem,console -mconsole")
--
1.9.0
Bug#742657: wxwidgets2.8: FTBFS on unstable
severity 742657 normal tags 742657 + unreproducible thanks On Wed, Mar 26, 2014 at 09:12:47AM +0900, Nobuhiro Iwamatsu wrote: > wxwidgets2.8 FTBFS on unstable > I confirmed on pbuilder. > Could you check on your environment? Works for me using sbuild. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742665: pkg-config: FTBFS on arm64 due to outdated config.{sub,guess}
Package: pkg-config
Version: 0.26-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64
pkg-config FTBFS on arm64 as it's config.sub and guess files are too old
to know about aarch64. this patch adds dh-autoreconf support which fixes
this for all architectures. A more conservative version could just use
dh-autotools-dev in the same way.
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -u pkg-config-0.26/debian/control pkg-config-0.26/debian/control
--- pkg-config-0.26/debian/control
+++ pkg-config-0.26/debian/control
@@ -2,7 +2,7 @@
Section: devel
Priority: optional
Maintainer: Tollef Fog Heen
-Build-Depends: debhelper (>= 7.0.50), libglib2.0-dev, libpopt-dev
+Build-Depends: debhelper (>= 7.0.50), dh-autoreconf, libglib2.0-dev, libpopt-dev
Homepage: http://pkg-config.freedesktop.org
Standards-Version: 3.8.4
diff -u pkg-config-0.26/debian/rules pkg-config-0.26/debian/rules
--- pkg-config-0.26/debian/rules
+++ pkg-config-0.26/debian/rules
@@ -8,7 +8,7 @@
done | sort -u | tr '\n' : | sed 's/:$$//')
%:
- dh $@
+ dh $@ --with autoreconf
override_dh_auto_configure:
./configure --prefix=/usr \
diff -u pkg-config-0.26/debian/changelog pkg-config-0.26/debian/changelog
--- pkg-config-0.26/debian/changelog
+++ pkg-config-0.26/debian/changelog
@@ -1,3 +1,10 @@
+pkg-config (0.26-1+cfg) unreleased; urgency=low
+
+ * Non-maintainer upload.
+ * Update config.{sub,guess} for new arches (with dh-autoreconf)
+
+ -- Wookey Mon, 24 Mar 2014 17:58:55 +
+
pkg-config (0.26-1) unstable; urgency=low
* New upstream release
only in patch2:
unchanged:
--- pkg-config-0.26.orig/config.log
+++ pkg-config-0.26/config.log
@@ -0,0 +1,233 @@
+This file contains any messages produced by compilers while
+running configure, to aid debugging if configure makes a mistake.
+
+It was created by configure, which was
+generated by GNU Autoconf 2.68. Invocation command line was
+
+ $ ./configure --prefix=/usr --with-installed-popt --mandir=${prefix}/share/man --infodir=${prefix}/share/info --disable-shared --with-pc-path=/usr/local/lib/aarch64-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/aarch64-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig --with-system-library-path=/lib:/lib/aarch64-linux-gnu:/usr/lib:/usr/lib/aarch64-linux-gnu
+
+## - ##
+## Platform. ##
+## - ##
+
+hostname = turfan
+uname -m = aarch64
+uname -r = 3.12.0-mustang_sw_1.11.09-beta
+uname -s = Linux
+uname -v = #4 SMP Mon Mar 24 10:24:20 CST 2014
+
+/usr/bin/uname -p = unknown
+/bin/uname -X = unknown
+
+/bin/arch = unknown
+/usr/bin/arch -k = unknown
+/usr/convex/getsysinfo = unknown
+/usr/bin/hostinfo = unknown
+/bin/machine = unknown
+/usr/bin/oslevel = unknown
+/bin/universe = unknown
+
+PATH: /usr/local/bin
+PATH: /usr/bin
+PATH: /bin
+PATH: /usr/local/games
+PATH: /usr/games
+
+
+## --- ##
+## Core tests. ##
+## --- ##
+
+configure:2300: checking for a BSD-compatible install
+configure:2368: result: /usr/bin/install -c
+configure:2379: checking whether build environment is sane
+configure:2429: result: yes
+configure:2570: checking for a thread-safe mkdir -p
+configure:2609: result: /bin/mkdir -p
+configure:2622: checking for gawk
+configure:2652: result: no
+configure:2622: checking for mawk
+configure:2638: found /usr/bin/mawk
+configure:2649: result: mawk
+configure:2660: checking whether make sets $(MAKE)
+configure:2682: result: yes
+configure:2763: checking whether to enable maintainer-specific portions of Makefiles
+configure:2772: result: no
+configure:2818: checking build system type
+configure:2827: error: cannot guess build type; you must specify one
+
+## ##
+## Cache variables. ##
+## ##
+
+ac_cv_env_CC_set=
+ac_cv_env_CC_value=
+ac_cv_env_CFLAGS_set=
+ac_cv_env_CFLAGS_value=
+ac_cv_env_CPPFLAGS_set=
+ac_cv_env_CPPFLAGS_value=
+ac_cv_env_CPP_set=
+ac_cv_env_CPP_value=
+ac_cv_env_LDFLAGS_set=
+ac_cv_env_LDFLAGS_value=
+ac_cv_env_LIBS_set=
+ac_cv_env_LIBS_value=
+ac_cv_env_build_alias_set=
+ac_cv_env_build_alias_value=
+ac_cv_env_host_alias_set=
+ac_cv_env_host_alias_value=
+ac_cv_env_target_alias_set=
+ac_cv_env_target_alias_value=
+ac_cv_path_install='/usr/bin/install -c'
+ac_cv_path_mkdir=/bin/mkdir
+ac_cv_prog_AWK=mawk
+ac_cv_prog_make_make_set=yes
+
+## - ##
+## Output variables. ##
+## - ##
+
+ACLOCAL='${SHELL} /home/buildd/packages/modified/pkg-config-0.26/missing --run aclocal-1.11'
+ALLOCA=''
+AMDEPBACKSLASH=''
+AMDEP_FALSE=''
+AMDEP_TRUE=''
+AMTAR='${SHELL} /home/buildd/packages/modified/pkg-config-0.26/missing --run tar'
+AR=''
+AUTOCONF='${SHELL} /home/buildd/packages
Bug#742392: hurd: Hang during apt-get upgrade from last image release
Hello, Downgrading my host kernel to 3.2 allowed me to reproduce the issue, and bisect the VGA driver changes down to a seemingly odd difference: the addition of unsigned char attr_mode; in the vga_state structure. Yes, that is what makes qemu completely hang with hwaccel on linux kernel 3.2. Putting some padding after that, i.e. unsigned char attr_mode, pad1, pad2, pad3; gets rid of the issue. My guess is that the additional byte unaligns videomem and fontmem, and then the memcpies between VGA memory and main RAM are unaligned, thus using some other code, which perhaps wasn't properly emulated by linux 3.2. Peter, could you try to put http://dept-info.labri.fr/~thibault/tmp/vga.so.0.3 into /usr/lib/hurd/console/ and start your Hurd console? That one does work for me and on Richard's VMs. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742664: Problem installing nvidia drivers in Testing
Package: nvidia-driver
Version: 331.49-1 [non-free]
When I do:
root@host:~# aptitude -r install linux-headers-$(uname -r|sed
's,[^-]*-[^-]*-,,') nvidia-kernel-dkms
I get:
The following NEW packages will be installed:
dkms{a} firmware-linux-free{a} glx-alternative-mesa{a}
glx-alternative-nvidia{a} glx-diversions{a}
libgl1-nvidia-alternatives{a} libgl1-nvidia-glx{a}
libglx-nvidia-alternatives{a} libxnvctrl0{a} libxvmcnvidia1{a}
linux-compiler-gcc-4.8-x86{a} linux-headers-3.13-1-686-pae{a}
linux-headers-3.13-1-common{a} linux-headers-686-pae
linux-image-3.2.0-4-rt-686-pae{a} linux-kbuild-3.13{a} menu{a}
nvidia-alternative{a}
nvidia-glx{a} nvidia-installer-cleanup{a} nvidia-kernel-common{a}
nvidia-kernel-dkms nvidia-settings{a} nvidia-support{a}
nvidia-vdpau-driver{a}
pkg-config{a} xserver-xorg-video-nvidia{ab}
0 packages upgraded, 27 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.8 MB of archives. After unpacking 197 MB will be used.
The following packages have unmet dependencies:
xserver-xorg-video-nvidia : Depends: xorg-video-abi-14 which is a
virtual package. or
xorg-video-abi-13 which is a
virtual package. or
xorg-video-abi-12 which is a
virtual package. or
xorg-video-abi-11 which is a
virtual package. or
xorg-video-abi-10 which is a
virtual package. or
xorg-video-abi-8 which is a
virtual package. or
xorg-video-abi-6.0 which is a
virtual package.
Depends: xserver-xorg-core (< 2:1.14.99)
but 2:1.15.0-2 is installed.
libgl1-mesa-glx : Breaks: glx-diversions (< 0.4) but 0.2.2 is to be
installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) glx-alternative-mesa [Not Installed]
2) glx-alternative-nvidia [Not Installed]
3) glx-diversions [Not Installed]
4) libgl1-nvidia-alternatives [Not Installed]
5) libgl1-nvidia-glx [Not Installed]
6) libglx-nvidia-alternatives [Not Installed]
7) libxvmcnvidia1 [Not Installed]
8) nvidia-alternative [Not Installed]
9) nvidia-glx [Not Installed]
10) xserver-xorg-video-nvidia [Not Installed]
Leave the following dependencies unresolved:
11) nvidia-settings recommends libgl1-nvidia-glx
12) nvidia-kernel-dkms recommends nvidia-glx (>= 304.88)
Accept this solution? [Y/n/q/?]
I don't know how to get around this issue, unless it is corrected by the
maintainers.
Cheers (and thanks, Debian rocks)
--
- Jeff
/http://clients.teksavvy.com/~jrsx13/
Bug#742663: ca-certificates: indentation issues in update-ca-certificates
Package: ca-certificates Version: 20140223 Severity: minor Tags: patch I was reading the code of update-ca-certificates and detected a few indentation issues. see the attached patch. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.52 ii openssl1.0.1f-1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information excluded -- Antonio Terceiro --- a/sbin/update-ca-certificates +++ b/sbin/update-ca-certificates @@ -26,13 +26,13 @@ fresh=0 while [ $# -gt 0 ]; do case $1 in - --verbose|-v) - verbose=1;; - --fresh|-f) - fresh=1;; - --help|-h|*) - echo "$0: [--verbose] [--fresh]" - exit;; +--verbose|-v) + verbose=1;; +--fresh|-f) + fresh=1;; +--help|-h|*) + echo "$0: [--verbose] [--fresh]" + exit;; esac shift done @@ -88,13 +88,13 @@ if [ "$fresh" = 1 ]; then echo -n "Clearing symlinks in $ETCCERTSDIR..." find . -type l -print | while read symlink do - case $(readlink $symlink) in - $CERTSDIR*) rm -f $symlink;; - esac +case $(readlink $symlink) in + $CERTSDIR*) rm -f $symlink;; +esac done find . -type l -print | while read symlink do - test -f $symlink || rm -f $symlink +test -f $symlink || rm -f $symlink done echo "done." fi signature.asc Description: Digital signature
Bug#734626: [Pkg-fonts-devel] Bug#734626: fonts-opendin: Typo in Menu Name of Font (Eng*sh*rift instead of Engschrift)
On Wed, Mar 26, 2014 at 4:48 AM, Francesca Ciceri wrote: > So: the archive and the directory names are correct, the filenames > and the metadata of the font contain the typo. Indeed: http://pkg-fonts.alioth.debian.org/review/fnt-10b31e2c901486b86b5e3b0703df360a.html > While it's certainly possible to fix it in the Debian package, maybe > it's even better if upstream fixes it directly in the source? Definitely. In addition it would be great if you added a build system to the upstream source and removed the generated files (SVG, EOT, TTF) so that if Debian has to change the font, we can automatically rebuild the binary TTF the same way you would. Right now we only have vague instructions that the font was "made using open-source tools, like Fontforge and Inkscape" but not the actual commands used to auto-convert the font to TTF. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718434: fixed in ca-certificates 20140223
On Tue, Mar 25, 2014 at 11:23:02PM +0100, Christoph Anton Mitterer wrote: > On Tue, 2014-03-25 at 18:58 +0100, Bas Wijnen wrote: > > No, the point is that an attacker is detectable. > Why should he be? Because I can store the certificate, go somewhere else, and check if my stored version is identical to the version that I receive from there. In that sense, self-signed certificates are actually more safe; they produce a new warning when the certificate changes. This is about "let's encrypt every single connection on the web". We're talking about people like me. I have a website with a CAcert certificate. I can check that my key as it is stored on my server (in my house) is the same key that I get when I visit the site from the US (if there's one place where the NSA should have no problem getting access it's there). > Well if one has to assume that they sit "in" the big internet exchange > points... this already gives them a lot... If they are in the building and can tap the wire, but not modify the packets, then an encrypted link is unreadable for them. > > But if they start to doubt, they can check if they have been attacked, > > by comparing their keys through an independent channel. > Well but that simply doesn't happen, does it? I recently did it, I'm guessing I'm not the only one. > So people must have your "doubts" by know, but nothing really changes. I'm talking about posts on Slashdot from people saying "I checked my certificate from home and from the US, and they were different, therefore 'someone is doing something naughty'". I haven't seen any of those. > > to convince people that not encrypting is better than encrypting > > with unchecked keys. > Well that's not what I said... I rather say the later is simply not > enough. Fair enough, you didn't say it was better, but you did disagree with "it's better to do crypto, even if it's anonymous and you have no idea who you're talking to". ... which leads to the conclusion that "it's not better to do crypto" in that situation (which isn't the same as "better not to", but close enough, I would think). > Well first... why is an attack only a problem if it's done at large > scale? Because the data we're talking about is approximately the definition of uninteresting. It's all the connections to people's private websites, personal chat sessions, that sort of stuff. The only way it is useful for them, is when they gather huge amounts of it and filter it. > If the NSA does this only for the Snowdens, Applebaums, etc. ... then > this is enough for them... In that case you can stop worrying. The NSA has billions of dollars at their disposal. If they really want some information, they will get it. There is no way we can prevent that, and we shouldn't waste our time on trying. Expect the NSA to always be able to read everything. It may not always be true, but who cares? We don't have the power to stop them. What remains, is a mostly unencrypted web. We should fix that. The NSA isn't the only one who wants to listen, and even if we can't stop the NSA, we can still stop most others. The only way to do that, is by making encryption easy and functional. Dropping CAs from the list is counterproductive. Especially with CAcert, which I expect to be disproportionally popular with Debian users. > I'm not saying that CAcert is secure or trustworthy (actually I wouldn't > use it for my own "security critical" services - neither would I use any > other CA not under my personal control)... but it's not less secure than > any other CA we ship. Unless you are really large (like Google or Microsoft), a CA under your personal control is useless. The point of a CA is that your visitors get the root key through an independent trusted channel. If you need to send your personal root key to all your visitors, you can as well send them the key you use for encryption. > And right now, the only thing we do is taking away the user's > possibility to retrieve root certificates in a secure way. > > We should not remove certs... we should add more, like CERN CA, TACAR > TERENA, etc. On that we agree, then. :-) Thanks, Bas signature.asc Description: Digital signature
Bug#742662: vrms does not detect non-free firmware added from USB during install
Package: vrms Version: 1.16 Severity: wishlist While vrms does warn about the firmware-linux-nonfree package if it is present, it cannot detect whether the user supplied non-free firmware from external storage during the Debian install. -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#685506: Modifying Files-Excluded pattern specification
On Sat, Mar 22, 2014 at 02:00:40PM +0100, Nicolas Boulenguez wrote: > In-Reply-To=<20140321105301.ge18...@an3as.eu> > > Joachim Breitner wrote: > > File-Excluded: foo/bar.js to exclude > > * foo/bar.js (in case of a dirty tarball) > > * pkg-1.0/foo/bar.js (as in your implementation) as well as > > * pkg-1.0/docs/foo/bar.js (this would be new > > the easiest, as it will conceivably stand less in the way of the > > developers, i.e. he would _not_ have to first look up the precise semantics. > > Andreas Tille wrote: > > it is really flexible > > The same effect was available with "*foo/bar.js" or the more accurate > "foo/bar.js */foo/bar.js". > > Imagine an upstream providing two implementations, a default non free > "imp.c" and a free alternative "gpl/imp.c". The maintainer cannot > remove the former while keeping the latter anymore. > > I call this less flexible, but I may miss your point. Agreed. We shouldn't be introducing divergence between how Files: and Files-Excluded: are interpreted. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742661: first file marked as done when Connection timed out
Package: sitecopy Version: 1:0.16.6-5 In this situation the first file gets marked as done, sitecopy: Updating site `dreamhost' (on jidanni.org in ~/jidanni.org/) Uploading comp/configuration/.emacs: [ssh: connect to host jidanni.org port 22: Connection timed out Couldn't read packet: Connection reset by peer ] done. Uploading comp/configuration/.emacs-w3m: [] failed: An error occurred. Uploading comp/configuration/.gnus.el: [] failed: An error occurred. Uploading sitemap.html: [] failed: An error occurred. sitecopy: Errors occurred while updating the remote site. A check shows that the first file was not in fact remotely updated, but still marked as done! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742660: move of ocp files breaks updates 2013.20140123-1 from 2013.20140314-1
Package: texlive-omega Version: 2013.20140314-1 Severity: important Control: owner -1 jsh...@yahoo.com It turned out that due to a move of the ocp files from texlive-base to texlive-omega, partial upgrades might be broken. Attached is the original followup to bug 673022, which is unrelated. Thanks Norbert On Sun, 23 Mar 2014, js wrote: > Package: texlive-base > Followup-For: Bug #673022 > > Dear Maintainer, > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > >* What led up to the situation: > During an upgrade texlive-base:all 2013.20140123-1 2013.20140314-1, I got the > same error as reported in this bug, so that texlive-base, and all packages > dependent > on it, failed to get configured: > > > Setting up texlive-base (2013.20140314-1) ... > > mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... > > mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... > > mktexlsr: Updating /var/lib/texmf/ls-R... > > mktexlsr: Done. > > /usr/bin/tl-paper: setting paper size for dvips to letter. > > /usr/bin/tl-paper: setting paper size for dvipdfmx to letter. > > /usr/bin/tl-paper: setting paper size for xdvi to letter. > > /usr/bin/tl-paper: setting paper size for pdftex to letter. > > Running mktexlsr. This may take some time... done. > > Building format(s) --all. > > This may take some time... > > fmtutil-sys failed. Output has been stored in > > /tmp/fmtutil.3YhQeNol > > Please include this file if you report a bug. > > Workaround: I ran apt-get remove texlive-base, followed by an apt-get install > of texlive-base and all the other packages removed because of texlive-base. > This install from scratch,without a prior version of texlive-base, worked > fine. > > > I'll include the zipped file /tmp/fmtutil.3YhQeNol in the next email. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > -- Package-specific info: > IMPORTANT INFORMATION: We will only consider bug reports concerning > the packaging of TeX Live as relevant. If you have problems with > combination of packages in a LaTeX document, please consult your > local TeX User Group, the comp.text.tex user group, the author of > the original .sty file, or any other help resource. > > In particular, bugs that are related to up-upstream, i.e., neither > Debian nor TeX Live (upstream), but the original package authors, > will be closed immediately. > >*** The Debian TeX Team is *not* a LaTeX Help Desk *** > > If you report an error when running one of the TeX-related binaries > (latex, pdftex, metafont,...), or if the bug is related to bad or wrong > output, please include a MINIMAL example input file that produces the > error in your report. > > Please run your example with > (pdf)latex -recorder ... > (or any other program that supports -recorder) and send us the generated > file with the extension .fls, it lists all the files loaded during > the run and can easily explain problems induced by outdated files in > your home directory. > > Don't forget to also include minimal examples of other files that are > needed, e.g. bibtex databases. Often it also helps > to include the logfile. Please, never send included pictures! > > If your example file isn't short or produces more than one page of > output (except when multiple pages are needed to show the problem), > you can probably minimize it further. Instructions on how to do that > can be found at > > http://www.minimalbeispiel.de/mini-en.html (english) > > or > > http://www.minimalbeispiel.de/mini.html (german) > > ## > minimal input file > > > ## > other files > > ## > List of ls-R files > > 4 -rw-r--r-- 1 root root 2969 Mar 23 11:15 /var/lib/texmf/ls-R > 4 -rw-rw-r-- 1 root staff 80 Nov 28 12:26 /usr/local/share/texmf/ls-R > 4 -rw-r--r-- 1 root root 80 Mar 23 11:15 /usr/share/texlive/texmf/ls-R > ## > Config files > 4 -rw-r--r-- 1 root root 1656 Mar 23 11:15 /etc/texmf/web2c/texmf.cnf > 12 -rw-r--r-- 1 root root 9185 Mar 23 11:15 /var/lib/texmf/web2c/fmtutil.cnf > 0 lrwxrwxrwx 1 root root 32 Mar 14 00:52 /usr/share/texmf/web2c/updmap.cfg -> > /var/lib/texmf/updmap.cfg-DEBIAN > 12 -rw-r--r-- 1 root root 11141 Mar 23 11:15 > /var/lib/texmf/tex/generic/config/language.dat > ## > Files in /etc/texmf/web2c/ > total 8 > 4 -rw-r--r-- 1 root root 283 Jun 25 2011 mktex.cnf > 4 -rw-r--r-- 1 root root 1656 Mar 23 11:15 texmf.cnf > ## > md5sums of texmf.d > ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf > d588a08518f705d06ac262acd78f2bc4 /etc/texmf/texmf.d/20xmltex.cnf > 8e901c9e6562b73e4ba4d1b4e603412f /etc/texmf/texmf.d/30ptex.bak > 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf > 1df66bc319cec731e2
Bug#742510: xserver-xorg-video-cirrus: fails rendering xdm login fonts
On Mon, Mar 24, 2014 at 05:13:30PM +0100, Gabriele Giacone wrote: > Username one types in will not be displayed and once pressed enter > greeting and prompt fonts will not be displayed as well. Plus, by mousing over where characters should be, they appear. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742659: delaboratory: Please update to use wxwidgets3.0
Package: delaboratory
Version: 0.8-1
Severity: normal
Tags: patch
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8.
I've rebuilt your package using the attached patch (a tiny patch to
the upstream Makefile to turn off wxWidgets' debug mode was all that was
required), and did some simple testing. Everything looks good to me.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru delaboratory-0.8/debian/changelog delaboratory-0.8/debian/changelog
--- delaboratory-0.8/debian/changelog 2013-12-25 23:08:39.0 +1300
+++ delaboratory-0.8/debian/changelog 2014-03-26 13:28:29.0 +1300
@@ -1,3 +1,11 @@
+delaboratory (0.8-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0.
+ * Fix typo in package description.
+
+ -- Olly Betts Wed, 26 Mar 2014 13:27:49 +1300
+
delaboratory (0.8-1) unstable; urgency=low
* Initial upload (closes: #733068).
diff -Nru delaboratory-0.8/debian/control delaboratory-0.8/debian/control
--- delaboratory-0.8/debian/control 2013-12-25 23:50:01.0 +1300
+++ delaboratory-0.8/debian/control 2014-03-26 13:28:07.0 +1300
@@ -2,7 +2,7 @@
Section: graphics
Priority: extra
Maintainer: Laszlo Boszormenyi (GCS)
-Build-Depends: debhelper (>= 9), libtiff-dev, libwxgtk2.8-dev, libxml2-dev
+Build-Depends: debhelper (>= 9), libtiff-dev, libwxgtk3.0-dev, libxml2-dev
Standards-Version: 3.9.5
Homepage: http://code.google.com/p/delaboratory/
@@ -31,4 +31,4 @@
- histograms and color matrices
- many blend modes (multiply, screen, overlay, inverted overlay, dodge,
burn, add, grain extract, grain merge, sub, difference, darken, lighten),
-color/luminocity blending for RGB and CMYK
+color/luminosity blending for RGB and CMYK
diff -Nru delaboratory-0.8/debian/patches/series delaboratory-0.8/debian/patches/series
--- delaboratory-0.8/debian/patches/series 2013-12-25 23:47:23.0 +1300
+++ delaboratory-0.8/debian/patches/series 2014-03-26 13:37:33.0 +1300
@@ -1,2 +1,3 @@
dont_force_CPU.patch
install_destdir_support.patch
+wx3.0-compat.patch
diff -Nru delaboratory-0.8/debian/patches/wx3.0-compat.patch delaboratory-0.8/debian/patches/wx3.0-compat.patch
--- delaboratory-0.8/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ delaboratory-0.8/debian/patches/wx3.0-compat.patch 2014-03-26 13:40:04.0 +1300
@@ -0,0 +1,21 @@
+Description: Need to build with -DNDEBUG to avoid assertions
+ Upstream now defaults to enabling their "WXDEBUG" checks for incorrect API
+ usage. These assertions can be disabled by defined NDEBUG when building the
+ application - e.g. by adding -DNDEBUG to CPPFLAGS, which means such assertions
+ will be handled as they would have been by a default build of 2.8 (such as
+ that in wxgtk2.8-0). This change also means the wx-using code is compiled
+ with optimisation on.
+Author: Olly Betts
+Last-Update: 2014-03-26
+
+--- delaboratory-0.8.orig/Makefile
delaboratory-0.8/Makefile
+@@ -57,7 +57,7 @@ CXXFLAGS_WX+=-Wno-long-long -Wno-variadi
+ INCLUDES=-I gui_wx -I layers -I algorithms -I core -I properties
+
+ CXXFLAGS += ${INCLUDES}
+-CXXFLAGS_WX += ${INCLUDES}
++CXXFLAGS_WX += ${CXXFLAGS}
+
+ SOURCES_TMP = ${addsuffix .cc, ${FILES}}
+ SOURCES = ${addprefix gui_wx/, ${SOURCES_TMP}}
signature.asc
Description: Digital signature
Bug#742510: xserver-xorg-video-cirrus: fails rendering xdm login fonts
On Mon, Mar 24, 2014 at 05:13:30PM +0100, Gabriele Giacone wrote: > Downgrading to 1.4.0-2, fonts are displayed well. |_built_on_|___version___|_fonts_rendering_| | sid| 1.4.0 (*) | > BUG < | | sid| 1.5.2 | > BUG < | | wheezy | 1.4.0 | OK| |__wheezy__|___1.5.2_|___OK| (*) backported few patches to make it build -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742589: edk2: copyright file does not include reasons for being in non-free (Policy 2.5)
On Tue, 2014-03-25 at 09:34 -0700, Steve Langasek wrote: > I don't think I knew about this policy "should" (probably because I've > managed to avoid maintaining contrib/non-free packages). It is semi-recent in policy terms and I expect very few non-free/contrib packages comply with it at this stage. > Is there a recommended way to encode this in copyright-format-1.0? I think just a Comment field at the top should do it. > Should we clone this bug against policy, to codify this as part of the format? That sounds reasonable to me. > Correct. FYI I sent a mail to the Intel people asking them to remove the additional terms so that it can be in Redhat/Fedora & Debian main. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#742658: argyll: new upstream version
Source: argyll Version: 1.5.1-5 Severity: wishlist Hi. A far newer upstream version is available, which seems to include many fixes amongst others for ColorHug. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742656: several plugins (e.g. exif-display, map) don't work because of mangled shared library names
Package: eog-plugins Version: 3.12.0-1 Severity: normal dh_python3 mangles _all_ *.so files in /usr/lib/eog/plugins, even those that don't belong to a python based plugin, e.g. /usr/lib/eog/plugins/exif-display.plugin -> /usr/lib/eog/plugins/libexif- display.cpython-33m-x86_64-linux-gnu.so /usr/lib/eog/plugins/libmap.so -> /usr/lib/eog/plugins/libmap.cpython-33m- x86_64-linux-gnu.so (This didn't happen with dh_python2, since it never mangles *.so names.) dh_python3 -p$(cdbs_curpkg) --no-ext-rename /usr/lib/eog/plugins seems to do the trick. Cheers, Roderich -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.6 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eog-plugins depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-1 ii eog 3.12.0-1 ii gir1.2-gtk-3.0 3.11.8-1 ii gsettings-desktop-schemas3.12.0-1 ii libatk1.0-0 2.11.90-1 ii libc62.18-4 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libchamplain-0.12-0 0.12.7-1 ii libchamplain-gtk-0.12-0 0.12.7-1 ii libclutter-1.0-0 1.18.0-1 ii libclutter-gtk-1.0-0 1.4.4-4 ii libcogl-pango20 1.18.0-1 ii libcogl-path20 1.18.0-1 ii libcogl201.18.0-1 ii libdrm2 2.4.52-1 ii libegl1-mesa [libegl1-x11] 10.1.0-4 ii libexif120.6.21-1 ii libgbm1 10.1.0-4 ii libgdata13 0.14.1-2 ii libgdk-pixbuf2.0-0 2.30.6-1 ii libgirepository-1.0-11.39.90-4 ii libglib2.0-0 2.40.0-1 ii libgtk-3-0 3.11.8-1 ii libjson-glib-1.0-0 0.16.2-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpeas-1.0-01.9.0-2 ii libsoup2.4-1 2.46.0-1 ii libwayland-client0 1.4.0-1 ii libwayland-cursor0 1.4.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.1.0-4 ii libwayland-server0 1.4.0-1 ii libx11-6 2:1.6.2-1 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-1 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-1 ii libxi6 2:1.7.2-1 ii libxkbcommon00.4.0-1 ii libxml2 2.9.1+dfsg1-3 ii libxrandr2 2:1.4.2-1 ii python3 3.3.4-1 ii python3-gi 3.12.0-1 pn python3:any eog-plugins recommends no packages. eog-plugins suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742652: Info received (Bug#742652: Acknowledgement (wheezy/backports nginx does not include basic_auth))
oops. It happens. Thanks for following up to let us know. On Wed, 26 Mar 2014 10:48:35 +1100 Paul Morahan wrote: > stupid user error, sorry. config was missing a line terminator. > > - Paul > -- Michael Lustfield -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707268: Bug#725957: gnudatalanguage and plplot not migrating
forwarded 725957 http://sourceforge.net/p/gnudatalanguage/bugs/594/ kthxbye Hi, Thibaut Paumard wrote: > Do you need help fixing plplot and gnudatalanguage so they can reach > testing? As documented in the BTS I've forwarded the FTBFS to Sylwester Arabas (the one of the GDL upstream devs I had most contact with) by e-mail after I noticed them, but got no reply so far. He though opened an issue at their tracker just an hour ago: http://sourceforge.net/p/gnudatalanguage/bugs/594/ > I think it would make sense to maintain them in a team, either > debian-science (CC:) or debian-astro. I'm happy if someone else would help keeping GDL in Debian in shape or even wants to take over maintainership completely. We both, Gürkan and me, only maintain GDL in Debian because we need it at work. We don't use it ourselves. (I though won't join a team to maintain GDL. So if debian-science or debian-astro wants to take over, I won't join the team for that, they need to take over the package completely.) With regards to plplot: I reviewed it for sponsoring and there's a package at https://mentors.debian.net/package/plplot -- it's mostly fine with one exception, it should have version 5.9.10-1, not version 5.9.10-2. The older 5.9.10-1 package at the same location has more issues and fixing them resulted in the 5.9.10-2 upload to mentors. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Bug#742652: Info received (Bug#742652: Acknowledgement (wheezy/backports nginx does not include basic_auth))
stupid user error, sorry. config was missing a line terminator. - Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742653: [Pkg-salt-team] Bug#742653: salt-ssh search for a ssh_user key
Looks like this is an upstream bug. I'm passing it upstream with some additional comments. https://github.com/saltstack/salt/issues/11525 I think if you add: ssh_user: root to your /etc/salt/master config file, then it will work. You may also need some similar options. Thanks, Joe On Wed, Mar 26, 2014 at 10:16 AM, Gilles Mocellin < gilles.mocel...@nuagelibre.org> wrote: > Package: salt-ssh > Version: 2014.1.1+ds-1 > Severity: important > > Dear Maintainer, > > Since last upgrade (I think after 0.17, so 2014.1.0+ds-1), I can not use > anymore salt-ssh. > > Here is the backtrace : > sudo salt-ssh 'host*' test.ping > > 1 > [ERROR ] An un-handled exception was caught by salt's global exception > handler: > KeyError: 'ssh_user' > Traceback (most recent call last): > File "/usr/bin/salt-ssh", line 10, in > salt_ssh() > File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 108, in > salt_ssh > client.run() > File "/usr/lib/python2.7/dist-packages/salt/cli/__init__.py", line 369, > in run > ssh = salt.client.ssh.SSH(self.config) > File "/usr/lib/python2.7/dist-packages/salt/client/ssh/__init__.py", > line 202, in __init__ > salt.config.DEFAULT_MASTER_OPTS['ssh_user'] > > I tried to replace the user entry in my /etc/salt/roster by ssh_user, but > it's not working. > I don't know where salt search for a default master option with the name > ssh_user... > > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (101, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages salt-ssh depends on: > ii python-msgpack 0.3.0-1 > pn python:any > ii salt-common 2014.1.1+ds-1 > ii sshpass 1.05-1 > > salt-ssh recommends no packages. > > salt-ssh suggests no packages. > > -- Configuration Files: > /etc/salt/roster changed [not included] > > -- no debconf information > > ___ > pkg-salt-team mailing list > pkg-salt-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-salt-team
Bug#742004: Info received (Bug#742004: perltidy.LOG file left behind)
This bug has been traced to a memoization update which was added to speed up perltidy. A temporary workaround is to use --no-memoize, but I should have a fixed version on CPAN in a few days. Steve On Wed, Mar 19, 2014 at 7:21 AM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Perl Group > > If you wish to submit further information on this problem, please > send it to 742...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 742004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742004 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#742655: libtwin: FTBFS with libpng1.6
Source: libtwin
Version: 3.1.0-6
User: lib...@packages.debian.org
Usertags: libpng15-transition
Tags: patch
Hi,
libpng maintainers have a plan transition of libpng16[0].
libpng16 is already installed in experimental, and we are re-building
the package depending on libpng16.
As a result, we checked that your package was FTBFS.
Would you check also in your environment?
I attached a patch which revice this problem.
-
dh_auto_configure -- --enable-x11 --enable-fbdev --enable-linux-mouse
--enable-linux-joystick --enable-linux-touchscreen
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/buildd/libtwin-13.05.03.15.06-g287d16c':
configure: error: C compiler cannot create executables
See `config.log' for more details
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-
Best regards,
Nobuhiro
[0]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
libtwin-libpng16.debdiff
Description: Binary data
Bug#742653: salt-ssh search for a ssh_user key
Package: salt-ssh Version: 2014.1.1+ds-1 Followup-For: Bug #742653 Dear Maintainer, ssh_user, ssh_timeaout... are not defined in DEFAULT_MASTER_OPTS hash of /usr/lib/python2.7/dist-packages/salt/config.py from salt-common. These constants are defined in the current trunk here : https://github.com/saltstack/salt/blob/develop/salt/config.py -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages salt-ssh depends on: ii python-msgpack 0.3.0-1 pn python:any ii salt-common 2014.1.1+ds-1 ii sshpass 1.05-1 salt-ssh recommends no packages. salt-ssh suggests no packages. -- Configuration Files: /etc/salt/roster changed [not included] -- 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#738789: libhamcrest-java: FTBFS: bad class file: hamcrest-core-1.3.jar(org/hamcrest/Description.class)
This issue is really intriguing. When the build fails hamcrest-core-1.3.jar is not corrupted (verified with zip --test) and the compiled Description.class file is always the same (the md5sum is constant in all cases). The random aspect of this bug leads me to think it's a kind of race condition between the part of the build that writes the jar and the part that reads it, but everything is executed sequentially so I'm not sure how this could actually happen. On Googling the error message I found this interesting bit in a python script used by Assembla to build Ant projects: http://subversion.assembla.com/svn/sivanea/trunk/src/buildscripts/antmake.py # Experience has shown that occasionally an ant build will cause an error # like the following: ''' [javac] DellDXConnector.java:14: cannot access com.perfectsearchcorp.feed.Connector [javac] bad class file: com/perfectsearchcorp/feed/Connector.class(com/perfectsearchcorp/feed:Connector.class) [javac] unable to access file: corrupted zip file [javac] Please remove or make sure it appears in the correct subdirectory of the classpath. [javac] import com.perfectsearchcorp.feed.Connector; [javac] ^ ''' # This error appears to be caused by a bug in how either ant or java itself # manages file handles for zip files on some platforms -- I think java is # sometimes opening the file for read before the handle for write is fully # released and flushed. So it may be either an Ant bug (but I reviewed the jar task code and the files seem to be properly closed) or a JVM bug on Linux. A simple workaround would be to mount the directory containing the hamcrest-core classes into the classpath instead of using the generated jar. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742654: -U doesn't always remove empty directories
Package: cpanminus Version: 1.7001-1 I notice after using some cpanm -U commands, some empty directories are left behind. $ find perl5/ -empty |wc -l 61 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742652: Acknowledgement (wheezy/backports nginx does not include basic_auth)
This bug can be cancelled, sorry. It's something to do with puppet - I changed the puppet install from wheezy-backports to the standard wheezy repo, and I ran into the same problem: installing via puppet (backports 1.4.6 or non-backports 1.2.2), get problem. Uninstall and reinstall either nginx version manually, and the problem goes away. Unfortunately I don't have time to troubleshoot further, but this bug is in the puppet application, not nginx. Thanks - Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742653: salt-ssh search for a ssh_user key
Package: salt-ssh Version: 2014.1.1+ds-1 Severity: important Dear Maintainer, Since last upgrade (I think after 0.17, so 2014.1.0+ds-1), I can not use anymore salt-ssh. Here is the backtrace : sudo salt-ssh 'host*' test.ping 1 [ERROR ] An un-handled exception was caught by salt's global exception handler: KeyError: 'ssh_user' Traceback (most recent call last): File "/usr/bin/salt-ssh", line 10, in salt_ssh() File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 108, in salt_ssh client.run() File "/usr/lib/python2.7/dist-packages/salt/cli/__init__.py", line 369, in run ssh = salt.client.ssh.SSH(self.config) File "/usr/lib/python2.7/dist-packages/salt/client/ssh/__init__.py", line 202, in __init__ salt.config.DEFAULT_MASTER_OPTS['ssh_user'] I tried to replace the user entry in my /etc/salt/roster by ssh_user, but it's not working. I don't know where salt search for a default master option with the name ssh_user... -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages salt-ssh depends on: ii python-msgpack 0.3.0-1 pn python:any ii salt-common 2014.1.1+ds-1 ii sshpass 1.05-1 salt-ssh recommends no packages. salt-ssh suggests no packages. -- Configuration Files: /etc/salt/roster changed [not included] -- 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#732219: transition: libmikmod
On Wed, 26 Mar 2014 00:18:39 +0100, Julien Cristau wrote: > On Tue, Mar 25, 2014 at 23:27:33 +0100, Stephen Kitt wrote: > > On Tue, 18 Mar 2014 23:23:06 +0100, Stephen Kitt wrote: > > > On Tue, 18 Mar 2014 07:57:06 +0100, Julien Cristau > > > wrote: > > > > Thanks. Feel free to upload to sid. > > > > > > Done, thanks. > > > > And the whole transition is over, thanks! > > > Not quite. tome/powerpc still depends on libmikmod2 (#742598). Oops, I forgot to check non-free... Oh well. You'll know better than me what should be done with this bug (re-open or leave closed), I'll leave it to you if you don't mind... Regards, Stephen signature.asc Description: PGP signature
Bug#732219: transition: libmikmod
On Tue, Mar 25, 2014 at 23:27:33 +0100, Stephen Kitt wrote: > On Tue, 18 Mar 2014 23:23:06 +0100, Stephen Kitt wrote: > > On Tue, 18 Mar 2014 07:57:06 +0100, Julien Cristau > > wrote: > > > Thanks. Feel free to upload to sid. > > > > Done, thanks. > > And the whole transition is over, thanks! > Not quite. tome/powerpc still depends on libmikmod2 (#742598). Cheers, Julien signature.asc Description: Digital signature
Bug#742652: wheezy/backports nginx does not include basic_auth
Package: nginx
Version: 1.4.6-1~bpo70+1
1) I installed 'nginx/wheezy-backports' via puppet, and manually confirmed that
nginx, nginx-full, and nginx-common are all the same version and installed (via
'aptitude show foo')
2) On setting up a vhost with basic auth, I received a 'basic_auth is an
invalid parameter' message and nginx failed to start:
root@uncle:~/puppet# nginx -t
nginx: [emerg] invalid parameter "auth_basic" in
/etc/nginx/sites-enabled/munin:10
nginx: configuration file /etc/nginx/nginx.conf test failed
3) I couldn't successfully troubleshoot it, so I manually did 'aptitude purge
nginx nginx-full nginx-common' to get rid of the backports version
4) I then manually installed nginx from the standard wheezy repo (version
1.2.1-2.2+wheezy2). This version of nginx passed 'nginx -t' as expected
The first part of the relevant config has nothing special:
server {
listen 80 default_server
auth_basic"Restricted stats";
auth_basic_user_file /etc/nginx/conf.d/.htpasswd;
location ^~ /cgi-bin/munin-cgi-graph/ {
(blah blah blah)
I'm not particularly familiar with the details of nginx compiled modules, but
it looks like the version in wheezy-backports is missing at least the
basic_auth module, if not more.
- Paul
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742651: icc-profiles: add a location for local profiles
Package: icc-profiles Version: 2.0.1-1 Severity: wishlist Hi. I think a location for local color profiles should be shipped (and ideally other packages looking for such profiles) should be modified to look there as well,... like e.g. /usr/local/share/color/icc Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742650: gmp-doc version is obsolete, please upgrade to 6.0.0 to match libgmp-dev
Package: gmp-doc Version: 5.1.2-1 Severity: normal Now that GMP 6.0.0 is released and provided by Debian, the documentation should be updated too. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gmp-doc depends on: ii dpkg 1.17.6 ii install-info 5.2.0.dfsg.1-2 gmp-doc recommends no packages. gmp-doc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742512: lm-sensors and kernel linux 3.13-1 does not work fine
On Mon, Mar 24, 2014 at 05:30:56PM +0100, merlin wrote: > Package: lm-sensors > Version: 1:3.3.4-2 > Severity: important > > Dear Maintainer, > > > When i move to linux 3.13-1 i remark that the fan of my computer HP 6830S > work by in blow and when i observe the temperature given by sensors the > temperature are very high so it's must be critical for the computer. > sensors : lm-sensors doesn't control the fan, it only display the temperatures returned by the sensors. Have you configured fancontrol to control the fan or did you leave the BIOS of you computer handling that (which is fine if it worked with 3.12)? -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742649: icc-profiles: include sRGB_v4_ICC_preference_displayclass.icc
Package: icc-profiles Version: 2.0.1-1 Severity: wishlist Hi. Perhaps it makes sense to include sRGB_v4_ICC_preference_displayclass.icc from http://www.color.org/srgbprofiles.xalter as well. btw: I've noted that the sRGB profile in the package differs from that e.g. shipped by Microsoft... any idea why? Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712167: dbus: add upstart init support
I have attached a deb diff that includes an upstart job. It is
different from the previous diff by Dimitri because it prompts for a
reboot in the post installation regardless, per Simon McVittie's
suggestion. It also uses the --nopidfile option to start dbus.
Please consider this for inclusion,
--
Cameron Norman
diff -Nru dbus-1.8.0/debian/changelog dbus-1.8.0/debian/changelog
--- dbus-1.8.0/debian/changelog 2014-02-26 05:15:58.0 -0800
+++ dbus-1.8.0/debian/changelog 2014-03-25 15:32:27.0 -0700
@@ -1,3 +1,15 @@
+dbus (1.8.0-2.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Add Upstart integration:
+- Check if init is upstart in the init.d script and exit
+ appropiately
+- Add Upstart job
+- Depend on lsb-base that provides init_is_upstart function
+- Prompt for reboot on post-install always
+
+ -- Cameron Norman Tue, 25 Mar 2014 15:29:17 -0700
+
dbus (1.8.0-2) unstable; urgency=low
* debian/rules: look for DEB_BUILD_PROFILES, the new name for
diff -Nru dbus-1.8.0/debian/control dbus-1.8.0/debian/control
--- dbus-1.8.0/debian/control 2014-02-26 05:15:58.0 -0800
+++ dbus-1.8.0/debian/control 2014-03-25 15:29:10.0 -0700
@@ -57,7 +57,7 @@
Depends: ${shlibs:Depends},
${misc:Depends},
adduser,
- lsb-base (>= 3.2-14)
+ lsb-base (>= 4.1+Debian3)
Suggests: dbus-x11
Multi-Arch: foreign
Description: simple interprocess messaging system (daemon and utilities)
diff -Nru dbus-1.8.0/debian/dbus.init dbus-1.8.0/debian/dbus.init
--- dbus-1.8.0/debian/dbus.init 2014-02-26 05:15:58.0 -0800
+++ dbus-1.8.0/debian/dbus.init 2014-03-25 15:27:16.0 -0700
@@ -97,6 +97,17 @@
log_action_end_msg $?
}
+if init_is_upstart; then
+ case "$1" in
+stop)
+ exit 0
+;;
+*)
+ exit 1
+;;
+ esac
+fi
+
case "$1" in
start)
start_it_up
diff -Nru dbus-1.8.0/debian/dbus.postinst dbus-1.8.0/debian/dbus.postinst
--- dbus-1.8.0/debian/dbus.postinst 2014-02-26 05:15:58.0 -0800
+++ dbus-1.8.0/debian/dbus.postinst 2014-03-25 14:51:12.0 -0700
@@ -38,11 +38,9 @@
# system bus is not supported by upstream). The code added by
# dh_installinit -r creates a start action, below.
-if [ -x "/etc/init.d/dbus" ] && /etc/init.d/dbus status > /dev/null; then
-# trigger an update notification which recommends to reboot
-[ -x /usr/share/update-notifier/notify-reboot-required ] && \
-/usr/share/update-notifier/notify-reboot-required || true
-fi
+# trigger an update notification which recommends to reboot
+[ -x /usr/share/update-notifier/notify-reboot-required ] && \
+/usr/share/update-notifier/notify-reboot-required || true
fi
# This is what the init script would do, but it's simpler (and less
diff -Nru dbus-1.8.0/debian/dbus.upstart dbus-1.8.0/debian/dbus.upstart
--- dbus-1.8.0/debian/dbus.upstart 1969-12-31 16:00:00.0 -0800
+++ dbus-1.8.0/debian/dbus.upstart 2014-03-25 15:24:38.0 -0700
@@ -0,0 +1,25 @@
+# dbus - D-Bus system message bus daemon
+#
+# The D-Bus system message bus allows system daemons
+# and user applications to communicate.
+
+description "dbus - D-Bus system message bus daemon"
+
+start on local-filesystems
+stop on deconfiguring-networking
+
+oom score -900
+
+expect fork
+respawn
+
+pre-start script
+ mkdir -p /var/run/dbus
+ chown messagebus:messagebus /var/run/dbus
+
+ exec dbus-uuidgen --ensure
+end script
+
+exec dbus-daemon --system --nopidfile --fork
+
+post-start exec kill -USR1 1
Bug#742648: gnome-control-center: When trying to change the background, the control center crash
Package: gnome-control-center Version: 1:3.8.3-4 Severity: minor Dear Maintainer, When trying to change the background in gnome, the control center crashes. Neither can it be changed by right clicking in the desktop. Greetings -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_CR.utf8, LC_CTYPE=es_CR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.34-2 ii apg2.2.3.dfsg.1-2 ii colord 1.0.6-1 ii desktop-file-utils 0.22-1 ii gnome-control-center-data 1:3.8.3-4 ii gnome-desktop3-data3.8.4-2 ii gnome-icon-theme 3.10.0-1 ii gnome-icon-theme-symbolic 3.10.1-1 ii gnome-menus3.8.0-2 ii gnome-settings-daemon 3.8.5-2 ii gsettings-desktop-schemas 3.8.2-2 ii libaccountsservice00.6.34-2 ii libatk1.0-02.10.0-2 ii libc6 2.18-4 ii libcairo2 1.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcheese-gtk233.10.1-1sid1 ii libcheese7 3.10.1-1sid1 ii libclutter-gtk-1.0-0 1.4.4-3 ii libcolord-gtk1 0.1.25-1.1 ii libcolord1 1.0.6-1 ii libcups2 1.7.1-7 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-2 ii libgdk-pixbuf2.0-0 2.30.6-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglib2.0-0 2.38.2-5 ii libgnome-bluetooth11 3.8.1-2 ii libgnome-desktop-3-7 3.8.4-2 ii libgoa-1.0-0 3.8.3-2 ii libgtk-3-0 3.10.7-1 ii libgtop2-7 2.28.5-2 ii libibus-1.0-5 1.5.5-1 ii libkrb5-3 1.12+dfsg-2 ii libnm-glib-vpn10.9.8.0-5 ii libnm-glib40.9.8.0-5 ii libnm-gtk0 0.9.8.4-1 ii libnm-util20.9.8.0-5 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-01.36.2-2 ii libpolkit-gobject-1-0 0.105-4 ii libpulse-mainloop-glib04.0-6+b1 ii libpulse0 4.0-6+b1 ii libpwquality1 1.2.3-1 ii libsmbclient 2:4.1.6+dfsg-1 ii libsocialweb-client2 0.25.20-6 ii libupower-glib10.9.23-2+b1 ii libwacom2 0.8-1 ii libx11-6 2:1.6.2-1 ii libxi6 2:1.7.2-1 ii libxml22.9.1+dfsg1-3 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.5-2 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.8.3-2 ii gnome-user-guide 3.8.2-1 ii gnome-user-share 3.8.3-1 ii iso-codes 3.51-1 ii mesa-utils 8.1.0-2+b1 ii mousetweaks3.10.0-1 ii network-manager-gnome 0.9.8.4-1 ii ntp1:4.2.6.p5+dfsg-3 ii policykit-1-gnome 0.105-2 ii rygel 0.20.3-1 ii rygel-tracker 0.20.3-1 ii system-config-printer 1.4.3-4 Versions of packages gnome-control-center suggests: ii gnome-screensaver3.6.1-1 ii gstreamer1.0-pulseaudio 1.2.3-1 ii libcanberra-gtk-module 0.30-2 ii libcanberra-gtk3-module 0.30-2 ii x11-xserver-utils7.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#742636: wheezy-pu: package spip/2.1.17-1+deb7u4
Hi, > Please go ahead. Thanks Adam for your quick ACK, uploaded. Regards David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742647: Please add gstreamer0.10-alsa to default install - or as a dependency gstreamer-based mediaplayers
Package: installation-reports Boot method: Graphical installer boot option from Debian LXDE Live CD Image version: debian-live-7.4-i386-lxde-desktop.iso Date: 25 March 2014 Machine: n/a Processor: n/a Memory: n/a Partitions: n/a Snippet of the output of lspci -v: 00:06.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a) Subsystem: Creative Labs Gameport Joystick Flags: bus master, medium devsel, latency 32 I/O ports at ec00 [size=8] Capabilities: Kernel driver in use: Emu10k1_gameport Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Nice installer! :-) However, can I please recommend adding the following package to the default Debian LXDE LIVE CD install please: gstreamer0.10-alsa. Or maybe consider asking media player packagers to add this as a dependency please. The default install uses ALSA, and without this package, media players such as Clementine, Banshee, Rhythmbox, etc, would output constant spluttering/stuttering for me. VLC worked fine as it could detect ALSA. I am guessing that without this package, pretty much any media player that uses gstreamer won't work with ALSA (at least on my setup) unless you can manually select ALSA as an output option. And none of the media players that I tried automatically installed this package for me when installing them - and I tried quite a few media players. Thanks in advance for your consideration. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718434: fixed in ca-certificates 20140223
On Tue, 2014-03-25 at 18:58 +0100, Bas Wijnen wrote: > No, the point is that an attacker is detectable. Why should he be? And even if he was... if I already sent my valuable data, then it's too late. > Do you think the NSA > does MITM attacks on all connections? I seriously thought that they > might. Well the question is less whether they actually try it with any connection... which is of course unlikely since people would notice that far to easy... the question is rather whether they could do it with all connections... and I guess that might be the case... the only thing they need to do is to hijack only such connections for which they know no verification will be made. > If the NSA starts doing this, someone will catch them. That will be big > news and everyone will start checking their keys. I doubt that... and how should it work anyway? How can I check the public key of my e.g. bank? Right now, only by trusting Verisign&friends... which again are all under the control of NSA&friends. > Well, not exactly, of course. It is still very likely that they are > trying to (and also that they succeeded to) put back doors into the > encryption protocols, or at least their implementations. Sure but that's another field... > Depending on what you mean by "sitting on the line". They can always > read, but to tamper they need to sit "in" the line, not just on it. > They have to make sure the original packets don't reach their > destination. I take it that's what you mean. > > (Note that this is a much smaller group of machines; for example, I can > read all traffic on the subnet of my block of houses, but I can't > effectively tamper with it.) Well if one has to assume that they sit "in" the big internet exchange points... this already gives them a lot... > But if they start to doubt, they can check if they have been attacked, > by comparing their keys through an independent channel. Well but that simply doesn't happen, does it? At least since Snowden, all world should really know: NSA&friends spy _everything_ ... I mean most of use expected it for sure before... but now there is no way to not know. And what changed? Well we still have the broken X.509 strict hierarchical trust model,... and it won't go away very soon. Of course the NSA won't issue forged certs (by forcing verisign&friends) at large (because that would be rather easily noticed) but they will do so for targets worth it. So people must have your "doubts" by know, but nothing really changes. Actually the contrary... like e.g. Debian who puts its own certificates under some commercial CA now, instead of using its own, which people could really trust (well at least as much as they can trust Debian itself). > If any of them is found to be under > attack, more checks will be done; if many of those will fail, all hell > will break loose. You can be sure that they do all this... and no hell broke loose. > to convince people that > not encrypting is better than encrypting with unchecked keys. Well that's not what I said... I rather say the later is simply not enough. > You're claiming that having an evil CA in the list means that my > communication is in danger of being eavesdropped. I'm saying that this > is nonsense, because: > > > > An evil CA cannot read your traffic (unless they are in > > > the path of your communication). > > You are saying that the NSA has control over evil CAs, and also is in > the path of communication. So they can eavesdrop. Technically this is > true. But there are two things to consider: > > 1. Due to the fact that they would be detected if they tried this on a >large scale, they won't actually do this. Well first... why is an attack only a problem if it's done at large scale? If the NSA does this only for the Snowdens, Applebaums, etc. ... then this is enough for them... Secondly,... "being detected" in that case means, that someone trustworthy regularly scans for forged certificates... (in the sense of having a different fingerprint, than the ones from the same CA, which are however known to be in the possession of their rightful owner). - This is difficult by the mass of certificates... even for single companies like google you have gazillions of domains and even more certs... This is the reason why programs like certificate patrol are only little helpful in practise. - It would need to mean, that this someone is not under the control of such government (also, not necessarily the case). - It would need to mean, that that someone does actually know the correct cert (if he only ever saw the forged one, he will never notice it). - And it would need to mean that the rightful owner is not evil... or not forced to be evil (by law)... which we again know is the case at least in the US. So you may be "lucky" to notice such forgery... but there is no guarantee. Anyway... the topic of that bug was rather the CAcert certificate... and I think Debian is doing very bad if it tries to give any
Bug#717805: Adding an advice about lsinitramfs is not working when hit this bug ?
Hello,
While the patch at 22 comment in this bug [1] is not accepted (can you
clarify why it is not accepted or applied?), I suggest adding an
advice to script.
Next patch could be useful for some of Debian Users:
--- lsinitramfs.orig2014-03-25 21:55:07.704334678 +0100
+++ lsinitramfs2014-03-25 23:08:06.132850281 +0100
@@ -54,7 +54,9 @@
bzip2 -c -d "$initramfs" | cpio ${cpio_args}
elif lzop -t "$initramfs" >/dev/null 2>&1 ; then
lzop -c -d "$initramfs" | cpio ${cpio_args}
+elif file "$initramfs" | grep -q "cpio archive" ; then
+echo "This tool is not ready for not compressed initramfs
files." >&2
+echo "See http://bugs.debian.org/717805 for more info"
fi
-
fi
done
Thank you very much
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717805#22
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742536: Re: Bug#742536: lists.debian.org: New mailing list: debian-ppc64el
On Tue, 25 Mar 2014, Breno Leitao wrote: > > tbh I don't think another list is needed for this subarch. We also only have > > one arm list. debian-ppc (which I still read) isn't very high traffic, so a > > little bit more traffic would be good for the list. > Right. I tend to agree with you. So, we will start to track this new port into > debian-powerpc mailing list. great. Thanks Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720831: fixed
[Bastian Blank] > Hi > > I pushed a fix. It is also attached. Please test. Thank you very much. :) Testing now, and a DVD which used to fail imediately did now start to rip as it should. I'll know in an hour or so if it really worked, but by that time I'll be sleeping. I'll test the other patch tomorrow, and try to play the ISOs to verify that the resulting file is working. :) -- 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#742637: squeeze-pu: package spip/2.1.1-3squeeze9
Hi, > Please go ahead Thanks Adam for your quick ACK, uploaded. Regards David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742618: missing cups enable in configure, so xfe don't have printing support if recompile
Hello! Thank you for your bug report. I will look for this problem. --- Have a nice day. Joachim (Germany) signature.asc Description: PGP signature
Bug#742457: iceweasel: iceseasel UI unresponsive
After a reboot, Iceweasel was responsive again.
Bug#742646: pyrit: FTBFS on hurd-i386
Source: pyrit Version: 0.4.0-3 Severity: important Pyrit FTBFS on hurd-i386 because of an inactivity timeout. The logs show that prior to that, some unit tests failed. The failure is identical to the failure of 0.4.0-2, which was built-attempted on two separate machines. So this probably requires investigation on a porter box. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660559: rhythmbox: playlists are destroyed when media files moves or gets deleted
2014-03-02 23:57, althaser skrev: Hey Anton, Could you please still reproduce this issue with newer rhythmbox version like 2.97-2.1 or 3.0.1-1+b1 ? thanks regards althaser Hi! I can reproduce this with Rhythmbox 3.0.1 in Arch Linux. I currently don't use Debian on my desktop computer. -- Best Regards, Anton Eliasson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742645: nvidia-kernel-dkms: fails to build with linux-image-3.14-rc7-amd64 from experimental
Package: nvidia-kernel-dkms Version: 331.49-1 Severity: important root@sid:/etc# dpkg-reconfigure nvidia-kernel-dkms Uninstall Beginning Module: nvidia-current Version: 331.49 Kernel: 3.13-1-amd64 (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/3.13-1-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod DKMS: uninstall completed. -- Deleting module version: 331.49 completely from the DKMS tree. -- Done. Loading new nvidia-current-331.49 DKMS files... Building for 3.13-1-amd64 and 3.14-rc7-amd64 Building initial module for 3.13-1-amd64 Done. nvidia-current: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.13-1-amd64/updates/dkms/ depmod DKMS: install completed. Building initial module for 3.14-rc7-amd64 Error! Bad return status for module build on kernel: 3.14-rc7-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/331.49/build/make.log for more information. make.log is attached. [snip irrelevant reportbug additions] -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nvidia-kernel-dkms depends on: ii dkms 2.2.0.3-1.2 ii nvidia-alternative [nvidia-alternative--kmod-alias] 331.49-1 ii nvidia-installer-cleanup 20131102+1 ii nvidia-kernel-common 20131102+1 Versions of packages nvidia-kernel-dkms recommends: ii nvidia-driver 331.49-1 nvidia-kernel-dkms suggests no packages. Versions of packages nvidia-driver depends on: ii libc6 2.18-4 ii libgl1-nvidia-glx 331.49-1 ii libnvidia-ml1 331.49-1 ii nvidia-alternative 331.49-1 ii nvidia-installer-cleanup 20131102+1 ii nvidia-support 20131102+1 ii nvidia-vdpau-driver331.49-1 ii xserver-xorg-video-nvidia 331.49-1 Versions of packages nvidia-driver recommends: ii nvidia-settings 319.82-1 nvidia-driver suggests no packages. Versions of packages libgl1-nvidia-glx depends on: ii libc6 2.18-4 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii multiarch-support 2.18-4 ii nvidia-alternative331.49-1 ii nvidia-installer-cleanup 20131102+1 ii nvidia-support20131102+1 libgl1-nvidia-glx recommends no packages. libgl1-nvidia-glx suggests no packages. Versions of packages xserver-xorg-video-nvidia depends on: ii debconf [debconf-2.0] 1.5.52 ii libc6 2.18-4 ii libgl1-nvidia-glx 331.49-1 ii nvidia-alternative 331.49-1 ii nvidia-installer-cleanup 20131102+1 ii nvidia-support 20131102+1 ii xserver-xorg-core [xorg-video-abi-15] 2:1.15.0-2 Versions of packages xserver-xorg-video-nvidia recommends: ii nvidia-driver331.49-1 ii nvidia-settings 319.82-1 ii nvidia-vdpau-driver 331.49-1 xserver-xorg-video-nvidia suggests no packages. Versions of packages nvidia-alternative depends on: ii glx-alternative-nvidia 0.4.1 Versions of packages glx-alternative-nvidia depends on: ii glx-alternative-mesa 0.4.1 ii glx-diversions0.4.1 Versions of packages glx-alternative-nvidia suggests: ii nvidia-driver 331.49-1 Versions of packages nvidia-kernel-dkms is related to: pn ia32-libs pn libdrm-nouveau1 pn libdrm-nouveau1a ii libdrm-nouveau22.4.52-1 pn libgl1-nvidia-alternatives-ia32 ii libgl1-nvidia-glx [libgl1-nvidia-glx-any] 331.49-1 pn libgl1-nvidia-glx-ia32 pn libgl1-nvidia-glx-ia32-any pn libgl1-nvidia-legacy-173xx-glx-ia32 pn libgl1-nvidia-legacy-96xx-glx-ia32 pn linux-headers ii nvidia-driver [nvidia-glx-any] 331.49-1 pn nvidia-glx ii nvidia-kernel-common
Bug#742644: nagvis: Livestatus dependency
Package: nagvis Version: 1:1.7.10+dfsg1-2 Severity: minor Hi, The check-mk-livestatus dependency is not completely true. If you use Nagvis with Shinken, check-mk-livestatus package is useless. Maybe this is more a recommend dependency ? Thank. -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nagvis depends on: ii check-mk-livestatus1.2.2p3-1 ii debconf [debconf-2.0] 1.5.52 ii dpkg 1.17.6 ii graphviz 2.26.3-16.2 ii php-gettext1.0.11-1 ii php-net-socket 1.0.14-1 ii php5 5.5.9+dfsg-1 ii php5-common5.5.9+dfsg-1 ii php5-gd5.5.9+dfsg-1 ii php5-sqlite5.5.9+dfsg-1 ii ucf3.0027+nmu1 nagvis recommends no packages. Versions of packages nagvis suggests: pn nagvis-demos -- debconf information: nagvis/delete_on_purge: false * nagvis/monitoring_system: shinken -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741236: [Pkg-xfce-devel] Bug#741236: lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.2-1 update happened
tomorrow i will install with the kde greeter and try some tests thanks for the work :) On 03/25/2014 10:09 PM, Yves-Alexis Perez wrote: On Mon, Mar 10, 2014 at 10:38:08AM +0100, lauren wrote: Package: lightdm-gtk-greeter Version: 1.8.2-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? apt-get update / apt-get upgrade * What exactly did you do (or not do) that was effective (or ineffective)? i have to hard power down my system and to start again and hope it works * What was the outcome of this action? randomly i can log in and other times it just hangs after i press enter with my credentials inputted * What outcome did you expect instead? to log in and actually use my system *** End of the template - remove these template lines *** If you manage to reproduce somehow consistently with lightdm-gtk-greeter, can you try with another greeter and see if it happens again? It'd help actually pinpointing if the problem lies in lightdm or the greeter. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741236: [Pkg-xfce-devel] Bug#741236: lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.2-1 update happened
On Mon, Mar 10, 2014 at 10:38:08AM +0100, lauren wrote: > Package: lightdm-gtk-greeter > Version: 1.8.2-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > apt-get update / apt-get upgrade > >* What exactly did you do (or not do) that was effective (or > ineffective)? > i have to hard power down my system and to start again and hope it works > >* What was the outcome of this action? > randomly i can log in and other times it just hangs after i press enter with > my credentials inputted > >* What outcome did you expect instead? > to log in and actually use my system > > *** End of the template - remove these template lines *** If you manage to reproduce somehow consistently with lightdm-gtk-greeter, can you try with another greeter and see if it happens again? It'd help actually pinpointing if the problem lies in lightdm or the greeter. Regards, -- Yves-Alexis Perez signature.asc Description: Digital signature
Bug#571120: pisa need python-reportlab >= 2.2
Package: python-pisa Version: 3.0.32-1 Followup-For: Bug #571120 Control: tag -1 upstream Bumping severity to RC, since with python-reportlab 3 in sid this package is now fatally broken. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pisa depends on: ii python2.7.5-5 ii python-html5lib 0.999-2 ii python-imaging2.3.0-2 ii python-pypdf 1.13-1 ii python-reportlab 3.0-1 ii python-support1.0.15 python-pisa recommends no packages. python-pisa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742641: Acknowledgement (Fails to run: [error] client.go:2298 Error getting size: bad file descriptor)
FWIW: according to https://github.com/ubergarm/debian-docker-runit it boils down to cgroups mounts -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. 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#742642: iotop reports gnome-shell I/O% but no disk I/O being done
Package: iotop Version: 0.6-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? iotop -o shows gnome-shell doing I/O (non-zero '%I/O' value) when in fact no disk I/O is being done by gnome-shell. * What exactly did you do (or not do) that was effective (or ineffective)? ran iotop -o to show tasks doing current I/O * What was the outcome of this action? A few threads show up in each screen, with gnome-shell consistently showing at or near the top of the '%I/O' column, but no disk I/O was shown in the top summary or any of the individual process lines. * What outcome did you expect instead? Investigation of the gnome-shell process via strace and /proc//fd showed the recvmsg and writev I/O being done to Unix sockets, not files on disk. I think this may be a quirk (or maybe bug) in the netlink/taskstats interface where Unix socket I/O is being counted as block I/O. I will try and write a test program to loop doing socket I/O and see if iotop shows it doing a % of I/O. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13.5-1inter04-686-pae (SMP w/2 CPU cores; PREEMPT) 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/dash Versions of packages iotop depends on: ii python 2.7.5-5 iotop recommends no packages. iotop suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742640: src:eglibc: build stage2 without selinux
Package: src:eglibc Version: 2.18-4 Severity: wishlist Tags: patch The eglibc package currently lacks a stage2 build profile entirely. A stage2 is needed though, because libselinux cannot be built without an actual libc among other things and eglibc explicitly enabled selinux via a configure flag. The attached patch removes that flag when the package is built with dpkg-buildpackage -Pstage2. Note that I did not convert the stage1 code to comply with the build profile spec. Thus eglibc now evaluates DEB_STAGE or DEB_BUILD_PROFILE (singular) for stage1 and DEB_BUILD_PROFILES (plural, in accordance with build profile spec) for stage2. Not all architectures successfully build a stage2 with this patch, but arm64, armel, armhf and m68k do. Helmut diff -Nru eglibc-2.18/debian/sysdeps/linux.mk eglibc-2.18/debian/sysdeps/linux.mk --- eglibc-2.18/debian/sysdeps/linux.mk +++ eglibc-2.18/debian/sysdeps/linux.mk @@ -12,7 +12,11 @@ ifeq ($(DEB_BUILD_PROFILE),bootstrap) libc_extra_config_options = $(extra_config_options) else - libc_extra_config_options = --with-selinux $(extra_config_options) + ifneq ($(filter stage2,$(DEB_BUILD_PROFILES)),) +libc_extra_config_options = $(extra_config_options) + else +libc_extra_config_options = --with-selinux $(extra_config_options) + endif endif ifndef LINUX_SOURCE
Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)
Copying various Kirkwood upstream kernel people: we received some bug
reports in Debian on SATA timing issues on boot on QNAP devices.
Apparently QNAP put in an mdelay hack in their kernel to make it work.
Below is Martin Waschbuesch's report and you can find some more
information at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714959
Is this a known issue?
* Martin Waschbuesch [2013-07-04 19:12]:
> Package: src:linux
> Version: 3.2.46-1
> Severity: normal
> Tags: upstream patch
>
> Dear Maintainer,
>
> On my QNAP TS-412, after a clean install of Wheezy, the kernel fails to bring
> up all sata ports (using Marvell 88SX7042 via sata_mv driver) before md/raid
> tries to assemble the array.
> The same disks/array work in a different model (TS-410) and the drives/array
> from said TS-410 also fail in my TS-412.
> At the same time, using the original QNAP firmware, everything works as
> expected.
> The only discernable differences between the devices that I could find (they
> share the exact same SoC and SATA Model ID and revision), apart from the core
> clock speed, is that the TS-412 shows some sort of spin-up delay / staggering
> behaviour while the TS-410 does not.
> Now, having had a look at the most recent GPL code package from QNAP that I
> could find here:
> http://sourceforge.net/projects/qosgpl/
> I found that they have a version 3.4.6 kernel tree.
> The file drivers/ata/sata_mv.c contains some changes regarding the delay
> while initializing the hardware.
> Using this as a blueprint, I patched the linux-image-3.2.0-4 source file
> accordingly.
> The resulting kernel works for me: The delay ensures that all drives are up
> and the raid array comes up.
>
> I discussed this with others on debian-...@lists.debian.org and while we
> agree that this kind of patch is a mere band-aid, we wanted to point out that
> there may be some issue concerning timing/delays with this kernel module.
>
> Maybe there is a more elegant / targeted approach to solving this?
...
> #define DRV_VERSION "1.28"
>
> +//Patch by QNAP: delay SATA disk initialization
> +#define QMV_SATA_INIT_DELAY_PHASE 5000 //milliseconds
> +
> +
> /*
> * module options
> */
> @@ -4329,7 +4333,11 @@
> struct ata_port *ap = host->ports[port];
> void __iomem *port_mmio = mv_port_base(hpriv->base, port);
> unsigned int offset = port_mmio - hpriv->base;
> -
> + // marvell 7042 port 2 port 3 will power on by order every 5
> sec
> + if( (port==2) || (port == 3) ){
> + printk("Wait %d seconds to initialize scsi
> %d.\n",QMV_SATA_INIT_DELAY_PHASE/1000,port);
> + mdelay(QMV_SATA_INIT_DELAY_PHASE);
> + }
> ata_port_pbar_desc(ap, MV_PRIMARY_BAR, -1, "mmio");
> ata_port_pbar_desc(ap, MV_PRIMARY_BAR, offset, "port");
> }
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734626: fonts-opendin: Typo in Menu Name of Font (Eng*sh*rift instead of Engschrift)
[cc-ing Paulo Silva, who's upstream for this font, because the problem seems to originate from the upstream source] Hi Ralph, you're correct about the typo. The problem, though, is that the typo in the font name appears to come from the upstream source. You can verify it going to the homepage of the project [1], downloading the .zip and unzipping it: madamezou@malatesta:~/bugs$ unzip 107153-OpenDinSchriftenEngschrift.zip Archive: 107153-OpenDinSchriftenEngschrift.zip creating: OpenDinSchriftenEngschrift/ inflating: OpenDinSchriftenEngschrift/About.txt inflating: OpenDinSchriftenEngschrift/OFL.txt inflating: OpenDinSchriftenEngschrift/OpenDinSchriftenEngshrift.otf inflating: OpenDinSchriftenEngschrift/OpenDinSchriftenEngshrift.sfd inflating: OpenDinSchriftenEngschrift/OpenDinSchriftenEngshrift.svg inflating: OpenDinSchriftenEngschrift/OpenDinSchriftenEngshrift.ttf So: the archive and the directory names are correct, the filenames and the metadata of the font contain the typo. While it's certainly possible to fix it in the Debian package, maybe it's even better if upstream fixes it directly in the source? Cheers, Francesca [1] http://kde-look.org/content/show.php/Open+Din+Schriften+Engschrift?content=107153 -- "I will not be reconstructed" The Pogues, Sunny Side of the Street signature.asc Description: Digital signature
Bug#742641: Fails to run: [error] client.go:2298 Error getting size: bad file descriptor
Package: docker.io Version: 0.9.0+dfsg1-1 Severity: important I had some previous installation installed, so for clean "run" stopped docker.io service, reinstalled docker.io package, and redid run $> sudo docker.io --debug run -i -t debian:wheezy /bin/sh Unable to find image 'debian:wheezy' locally Pulling repository debian b5fe16f2ccba: Download complete 511136ea3c5a: Download complete 584162d19e17: Download complete [debug] client.go:2252 [hijack] End of stdout [error] client.go:2315 Error resize: Error: bad file descriptor [debug] client.go:1844 End of CmdRun(), Waiting for hijack to finish. Log: 2014/03/25 16:48:03 POST /v1.10/containers/create [/var/lib/docker|480934b7] +job create() No such image: debian:wheezy (tag: wheezy) [/var/lib/docker|480934b7] -job create() = ERR (1) [error] server.go:951 Error: No such image: debian:wheezy (tag: wheezy) [error] server.go:86 HTTP Error: statusCode=404 No such image: debian:wheezy (tag: wheezy) 2014/03/25 16:48:03 POST /v1.10/images/create?fromImage=debian&tag=wheezy [/var/lib/docker|480934b7] +job pull(debian, wheezy) [/var/lib/docker|480934b7] -job pull(debian, wheezy) = OK (0) 2014/03/25 16:48:20 POST /v1.10/containers/create [/var/lib/docker|480934b7] +job create() [/var/lib/docker|480934b7] -job create() = OK (0) 2014/03/25 16:48:20 POST /v1.10/containers/f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66/attach?stderr=1&stdin=1&stdout=1&stream=1 [/var/lib/docker|480934b7] +job inspect(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, container) [/var/lib/docker|480934b7] -job inspect(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, container) = OK (0) [/var/lib/docker|480934b7] +job attach(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) 2014/03/25 16:48:20 POST /v1.10/containers/f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66/start [/var/lib/docker|480934b7] +job start(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) [/var/lib/docker|480934b7] +job allocate_interface(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) [/var/lib/docker|480934b7] -job allocate_interface(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) = OK (0) [/var/lib/docker|480934b7] -job start(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) = OK (0) [error] container.go:784 Error running container: mkdir /sys/fs/devices: no such file or directory [/var/lib/docker|480934b7] +job release_interface(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) [/var/lib/docker|480934b7] -job release_interface(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) = OK (0) [error] container.go:841 f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66: Error closing terminal: invalid argument [/var/lib/docker|480934b7] -job attach(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66) = OK (0) 2014/03/25 16:48:20 POST /v1.10/containers/f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66/resize?h=25&w=130 [/var/lib/docker|480934b7] +job resize(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, 25, 130) bad file descriptor [/var/lib/docker|480934b7] -job resize(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, 25, 130) = ERR (1) [error] server.go:951 Error: bad file descriptor [error] server.go:86 HTTP Error: statusCode=500 bad file descriptor 2014/03/25 16:48:20 GET /v1.10/containers/f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66/json [/var/lib/docker|480934b7] +job inspect(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, container) [/var/lib/docker|480934b7] -job inspect(f03353ad06d52aa88fa788403e00f810fdf872e7a4ceb6ac65dfd9cf5bee6d66, container) = OK (0) 2014/03/25 16:49:31 POST /v1.10/containers/create [/var/lib/docker|480934b7] +job create() [/var/lib/docker|480934b7] -job create() = OK (0) 2014/03/25 16:49:31 POST /v1.10/containers/ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db/attach?stderr=1&stdin=1&stdout=1&stream=1 [/var/lib/docker|480934b7] +job inspect(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db, container) [/var/lib/docker|480934b7] -job inspect(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db, container) = OK (0) [/var/lib/docker|480934b7] +job attach(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db) 2014/03/25 16:49:31 POST /v1.10/containers/ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db/start [/var/lib/docker|480934b7] +job start(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db) [/var/lib/docker|480934b7] +job allocate_interface(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db) [/var/lib/docker|480934b7] -job allocate_interface(ca1614f7eefd6df6824e063a440ad67a251a007642d4fb25026f7de4b36b81db) = OK (0) [err
Bug#740683: provide web service client package via stable-updates
On Sat, 2014-03-08 at 15:24 +, Adam D. Barratt wrote: > I'm not sure what comments you're after here. > > As with any package, if an update is available in proposed-updates and > there's an argument to make it also available via -updates, we're happy > to look at that. > > However, packages aren't going to magically appear in -updates - someone > needs to produce a package that runs on stable, test it and propose an > update via the usual process (i.e. a "pu" bug against the > release.debian.org pseudo-package). > > I'm also not really sure why this discussion is being had in a bug > report, as there isn't a closing "action" as such. If the intent was > some form of blanket statement that any such update would automatically > be accepted, I don't think that's appropriate; OMMV. Ping? If there's no reply in another week then I'll close this bug, as there doesn't seem to be anything directly actionable. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616290: isc-dhcp: Updated patches for GNU/Hurd
On Tue, 2014-03-25 at 21:39 +0100, Samuel Thibault wrote: > Svante Signell, le Tue 25 Mar 2014 21:36:45 +0100, a écrit : > > On Tue, 2014-03-25 at 21:21 +0100, Samuel Thibault wrote: > > > > > I have pushed all that in a commit, which you can pull from the > > > experimental branch of > > > ssh://alioth.debian.org/srv/home/users/sthibault/isc-dhcp.git > > > > > > I plan to NMU these changes to experimental. > > > > Samuel, what happened to patch-osdep? > > It is replaced by just setting export DO_LPF=1 from rules. So you wanted to avoid upstream involvement to keep things debian only, wise :-) Especially when considering the maintainer's note about NMU-ing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742009: liferea: New upstream release 1.10.7
On 25/03/14 21:31, Paul Gevers wrote: > On 24-03-14 07:41, David Smith wrote: >> Hmm.. Have you tried moving ~/.config/liferea out of the way to reset >> your configuration to the defaults and then try loading up liferea >> again? > > No I haven't yet. > >> On another note, I believe I've got 1.10.7-1 in the git repo all set for >> a review for upload into unstable. > > So you want me to upload? This means that you consider the bug we have > been discussing so far as not the regression you thought it to be? > >> Let me know if you find any problems. > > Yes, I like to fix bug 738099. David, I assume you want to claim > maintainership of liferea. I think you deserve it, so please do (unless > Emilio now starts complaining). I'm fine with that. David, you've done an amazing job at taking care of liferea. Best regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720831: fixed
Hi
I pushed a fix. It is also attached. Please test.
Bastian
--
Vulcans believe peace should not depend on force.
-- Amanda, "Journey to Babel", stardate 3842.3
commit 298c96cdb311ed847bc4d75df1e89adb239879d5
Author: Bastian Blank
Date: Tue Mar 25 21:02:16 2014 +0100
Add support for 16-bit strings
diff --git a/dvdvideo/udf/general.py b/dvdvideo/udf/general.py
index 1f819e4..ba6b6c1 100644
--- a/dvdvideo/udf/general.py
+++ b/dvdvideo/udf/general.py
@@ -38,10 +38,10 @@ class OSTACompressedUnicode(str):
stype = buf[0]
if stype == 8:
-return buf[1:].decode()
+return buf[1:].decode('utf-8')
elif stype == 16:
-raise NotImplementedError
-raise RuntimeError
+return buf[1:].decode('utf-16be')
+raise ValueError
class ExtentAD(object):
diff --git a/dvdvideo/udf/test_general.py b/dvdvideo/udf/test_general.py
new file mode 100644
index 000..4cee135
--- /dev/null
+++ b/dvdvideo/udf/test_general.py
@@ -0,0 +1,40 @@
+"""
+@copyright: 2014 Bastian Blank
+@license: GNU GPL-3
+"""
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 3 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see
Bug#616290: isc-dhcp: Updated patches for GNU/Hurd
Svante Signell, le Tue 25 Mar 2014 21:36:45 +0100, a écrit : > On Tue, 2014-03-25 at 21:21 +0100, Samuel Thibault wrote: > > > I have pushed all that in a commit, which you can pull from the > > experimental branch of > > ssh://alioth.debian.org/srv/home/users/sthibault/isc-dhcp.git > > > > I plan to NMU these changes to experimental. > > Samuel, what happened to patch-osdep? It is replaced by just setting export DO_LPF=1 from rules. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616290: isc-dhcp: Updated patches for GNU/Hurd
On Tue, 2014-03-25 at 21:21 +0100, Samuel Thibault wrote: > I have pushed all that in a commit, which you can pull from the > experimental branch of > ssh://alioth.debian.org/srv/home/users/sthibault/isc-dhcp.git > > I plan to NMU these changes to experimental. Samuel, what happened to patch-osdep? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510466: at: Needs SE Linux support
Laurent, it's great that someone verified the patch is working with SElinux on Debian. It would be big help for me if it was included in the upstream. Marcela -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742639: ITP: python-expyriment -- Python library for cognitive and neuroscientific experiments
Package: wnpp Severity: wishlist Owner: Yaroslav Halchenko * Package name: python-expyriment Version : 0.7.0 Upstream Author : Oliver Lindemann * URL : http://www.expyriment.org * License : GPL-3.0+ Programming Lang: Python Description : Python library for cognitive and neuroscientific experiments Expyriment is a light-weight Python library for designing and conducting timing-critical behavioural and neuroimaging experiments. The major goal is to provide a well-structured Python library for a script-based experiment development with a high priority on the readability of the resulting programme code. Due to the availability of an Android runtime environment, Expyriment is also suitable for the development of experiments running on tablet PCs or smart-phones. Filing ITP on behalf of the upstream (Oliver) who is preparing the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742009: liferea: New upstream release 1.10.7
On 24-03-14 07:41, David Smith wrote: > Hmm.. Have you tried moving ~/.config/liferea out of the way to reset > your configuration to the defaults and then try loading up liferea > again? No I haven't yet. > On another note, I believe I've got 1.10.7-1 in the git repo all set for > a review for upload into unstable. So you want me to upload? This means that you consider the bug we have been discussing so far as not the regression you thought it to be? > Let me know if you find any problems. Yes, I like to fix bug 738099. David, I assume you want to claim maintainership of liferea. I think you deserve it, so please do (unless Emilio now starts complaining). Paul signature.asc Description: OpenPGP digital signature
Bug#616290: isc-dhcp: Updated patches for GNU/Hurd
Control: tags -1 + patch
Hello,
Svante Signell, le Tue 25 Mar 2014 14:52:11 +0100, a écrit :
> Attached are updated patches to enable a successful build of isc-dhcp
> from experimental on GNU/Hurd. The first two, patch-bind and
> patch-osdep, are upstream material, while the remaining four are
> debian-specific.
Don't forget some details about how patches are to be applied, otherwise
you run the risk of seeing the maintainer miss some bits.
- There is a bug in debian/rules for applying bind patches, see attached
file "patch".
- patch-bind (from upstream bind) can then be put into
debian/bind-patches/ (use the version attached to this mail, it provides
the required generated configure bits)
- debian/bind-patches/series can then be created with patch-bind in it.
- patch-config should be applied to make the debian package select
proper isc-dhcp backends on the Hurd. Use the version attached to this
mail, it does so by just passing information to configure instead of
patching upstream.
- dhclient-script.hurd, dhclient-script.hurd.udeb and
rfc3442-classless-routes.hurd should be put to debian/
I have pushed all that in a commit, which you can pull from the
experimental branch of
ssh://alioth.debian.org/srv/home/users/sthibault/isc-dhcp.git
I plan to NMU these changes to experimental.
Samuel
--- debian/rules.original 2014-03-25 19:32:52.0 +
+++ debian/rules2014-03-25 19:32:54.0 +
@@ -34,7 +34,7 @@
override_dh_auto_build:
# extract and patch embedded bind
cd bind && tar xf bind.tar.gz && \
- cd bind-* && test -e debian/bind-patches/series && \
+ cd bind-* && test -e ../../debian/bind-patches/series && \
QUILT_PATCHES=../../debian/bind-patches quilt push -a || true
# ldap-enabled build
test -f Makefile && $(MAKE) distclean || true
--- bind-9.9.5b1/configure.in.orig 2013-12-12 06:59:59.0 +0100
+++ bind-9.9.5b1/configure.in 2014-03-25 09:33:41.0 +0100
@@ -352,7 +352,7 @@ case "$host" in
# as it breaks how the two halves (Basic and Advanced) of the IPv6
# Socket API were designed to be used but we have to live with it.
# Define _GNU_SOURCE to pull in the IPv6 Advanced Socket API.
- *-linux* | *-kfreebsd*-gnu)
+ *-linux* | *-kfreebsd*-gnu | *-gnu*)
STD_CDEFINES="$STD_CDEFINES -D_GNU_SOURCE"
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
;;
--- bind-9.9.5b1/configure.orig 2013-12-12 06:59:59.0 +0100
+++ bind-9.9.5b1/configure 2014-03-25 09:33:41.0 +0100
@@ -352,7 +352,7 @@ case "$host" in
# as it breaks how the two halves (Basic and Advanced) of the IPv6
# Socket API were designed to be used but we have to live with it.
# Define _GNU_SOURCE to pull in the IPv6 Advanced Socket API.
- *-linux* | *-kfreebsd*-gnu)
+ *-linux* | *-kfreebsd*-gnu | *-gnu*)
STD_CDEFINES="$STD_CDEFINES -D_GNU_SOURCE"
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
;;
--- bind-9.9.5b1/lib/isc/unix/net.c.orig2013-12-12 06:59:59.0
+0100
+++ bind-9.9.5b1/lib/isc/unix/net.c 2014-03-25 10:21:08.0 +0100
@@ -130,6 +130,9 @@ try_proto(int domain) {
#ifdef EAFNOSUPPORT
case EAFNOSUPPORT:
#endif
+#ifdef EPFNOSUPPORT
+ case EPFNOSUPPORT:
+#endif
#ifdef EPROTONOSUPPORT
case EPROTONOSUPPORT:
#endif
--- a/debian/rules.orig 2013-12-22 04:36:57.0 +0100
+++ b/debian/rules 2014-03-25 10:26:24.0 +0100
@@ -19,8 +19,16 @@ CFLAGS+=-D_PATH_DHCPD_CONF='"/etc/dhcp/d
CFLAGS+=-D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"'
CFLAGS+=-DNOMINUM
+ifeq ($(DEB_HOST_ARCH_OS), hurd)
+CONFIG=--enable-use-sockets
+export DO_LPF=1
+else
+CONFIG=
+endif
+
CONFFLAGS=--prefix=/usr \
--sysconfdir=/etc/dhcp \
+ $(CONFIG) \
--with-srv-lease-file=/var/lib/dhcp/dhcpd.leases \
--with-srv6-lease-file=/var/lib/dhcp/dhcpd6.leases \
--with-cli-lease-file=/var/lib/dhcp/dhclient.leases \
#!/bin/bash
# dhclient-script for GNU, based on the script for Linux.
# Dan Halbert, March, 1997.
# Updated for Linux 2.[12] by Brian J. Murrell, January 1999.
# Modified for Debian. Matt Zimmerman and Eloy Paris, December 2003
# Modified to remove useless tests for antiquated kernel versions that
# this doesn't even work with anyway, and introduces a dependency on /usr
# being mounted, which causes cosmetic errors on hosts that NFS mount /usr
# Andrew Pollock, February 2005
# Modified to work on point-to-point links. Andrew Pollock, June 2005
# Modified to support passing the parameters called with to the hooks. Andrew
Pollock, November 2005
# Modified to work under GNU/Hurd for isc-dhcp-4.1.1 based on the
# patch by Samuel Thibault for dhcp3. Svante Signell, February 2011.
# The alias handling in here probably still sucks. -mdz
# update /etc/resolv.conf based on
Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)
I tried stable wheezy with kernel 3.2.0-4-kirkwood on my QNAP TS-412 (logs attached) and unstable as of 13.03.2014 (sorry, didn’t remember kernel version) with same result. The «delayroot» boot argument set to 20 sec helped me. In a few days will try latest kernel and report then. __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Oct 27 2010 - 16:50:30) Marvell version: 3.4.4 U-Boot code: 0060 -> 0067FFF0 BSS: -> 00690DCC Soc: MV88F6281 Rev 3 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 6 tRAS = 18 tRCD=6 DRAM CS[0] base 0x size 256MB DRAM Total size 256MB 16bit width [16384kB@f800] Flash: 16 MB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done CPU : Marvell Feroceon (Rev 1) USB 0: host mode PCI 0: PCI Express Root Complex Interface PEX interface detected Link X1 Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 Unknown command 'uart1' - try 'help' ## Booting image at 0080 ... Image Name: kernel 3.2.0-4-kirkwood Created: 2014-03-13 15:07:08 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1610768 Bytes = 1.5 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-4-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.54-2 [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: QNAP TS-41x [0.00] Ignoring unrecognised tag 0x41000403 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=34816 [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Memory: 256MB = 256MB total [0.00] Memory: 245868k/245868k available, 16276k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xd080 - 0xfe80 ( 736 MB) [0.00] lowmem : 0xc000 - 0xd000 ( 256 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc03e757c (3966 kB) [0.00] .init : 0xc03e8000 - 0xc040c000 ( 144 kB) [0.00] .data : 0xc040c000 - 0xc0446820 ( 235 kB) [0.00].bss : 0xc0446844 - 0xc04a9ed8 ( 398 kB) [0.00] NR_IRQS:114 [0.00] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [0.00] Console: colour dummy device 80x30 [7.625187] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256) [7.715078] pid_max: default: 32768 minimum: 301 [7.715199] Security Framework initialized [7.715271] Mount-cache hash table entries: 512 [7.715597] Initializing cgroup subsys cpuacct [7.715620] Initializing cgroup subsys memory [7.715643] Initializing cgroup subsys devices [7.715653] Initializing cgroup subsys freezer [7.715662] Initializing cgroup subsys net_cls [7.715671] Initializing cgroup subsys blkio [7.715691] Initializing cgroup subsys perf_event [7.715778] CPU: Testing write buffer coherency: ok [7.716961] devtmpfs: initialized [7.718758] print_constraints: dummy: [7.718992] NET: Registered protocol family 16 [7.719756] Kirkwood: MV88F6281-A1, TCLK=2. [7.719770] Feroceon L2: Enabling L2 [7.719803] Feroceon L2: Cache support initialised. [7.761244] Kirkwood PCIe port 0: [7.761251] link up [7.761275] PCI: bus0 uses PCIe port 0 [7.761678] PCI: bus0: Fast back to back transfers disabled [7.761928] pci :00:01.0: BAR 0: assigned [mem 0xe000-0xe00f 64bit] [7.761947] pci :00:01.0: BAR 2: assigned [io 0x1000-0x10ff] [7.763610] bio: create slab at 0 [7.763992] vgaarb: loaded [7.764540] Switching to clocksource orion_clocksource [7
Bug#742638: crashes if UserProfile is not an instance of ConversationProfile
Package: librecon-1.9 Version: 1.9.3-1 Severity: serious ConversationManager uses dynamic_cast to try and retrieve a ConversationProfile It doesn't check if the cast was successful and tries to use the pointer. This leads to a segmentation fault. Fixed upstream in 1.9.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723079: fix?
Hi Peter
I have a possible fix for this problem. I just considers all info and
backup files equal. Please test, I currently have no access to any
video DVD.
Bastian
--
"Beauty is transitory."
"Beauty survives."
-- Spock and Kirk, "That Which Survives", stardate unknown
diff --git a/dvdvideo-backup-image b/dvdvideo-backup-image
index bbd06cd..ac5c2cf 100755
--- a/dvdvideo-backup-image
+++ b/dvdvideo-backup-image
@@ -125,14 +125,6 @@ class PartIfoVts(PartIfo):
pass
-class PartBupVmg(PartIfoVmg):
-pass
-
-
-class PartBupVts(PartIfoVts):
-pass
-
-
class PartVob(PartFile):
def adjust_other_special(self, other, all):
if isinstance(other, PartIfo):
@@ -193,7 +185,7 @@ def main(stream, input, output):
parts.append(PartIfoVmg(vmg.fileset.ifo))
if vmg.fileset.menu_vob:
parts.append(PartMenuVob(vmg.fileset.menu_vob))
-parts.append(PartBupVmg(vmg.fileset.bup))
+parts.append(PartIfoVmg(vmg.fileset.bup))
for i in vts:
parts.append(PartIfoVts(i.fileset.ifo))
@@ -201,7 +193,7 @@ def main(stream, input, output):
parts.append(PartMenuVob(i.fileset.menu_vob))
parts.append(PartTitleVob(i.fileset.title_vob))
if i.bup:
-parts.append(PartBupVts(i.fileset.bup))
+parts.append(PartIfoVts(i.fileset.bup))
logging.debug('parts: %r', parts)
Bug#741992: mkfs.ntfs -V exits with failure status
Hi, This will be changed (along with most ntfsprogs utilities) in future releases. Regards Jean-Pierre Daniel Baumann wrote: tag 741992 upstream tag 741992 wontfix thanks On 03/20/2014 09:13 PM, Phillip Susi wrote: The C and posix standards. as said they don't cover --usage/--help/--version. There isn't anything "special" about these options that overrides the broader exit status standard. as said, i beg to differ. but whatever, we're going into circles which leads to nothing. please talk to upstream, it's his choice anyway, i for myself am not going to 'fix' it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742636: wheezy-pu: package spip/2.1.17-1+deb7u4
Control: tags -1 + confirmed On Tue, 2014-03-25 at 15:54 -0400, David Prévot wrote: > As agreed with the security team, here I am proposing another stable > update for fixing a minor security issues in SPIP. Attached debdiff, > thanks in advance for considering. Please go ahead. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742637: squeeze-pu: package spip/2.1.1-3squeeze9
Control: tags -1 + confirmed On Tue, 2014-03-25 at 15:54 -0400, David Prévot wrote: > As agreed with the security team, here I am proposing another oldstable > update for fixing minor security issues in SPIP. Attached debdiff, > thanks in advance for considering. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616689: Anothor occurence on sid
Hello, I can confirm to have had a problem similar to the one described here. On initramfs shell, vgchange -ay, ^D, ^D, solved the issue and after booting the system up, I downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to 2.00-22 and the issue was solved. Initially I thought it was bug #741652, following the thread on https://lists.debian.org/debian-user/2014/03/msg01313.html. However, I was only able to restore the system following the same manual activation of lvm2 volume groups. Since I do not know if it was an issue with initramfs or grub, I though a notice here could be of some help. -- André N. Batista GNUPG/PGP KEY: 6722CF80 signature.asc Description: This is a digitally signed message part
Bug#554167: Upgrading mawk to 1.3.4
On Tue, Mar 25, 2014 at 10:01:53PM +0200, Riku Voipio wrote: > On Tue, Mar 25, 2014 at 09:32:33AM -0700, Steve Langasek wrote: > > On Tue, Mar 25, 2014 at 05:30:50PM +0200, Riku Voipio wrote: > > This is the bug about requesting a new upstream version. I'm pretty sure > > that's not the bug your users were running into. > The code worked fine on mawk from other distro's (and gawk) - but not > ubuntu/debian. So from their PoV the bug is caused by the rather old > mawk version carried by us. > Now, of course, one can argue that they shouldn't be surprised that > debian comes with something outdated... No, I argue that if they have a problem with the code they should report the exact issue instead of blaming it on the package being "outdated". -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#554167: Upgrading mawk to 1.3.4
On Tue, Mar 25, 2014 at 09:32:33AM -0700, Steve Langasek wrote: > On Tue, Mar 25, 2014 at 05:30:50PM +0200, Riku Voipio wrote: > This is the bug about requesting a new upstream version. I'm pretty sure > that's not the bug your users were running into. The code worked fine on mawk from other distro's (and gawk) - but not ubuntu/debian. So from their PoV the bug is caused by the rather old mawk version carried by us. Now, of course, one can argue that they shouldn't be surprised that debian comes with something outdated... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)
* Martin Waschbuesch [2013-07-04 19:12]: > Package: src:linux > Version: 3.2.46-1 Alexander Rumyantsev just reported the same issue to me. Alexander, which kernel version are you using? If this is still present in the kernel in Debian unstable, I'll email the upstream kernel folks. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)
* Martin Michlmayr [2013-12-15 11:20]: > Since nobody has responded to your bug report yet, do you think you > can go ahead and report this issue on the linux-ide mailing list (the > upstream kernel list for SATA): linux-...@vger.kernel.org > > You can CC some Kirkwood maintainers: > Andrew Lunn > Sebastian Hesselbarth > Jason Cooper Hi Martin, did you ever submit your bug report upstream? If not, can you try the latest kernel in Debian to see if that works? If the bug is still there, we should email the upstream developers. In addition to the people I listed above, we should CC Thomas Petazzoni -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742637: squeeze-pu: package spip/2.1.1-3squeeze9
Package: release.debian.org
Severity: normal
Tags: squeeze
User: release.debian@packages.debian.org
Usertags: pu
Dear release team,
As agreed with the security team, here I am proposing another oldstable
update for fixing minor security issues in SPIP. Attached debdiff,
thanks in advance for considering.
Regards
David
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 0427965..25a8296 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+spip (2.1.1-3squeeze9) squeeze; urgency=medium
+
+ * Fix missing escape
+ * Fix missing escape in SQL
+ * Update security screen to 1.1.9 (Closes: #742456)
+
+ -- David Prévot Thu, 13 Mar 2014 16:58:14 -0300
+
spip (2.1.1-3squeeze8) squeeze; urgency=medium
* Document fixed #729172
diff --git a/debian/patches/fix_missing_escape.patch b/debian/patches/fix_missing_escape.patch
new file mode 100644
index 000..7d08c36
--- /dev/null
+++ b/debian/patches/fix_missing_escape.patch
@@ -0,0 +1,19 @@
+From: Cédric Morin
+Subject: Fix missing escape
+
+ * ecrire/inc/log.php: Always escape < in logs, unless the _LOG_BRUT
+ constant is defined to true at the end of debug.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21251
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/inc/log.php
b/ecrire/inc/log.php
+@@ -56,7 +56,7 @@
+
+ $f = @fopen($logfile, "ab");
+ if ($f) {
+- fputs($f, ($logname!==NULL) ? $m : str_replace('<','<',$m));
++ fputs($f, (defined('_LOG_BRUT') AND _LOG_BRUT) ? $m : str_replace('<','<',$m));
+ fclose($f);
+ }
+
diff --git a/debian/patches/fix_missing_escape_in_SQL.patch b/debian/patches/fix_missing_escape_in_SQL.patch
new file mode 100644
index 000..8024698
--- /dev/null
+++ b/debian/patches/fix_missing_escape_in_SQL.patch
@@ -0,0 +1,18 @@
+From: Cédric Morin
+Subject: Fix missing escape in SQL
+
+ * ecrire/inc/quete.php: Fix missing escape in a SQL request.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21247
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/public/quete.php
b/ecrire/public/quete.php
+@@ -248,7 +248,7 @@
+ $exposer[$m][$type][$principal] = true;
+ if ($type == 'id_mot'){
+ if (!$parent) {
+- $parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . $principal, '','','','',$connect);
++ $parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . intval($principal), '','','','',$connect);
+ }
+ if ($parent)
+ $exposer[$m]['id_groupe'][$parent] = true;
diff --git a/debian/patches/series b/debian/patches/series
index 7646257..1ec8a6c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -19,3 +19,5 @@ fix_privilege_escalation_2.1.21.patch
fix_CSRF_on_logout.patch
fix_XSS_on_author_page.patch
fix_XSS_on_signature.patch
+fix_missing_escape.patch
+fix_missing_escape_in_SQL.patch
diff --git a/debian/security/ecran_securite.php b/debian/security/ecran_securite.php
index 7e6ec1c..36b0044 100644
--- a/debian/security/ecran_securite.php
+++ b/debian/security/ecran_securite.php
@@ -5,7 +5,7 @@
* --
*/
-define('_ECRAN_SECURITE', '1.1.8'); // 2013-08-29
+define('_ECRAN_SECURITE', '1.1.9'); // 2014-03-13
/*
* Documentation : http://www.spip.net/fr_article4200.html
@@ -254,13 +254,12 @@ if (isset($_REQUEST['connect'])
AND
// cas qui permettent de sortir d'un commentaire PHP
(strpos($_REQUEST['connect'], "?")!==false
+ OR strpos($_REQUEST['connect'], "<")!==false
OR strpos($_REQUEST['connect'], ">")!==false
OR strpos($_REQUEST['connect'], "\n")!==false
OR strpos($_REQUEST['connect'], "\r")!==false)
) {
- $_REQUEST['connect'] = str_replace(array("?", ">", "\r", "\n"), "", $_REQUEST['connect']);
- if (isset($_GET['connect'])) $_GET['connect'] = $_REQUEST['connect'];
- if (isset($_POST['connect'])) $_POST['connect'] = $_REQUEST['connect'];
+ $ecran_securite_raison = "malformed connect argument";
}
/*
@@ -317,4 +316,4 @@ if (
}
-?>
+?>
\ No newline at end of file
signature.asc
Description: Digital signature
Bug#742636: wheezy-pu: package spip/2.1.17-1+deb7u4
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Dear release team,
As agreed with the security team, here I am proposing another stable
update for fixing a minor security issues in SPIP. Attached debdiff,
thanks in advance for considering.
Regards
David
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index d09ada5..e00ae22 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+spip (2.1.17-1+deb7u4) wheezy; urgency=medium
+
+ * Update displayed version
+ * Fix missing escape
+ * Fix missing escape in SQL
+ * Update security screen to 1.1.9 (Closes: #742456)
+
+ -- David Prévot Thu, 13 Mar 2014 16:50:23 -0300
+
spip (2.1.17-1+deb7u3) wheezy; urgency=medium
* Document fixed #729172
diff --git a/debian/patches/fix_displayed_version.patch b/debian/patches/fix_displayed_version.patch
index fdc1186..80ff1d0 100644
--- a/debian/patches/fix_displayed_version.patch
+++ b/debian/patches/fix_displayed_version.patch
@@ -2,7 +2,7 @@ Description: Fix displayed version in the private interface
Make it obvious it's a Debian (patched) version
Forwarded: not-needed
Author: David Prévot
-Last-Update: 2013-11-02
+Last-Update: 2014-01-24
--- a/ecrire/inc_version.php
+++ b/ecrire/inc_version.php
@@ -423,7 +423,7 @@
@@ -10,7 +10,7 @@ Last-Update: 2013-11-02
// 1.xxyy : xx00 versions stables publiees, xxyy versions de dev
// (ce qui marche pour yy ne marchera pas forcement sur une version plus ancienne)
-$spip_version_affichee = "$spip_version_branche";
-+$spip_version_affichee = "2.1.17-1+deb7u2 (Debian)";
++$spip_version_affichee = "2.1.17-1+deb7u4 (Debian)";
// ** Securite **
$visiteur_session = $auteur_session = $connect_statut = $connect_toutes_rubriques = $hash_recherche = $hash_recherche_strict = $ldap_present ='';
diff --git a/debian/patches/fix_missing_escape.patch b/debian/patches/fix_missing_escape.patch
new file mode 100644
index 000..7d08c36
--- /dev/null
+++ b/debian/patches/fix_missing_escape.patch
@@ -0,0 +1,19 @@
+From: Cédric Morin
+Subject: Fix missing escape
+
+ * ecrire/inc/log.php: Always escape < in logs, unless the _LOG_BRUT
+ constant is defined to true at the end of debug.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21251
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/inc/log.php
b/ecrire/inc/log.php
+@@ -56,7 +56,7 @@
+
+ $f = @fopen($logfile, "ab");
+ if ($f) {
+- fputs($f, ($logname!==NULL) ? $m : str_replace('<','<',$m));
++ fputs($f, (defined('_LOG_BRUT') AND _LOG_BRUT) ? $m : str_replace('<','<',$m));
+ fclose($f);
+ }
+
diff --git a/debian/patches/fix_missing_escape_in_SQL.patch b/debian/patches/fix_missing_escape_in_SQL.patch
new file mode 100644
index 000..8024698
--- /dev/null
+++ b/debian/patches/fix_missing_escape_in_SQL.patch
@@ -0,0 +1,18 @@
+From: Cédric Morin
+Subject: Fix missing escape in SQL
+
+ * ecrire/inc/quete.php: Fix missing escape in a SQL request.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21247
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/public/quete.php
b/ecrire/public/quete.php
+@@ -248,7 +248,7 @@
+ $exposer[$m][$type][$principal] = true;
+ if ($type == 'id_mot'){
+ if (!$parent) {
+- $parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . $principal, '','','','',$connect);
++ $parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . intval($principal), '','','','',$connect);
+ }
+ if ($parent)
+ $exposer[$m]['id_groupe'][$parent] = true;
diff --git a/debian/patches/series b/debian/patches/series
index 79be5e2..7de80f0 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,5 @@ fix_privilege_escalation_2.1.21.patch
fix_CSRF_on_logout.patch
fix_XSS_on_author_page.patch
fix_XSS_on_signature.patch
+fix_missing_escape.patch
+fix_missing_escape_in_SQL.patch
diff --git a/debian/security/ecran_securite.php b/debian/security/ecran_securite.php
index 7e6ec1c..36b0044 100644
--- a/debian/security/ecran_securite.php
+++ b/debian/security/ecran_securite.php
@@ -5,7 +5,7 @@
* --
*/
-define('_ECRAN_SECURITE', '1.1.8'); // 2013-08-29
+define('_ECRAN_SECURITE', '1.1.9'); // 2014-03-13
/*
* Documentation : http://www.spip.net/fr_article4200.html
@@ -254,13 +254,12 @@ if (isset($_REQUEST['connect'])
AND
// cas qui permettent de sortir d'un commentaire PHP
(strpos($_REQUEST['connect'], "?")!==false
+ OR strpos($_REQUEST['connect'], "<")!==false
OR strpos($_REQUEST['connect'], ">")!==false
OR strpos($_R
Bug#742635: yudit: Wrong path to help files
Package: yudit Version: 2.9.2-4 Severity: normal Dear Maintainer, When I type "howto configure" command, Yudit prints: Can not read" '/usr/share/yudit/doc/HOWTO-configure.txt The real path to this file on Debian system is instead: /usr/share/doc/yudit-doc/HOWTO-configure.txt Please correct the path. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages yudit depends on: ii libc6 2.18-4 ii libgcc1 1:4.8.2-16 ii libstdc++64.8.2-16 ii libx11-6 2:1.6.2-1 ii yudit-common 2.9.2-4 Versions of packages yudit recommends: ii gv1:3.7.4-1 ii libhunspell-1.3-0 1.3.2-7 ii myspell-ru [hunspell-dictionary] 0.99g5-18 ii unifont 1:6.3.20140214-1 Versions of packages yudit suggests: ii fonts-freefont-ttf 20120503-4 ii fonts-ipaexfont-gothic [fonts-japanese-gothic] 00201-4 ii fonts-ipafont-gothic [fonts-japanese-gothic]00303-12 ii ttf-mscorefonts-installer 3.5 ii yudit-doc 2.9.2-4 -- 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
