Bug#785685: ruby2.2: Provide debug symbols (-dbg)
Source: ruby2.2 Severity: wishlist Dear ruby maintainers, Could you consider providing debug symbols for ruby? We had a segfault issue and it'd make debugging a lot easier. thanks, chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784854: MIA for Karolina Kalic karol...@resenje.org
Hi Karolina, On Mon, 18 May 2015 10:58:08 Karolina Kalic wrote: As I can remember, MIA team contacted me a while ago. And I explained that I can not continue my work for Debian at the moment. The packages should have been orphaned properly after that. I don't know what happened. I'm glad that someone wants to continue the work on unico. I don't have any objections. Thanks for your reply. I hope one day you will be able to contribute to Debian again. -- Best wishes, Dmitry Smirnov. --- The more false we destroy the more room there will be for the true. -- Robert G. Ingersoll, 1902 signature.asc Description: This is a digitally signed message part.
Bug#772423: O: haskell-doc -- Assorted Haskell language documentation
2015/05/18, 11:30, Alexandre Delanoë: 2015/05/08, 08:42, Robert Bihlmeyer: Hi, please summarise or give a pointer to the discussion. In the list: pkg-haskell-maintain...@lists.alioth.debian.org Thread open by message-ID: 20150410184237.ga14...@delanoe.org The end of the thread is here: https://lists.debian.org/debian-haskell/2015/04/msg00011.html -- Alexandre Delanoë www.delanoe.org/c -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784439: [Pkg-javascript-devel] Bug#784439: Bug#784439: uglifyjs version failing
2015-05-19 9:25 GMT+02:00 Jonas Smedegaard d...@jones.dk: Quoting Jérémy Lal (2015-05-19 02:15:29) 2015-05-19 1:34 GMT+02:00 Jonas Smedegaard d...@jones.dk: Please actually look at the uglifyjs source package - or just read closely the original bugreport - before you comment further. I think you will then agree that your remarks are totally irrelevant here. Well, i actually did that. So if you've setup the files with the same tree as in source, that is /usr/lib/nodejs/uglify-js/bin/uglifyjs /usr/lib/nodejs/uglify-js/lib/*.js /usr/lib/nodejs/uglify-js/package.json and a symlink /usr/lib/nodejs/uglify-js/bin/uglifyjs - /usr/bin/uglifyjs there wouldn't be a need for the patches. As i said, i'm not questionning the dislike for keeping the original tree, i'm just saying that it avoids adding more patches. Ohh, now I get it. Thanks for spelling it out to me: I even considered if you perhaps meant to install _everything_ including the script below /usr/lib/nodejs but dismissed that as unrealistic. So Nodejs lookup path is not only /usr/lib/nodejs/$lib.js and /usr/lib/$lib/index.js but also /usr/lib/nodejs/$lib/lib/index - or does it take /usr/lib/nodejs/$lib/package.json into account (I notice there's a mention of main in there - which is actually incorrect now with my patching)? package.json it is Jérémy.
Bug#785659: libdist-zilla-perl: FTBFS: t/plugins/testrelease.t failure
Control: forwarded -1 https://github.com/rjbs/Dist-Zilla/issues/398 On Mon, 18 May 2015 23:37:26 +0300, Niko Tyni wrote: Package: libdist-zilla-perl Version: 5.020-1 Severity: serious Tags: stretch sid This package fails to build from source for me on current sid, but not on jessie. No idea yet which package upgrade broke it. This looks like #723930 reappearing. What has changed since jessie is that debhelper now indeed runs tests verbosely. Maybe the test-in-the-test (if I'm reading the output correctly) is the problem here? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #296: The hardware bus needs a new token. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785672: Critical ext4 data corruption bug
Am 19.05.15 um 01:12 schrieb Josh Triplett: Package: src:linux Version: 4.0.2-1 Severity: critical Tags: upstream 4.0.3 includes a fix for a critical ext4 bug that can result in major data loss. I believe this is the bug I just hit on my server, resulting in massive filesystem corruption. See upstream commit d2dc317d564a46dfc683978a2e5a4f91434e9711 (ext4: fix data corruption caused by unwritten and delayed extents), which has been added to stable kernels 4.0.3 as well as much older stable kernels. Please consider incorporating this patch into the Debian kernels as soon as possible, including into the Jessie kernel. Some time ago I also had some massive data corruption problem with an ext4 partition which may also have been caused by the same bug. The notable thing is that other ext4 installations have worked fine for a long while in spite of this bug. No fsck had helped; had to reformat having lost all data on the partition. We need to warn any existing ext4 user! The patch should be distributed as soon as possible. My recommendation would be not to use ext4 or to convert to btrfs unless a fix is available. Otherwise assert your backups! Elmar - Josh Triplett -- Package-specific info: ** Version: Linux version 4.0.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-16) ) #1 SMP Debian 4.0.2-1 (2015-05-11) ** Command line: BOOT_IMAGE=/vmlinuz-4.0.0-1-amd64 root=/dev/mapper/data-root ro quiet ** Not tainted -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.0.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.56 ii initramfs-tools [linux-initramfs-tool] 0.120 ii kmod20-1 ii linux-base 3.5 ii module-init-tools 20-1 Versions of packages linux-image-4.0.0-1-amd64 recommends: ii firmware-linux-free 3.3 pn irqbalance none Versions of packages linux-image-4.0.0-1-amd64 suggests: pn debian-kernel-handbook none ii grub-pc 2.02~beta2-23 pn linux-doc-4.0 none Versions of packages linux-image-4.0.0-1-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none ii firmware-iwlwifi0.43 pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-4.0.0-1-amd64/postinst/depmod-error-initrd-4.0.0-1-amd64: false linux-image-4.0.0-1-amd64/prerm/removing-running-kernel-4.0.0-1-amd64: true linux-image-4.0.0-1-amd64/postinst/mips-initrd-4.0.0-1-amd64: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784863: Debian package for kmer -- test suites
Hello again, As I've been looking to modify kmer to use an unmodified version of kazlib as already packaged in Debian, I first started checking out your test suite to make sure there is a chance of detecting potential issues due to such a change. I see, however, that the test suite is not in very good shape. I may be able to help you get it working again if it's a matter of some shuffling around in the interfaces used by the drivers. Is there anything I should be aware of before undertaking this? Thanks for your cooperation with this effort. Afif PS: In CC on this email, we have the Debian Med list and the packaging log for kmer in Debian. -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785684: libmariadb-client-lgpl-dev: New upstream version (MariaDB Connector/C 2.1.0)
Package: libmariadb-client-lgpl-dev Version: 2.0.0-1 Severity: normal Hello, There is a new upstream GA version (2.1.0), fixing various issues. It'd be great if it can be packaged. We have migrated our jenkins test suite to build against libmariadb-client-lgpl-dev 2.0.0 and we are getting some random segfaults that seem to be fixed in 2.1.0. More info at the mariadb KB: https://mariadb.com/kb/en/mariadb/mariadb-connector-c-210-release-notes/ This is a Stable (GA) release of the MariaDB Connector/C, formerly known as MariaDB Client Library for C. In general, marking this release as stable means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow). thank you, chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785678: blends-dev: Do not drop virtual packages in alternatives
Hi Felipe, thanks for this bug report. I confirm that this is actually an issue that should be fixed. However, I intend to switch to the blends-dev code base developed in GSoC 2013 in the Jessie release cycle basically because it will enable architecture dependant metapackages. The current blends-dev just uses the build machine (in my case amd64) to decide what package is available which is simply wront. The new code checks UDD for creating the list of architectures which is more correct but requires creating the blends source package on a machine with access to an UDD instance (alioth for instance). And it needs more testing. I'm hesitating to fix this bug in the old code base since I hope I will be able to use DebCamp to work on the final switch. (As always a patch could convince me to be faster ;-)) On Tue, May 19, 2015 at 10:09:32AM +0800, Paul Wise wrote: On Tue, May 19, 2015 at 9:15 AM, Felipe Sateler wrote: I use blends-dev to create local metapackages. I sometimes use the common real-package | virtual-package pattern to specify a default but allow alternatives. However, blends-dev removes the virtual-package alternatives since they do not exist. It would be great if one could pass an option or something to allow nonexistent packages in Depends lines. I think it would be better if blends-dev could know which virtual packages exist and allow them in Depends, but not allow non-existent real or virtual packages. Since dpkg now allows versioned Provides, it would also need to check the version constraints are correct. I need to verify but I think in UDD we can use a list of virtual packages so yes, this suggestion will be probably implemented. Moreover I think we should implement some test suite that guaranties that this kind of problems will be detected quickly. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#395843: Status Report (wgs-assembler)
An old thread (from 2011) on this package's status: https://lists.debian.org/debian-med/2011/03/msg00028.html A recent, pertinent thread: https://lists.debian.org/debian-med/2015/04/msg00065.html Currently, packaging is ongoing for kmer, a dependency of wgs-assembler. See https://bugs.debian.org/784863 for its status. -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785686: supertux: New upstream release: 0.3.5a
Package: supertux Version: 0.3.4-1 Severity: wishlist Dear Maintainer, please consider updating supertux in experimental to 0.3.5a: http://supertux.lethargik.org/download.html http://supertux.lethargik.org/wiki/Changelog_0.3.5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784439: [Pkg-javascript-devel] Bug#784439: Bug#784439: uglifyjs version failing
Quoting Jérémy Lal (2015-05-19 02:15:29) 2015-05-19 1:34 GMT+02:00 Jonas Smedegaard d...@jones.dk: Please actually look at the uglifyjs source package - or just read closely the original bugreport - before you comment further. I think you will then agree that your remarks are totally irrelevant here. Well, i actually did that. So if you've setup the files with the same tree as in source, that is /usr/lib/nodejs/uglify-js/bin/uglifyjs /usr/lib/nodejs/uglify-js/lib/*.js /usr/lib/nodejs/uglify-js/package.json and a symlink /usr/lib/nodejs/uglify-js/bin/uglifyjs - /usr/bin/uglifyjs there wouldn't be a need for the patches. As i said, i'm not questionning the dislike for keeping the original tree, i'm just saying that it avoids adding more patches. Ohh, now I get it. Thanks for spelling it out to me: I even considered if you perhaps meant to install _everything_ including the script below /usr/lib/nodejs but dismissed that as unrealistic. So Nodejs lookup path is not only /usr/lib/nodejs/$lib.js and /usr/lib/$lib/index.js but also /usr/lib/nodejs/$lib/lib/index - or does it take /usr/lib/nodejs/$lib/package.json into account (I notice there's a mention of main in there - which is actually incorrect now with my patching)? Or does stuffing everything below /usr/lib/nodejs/$lib/ only solve internal lib paths, and I should still patch main lib to be .../index.js? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#750135: Initial draft of resolution
Le dimanche, 17 mai 2015, 19.00:27 Sam Hartman a écrit : Proposed for your consideration and checked into git for your editing: Thank you for this draft, it's a very good start. I've pushed 5 isolated commits that make the draft text consistent in numbering, capitalization and names. Here come my (uncommitted) comments on the text: Background/Rationale (Constitution 6.1.5): 1. In #750135, the Technical Committee was asked by Manuel Fernandez Montecelo who should be the maintainer of the Aptitude project. He had been actively committing until his commit access was removed by Daniel Hartwig. Manuel and Daniel took over development of Aptitude in 2011 with the support of Christian Perrier, an admin for the Aptitude alioth project. There was friction between Manuel and Daniel, which eventually resulted in Manuel's commit access being revoked by Daniel. Since then, Daniel has become inactive, and did not comment on the issue when requested by the Technical Committee. That reads like a correct description of events as they have been presented to us. 2. During the discussion of this issue, Christian Perrier proposed that he and Axel Beckert could watch the social aspects of Aptitude development and restore Manuel's commit access. Christian still has administrative rights and believes he has the technical power to implement his proposal. However he wants review from a broader audience before implementing that proposal. Ditto. Did you intend to have these two paragraphs part of the actual decision, or not? Advice (Constitution 6.1.5): 1. The Technical Committee agrees that Christian has the power to implement his proposal and encourages him to do so. I'd replace agrees with acknowledges, but beware of my en_CH ! 2. The committee agrees that restoring Manuel's commit access is a good step to move Aptitude development forward. Since there is a clear way to accomplish this goal within the existing Aptitude project support that approach. I don't understand this second sentence. Is there some punctuation hiccup? 3. We hope that Christian and Axel will work to managed the social aspects of the Aptitude project, working to recruit new developers, building a stronger Aptitude development community, and establishing policies and procedures that promote a collaborative team. Sometimes the skills necessary to grow a community ar different than the skills to develop a project. Through this approach we hope the Aptitude community will gain both sets of skills. Although I don't disagree with the paragraph, I'm not overly comfortable with formalizing our hopes in a resolution. I'd rather drop the complete paragraph from the actual decision, eventually moving it to a non-formal part (either pre- or post- decision). 4. We thank Manuel for bringing this matter to our attention and apologize for our delay in resolving this matter. Good. As you probably noticed from my comments above, I'd rather have a longer background part and a small, but straight-to-the-point formal resolution text. Opinions? Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#782781: No security fix yet
Dear proftpd maintainers, following a recent press release [1], exploits [2] for this bug [3] exist and the bug seems to be unfixed in the currently supported oldstable and stable releases [4]. What about considering a security release or updating the security-tracker information? [1] http://www.heise.de/newsticker/meldung/Angreifer-nutzen-kritische-Luecke-in-ProFTPD-aus-2652114.html (German) [2] https://github.com/nootropics/propane [3] http://bugs.proftpd.org/show_bug.cgi?id=4169 [4] https://security-tracker.debian.org/tracker/CVE-2015-3306 -- Mit freundlichen Grüßen, Mario Lipinski IServ GmbH Bültenweg 73 38106 Braunschweig Telefon: 0531-2243666-0 Fax: 0531-2243666-9 E-Mail:i...@iserv.eu Internet: iserv.eu USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822 Geschäftsführer: Benjamin Heindl, Jörg Ludwig -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785688: abiword: please enable introspection needed by recent sugar-write-activity
Package: abiword Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Recent releases of sugar-write-activity needs abiword introspection. Please enable that. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVWuseAAoJECx8MUbBoAEhbUQP/jSViRtfsbD2aii7Xu2kof1U VUkrQpEcb9lvnmm9+2Z/5lAS+7NNRajvYu5psvtDH7VPE0lJZ3lkHw4ZKlW58dWD OWGiPKjoWcpMaKWsdOQ87lxiuO3kFMfUtHY3M47EfT/lNvFiE8WJ8fKO7+OuXkcm m2xkyxjPki8HCg3yxqiC+r4SoQxMpOxvDpRrqpH+mmSjQ9Xt6v9LOi2B03pvow3R wJtEtI1q9tGLe4DOsPhtclPSJdYinPRa6bd0y2+arLxzgP2F0UVPY3LMtsDB/flj SwyAwTuaC0p2PbUUBUIyAYhVnI/DoPjFI4cGml2ei/HzFmNF+GEhGPNiPlRzgy0Y F9OGwE3ldbm5haRdb2lK2Lnltgh6tfbnHrpEfxHQ9SKdp1Kg5Cqvh0Tw2sHjz4zZ uE5T/PJOCOdZMsbhUT+04DMKUS4Du5saXpbqCpyxnLTKo33mOBLcN0rFJpNH7Xhx UR/J0r4pS21D9mxhz+anR4h6VoszboDHd9d1yetk7BvXbZfB04KPS33f4WQjimnw X8QdFoAY60k3VuP0IEnf+yxxJcOPATgDKLnnOhEioJGRVQ0X9RjJ8jjXt1jTbgCe NXuLd+P59WkbswoS03Ui+OZZHRemzhFO77dpKt6oi5SMfpPCUfWhAnyQHYGnPtyI AWPIDWbMff7ALceXqNcU =Xful -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#732242: rmmod i8k
I had similar symptoms (see #785601), so I ended up doing: $ sudo rmmod i8k Everything seems to operate nicely now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785683: RFS: mod-gnutls/0.6-1.4 [NMU]
Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for a bugfix update of mod-gnutls that would close bug #775909 (segfaults with reverse proxy configuration). I've uploaded the package to Debian Mentors a few weeks ago. The maintainer has not responded (like for the security updates to 0.5.10-1.1+deb7u1 and 0.6-1.3, which went through the security team, see DSA-3177 [1]), so now I'm looking for a sponsor for an NMU. * Package name: mod-gnutls Version : 0.6-1.4 Upstream Author : Daniel Kahn Gillmor d...@fifthhorseman.net * URL : https://mod.gnutls.org/ * License : Apache-2.0 Section : httpd It builds those binary packages: libapache2-mod-gnutls - Apache module for SSL and TLS encryption with GnuTLS To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mod-gnutls Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mod-gnutls/mod-gnutls_0.6-1.4.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Fix segfaults with reverse proxy configuration (Closes: #775909) * Upgrade Standards-Version to 3.9.6, change DocumentRoot in default-tls.conf to /var/www/html accordingly. Regards, Thomas Klute [1] https://www.debian.org/security/2015/dsa-3177 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784863: a note for watchers of this log
Packaging of this project has been discussed solely on the Debian Med mailing list on a thread starting at https://lists.debian.org/debian-med/2015/05/msg6.html. Coordination with the upstream developer began with the thread at https://lists.debian.org/debian-med/2015/05/msg00018.html -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785687: systemd: systemctl double free or corruption when enabling/disabling sysv units if pwd non-readable
Package: systemd Version: 215-17 Severity: normal Dear Maintainer, systemctl fails to enable/disable sysv units if the current working directory is not readable to the user systemctl is running at (root). In my case, the home directory is mounted via nfs and unreadable to root. gdb output: Synchronizing state for docker.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d docker defaults insserv: popd() can not change directory /home/lorenzhs: Permission denied update-rc.d: error: insserv rejected the script header *** Error in `/bin/systemctl': double free or corruption (fasttop): 0x557da900 *** Program received signal SIGABRT, Aborted. 0x7784b107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: Permission denied. (gdb) bt #0 0x7784b107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7784c4e8 in __GI_abort () at abort.c:89 #2 0x77889204 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7797bfe0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #3 0x7788e9de in malloc_printerr (action=1, str=0x7797c1c8 double free or corruption (fasttop), ptr=optimized out) at malloc.c:4996 #4 0x7788f6e6 in _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 #5 0x5556ef93 in freep () at ../src/shared/util.h:641 #6 enable_sysv_units (verb=optimized out, args=0x557da860) at ../src/systemctl/systemctl.c:5016 #7 0x5556f5fd in enable_unit.lto_priv.331 (bus=0x557d9f70, args=0x7fffeb80) at ../src/systemctl/systemctl.c:5235 #8 0x55561bd2 in systemctl_main (bus_error=0, argv=0x7fffeb78, argc=optimized out, bus=0x557d9f70) at ../src/systemctl/systemctl.c:6730 #9 main (argc=optimized out, argv=0x7fffeb78) at ../src/systemctl/systemctl.c:6985 Best, Lorenz -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59.1 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.26.2-3 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod220-1 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17 ii mount 2.26.2-3 ii sysv-rc 2.88dsf-59.1 ii udev215-17 ii util-linux 2.26.2-3 Versions of packages systemd recommends: ii dbus1.8.18-1 ii libpam-systemd 215-17 Versions of packages systemd suggests: pn systemd-ui 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#785601: # rmmod i8k
reassign 785601 src:linux 3.16.7-ckt9-2 affects 785601 src:i8kutils thanks Turns out, disabling i8kmon simply delays the symtoms to later on. The actual symptoms-solver is: # rmmod i8k (for some reason I cannot get blacklisting of i8k to work). hope this help someone else. Since `sensors` does work after `rmmod` I assumes that ACPI has changed in jessie and/or that i8k was not loaded automatically on wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784565: [pkg-x2go-devel] Bug#784565: Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code
Hi Kevin, hi Frederico, On Di 19 Mai 2015 03:16:25 CEST, Kevin Vigor wrote: On 5/18/2015 4:14 PM, Francesco Poli wrote: If it is confirmed that Gian Filippo contributed to the forking of DXPC within the NoMachine project, but not directly to DXPC, then I think that he made his contributions available under the terms of the GPL v2 of the NoMachine project. If this is the case, no feedback should be required from his side. I can confirm that Gian Fillippo never contributed directly to DXPC. You'll note his name does not appear in the DXPC README, and never has. @Kevin: This is again good news for sorting out this issue. Thanks a lot for your help, Kevin. @Frederico: I guess we are through then. Thanks for helping with clarifying the situation (and bringing it up in the first place). For fixing this issue (in terms of closing the bug), I propose this for downstream (i.e., Debian): o copy bug_784565.mbox [1] into the debian/ folder of the nx-libs-lite package o upload some latest release of nx-libs-lite 3.5.0.x to unstable o update debian/copyright accordingly o close this bug via debian/changelog For upstream, I propose this: o copy bug_784565.mbox into the docs/ folder o update copyright information in nxcomp/ subfolder o provide some README or such that shortly explains our last weeks' process o this will be for the upcoming 3.6.x release series of nx-libs o this should also be backported to the 3.5.x release series Once the mbox file and README are upstreamed, I will drop that content from the debian/ folder in the Debian package nx-libs-lite (as it will be in the upstream tarball of nx-libs-lite). Feedback (esp. from Frederico), concerns, other suggestions? Greets, Mike [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?mbox=yes;bug=784565 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpImYGZaEwRe.pgp Description: Digitale PGP-Signatur
Bug#785690: libav-tools: avprobe fail on file with colon in the name
Package: libav-tools Version: 6:0.8.17-1 Severity: normal Dear Maintainer, The avprobe and ffprobe tool fail to open a file with colon in the file name. Here is an example: % ffprobe makercon-2014-10-18T16:22:35.dv avprobe version 0.8.17-6:0.8.17-1, Copyright (c) 2007-2014 the Libav developers built on Mar 15 2015 17:00:31 with gcc 4.7.2 makercon-2014-10-18T16:22:35.dv: No such file or directory % File names without colons do not cause this problem. Can the tool be changed to handle file names with colon in them? -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libav-tools depends on: ii dpkg 1.16.16 ii libavcodec53 6:0.8.17-1 ii libavdevice536:0.8.17-1 ii libavfilter2 6:0.8.17-1 ii libavformat536:0.8.17-1 ii libavutil51 6:0.8.17-1 ii libc62.13-38+deb7u8 ii libpostproc526:0.8.17-1 ii libsdl1.2debian 1.2.15-5 ii libswscale2 6:0.8.17-1 libav-tools recommends no packages. libav-tools 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#785424: [Pkg-virtualbox-devel] Bug#785424: virtualbox: CVE-2015-3456: floppy driver host code execution
Hi Frank, is 4.1.18 affected? cheers, Gianfranco Il Lunedì 18 Maggio 2015 20:36, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, could you also have a look here? https://www.virtualbox.org/ticket/14128#comment:1 This is regarding the 4.3.18 Jessie package. Thanks, Frank On Monday 18 May 2015 16:48:13 Gianfranco Costamagna wrote: Hi sid/testing: - 4.3.28 is not affected (upload pending) -jessie: 4.3.18-dfsg-3+deb8u2 is fixed in git branch jessie, with the upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=jessi eid=990f846aec31871952b839ed93f7963f16bceb0c -wheezy: 4.1.18-dfsg-2+deb7u5 should be fixed in git branch wheezy with the (little changed to remove fuzz and to find the file in the right location) upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=wheez yid=3426d960fc44c86b31d8755717499c83fc127194 I'm rebuilding right now them, sorry for the looong delay in fixing them, upstream only ack'd the patch today, and I was also on VAC for two days. cheers, Gianfranco ___ Pkg-virtualbox-devel mailing list pkg-virtualbox-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-virtualbox-devel -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753401: fonts-dejavu-core: 57-dejavu-sans overrides sans-serif settings in 60-latin.conf
Hi Jan Niklas, On Tue, 01 Jul 2014 16:19:45 +0200 Jan Niklas Hasse jha...@gmail.com wrote: In 57-dejavu-sans.conf DejaVu Sans is set as the default sans-serif font which is redundant IMHO. 60-latin.conf already has a list of fonts to use and the dejavu settings overrides the settings there. This was very confusing for me as I didn't unterstand why the chang in 60-latin.conf didn't have any effect. could you confirm that removing the lines you quoted from 57-dejavu-sans.conf enables the changes in the fontconfig-config shipped 60-latin.conf file to take effect? If this is really the case, we should probably ask fonts-dejavu upstream to remove the offending lines from this config file. Thanks, - Fabian signature.asc Description: This is a digitally signed message part
Bug#779072: RFS: fortune-zh/1.11 [ITA] -- Chinese Data files for fortune
retitle 779072 RFS: fortune-zh/1.11 [ITA] -- Chinese Data files for fortune thanks To access further information about this package, please visit the following URL: http://mentors.debian.net/package/fortune-zh Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/f/fortune-zh/fortune-zh_1.11.dsc Changes since the last upload: fortune-zh (1.11) unstable; urgency=low * New maintainer. (Closes: #629014) * Fix a few characters in tang300. * Add manpage for fortune-zh(6). * Switched to dpkg-source 3.0 (native) format. - debian/source/format * Convert shijing.gb into UTF-8 encoding. * Update description. * Remove dependency on zh-autoconvert, use iconv instead. and specify dependency on libc (=2.1.1) explicitly. - fortune-zh, debian/control * Handle environment LANG properly in fortune-zh. * Update Makefile. I reverted the release of 1.12 and 1.13, and squashed changes into 1.11, since the release of 1.12 and 1.13 is nearly bumping version numbers. I acknowledge that this is dirty in some ways. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785693: debian-installer: Daily-installer fails on debootstrap with err 127
Package: debian-installer Version: 20150519 Severity: important Dear Maintainer, * What led up to the situation? Installing Debian via Daily-installer. Singlepartition, language german on a VM with IDE hdd. * What was the outcome of this action? Installer fails while debootstrap with Err 127. Console shows: main-menu[337]: DEBUG: resolver(libgcc1):package doesnt exist(ignored) main-menu[337]: INFO: Menu item 'bootstrap-base' selected debootstrap: /usr/sbin/debootstrap: debootstrap: line 621: debootstrap: xargs: not found debootstrap: debootstrap: sort: standard output: Broken pipe (Ofc this isnt vital to me, i went via jessie and distupgrade by now, but this seems like something that needs to be fixed) -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (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 Init: systemd (via /run/systemd/system)
Bug#755071: [Pkg-xfce-devel] Bug#755071: evince-gtk still necessary?
Hi again,
Am Donnerstag, den 14.05.2015, 16:13 +0200 schrieb Emilio Pozuelo
Monfort:
Just build evince with
DEB_DH_MAKESHLIBS_ARGS_evince += -X/usr/lib/nautilus/
(or whatever it should be, I'm saying this from memory). That would exclude
the
extension from ${shlibs:Depends}, which means evince won't depend on
libnautilus-extension1a. Since the extension is (I guess) only used by
nautilus
itself, which already links to libnautilus-extension, that should be fine (and
is what we normally do for dlopen'ed extensions).
so, do you think this can be done in the next upload?
- Fabian
(who went washing his fingers after seeing that evince was packaged in
SVN and built using CDBS *g*)
signature.asc
Description: This is a digitally signed message part
Bug#785694: cdrom-detect, isohybrid image fails no common CD-ROM was detected from internal block device
Package: cdrom-detect Version: 1.49 ?jessie Software: debian-8.0.0-amd64-netinst.iso http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-cd/debian-8.0.0-amd64-netinst.iso #D9209F355449FE13DB3963571B1F52D4 Problem: “no common CD-ROM was detected” This issue #588646 seems not fully fixed, for example internal block devices with the isohybrid image written(dd) to it, which are connected directly to the motherboard SATA interface (AHCI or IDE mode) still fail to detect the iso hybrid cdrom image on the same blockdevice, therefor failing the debian installer! It won't matter/helps if its the only single blockdevice connected to the motherboard. Removing the real physical SATA cdrom/dvd drive won't help either still same error message. Expected behaviour: The debian-8.0.0-amd64-netinst.iso must behave the same on a internal blockdevice connected through a internal SATA/PATA/ETC(any mode) controller as on a external blockdevices through a USB controller. A USB connected block device like a pendrive/hdd with the isohybrid image dd't on to it will boot the debian installer and further during the installation process it will detect the cdrom image located on the blockdevice and the installation can finish succesfull. Hardware: *motherboards: ASUS p5k-e-wifi-ap ich9r, Jetway NF9I-2550 ich8m *blockdevices: Kingston SSD 8GB, Hitachi HTS545032B9SA00 *AHCI/IDE mode, different sata ports -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785695: libopusfile-dev: opusfile.h fails to include opus_multistream.h
Package: libopusfile-dev Version: 0.6-1 Severity: normal Dear Maintainer, Line 110 of opusfile.h reads: # include opus_multistream.h However the file opus_multistream.h is provided by libopus-dev and it is not in the include path. It is instead in include/opus, the same as opusfile.h. My proposed solution is to change the above line in # include opus_multistream.h (this is how the other headers in libopus-dev include each other). or # include opus/opus_multistream.h -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopusfile-dev depends on: ii libogg-dev1.3.2-1 ii libopus-dev 1.1-2 ii libopusfile0 0.6-1 Versions of packages libopusfile-dev recommends: ii libssl-dev 1.0.2a-1 libopusfile-dev 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#783788: needrestart: gives false impression of dpkg failure
On Friday 15 May 2015 04:11 AM, Thomas Liske wrote: I've enabled for what you've asked and hope to get the next trigger soon. OK, I'm awaiting your update. I haven't been able to reproduce it yet again. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#785424: [vbox-dev] CVE-2015-3456 aka VENOM
Hi Frank, are you sure the bug is really fixed? the qemu patch seems to be different from the virtualbox one, and seems that the affected code is not fixed http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/block/fdc.c;h=d8a8edd936f42d4b1d801c996932668e456b5896;hp=f72a39216347e722496797555db9f208b0c5b4b2;hb=e907746266721f305d67bc0718795fedee2e824c;hpb=968bb75c348a401b85e08d5eb1887a3e6c3185f5 e.g. https://security-tracker.debian.org/tracker/CVE-2015-3456 http://xenbits.xen.org/xsa/advisory-133.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785696: libv8: newer upstream version that works on arm64
Source: libv8-3.14 Version: 3.14.5.8-8.1 Severity: wishlist Hi, The version of libv8 currently in Debian unstable is very old. It would be nice to have a newer version that works on arm64 so all the dependencies could be built and tested. Obviously you don't want lots of different versions of libv8 in Debian. I looked into the matter a little and am putting what I discovered below in case anyone finds it useful. V8's repo is here: https://chromium.googlesource.com/v8/v8 You can see from the ChangeLog that there is a new version X.Y, with useful but incompatible changes, roughly every 6 weeks. It's currently on 4.5.2. Debian's current package is apparently based on 2012-10-22: Version 3.14.5. The first mention of ARM64 in the ChangeLog is at 2014-03-24: Version 3.25.23. The main user of libv8 in Debian is nodejs, and that presumably explains why Jessie has libv8-3.14 rather than any other version. Node.js's repo is here: https://github.com/joyent/node Node.js includes its own copy of V8 in deps/v8/. Node.js's ChangeLog gives an idea of which versions of V8 correspond to which versions of Node.js. The Debian packages built from nodejs depend on the packages built from libv8-3.14: Debian does not include a separate version of V8 for use by Node.js, though there is, I think, a separate version of V8 bundled with Chrome. Debian's nodejs is currently based on 0.10.38, the latest, and perhaps last, 0.10 release. According to the ChangeLog, Node.js 0.10 was always based on V8 3.14: 0.10.0 is dated 2013.03.11, and 0.10.38 is dated 2015.03.23. So Node.js was using V8 3.14.5 29 months after upstream had finished with it. You can see in Node.js's ChangeLog how various fixes had to be backported. Node.js uses the odd-even convention, so 0.11 is unstable. Node.js's 0.12.0 is dated 2015.02.06, and the latest is 0.12.3, dated 2015.05.13. These are all based on V8 3.28.x. Moreover, I read here (https://github.com/joyent/node/issues/9162) that V8 won't be upgraded past 3.28 for v0.12 because it requires a C++11 capable compiler. So I would guess that if Debian wants to continue having nodejs based on a separate libv8 package then the thing to do is add a libv8-3.28 package and then upgrade nodejs to 0.12.something. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785681: apt-cacher: Infinite loop in ssl_proxy()
Hello, On Tue, 19 May 2015 at 16:32:40, Mark Hindley m...@hindley.org.uk wrote: On Tue, May 19, 2015 at 01:42:23PM +0800, Michael Deegan wrote: Some poking around led to the discovery that ssl_proxy() doesn't appear to notice EOF on the upstream connection, leading to an infinite loop. I added a debugging message (and a sleep :P) inside the main loop, resulting in: Thanks. Does this patch help? It does not...because the socket continues to be at EOF. :P Doing last LOOP instead does work, but makes me wonder uncomfortably whether this would result (under certain currently unspecified and unreproducible circumstances) in the tail end of data from the other socket to be forgotten, though I'm also mindful of the possibility of it being safe to give up as soon as either side becomes unreadable. I feel that doing $s-remove($_) instead (a la the attached patch against 1.7.10) would give the other socket a chance to finish more cleanly. Thanks, -MD apt-cacher-ssl-finite-loops.patch Description: apt-cacher-ssl-finite-loops.patch
Bug#773582: [Pkg-xfce-devel] Bug#773582: xfwm4: Horizontal lines tearing when moving windows or watching video
I have to wait for 4.12 to become available for stable and testing releases first. On 05/17/2015 03:57 PM, Yves-Alexis Perez wrote: Do you still experience this on 4.12? Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785692: SEGFAULT at startup if not in the first PATH directory
Package: yorick Version: 2.2.04+dfsg-1 Severity: important Hi self, when launching Yorick simply as 'yorick', if it is not in the first directory of PATH, then it segfaults. Yorick works fine if it is in the first directory of the PATH and if started with its full path. Regards, self. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yorick depends on: ii debconf 1.5.56 ii libc62.19-18 ii libx11-6 2:1.6.2-3 ii yorick-data 2.2.04+dfsg-1 Versions of packages yorick recommends: ii rlwrap0.41-1 ii yorick-z 1.2.0+cvs20080115-5+b1 Versions of packages yorick suggests: ii curl7.38.0-4+deb8u2 ii emacs23 [emacsen] 23.4+1-4.1+b1 ii emacs24 [emacsen] 24.4+1-5 ii yorick-dbg 2.2.04+dfsg-1 pn yorick-full none pn yorick-mpy-openmpi | yorick-mpy-mpich2 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#785569: Work in progress in personal GitHub fork
2015-05-18 20:46 GMT+01:00 Mathieu Malaterre ma...@debian.org: Hi Ghislain, On Mon, May 18, 2015 at 9:39 PM, Ghislain Vaillant ghisv...@gmail.com wrote: The CUDA backend should be more straightforward. Also, I am not sure whether it is more desirable to build the CUDA backend and have ArrayFire in contrib or stick with just CPU and OpenCL and have it in main. Please keep this package in main. Same thing happen in the past to libthrust. Having a package in contrib or non-free make it non-existant to lots of people. I understand the reasoning, although a significant portion of the scientific crowd still favours CUDA over OpenCL. The case of libthrust is a bit of a non-issue now, since it is a header-only library so no build-deps on non-free components like the CUDA stack. On the other hand, ArrayFire would require the CUDA stack at build time. Just add a quick documentation to README.Debian to build the CUDA backend. 2cts I am only interested in the CPU and OpenCL backend so far. This is a good suggestion to provide the steps to build the CUDA backend from the source package in a README. Since some of the dependencies required to build the OpenCL backend are missing, wouldn't it be worth to submit the CPU backend first and later update the package with the OpenCL binaries ? I am intending to help with packaging clBLAS and clFFT (which Jerome recently started working on I believe), but these new packages will take quite some time to be reviewed and uploaded to the main archive, which would postpone the subsequent availability of ArrayFire in Debian. Additional comments / suggestions welcome :) Ghis
Bug#785424: Re: Bug#785424: [Pkg-virtualbox-devel] Bug#785424: virtualbox: CVE-2015-3456: floppy driver host code execution
Hi Frank, yes I know, I wasn't sure if an update was needeed for wheezy too. I know the bug isn't related to the CVE, in fact I opened 785689 to track it down :) Unfortunately we will need to make another upload for it. cheers, Gianfranco Il Martedì 19 Maggio 2015 10:27, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, ticket https://www.virtualbox.org/ticket/14128 is only about VBox version 4.3.18. No other version is affected by this bug. Note that this has nothing to do with CVE-2015-3456. Kind regards, Frank On Tuesday 19 May 2015 08:20:07 Gianfranco Costamagna wrote: Hi Frank, is 4.1.18 affected? cheers, Gianfranco Il Lunedì 18 Maggio 2015 20:36, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, could you also have a look here? https://www.virtualbox.org/ticket/14128#comment:1 This is regarding the 4.3.18 Jessie package. Thanks, Frank On Monday 18 May 2015 16:48:13 Gianfranco Costamagna wrote: Hi sid/testing: - 4.3.28 is not affected (upload pending) -jessie: 4.3.18-dfsg-3+deb8u2 is fixed in git branch jessie, with the upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=jes si eid=990f846aec31871952b839ed93f7963f16bceb0c -wheezy: 4.1.18-dfsg-2+deb7u5 should be fixed in git branch wheezy with the (little changed to remove fuzz and to find the file in the right location) upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=whe ez yid=3426d960fc44c86b31d8755717499c83fc127194 I'm rebuilding right now them, sorry for the looong delay in fixing them, upstream only ack'd the patch today, and I was also on VAC for two days. cheers, Gianfranco ___ Pkg-virtualbox-devel mailing list pkg-virtualbox-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-virtualbox-dev el -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785681: apt-cacher: Infinite loop in ssl_proxy()
On Tue, May 19, 2015 at 01:42:23PM +0800, Michael Deegan wrote:
Package: apt-cacher
Version: 1.7.10
Severity: normal
Dear Maintainer,
Hello, after adding HTTPS sources (deb https://deb.packager.io/gh/pkgr/gogs
wheezy pkgr)
on a client PC I noticed apt-cacher's CPU usage go through the roof.
Some poking around led to the discovery that ssl_proxy() doesn't appear to
notice EOF on the upstream connection, leading to an infinite loop. I added
a debugging message (and a sleep :P) inside the main loop, resulting in:
Thanks.
Does this patch help?
Mark
commit 4d1675654f73c9e1da808661ea405c3e29f4232e
Author: Mark Hindley m...@hindley.org.uk
Date: Tue May 19 09:30:53 2015 +0100
In ssl_proxy(), sysread returns 0 on EOF.
diff --git a/apt-cacher b/apt-cacher
index 1317c25..f1526e8 100755
--- a/apt-cacher
+++ b/apt-cacher
@@ -455,6 +455,7 @@ sub ssl_proxy {
while (my @pending = $s-can_read($cfg-{request_timeout})) {
foreach (@pending) {
if(defined(my $num=sysread($_, my $buf,65536))) {
+ last unless $num; # EOF
local $SIG{PIPE} = sub {$cfg-{debug} debug_message('Got
SIGPIPE whilst proxying')}; # Catch disconnects/write failure
my $writeto = (fileno($_)==fileno($ssl)?$con:$ssl);
last LOOP if !defined(syswrite($writeto,$buf,$num));
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785240: jessie-pu: package open-iscsi/2.0.873+git0.3b4b4500-8
On Thursday 14 May 2015 12:43 AM, Christian Seiler wrote: Please review and consider this for the next Jessie point release. Ritesh would upload the package upon receiving your ACK. No objections from my point of view. Hello Release Team, We did not hear back. Can you review and ACK the diff ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#785424: Re: [vbox-dev] CVE-2015-3456 aka VENOM
Hi Gianfranco, On Tuesday 19 May 2015 09:17:13 Gianfranco Costamagna wrote: Hi Frank, are you sure the bug is really fixed? the qemu patch seems to be different from the virtualbox one, and seems that the affected code is not fixed http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/block/fdc.c;h=d8a8edd936f42 d4b1d801c996932668e456b5896;hp=f72a39216347e722496797555db9f208b0c5b4b2;hb=e 907746266721f305d67bc0718795fedee2e824c;hpb=968bb75c348a401b85e08d5eb1887a3e 6c3185f5 e.g. https://security-tracker.debian.org/tracker/CVE-2015-3456 http://xenbits.xen.org/xsa/advisory-133.html the VirtualBox code is inherited from Qemu but the code is not the same. Yes, we are sure the bug is fixed in VBox 4.3.28. Kind regards, Frank -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785683: RFS: mod-gnutls/0.6-1.4 [NMU]
Thomas Klute thomas2.kl...@uni-dortmund.de writes: Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for a bugfix update of mod-gnutls that would close bug #775909 (segfaults with reverse proxy configuration). I've uploaded the package to Debian Mentors a few weeks ago. The maintainer has not responded (like for the security updates to 0.5.10-1.1+deb7u1 and 0.6-1.3, which went through the security team, see DSA-3177 [1]), so now I'm looking for a sponsor for an NMU. Hi. I'm using mod-gnutls on some servers, and would like to help. I have never sponsored an upload before, but let me read up on what to do and I'll try to see if it can be done. /Simon * Package name: mod-gnutls Version : 0.6-1.4 Upstream Author : Daniel Kahn Gillmor d...@fifthhorseman.net * URL : https://mod.gnutls.org/ * License : Apache-2.0 Section : httpd It builds those binary packages: libapache2-mod-gnutls - Apache module for SSL and TLS encryption with GnuTLS To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mod-gnutls Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mod-gnutls/mod-gnutls_0.6-1.4.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Fix segfaults with reverse proxy configuration (Closes: #775909) * Upgrade Standards-Version to 3.9.6, change DocumentRoot in default-tls.conf to /var/www/html accordingly. Regards, Thomas Klute [1] https://www.debian.org/security/2015/dsa-3177 signature.asc Description: PGP signature
Bug#784874: Fwd: Bug#784874: mdadm --re-add Segmentation Fault
The raid was a degraded raid 6 array of 5 disks with one missing disk, so only one parity disk, [_] in /proc/mdstat There was a malfunction in the hard drive enclosure so that it momentarily lost contact with the 4 active disks, and then /proc/mdstat said [_], meaning no disks at all. I'm not sure if --re-add is supposed to work in this scenario, however --stop and --assemble worked fine. Thank you for your help! / C On Thu, May 14, 2015 at 8:07 AM, NeilBrown ne...@suse.de wrote: On Wed, 13 May 2015 11:22:47 +0200 Christoffer Hammarström christoffer.hammarst...@linuxgods.com wrote: Yes, i'm sorry, i thoughtlessly ran mdadm --stop /dev/md/storage before reporting the bug. Well that explains some of it. I'd really like to know what the state of the array was when mdadm crashed - that code path should hardly ever be reached. Anyway, the fix is at: http://git.neil.brown.name/?p=mdadm.git;a=commitdiff;h=2609f339028a6035a3fadb1190b565438000e35c in case the Debian maintainer wants to pick it up. Thanks for the report. NeilBrown I managed to reassemble the raid later with --assemble. / C
Bug#785326: libavcodec56: CVE-2014-7937 - Multiple off-by-one errors in libavcodec/vorbisdec.c
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [reformatted] begin quotation from Sebastian Ramacher (in 20150518184906.ga22...@ramacher.at): On 2015-05-18 20:01:47, Alessandro Ghedini wrote: On Sat, May 16, 2015 at 03:43:37PM +0200, Alessandro Ghedini wrote: On Sat, May 16, 2015 at 03:07:57PM +0200, Sebastian Ramacher wrote: On 2015-05-15 15:22:28, Alessandro Ghedini wrote: On Fri, May 15, 2015 at 11:05:17AM +0200, Sebastian Ramacher wrote: On 2015-05-14 20:41:15, Arne Wichmann wrote: Hi, as far as I can see this has not yet been reported or fixed: CVE-2014-7937 : Multiple off-by-one errors in libavcodec/vorbisdec.c in FFmpeg before 2.4.2, as used in Google Chrome before 40.0.2214.91, allow remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted Vorbis I data [1] I marked this as grave as the impact is unclear and might include arbitrary code execution. Feel free do downgrade if this can be ruled out. (Actually I would like to have a look at the test case to check a bit more thoroughly, but AFAICS I would need to talk to google for this.) [1] https://security-tracker.debian.org/tracker/CVE-2014-7937 https://lists.libav.org/pipermail/libav-devel/2015-January/066433.html A similar commit to the one maintained in this mailing list post was applied to 11.3. So closing with that version. Do you mean the patch at [0]? Honestly it doesn't look like the ffmpeg patch at all, and the commit message doesn't even mention the bug fix. How can you be so sure that the bug is fixed? I might have read the commit wrong. Do you have a sample for this CVE? Unfortunately the reproducer isn't public. I contacted ffmpeg-security about it, I'll keep you posted. I got the reproducer from ffmpeg and it seems that libav in sid isn't affected like Sebastian said. So yeah, this bug should stay closed. I don't know if the patch linked above is what fixed the issue though. Great! Thank you for checking. I am not amused about the closedness with that this was handled - but I am very sure that you are not to blame for this. cu AW - -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVWwSMAAoJEENYfBy4DUs+lIEP+wQPZB4LPpuc9IfA94jAfEuy 4NY3lGOcF7EZmMKqD0Ha2xhrO1IINTwT7Ifkz/cseJMnqaibP+7FHC2dFoPgQNYR AabT7oGvT3nsWidFJhlnWS2UlRu2oq2MAS2cvCy4bD98EyOl6CGs+Bnv6ZlUVClM qadtfa+s+xGIfrLVntRP5ZGp+pkcYYQcVFCKnR5KVIuYzA0iryw2tORB4bEV56Bi xwEFFXvCta9z8VQs4D6dnmSvIvLBhcyP5zzSQFrqRNXIxbNHSDNyWxQHy5ACzm8Z 9vAL0wZPv6tpCkjrfYlF6pkewtlcUdlnU7pZObpfXfOnc3qS6SJHLnPe77KSWMQ8 TOqneKXtLH2Py0Vt0PxE/vAP5O6rcDl5ixIsDwcdkYQMBNgUTBTlaFCuK3zVSr0Q s4y7fNoMQ/ruff9L3CNuWLvTtMgzM5HwY+krNvl70ctXj0ah2WZatNvF8D0BQ85C O+p79rxfwNWN5pwL7KxkarppwGktZDF7ekjQeNutZwZ+NccCJaaxOGpUbWPFEcya m4ceYsU3tp+QufOCGv9kGrvuxeI6Hz17xN3+bF2uc6A76/nj3gtjRjghnYtzOPzX Fr6y5Ecd44rxy74nkRYCpcvxfSe63GR7/u4VJwCGJ1D3wygnEAloJxFJHIq3UjEJ xn5UfNHp+Ho4XMVSHUfP =3job -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#785601: blacklist i8k
On Tue, May 19, 2015 at 9:52 AM, Mathieu Malaterre ma...@debian.org wrote: (for some reason I cannot get blacklisting of i8k to work). hope this Neither: $ cat /etc/modprobe.d/i8k-blacklist.conf # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732242 blacklist i8k Nor: $ cat /etc/default/grub [...] GRUB_CMDLINE_LINUX_DEFAULT=quiet i8k.blacklist=yes $ sudo update-grub does seems to work (=blacklist i8k) for me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785687: systemd: systemctl double free or corruption when enabling/disabling sysv units if pwd non-readable
Control: reassign -1 insserv 1.14.0-5 Lorenz Hübschle-Schneider [2015-05-19 9:46 +0200]: systemctl fails to enable/disable sysv units if the current working directory is not readable to the user systemctl is running at (root). In my case, the home directory is mounted via nfs and unreadable to root. gdb output: Synchronizing state for docker.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d docker defaults insserv: popd() can not change directory /home/lorenzhs: Permission denied update-rc.d: error: insserv rejected the script header This is a bug in insserv, reassigning. *** Error in `/bin/systemctl': double free or corruption (fasttop): 0x557da900 *** This is a bug in systemctl indeed, bug already tracked in https://bugs.debian.org/764613 (fixed in experimental, not yet fixed in unstable/jessie). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#785689: I: Bug#785424: [Pkg-virtualbox-devel] Bug#785424: virtualbox: CVE-2015-3456: floppy driver host code execution
Package: virtualbox Severity: Serious Version: 4.3.18-dfsg-3 Tags: patch Virtualbox crashes after 10 minutes of run Il Lunedì 18 Maggio 2015 20:36, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, could you also have a look here? https://www.virtualbox.org/ticket/14128#comment:1 This is regarding the 4.3.18 Jessie package. Thanks, Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785691: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Package: zenity Version: 3.16.2-1 Severity: minor When using zenity, e.g. zenity --info foo I get the following message: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages zenity depends on: ii libc6 2.19-18 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.44.0-3 ii libgtk-3-0 3.14.5-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libwebkitgtk-3.0-0 2.4.8-2 ii libx11-62:1.6.3-1 ii zenity-common 3.16.2-1 zenity recommends no packages. zenity 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#785626: caja: lost preferences after upgrade
Control: tags -1 wontfix Control: close -1 Hi Pol, On Mo 18 Mai 2015 15:09:03 CEST, Pol Hallen wrote: Package: caja Version: 1.8.2-4 Severity: normal Hello, on every upgrade of caja package, the file /usr/share/caja/ui/caja-navigation-window-ui.xml has overwritten thanks Pol As the above referenced file is _not_ a configuration file (in /etc), it will, of course, be overwritten on upgrades. I presume that your are trying to achieve something that people would to with gscheme.override files [1]. Please join #debian-mate on IRC (OFTC, irc.debian.org) to retrieve further help with this. I close this bug with this mail and tag it with the wontfix tag. Mike [1] http://www.burtonini.com/blog/computers/gsettings-override-2011-07-04-15-45 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpZP2j_oLPvT.pgp Description: Digitale PGP-Signatur
Bug#785506: mate-themes: MATE theme changes are not applied on-the-fly anymore.
Control: reassing -1 mate-settings-daemon Control: retitle -1 upload msd (= 1.8.3) to unstable Hi Igor, On So 17 Mai 2015 09:45:37 CEST, Igor Liferenko wrote: Package: mate-themes Version: 1.9.3-1 Severity: normal Dear Maintainer, I installed debian testing build for 11th May 2015 (http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo) That must be the first Debian stretch DVD, right? When in MATE Appearance Preferences dialog (Theme tab) I choose a theme, it is not applied until I re-login. However, in debian testing build for 20th April 2015 the changes were applied on-the-fly. (Unfortunately, I didn't check the releases between these two dates.) That DVD, then, was the last Debian jessie DVD, right? Steps to reproduce: right mouse button click on desktop - Change Desktop Background - Theme - choose any theme I tried dconf-gsettings-backend_0.24.0-1_i386.deb from experimental, but nothing changed. The problem is that we need to update some of the MATE packages (esp. mate-settings-daemon) in unstable to make them work against latest GLib (= 2.43). Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpqHl6iI_rSP.pgp Description: Digitale PGP-Signatur
Bug#784665: Patch for unittest-cpp
ping :) Actually the package doesn't completely work on my package, I suspect some changes are needed. I'll try to work with upstream to merge the changes I need for it... is that ok for you? having a dead upstream makes so many troubles... cheers, G. Il Martedì 12 Maggio 2015 18:41, Loic Dachary l...@debian.org ha scritto: I'd be happy to upload if you tell me to. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773582: [Pkg-xfce-devel] Bug#773582: xfwm4: Horizontal lines tearing when moving windows or watching video
On mar., 2015-05-19 at 11:31 +0300, john wrote: I have to wait for 4.12 to become available for stable and testing releases first. 4.12 is in testing. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#785424: Re: [vbox-dev] CVE-2015-3456 aka VENOM
Hi Debian security team, can we please followup with the two uploads then? I'm attaching the two debdiffs, chers, Gianfranco Il Martedì 19 Maggio 2015 11:27, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, On Tuesday 19 May 2015 09:17:13 Gianfranco Costamagna wrote: Hi Frank, are you sure the bug is really fixed? the qemu patch seems to be different from the virtualbox one, and seems that the affected code is not fixed http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/block/fdc.c;h=d8a8edd936f42 d4b1d801c996932668e456b5896;hp=f72a39216347e722496797555db9f208b0c5b4b2;hb=e 907746266721f305d67bc0718795fedee2e824c;hpb=968bb75c348a401b85e08d5eb1887a3e 6c3185f5 e.g. https://security-tracker.debian.org/tracker/CVE-2015-3456 http://xenbits.xen.org/xsa/advisory-133.html the VirtualBox code is inherited from Qemu but the code is not the same. Yes, we are sure the bug is fixed in VBox 4.3.28. Kind regards, Frank -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher jessie-debdiff Description: Binary data wheezy-debdiff Description: Binary data
Bug#785702: [Pkg-anonymity-tools] Bug#785702: onionshare: Please consider downgrading the Depends: torbrowser-launcher to Recommends
Hi, intrig...@debian.org: Package: onionshare Version: 0.6-3 Severity: normal User: tails-...@boum.org Usertags: p2p Hi, previously, onionshare had Suggests: torbrowser-launcher, and commit e008b41 switched it to Depends (among a few other packaging changes) without any more explanation than new upstream release 0.6. I've not tried it myself yet, but it seems to me that OnionCat should be perfectly able to use a system-wide Tor instance (e.g. as provided by the tor Debian package). More specifically, I see that it tries both ports 9051 and 9151 when trying to get in touch with Tor's control port. If my rough guess is correct, then Depends: torbrowser-launcher is not correct, and possibly a mere Recommends (or even Suggests?) would be enough. Of course one will need to actually test that before acting on it, hence the normal severity for now, even if that might be a policy violation technically. Note that the current Depends: relationship is one of the blockers for including OnionCat in Tails, as we don't ship TBL in there. Thanks for pointing this out! Yes it should be able to use system tor, however, currently it does not do that correctly: it does not accept a hashed password for the ControlPort from what I've seen. Waiting for some input from the upstream developer on this issue. However, this should work and thus I'll modify the dependency for version 0.7. Cheers! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739399: (no subject)
Same probleme here: /etc/cron.daily/welcome2l: Failed to open /dev/tty: Device o indirizzo non esistente -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711757: [PATCH] Wired connection, static IP profile: immediately disconnects
Package: wicd Version: 1.7.2.4-4.1 Severity: normal Apparently the wired connection process is too fast in setting the ip address and issuing an update_connection_status() . When using a static ip the function CheckPluggedIn() in wicd_daemon.py initially returns a 0 even if the cable is connected and the ip properly set: I believe that is due to some kind of delay having put the interface down and then up before connecting and the extra time dhcp takes to get/set an address could explain why the issue is not present when not using static IPs. As a patch/workaround I added a time.sleep(1) at the beginning of check_for_wired_connection() and now everything works like a charm if you don't mind the extra second delay, of course. Here is the update_connection_status() in monitor.py: def check_for_wired_connection(self, wired_ip): Checks for a wired connection. Checks for two states: 1) A wired connection is not in use, but a cable is plugged in, and the user has chosen to switch to a wired connection whenever its available, even if already connected to a wireless network. 2) A wired connection is currently active. time.sleep(1) self.trigger_reconnect = False if not wired_ip and daemon.GetPreferWiredNetwork(): if not daemon.GetForcedDisconnect() and wired.CheckPluggedIn(): self.trigger_reconnect = True elif wired_ip and wired.CheckPluggedIn(): # Only change the interface if it's not already set for wired if not self.still_wired: daemon.SetCurrentInterface(daemon.GetWiredInterface()) self.still_wired = True return True # Wired connection isn't active elif wired_ip and self.still_wired: # If we still have an IP, but no cable is plugged in # we should disconnect to clear it. wired.DisconnectWired() self.still_wired = False return False The issue is here: elif wired_ip and wired.CheckPluggedIn() -- it is not verified because of wired.CheckPluggedIn() returning 0 before settling to 1. Mattia Belluco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785702: [Pkg-anonymity-tools] Bug#785702: Bug#785702: onionshare: Please consider downgrading the Depends: torbrowser-launcher to Recommends
u wrote (19 May 2015 10:51:34 GMT) : Yes it should be able to use system tor, however, currently it does not do that correctly: it does not accept a hashed password for the ControlPort from what I've seen. As said elsewhere already, and just so that this bug report has current info: the default control port+socket tor config in Debian lives in /usr/share/tor/tor-service-defaults-torrc, and doesn't use a hashed password, so IMO that's orthogonal to the problem at hand. What needs to be tested instead is onioncat with the default configuration of the system-wide tor daemon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785706: Uninstallable build-dep apache2-mpm-worker
Source: 389-admin Version: 1.1.35-4 Justification: fails to build from source (but built successfully in the past) Severity: serious Hello Your package 389-admin used to build-depend on transitionnal package apache2-mpm-worker. This was still kind of ok in Jessie, but now that package is no longer built by apache2. Please remove the build-dependency. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785697: clang-3.6: Clang++ does not find standard include files, e.g. iostream
Package: clang-3.6 Version: 1:3.6-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Latest apt-get update/apt-get upgrade/Installation of gcc-5 (I think) * What exactly did you do (or not do) that was effective (or ineffective)? Project, which compiled before the upgrade perfectly now bails out with main.cpp:1:10: fatal error: 'iostream' file not found. gcc toolchain still works as expected. * What was the outcome of this action? main.cpp:1:10: fatal error: 'iostream' file not found. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, armhf Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages clang-3.6 depends on: ii binutils 2.25-7 ii libc62.19-18 ii libc6-dev2.19-18 ii libclang-common-3.6-dev 1:3.6-2 ii libclang1-3.61:3.6-2 ii libedit2 3.1-20150325-1 ii libffi6 3.1-2+b2 ii libgcc-4.9-dev 4.9.2-17 ii libgcc1 1:5.1.1-5 ii libllvm3.6 1:3.6-2 ii libobjc-4.9-dev 4.9.2-17 ii libstdc++-4.9-dev4.9.2-17 ii libstdc++6 5.1.1-5 ii libtinfo55.9+20140913-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages clang-3.6 recommends: ii llvm-3.6-dev 1:3.6-2 ii python2.7.9-1 Versions of packages clang-3.6 suggests: pn clang-3.6-doc none pn gnustepnone pn gnustep-devel 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#785698: RM: node-in2 -- ROM; no longer used anywhere in Debian
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As subject says, please drop node-ain2 from unstable, as it is no longer used anywhere in Debian. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVWwZBAAoJECx8MUbBoAEhB/0P/iQBR3KCbkH1ovS2y/dCDYp1 1b54JL/oeOlaN5INWYs/+8BWaKY1jOI/1mZIzYdGO5ueT5dWT1i+fvLFqzspFMKh 4cV9/FCU7aA40y0/o+5xxRs/HzFj4sNWgbo2VP4lzJmyKtvLyx3sjcw6ZRP8P3n1 3hGP6JbSmWvP3nx6cn+MJnmn8P/VhO1f6zWm+Xk5VcjF3MFdE+lIVhN31jdCZ4Yu wvGN18pULSoadDeSf0BKWuAoywHOYIjoJReLiWefjvtVCc5Z8gNCPKonp13uh5eO YDVWYPm1CWyQ0M3Qq7rznZu9NFTHnnM2fbpXRgxKaWlPcgFmgSBEso+TWfdbNUgU m+N28sXleMgqyzXNCj6O2HCxo38A7pE8N8pMTZDRtwhBrSLB/mAxODaXB5Pyd0lE s7hJ33lImm3paQaMEdB3YnUXUmMZm/26iIBkR+1yY/EaJxREmQjACsUAjH9tfUD8 jES+8XgVr7/jqP3WC8YYksn9WbNbwF+U/L97GxNLvqLpIvtTcLARckUUlLxPouMu tREMYsrae66mqvJ3vVE0AoF4Vc5HShjjitkuzf367NOVkb6SIBbeAwGBjk8/M3Em XWZUpFHNqMpP5jscMQJy/gFpcla+89yw5/Qe9a8OX3BMNAlP4x3BFaJCVwmiJQhx IUi0l5IJ9nik5MvCcoPR =ZkY1 -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#785700: RM: node-underscore.logger -- ROM; no longer used anywhere in Debian
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As subject says, please drop node-underscore.logger (i.e. src:underscore.logger) from unstable, as it is no longer used anywhere in Debian. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVWwdEAAoJECx8MUbBoAEhkvUP/0jeQttjpFh7uDGmhSfL5WrU 4LHUK1N0O5ciSpcrqPgxNTU1zuX/Cjrjhhaet76ko7pSGall+SqXDagtispqCUJx N1UuAqa5PX07n2sagr4n7zhY1e+Ppmp9vHmb32vKasrMA5szvIw8FnluUwwvzyGe ZzCdhfajz3XbDRKAAnSQhX91eGraOw32/l2jbntKLsOJG+12pks6I0sCmUJoy+6m DKT+5zLQKVsZLUU1yBMDFbOkdtA360bkTlCmfvs55P+g0hTKlbJplLKxcIr7Qt3B W9UIhPME1rjZrD1v6z63wlDJS9w5aZfZCaliCmcgCBSOaDX/8vSI8bSHq9JPopxE B94ZpZq3ivmnN4M3/hlUxpJm1u/OEAdRRA7S7ob3S644HVlrlw0TlkPRkLj6nU+H cF6isr1pw1zBrHq2T64VuebvJYlfvfMB1Xdo+x6XmQNMnICf8MK0QCpnjrBa1PKI BOC8bbD3kbON0qpXql/g+S8NGVIQYBFHI6saCUG9BVyFTVbNl50YGvgal7iIeYEa E6T+2DWIPP+DS3RLDSHoJmQon97yolvR4zRExEiId7DdnvdC1XvstNp4ybW3LACo U5HdVBJr88Q+Y/OLzxkmTD0aWit5KelyuY7GXEyqVTYTIun8zSOd1eQDAsOCXyO/ C2qhqyhgdsNZ+d6EMver =FM4k -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#785690: libav-tools: avprobe fail on file with colon in the name
Control: found -1 6:11.3-1 I tested again in Jessie, and now I get this error instead: % avprobe makercon-2014-10-18T16:49:26.dv avprobe version 11.3-6:11.3-1, Copyright (c) 2007-2014 the Libav developers built on Mar 13 2015 23:08:20 with gcc 4.9.2 (Debian 4.9.2-10) makercon-2014-10-18T16:49:26.dv: Protocol not found # avprobe output % -- 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#785514: RFS: ming/1:0.4.7-1 [RC]
On Mon, May 18, 2015 at 06:03:48PM -0700, Vincent Cheng wrote:
On Mon, May 18, 2015 at 4:51 PM, Gabriele Giacone 1o5g4...@gmail.com wrote:
On Sun, May 17, 2015 at 08:41:02PM -0700, Vincent Cheng wrote:
[1] https://github.com/libming/libming/issues/42
I've just updated the list few hours ago, just 2 missing contributors, 4
commits. Not sure that commits in question are legally significant and
can block relicensing. Opinions? [also CC'ing d-legal]
IANAL, so my opinion doesn't actually matter. :)
If you want an authoritative yes/no regarding whether this is legally
acceptable or not, debian-legal is the wrong place; you should be
asking the ftpmasters directly instead.
I don't actually know anything about ming (and the Debian ming
packages); are php_ext/ming.{c,h} actually used to build the binary
packages? Can they be removed just like java_ext?
They can, they are both extensions but php one is packaged as php5-ming
(java_ext is not) and its popcon is around 2000.
https://qa.debian.org/popcon.php?package=ming
[ CC'ing ftpmaster@d.o ]
Hi ftpmasters,
question is: Ming PHP extension (see #752629) has been relicensed in
both upstream git repo and latest tarballs released few days ago. Should
Debian be concerned about upstream contributors who haven't expressed
any agreement (yet) with license change?
Thanks for your time.
--
G..e
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785699: RM: node-jsconfig -- ROM; no longer used anywhere in Debian
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As subject says, please drop node-jsconfig from unstable, as it is no longer used anywhere in Debian. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVWwasAAoJECx8MUbBoAEhjBAP/38e1K84ml+XxytHW1kk30m7 GCcgeeczr69DBlRhaT+YNQNpt/y9JVkYxSm5/H0hGTuF5RJK5wMgl8MctzwhoCzt P2yHBTkSJWuSW1hvOB5pPv4Dtk7+cqu1sT6q/bdRY/9hnmYyGfByPMyqrwahrLWZ Mv8PdS2UNxVd0Q6MxBHA7BclWqQdcJDCh5UTbfhgO9eoJgCgLHralZeBzjDaIqSG OLIU0fa99fP4k6toxoEDLkvBVidNlbZPm4l4lyiICrshvsDTyQTAccBBezY1mDFR tqLu/4EjYFAgOoF79BZvF1KXPpwdxGsB9ICd5IfBs1qvJ/p5ajKObizf8um355CB VM6nrKN7NYeGZwJJILubUyyRYs2hsTAFRvXDsmoP8TY1AjgR79nmIf2qxt0oNw5r uM/MocQT95lWcEjbEYHK0xuBKtCaJ5ZgbUBPAT28PeCKW85sDCak0X9YgT2W2X8N +hfDPX/6pgBRZuGLxswNxtzeHoftsaOwyvJpPnmjlpS9TBGB33fE8m3rLSBmsEVi eKPk7/+AbYe7H2EzEwXd6b9+Ta9C0M0r3nOoXXYpSBNu+C6RWnS082MMGpgzvkMy syFiGCAkO1Xbs23jcj/v3hOkpGSe1SUiCBXFgI/rkDLHe3gVSLCqwWCmRCnmr9a1 q9tA4jDj7bDnQw3S0gDT =fZRo -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#773229: [PATCH] Skip eMMC partition checking
Hi, I've just made a patch to solve the emmc partition issue during installation. Could you kindly help review this? Thank you. BugLink: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1456443 Index: partman-base-172ubuntu1/init.d/parted === --- partman-base-172ubuntu1.orig/init.d/parted 2014-02-05 22:50:17.0 +0800 +++ partman-base-172ubuntu1/init.d/parted 2015-05-19 12:08:13.878119958 +0800 @@ -93,6 +93,11 @@ continue fi + # Skip emmc devices' boot0, boot1 and rpmb partitions + if echo $device | grep -q -e '/dev/mmcblk0\(rpmb\|boot\)'; then + continue + fi + # Skip MD devices which are not active if [ -e /proc/mdstat ]; then if is_inactive_md $device; then
Bug#785701: libmodule-signature-perl: option --skip not working
Package: libmodule-signature-perl Version: 0.68-1+deb7u2 Severity: normal Dear Maintainer, the latest security updates (#783451) introduced a change in the handling of files/directories in a MANIFEST.SKIP file. Previously, files/directories in MANIFEST.SKIP are not checked by default (cpansign -v). Now, all files are checked. There is a --skip option that prevents cpansign from checking files/directories in MANIFEST.SKIP, but upstream missed to change the logic for parsing the option in cpansign after changing the default. I send a patch to upstream and this is fix in 0.79: https://github.com/audreyt/module-signature/commit/6e1b7d3 Please integrate the patch to let cpansign behave like before the security updates by additionally use the --skip option. Chris -- System Information: Debian Release: 7.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-042stab092.3 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages libmodule-signature-perl depends on: ii perl 5.14.2-21+deb7u2 Versions of packages libmodule-signature-perl recommends: ii gnupg 1.4.12-7+deb7u7 libmodule-signature-perl 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#785702: onionshare: Please consider downgrading the Depends: torbrowser-launcher to Recommends
Package: onionshare Version: 0.6-3 Severity: normal User: tails-...@boum.org Usertags: p2p Hi, previously, onionshare had Suggests: torbrowser-launcher, and commit e008b41 switched it to Depends (among a few other packaging changes) without any more explanation than new upstream release 0.6. I've not tried it myself yet, but it seems to me that OnionCat should be perfectly able to use a system-wide Tor instance (e.g. as provided by the tor Debian package). More specifically, I see that it tries both ports 9051 and 9151 when trying to get in touch with Tor's control port. If my rough guess is correct, then Depends: torbrowser-launcher is not correct, and possibly a mere Recommends (or even Suggests?) would be enough. Of course one will need to actually test that before acting on it, hence the normal severity for now, even if that might be a policy violation technically. Note that the current Depends: relationship is one of the blockers for including OnionCat in Tails, as we don't ship TBL in there. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785225: how to manually update
Hello, how do you manually update to 460? thanks for your answer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785703: ITP: python-oath -- implementation of the three main OATH specifications
Package: wnpp Severity: wishlist Owner: Goswin von Brederlow brede...@q-leap.de * Package name: python-oath Version : 1.4.0 Upstream Author : Benjamin Dauvergne benjamin.dauver...@gmail.com * URL : https://github.com/bdauvergne/python-oath * License : BSD Programming Lang: Python Description : implementation of the three main OATH specifications Oath includes 3 modules implementing the three main OATH specifications: - HOTP, an event based one-time password standard using HMAC signatures, - TOTP, a time based OTP, - OCRA, a mixed OTP / signature system based on HOTP for complex use cases. Supports python 2.x and python 3.x. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785704: mps-youtube: package needs update from upstream, versions 0.2.4 not functional with current youtube API
Package: mps-youtube Version: 0.01.46-3 Severity: important mps-yt is a very practical tool for vision-impaired or blind computer users in order to find and convert videos from the youtube platform. Unfortunately, because of a change in youtubes API, the version 0.01.46 ceases to function, completely, and displays the youtube your client is not supported video on all requests. There is a new upstream maintainer for the project who, due to reports in the projects forum, has already adapted the new API to mps-yt, so version 0.2.4 will work again. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 4.0.0-64 (SMP w/2 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 Versions of packages mps-youtube depends on: ii mpv 1:0.7.1-dmo2 Free and open-source general-purpo ii python 2.7.9-1 interactive high-level object-orie ii python-pafy 0.3.62-1 Download videos and retrieve metad mps-youtube recommends no packages. mps-youtube suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785705: linux-image-3.16.0-0.bpo.4-amd64: kernel NULL pointer oops in r8169 realtek driver rtl8169_poll
Package: src:linux Version: 3.16.7-ckt9-3~deb8u1~bpo70+1 Severity: important Hi, Kernel crashed with NULL pointer into an Oops. Last things I did when I got this triggered: 1) Battery on laptop went very low (critical: red mark) 2) I plugged in power chord 3) Let around 1 minute with power chord in to charge 4) I plugged in via USB my tablet in order to charge its battery 5) Laptop went into stand by mode 6) I waited until it settled into stand by 7) Activated to exit stand by, by pressing the power button 8) It booted back to the login screen (NOTE: 1/3 of the screen was black) 9) TRIGGER: after I typed in my password to login the oops occured Please also check the attached screenshot for the full Oops. Thanks in advance, Alex -- Package-specific info: ** Version: Linux version 3.16.0-0.bpo.4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1~bpo70+1 (2015-04-27) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-amd64 root=UUID=206d4688-79d7-45d9-8d1d-f2e8e8674962 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 12.369331] lis3lv02d: 8 bits 3DC sensor found [ 12.423384] [drm] Memory usable by graphics device = 2048M [ 12.423387] [drm] Replacing VGA console driver [ 12.424486] Console: switching to colour dummy device 80x25 [ 12.424870] [drm] ACPI BIOS requests an excessive sleep of 5000 ms, using 1500 ms instead [ 12.434143] tpm_tis 00:05: TPM is disabled/deactivated (0x7) [ 12.446214] i915 :00:02.0: irq 66 for MSI/MSI-X [ 12.446226] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 12.446228] [drm] Driver supports precise vblank timestamp query. [ 12.446273] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 12.471616] [drm] VBT doesn't support DRRS [ 12.505088] fbcon: inteldrmfb (fb0) is primary device [ 12.514154] ACPI: Battery Slot [BAT0] (battery present) [ 12.514648] wmi: Mapper loaded [ 12.778892] input: PC Speaker as /devices/platform/pcspkr/input/input13 [ 12.950498] cfg80211: Calling CRDA to update world regulatory domain [ 13.143984] AVX2 version of gcm_enc/dec engaged. [ 13.145495] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 13.160117] alg: No test for crc32 (crc32-pclmul) [ 13.583585] rtl8723be: Using firmware rtlwifi/rtl8723befw.bin [ 13.583913] psmouse serio3: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1e0b1, caps: 0xf00173/0x64/0xa2400, board id: 2654, fw id: 1323623 [ 13.594899] Console: switching to colour frame buffer device 200x56 [ 13.597757] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 13.597758] i915 :00:02.0: registered panic notifier [ 13.620802] intel_rapl: Found RAPL domain package [ 13.620806] intel_rapl: Found RAPL domain core [ 13.620808] intel_rapl: Found RAPL domain uncore [ 13.620810] intel_rapl: Found RAPL domain dram [ 13.620940] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio3/input/input12 [ 13.670763] rtl8723be :09:00.0: firmware: direct-loading firmware rtlwifi/rtl8723befw.bin [ 13.706954] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input15 [ 13.723357] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 13.725194] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16 [ 13.725279] [Firmware Bug]: ACPI(DGFX) defines _DOD but not _DOS [ 13.725456] ACPI: Video Device [DGFX] (multi-head: yes rom: no post: no) [ 13.725522] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:40/LNXVIDEO:01/input/input17 [ 13.725569] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 13.725998] snd_hda_intel :00:1b.0: irq 67 for MSI/MSI-X [ 13.733327] snd_hda_intel :00:03.0: irq 68 for MSI/MSI-X [ 13.835116] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [ 13.839133] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 13.839349] rtlwifi: wireless switch is on [ 13.891296] sound hdaudioC1D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 13.891299] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.891301] sound hdaudioC1D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 13.891302] sound hdaudioC1D0:mono: mono_out=0x0 [ 13.891303] sound hdaudioC1D0:inputs: [ 13.891304] sound hdaudioC1D0: Mic=0x19 [ 13.891306] sound hdaudioC1D0: Internal Mic=0x12 [ 13.898098] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input19 [ 13.898150] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input20 [ 13.898198] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input21 [ 13.898281] input: HDA Digital PCBeep as
Bug#785424: Re: Bug#785424: [Pkg-virtualbox-devel] Bug#785424: virtualbox: CVE-2015-3456: floppy driver host code execution
Hi Gianfranco, ticket https://www.virtualbox.org/ticket/14128 is only about VBox version 4.3.18. No other version is affected by this bug. Note that this has nothing to do with CVE-2015-3456. Kind regards, Frank On Tuesday 19 May 2015 08:20:07 Gianfranco Costamagna wrote: Hi Frank, is 4.1.18 affected? cheers, Gianfranco Il Lunedì 18 Maggio 2015 20:36, Frank Mehnert frank.mehn...@oracle.com ha scritto: Hi Gianfranco, could you also have a look here? https://www.virtualbox.org/ticket/14128#comment:1 This is regarding the 4.3.18 Jessie package. Thanks, Frank On Monday 18 May 2015 16:48:13 Gianfranco Costamagna wrote: Hi sid/testing: - 4.3.28 is not affected (upload pending) -jessie: 4.3.18-dfsg-3+deb8u2 is fixed in git branch jessie, with the upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=jes si eid=990f846aec31871952b839ed93f7963f16bceb0c -wheezy: 4.1.18-dfsg-2+deb7u5 should be fixed in git branch wheezy with the (little changed to remove fuzz and to find the file in the right location) upstream patch http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=whe ez yid=3426d960fc44c86b31d8755717499c83fc127194 I'm rebuilding right now them, sorry for the looong delay in fixing them, upstream only ack'd the patch today, and I was also on VAC for two days. cheers, Gianfranco ___ Pkg-virtualbox-devel mailing list pkg-virtualbox-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-virtualbox-dev el -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785187: [Pkg-xen-devel] Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: Here's an idea. First extract the real initrd from the back half of the initrd: ijc@dagon:tmp$ cat /boot/initrd.img | ( cpio -t 2 ; cat ) initrd.real kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/GenuineIntel.bin 16 blocks ijc@dagon:tmp$ file initrd.real initrd.real: gzip compressed data, last modified: Sun Apr 19 16:31:17 2015, from Unix ijc@dagon:tmp$ zcat initrd.real | cpio -t | head -n 5 . etc etc/ld.so.conf.d etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf etc/ld.so.conf.d/x86_64-linux-gnu.conf Now you can experiment with regenerating the ucode bit with whatever commands are recommended and reconcatenating the two. If that works then we know there is some incompatibility between iucode-tools's output and Xen's cpio reader (could be a bug in either or both I think). All right. Can you please provide some commands how to create and reconcatenate the two initrds? I don’t have any experience with cpio. Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: s...@fsing.rootsland.net | | Public Keys: http://fsing.rootsland.net/~stse/keys.html | smime.p7s Description: S/MIME cryptographic signature
Bug#785690: libav-tools: avprobe fail on file with colon in the name
Hi Petter, Quoting Petter Reinholdtsen (2015-05-19 12:24:45) Control: found -1 6:11.3-1 I tested again in Jessie, and now I get this error instead: % avprobe makercon-2014-10-18T16:49:26.dv avprobe version 11.3-6:11.3-1, Copyright (c) 2007-2014 the Libav developers built on Mar 13 2015 23:08:20 with gcc 4.9.2 (Debian 4.9.2-10) makercon-2014-10-18T16:49:26.dv: Protocol not found # avprobe output Deep down in the manpage for avprobe is mentioned that input isn't really bare filename but a URL, defaulting to file: protocol. Therefore a filename foo:bar is treated as resource bar via protocol foo. To use filenames with colon you can explicitly state protocol as file:foo:bar. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#785690: libav-tools: avprobe fail on file with colon in the name
Control: severity -1 wishlist [Jonas Smedegaard] Hi Petter, Hi, Jonas. Thank you for the quick reply. Deep down in the manpage for avprobe is mentioned that input isn't really bare filename but a URL, defaulting to file: protocol. Therefore a filename foo:bar is treated as resource bar via protocol foo. To use filenames with colon you can explicitly state protocol as file:foo:bar. Right. I did not know that. Then I guess what I am asking for is a nicer fallback when the protocol is unknown and the string matches an existing file name. In that case, I believe it make more sense to open the file instead of giving an error about an unknown protocol. It would for me be more according to the principle of least surprise. And I am happy to report that my problem indeed is solved by adding file: in front of the file name: % avprobe file:makercon-2014-10-18T16:49:26.dv avprobe version 11.3-6:11.3-1, Copyright (c) 2007-2014 the Libav developers built on Mar 13 2015 23:08:20 with gcc 4.9.2 (Debian 4.9.2-10) [dv @ 0x17abd20] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'file:makercon-2014-10-18T16:49:26.dv': Duration: 00:01:00.84, start: 0.00, bitrate: 28800 kb/s Stream #0.0: Video: dvvideo, yuv420p, 720x576, 28800 kb/s, PAR 64:45 DAR 16:9, 25 fps, 25 tbn Stream #0.1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s # avprobe output % -- 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#785187: [Pkg-xen-devel] Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: Here's an idea. First extract the real initrd from the back half of the initrd: ijc@dagon:tmp$ cat /boot/initrd.img | ( cpio -t 2 ; cat ) initrd.real kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/GenuineIntel.bin 16 blocks ijc@dagon:tmp$ file initrd.real initrd.real: gzip compressed data, last modified: Sun Apr 19 16:31:17 2015, from Unix ijc@dagon:tmp$ zcat initrd.real | cpio -t | head -n 5 . etc etc/ld.so.conf.d etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf etc/ld.so.conf.d/x86_64-linux-gnu.conf Now you can experiment with regenerating the ucode bit with whatever commands are recommended and reconcatenating the two. If that works then we know there is some incompatibility between iucode-tools's output and Xen's cpio reader (could be a bug in either or both I think). All right. Can you please provide some commands how to create and reconcatenate the two initrds? I don’t have any experience with cpio. The reconcatenate bit is easy, just: $ cat initrd.ucode initrd.real initrd.img With initrd.real extracted above. initrd.ucode creation I'm a little unsure about but something like: $ mkdir initrd.ucode.tree $ cd initrd.ucode.tree $ cat /boot/initrd.img | cpio -id $ find . ./kernel ./kernel/x86 ./kernel/x86/microcode ./kernel/x86/microcode/GenuineIntel.bin $ find | cpio -o -H newc ../initrd.ucode Is what I think is required/expected. BTW, could you please post the output xl dmesg for the failing case, I should have asked for that right at the start in case it contains anything of use. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783610: Processed: [bts-link] source package libxml-libxml-perl
Control: tags -1 - wontfix
Control: tags -1 + patch
On 2015-05-07 16:51:34 +, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
#
# bts-link upstream status pull for source package libxml-libxml-perl
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was
bts-link-de...@lists.alioth.debian.org).
# remote status report for #783610 (http://bugs.debian.org/783610)
# Bug title: Warning: XML::LibXML compiled against libxml2 20902, but
runtime libxml2 is older 20901
# * http://rt.cpan.org/Public/Bug/Display.html?id=104156
# * remote status changed: (?) - rejected
# * upstream said bug is wontfix
[...]
Upstream rejected the bug because it assumed that Debian's weak
dependency was wrong. So, either Debian follows upstream and uses
a stronger dependency, or Debian should ignore what upstream is
saying here. In any case, if there is a version test in XML::LibXML,
it must be consistent with the dependency constraint from the binary
package.
Anyway, while tests like that may be useful in environments without
checks on symbol versioning, such a test is useless when the packages
are provided by a binary distribution with versioned dependencies,
like in Debian. I've attached a patch that disables the test entirely.
--
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- a/LibXML.pm 2015-05-19 12:20:11.0 +0200
+++ b/LibXML.pm 2015-05-19 12:22:54.908174164 +0200
@@ -217,17 +217,6 @@
# our $__PROXY_NODE_REGISTRY = XML::LibXML::HashTable-new();
# }
-#-#
-# test exact version (up to patch-level) #
-#-#
-{
- my ($runtime_version) = LIBXML_RUNTIME_VERSION() =~ /^(\d+)/;
- if ( $runtime_version LIBXML_VERSION ) {
-warn Warning: XML::LibXML compiled against libxml2 .LIBXML_VERSION.
- , but runtime libxml2 is older $runtime_version\n;
- }
-}
-
#-#
# parser flags#
Bug#785701: libmodule-signature-perl: option --skip not working
Hi Christian, On Tue, May 19, 2015 at 12:11:31PM +0200, Christian Loos wrote: Package: libmodule-signature-perl Version: 0.68-1+deb7u2 Severity: normal Dear Maintainer, the latest security updates (#783451) introduced a change in the handling of files/directories in a MANIFEST.SKIP file. Previously, files/directories in MANIFEST.SKIP are not checked by default (cpansign -v). Now, all files are checked. There is a --skip option that prevents cpansign from checking files/directories in MANIFEST.SKIP, but upstream missed to change the logic for parsing the option in cpansign after changing the default. I send a patch to upstream and this is fix in 0.79: https://github.com/audreyt/module-signature/commit/6e1b7d3 Please integrate the patch to let cpansign behave like before the security updates by additionally use the --skip option. Yes indeed this is a problem. I'm uploading a fixed version for unstable now first. Thanks for your report! 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#783357: closed by Matteo F. Vescovi m...@debian.org (Re: Wrong keyboard layout used for shortcuts if multiple layouts available)
Hi Mateo, I'm sorry but I don't understand what makes you say that this is not a bug report. In my opinion, the way Inkscape reacts to multiple keyboard layouts is not what is expected. Moreover, I could not find anything about this behaviour in the documentation, this is why I think that this is indeed a bug. If there is not enough information in this bug or if I am not clear, please ask. And if you think this should be reported upstream, I can do it if you wish. Regards, Yvan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785707: Add USB support for APM Mustang
Package: src:linux
Version: 3.16.7-ckt9-2
Severity: normal
Tags: d-i patch
Hi folks,
As described a little at
http://blog.einval.com/2015/05/19#mustang_installer I've been working
on getting Mustang support working. There's a (quite generic!) patch
from Mark Langsdorf for the XHCI platform code that allows for a
64-bit DMA mask:
http://www.spinics.net/lists/arm-kernel/msg373699.html
AFAICS this is needed for the Mustang, as all of its memory is mapped
over 4GiB. The patch hasn't (yet!) been accepted upstream, but I've
swapped mail with Mark and he says he's about to propose it again this
week. With the small attached patch applied to the Jessie kernel
(Mark's code plus a config tweak), I've got things working just fine.
It would be lovely if we could get this into Jessie for the 8.1 point
release. :-)
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru linux-3.16.7-ckt9/debian/changelog linux-3.16.7-ckt9/debian/changelog
--- linux-3.16.7-ckt9/debian/changelog 2015-04-13 01:01:55.0 +
+++ linux-3.16.7-ckt9/debian/changelog 2015-05-15 08:47:00.0 +
@@ -1,3 +1,10 @@
+linux (3.16.7-ckt9-2.1) unstable; urgency=medium
+
+ * arm64: enable XHCI USB on APM X-Gene
+ * usb: host: allow 64-bit DMA mask for XHCI
+
+ -- Steve McIntyre 93...@debian.org Fri, 15 May 2015 09:41:31 +0100
+
linux (3.16.7-ckt9-2) unstable; urgency=medium
* btrfs: simplify insert_orphan_item (Closes: #782362)
diff -Nru linux-3.16.7-ckt9/debian/config/arm64/config linux-3.16.7-ckt9/debian/config/arm64/config
--- linux-3.16.7-ckt9/debian/config/arm64/config 2015-01-02 03:46:07.0 +
+++ linux-3.16.7-ckt9/debian/config/arm64/config 2015-05-15 08:54:05.0 +
@@ -120,6 +120,8 @@
CONFIG_USB_EHCI_HCD_PLATFORM=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_HCD_PLATFORM=m
+CONFIG_USB_XHCI_HCD=m
+CONFIG_USB_XHCI_PLATFORM=y
##
## file: drivers/virtio/Kconfig
diff -Nru linux-3.16.7-ckt9/debian/patches/features/arm64/xgene-enable-xhci-usb.patch linux-3.16.7-ckt9/debian/patches/features/arm64/xgene-enable-xhci-usb.patch
--- linux-3.16.7-ckt9/debian/patches/features/arm64/xgene-enable-xhci-usb.patch 1970-01-01 00:00:00.0 +
+++ linux-3.16.7-ckt9/debian/patches/features/arm64/xgene-enable-xhci-usb.patch 2015-05-15 10:48:28.0 +
@@ -0,0 +1,40 @@
+Index: linux-3.16.7-ckt9/drivers/usb/host/xhci-plat.c
+===
+--- linux-3.16.7-ckt9.orig/drivers/usb/host/xhci-plat.c
linux-3.16.7-ckt9/drivers/usb/host/xhci-plat.c
+@@ -115,14 +115,18 @@ static int xhci_plat_probe(struct platfo
+ if (!res)
+ return -ENODEV;
+
+- /* Initialize dma_mask and coherent_dma_mask to 32-bits */
+- ret = dma_set_coherent_mask(pdev-dev, DMA_BIT_MASK(32));
+- if (ret)
+- return ret;
++ /* Try setting the coherent_dma_mask to 64 bits, then try 32 bits */
++ if (sizeof(dma_addr_t) 8 ||
++ dma_set_coherent_mask(pdev-dev, DMA_BIT_MASK(64))) {
++ ret = dma_set_coherent_mask(pdev-dev, DMA_BIT_MASK(32));
++ if (ret)
++ return ret;
++ }
+ if (!pdev-dev.dma_mask)
+ pdev-dev.dma_mask = pdev-dev.coherent_dma_mask;
+ else
+- dma_set_mask(pdev-dev, DMA_BIT_MASK(32));
++ dma_set_mask(pdev-dev, pdev-dev.coherent_dma_mask);
++
+
+ hcd = usb_create_hcd(driver, pdev-dev, dev_name(pdev-dev));
+ if (!hcd)
+Index: linux-3.16.7-ckt9/drivers/usb/host/Kconfig
+===
+--- linux-3.16.7-ckt9.orig/drivers/usb/host/Kconfig
linux-3.16.7-ckt9/drivers/usb/host/Kconfig
+@@ -28,6 +28,7 @@
+
+ config USB_XHCI_PLATFORM
+ tristate
++ default m
+
+ config USB_XHCI_MVEBU
+ tristate xHCI support for Marvell Armada 375/38x
diff -Nru linux-3.16.7-ckt9/debian/patches/series linux-3.16.7-ckt9/debian/patches/series
--- linux-3.16.7-ckt9/debian/patches/series 2015-04-13 00:40:38.0 +
+++ linux-3.16.7-ckt9/debian/patches/series 2015-05-15 08:47:26.0 +
@@ -578,3 +578,4 @@
debian/procfs-avoid-abi-change-in-3.16.7-ckt8.patch
bugfix/all/btrfs-simplify-insert_orphan_item.patch
+features/arm64/xgene-enable-xhci-usb.patch
Bug#785776: O: fwanalog -- firewall log-file report generator (using analog)
Package: wnpp Severity: normal Orphaning fwanalog since I am not using it any longer. fwanalog is a shell script that parses and summarizes firewall logfiles. It is able to work on firewall logs from ipchains (Linux 2.2), iptables (Linux 2.4), ipf (OpenBSD, FreeBSD and NetBSD) and some ZyXEL/NetGear routers. . It uses analog to generate the log-files, which includes daily statistics and such, and is both formatted in html and text (for online perusing, and a daily email, for instance). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487719: alsamixer: function snd_ctl_open failed for default: No such device
P.s., the current problem appeared immediately subsequent to upgrade from wheezy to jessie. Regards, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +13606390202 http://easthope.ca/peter.html Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785769: dbconfig-common: Korean debconf translation update
Package: dbconfig-common
Version: 1.8.51
Severity: wishlist
Tags: patch l10n
Please update the Korean debconf translation.
Cheers,
# Korean translations for dbconfig-common package
# dbconfig-common 패키지 한국어 번역문.
# Copyright (C) 2007 THE dbconfig-common'S COPYRIGHT HOLDER
# This file is distributed under the same license as the dbconfig-common package.
# Sunjae Park dareh...@gmail.com, 2007.
# Changwoo Ryu cw...@debian.org, 2009, 2015.
#
msgid
msgstr
Project-Id-Version: dbconfig-common\n
Report-Msgid-Bugs-To: dbconfig-com...@packages.debian.org\n
POT-Creation-Date: 2015-05-19 15:29+0200\n
PO-Revision-Date: 2015-05-20 09:42+0900\n
Last-Translator: Changwoo Ryu cw...@debian.org\n
Language-Team: Korean debian-l10n-kor...@lists.debian.org\n
Language: ko\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=1; plural=0;\n
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid Will this server be used to access remote databases?
msgstr 이 서버가 원격 데이터베이스에 접속합니까?
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid
For the database types that support it, dbconfig-common includes support for
configuring databases on remote systems. When installing a package's
database via dbconfig-common, the questions related to remote configuration
are asked with a priority such that they are skipped for most systems.
msgstr
원격 연결을 지원하는 데이터베이스의 경우, dbconfig-common에서 원격 시스템의
데이터베이스를 설정할 수 있습니다. dbconfig-common을 통해 패키지 데이터베이스
를 설치하는 경우, 대부분 시스템에서 원격 설정과 관련한 질문은 넘어가도록 우
선 순위가 설정되어 있습니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid
If you select this option, the default behavior will be to prompt you with
questions related to remote database configuration when you install new
packages.
msgstr
이 옵션을 선택하면, 새 패키지를 설치할 때 기본적으로 원격 데이터베이스 설정
에 관련한 질문을 묻습니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid If you are unsure, you should not select this option.
msgstr 잘 모르겠으면 이 옵션을 선택하지 마십시오.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid Keep \administrative\ database passwords?
msgstr \관리자용\ 데이터베이스 암호를 debconf에 저장해 두시겠습니까?
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid
By default, you will be prompted for all administrator-level database
passwords when you configure, upgrade, or remove applications with dbconfig-
common. These passwords will be stored in debconf's configuration database
only for as long as they are needed.
msgstr 기본값을 사용하는 경우에는 dbconfig-common을 통해 응용프로그램을 설정하거나, 업그레이드하거나, 제거할 때마다 관리자용 데이터베이스의 암호를 물어봅니다. 암호는 debconf의 설정 데이터베이스에 저장하지 않습니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid
This behavior can be disabled, in which case the passwords will remain in
the debconf database. This database is protected by Unix file permissions,
though this is less secure and thus not the default setting.
msgstr 이 기본 방식과 다르게 하면, 이 암호를 debconf 설정 데이터베이스에 저장합니다. 이 설정 데이터베이스는 유닉스 파일 권한을 통해 보호되지만, 보안상 덜 안전하므로 기본값이 아닙니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid
If you would rather not be bothered for an administrative password every
time you upgrade a database application with dbconfig-common, you should
choose this option. Otherwise, you should refuse this option.
msgstr
dbconfig-common을 통해 데이터베이스 응용 프로그램을 업그레이드할 때마다 관리
자용 암호를 입력하고 싶지 않다면, 이 옵션을 선택하십시오. 그렇지 않다면 이 옵
션을 선택하지 마십시오.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid Configure database for ${pkg} with dbconfig-common?
msgstr ${pkg}의 데이터베이스를 dbconfig-common으로 설정하시겠습니까?
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid
The ${pkg} package must have a database installed and configured before it
can be used. This can be optionally handled with dbconfig-common.
msgstr
${pkg} 패키지를 사용하려면 먼저 데이터베이스를 설치해 설정해야 합니다. 선택하
면 dbconfig-common을 이용해 데이터베이스를 설정할 수 있습니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid
If you are an advanced database administrator and know that you want to
perform this configuration manually, or if your database has already been
installed and configured, you should refuse this option. Details on what
needs to be done should most likely be provided in /usr/share/doc/${pkg}.
msgstr
경험 많은 데이터베이스 관리자라서 이 설정을 직접 하고 싶다면, 혹은 데이터베이
스를 이미 설치하고 설정한 경우, 이 옵션을 사용하지 마십시오. 설정하는 데 필요
한 내용은 /usr/share/doc/${pkg} 아래 들어 있을 것입니다.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid Otherwise, you should probably choose this option.
msgstr 그렇지 않다면 이 옵션을 선택하십시오.
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:5001
msgid Reinstall database for ${pkg}?
msgstr ${pkg}의 데이터베이스를 다시 설치하시겠습니까?
#. Type: boolean
#. Description
#: ../dbconfig-common.templates:5001
msgid
Since you are reconfiguring ${pkg}, you may also want to reinstall the
database which it uses.
Bug#785770: RM: xserver-xorg-video-siliconmotion [arm64] -- RoP; FTBFS; out-of-date; uninstallable; quite possiblly never worked, little if any utility
Package: ftp.debian.org x-debbugs-cc: debian-...@lists.debian.org,debia...@lists.debian.org A recent xorg update caused xserver-xorg-siliconmotion to fail to build with the following error. /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I.. -D_FORTIFY_SOURCE=2 -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o smi_501.lo ../../src/smi_501.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I.. -D_FORTIFY_SOURCE=2 -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c ../../src/smi_501.c -fPIC -DPIC -o .libs/smi_501.o In file included from ../../src/smi.h:317:0, from ../../src/smi_501.c:33: ../../src/regsmi.h: In function 'VGAIN8_INDEX': ../../src/regsmi.h:67:2: error: implicit declaration of function 'outb' [-Werror=implicit-function-declaration] outb(pSmi-PIOBase + indexPort, index); ^ ../../src/regsmi.h:67:2: warning: nested extern declaration of 'outb' [-Wnested-externs] ../../src/regsmi.h:68:2: error: implicit declaration of function 'inb' [-Werror=implicit-function-declaration] return(inb(pSmi-PIOBase + dataPort)); ^ ../../src/regsmi.h:68:2: warning: nested extern declaration of 'inb' [-Wnested-externs] cc1: some warnings being treated as errors Further investigation (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785491) showed that the reason for the FTBFS was the removal of non-functional stub implementations of those functions from xorg. I belive the out of date binary should be removed from sid for the following reasons. 1: it's uninstallable with the xorg currently in sid/stretch 2: while I have not investigated throughly it seems very likely that the use of stub versions of those functions would have rendered the driver unusable. 3: the siliconmotion chips in question seem to be obsolete parts mostly used for onboard graphics in old systems (though I did find one industrial minipcie card that claimed to use a siliconmotion chip, dunno if it's one supported by this driver). It seems unlikely that one would end up in an arm64 system. If this removal request is actioned I will downgrade bug 785491 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769811: needrestart: Should not ask for key-press upon pending kernel upgrade if $nrconf{restart} is set to 'a'
tag 769811 fixed-upstream
thanks
Hi Axel,
On 11/16/2014 09:21 PM, Axel Beckert wrote:
Hi Thomas,
Thomas Liske wrote:
You could disable the kernel check feature via the config file:
Sure, but that's not what I want. I want to see them, but I don't want
them to prevent the actual restarts.
sorry for ign...overlooking your bug for a long time. Upstream has been
just patched to add a new option to change kernel hints into simple
messages w/o acknowledgements:
# Enable/disable hints on pending kernel upgrades:
# 1: requires the user to acknowledge pending kernels
# 0: disable kernel checks completely
# -1: print kernel hints to stderr only
#$nrconf{kernelhints} = -1;
HTH,
Thomas
Common case: I run e.g. apt-get upgrade -y and then leave for lunch,
detach the screen session or just switch to another terminal for the
next machine.
An alternative solution would be to add a specific config option to
disable the requirement to press enter and just show that message.
Regards, Axel
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785484: systemd: on Raspberry pi B+, several essential services fail, including systemd-logind
Am 20.05.2015 um 05:42 schrieb Michael Biebl: Just in case you want to file this bug at the downstream distro: http://www.raspbian.org/RaspbianBugs Submitted yesterday. It's actually quite a challenge to find the right place. Finally I ended up here and, believe it or not, submitted bug #1: https://github.com/RPi-Distro/repo/issues/1 Cheers, Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777113: Followup NMU [was: invoke-rc.d, service under systemd: Avoid job dependency loops during boot/shutdown]
Hello all, sorry, the patch I uploaded in 2.88dsf-59.1 has a rather major bug: If systemd starts in degraded mode because some unit fails, then systemctl is-system-running exits with nonzero and prints degraded. In that case we still want to respect unit dependencies in service and invoke-rc.d, this is only for early-boot and late-shutdown. This was already fixed in https://launchpad.net/bugs/1429734 a while ago, so this got plenty of field testing. I committed the fix to git: http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=3a5540b4c I would like to do a followup NMU with that before the new version hits testing, as it can break stuff pretty severely. Sorry about that! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#758315: Patch for diatheke available
Green wrote: Beginning with the update to 1.7.3, diatheke now outputs the last verse twice. For example: $ diatheke -b KJV -k Gen1:1 Genesis 1:1: In the beginning God created the heaven and the earth. : In the beginning God created the heaven and the earth. (KJV) I've encountered this bug locally, but I also encountered it when packaging sword for Alpine Linux. Jaak Ristioja on the sword-devel list provided a patch, which is r3245 in sword SVN; the patch is also online here: http://git.alpinelinux.org/cgit/aports/tree/testing/sword/01-corediatheke.patch?id=708e933b22f8c17cbeeb5a65c25aaf3104aeb446 Thanks, Isaac Dunham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)
I have rebuild the package cv_0.6-1, with a working watch file, and modified Makefile, and some other small changes. lintian clean. Then the last thing remains to be done upon this package is the change of name ? To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cv Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cv/cv_0.6-1.dsc cv (0.6-1) unstable; urgency=low * Initial release (Closes: #785425) * This is my first Debian package. * Adjusted Makefile according to maint-guide. - for DESTDIR variable and install path. - Harden binary files. * Adjusted manpage for lintian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784567: intent to NMU sysvinit really soon -- followup fix
Hello all, The new sysvinit-utils versioned dependencies on util-linux introduces a circular dependency sysvinit-utils → util-linux → initscripts → sysvinit-utils. This breaks debootstrap at least for Ubuntu (see https://launchpad.net/bugs/1456670). I tested debootstrapping sid, and that does seem to work. But I have a gut feeling that this is some time bomb and may cause debootstrap woes at some point. So I replaced the versioned depends with a versioned Breaks:. util-linux is Priority: required anyway. http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=2e4267ce40f2 As it doesn't seem to be an imminent problem for sid, uploading that right now doesn't seem urgent. However, I'd like to do a followup NMU for a fix for bug 777113, I'll respond there with details. While I was at it, I also dropped an obsolete patch: http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=8784eabc (I ported this to util-linux on the Ubuntu side, I'll work with Andreas and upstream to get it into util-linux) Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#784709: solution
I managed to prevent this trouble by adding an extra test is os-prober Please check the attached patch or https://github.com/rzr/os-prober/tree/sandbox/rzr/for-upstream Or check my 1st post of : https://bugs.debian.org/768902 -- http://rzr.free.fr gpg:0x467094BC mailto:r...@gna.org xmpp:r...@jabber.org . From e5518c2f8dc75609b4e1972092fd6db3a535b9aa Mon Sep 17 00:00:00 2001 From: Philippe Coval r...@gna.org Date: Wed, 20 May 2015 02:12:59 +0200 Subject: [PATCH] Fix by forcing fs type to not-detected if not named This workaround prevents mount to hang on extended part (#768902) Signed-off-by: Philippe Coval r...@gna.org --- linux-boot-probes/common/50mounted-tests | 1 + os-probes/common/50mounted-tests | 1 + 2 files changed, 2 insertions(+) diff --git a/linux-boot-probes/common/50mounted-tests b/linux-boot-probes/common/50mounted-tests index 41e26e6..2bc2317 100755 --- a/linux-boot-probes/common/50mounted-tests +++ b/linux-boot-probes/common/50mounted-tests @@ -6,6 +6,7 @@ set -e partition=$1 types=$(fs_type $partition) || types=NOT-DETECTED +[ != $types ] || types=NOT-DETECTED if [ $types = NOT-DETECTED ]; then debug $1 type not recognised; skipping exit 0 diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests index 561163b..67744bd 100755 --- a/os-probes/common/50mounted-tests +++ b/os-probes/common/50mounted-tests @@ -6,6 +6,7 @@ partition=$1 . /usr/share/os-prober/common.sh types=$(fs_type $partition) || types=NOT-DETECTED +[ != $types ] || types=NOT-DETECTED if [ $types = NOT-DETECTED ]; then debug $1 type not recognised; skipping exit 0 -- 2.1.4 signature.asc Description: OpenPGP digital signature
Bug#487719: reopen 487719
reopen 487719 -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +13606390202 http://easthope.ca/peter.html Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785768: ITP: libatteanx-store-memorytriplestore-perl -- in-memory RDF triple store
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: libatteanx-store-memorytriplestore-perl Version : 0.001 Upstream Author : Gregory Todd Williams gwilli...@cpan.org * URL : https://metacpan.org/release/AtteanX-Store-MemoryTripleStore * License : GPL-2+ Programming Lang: Perl, C Description : in-memory RDF triple store AtteanX::Store::MemoryTripleStore provides an in-memory triple-store that is especially optimized for matching BGPs which contain at least one bound subject or object (e.g. preferring star or path queries rather than analytical queries). . The triple store is read-only, requiring a filename to be specified during construction which points at an N-Triples or Turtle file containing the RDF data to load. The triple store links with libraptor2 to allow fast parsing of input files. Package will be maintained in the Perl team. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVW9cQAAoJECx8MUbBoAEh/6oP/30c1lBaKczFxTtLusQT4LJL 2l75Wt9BsHB1/6seHtjotM/CoGL+aZS7qvxOunHfWs0VcYPWmGbKuca1ixlesmuR rQFsjU8SgEdy3sOreafFZcjcjfFacAzKK0EoOtWyoFlMqt4iohUVN1iofu48oGlQ b56K49Ed8t5SNPD2LCfltSR6K8UlF8kVpbXY8wzzF0S/ZTGDqVoOxUIBuCTC+dF5 TdhODtVqSJuvIIqD8l4J4iV4aJpwLkdTrSR/keJd6GnR9Ab8O69E5vf+dAsuz16p gI5dXwu9GGYug3SHJF+R6mKzybmES/MsGmUNb4Aw36z6yiku805a7QGhoqVeUf5v x6q/9209N3xFouVRtaXdUxijZWwG8RR8w/p3D2BXL1zGBVreX5WPiQ23UfD35109 abPvArkpBJIZ7uzReLMsGuIyXQc/bemaQeb7ItVzX8hqbRraXrGlhx/PiZFOS2/s GcZiYwSQbMszoNjE+A7ACJcXw5L2vbyTJE64XddLK0XZQu/7Tb4ZHGi6MkzpZaAr KsW15hn6vXIDWSGdMjsDcRF9HqV2T67xy4nMko/uYJNVUm7YVwa5YOxo1rdPz0hB XwAtPdOcX1I1OToWoWqrDTYQ3cMf6YGcARvA4Pj08QhZEkPIbvPpgbXrxF5DXtkd qAd2vh/0jVjqxUE6zC/J =WjBa -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#487719: found 487719 alsamixergui
found 487719 alsamixergui -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +13606390202 http://easthope.ca/peter.html Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784709: solution
On Wed, 20 May 2015 02:35:52 +0200 Philippe Coval wrote: I managed to prevent this trouble by adding an extra test is os-prober We discussed this on #debian-boot: rzr hi , would anyone like to help fixing a critical bug ? https://bugs.debian.org/784709 rzr I want to push a patch upstream pabs I think a better option might be to change return 0 to return 1 in fs_type? pabs and or possibly add support for blkid pabs oh, it is already there pabs rzr: do you have an extended partition handy? rzr yea pabs rzr but I upgraded kernel since pabs what is the output of this? blkid -o value -s TYPE /dev/sdX ; echo $? rzr 2 pabs hmmm, so that should trigger the types=NOT-DETECTED part already? rzr suspicious rzr I was thinking the same rzr well It's a bit late let's get feedback from bug reporter rzr pabs, thx anyway I'll stay around pabs indeed, could you send a mail CCing the submitter and asking them for this? blkid -o value -s TYPE /dev/sdb4 ; echo $? rzr older kernel return 0 rzr double checking current one pabs you mean older blkid? rzr no kernel 3.5.0-030500rc5-generic rzr from u rzr :) pabs but blkid is the thing that returns the value 2? rzr but stay calm i run debian rzr oh wait rzr it return 0 in all cases rzr I had mistyped sd4 for sda4 rzr so I could return err in that fs_type fuct if nullstring pabs blkid returns 0 or fs_type returns 0? rzr blkid pabs does it return the right thing for the other partitions? rzr yea pabs hmm rzr http://paste.debian.net/180700/ (copied below) rzr may the bug be in blkid then ? pabs not sure where it is TBH pabs which version of util-linux rzr Version: 2.25.2-6 rzr 1 version behind upstream rzr well i have to go rzr I'll email if no feedback in a couple of days pabs rzr: what about sudo file -s /dev/sda4 ? rzr /dev/sda4: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x3ff,47,57), end-CHS (0x3ff,254,63), startsector 2, 47565448 sectors; partition 2 : ID=0x5, start-CHS (0x3ff,0,1), end-CHS (0x3ff,254,63), startsector 47565450, 32772600 sectors --- rzr is now known as rZr rZr see ya pabs later for i in $(seq 1 5 ) ; do echo ; blkid -o value -s TYPE /dev/sda$i ; echo $i=$? ; done vfat 1=0 vfat 2=0 swap 3=0 4=0 ext3 5=0 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#785772: golang-gocheck: New upstream version available
Source: golang-gocheck Version: 0.0~bzr20131118+85 Severity: wishlist Dear Maintainer, Hi there. I'm packaging up a bunch of Go modules and an updated version of gocheck is required as a test dependency. The latest version in the git repo is 0.0~git20141025. I've already packaged this up in my public repo, but can easily merge into the pkg-go repo. https://anonscm.debian.org/cgit/users/tpot-guest/golang-gocheck.git/ Thanks! Tim. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785773: libsecret-common: Faulty/non-existing Homepage in package description
Package: libsecret-common Version: 0.18-1 Severity: minor Dear Maintainer, In the package description for the libsecret packages the referenced Homepage is https://wiki.gnome.org/Libsecret. That appear to be a non-existing page, returning a 404 code. The page https://wiki.gnome.org/Projects/Libsecret does exist. // Andreas -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- 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#785766: diaspora-installer: better description and vrms file
Source: src:diaspora-installer Version: 0.5.0.1+debian1 Severity: normal diaspora-installer do not inform user why installer is necessary. Usually Debian provides installers only when software is non-free (e.g. not suitable for (re-)distribution etc.) but nowhere in the diaspora-installer package it is explained why disapora needs installer and why it is not a normal Debian package. Users need to be informed what they are downloading and what freedoms there are giving away by using installer. I would put a notice to long package description and/or to README.source. Besides it might be a good idea to ship an additional vrms reason file to /usr/share/vrms/reasons in order to warn users about non-free software on their system through `vrms` utility. Such file can contain a one line explanation like the following: diaspora-installer: not-for-sale (no commercial exploitation) restriction If you choose to ship a reason file for vrms then you might want to add `vrms` to Suggests. Please let users know what is wrong with disapora. Thank you. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- Democracy is a pathetic belief in the collective wisdom of individual ignorance. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#785723: owncloud: column size on oc_activity too short
Control: forwarded -1 https://github.com/owncloud/activity/issues/254 Control: tags -1 upstream fixed-upstream pending Hi, thanks for your interest in this package. On Tue, May 19, 2015 at 11:23:33AM -0400, cloud3root wrote: Package: owncloud Version: 7.0.4+dfsg-4~deb8u1 Severity: normal […] has been reported and fixed upstream. https://github.com/owncloud/activity/issues/254 Marking the bug as forwarded then. https://github.com/owncloud/activity/pull/255 Since it has already fixed upstream, before the first 8.1 alpha, tagging it appropriately. seems like something that might be fixable in 7.x. Feel free to request a backport of the fix upstream. Pilling up this bug with #785052 and others, not sure what was expected from the package maintainers here. Regards David signature.asc Description: Digital signature
Bug#782811: trans: no longer works as Google Translate API changed
[I never recieved your mail as I do not subscribe to bugs] On Thu, 30 Apr 2015 10:53:23 +0200 Andreas Tille wrote: while I fixed the issue in unstable now I wonder how to proceed with tpu. Since translate-shell just got removed from stretch/testing, you don't need to bother with tpu. However, you do need to bother with jessie. I think you should cherry-pick the upstream patch for this issue. I think it would be best to upload to jessie-updates for this issue. Please follow the guidelines set out in the developers reference: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#785369: libimlib2: GIF loader: out-of-bounds read
Hello,
(not being maintainer I hope following could still be useful.)
For this example picture we get from libgif.so.4.1.6 in MakeMapObject
an array of ColorCount*sizeof(GifColorType) = 4*3 = 12 bytes.
Breakpoint 2, MakeMapObject (ColorCount=optimized out,
ColorMap=ColorMap@entry=0x0) at gifalloc.c:65
65 Object-Colors = (GifColorType *)calloc(ColorCount,
sizeof(GifColorType));
(gdb) print ColorCount
$3 = 4
(gdb) print sizeof(GifColorType)
$4 = 3
Note for later, ColorCount is also saved in Object:
Breakpoint 3, MakeMapObject (ColorCount=optimized out,
ColorMap=ColorMap@entry=0x0) at gifalloc.c:70
70 Object-ColorCount = ColorCount;
Back in imlib2 the variable cmap gets the value of gif-SColorMap assigned:
Breakpoint 4, load (im=0x6030f0, progress=0x0,
progress_granularity=optimized out, immediate_load=optimized out) at
loader_gif.c:145
145 cmap = (gif-Image.ColorMap ? gif-Image.ColorMap :
gif-SColorMap);
2: sizeof(GifColorType) = 3
(gdb) print gif-Image.ColorMap
$5 = (ColorMapObject *) 0x0
(gdb) print gif-SColorMap
$6 = (ColorMapObject *) 0x614aa0
(gdb) next
...
(gdb) print cmap
$11 = (ColorMapObject *) 0x614aa0
Finally the out-of-bounds reads are done. Here cmap-Colors gets accessed on
index 8, but just 0 to 3 would be valid:
Breakpoint 5, load (im=0x6030f0, progress=0x0,
progress_granularity=optimized out, immediate_load=optimized out) at
loader_gif.c:180
180r = cmap-Colors[rows[i][j]].Red;
(gdb) print i
$25 = 0
(gdb) print j
$26 = 17
(gdb) print rows[i][j]
$27 = 8 '\b'
At least following change would make in valgrind the invalid reads go away for
the test image:
--- src/modules/loaders/loader_gif.c.orig 2015-05-20 01:23:20.275121753
+0200
+++ src/modules/loaders/loader_gif.c2015-05-20 01:23:43.418378231 +0200
@@ -177,9 +177,13 @@ load(ImlibImage * im, ImlibProgressFunct
}
else
{
- r = cmap-Colors[rows[i][j]].Red;
- g = cmap-Colors[rows[i][j]].Green;
- b = cmap-Colors[rows[i][j]].Blue;
+ if (rows[i][j] cmap-ColorCount) {
+ r = cmap-Colors[rows[i][j]].Red;
+ g = cmap-Colors[rows[i][j]].Green;
+ b = cmap-Colors[rows[i][j]].Blue;
+ } else {
+ r = g = b = 0;
+ }
*ptr++ = (0xff 24) | (r 16) | (g 8) | b;
}
per += per_inc;
Was tested on amd64 with 4.1.6-11.
Is visible in Jessie version (1.4.6-2+b3) too.
Could probably also affect the transparency case of the
if statement when gif-SBackGroundColor gets an invalid value.
Kind regards,
Bernhard
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
