Bug#773631: mariadb-server: Fails to install
Package: mariadb-server Version: 10.0.15-2 Severity: important Dear Maintainer, the package fails to install in Sid and fails to upgrade on Jessie. This is the messages when I tried to install MariaDB on Sid Setting up libmysqlclient18:amd64 (5.5.40-1) ... Setting up libreadline5:amd64 (5.2+dfsg-2) ... Setting up libdbi-perl (1.631-3+b1) ... Setting up libterm-readkey-perl (2.32-1+b1) ... Setting up mariadb-client-core-10.0 (10.0.15-2) ... Setting up mariadb-client-10.0 (10.0.15-2) ... Setting up mariadb-server-core-10.0 (10.0.15-2) ... Setting up mariadb-server-10.0 (10.0.15-2) ... Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details. invoke-rc.d: initscript mysql, action start failed. dpkg: error processing package mariadb-server-10.0 (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libdbd-mysql-perl (4.028-2+b1) ... Setting up libhtml-template-perl (2.95-1) ... dpkg: dependency problems prevent configuration of mariadb-server: mariadb-server depends on mariadb-server-10.0 (= 10.0.15-2); however: Package mariadb-server-10.0 is not configured yet. dpkg: error processing package mariadb-server (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.19-13) ... Processing triggers for menu (2.1.47) ... Errors were encountered while processing: mariadb-server-10.0 mariadb-server E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up mariadb-server-10.0 (10.0.15-2) ... However, thanks for providing MariaDB for Debian. My experience with version 10.0.14 is positive. Kind regards Georgi -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mariadb-server depends on: ih mariadb-server-10.0 10.0.15-2 mariadb-server recommends no packages. mariadb-server 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#773632: RFS: pcsx2/1.2.1-783-g1f54bb7+dfsg-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package pcsx2 * Package name: pcsx2 Version : 1.2.1-783-g1f54bb7+dfsg-1 Upstream Author : PCSX2 Dev Team * URL : http://pcsx2.net/ * License : GPL-3 Section : games It builds those binary packages: pcsx2 - Playstation 2 emulator pcsx2-dbg - Debug symbols for PCSX2 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/pcsx2 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/pcsx2/pcsx2_1.2.1-783-g1f54bb7+dfsg-1.dsc or go directly to the VCS: http://anonscm.debian.org/cgit/pkg-games/pcsx2.git Regards, Miguel A. Colón Vélez -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768110: wget: strange progress display with certain locale settings
Please consider applying this to jessie. wget looks pretty bad in there for me (ru locale), I had to use a wrapper for it which sets LANG. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769511: [Fwd: Processed (with 5 errors): [Fwd: Re: Bug#769511: Info received (Bug#769511: netscript-2.4: installation fails]
severity 769511 wishlist -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750011: gnome-tweak-tool: Windows Scaling Not Undoable
Hi! I have found out one solution. You simplify use shortcut for GNOME window ALT+F8 in order to move it freely. Then, focusing on your factor and rescaling it. Cheers, Minh On Sat, 31 May 2014 11:17:52 -0400 Dean Chia perido...@gmail.com wrote: Package: gnome-tweak-tool Version: 3.12.0-2 Severity: normal Dear Maintainer, I went to Tweak Tool -- Windows -- Windows Scaling to see what it would do. I pressed + and it made my window scaling from 1 to 2. Problem was, because everything was scaled, I was unable to undo what I did and rescale it back to 1. My whole gnome session became practically unusable. My cursor and desktop did not match up, and I was unable to move my windows. I could not reach with my mouse the menu item to rescale the Windows, so it was essentially stuck at a scale of 2. This applied both to Gnome and Gnome Classic. Luckily, I had XFCE to fallback to, and from there I opened gnome-tweak-tool to rescale my windows back to 1. If all I had was gnome for my DE, then I would have been in big trouble. I'm not sure how one would fix this, as this is actually quite a serious bug. Would it be possible if you employed some kind of kill switch (like what you do in Displays), where it would revert in 15-30 seconds to previous windows scaling. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-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 gnome-tweak-tool depends on: ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-gtk-3.0 3.12.2-1 ii gir1.2-notify-0.7 0.7.6-2 ii gnome-shell-common 3.8.4-8.1 ii gsettings-desktop-schemas 3.8.2-2 ii python 2.7.6-2 ii python-gi 3.12.1-1 gnome-tweak-tool recommends no packages. gnome-tweak-tool 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#773617: ITP: kcmsystemd -- A KDE Control Center module for systemd
Hi, That would be really nice ! I managed to find your packaging tree, so I add it in this CC so ohters can have alook at it: https://github.com/shsorbom/kcmsystemd-debian Package: wnpp Severity: wishlist Owner: Shawn Sörbom sh...@sorbom.com * Package name: kcmsystemd Version : 0.7.0 Upstream Author : Ragnar Thomsen rthoms...@gmail.com * URL : https://github.com/rthomsen/kcmsystemd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773633: flashplugin-nonfree: should have Pre-Depends: ca-certificates
Package: flashplugin-nonfree Version: 1:3.6 Severity: serious As illustrated below, flashplugin-nonfree should have Pre-Depends: ca-certificates. | # apt-get install flashplugin-nonfree | Reading package lists... Done | Building dependency tree | Reading state information... Done | The following extra packages will be installed: |ca-certificates wget ... | Setting up wget (1.16-1) ... | Setting up ca-certificates (20141019) ... | Setting up flashplugin-nonfree (1:3.6) ... | ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp | More information might be available at: |http://wiki.debian.org/FlashPlayer | Processing triggers for ca-certificates (20141019) ... | Updating certificates in /etc/ssl/certs... 173 added, 0 removed; done. | Running hooks in /etc/ca-certificates/update.ddone. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773557: debian-policy: Avoid unsafe RPATH/RUNPATH
On Sat, 2014-12-20 at 02:10 -0200, Henrique de Moraes Holschuh wrote: IMHO, the suggested wording does get the point across that whomever wants to use RPATH/RUNPATH must be prepared to defend its use with strong technical reasons. Exactly. Without it I was concerned this would tacitly condone use of RPATH/RUNPATH and that's counterproductive. (At the same time there seem to be cases where complete avoidance is difficult hence the escape clause). This part looks good. IMO, it is too weak. This is about introducing security hazards, so... weak is a feature :) My suggested text is not perfect. My aim is to seed uncontroversial text that will educate, delimit bad practice, serve as a basis for further refinement. Perfect has been the enemy of good here. And in fact, I'd add: Packages are not allowed to create *and* execute libraries or executables with unsafe RPATH or RUNPATH at any time, not even during their build process. But actually Package maintainers should not make or run dangerous stuff? Agreed -- and also seems uncontroversial. Although I think you mean or not and? Perhaps neither/nor to kill any ambiguity: 8.7 RUNPATH and RPATH Libraries and executables should not define RPATH or RUNPATH unless absolutely necessary. Those that do should ensure that relative paths or paths that traverse insecure directories (eg /tmp or /var/tmp) are not included. This is to prevent an executable from loading a library from an untrusted location. (This should include the corner cases whereby the path list starts or ends with a colon, or includes two consecutive colons). Packages should neither create nor execute libraries or executables with unsafe RPATH or RUNPATH at any time, not even during their build process. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773256: pre-approval: unblock: dpkg/1.17.23
CC: @deity (look for a couple of @deitys below) On 2014-12-19 20:35, Guillem Jover wrote: Hi! On Wed, 2014-12-17 at 22:18:12 +0100, Niels Thykier wrote: On 2014-12-16 06:22, Guillem Jover wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: block -1 by 770627 I'd prefer if 1.17.22 could be unblocked before uploading this, because that version is way better than the one currently in testing, and it is causing fewer upgrade issues. Otherwise I'll just merge both unblock requests. Apologies, but I am not entirely convinced here. I would strongly prefer /not/ having trigger regressions right now. Sorry, it seems there was a communication breakdown somewhere, my fault. As I just mentioned on #771730, once tracked down I always thought this affected all dpkg versions doing trigger dependency checks (although other issues might have shadowed that specific problem), but it seems I thought I mentioned it somewhere but cannot find any reference now :(, and did not actually try to reproduce with older versions because it seemed a bit like a waste of time when the unblock didn't seem to be dependenent on that issue. So, yes, 1.17.22 is really better in any possible way to 1.17.21. But, obviously your call. Okay, it was not clear to me that dpkg/1.17.21 was also affected by #771730. That changes it quite a bit as it is no longer a regression between unstable and testing. It possibly still is since the version that introduced the trigger checks. I hope we can have it resolved shortly. In fact, I am honestly considering to request having the trigger change reverted if 1.17.23 does not solve the issues without introduce another regression. Ok. I'll do another pass over the code, and then try to improve the functional test suite to see if I catch something else before the upload. Excellent. We are one and a half month into the freeze and we still do not have a clean upgrade path on a package level. I am deeply concerned that we have been missing out on (e.g.) the systemd upgrade reports because of this. Sorry, I guess I should have tried to push a fix for the RC bug earlier w/o waiting for the translations deadline, but was not entirely clear on whether the disabled unblock was permanent or temporary until clarification on the dbus issue and enabling it back had not happened for unrelated reasons. Also given that #771730 was not a regression, it seemed prudent to let .22 migrate first. Okay, I have decided to let dpkg/1.17.22 migrate. I am still not pleased with the dbus situation - regardless of whose fault it is. @deity/@dpkg: On the RC bug fixes vs. translations. Given that (one of?) dpkg and APT is correctly breaking our upgrades, I am much more interested in the RC bug fixes for these packages. I do not mind waiting up to 14 days on a translations only update provided that it gets me *working* an upgrade path between Wheezy and Jessie sooner. I've delayed a bit the request because there are still some packages with trigger cycles that have not been uploaded yet, I can start taking a look on delayed NMUs and wait for those or upload .23 right away and possibly prepare a .24 with those additional versioned Breaks, whichever you prefer. It seems that only gxine and icecc are missing now. If so, please go ahead with the .23 with versioned breaks for them as well. Worst case, I will have them removed from testing - best case, they will be fixed. I will take the political fall-out of this and notify the maintainers of the affected packages. Let me know if I missed any packages. Unfortunately there's still auctex, gxine, icecc, mcollective, pypy and wordpress. And I'm not sure if the fix for all of them might be a strightforward switch to a -noawait directive. Indeed I missed those. For reference, pypy got fixed and gxine, icecc and mcollective will get auto-removed eventually. My previous remark for gxine plus icecc applies equally to mcollective (and pypy, in case migration is stalled) as well. This leaves auctex as the only remaining blocker auctex. I've also not added the --force-configure-any default switch, because we don't really know what happened with apt and dbus there, and if apt from stable is affected or not. Given the recent dpkg, apt, and dbus changes I think I'd rather let this as is, and wait in case it shows up again, which should give us more information (due to the new apt not eating dpkg's output). Noted, though I sincerely hope it is fixed. I /might/ be convinced to accept a .24 for this particular issue. Just to clarify, if there's still an issue, it's exclusively in apt. The problems with dbus were due to apt trying to configure stuff when libdbus was not yet properly configured (AFAIR). And there was similar issues in apt between 0.9.9 and 1.0.7 (see #767734), but maybe this is something else, although
Bug#773634: lazarus: Fails any execution due to missing LConvEncoding
Package: lazarus Version: 0.9.30.4-6 Severity: important After a fresh installation, compiling even the smallest program gives Looks like a package is missing in the dependencies. /usr/lib/lazarus/0.9.30.4/lcl/lconvencoding.pas(27,24) Fatal: Can't find unit iconvenc used by LConvEncoding -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lazarus depends on: ii lazarus-0.9.30.4 0.9.30.4-6 lazarus recommends no packages. lazarus 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#773631: [debian-mysql] Bug#773631: mariadb-server: Fails to install
Hello! Thanks for taking the time to report. I think #773631 and #773282 are duplicates, so this issue is fixed, but not uploaded yet. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769511: Info received (Bug#769511: netscript-2.4: installation fails)
Hello, On Sun, 21 Dec 2014 20:26:28 +1300 Matt Grant m...@mattgrant.net.nz wrote: Could you please fix this? I am marking bug as important and assigning to your package ifupdown. Sorry Matt, definitely not in jessie. -- Cheers, Andrew pgpxpMm0auAPV.pgp Description: OpenPGP digital signature
Bug#749531: Patch
Hi Anton, first of all: thanks for the patch and sorry for the ridiculously long time it took me to respond. On Tue, May 27, 2014 at 09:22:56PM +0200, Anton Gladky wrote: new VTK version 6.1 is already in archive. We are planning to switch all dependent on VTK 5 packages to this new version to escape dependencies on older unsupported VTK. I tried to build the package with your patch, but it fails. VTK6 seems to pull in Qt5 dependencies that it does not seem to resolve properly. Linking the main binary fails like this: Linking CXX executable ../../bin/fslview cd /home/mih/debian/fsl/fslview/obj-x86_64-linux-gnu/src/fslview /usr/bin/cmake -E cmake_link_script CMakeFiles/fslview.dir/link.txt --verbose=1 snip /usr/bin/ld: cannot find -lQt5::Widgets collect2: error: ld returned 1 exit status As FSLView itself relies on Qt4, I think that Qt5 dependency should be resolved by VTK6. I hope that mixing Qt versions is a more fundamental problem, as switching to Qt5 seems infeasible at this point. Qwt (another dependencies) also depends on Qt4 in its latest version in Debian. Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772924: [Fwd: Re: [UPDATED] grub2 2.02~beta2-18: Please update debconf PO translation for the package grub2]
---BeginMessage--- On Sat, Dec 13, 2014 at 08:37:10PM +, Ian Campbell wrote: [...] I'm afraid this will have marked any existing translations as fuzzy. Hi Ian, please find attached updated Czech (cs.po) translation. Cheers -- Miroslav Kure # Czech translation of grub2 debconf messages. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the grub2 package. # Miroslav Kure ku...@debian.cz, 2008 -- 2014 # msgid msgstr Project-Id-Version: grub2\n Report-Msgid-Bugs-To: gr...@packages.debian.org\n POT-Creation-Date: 2014-12-13 20:23+\n PO-Revision-Date: 2014-12-21 10:32+0100\n Last-Translator: Miroslav Kure ku...@debian.cz\n Language-Team: Czech debian-l10n-cz...@lists.debian.org\n Language: cs\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid Chainload from menu.lst? msgstr Zavést přes menu.lst? #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub. msgstr Aktualizační skripty GRUBu rozpoznaly v /boot/grub nastavení pro předchozí verzi GRUBu (tzv. GRUB Legacy). #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid In order to replace the Legacy version of GRUB in your system, it is recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image from your existing GRUB Legacy setup. This step can be automatically performed now. msgstr Abyste na svém systému nahradili zastaralou verzi GRUBu, je doporučeno upravit /boot/grub/menu.lst tak, aby zavedl obraz GRUBu 2 pomocí stávajícího GRUB Legacy. Tento krok je nyní možné provést automaticky. #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid It's recommended that you accept chainloading GRUB 2 from menu.lst, and verify that the new GRUB 2 setup works before it is written to the MBR (Master Boot Record). msgstr Před instalací GRUBu 2 přímo do MBR (Master Boot Record) se doporučuje nejprve vyzkoušet zavedení GRUBu 2 skrze menu.lst a teprve po ověření, že vše funguje očekávaným způsobem, zkusit instalaci do MBR. #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid Whatever your decision, you can replace the old MBR image with GRUB 2 later by issuing the following command as root: msgstr Ať se rozhodnete jakkoliv, obraz v MBR můžete kdykoliv později nahradit GRUBem 2. Stačí jako root spustit následující příkaz: #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid GRUB install devices: msgstr Zařízení pro instalaci GRUBu: #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid The grub-pc package is being upgraded. This menu allows you to select which devices you'd like grub-install to be automatically run for, if any. msgstr Balík grub-pc se právě aktualizuje. Tato nabídka vám umožňuje zvolit zařízení, na kterých se má automaticky spouštět grub-install. #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid Running grub-install automatically is recommended in most situations, to prevent the installed GRUB core image from getting out of sync with GRUB modules or grub.cfg. msgstr Automatické spouštění grub-install je ve většině případů doporučeno, protože tak předcházíte tomu, aby se obraz jádra GRUBu rozcházel s GRUB moduly nebo souborem grub.cfg. #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. msgstr Pokud si nejste jisti, který disk je v BIOSu označen jako zaváděcí, bývá často dobrým nápadem nainstalovat GRUB na všechny disky. #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. msgstr Poznámka: GRUB je možné instalovat také do zaváděcích záznamů jednotlivých oblastí, jejichž seznam zde vidíte. Tímto však donutíte GRUB, aby používal mechanismus zvaný blocklist, který je méně spolehlivý tudíž se nedoporučuje. #. Type: multiselect #. Description #: ../grub-pc.templates.in:4001 msgid The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices. msgstr
Bug#773631: [debian-mysql] Bug#773631: mariadb-server: Fails to install
On 12/21/2014 11:24 AM, Otto Kekäläinen wrote: Hello! Thanks for taking the time to report. I think #773631 and #773282 are duplicates, so this issue is fixed, but not uploaded yet. I confirm that this bug is something related to init script. The command # /etc/init.d/mysql stop doesn't stop MariaDB and that the problem was. I managed to install mariaDB 10.0.15 on Jessie by killing mysql and executing dpkg --reconfigure -a. Kind regards Georgi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773635: python-wxgtk2.8: WXU_2.8 not defined: Cannot run apps that use wxPython 2.8
Package: python-wxgtk2.8 Version: 2.8.12.1+dfsg2-2 Severity: important Dear Maintainer, I have an application that I develop that used wxPython. Currently my app supports both version 2.8 and 3.0 of wxPython/wxWidgets. However, when trying to run my app on Debian using 2.8 I get the following error: ImportError: /usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode/wx/_gdi_.so: symbol _ZTV14wxGraphicsPath, version WXU_2.8 not defined in file libwx_gtk2u_core-2.8.so.0 with link time reference I was curious if only my application was affected so I went into the source code of an application from the Debian repository that uses wxPython. In this case I used drPython. By default drPython will use the newest version of wxPython (I believe). drPython started up fine as it was using wxPython 3.0 by default. However, I changed its code and forced it to use version 2.8. Once I did that I received the same error output as above. I believe that this is a problem with the build of wxpython2.8 on Debian. I do not know if the main problem lies upstream. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-wxgtk2.8 depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.2-9 ii libstdc++64.9.2-9 ii libwxbase2.8-02.8.12.1+dfsg2-2 ii libwxgtk2.8-0 2.8.12.1+dfsg2-2 ii python2.7.8-2 ii python-wxversion 3.0.1.1+dfsg-2 python-wxgtk2.8 recommends no packages. Versions of packages python-wxgtk2.8 suggests: pn editra none pn wx2.8-doc none pn wx2.8-examples none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773623: nodejs: CVE-2014-7192
Le samedi 20 décembre 2014 à 22:07 -0500, Michael Gilbert a écrit : package: src:nodejs CVE-2014-7192[0],[1]: | Eval injection vulnerability in index.js in the syntax-error package | before 1.1.1 for Node.js 0.10.x, as used in IBM Rational Application | Developer and other products, allows remote attackers to execute | arbitrary code via a crafted file. This doesn't affect nodejs, but the syntax-error module, a dependency of browserify - both not packaged in debian. Cannot reassign, then. Maybe close ? Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773636: unblock: flashplugin-nonfree/1:3.6.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock flashplugin-nonfree 1:3.6.1 to fix bug 773633 in jessie. Output
of debdiff attached. The only change is that ca-certificates is moved from
Depends to Pre-Depends. The effect is illustrated on bug 773633.
diff -Nru flashplugin-nonfree-3.6/debian/changelog
flashplugin-nonfree-3.6.1/debian/changelog
--- flashplugin-nonfree-3.6/debian/changelog2014-09-15 18:30:41.0
+0200
+++ flashplugin-nonfree-3.6.1/debian/changelog 2014-12-21 10:03:31.0
+0100
@@ -1,3 +1,9 @@
+flashplugin-nonfree (1:3.6.1) unstable; urgency=medium
+
+ * debian/control: Pre-Depends: ca-certificates. Closes: #773633.
+
+ -- Bart Martens ba...@debian.org Sun, 21 Dec 2014 10:02:23 +0100
+
flashplugin-nonfree (1:3.6) unstable; urgency=medium
* debian/control: Depends: ca-certificates. Closes: #760638.
diff -Nru flashplugin-nonfree-3.6/debian/control
flashplugin-nonfree-3.6.1/debian/control
--- flashplugin-nonfree-3.6/debian/control 2014-09-15 19:04:40.0
+0200
+++ flashplugin-nonfree-3.6.1/debian/control2014-12-21 10:03:54.0
+0100
@@ -8,7 +8,8 @@
Package: flashplugin-nonfree
Architecture: i386 amd64
-Depends: debconf | debconf-2.0, wget, gnupg, libatk1.0-0, libcairo2,
libfontconfig1, libfreetype6, libgcc1, libglib2.0-0, libgtk2.0-0 (= 2.14),
libnspr4, libnss3, libpango1.0-0, libstdc++6, libx11-6, libxext6, libxt6,
libcurl3-gnutls, binutils, ${misc:Depends}, ${shlibs:Depends}, ca-certificates
+Depends: debconf | debconf-2.0, wget, gnupg, libatk1.0-0, libcairo2,
libfontconfig1, libfreetype6, libgcc1, libglib2.0-0, libgtk2.0-0 (= 2.14),
libnspr4, libnss3, libpango1.0-0, libstdc++6, libx11-6, libxext6, libxt6,
libcurl3-gnutls, binutils, ${misc:Depends}, ${shlibs:Depends}
+Pre-Depends: ca-certificates
Suggests: iceweasel, konqueror-nsplugins, ttf-mscorefonts-installer,
fonts-dejavu, ttf-xfree86-nonfree, flashplugin-nonfree-extrasound [i386], hal
Conflicts: flashplugin ( 6), xfs ( 1:1.0.1-5), flashplayer-mozilla,
libflash-mozplugin
Replaces: flashplugin ( 6)
Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)
Here is the tail of dmesg after such an error. Best regards Tom Guder [ 1104.412089] radeon :02:00.0: ring 0 stalled for more than 10104msec [ 1104.412098] radeon :02:00.0: GPU lockup (waiting for 0x000664a0 last fence id 0x0006649f on ring 0) [ 1104.412102] radeon :02:00.0: failed to get a new IB (-35) [ 1104.900461] radeon :02:00.0: Saved 21357 dwords of commands on ring 0. [ 1104.900590] radeon :02:00.0: GPU softreset: 0x006C [ 1104.900592] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1104.900593] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1104.900594] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1104.900595] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1104.900706] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1104.900707] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1104.900708] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1104.900710] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [ 1104.900711] radeon :02:00.0: R_008680_CP_STAT = 0x80010243 [ 1104.900713] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83146 [ 1104.900714] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [ 1104.900716] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1104.900718] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [ 1105.370049] radeon :02:00.0: GRBM_SOFT_RESET=0xDDFF [ 1105.370101] radeon :02:00.0: SRBM_SOFT_RESET=0x00100140 [ 1105.371247] radeon :02:00.0: GRBM_STATUS = 0x3028 [ 1105.371248] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1105.371249] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1105.371250] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1105.371361] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1105.371362] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1105.371363] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x [ 1105.371365] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x [ 1105.371366] radeon :02:00.0: R_008680_CP_STAT = 0x [ 1105.371367] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 1105.371369] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ 1105.371608] radeon :02:00.0: GPU reset succeeded, trying to resume [ 1105.402616] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [ 1105.402619] [drm] PCIE gen 3 link speeds already enabled [ 1105.404456] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [ 1105.404557] radeon :02:00.0: WB enabled [ 1105.404559] radeon :02:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8800b54c0c00 [ 1105.404560] radeon :02:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x8800b54c0c04 [ 1105.404561] radeon :02:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x8800b54c0c08 [ 1105.404561] radeon :02:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x8800b54c0c0c [ 1105.404562] radeon :02:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x8800b54c0c10 [ 1105.405169] radeon :02:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90011fb5a18 [ 1105.564971] [drm] ring test on 0 succeeded in 2 usecs [ 1105.564978] [drm] ring test on 1 succeeded in 1 usecs [ 1105.564984] [drm] ring test on 2 succeeded in 1 usecs [ 1105.564995] [drm] ring test on 3 succeeded in 5 usecs [ 1105.565005] [drm] ring test on 4 succeeded in 5 usecs [ 1105.740770] [drm] ring test on 5 succeeded in 2 usecs [ 1105.740776] [drm] UVD initialized successfully. [ 1115.740176] radeon :02:00.0: ring 0 stalled for more than 1msec [ 1115.740183] radeon :02:00.0: GPU lockup (waiting for 0x000665a7 last fence id 0x0006649f on ring 0) [ 1115.740187] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 1115.740192] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 1115.740195] radeon :02:00.0: ib ring test failed (-35). [ 1116.221093] radeon :02:00.0: GPU softreset: 0x0048 [ 1116.221095] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1116.221097] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1116.221098] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1116.221099] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1116.221210] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1116.221211] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1116.221212] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1116.221214] radeon
Bug#773637: grub2: [INTL:nl] Dutch translation of debconf messages
Package: grub2 Severity: wishlist Tags: l10n patch Dear Maintainer, == Please find attached the Dutch translation of grub2 debconf messages. It has been submitted for review to the debian-l10n-dutch mailing list. Please add it to your next package revision. It should be put as debian/po/nl.po in your package build tree. === Groetjes, Frans === www.frans-spiesschaert.homenet.org home.base.be/vt6362833/ nl.po.gz Description: Binary data
Bug#767037: Grub EFI fallback - patches for review
On Sat, 2014-12-20 at 09:45 +0100, David Härdeman wrote: one option that doesn't seem to have been considered would be to create a separate package (let's call it UEFIx) that installs an UEFI binary to EFI/boot/bootx64.efi. That binary could then do what the UEFI BIOS should've done (i.e. look at the EFI vars for bootorder, bootnext, etc and then go on to load the right bootloader). Interesting idea, does this stub bootloader already exist, or is it something someone would need to write? (Either way I think it's likely too late for Jessie, but perhaps something to think about for Stretch) I'd also have some worries about packages installing to /boot/EFI since that is by definition going to be a VFAT filesystem and I'm not confident that dpkg will work fully/safely without all the POSIX-ish semantics (hardlinks, atomic updates and the like), might want to handle that by installing via the postinst instead of shipping in /boot/EFI. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773191: python-ogg-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi Jean-Michel, Thanks for your work, I will fix the package soon from dpmt repo; and yes the right solution is to use dpkg maint scripts to fix the dir-link transition. Regards, Sandro Il 21/dic/2014 02:57 Jean-Michel Nirgal Vourgère jmv_...@nirgal.com ha scritto: Jean-Michel Nirgal Vourgère: This problem was introduced in commit 27848, where d/rules target override_dh_installdocs got an extraneous dh_installdocs: The second one try to make the link but fails because the first one created a directory with that name. Actually, there is a problem when uploading from version -6 in my proposal above. That version is not in wheezy and probably will not be in jessie either, so this is not a big deal. But to do things properly, one need to use a maintscript with a dir_to_symlink. I tested fresh installs and upgrades both from -6 and straight from -5. I could not detect any problem with dir_to_symlink when there is already a symlink, like in -5. :) I updated the version on mentors. See previous mail.
Bug#732440: Patch not present in Jessie?
I just got this error. Is it going to be fixed in Jessie?
Bug#773638: unblock: pepperflashplugin-nonfree/1.8.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock pepperflashplugin-nonfree 1.8.1 to fix bug 773629 in jessie.
Output
of debdiff attached. The only change is that ca-certificates is moved from
Depends to Pre-Depends. The effect is illustrated on bug 773629.
diff -Nru pepperflashplugin-nonfree-1.8/debian/changelog
pepperflashplugin-nonfree-1.8.1/debian/changelog
--- pepperflashplugin-nonfree-1.8/debian/changelog 2014-10-22
08:29:52.0 +0200
+++ pepperflashplugin-nonfree-1.8.1/debian/changelog2014-12-21
11:38:47.0 +0100
@@ -1,3 +1,9 @@
+pepperflashplugin-nonfree (1.8.1) unstable; urgency=medium
+
+ * debian/control: Pre-Depends: ca-certificates. Closes: #773629.
+
+ -- Bart Martens ba...@debian.org Sun, 21 Dec 2014 11:37:47 +0100
+
pepperflashplugin-nonfree (1.8) unstable; urgency=medium
* Removed support for /etc/chromium/default. Closes: #760388.
diff -Nru pepperflashplugin-nonfree-1.8/debian/control
pepperflashplugin-nonfree-1.8.1/debian/control
--- pepperflashplugin-nonfree-1.8/debian/control2014-10-22
08:31:48.0 +0200
+++ pepperflashplugin-nonfree-1.8.1/debian/control 2014-12-21
11:40:47.0 +0100
@@ -8,7 +8,8 @@
Package: pepperflashplugin-nonfree
Architecture: i386 amd64
-Depends: debconf | debconf-2.0, wget, gnupg, libatk1.0-0, libcairo2,
libfontconfig1, libfreetype6, libgcc1, libglib2.0-0, libgtk2.0-0 (= 2.14),
libnspr4, libnss3, libpango-1.0-0 | libpango1.0-0, libstdc++6, libx11-6,
libxext6, libxt6, libcurl3-gnutls, binutils, ${misc:Depends},
${shlibs:Depends}, ca-certificates
+Depends: debconf | debconf-2.0, wget, gnupg, libatk1.0-0, libcairo2,
libfontconfig1, libfreetype6, libgcc1, libglib2.0-0, libgtk2.0-0 (= 2.14),
libnspr4, libnss3, libpango-1.0-0 | libpango1.0-0, libstdc++6, libx11-6,
libxext6, libxt6, libcurl3-gnutls, binutils, ${misc:Depends}, ${shlibs:Depends}
+Pre-Depends: ca-certificates
Suggests: chromium, ttf-mscorefonts-installer, ttf-dejavu,
ttf-xfree86-nonfree, hal
Conflicts: libflash-mozplugin, chromium ( 37.0.2062.120-4)
Description: Pepper Flash Player - browser plugin
Bug#773639: use cron.daily cron script
Package: debsecan Version: 0.4.16+nmu1 please use cron script in cron.daily. This will cause run debsecan AFTER apt, which means the debsecan cron will NOT be run before unattended-upgrades fix packages and will not report vulnerabilities fixed in cron.daily job. as a sideeffect it will: - simplify cron processing - show the cron job in dpkg -L output (bug #345256) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. It's now safe to throw off your computer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773639: use cron.daily cron script
severity 773639 wishlist thanks * Matus UHLAR: please use cron script in cron.daily. We can't because we don't want all clients to hit the web server at the same time (in each time zone). This will cause run debsecan AFTER apt, which means the debsecan cron will NOT be run before unattended-upgrades fix packages and will not report vulnerabilities fixed in cron.daily job. Maybe I could change the automatically generated crontab to run after the cron.daily scripts, but I'm not sure if all systems run cron.daily at the same time. - show the cron job in dpkg -L output (bug #345256) I can't fix this due to policy constraints. ghost file support (as in RPM) in dpkg would address this, though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773640: CVE-2014-9390: Errors in handling case-sensitive directories allow for remote code execution on pull
Package: mercurial Version: 3.1.2-1 Severity: important Tags: security upstream CVE-2014-9390[0][1] is a security vulnerability that affects mercurial repositories in a case-sensitive filesystem (eg. VFAT or HFS+). It allows for remote code execution of a specially crafted repository. This is less severe for the average Debian installation as they are usually set up with case-insensitive filesystems. [0] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9390 [1] https://security-tracker.debian.org/tracker/CVE-2014-9390 This affects both Wheezy and Jessie. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mercurial depends on: ii libc6 2.19-13 ii mercurial-common 3.1.2-1 ii python2.7.8-2 ii ucf 3.0030 Versions of packages mercurial recommends: ii openssh-client 1:6.7p1-3 Versions of packages mercurial suggests: pn kdiff3 | kdiff3-qt | kompare | meld | tkcvs | mgdiff none pn qct none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773641: unblock: mediawiki/1.19.20+dfsg-2.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mediawiki; it fixes CVE-2014-9277, which is a
security issue referenced in #772764. THe description of the problem
is as follows (taken from the recently released mediawiki DSA):
| The cross-domain-policy mangling in OutputHandler.php poses a
| potentially severe security problem for API clients written in
| PHP, in that format=php is affected.
unblock mediawiki/1.19.20+dfsg-2.1
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (501, 'stable'), (500, 'oldstable-proposed-updates'), (500,
'oldstable'), (1, 'unstable'), (1, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- Debdiff:
diff -Nru mediawiki-1.19.20+dfsg/debian/changelog
mediawiki-1.19.20+dfsg/debian/changelog
--- mediawiki-1.19.20+dfsg/debian/changelog 2014-10-07 20:14:04.0
+0200
+++ mediawiki-1.19.20+dfsg/debian/changelog 2014-12-14 18:27:31.0
+0100
@@ -1,3 +1,12 @@
+mediawiki (1:1.19.20+dfsg-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * CVE-2014-9277: The cross-domain-policy mangling in OutputHandler.php
+poses a potentially severe security problem for API clients written in
+PHP, in that format=php is affected (Closes: #772764).
+
+ -- Sebastien Delafond s...@debian.org Sun, 14 Dec 2014 18:23:47 +0100
+
mediawiki (1:1.19.20+dfsg-2) unstable; urgency=low
* Team upload.
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_1.patch
mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_1.patch
--- mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_1.patch 1970-01-01
01:00:00.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_1.patch 2014-12-14
18:22:36.0 +0100
@@ -0,0 +1,32 @@
+--- a/includes/DefaultSettings.php
b/includes/DefaultSettings.php
+@@ -2688,6 +2688,14 @@
+ */
+ $wgResourceLoaderExperimentalAsyncLoading = false;
+
++/**
++ * When OutputHandler is used, mangle any output that contains
++ * cross-domain-policy. Without this, an attacker can send their own
++ * cross-domain policy unless it is prevented by the crossdomain.xml file at
++ * the domain root.
++ */
++$wgMangleFlashPolicy = true;
++
+ /** @} */ # End of resource loader settings }
+
+
+--- a/includes/OutputHandler.php
b/includes/OutputHandler.php
+@@ -13,8 +13,10 @@
+ * @return string
+ */
+ function wfOutputHandler( $s ) {
+- global $wgDisableOutputCompression, $wgValidateAllHtml;
+- $s = wfMangleFlashPolicy( $s );
++ global $wgDisableOutputCompression, $wgValidateAllHtml,
$wgMangleFlashPolicy;
++ if ( $wgMangleFlashPolicy ) {
++ $s = wfMangleFlashPolicy( $s );
++ }
+ if ( $wgValidateAllHtml ) {
+ $headers = apache_response_headers();
+ $isHTML = true;
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_2.patch
mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_2.patch
--- mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_2.patch 1970-01-01
01:00:00.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/CVE-2014-9277_2.patch 2014-12-14
18:22:36.0 +0100
@@ -0,0 +1,53 @@
+--- a/includes/api/ApiFormatJson.php
b/includes/api/ApiFormatJson.php
+@@ -67,9 +67,21 @@
+ $prefix = ( /**/$prefix );
+ $suffix = ')';
+ }
++
++ $json = FormatJson::encode( $this-getResultData(),
$this-getIsHtml() );
++
++ // Bug 66776: wfMangleFlashPolicy() is needed to avoid a nasty
bug in
++ // Flash, but what it does isn#039;t friendly for the API, so
we need to
++ // work around it.
++ if ( preg_match( #039;/\\s*cross-domain-policy\s*\/i#039;,
$json ) ) {
++ $json = preg_replace(
++ #039;/\(\s*cross-domain-policy\s*)\/i#039;,
#039;\\u003C$1\\u003E#039;, $json
++ );
++ }
++
+ $this-printText(
+ $prefix .
+- FormatJson::encode( $this-getResultData(),
$this-getIsHtml() ) .
++ $json .
+ $suffix
+ );
+ }
+--- a/includes/api/ApiFormatPhp.php
b/includes/api/ApiFormatPhp.php
+@@ -39,7 +39,24 @@
+ }
+
+ public function execute() {
+- $this-printText( serialize( $this-getResultData() ) );
++ global $wgMangleFlashPolicy;
++ $text = serialize( $this-getResultData() );
++
++ // Bug 66776: wfMangleFlashPolicy() is needed to avoid a nasty
bug in
++ // Flash, but what it does isn#039;t friendly for the API.
There#039;s nothing
++ // we can do here that isn#039;t actively broken
Bug#773642: jenkins-job-builder: deleting jobs is completly broken
package: jenkins-job-builder severity: important tags: patch upstream version: 0.9.0-0.1 Hi, trying to delete a job results in this: root@hestia:/srv/jenkins/job-cfg# chroot /root/jessie/ su jenkins -c jenkins- jobs delete kali_build_rolling_armel INFO:root:Deleting jobs in [kali_build_rolling_armel] Traceback (most recent call last): File /usr/bin/jenkins-jobs, line 10, in module sys.exit(main()) File /usr/share/jenkins-job-builder/jenkins_jobs/cmd.py, line 119, in main execute(options, config) File /usr/share/jenkins-job-builder/jenkins_jobs/cmd.py, line 204, in execute builder.delete_job(job, options.path) File /usr/share/jenkins-job-builder/jenkins_jobs/builder.py, line 611, in delete_job self.load_files(fn) File /usr/share/jenkins-job-builder/jenkins_jobs/builder.py, line 576, in load_files if os.path.isdir(path): File /usr/lib/python2.7/genericpath.py, line 41, in isdir st = os.stat(s) TypeError: coercing to Unicode: need string or buffer, NoneType found The upstream commit https://git.openstack.org/cgit/openstack-infra/jenkins- job-builder/commit/?id=b7ff37ca5dfa1e7387c636b8b0108404a0bf has the fix. The workaround is easy (rm -r $job_directory), so I've only filed this with severity important, but I do think this should be fixed for jessie. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Package: initramfs-tools Version: 0.118 Severity: important Dear Debian folks, since some time, the filesystem type of the LUKS encrypted root partition (/) is not detected. $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Warning: couldn't identify filesystem type for fsck hook, ignoring. setupcon is missing. Please install the 'console-setup' package. $ mount […] /dev/mapper/luks-6fb2f31d-ca5f-4c02-b120-13fd929fcac1 on / type ext4 (rw,noatime,discard,errors=remount-ro,commit=600,data=ordered) […] Unfortunately, I do not know when started. Either due to a `initramfs-tool` upgrade or testing `dracut`, where I had to switch to using UUIDs. Thanks, Paul -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii busybox1:1.22.0-14 ii cpio 2.11+dfsg-2+b1 ii klibc-utils2.0.4-2 ii kmod 18-3 ii module-init-tools 18-3 ii udev 215-8 ii util-linux 2.25.2-4 Versions of packages initramfs-tools recommends: ii busybox 1:1.22.0-14 Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4 -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#773644: gnome-session-flashback: Applications with header bar do not show fallback menus in flashback session, no way to access menu
Package: gnome-session-flashback Version: 3.8.1-7 Severity: important Gnome applications with header bar do not show their fallback menus in flashback session. I also tried the newer flashback package from experimental, but without success. This seems to be related to this list message: https://mail.gnome.org/archives/gnome-flashback-list/2014-September/msg00019.html I have not found any indication that these patches already exist, but maybe someone with knowledge of these things does know what to do here? I think this problem quite severely limits the usability of several gnome applications in the flashback session currently in jessie. thanks florian -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-session-flashback depends on: ii gnome-flashback3.10.0-3 ii gnome-panel3.8.1-7 ii gnome-screensaver 3.6.1-2 ii gnome-session-bin 3.14.0-2 ii gnome-session-common 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii metacity 1:3.14.3-1 ii nautilus 3.14.1-2 ii notification-daemon0.7.6-2 ii policykit-1-gnome 0.105-2 Versions of packages gnome-session-flashback recommends: ii gnome-power-manager 3.14.1-1 Versions of packages gnome-session-flashback suggests: ii desktop-base 8.0.2 ii gnome-keyring 3.14.0-1+b1 ii gnome-user-guide 3.14.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773640: CVE-2014-9390: Errors in handling case-sensitive directories allow for remote code execution on pull
On Sun, Dec 21, 2014 at 12:38:02PM +0100, Javi Merino wrote: Package: mercurial Version: 3.1.2-1 Severity: important Tags: security upstream CVE-2014-9390[0][1] is a security vulnerability that affects mercurial repositories in a case-sensitive filesystem (eg. VFAT or HFS+). It allows for remote code execution of a specially crafted repository. This is less severe for the average Debian installation as they are usually set up with case-insensitive filesystems. [0] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9390 [1] https://security-tracker.debian.org/tracker/CVE-2014-9390 This affects both Wheezy and Jessie. In Ubuntu[0] they've fixed it by applying the following patches: - http://selenic.com/repo/hg-stable/rev/035434b407be - http://selenic.com/repo/hg-stable/rev/885bd7c5c7e3 - http://selenic.com/repo/hg-stable/rev/c02a05cc6f5e - http://selenic.com/repo/hg-stable/rev/7a5bcd471f2e - http://selenic.com/repo/hg-stable/rev/6dad422ecc5a [0] https://bugs.launchpad.net/ubuntu/+source/git/+bug/1404035 [1] https://launchpadlibrarian.net/193058010/mercurial_3.1.2-1ubuntu1_source.changes I'm working on applying the same patches. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773645: debian-cd: [armhf/armel/arm64] u-boot-tools missing on CD1 - d-i fails
Package: debian-cd Severity: important Hello, in the current daily CD builds, the first armhf CD does not include the package u-boot-tools. This package is required by d-i to make the system bootable at the end of the installation on nearly all armhf systems. As a consequence, single-CD installations, respectively hd-media installations that use the first CD iso, fail completely if no network access is available during the d-i run. From looking at the flash-kernel machine database, the situation will probably be the same for armel and arm64, so please include u-boot-tools on the first CD for armhf/armel/arm64. From the d-i log with CD1 but no network access: in-target: Setting up flash-kernel (3.28) ... in-target: in-target: Creating config file /etc/default/flash-kernel with new version^ in-target: Reading package lists... in-target: in-target: Building dependency tree... in-target: in-target: Reading state information... in-target: in-target: Package u-boot-tools is not available, but is referred to by another package. in-target: This may mean that the package is missing, has been obsoleted, or in-target: is only available from another source in-target: in-target: E: Package 'u-boot-tools' has no installation candidate flash-kernel-installer: error: apt-install u-boot-tools failed Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773639: use cron.daily cron script
* Matus UHLAR: please use cron script in cron.daily. On 21.12.14 12:20, Florian Weimer wrote: We can't because we don't want all clients to hit the web server at the same time (in each time zone). I believe this could be fixed by letting it waiting in the background for random time. This will cause run debsecan AFTER apt, which means the debsecan cron will NOT be run before unattended-upgrades fix packages and will not report vulnerabilities fixed in cron.daily job. Maybe I could change the automatically generated crontab to run after the cron.daily scripts, but I'm not sure if all systems run cron.daily at the same time. They do not, especially with anacron. That's why it has to run from cron.daily job to run after apt. - show the cron job in dpkg -L output (bug #345256) I can't fix this due to policy constraints. ghost file support (as in RPM) in dpkg would address this, though. this would natively work if the cron job was part of the package. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Windows 2000: 640 MB ought to be enough for anybody -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773550: autoremoval problem on gnome wheezy to jessie upgrades
Hi Joss, On Samstag, 20. Dezember 2014, Josselin Mouette wrote: Most of these candidates look fine to me. They are packages removed from the dependency tree of the “gnome” metapackage in jessie, and there’s nothing wrong with that. Except for libreoffice. Which brings us to the java problems, mostly related to LO as well. what's your proposal for that, is there a bug about this? much and fails when it try to remove sudo. (This failure to remove sudo is a feature and not subject of this bug report..) I see. sudo removes fine if a root password is set, this how piuparts solves this issue. I think it's also possible to force something else with SUDO_SOME_VAR, but I might be wrong... This is because nothing in GNOME depends on sudo/gksu anymore. And this was the way sudo was kept in the dependency tree. Given the usefulness of this package, but its absence of relation to GNOME, I think a dependency on sudo should be added to task-desktop. Would it be OK to reassign? I'd be totally fine with that. Bugs are for everyone and can be easily cloned and reassigned (and closed too :) Thanks! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#772233: bashism in /bin/sh script
Hi, On Samstag, 20. Dezember 2014, Bálint Réczey wrote: I made a typo in the bug number, please see the fixed patch attached. I also reuploaded the package to DELAYED/2. looks good to me, thanks for your work, Balint! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#770615: mate-session-manager: Switching users don't work with MATE and Lightdm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2014 03:32 PM, Mike Gabriel wrote: After looking at mate-session-manager code, I am not even sure if this feature in relation to LightDM will be available for MATE 1.10. It definitely won't be in Debian jessie (MATE 1.8). Actually, it might be easier than you would think. The session-manager tries to start a new greeter using the 'gdmflexiserver' command which is not available on lightdm. However, lightdm provides the command 'dm-tool' which allows to start a new greeter using the following command: dm-tool switch-to-greeter If you replace /usr/bin/gdmflexiserver with a simple bash script as described here [1], you will be able to switch users from the mate-screensaver lock screen using the Switch User button. It works absolutely fine except that after the new user has logged out, the new greeter session is not killed and the screen returns back to the lightdm greeter instead of the lock screen of the previously logged in user. Clicking Cancel in the new lightdm greeter session doesn't help either. In any case, to get this implemented into the code, we would need to define LIGHTDM_FLEXISERVER_COMMAND in mate-session/gsm-manager.c as dm-tool and LIGHTDM_FLEXISERVER_ARGS as switch-to-greeter. If we figured out how to kill the new lightdm greeter after the second user has logged out or someone clicked Cancel in the new lightdm greeter session, user switching would work as expected with lightdm. Cheers, Adrian [1] https://wiki.archlinux.org/index.php/LightDM#User_switching_under_Xfce4 - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUlsCKAAoJEHQmOzf1tfkT42MP/ix6yJMkBo/NVRfaFjXolsvz WmTJwfeTz/RkVDlhaeXWNR0shCtiIOJEyh/lNORW+5QgW3O03wRReu+fdeYp2j7z EUfTENZppWoLm4gEoT1xOms6HiNIhcqHFghfyVLVcux56Mzi3gTnPMtuB8Gqh1wQ eS5yURcQBsMpB7FCc68peyjdOFVCuV8f73862tKzXh6I24abM8P+i+Lo3DGAv5ye A6VOnRRCT/mGO+SyG1FcP32lbrv90fKVf7WNiMidq5BtasBcENfMZjJIwUZ1et0J QH/BsFPhi1vbgdxMpQ7rSgVuaXTwmuhuIO9oSnSxlChMA4BjCmJ/TJwTvilCVxbI xKA2k2lqbFBYL2xiaxZTZdjrBEFsVXFsHXOFmffpvsUGhrN3KAozWNKRSJbgCC19 oB1oLvS74l30cQXy1Vfbm0KPo3i1nv6LVzr0RpOSA9VP1R8MxAJduyvji4bAU83m ODmrpXy9pBfRggdEry1iP6JGWzwwzdWsE8dezlSdCLoECok4r5M60ui4VTCcSgX+ Kdjg3VSLRtUNRsSPtPZV8LbfDY8iuGga01fjlMRCz6lsGqNGKZXKPJ0DoRQS0m4P fo7UoKTysL71r9e1iUAcGic1na2P4FtuTtWV0CLBIbRHp6iLIygRqYJvs7f7vVRG z8LYsoPirGN+bc0jFYk9 =yMF7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766829:
The message is also displayed in kernel 3.18 from experimental. -- Thiago Bellini Ribeiro http://hackedbellini.org PGP: D70FD60E “Real knowledge is to know the extent of one's ignorance.” - Confucius -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767468: autofs: mounts may fail with 'Too many levels of symbolic links' when using cgmanager
Hello Petter! Note, autofs is an important part of the Debian Edu infrastructure, used to mount home directories and shared directories on the clients of the Debian Edu main server. It is important to us that the autofs package stay in Jessie. :) Since the bug seems only to affect systems using cgmanager instead of systemd for the CGroup management and assuming - since you are one of the maintainers of the sysvinit package - you are preferring sysvinit over systemd, I highly suggest that you extensively test autofs on a system with sysvinit and cgmanager and possibly re-assign the bug from the autofs to the cgmanager package. My suspicion is that this is actually bug in cgmanager and not autofs and will affect all systems that are using autofs with alternative init systems. I haven't seen the bug ever since I purged the cgmanager package as I am running systemd-only installations anyway. cgmanager was installed on these systems during a dist-upgrade but isn't actually required at all since systemd does CGroup management on its own. You might risk autofs not working on installations not using systemd. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771877: original symlink target is not an absolute path on libdb5.3-java_5.3.28-7~deb8u1
The post-removal script fails during the upgrade of libdb5.3-java from version 5.3.28-6 to 5.3.28-7~deb8u1. dpkg-maintscript-helper says « error: original symlink target is not an absolute path ». I assume this is linked to the symlink_to_dir that has been solved but my apt stays blocked on this error, probably because I've installed the buggous version of the package. Is there a way to solve it ? Tangui -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772994: [lack-of] update
Hi, Just FTR, I don't propose to upload a new version of this package until after the freeze, unless an RC bug is found, since it's a library package. Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
Package: linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1 Version: 3.16.7 After installing the Backport Package the system cannot boot with the new kernel. The System hangs and falls back to dracut console. It mentions that the root filesystem UID cannot not be found. The system itself has a boot disk (vda3) and the root is on (vda1). I checked the grub.cfg the Filesystem uid's are correct. Reboot to the original kernel 3.2.0 works though. During the installation of the Backport Kernel dracut warns that it can not find consolefonts, ... (the rest I can't remember, sadly not logged) Looks to me that some depencies are not in the package which are necessary when initramfs is replaced with dracut. I am using Debian GNU/Linux 7, Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773465: unblock: exim4/4.84-5
Control: retitle -1 unblock: exim4/4.84-6 On 2014-12-20 Julien Cristau jcris...@debian.org wrote: On Fri, Dec 19, 2014 at 18:43:46 +0100, Andreas Metzler wrote: [...] I can either back out this change for jessie and re-upload or can upload a better fix. - I guess I will add a something like --dry-run to /usr/sbin/update-exim4.conf. Which of these options would you prefer? I'm not sure, so I'm happy to trust your judgement on that, just wanted to raise the potential issue. Thank you. I have just uploaded -6 with this change reverted. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: Digital signature
Bug#773647: pm-utils: wireless: fix for typo wasn't fix
Source: pm-utils Version: 1.4.1-15 Severity: normal Hi, The changelog for 1.4.1-15 says: * Add 17-fix-wireless-hook.patch: Fix typo in wireless hook to make enabled check actually work. Thanks to Whoopie! (LP: #1299975) LP #1299975 says: I discovered an invalid check in '/usr/lib/pm-utils/power.d/wireless'. The script checks '/sys/class/net/$1/device/enable' to see if the wireless device is enabled, failing to perform any configuration if this sys file does not exist. That happens to be the case for me (intel wireless), which the actual location is '/sys/class/net/$1/device/enabled' (enable - enabled). However, on my laptop with a BCM4360 (wifi), and my desktop with a Qualcomm Atheros AR8151, both with a 3.16.7-ckt2-1 kernel, the actual location is in fact enable. There seems to be a discrepancy in how these files are named. I have not yet located the documenation for the canonical way of naming these files, although the output of `find /sys/devices -name 'enable*'` suggests that enable is the correct spelling, and the few uses of enabled seem to be read-only locations -- ie, for retrieving status, not changing it. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773649: wheezy-pu: package freecol/0.10.5+dfsg-2
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Dear release Team,
I wish to update the freecol package in wheezy, where it is affected
by #771700 (hangs at startup). The patch, attached is minimal and has
been shown to work in unstable.
Is that OK for you ?
Cheers,
Vincent
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14.0+p (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru freecol-0.10.5+dfsg/debian/changelog freecol-0.10.5+dfsg/debian/changelog
--- freecol-0.10.5+dfsg/debian/changelog 2012-03-06 00:10:28.0 +0100
+++ freecol-0.10.5+dfsg/debian/changelog 2014-12-20 23:57:25.0 +0100
@@ -1,3 +1,11 @@
+freecol (0.10.5+dfsg-2) stable; urgency=low
+
+ * Disable intro video to avoid hanging at startup (closes: #771700)
+ * Conforms to 3.9.5
+ * Build with openjdk-7 when available
+
+ -- Vincent Fourmond fourm...@debian.org Sat, 20 Dec 2014 23:57:15 +0100
+
freecol (0.10.5+dfsg-1) unstable; urgency=low
* New upstream release
diff -Nru freecol-0.10.5+dfsg/debian/control freecol-0.10.5+dfsg/debian/control
--- freecol-0.10.5+dfsg/debian/control 2012-03-06 00:09:54.0 +0100
+++ freecol-0.10.5+dfsg/debian/control 2014-12-20 23:57:05.0 +0100
@@ -3,19 +3,19 @@
Priority: optional
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Uploaders: Vincent Fourmond fourm...@debian.org
-Build-Depends: debhelper (= 5), ant, openjdk-6-jdk, cdbs
+Build-Depends: debhelper (= 5), ant, openjdk-7-jdk | openjdk-6-jdk, cdbs
Build-Depends-Indep:
tex4ht, texlive-binaries | texlive-base-bin, ant-optional,
texlive-latex-recommended, libcommons-cli-java, libmiglayout-java,
libcortado-java, javahelper
-Standards-Version: 3.9.3
+Standards-Version: 3.9.5
Homepage: http://www.freecol.org
Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/freecol
Vcs-Browser: http://svn.debian.org/viewsvn/pkg-games/packages/trunk/freecol
Package: freecol
Architecture: all
-Depends: openjdk-6-jre | java6-runtime,
+Depends: openjdk-7-jre | openjdk-6-jre | java6-runtime,
java-wrappers (= 0.1.13), ${misc:Depends}, ${java:Depends},
fonts-liberation (= 1.07.0-2~)
Description: open source remake of the old Colonization
diff -Nru freecol-0.10.5+dfsg/debian/wrapper/freecol freecol-0.10.5+dfsg/debian/wrapper/freecol
--- freecol-0.10.5+dfsg/debian/wrapper/freecol 2012-01-31 00:42:22.0 +0100
+++ freecol-0.10.5+dfsg/debian/wrapper/freecol 2014-12-20 23:39:11.0 +0100
@@ -24,5 +24,5 @@
disablenet=-Djava.net.preferIPv4Stack=true
fi
-run_java $disablenet -Xincgc -Xmx512M net.sf.freecol.FreeCol --freecol-data \
+run_java $disablenet -Xincgc -Xmx512M net.sf.freecol.FreeCol --no-intro --freecol-data \
/usr/share/games/freecol $lang_argument $@
Bug#773648: [simple-scan] Regression: Canon LiDE 110 not scanning anymore
Package: simple-scan Version: 3.15.2-1 Severity: normal --- Please enter the report below this line. --- Hi there, scanning with a Canon LiDE 110 does not work anymore. The scanner is detected, but when the Scan button in simple-scan is pressed, I can here the scanner apparently doing a regular scan, but no data seems to be transmitted to simple-scan. Just the spinner is displayed. After a couple of seconds, simple-scan tells me, it had trouble to scan. After this, I have to un- and re-plug the scanner. If that step is omitted, the scanner seems to be left in a unusable state, because other applications can not use it. Though, the scanner has been working perfectly fine before im simple-scan and it still works perfectly fine in xsane. Cheers - Fuddl --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== dbus-x11 (= 1.8) | 1.8.12-1 gnome-icon-theme | 3.12.0-1 xdg-utils | 1.1.0~rc1+git20111210-7.1 dconf-gsettings-backend | 0.22.0-1 OR gsettings-backend | libc6 (= 2.14) | 2.19-13 libcairo2 (= 1.6.0) | 1.14.0-2.1 libcolord2(= 0.1.10) | 1.2.1-1+b2 libgdk-pixbuf2.0-0(= 2.22.0) | 2.31.1-2+b1 libglib2.0-0 (= 2.37.0) | 2.42.1-1 libgtk-3-0(= 3.9.10) | 3.14.5-1 libgudev-1.0-0 (= 146) | 215-8 libsane (= 1.0.11-3) | 1.0.24-7 zlib1g (= 1:1.1.4) | 1:1.2.8.dfsg-2+b1 Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- -- BEGIN ATTACHMENTS -- -- END ATTACHMENTS -- signature.asc Description: This is a digitally signed message part
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
Control: reassign -1 src:linux 3.16.7-ckt2-1~bpo70+1 On Sun, 2014-12-21 at 14:15 +0100, Mario Kothe wrote: Package: linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1 Version: 3.16.7 After installing the Backport Package the system cannot boot with the new kernel. The System hangs and falls back to dracut console. It mentions that the root filesystem UID cannot not be found. The system itself has a boot disk (vda3) and the root is on (vda1). I checked the grub.cfg the Filesystem uid's are correct. Reboot to the original kernel 3.2.0 works though. During the installation of the Backport Kernel dracut warns that it can not find consolefonts, ... (the rest I can't remember, sadly not logged) Looks to me that some depencies are not in the package which are necessary when initramfs is replaced with dracut. Presumably that would be a dracut bug. I am using Debian GNU/Linux 7, Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux What happens if you install initramfs-tools from wheezy-backports? Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#773256: pre-approval: unblock: dpkg/1.17.23
Hi, On Sonntag, 21. Dezember 2014, Niels Thykier wrote: As I recall, it is not a requirement - but I believe we can recommend it in the release-notes. Although, with the Breaks being added to dpkg for trigger issues, you would quite possibly pull in additional upgrades along with it. By upgrading specific packaging tools, I presume you mean something like: I've now aded a second type of upgrade tests to https://jenkins.debian.net/view/chroot-installation/ so now there are eg wheezy2jessie upgrades and wheezy2jessie dpkgapt_first upgrade jobs, in which apt-get install -y dpkg apt is run before apt-get upgrade is tried as usual... First results should be available in 1-2h, the relevant jobs have been triggered, but there is a queue of jobs waiting to be run :) HTH! :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#717287: munin-plugins-core: cpuspeed plugin doesn't work with kernel 3.10
On Fri, 12 Dec 2014 14:58:53 +0100, Francois Gouget wrote: Message 45 claims that with the latest linux-image-3.16.0-4-amd64 this issue is solved. However this does not seem to be the case here: # dpkg -l linux-image-3.16.0-4-amd64 ii linux-image-3.16.0-4-amd64 3.16.7-2 amd64 Linux 3.16 for 64-bit PCs # lsmod | grep cpufreq_stats cpufreq_stats 12782 0 # ls /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state ls: cannot access /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state: No such file or directory Same with 3.18.0-trunk-amd64. cpufreq_stats is loaded but there are no /sys/devices/system/cpu/cpu*/cpufreq/stats directories. What vicious (aweseome widget library) is doing in its cpufreq.lua: local cpufreq = helpers.pathtotable(/sys/devices/system/cpu/cpu..n../cpufreq) local freq = tonumber(cpufreq.scaling_cur_freq) or tonumber(cpufreq.cpuinfo_cur_freq) in some old (or locally patched?) version, and local cpufreq = helpers.pathtotable(/sys/devices/system/cpu/..warg../cpufreq) local freq = tonumber(cpufreq.scaling_cur_freq) in the packaged version. I guess someone should find out where cpufreq_stats actually exports its values; otherwise looking for /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq might be an alternative. Although admittedly this only gives a snapshot, while /stats/time_in_state is supposed to have some, well, statistics over time. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Supertramp: Where There's A Will signature.asc Description: Digital Signature
Bug#772811: unrtf: CVE-2014-9274 CVE-2014-9275
Hi Willi, On Sun, Dec 14, 2014 at 10:10:58AM +0100, Willi Mann wrote: Hi Dave, does 0.21.7 solve both security issues reported? If yes, could point send me the individual patches that fix these issues? The Debian branch for the next stable distribution is already frozen, so I cannot fix these bugs with new upstream versions. The three required commits are referenced now in Red Hat's Bugzilla entry at [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1170233 Jean-Francois Dockes proposed fixes for both CVEs. CVE-2014-9274 is addressed by https://lists.gnu.org/archive/html/bug-unrtf/2014-12/msg0.html CVE-2014-9275 is addressed by https://lists.gnu.org/archive/html/bug-unrtf/2014-12/msg1.html All three changes were incorporated upstream and shipped as a part of unrtf 0.21.6. (http://hg.savannah.gnu.org/hgweb/unrtf/rev/891c2f431c90) Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773649: wheezy-pu: package freecol/0.10.5+dfsg-2
Control: tags -1 + moreinfo On Sun, 2014-12-21 at 14:41 +0100, Vincent Fourmond wrote: I wish to update the freecol package in wheezy, where it is affected by #771700 (hangs at startup). The patch, attached is minimal and has been shown to work in unstable. The patch for the bug itself does appear to be minimal and fine, but looking at the changelog: +freecol (0.10.5+dfsg-2) stable; urgency=low We'd tend to suggest 0.10.5+dfsg-1+deb7u1, but as long as 0.10.5+dfsg-2 has never been used before then it'll be okay. + * Disable intro video to avoid hanging at startup (closes: #771700) Fine. + * Conforms to 3.9.5 + * Build with openjdk-7 when available Neither of these two changes appears to be related to the fix for #771700? 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#760385: lowering severity of bugs not tracked by release team
Hi Mike, First, I had to cancel the upload because of too strict reverse dependencies. Dear fellow JavaScript maintainers please figure out a less strict dependency graph because every otherwise fully compatible libv8 update would break several packages. 2014-12-21 2:13 GMT+01:00 Michael Gilbert mgilb...@debian.org: On Sat, Dec 20, 2014 at 7:52 PM, Bálint Réczey wrote: The proper severity of this bug is grave as set by Moritz IMO. I'm restoring it wearing my maintainer hat. It's not really constructive arguing over severity, so that's fine. I appreciate the work done by the Security Team but to work together we have to know what actions can be taken by the Security Team. Increasing severity of bugs is business as usual and perfectly reasonable, but _decreasing_ the severity _based on the availability of security support_ was crossing a line IMO. It seems the line was there based on Jonas' and Adam's email. To clarify my position the Security Team can and is expected to decrease the severity in case a security bug's impact turns out to be less than originally expected but in this particular case this rule does not seem to be applicable. You've saved yourself from needing to write an unblock request. The problem still remains that the backlog of libv8 security issues never get fixed (except for a new upstream every now and then), so treating this one as RC but not the others is rather inconsistent: https://security-tracker.debian.org/tracker/source-package/libv8 https://security-tracker.debian.org/tracker/source-package/libv8-3.14 If there were bugs opened for those CVE-s those should have been opened with grave severity, too. Note that unimportant there indicates lack of security support for the package. This is confusing. Please don't mark them as unimportant because in this context unimportant is defined differently. https://security-tracker.debian.org/tracker/status/unimportant : This page lists packages that are affected by issues that are considered unimportant from a security perspective. These issues are thought to be unexploitable or uneffective in most situations (for example, browser denial-of-services). If there is interest in security support for libv8, that is a good thing, but a lot more needs to be done for that to be true. Well, there is a long way to go, I agree. Thank you for helping the Security Team and keeping the bugs and CVE-s updated. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741195: gzip: stdin has more than one entry--rest ignored for zip file
I download Tomcat distribution and MC can't enter to archive. On Enter key just nothing happen. If press F3 I get error: gzip: stdin has more than one entry--rest ignored and next: Can not open ... in parse mode. No such file or directory. If I issue command: cd /path/to/archive.zip/unzip:// I can browse content. -- Best regards! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772811: unrtf: CVE-2014-9274 CVE-2014-9275
Control: tags -1 + patch
Hi Willi
Attached are two patches separated per CVEs.
Regards,
Salvatore
Description: CVE-2014-9274: out-of-bounds memory access
UnRTF allows remote attackers to cause a denial of service (crash) and
possibly execute arbitrary code as demonstrated by a file containing
the string {\cb-9.
Origin: upstream, https://bitbucket.org/medoc/unrtf-int/commits/b0cef89a170a66bc48f8dd288ce562ea8ca91f7a
Bug-Debian: https://bugs.debian.org/772811
Forwarded: no
Author: Jean-Francois Dockes j...@recoll.org
Last-Update: 2014-12-21
--- a/src/convert.c
+++ b/src/convert.c
@@ -868,6 +868,9 @@ process_color_table (Word *w)
r=g=b=0;
while(w) {
+if (total_colors = MAX_COLORS) {
+break;
+}
char *s = word_string (w);
if (!strncmp(\\red,s,4)) {
@@ -921,7 +924,7 @@ static int
cmd_cf (Word *w, int align, char has_param, int num) {
char str[40];
- if (!has_param || num=total_colors) {
+ if (!has_param || num 0 || num=total_colors) {
warning_handler (font color change attempted is invalid);
}
else
@@ -948,7 +951,7 @@ static int
cmd_cb (Word *w, int align, char has_param, int num) {
char str[40];
- if (!has_param || num=total_colors) {
+ if (!has_param || num 0 || num=total_colors) {
warning_handler (font color change attempted is invalid);
}
else
@@ -1153,7 +1156,7 @@ cmd_highlight (Word *w, int align, char
{
char str[40];
- if (!has_param || num=total_colors) {
+ if (!has_param || num 0 || num=total_colors) {
warning_handler (font background color change attempted is invalid);
}
else
Description: CVE-2014-9275: out-of-bounds memory access
UnRTF allows remote attackers to cause a denial of service
(out-of-bounds memory access and crash) and possibly execute arbitrary
code via a crafted RTF file.
Origin: upstream, https://bitbucket.org/medoc/unrtf-int/commits/1df886f2e65f7c512a6217588ae8d94d4bcbc63d,
https://bitbucket.org/medoc/unrtf-int/commits/3c7ff3f888de0f0d957fe67b6bd4bec9c0d475f3
Bug-Debian: https://bugs.debian.org/772811
Forwarded: no
Author: Jean-Francois Dockes j...@recoll.org
Last-Update: 2014-12-21
--- a/src/hash.c
+++ b/src/hash.c
@@ -133,8 +133,8 @@ hashitem_new (char *str)
hi-str = my_strdup(str);
- i = *str;
- if (i=='\\') i=str[1];
+ i = (unsigned char)*str;
+ if (i=='\\') i=(unsigned char)str[1];
i = 24;
hi-value = i | (hash_value++ 0xff);
hi-next = NULL;
--- a/src/convert.c
+++ b/src/convert.c
@@ -278,6 +278,8 @@ word_dump_date (Word *w)
CHECK_PARAM_NOT_NULL(w);
while (w) {
char *s = word_string (w);
+if (!s)
+return;
if (*s == '\\') {
++s;
if (!strncmp (s, yr, 2) isdigit(s[2])) {
@@ -524,6 +526,8 @@ process_font_table (Word *w)
if ((w2 = w-child)) {
tmp = word_string(w2);
+if (!tmp)
+break;
if (!strncmp(\\f, tmp, 2)) {
num = atoi(tmp[2]);
name[0] = 0;
@@ -704,7 +708,8 @@ process_info_group (Word *w)
char *s;
s = word_string(child);
-
+if (!s)
+return;
if (!inline_mode) {
if (!strcmp(\\title, s)) {
@@ -712,11 +717,11 @@ process_info_group (Word *w)
w2=child-next;
while (w2) {
char *s2 = word_string(w2);
- if (s2[0] != '\\')
+ if (s2 s2[0] != '\\')
{
print_with_special_exprs (s2);
}
- else
+ else if (s2)
{
if (s2[1] == '\'')
{
@@ -735,7 +740,7 @@ process_info_group (Word *w)
w2=child-next;
while (w2) {
char *s2 = word_string(w2);
- if (s2[0] != '\\')
+ if (s2 s2[0] != '\\')
printf(%s,, s2);
w2 = w2-next;
}
@@ -746,7 +751,7 @@ process_info_group (Word *w)
w2=child-next;
while (w2) {
char *s2 = word_string(w2);
- if (s2[0] != '\\')
+ if (s2 s2[0] != '\\')
printf(%s, s2);
w2 = w2-next;
}
@@ -758,7 +763,7 @@ process_info_group (Word *w)
w2=child-next;
while (w2) {
char *s2 = word_string(w2);
- if (s2[0] != '\\')
+ if (s2 s2[0] != '\\')
printf(%s, s2);
w2 = w2-next;
}
@@ -868,11 +873,10 @@ process_color_table (Word *w)
r=g=b=0;
while(w) {
-if (total_colors = MAX_COLORS) {
+ char *s = word_string (w);
+if (s == 0 || total_colors = MAX_COLORS) {
break;
}
- char *s = word_string (w);
-
if (!strncmp(\\red,s,4)) {
r = atoi(s[4]);
while(r255) r=8;
@@ -1010,6 +1014,8 @@ cmd_field (Word *w, int align, char has_
char *s;
s = word_string(child);
+if (!s)
+return FALSE;
#if 1 /* daved experimenting with fldrslt */
if(!strcmp(\\fldrslt, s))
return FALSE;
@@ -1033,7 +1039,7 @@ cmd_field (Word *w, int align, char has_
Bug#773642: jenkins-job-builder: deleting jobs is completly broken
On Sonntag, 21. Dezember 2014, Holger Levsen wrote: The workaround is easy (rm -r $job_directory), so I've only filed this with severity important, but I do think this should be fixed for jessie. the workaround is actually slightly more complicated: rm -r $job_cfg.xml $job_directory then a jenkins restart still easy, but more annoying and less trivial. And a jenkins restart is super annoying, so I'm even more tempted to raise severity to serious... signature.asc Description: This is a digitally signed message part.
Bug#772811: unrtf: CVE-2014-9274 CVE-2014-9275
On Sun, Dec 21, 2014 at 03:08:00PM +0100, Salvatore Bonaccorso wrote: Hi Willi, On Sun, Dec 14, 2014 at 10:10:58AM +0100, Willi Mann wrote: Hi Dave, does 0.21.7 solve both security issues reported? If yes, could point send me the individual patches that fix these issues? The Debian branch for the next stable distribution is already frozen, so I cannot fix these bugs with new upstream versions. The three required commits are referenced now in Red Hat's Bugzilla entry at [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1170233 Jean-Francois Dockes proposed fixes for both CVEs. CVE-2014-9274 is addressed by https://lists.gnu.org/archive/html/bug-unrtf/2014-12/msg0.html CVE-2014-9275 is addressed by https://lists.gnu.org/archive/html/bug-unrtf/2014-12/msg1.html All three changes were incorporated upstream and shipped as a part of unrtf 0.21.6. (http://hg.savannah.gnu.org/hgweb/unrtf/rev/891c2f431c90) Regards, Salvatore 0.21.8 has just been released with range of fixes. We think all known security issues have been addressed. There is now a mecurial repository with a log file detailing changes. cheers Dave -- David F. Davey D'Entrecasteaux Phone: +61 3 6267 4852 378 Manuka Road Mobile: +61 428 674 852 Kettering Fax: +61 3 6267 4791 Tasmania 7155 Australiada...@windclimber.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773650: Missing copyright licence for nntpid
Package: chiark-utils Version: 4.4.1 Severity: important The chiark-utils package is missing a formal copyright licence for nntpid. I know all the authors personally and they intend distribution, but this permission ought to be properly documented in the VCS history and in the Debian package. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
On Sun, 2014-12-21 at 15:13 +0100, Mario Kothe wrote: I tried it with the initramfs-tools. Still no change. Error messsage is the same: dracut Warning: Could not boot. dracut Warning: /dev/disk/by-uuid/ does not exist Droping to debug shell. And yes it is a dracut bug. Here the install messages from installing initramfs-tools [...] Setting up initramfs-tools (0.115~bpo70+1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: /boot/initrd.img-3.2.0-4-amd64 has been altered. update-initramfs: Cannot update. Override with -t option. root@nova:/etc# reboot Oh, well you need to tell initramfs-tools to rebuild the initramfs too: update-initramfs -u -t -k 3.16.0-0.bpo.4-amd64. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
El 19/12/14 a las 22:03, Tobias Hansen escribió:
On Tue, 02 Dec 2014 21:29:29 +0100
=?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?=
mariodeb...@gmail.com wrote:
El 24/11/14 a las 15:28, Jonathan Wiltshire escribió:
On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo RodrÃguez wrote:
El 23/11/14 a las 19:40, Jonathan Wiltshire escribió:
Control: tags 765129 + pending
Dear maintainer,
I've prepared an NMU for tcos (versioned as 0.89.93+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
Hi, thanks for NMU, I'm not a DD and I have a new package but no sponsor for
upload.
How about preparing a maintainer upload and I'll sponsor it for you?
Hi Jonathan.
I had prepared new TCOS package:
http://mariodebian.com/debian-packages/tcos_0.89.97.dsc
Only sources (not binary)
Can you upload it?
Thanks in advance.
Hi Mario,
the freeze policy allows only targeted fixes for rc bugs. The changes in
0.89.97 are too extensive. I could upload Jonathans NMU patch, unless
there's another small and important fix you want to include. Is the
patch you mentioned on Nov 24 important?
Best,
Tobias
Hi I attach the minimal patch needed to fix this bug and another one
that fix start-stop-daemon start
You can split to use only debian/control diff but the diff of
debian/tcos-standalone.init is needed to fix start-stop-daemon
Thanks in advance
--
Mario Izquierdo Rodríguez
http://mariodebian.com
diff --git a/debian/control b/debian/control
index df22fab..3d61e7d 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Mario Izquierdo (mariodebian) mariodeb...@gmail.com
Build-Depends: debhelper (= 7.0.50~),
python (= 2.6.6-3~),
dh-python,
- libxmlrpc-c3-dev | libxmlrpc-core-c3-dev,
+ libxmlrpc-core-c3-dev | libxmlrpc-c3-dev,
libxau-dev,
libxaw7-dev,
libimlib2-dev,
diff --git a/debian/tcos-standalone.init b/debian/tcos-standalone.init
index ebc2dd5..5abfeda 100644
--- a/debian/tcos-standalone.init
+++ b/debian/tcos-standalone.init
@@ -23,7 +23,7 @@ NAME=tcosxmlrpc-standalone
DAEMON=/usr/lib/tcos/$NAME
DAEMON_WWW=/var/lib/tcos/standalone/www
-PID_FILE=/var/lib/tcos/standalone/log/abyss.pid
+PIDFILE=/var/lib/tcos/standalone/log/abyss.pid
SCRIPTNAME=/etc/init.d/$NAME
DEFAULT_CONF=/etc/default/tcos-standalone
@@ -83,9 +83,9 @@ do_start()
stunnel4 /var/lib/tcos/standalone/etc/stunnel/stunnel.conf /dev/null 21
fi
-
+
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test /dev/null || return 1
-start-stop-daemon --background --start --quiet --pidfile $PIDFILE --exec $DAEMON || return 2
+start-stop-daemon --background --start --quiet --make-pidfile --pidfile $PIDFILE --exec $DAEMON || return 2
}
#
@@ -139,7 +139,7 @@ do_checklog_size()
{
# clean logs when size 5 MB
for logfile in /var/lib/tcos/standalone/log/*; do
-[ $(du $logfile| awk '{print $1}') -gt 5000 ] \
+[ -f $logfile ] [ $(du $logfile| awk '{print $1}') -gt 5000 ] \
cat /dev/null $logfile
done
}
Bug#773649: wheezy-pu: package freecol/0.10.5+dfsg-2
On Sun, Dec 21, 2014 at 3:51 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: [I just spotted that your mail didn't have the bug CCed; was that intentional?] Argh, my mistake. Now Ccing the bug report. On Sun, 2014-12-21 at 15:29 +0100, Vincent Fourmond wrote: No, that was private mail. What he said that made me think I should build it with openjdk-7 was We rebuilt newer OpenJDK releases for stable since the security fixes are almost impossible to extract and backport, but maybe I overinterpreted. Ah. Yeah, I think that's more we backport the new upstream releases because we can't just pull the security fixes out. I shall revert that specific bit, then ;-)... Thanks. It's up to you whether you want to include the S-V bump - nothing in tooling looks at it in stable anyway. OK. Shall I upload the attached debdiff ? BTW, do I need to make a full upload with the orig source to stable ? Regards, Vincent diff -Nru freecol-0.10.5+dfsg/debian/changelog freecol-0.10.5+dfsg/debian/changelog --- freecol-0.10.5+dfsg/debian/changelog2012-03-06 00:10:28.0 +0100 +++ freecol-0.10.5+dfsg/debian/changelog2014-12-21 15:30:36.0 +0100 @@ -1,3 +1,9 @@ +freecol (0.10.5+dfsg-1+deb7u1) stable; urgency=low + + * Disable intro video to avoid hanging at startup (closes: #771700) + + -- Vincent Fourmond fourm...@debian.org Sat, 20 Dec 2014 23:57:15 +0100 + freecol (0.10.5+dfsg-1) unstable; urgency=low * New upstream release diff -Nru freecol-0.10.5+dfsg/debian/wrapper/freecol freecol-0.10.5+dfsg/debian/wrapper/freecol --- freecol-0.10.5+dfsg/debian/wrapper/freecol 2012-01-31 00:42:22.0 +0100 +++ freecol-0.10.5+dfsg/debian/wrapper/freecol 2014-12-20 23:39:11.0 +0100 @@ -24,5 +24,5 @@ disablenet=-Djava.net.preferIPv4Stack=true fi -run_java $disablenet -Xincgc -Xmx512M net.sf.freecol.FreeCol --freecol-data \ +run_java $disablenet -Xincgc -Xmx512M net.sf.freecol.FreeCol --no-intro --freecol-data \ /usr/share/games/freecol $lang_argument $@
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
Am 21.12.2014 um 16:05 schrieb Mario Izquierdo Rodríguez: El 19/12/14 a las 22:03, Tobias Hansen escribió: On Tue, 02 Dec 2014 21:29:29 +0100 =?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?= mariodeb...@gmail.com wrote: El 24/11/14 a las 15:28, Jonathan Wiltshire escribió: On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo RodrÃguez wrote: El 23/11/14 a las 19:40, Jonathan Wiltshire escribió: Control: tags 765129 + pending Dear maintainer, I've prepared an NMU for tcos (versioned as 0.89.93+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. Hi, thanks for NMU, I'm not a DD and I have a new package but no sponsor for upload. How about preparing a maintainer upload and I'll sponsor it for you? Hi Jonathan. I had prepared new TCOS package: http://mariodebian.com/debian-packages/tcos_0.89.97.dsc Only sources (not binary) Can you upload it? Thanks in advance. Hi Mario, the freeze policy allows only targeted fixes for rc bugs. The changes in 0.89.97 are too extensive. I could upload Jonathans NMU patch, unless there's another small and important fix you want to include. Is the patch you mentioned on Nov 24 important? Best, Tobias Hi I attach the minimal patch needed to fix this bug and another one that fix start-stop-daemon start You can split to use only debian/control diff but the diff of debian/tcos-standalone.init is needed to fix start-stop-daemon Thanks in advance Hi, could you please prepare a maintainer upload (create a .dsc) where these patches are applied? Please mention both changes in the changelog. Then I upload it. Best, Tobias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773548: unblock: bind9/1:9.9.5.dfsg-7
Hi, Cyril Brulebois wrote: Non-linux porters may want to double check this new version isn't going to lead to regressions on their architecture(s) though, so letting them know through Cc (patch available below). Thanks for checking with us. Seems like only DNS resolver code was changed, I don't think d-i uses any part of that, and needs only unrelated library functions for ISC dhcpd. Still, with the updated libs d-i still completed successfully (a netboot install involving DNS resolution and using DHCP). This test-run was more than 24 hours after 1:9.9.5.dfsg-7 built on kfreebsd-amd64 so would have been using the new udebs. https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/447/ Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773651: nntpid not shipped
Package: chiark-scripts Version: 4.4.2 The script nntpid should be shipped in /usr/bin, and its perl module in the appropriate place. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
El 21/12/14 a las 16:17, Tobias Hansen escribió:
Am 21.12.2014 um 16:05 schrieb Mario Izquierdo Rodríguez:
El 19/12/14 a las 22:03, Tobias Hansen escribió:
On Tue, 02 Dec 2014 21:29:29 +0100
=?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?=
mariodeb...@gmail.com wrote:
El 24/11/14 a las 15:28, Jonathan Wiltshire escribió:
On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo RodrÃguez
wrote:
El 23/11/14 a las 19:40, Jonathan Wiltshire escribió:
Control: tags 765129 + pending
Dear maintainer,
I've prepared an NMU for tcos (versioned as 0.89.93+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
Hi, thanks for NMU, I'm not a DD and I have a new package but no
sponsor for
upload.
How about preparing a maintainer upload and I'll sponsor it for you?
Hi Jonathan.
I had prepared new TCOS package:
http://mariodebian.com/debian-packages/tcos_0.89.97.dsc
Only sources (not binary)
Can you upload it?
Thanks in advance.
Hi Mario,
the freeze policy allows only targeted fixes for rc bugs. The changes in
0.89.97 are too extensive. I could upload Jonathans NMU patch, unless
there's another small and important fix you want to include. Is the
patch you mentioned on Nov 24 important?
Best,
Tobias
Hi I attach the minimal patch needed to fix this bug and another one
that fix start-stop-daemon start
You can split to use only debian/control diff but the diff of
debian/tcos-standalone.init is needed to fix start-stop-daemon
Thanks in advance
Hi,
could you please prepare a maintainer upload (create a .dsc) where these
patches are applied? Please mention both changes in the changelog. Then
I upload it.
Best,
Tobias
Here is it:
http://mariodebian.com/debian-packages/tcos_0.89.96+1.dsc
Diff from 0.89.96 (current Debian unstable version) attached.
Thanks
--
Mario Izquierdo Rodríguez
http://mariodebian.com
diff --git a/debian/changelog b/debian/changelog
index fe30f0c..f5f6ba1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+tcos (0.89.96+1) unstable; urgency=medium
+
+ * Fix build dependencies libxmlrpc-core-c3-dev (closes: #765129)
+ * Fix tcos-standalone start-stop-daemon command
+
+ -- Mario Izquierdo (mariodebian) mariodeb...@gmail.com Sun, 21 Dec 2014 16:23:51 +0100
+
tcos (0.89.96) unstable; urgency=medium
* Start tcosxmlrpc with start-stop-daemon
diff --git a/debian/control b/debian/control
index df22fab..3d61e7d 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Mario Izquierdo (mariodebian) mariodeb...@gmail.com
Build-Depends: debhelper (= 7.0.50~),
python (= 2.6.6-3~),
dh-python,
- libxmlrpc-c3-dev | libxmlrpc-core-c3-dev,
+ libxmlrpc-core-c3-dev | libxmlrpc-c3-dev,
libxau-dev,
libxaw7-dev,
libimlib2-dev,
diff --git a/debian/tcos-standalone.init b/debian/tcos-standalone.init
index ebc2dd5..aeb1abc 100644
--- a/debian/tcos-standalone.init
+++ b/debian/tcos-standalone.init
@@ -23,7 +23,7 @@ NAME=tcosxmlrpc-standalone
DAEMON=/usr/lib/tcos/$NAME
DAEMON_WWW=/var/lib/tcos/standalone/www
-PID_FILE=/var/lib/tcos/standalone/log/abyss.pid
+PIDFILE=/var/lib/tcos/standalone/log/abyss.pid
SCRIPTNAME=/etc/init.d/$NAME
DEFAULT_CONF=/etc/default/tcos-standalone
@@ -83,9 +83,9 @@ do_start()
stunnel4 /var/lib/tcos/standalone/etc/stunnel/stunnel.conf /dev/null 21
fi
-
+
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test /dev/null || return 1
-start-stop-daemon --background --start --quiet --pidfile $PIDFILE --exec $DAEMON || return 2
+start-stop-daemon --background --start --quiet --make-pidfile --pidfile $PIDFILE --exec $DAEMON || return 2
}
#
@@ -139,7 +139,7 @@ do_checklog_size()
{
# clean logs when size 5 MB
for logfile in /var/lib/tcos/standalone/log/*; do
-[ $(du $logfile| awk '{print $1}') -gt 5000 ] \
+[ -f $logfile ] [ $(du $logfile| awk '{print $1}') -gt 5000 ] \
cat /dev/null $logfile
done
}
Bug#773653: unblock: slim/1.3.6-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Please unblock package slim.
I made package update for jessie release. New theme Debian-Lines is
included, also bugs for machines with systemd was fixed.
diff -Nru slim-1.3.6/debian/changelog slim-1.3.6/debian/changelog
--- slim-1.3.6/debian/changelog 2014-04-29 13:18:36.0 +0200
+++ slim-1.3.6/debian/changelog 2014-12-21 13:50:09.0 +0100
@@ -1,3 +1,29 @@
+slim (1.3.6-4) unstable; urgency=medium
+
+ * Drop consolekit depends. Thanks Elimar Riesebieter riese...@lxtec.de
+for the patch. (Closes: #751618)
+ * Bump Standards-Version to 3.9.6. (no changes needed)
+ * Update homepage.
+ * Update debian/watch to new homepage.
+ * Add new themes Lines for Debian 8:
+- Update debian/copyright.
+- Refresh debian/patches/slim-conf.patch
+- Update debian/slim.install, debian/rules and
+ debian/source/include-binaries for new files.
+- Fix select session. (Closes: #756519)
+ * Making lintian clear package:
+- Add fix-hyphen-used-as-minus-sign.patch for like the name call.
+- Update debian/copyright.
+- Add lintian-overrides for info tags which can be ignored.
+ * Rewrite debian/patches/fix-systemd-service.patch, debian/slim.posinst:
+- ensure we are starting slim under systemd only when selected as
+ default. Thanks Didier Roche didro...@ubuntu.com for suggests
patch.
+ (Closes: #748668)
+ * Add lintian-overrides for check-gpg-signature it is not provides by
+upstream yet.
+
+ -- Mateusz Łukasik mat...@linuxmint.pl Sun, 21 Dec 2014 13:46:02 +0100
+
slim (1.3.6-3) unstable; urgency=high
* debian/patches:
diff -Nru slim-1.3.6/debian/control slim-1.3.6/debian/control
--- slim-1.3.6/debian/control 2014-04-25 15:16:46.0 +0200
+++ slim-1.3.6/debian/control 2014-12-19 20:15:02.0 +0100
@@ -5,17 +5,17 @@
Uploaders: Jens Peter Secher j...@debian.org, Mateusz Łukasik
mat...@linuxmint.pl
Build-Depends: debconf, debhelper (= 9), libjpeg-dev, libpam0g-dev,
libpng-dev, libxft-dev, libxmu-dev, po-debconf, sharutils,
- libck-connector-dev, zlib1g-dev, cmake, freeglut3-dev,
- libpthread-stubs0-dev, libxrandr-dev, dh-systemd
-Standards-Version: 3.9.5
-Homepage: http://slim.berlios.de/
+ zlib1g-dev, cmake, freeglut3-dev, libpthread-stubs0-dev, libxrandr-dev,
+dh-systemd
+Standards-Version: 3.9.6
+Homepage: http://sourceforge.net/projects/slim.berlios/
Package: slim
Architecture: any
Provides: x-display-manager
Recommends: xterm
Suggests: scrot, xauth
-Depends: ${shlibs:Depends}, ${misc:Depends}, debconf (= 1.2.9) |
debconf-2.0, dbus, consolekit
+Depends: ${shlibs:Depends}, ${misc:Depends}, debconf (= 1.2.9) |
debconf-2.0, dbus
Description: desktop-independent graphical login manager for X11
SLiM aims to be light, simple and independent from the various
desktop environments. Although completely configurable through
diff -Nru slim-1.3.6/debian/copyright slim-1.3.6/debian/copyright
--- slim-1.3.6/debian/copyright 2014-02-15 15:46:18.0 +0100
+++ slim-1.3.6/debian/copyright 2014-12-20 15:45:55.0 +0100
@@ -13,39 +13,40 @@
Copyright: 2011, David Hauweele
License: GPL-2+
-Files: Ck.h; PAM.*
+Files: Ck.h PAM.*
Copyright: 2007, Martin Parm
License: GPL-2+
Files: image.*
-Copyright: 2002-2004 Hari Nair h...@alumni.caltech.edu
+Copyright: 2002-2004, Hari Nair h...@alumni.caltech.edu
License: GPL-2+
-Files: jpeg.c; png.c
-Copyright: 2002 Hari Nair h...@alumni.caltech.edu
+Files: jpeg.c
+ png.c
+Copyright: 2002, Hari Nair h...@alumni.caltech.edu
License: GPL-2+
Files: slimlock.cpp
-Copyright: 2010-2012 Joel Burget joelbur...@gmail.com
+Copyright: 2010-2012, Joel Burget joelbur...@gmail.com
License: GPL-2+
Files: util.*
-Copyright: 2009 Eygene Ryabinkin r...@codelabs.ru
+Copyright: 2009, Eygene Ryabinkin r...@codelabs.ru
License: GPL-2+
Files: themes/default/panel.png
-Copyright: 2004 Lila Community
+Copyright: 2004, Lila Community
License: GPL-2+
-Files: themes/default/background.png
-Copyright: 2005 rafael nascimento
+Files: themes/default/background.jpg
+Copyright: 2005, rafael nascimento
License: permissive
This file may be copied and used freely without restrictions. It may
be used in projects which are not available under a GNU General
Public License.
Files: cmake/*
Copyright: 2006, Alexander Neundorf, neund...@kde.org
- 2008, Kevin Kofler, kevin.kof...@chello.at
+ 2008, Kevin Kofler, kevin.kof...@chello.at
License: BSD-3-clause
These scripts are placed under the BSD license:
Copyright (c) The Regents of the University of California.
@@ -81,19 +82,26 @@
2014, Mateusz Łukasik mat...@linuxmint.pl
License: GPL-2+
-Files:
debian/debian-joy/*;debian/debian-moreblue-orbit/*;debian/debian-spacefun/*;
-Copyright: 2007-2008 Mike Massonnet mmasson...@gmail.com
- 2008
Bug#773652: unblock: chiark-utils/4.4.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi. Please unblock package chiark-utils. Alternatively, please decide that #773650 is not RC. #773650 is: The chiark-utils package is missing a formal copyright licence for nntpid. I know all the authors personally and they intend distribution, but this permission ought to be properly documented in the VCS history and in the Debian package. Note that the offending script `nntpid' is (due to another bug) not currently actually shipped in any .deb. But it is in the source package. The debdiff is below. The changes are: - Add a copyright message to nntpid and the perl module it uses, and a corresponding stanza to debian/copyright (#773650). - Update the copyright year for git-cache-proxy and mention that in debian/copyright. To check that the rebuild has had no deleterious effect, I have debdiffed the .debs, and they all say: File lists identical (after any substitutions) No differences were encountered between the control files Thanks, Ian. unblock chiark-utils/4.4.2 diff -Nru chiark-utils-4.4.1/debian/changelog chiark-utils-4.4.2/debian/changelog --- chiark-utils-4.4.1/debian/changelog 2014-10-27 00:14:34.0 + +++ chiark-utils-4.4.2/debian/changelog 2014-12-21 15:14:10.0 + @@ -1,3 +1,12 @@ +chiark-utils (4.4.2) unstable; urgency=low + + Copyright licencing fixes: + * nntpid: Provice actual licence (dual MIT/GPL3+). Closes:#773650. + * git-cache-proxy: Mention in debian/copyright. + * git-cache-proxy: Update copyright year list to include 2014. + + -- Ian Jackson ijack...@chiark.greenend.org.uk Sun, 21 Dec 2014 15:07:20 + + chiark-utils (4.4.1) unstable; urgency=low Safety and convenience fix: diff -Nru chiark-utils-4.4.1/debian/copyright chiark-utils-4.4.2/debian/copyright --- chiark-utils-4.4.1/debian/copyright 2014-10-26 14:20:47.0 + +++ chiark-utils-4.4.2/debian/copyright 2014-12-21 15:12:51.0 + @@ -69,6 +69,17 @@ Miscellaneous utilities. Copyright 2004,2006 Ian Jackson i...@chiark.greenend.org.uk +nntpid + Utility for finding usenet articles by messageid from an NNTP server + Copyright -2011 Simon Tatham + Copyright 2011 Richard Kettlewell + Copyright 2011 Colin Watson + Copyright 2011 Ian Jackson + Dual licence MIT/GPL3+ + +git-cache-proxy + Copyright 2010 Tony Finch + Copyright 2013,2014 Ian Jackson The chiark utilities are all free software; you can redistribute them and/or modify them under the terms of the GNU General Public License diff -Nru chiark-utils-4.4.1/scripts/ChiarkNNTP.pm chiark-utils-4.4.2/scripts/ChiarkNNTP.pm --- chiark-utils-4.4.1/scripts/ChiarkNNTP.pm2014-10-26 14:14:18.0 + +++ chiark-utils-4.4.2/scripts/ChiarkNNTP.pm2014-12-21 15:11:09.0 + @@ -1,5 +1,31 @@ #!/usr/bin/perl +# Originally by Simon Tatham +# Modified by Richard Kettlewell, Colin Watson, Ian Jackson +# +# Copyright -2011 Simon Tatham +# Copyright 2011 Richard Kettlewell +# Copyright 2011 Colin Watson +# Copyright 2011 Ian Jackson +# +# Permission is hereby granted, free of charge, to any person obtaining a +# copy of this software and associated documentation files (the Software), +# to deal in the Software without restriction, including without limitation +# the rights to use, copy, modify, merge, publish, distribute, sublicense, +# and/or sell copies of the Software, and to permit persons to whom the +# Software is furnished to do so, subject to the following conditions: +# +# The above copyright notice and this permission notice shall be included in +# all copies or substantial portions of the Software. +# +# THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +# SOFTWARE IN THE PUBLIC INTEREST, INC. BE LIABLE FOR ANY CLAIM, DAMAGES OR +# OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +# ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER +# DEALINGS IN THE SOFTWARE. + use strict qw(subs); use warnings; diff -Nru chiark-utils-4.4.1/scripts/git-cache-proxy chiark-utils-4.4.2/scripts/git-cache-proxy --- chiark-utils-4.4.1/scripts/git-cache-proxy 2014-10-26 14:14:18.0 + +++ chiark-utils-4.4.2/scripts/git-cache-proxy 2014-12-21 15:12:46.0 + @@ -29,7 +29,7 @@ # git-cache-proxy # Copyright 2010 Tony Finch -# Copyright 2013 Ian Jackson +# Copyright 2013,2014 Ian Jackson # # git-cache-proxy is free software; you can redistribute it and/or # modify them under the terms of the GNU General Public License as diff -Nru chiark-utils-4.4.1/scripts/nntpid chiark-utils-4.4.2/scripts/nntpid --- chiark-utils-4.4.1/scripts/nntpid 2014-10-26 14:14:18.0 + +++ chiark-utils-4.4.2/scripts/nntpid 2014-12-21
Bug#753741: tcos-core: please depend on iproute2 instead of iproute transitional package
Version: 0.89.94 thanks Bug is fixed in 0.89.94 https://github.com/mariodebian/tcos/commit/b04fb2cc5db19f22f86fd6bcbc5c6b21e33b38d0 El 04/07/14 a las 17:01, Andreas Henriksson escribió: Package: tcos-core Version: 0.89.93 Severity: normal Usertags: iproute-removal Dear Maintainer, The iproute package is now a transitional package to iproute2. It will soon be removed. Please update your dependency to iproute2 (or alternatively iproute2 | iproute if you're concerned with backports). -- 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.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Mario Izquierdo Rodríguez http://mariodebian.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773654: mediawiki: Security issue: thumb.php outputs wikitext message as raw HTML
Package: mediawiki Version: 1:1.19.20+dfsg-2.1 Severity: important Tags: upstream patch From upstream bug T76686 (still not public): thumb.php outputs wikitext message as raw HTML, which could lead to xss. Permission to edit MediaWiki namespace is required to exploit this. The upstream patch fixing this is at https://github.com/wikimedia/mediawiki/commit/fdd3f464ef9aa7f3276a2a8dddc85e3769cfda83, and I have uploaded 1:1.19.20+dfsg-2.2 to DELAYED/2, that includes it. The corresponding debdiff is included at the end of this email. Cheers, --Seb -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (501, 'stable'), (500, 'oldstable-proposed-updates'), (500, 'oldstable'), (1, 'unstable'), (1, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
Am 21.12.2014 um 16:31 schrieb Mario Izquierdo Rodríguez: El 21/12/14 a las 16:17, Tobias Hansen escribió: Am 21.12.2014 um 16:05 schrieb Mario Izquierdo Rodríguez: El 19/12/14 a las 22:03, Tobias Hansen escribió: On Tue, 02 Dec 2014 21:29:29 +0100 =?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?= mariodeb...@gmail.com wrote: El 24/11/14 a las 15:28, Jonathan Wiltshire escribió: On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo RodrÃguez wrote: El 23/11/14 a las 19:40, Jonathan Wiltshire escribió: Control: tags 765129 + pending Dear maintainer, I've prepared an NMU for tcos (versioned as 0.89.93+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. Hi, thanks for NMU, I'm not a DD and I have a new package but no sponsor for upload. How about preparing a maintainer upload and I'll sponsor it for you? Hi Jonathan. I had prepared new TCOS package: http://mariodebian.com/debian-packages/tcos_0.89.97.dsc Only sources (not binary) Can you upload it? Thanks in advance. Hi Mario, the freeze policy allows only targeted fixes for rc bugs. The changes in 0.89.97 are too extensive. I could upload Jonathans NMU patch, unless there's another small and important fix you want to include. Is the patch you mentioned on Nov 24 important? Best, Tobias Hi I attach the minimal patch needed to fix this bug and another one that fix start-stop-daemon start You can split to use only debian/control diff but the diff of debian/tcos-standalone.init is needed to fix start-stop-daemon Thanks in advance Hi, could you please prepare a maintainer upload (create a .dsc) where these patches are applied? Please mention both changes in the changelog. Then I upload it. Best, Tobias Here is it: http://mariodebian.com/debian-packages/tcos_0.89.96+1.dsc Diff from 0.89.96 (current Debian unstable version) attached. Thanks Hi, I just realized that there are already different versions in testing and unstable. That means we have to upload a targeted fix for the bug for the package version that is in testing (0.89.93) to testing-proposed-updates. Is the start-stop-daemon bug relevant for that version? Also, we can really just fix RC bugs this late in the freeze (freeze policy was tightened on Dec 5), so if the second bug is also RC you have to open a bug for it and close it in the changelog. If the second bug is not in version 0.89.93 or not RC, I'll just upload Jonathans debdiff to t-p-u ok? Best, Tobias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773654: Debdiff
diff -Nru mediawiki-1.19.20+dfsg/debian/changelog
mediawiki-1.19.20+dfsg/debian/changelog
--- mediawiki-1.19.20+dfsg/debian/changelog 2014-12-14 18:27:31.0
+0100
+++ mediawiki-1.19.20+dfsg/debian/changelog 2014-12-21 13:11:10.0
+0100
@@ -1,3 +1,12 @@
+mediawiki (1:1.19.20+dfsg-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch fixing T76686: thumb.php outputs wikitext message as raw
+HTML, which could lead to xss. Permission to edit MediaWiki namespace
+is required to exploit this.
+
+ -- Sebastien Delafond s...@debian.org Sun, 21 Dec 2014 13:11:10 +0100
+
mediawiki (1:1.19.20+dfsg-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/series
mediawiki-1.19.20+dfsg/debian/patches/series
--- mediawiki-1.19.20+dfsg/debian/patches/series2014-12-14
18:22:55.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/series2014-12-21
13:10:23.0 +0100
@@ -11,3 +11,4 @@
suppress_warnings.patch
CVE-2014-9277_1.patch
CVE-2014-9277_2.patch
+T76686.patch
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/T76686.patch
mediawiki-1.19.20+dfsg/debian/patches/T76686.patch
--- mediawiki-1.19.20+dfsg/debian/patches/T76686.patch 1970-01-01
01:00:00.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/T76686.patch 2014-12-21
13:10:21.0 +0100
@@ -0,0 +1,55 @@
+From fdd3f464ef9aa7f3276a2a8dddc85e3769cfda83 Mon Sep 17 00:00:00 2001
+From: Kunal Mehta lego...@gmail.com
+Date: Thu, 4 Dec 2014 14:06:55 -0800
+Subject: [PATCH] thumb.php: Set proper output formats for messages going into
+ HTML
+
+* Use -parse() instead of -text() for wikitext messages that were
+ being treated as HTML
+* Explicitly specify -parse() if no output format was set
+* Document that wfThumbError() takes HTML
+
+Bug: T76686
+Change-Id: Id6e7548b2e081cfda7803772ed0395a15feb1f84
+---
+ thumb.php | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/thumb.php b/thumb.php
+index 60a7ffb..a7a09fc 100644
+--- a/thumb.php
b/thumb.php
+@@ -107,13 +107,13 @@ function wfStreamThumb( array $params ) {
+ // Format is timestamp!name
+ $bits = explode( '!', $fileName, 2 );
+ if ( count( $bits ) != 2 ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse()
);
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+ $title = Title::makeTitleSafe( NS_FILE, $bits[1] );
+ if ( !$title ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse()
);
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+@@ -136,7 +136,7 @@ function wfStreamThumb( array $params ) {
+
+ // Check the source file storage path
+ if ( !$img ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse() );
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+@@ -291,7 +291,7 @@ function wfExtractThumbParams( $uri ) {
+ * Output a thumbnail generation error message
+ *
+ * @param $status integer
+- * @param $msg string
++ * @param string $msg HTML
+ * @return void
+ */
+ function wfThumbError( $status, $msg ) {
Bug#767468: autofs: mounts may fail with 'Too many levels of symbolic links' when using cgmanager
[John Paul Adrian Glaubitz] Hello Petter! Hi. assuming - since you are one of the maintainers of the sysvinit package - you are preferring sysvinit over systemd, This is an incorrect assumtion. I do not prefer sysvinit over systemd. In fact, I do not really care much. :) Also, Debian Edu do not adjust the default boot system in Jessie, and whatever is installed is installed by the default depends/recommends settings. So if autofs fail in Debian Edu, I expect it will fail also outside Debian Edu using the default setup in Debian Jessie. -- 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#765129: tcos: diff for NMU version 0.89.93+nmu1
Hi, I just realized that there are already different versions in testing and unstable. That means we have to upload a targeted fix for the bug for the package version that is in testing (0.89.93) to testing-proposed-updates. Is the start-stop-daemon bug relevant for that version? Also, we can really just fix RC bugs this late in the freeze (freeze policy was tightened on Dec 5), so if the second bug is also RC you have to open a bug for it and close it in the changelog. If the second bug is not in version 0.89.93 or not RC, I'll just upload Jonathans debdiff to t-p-u ok? Best, Tobias The transition to libxmlrpc-core-c3-dev breaks some binaries and 0.89.93 + debian/control diff don't fix the real problem. I think it's better to remove from testing, and 0.89.97 will be too dificult to upload to testing-proposed-updates because of freeze. What's your opinion? Thanks for your help -- Mario Izquierdo Rodríguez http://mariodebian.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741195: Sorry, my fault with outdated configs.
Sorry, my fault with outdated configs. See https://www.midnight-commander.org/ticket/2772#comment:3 I build ~/.config/mc/mc.ext as: $ cat $skelproj/.config/mc/mc.ext /etc/mc/mc.ext ~/.config/mc/mc.ext and seems that /etc/mc/mc.ext part outdated after MC updates. -- Best regards! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767468: autofs: mounts may fail with 'Too many levels of symbolic links' when using cgmanager
On 12/21/2014 05:02 PM, Petter Reinholdtsen wrote: This is an incorrect assumtion. I do not prefer sysvinit over systemd. In fact, I do not really care much. :) Alright, good to know. Also, Debian Edu do not adjust the default boot system in Jessie, and whatever is installed is installed by the default depends/recommends settings. So if autofs fail in Debian Edu, I expect it will fail also outside Debian Edu using the default setup in Debian Jessie. Ok, I thought Debian Edu was special in that regard. Then I honestly to expect any problems with autofs to arise in Debian Edu. According to my observations at our department - being a heavy autofs user - the problem does only occur when not using the default installation which involves not using systemd and an alternative init system plus cgmanager. Then we'll leave it to the maintainers and users of alternative init systems to take care of this particular problem. Moreover, they should take care of fixing the bug in cgmanager. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754459: ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
Hi, I have a similar problem trying to play youtube files. I'm not behind a proxy or anything and a browser can play the same youtube file just fine. It also doesn't appear for every youtube file. Here is an example: I'm having the same problem with the current version in jessie (2:13.2+dfsg1-4): The Youtube plugin does not work, and I get HTTP errors. Same on my Raspberry Pi. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: diff for NMU version 0.89.93+nmu1
Am 21.12.2014 um 17:09 schrieb Mario Izquierdo Rodríguez: Hi, I just realized that there are already different versions in testing and unstable. That means we have to upload a targeted fix for the bug for the package version that is in testing (0.89.93) to testing-proposed-updates. Is the start-stop-daemon bug relevant for that version? Also, we can really just fix RC bugs this late in the freeze (freeze policy was tightened on Dec 5), so if the second bug is also RC you have to open a bug for it and close it in the changelog. If the second bug is not in version 0.89.93 or not RC, I'll just upload Jonathans debdiff to t-p-u ok? Best, Tobias The transition to libxmlrpc-core-c3-dev breaks some binaries and 0.89.93 + debian/control diff don't fix the real problem. I think it's better to remove from testing, and 0.89.97 will be too dificult to upload to testing-proposed-updates because of freeze. What's your opinion? Thanks for your help So you mean 0.89.93 in testing has a third RC bug right now? It could also be possible to upload a 0.89.93+tpu1 with fixes for 3 RC bugs to testing-proposed-updates. If you want to know for sure, file the RC bugs, prepare the patches and get them pre-approved by the release team on the debian-release list. Or just explain them the problem without preparing everything and ask them what they think. Best, Tobias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773656: ITP: daps -- DocBook Authoring and Publishing Suite
Package: daps Severity: wishlist URL: http://daps.sourceforge.net/ SVN: http://sourceforge.net/p/daps/svn/HEAD/tree/ The DocBook Authoring and Publishing Suite (DAPS) fills this gap by providing a tool set for easy creation and publication of DocBook sources on Linux. DAPS lets you create HTML (incl. webhelp), PDF, EPUB, man pages, and other formats with a single command. It automatically takes care of validating and filtering (profiling) your sources and automatically converts images into a format best suited for the output format. Furthermore one can easily create profiled source tarballs for translation or review. DAPS supports authors by providing linkchecker, validator, spellchecker, and editor macros. It is perfectly suited to manage large documentation projects with multiple authors using the DAPS docmanager. -- Yours sincerly Sascha Manns Maifeldstraße 10 56727 Mayen Phone: +49-1573-9242730 Email: sascha.ma...@bdvb.de Web: http://saigkill.ddns.net/wordpress -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773501: debdiff for gosa wheezy-pu
Control: tags -1 + pending On Fri, 2014-12-19 at 09:21 +, Mike Gabriel wrote: On Fr 19 Dez 2014 10:18:54 CET, Adam D. Barratt wrote: Ack. Sorry about that. I thought for fixing a grave RC bug it would be ok. Next time, I'll seek for pre-approval. No worries. In this case it looks fine from a quick glance (I'll look properly when I next do a p-u catchup), it's just that if there are any issues then we end up having to reject the package and round-trip back to the submitter and it's generally easier for both parties if we agree on the diff first. OK. Thanks! I get that. Flagged for acceptance. 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#773649: wheezy-pu: package freecol/0.10.5+dfsg-2
Control: tags -1 + pending [I also managed to drop the bug CC; re-added] On Sun, 2014-12-21 at 16:35 +0100, Vincent Fourmond wrote: On Sun, Dec 21, 2014 at 4:14 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 +confirmed -moreinfo On Sun, 2014-12-21 at 16:11 +0100, Vincent Fourmond wrote: OK. Shall I upload the attached debdiff ? That looks fine; thanks. BTW, do I need to make a full upload with the orig source to stable ? No, it's just a normal upload to ftp-master (other than the target suite). On its way. Flagged for acceptance, 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#773657: Obey bootstrap selection
Package: live-build
Version: 4.0.4-1
Tags: patch
Attached is a patch (built against 4.x - assuming this is important
enough to get into jessie) which improves the processing of bootstrap
program selection.
Current logic takes my bootstrap selection and checks to see the program
is installed; if not, it completely disregards my choice and goes with
whatever program is actually installed on my system. I don't consider
this behaviour to be acceptable.
The patch:
- Improves the logic so that if the user explicitly specifies a
particular bootloader to use, and it's not installed, an error is issued
to prompt the user to get it installed before trying again. It validates
the user's choice, and only resorts to looking for an installed program
if the user/config hasn't specified one.
- Switches the newer cdebootstrap program round to be the preferred
choice, but only for when no specific choice has been made, and if
multiple bootstrap programs are installed.
- Gets rid of an obsolete reference in the logic to an old 'copy'
bootstrap parameter choice.
commit 30d5774b753c25f4f42817e0b5c7547f7a4eb9ad
Author: jnqnfe jnq...@gmail.com
Date: Sun Dec 21 16:39:16 2014 +
Properly obey bootstrap selection, update preferential default to
cdebootstrap, and clear out remaining reference to old copy option.
diff --git a/functions/defaults.sh b/functions/defaults.sh
index c74d1c1..d341417 100755
--- a/functions/defaults.sh
+++ b/functions/defaults.sh
@@ -221,14 +221,20 @@ Set_defaults ()
esac
# Setting bootstrap program
- if [ -z ${LB_BOOTSTRAP} ] || ( [ ! -x $(which ${LB_BOOTSTRAP}
2/dev/null) ] [ ${LB_BOOTSTRAP} != copy ] )
+ if [ -z ${LB_BOOTSTRAP} ]
then
- if [ -x /usr/sbin/debootstrap ]
- then
- LB_BOOTSTRAP=debootstrap
- elif [ -x /usr/bin/cdebootstrap ]
+ if [ -x /usr/bin/cdebootstrap ]
then
LB_BOOTSTRAP=cdebootstrap
+ elif [ -x /usr/bin/cdebootstrap-static ]
+ then
+ LB_BOOTSTRAP=cdebootstrap-static
+ elif [ -x /usr/sbin/debootstrap ]
+ then
+ LB_BOOTSTRAP=debootstrap
+ else
+ Echo_error No bootstrap program specified or otherwise
found, please install one and try again!
+ exit 1
fi
fi
@@ -1053,6 +1059,20 @@ Check_defaults ()
fi
fi
+ case ${LB_BOOTSTRAP} in
+ cdebootstrap|cdebootstrap-static|debootstrap)
+ ;;
+ *)
+ Echo_error Bootstrap program selection '%s' is invalid
or unsupported! ${LB_BOOTSTRAP}
+ exit 1
+ ;;
+ esac
+ if [ ! -x $(which ${LB_BOOTSTRAP} 2/dev/null) ]
+ then
+ Echo_error Command %s not found. Please check that the
relevant bootstrap program is installed and try again! ${LB_BOOTSTRAP}
+ exit 1
+ fi
+
case ${LB_BINARY_FILESYSTEM} in
ntfs)
if [ ! -x $(which ntfs-3g 2/dev/null) ]
diff --git a/manpages/en/lb_config.1 b/manpages/en/lb_config.1
index b612f87..685cec6 100644
--- a/manpages/en/lb_config.1
+++ b/manpages/en/lb_config.1
@@ -268,7 +268,7 @@ sets boot parameters specific to debian\-live. A complete
list of boot parameter
.IP \fB\-\-bootloader\fR grub|grub2|syslinux 4
defines which bootloader is being used in the generated image. This has only
an effect if the selected binary image type does allow to choose the
bootloader. For example, if you build a iso, always syslinux (or more precise,
isolinux) is being used. Also note that some combinations of binary images
types and bootloaders may be possible but live\-build does not support them
yet. \fBlb config\fR will fail to create such a not yet supported configuration
and give a explanation about it. For hdd images on amd64 and i386, the default
is syslinux.
.IP \fB\-\-bootstrap\fR cdebootstrap|cdebootstrap-static|debootstrap 4
-defines which program is used to bootstrap the debian chroot, default is
debootstrap.
+defines which program is used to build a base debian filesystem, which
provides the foundations for the live OS filesystem, and also a chroot
environment for the build process. If a selection is not explicitly made via
this parameter, an attempt will be made to find and default to one already
installed on your system, in the order of preference cdebootstrap, then
cdebootstrap, then finally debootstrap.
.IP \fB\-\-cache\fR true|false 4
defines globally if any cache should be used at all. Different caches can be
controlled through the their own options.
.IP \fB\-\-cache\-indices\fR true|false 4
diff --git a/scripts/build/bootstrap_cdebootstrap
b/scripts/build/bootstrap_cdebootstrap
index 490352b..55bbdf3 100755
---
Bug#773658: please reformat README.Debian to have normal text width
Package: mono-xsp4 Version: 3.8-2 Severity: wishlist Hello, contrary to some modern beliefs, the README.Debian files are still contain plain text which people would like to read on the console, especially on servers when the package is made for servers, like mono-xsp. Unfortunatelly the file in your package is hard to read. Example: If you want to install a new virtualhost to XSP 4, you just need to apt-get it, and if XSP 4 is running it should be started normally, if it's the first virtualhost and you configured mono-xsp4 to be started automatically it will start xsp4 by default. or: NOTE: In some cases you can find that /etc/mono-server|/etc/xsp4 exists with oth er virtualhosts and you don't have mono-server|mono-xsp4 installed, don't get in panic, some virtualhost s installs host configuration files in both server (xsp4 and mono-server). Please make sure that line length is less than 80 chars. Regards, Eduard. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0+ (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/bash Init: sysvinit (via /sbin/init) Versions of packages mono-xsp4 depends on: ii debconf [debconf-2.0]1.5.54 ii libmono-corlib4.0-cil3.2.8+dfsg-8 ii libmono-security4.0-cil 3.2.8+dfsg-8 ii libmono-system-configuration4.0-cil 3.2.8+dfsg-8 ii libmono-system-data4.0-cil 3.2.8+dfsg-8 ii libmono-system4.0-cil3.2.8+dfsg-8 ii mono-runtime 3.2.8+dfsg-8 pn mono-xsp4-base none ii procps 2:3.3.9-8 mono-xsp4 recommends no packages. mono-xsp4 suggests no packages. -- Was sagt ein Hund, kurz bevor ein Auto ihn trifft? Hilf... Was sagt ein Hirsch, kurz bevor ein Auto ihn trifft? Hilf... Was sagt ein Elefant, kurz bevor ein Auto ihn trifft? Komm nur! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773659: cabextract: null pointer dereference on a crafted CAB
Package: cabextract Version: 1.4-4+b1 Usertags: afl cabextract crashes (trying to dereference null pointed) on the attached crafted CAB file: $ gpg -d nullderef.cab.asc nullderef.cab $ cabextract -t nullderef.cab nullderef.cab: WARNING; possible 1626 extra bytes at end of file. Testing cabinet: nullderef.cab failed (error in CAB data format) failed (Success) E failed (error in CAB data format) Segmentation fault Backtrace: #0 0x in ?? () #1 0x0804e094 in cabd_extract (base=0x805b008, file=0x8063600, filename=0x8056643 test) at mspack/cabd.c:1068 #2 0x080493b4 in process_cabinet (basename=0xd9b8 nullderef.cab) at src/cabextract.c:467 #3 0x08048fc4 in main (argc=3, argv=0xd804) at src/cabextract.c:350 This bug was found using American fuzzy lop: https://packages.debian.org/experimental/afl -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages cabextract depends on: ii libc6 2.19-13 -- Jakub Wilk -BEGIN PGP MESSAGE- Version: GnuPG v1 owFby+6ZxJtXmpOTklqUmqaXnJgUMp1J0TfY2Y0BCO4wQIAOlGZmZGRghLJdgRjE 288AAz2uGDoaGLDqcFu0z4J9W9J85enNT+8X55W7G68/MPWihaPE0yn6Rpx2W1Ns XioUvg+YMjHpmdTftQL/Cl31028tmPck9w23R/m9C4cduK8s+/BMrueUe1dJzLSy 0DVvXoaUcWuUSqWH9ep/mLpJMq1qxq68Lo1t23NSL6VVPuTUmXrRE8X0KRNZGKT+ rkMYnceCMPoNxOgyFKO7cAeKIAMzLAy8RXsN+Q4Z/GSu3p/katVcwb4Q6Ffswfj3 P0YwMoLV3weHzf8GcNjkuKNYy4tiLa64wBd7fwUwdECdCYmS+ZAoSVEBRQki0GLA gQaKD8xAw+qkR6hOEmDoCc/PUWDIycxNLcpMzmYw27hRr59hG4OzNwsorJybKxb5 UhUYUdMwUOAkZ2+FOHo/0NHAeOY4ZCDAUr0X6PaTqGAbnIUtZN2FUUMWKbHXQwJX AiNFfsBIkQ6lSfPzqAdO4gBbUXhncCkjH2yHMeAJiPp2EA12oPBAiZaGls0lS9cB NP42rKpQASwRR2JP2zoQyg+7bA8FAFYeFKAXUUrg6gKjPGCAZS0+cNaCFgvg7DMR ln2SbdCzzwGf+DuCoHxjjpRvMMvD/+fxFO7o9UYCtN6w6MqKuQyyQJ6wCgA= =8ie6 -END PGP MESSAGE-
Bug#773623: nodejs: CVE-2014-7192
On Sun, Dec 21, 2014 at 5:31 AM, Jérémy Lal wrote: Le samedi 20 décembre 2014 à 22:07 -0500, Michael Gilbert a écrit : package: src:nodejs CVE-2014-7192[0],[1]: | Eval injection vulnerability in index.js in the syntax-error package | before 1.1.1 for Node.js 0.10.x, as used in IBM Rational Application | Developer and other products, allows remote attackers to execute | arbitrary code via a crafted file. This doesn't affect nodejs, but the syntax-error module, a dependency of browserify - both not packaged in debian. Cannot reassign, then. Maybe close ? The advisories seem to indicate that the origin of the flaw lies within nodejs, not the libraries using it. That may be right or wrong, but it should be checked. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772365: simpleburn: bashism in /bin/sh script
Hello,
here is my contribution to Jessie's bug squash.
I attach a patch with various fixes for bashisms (not fully tested).
Best regards, Georges.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
Index: simpleburn-1.7.0/scripts/simpleburn-detect.sh
===
--- simpleburn-1.7.0.orig/scripts/simpleburn-detect.sh
+++ simpleburn-1.7.0/scripts/simpleburn-detect.sh
@@ -1,6 +1,6 @@
#!/bin/sh
-function detect() {
+detect() {
device=$1 #assumes it is a valid CD / DVD device
readcd dev=$device -fulltoc 2/dev/null; rm -f ~/toc.dat; rm -f toc.dat #wait for loading
if cdrom_id $device | grep -q ID_CDROM_MEDIA; then
@@ -22,7 +22,7 @@ function detect() {
if [ -z $mediacapacity ]; then
mediacapacity=`cdrecord -atip dev=$device 21 | grep phys size:... | tail -1 | sed 's/phys size:... \+//'`
fi
-let mediacapacity=mediacapacity*2048
+mediacapacity=$((mediacapacity*2048))
fi
{ mplayer -dvd-device $device dvd://1 -identify -vo null -ao null -frames 0 21 /tmp/simpleburn-detect.$$ ;} 21 /dev/null
if grep -q ID_DVD_TITLES /tmp/simpleburn-detect.$$; then
@@ -31,13 +31,13 @@ function detect() {
for title in `cat /tmp/simpleburn-detect.$$ | grep TITLE_[0-9]\+_LENGTH`; do #for each title during more than 3'
titlenum=`echo $title | cut -d'_' -f4`
titlelenght=`echo $title | cut -d'=' -f2 | cut -f1 -d'.'`
- let minutes=titlelenght/60
- if (( minutes 3 )); then
- if (( $titlenum != 1 )); then
+ minutes=$((titlelenght/60))
+ if [ $(( minutes 3 )) = 1 ]; then
+ if [ $(( $titlenum != 1 )) = 1 ]; then
{ mplayer -dvd-device $device dvd://$titlenum -identify -vo null -ao null -frames 0 21 /tmp/simpleburn-detect.$$; } 21 /dev/null
fi
if grep -q ID_AID /tmp/simpleburn-detect.$$ grep -q ID_SID /tmp/simpleburn-detect.$$; then
- let trackscount=trackscount+1
+ trackscount=$((trackscount+1))
if [ ! -z $mediainfos ]; then
mediainfos=$mediainfos\n
detailedinfos=$detailedinfos\n
@@ -58,7 +58,7 @@ function detect() {
subdetailedinfos=$subdetailedinfos $languagename($languageid)
done
mediainfos=$mediainfos;$mediasubinfos
-if [ $id == ID_AID ]
+if [ $id = ID_AID ]
then detailedinfos=$detailedinfos\n\tlanguages: $subdetailedinfos
else detailedinfos=$detailedinfos\n\tsubtitles: $subdetailedinfos
fi
@@ -76,16 +76,17 @@ function detect() {
mediatype=cd
if cdrom_id $device | grep -q ID_CDROM_MEDIA_CD_R; then
mediacapacity=`cdrecord -atip dev=$device 21 | grep ATIP start of lead out: | sed 's/.*: \([0-9]\+\) .*/\1/'`
- let mediacapacity=mediacapacity*2048
+ mediacapacity=$((mediacapacity*2048))
fi
if cdrom_id $device | grep -q ID_CDROM_MEDIA_TRACK_COUNT_AUDIO; then
mediacontent=audio
mediasize=`cdrecord -toc dev=$device 21 | grep track:lout | sed 's/track:lout lba: \+\([0-9]\+\) .*/\1/'`
- let mediasize=mediasize*2048
+ mediasize=$((mediasize*2048))
cdda2wav -J -L1 -v titles,toc -g -N -H dev=$device out-fd=1 2/dev/null | tr -d '\200-\377' /tmp/simpleburn-detect.$$
medialabel=`cat /tmp/simpleburn-detect.$$ | grep ^Album title: | sed 's/^Album title: .\(.*\). from .*$/\1/'`
n=`cat /tmp/simpleburn-detect.$$ | grep ^T..: | wc -l`
- for (( i=1; i=$n; i++ )); do
+ i=1
+ while [ $((i=$n)) =1 ]; do
line=`cat /tmp/simpleburn-detect.$$ | grep ^T..: | sed -n $i\p`
if [ ! -z $mediainfos ]; then
mediainfos=$mediainfos\n
@@ -96,6 +97,7 @@ function detect() {
tracklength=`echo $line | sed 's/T..: \(.*\) title.*/\1/' | cut -f1 -d .`
detailedinfos=$detailedinfostrack $tracknum ($tracklength): $tracktitle
mediainfos=$mediainfos$tracknum;$tracktitle;$tracklength
+ i=$((i+1))
done
rm -f /tmp/simpleburn-detect.$$
fi
@@ -105,8 +107,8 @@ function detect() {
fi
fi
- let mediasize_=mediasize/1048576
- let mediacapacity_=mediacapacity/1048576
+ mediasize_=$((mediasize/1048576))
+ mediacapacity_=$((mediacapacity/1048576))
if [ $rewritablemedia -eq 1 ]
then rewritablemedia_=yes
else rewritablemedia_=no
@@ -122,12 +124,12 @@ for tool in cdrom_id blkid isosize cdrec
done
#common parameters
-if [ $1 == --help ] || [ $1 == -h ]; then
+if [ $1 = --help ] || [ $1 = -h ]; then
echo usage: $0 [CD / DVD device]
echo example: $0 /dev/sr0
exit
fi
-if [ $1 == -cr ]; then opt=-cr; shift; fi
+if [ $1 = -cr ]; then opt=-cr; shift; fi
if [ -b $1 ]
then device=$1; shift
else device=/dev/cdrom
@@ -145,12 +147,12 @@ mediainfos= #computer readable (-cr)
detailedinfos= #human readable
#display infos if asked for
-if [ `basename '$0` == simpleburn-detect.sh ]; then
+if [ `basename '$0` = simpleburn-detect.sh ]; then
detect $device
- if [ $opt == -cr ]
+ if [
Bug#773635: python-wxgtk2.8: WXU_2.8 not defined: Cannot run apps that use wxPython 2.8
Control: tags -1 +wontfix
On Sun, Dec 21, 2014 at 02:22:35AM -0800, Jordan Irwin wrote:
I have an application that I develop that used wxPython. Currently my app
supports both version 2.8 and 3.0 of wxPython/wxWidgets. However, when
trying to run my app on Debian using 2.8 I get the following error:
ImportError: /usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode/wx/_gdi_.so:
symbol _ZTV14wxGraphicsPath, version WXU_2.8 not defined in file
libwx_gtk2u_core-2.8.so.0 with link time reference
I was curious if only my application was affected so I went into the source
code of an application from the Debian repository that uses wxPython. In
this case I used drPython. By default drPython will use the newest version of
wxPython (I believe). drPython started up fine as it was using wxPython 3.0
by default. However, I changed its code and forced it to use version 2.8.
Once I did that I received the same error output as above.
FWIW, I'm unable to reproduce this - I uncommented these two lines in
/usr/share/drpython/drpython/drpython.py:
#import wxversion
#wxversion.select('2.8')
And drpython appears to run OK (the about dialog system information
shows it is using 2.8).
But anyway, wxwidgets2.8 is dead at this point (both upstream and in
Debian). It won't be in jessie, and the only reason the package hasn't
been removed from unstable already is as a courtesy to a handful of
packages which haven't yet updated to 3.0. If you aren't one of those
packages, just use 3.0 instead (and if you are, please put your efforts
into updating to 3.0 rather than continuing to try to support 2.8).
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#773576: ntp: CVE-2014-9293 CVE-2014-9294 CVE-2014-9295 CVE-2014-9296
What about fixes for unstable? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#772365: simpleburn: bashism in /bin/sh script
On 21.12.2014 18:51, Georges Khaznadar wrote: Hello, here is my contribution to Jessie's bug squash. I attach a patch with various fixes for bashisms (not fully tested). Best regards, Georges. Control: +patch Contro: +pending Hello, Thanks for patch, I will upload fixed package tomorrow. Mateusz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773660: www.debian.org(/security) misses critical information
package: www.debian.org severity: important x-debbugs-cc: t...@security.debian.org Hi, verbatin from #debian-security: h01ger | the german version of http://www.debian.org/ only show dsa-3091 from december 7 as latest h01ger | oh, same for http://www.debian.org/index.en.html h01ger | http://www.debian.org/security/ has it though - even in germam h01ger | now www.d.o has them. yay caching? h01ger | but it still misses dsa-3107-1, dsa-3108-1 and 3107-2 h01ger | also on the security page Thanks for maintaining www.debian.org! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773661: linux-image-3.16-3-amd64: drm error messages on boot
Package: src:linux Version: 3.16.5-1 Severity: minor Dear Maintainer, On boot I have two errors reported by the kernel : [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun This is just cosmetic because boot process continues normally after the warnings. Thanks in advance. Best regards. Librement from France. -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-3-amd64 root=UUID=d73ac13e-29f5-477b-9324-ff6d9aed054f ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [8.406848] ACPI: Power Button [PWRF] [8.408663] ACPI: AC Adapter [AC] (on-line) [8.431389] mei_me :00:16.0: irq 47 for MSI/MSI-X [8.434777] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input10 [8.458211] tpm_tis 00:01: 1.2 TPM (device-id 0xB, rev-id 16) [8.471499] wmi: Mapper loaded [8.482284] [drm] Initialized drm 1.1.0 20060810 [8.569473] ACPI: Battery Slot [BAT0] (battery present) [8.569561] ACPI: Battery Slot [BAT1] (battery absent) [8.671004] tpm_tis 00:01: TPM is disabled/deactivated (0x7) [8.848324] alg: No test for crc32 (crc32-pclmul) [8.852231] cfg80211: Calling CRDA to update world regulatory domain [8.946310] [drm] Memory usable by graphics device = 2048M [8.946316] [drm] Replacing VGA console driver [8.947461] Console: switching to colour dummy device 80x25 [8.985456] iTCO_vendor_support: vendor-support=0 [8.985993] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [8.986046] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [8.986208] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [9.123688] i915 :00:02.0: irq 48 for MSI/MSI-X [9.123711] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [9.123713] [drm] Driver supports precise vblank timestamp query. [9.152262] input: HP WMI hotkeys as /devices/virtual/input/input15 [9.152915] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [9.193511] fbcon: inteldrmfb (fb0) is primary device [9.402480] intel_rapl: RAPL domain dram detection failed [9.456700] ath: phy0: Enable LNA combining [9.457950] ath: EEPROM regdomain: 0x60 [9.457951] ath: EEPROM indicates we should expect a direct regpair map [9.457954] ath: Country alpha2 being used: 00 [9.457955] ath: Regpair used: 0x60 [9.467190] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.467191] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [9.530129] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [9.530911] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [9.531257] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc9001118, irq=19 [9.640942] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1c0b1, caps: 0xd00033/0x64/0xa0400, board id: 1621, fw id: 730177 [9.687781] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input14 [9.913111] Console: switching to colour frame buffer device 170x48 [9.917204] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.917206] i915 :00:02.0: registered panic notifier [9.982649] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [9.982882] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16 [9.983160] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [9.983802] snd_hda_intel :00:1b.0: irq 49 for MSI/MSI-X [ 10.109328] sound hdaudioC0D0: autoconfig: line_outs=1 (0xa/0x0/0x0/0x0/0x0) type:line [ 10.109336] sound hdaudioC0D0:speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 10.109339] sound hdaudioC0D0:hp_outs=1 (0xb/0x0/0x0/0x0/0x0) [ 10.109342] sound hdaudioC0D0:mono: mono_out=0x0 [ 10.109344] sound hdaudioC0D0:inputs: [ 10.109348] sound hdaudioC0D0: Mic=0xc [ 10.109351] sound hdaudioC0D0: Internal Mic=0x11 [ 10.109354] sound hdaudioC0D0: Line=0xf [ 10.298357] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input17 [ 10.299367] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input18 [ 10.300662] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input19 [ 10.300932] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card0/input20 [ 10.301128] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input21 [ 10.301265] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input22 [ 10.301390] input: HDA
Bug#764630: RFS: javatools 0.48 [RC]
On 12/14/2014 09:50 AM, Markus Koschany wrote: On 12.12.2014 07:05, tony mancill wrote: [...] Any concerns from the team? This is kind of a brute force approach, but seems reasonable. My question is: Do we feel confident that this the lists below are representative for for jessie? MULTIARCH_LIBRARY_PATH_32BIT=/usr/lib/jni:/usr/lib/arm-linux-gnueabi/jni:/usr/lib/arm-linux-gnueabihf/jni:/usr/lib/i386-gnu/jni:/usr/lib/i386-linux-gnu/jni:/usr/lib/x86_64-kfreebsd-gnu/jni:/usr/lib/i386-kfreebsd-gnu/jni:/usr/lib/mips-linux-gnu/jni:/usr/lib/mipsel-linux-gnu/jni:/usr/lib/powerpc-linux-gnu/jni:/usr/lib/powerpc-linux-gnuspe/jni:/usr/lib/sparc-linux-gnu/jni:/usr/lib/x86_64-linux-gnux32/jni:/usr/lib/hppa-linux-gnu/jni:/usr/lib/sh4-linux-gnu/jni:/usr/lib/m68k-linux-gnu/jni MULTIARCH_LIBRARY_PATH_64BIT=/usr/lib/jni:/usr/lib/alpha-linux-gnu/jni:/usr/lib/x86_64-linux-gnu/jni:/usr/lib/aarch64-linux-gnu/jni:/usr/lib/x86_64-kfreebsd-gnu/jni:/usr/lib/powerpc64-linux-gnu/jni:/usr/lib/powerpc64le-linux-gnu/jni:/usr/lib/s390x-linux-gnu/jni:/usr/lib/sparc64-linux-gnu/jni Hi, since nobody seems to have any comments, let me chime in here. The list above is complete and contains all possible 32bit and 64bit multiarch paths. There was one mistake with kfreebsd-64 but this one has been already fixed two days ago. As you rightfully wrote above, this is some kind of brute force approach but I'm confident that it covers all possible scenarios. Now the code checks what kind of JVM is used and adds the respective MULTIARCH_LIBRARY_PATH to -Djava.library.path. Actually I would prefer that all JREs would handle that by themselves but it seems so far only OpenJDK is capable of doing it. Or should jarwrapper honor MULTIARCH_LIBRARY_PATH (or JARWRAPPER_MULTIARCH_LIBRARY_PATH, or similar) in the environment? Just in case we missed something or something else comes along. If present, perhaps this could be added after /usr/lib/jni, and before the other components of the path. The downside of this approach is that we need to add new multiarch paths to jarwrapper whenever a new architecture gets introduced to Debian. However I think this is manageable. The purpose of jarwrapper is to set up binfmt-misc to run executable jar files. I feel that no further user or maintainer interaction should be necessary in addition to that. It should just work (TM). So in my opinion it would be better if it did not honor any additional environment variables and simply did its job. [trimming the portion of the email regarding policy - we'll return to that post-jessie] I'll buy the statement that it should just work. Regarding an upload, I noticed that there are a few subsequent changes/fixes pushed to the packaging repo since December 5th. They don't require any updates to debian/changelog, since they're all related to this bug. Is there any work or testing still in progress? Any concerns with an upload for the state of the package as of 94c25581? Thank you, tony signature.asc Description: OpenPGP digital signature
Bug#773660: dsa-3108 returns 404, I think that explains...
http://www.debian.org/security/2014/dsa-3108 returns a page not found error, I guess that explains... now why is this DSA missing? signature.asc Description: This is a digitally signed message part.
Bug#773576: ntp: CVE-2014-9293 CVE-2014-9294 CVE-2014-9295 CVE-2014-9296
On Sun, Dec 21, 2014 at 12:59 PM, Christoph Anton Mitterer wrote: What about fixes for unstable? What about asking for an RFS? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773662: Package homepage has moved/changed
Package: node-mocha Version: 1.20.1-1 Severity: minor Tags: patch Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/control b/debian/control index fdcc0c5..92630ac 100644 --- a/debian/control +++ b/debian/control @@ -18,7 +18,7 @@ Build-Depends: , node-glob , uglifyjs Standards-Version: 3.9.5 -Homepage: http://visionmedia.github.io/mocha +Homepage: http://mochajs.org/ Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-mocha.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-mocha.git
Bug#773576: ntp: CVE-2014-9293 CVE-2014-9294 CVE-2014-9295 CVE-2014-9296
On Sun, Dec 21, 2014 at 01:05:04PM -0500, Michael Gilbert wrote: What about fixes for unstable? What about asking for an RFS? I'm putting an NMU targeting sid/jessie together now. Unless someone beats me to it, I should be uploading today. noah signature.asc Description: Digital signature
Bug#748728: Bug#772679: unblock: libuser/1:0.60~dfsg-1.1
On Sun, Dec 21, 2014 at 1:32 PM, Michael Gilbert wrote: Here is a proposal, rename lid in id-utils to qid. Here is the logic: Also, no other package provides a qid binary in any of the bin dirs. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748728: Bug#772679: unblock: libuser/1:0.60~dfsg-1.1
On Wed, Dec 10, 2014 at 11:39 AM, Julien Cristau wrote: Because that's not what policy says Conflicts is for. If typing 'lid' runs an entirely different command depending on the phase of the moon, we've done something wrong, and we should fix it. It's quite possible the least disruptive option is to rename both commands. Here is a proposal, rename lid in id-utils to qid. Here is the logic: - the libuser commands are all preceded by L, so changing that to anything else would be inconsistent - the id-utils lid command is a Query operation, so Q probably makes more sense than L (see manpage) Note that id-utils does have one reverse-dependency (seascope), and that does use the lid command, so there will be some small fallout. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738987: Update to new stable version 1.2.4
Hi, Is there a plan to update to new stable version? It seems that there is no activity recently on this package (8 months?). Is this package became an orphan package? It would be great if you continue to support this package. Thanks.
Bug#773663: popularity-contest: Patch to enable Tor support
Attaching the correct support_tor.diff :(
--
Federico
diff --git a/debian/control b/debian/control
index 2bf1d82..dbe674a 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Architecture: all
Pre-Depends: debconf (= 1.5.34) | cdebconf (= 0.106)
Depends: ${misc:Depends}, ${perl:Depends}, dpkg (= 1.10),
libio-socket-ip-perl (= 0.25-3)
Recommends: gnupg, cron | fcron, exim4 | mail-transport-agent
-Suggests: anacron
+Suggests: anacron, tor
Provides: popcon
Description: Vote for your favourite packages automatically
The popularity-contest package sets up a cron job that will
diff --git a/debian/cron.daily b/debian/cron.daily
index c45bccb..f3feaa7 100644
--- a/debian/cron.daily
+++ b/debian/cron.daily
@@ -12,6 +12,7 @@ unset MY_HOSTID
unset PARTICIPATE
unset SUBMITURLS
unset USEHTTP
+unset USETOR
unset MTAOPS
# get configuration information
@@ -31,6 +32,24 @@ if [ -z $MAILTO ] [ yes != $USEHTTP ]; then exit 0;
fi
# don't run if PARTICIPATE is no or unset!
if [ $PARTICIPATE = no ] || [ -z $PARTICIPATE ]; then exit 0; fi
+# enable torify
+TORIFY_PATH=/usr/bin/torify
+if [ $USETOR = yes ]; then
+if [ yes != $USEHTTP ]; then
+echo popularity-contest: when USETOR is set USEHTTP must be set as
well 21
+exit 1
+fi
+if [ ! -x $TORIFY_PATH ]; then
+echo popularity-contest: USETOR is set but torify is not available.
21
+echo popularity-contest: Please install the tor package. 21
+exit 1
+fi
+TORIFY=$TORIFY_PATH
+else
+TORIFY=''
+fi
+
+
if [ -n $HTTP_PROXY ]; then
export http_proxy=$HTTP_PROXY;
fi
@@ -98,7 +117,7 @@ SUBMITTED=no
# try to post the report through http POST
if [ $SUBMITURLS ] [ yes = $USEHTTP ]; then
for URL in $SUBMITURLS ; do
- if setsid /usr/share/popularity-contest/popcon-upload \
+ if setsid $TORIFY /usr/share/popularity-contest/popcon-upload \
-u $URL -f $POPCON 2/dev/null ; then
SUBMITTED=yes
else
@@ -108,8 +127,9 @@ if [ $SUBMITURLS ] [ yes = $USEHTTP ]; then
fi
# try to email the popularity contest data
+# skip emailing if USETOR is set
-if [ yes != $SUBMITTED ] [ $MAILTO ]; then
+if [ yes != $SUBMITTED ] [ yes != $USETOR ] [ $MAILTO ]; then
if [ -x `which sendmail 2/dev/null` ]; then
(
if [ -n $MAILFROM ]; then
diff --git a/default.conf b/default.conf
index 433bc14..718aa99 100644
--- a/default.conf
+++ b/default.conf
@@ -51,6 +51,14 @@ SUBMITURLS=http://popcon.debian.org/cgi-bin/popcon.cgi;
# USEHTTP enables http reporting. Set this to 'yes' to enable it.
USEHTTP=yes
+# USETOR enables using Tor to perform http reporting.
+# In order to use it, set it to yes and set USEHTTP to yes as well.
+# Also ensure that the tor package is installed and the tor daemon
+# is running.
+# When USETOR is set, email-based submission is disabled.
+# More information: https://www.torproject.org/
+USETOR=no
+
# HTTP_PROXY allows to specify an HTTP proxy server, the syntax is
# HTTP_PROXY=http://proxy:port;. This overrides the environment
# variable http_proxy.
Bug#773663: popularity-contest: Patch to enable Tor support
On Sun, Dec 21, 2014 at 06:31:33PM +, Federico Ceratto wrote: Package: popularity-contest Version: 1.61 Severity: wishlist Hi, Attached is a small patch to enable popcon submissions over Tor. It might help https://trac.torproject.org/projects/tor/ticket/13154 Even with GnuPG encryption, regular HTTP submissions leaks the presence of a Debian[-derivative] OS and this could also be used to enumerate Debian hosts in a network; Also, popcon-upload could be forced to fall-back to SMTP and leak more information in the headers. The patch relies on exit nodes to connect to the HTTP service and prevents SMTP fallback. If a popcon hidden service was to be set up in future, it could be used with: SUBMITURLS=http://HIDDEN_SERVICE_NAME/cgi-bin/popcon.cgi; Hello Federico, For some reason, your patch is empty: all I have is commit 58af819641e879260b180558cac56cfd3f5d7333 Author: Federico Ceratto federico.cera...@gmail.com Date: Sun Dec 21 16:49:16 2014 + Add Tor support :100644 100644 2bf1d82... dbe674a... M debian/control :100644 100644 c45bccb... f3feaa7... M debian/cron.daily :100644 100644 433bc14... 718aa99... M default.conf Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773664: [I18N:de] Updated German translation of debconf templates
Package: src:grub2 Severity: wishlist Tags: patch, l10n Control: submitter -1 Martin Eberhard Schauer martin.e.scha...@gmx.de ---BeginMessage--- Hi Ian, sorry for the late reply. You are noted as the last translator of the debconf translation for grub2. I'm quite proud of this prominent contribution to Debian :-) Unfortunately the two new strings did not get a review on debian-l10n-german. But I had a second and a third glance at the translation. Kind regards, Martin # Translation of GRUB 2 debconf templates to German # Copyright (C) Helge Kreutzmann deb...@helgefjell.de, 2007-2009. # Martin Eberhard Schauer martin.e.scha...@gmx.de, # 2010, 2011, 2014. # This file is distributed under the same license as the grub2 package. # msgid msgstr Project-Id-Version: grub2 1.98+20100710-2\n Report-Msgid-Bugs-To: gr...@packages.debian.org\n POT-Creation-Date: 2014-12-13 20:23+\n PO-Revision-Date: 2014-12-21 18:29+0100\n Last-Translator: Martin Eberhard Schauer martin.e.scha...@gmx.de\n Language-Team: German debian-l10n-ger...@lists.debian.org\n Language: de\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: Lokalize 1.0\n Plural-Forms: nplurals=2; plural=n != 1;\n #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid Chainload from menu.lst? msgstr Aus »menu.lst« laden (Chainload)? #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub. msgstr Die Upgrade-Skripte von GRUB haben eine Installation von »GRUB Legacy« in / boot/grub gefunden. #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid In order to replace the Legacy version of GRUB in your system, it is recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image from your existing GRUB Legacy setup. This step can be automatically performed now. msgstr Um die Legacy-Version von GRUB auf Ihrem System zu ersetzen, wird die Anpassung von /boot/grub/menu.lst empfohlen, so dass GRUB 2 aus Ihrer bestehenden GRUB-Legacy-Konfiguration heraus geladen wird. Dieser Schritt kann jetzt automatisch vollzogen werden. #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid It's recommended that you accept chainloading GRUB 2 from menu.lst, and verify that the new GRUB 2 setup works before it is written to the MBR (Master Boot Record). msgstr Es wird empfohlen, dass Sie dem Laden von GRUB 2 aus menu.lst zustimmen und überprüfen, dass Ihre neue »GRUB 2«-Installation funktioniert, bevor diese in den MBR (Master Boot Record) geschrieben wird. #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid Whatever your decision, you can replace the old MBR image with GRUB 2 later by issuing the following command as root: msgstr Unabhängig von Ihrer Entscheidung können Sie den alten MBR später durch GRUB 2 ersetzen. Geben Sie dazu als »root« den folgenden Befehl ein: #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid GRUB install devices: msgstr Geräte für die GRUB-Installation: #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid The grub-pc package is being upgraded. This menu allows you to select which devices you'd like grub-install to be automatically run for, if any. msgstr Für das Paket grub-pc wird gerade ein Upgrade durchgeführt. In diesem Menü können Sie auswählen, ob und für welche Geräte grub-install automatisch ausgeführt werden soll. #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid Running grub-install automatically is recommended in most situations, to prevent the installed GRUB core image from getting out of sync with GRUB modules or grub.cfg. msgstr Für die Mehrzahl der Fälle wird empfohlen, grub-install automatisch laufen zu lassen. So wird vermieden, dass das installierte GRUB-Image nicht zu den GRUB-Modulen oder grub.cfg passt. #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. msgstr Wenn Sie nicht sicher sind, welches Gerät das BIOS zum Booten benutzt, ist es oft eine gute Idee, GRUB auf allen Geräten zu installieren. #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. msgstr Hinweis: Sie können GRUB auch in die Boot-Blöcke von Partionen schreiben. Hier werden
