Bug#794458: release.debian.org: boost1.58/icu/gcc5 transition
Package: release.debian.org Severity: normal X-Debbugs-CC: s...@debian.org gcc5, icu are now build with libstdc++11 abi, and so is boost1.58. It's time to switch boost from 1.55 to 1.58. Otherwise libraries that are getting gcc5 soname bump that use boost as well, may get incompatible abi as a whole. I have boost-defaults upload ready, may I upload it? Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778292: python-jenkins: New upstream release 0.4.4
ping, any news on this? several people offered to help... signature.asc Description: This is a digitally signed message part.
Bug#794028: nvidia-kernel-dkms: Error! Bad return status for module build on kernel: 4.1.3 (x86_64)
fixed 794028 340.76-2 thanks On 3 August 2015 at 09:40, ioann sys ioann@gmail.com wrote: Hello! I try install packet bumblebee-nvidia from stretch, and now problem fixed. Also, i use newest kernel linux-image-4.0.2-rt-amd64. Now problem has been fixed. 2015-07-30 13:00 GMT+04:00 ioann sys ioann@gmail.com: Hello! Well, tomorrow, I send. 2015-07-30 5:10 GMT+04:00 Luca Boccassi luca.bocca...@gmail.com: Hi, Please provide the DKMS build log, should be in: /var/lib/dkms/nvidia-current/340.65/build/make.log Glad to hear that. Bumblebee-nvidia from Stretch will have installed 340.76-2, so even without seeing the logs I'm going to assume it was the same as 781810. Kind regards, Luca Boccassi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794461: RequirementParseError: Expected version spec in funcsigs; python_version3.3 at ; python_version3.3
Package: cookiecutter Version: 1.0.0-2 Severity: grave Dear Maintainer, When running cookiecutter the aforementioned error is encountered. The entire traceback is: $ cookiecutter --help Traceback (most recent call last): File /usr/bin/cookiecutter, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3084, in module @_call_aside File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3070, in _call_aside f(*args, **kwargs) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3097, in _initialize_master_working_set working_set = WorkingSet._build_master() File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 651, in _build_master ws.require(__requires__) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 952, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 847, in resolve new_requirements = dist.requires(req.extras)[::-1] File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2602, in requires dm = self._dep_map File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2597, in _dep_map dm.setdefault(extra,[]).extend(parse_requirements(reqs)) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2930, in parse_requirements version spec) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2895, in scan_list raise RequirementParseError(msg, line, at, line[p:]) pkg_resources.RequirementParseError: Expected version spec in funcsigs;python_version3.3 at ;python_version3.3 This is, obviously, rather unfortunate and prevents users from using this program. Please let me know if additional information is required or if there is anything I can do to help with this issue. I'd like to mention that cookiecutter installed in a virtualenv works fine and that this issue is specific to the one packaged in Debian. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-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) Versions of packages cookiecutter depends on: ii python 2.7.9-1 ii python-cookiecutter 1.0.0-2 cookiecutter recommends no packages. cookiecutter 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#794461: RequirementParseError: Expected version spec in funcsigs; python_version3.3 at ; python_version3.3
Control: reassign -1 python-mock ❦ 3 août 2015 11:32 +0200, Wolodja Wentland deb...@babilen5.org : When running cookiecutter the aforementioned error is encountered. The entire traceback is: $ cookiecutter --help Traceback (most recent call last): File /usr/bin/cookiecutter, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3084, in module @_call_aside File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3070, in _call_aside f(*args, **kwargs) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3097, in _initialize_master_working_set working_set = WorkingSet._build_master() File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 651, in _build_master ws.require(__requires__) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 952, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 847, in resolve new_requirements = dist.requires(req.extras)[::-1] File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2602, in requires dm = self._dep_map File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2597, in _dep_map dm.setdefault(extra,[]).extend(parse_requirements(reqs)) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2930, in parse_requirements version spec) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2895, in scan_list raise RequirementParseError(msg, line, at, line[p:]) pkg_resources.RequirementParseError: Expected version spec in funcsigs;python_version3.3 at ;python_version3.3 This seems to be a regression in python-mock. This spec string comes From its requirements.txt. It seems that pkg-resources from Python 2.7 is unable to parse such a string. A workaround may be to invoke with Python 3: python3 $(which cookiecutter) --help Reassigning. -- As to the Adjective: when in doubt, strike it out. -- Mark Twain, Pudd'nhead Wilson's Calendar signature.asc Description: PGP signature
Bug#794441: obnam: chunk ... does not exist
On Mon, Aug 03, 2015 at 11:57:40AM +0300, Lars Wirzenius wrote: The question was not why it isn't done YET, but why they are not removing at all, thinking it is a bug. And Yes, if You treat bug as missing feature, then there are less chances that it happen faster to fix it. I don't understand what you're trying to say. I am trying to say I don't reproach You for missing feature, for it isn't done YET. But I am wondering, why if and when fsck ALREADY have found reference to non-existent chunk, why it does not remove it? What makes sense to leave it in place? It would be missing feature to FIND AND REMOVE such references. But if You ALREADY have found it, what prevents You to remove it at this point, at this moment? If a file is missing a chunk, then it's data cannot be restored correctly, and the checksum of the restored data does not match the original file. That's what it means, and yes, it's related to the missing chunk. If I understand right, this means that when You find the reference that points to missing chunk, You should remove both the reference as well as the file containing this missing chunk, this reference points to, do You? ### Vladimir Stavrinov ### -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791165: libsdl-sge: library transition may be needed when GCC 5 is the default
2015-08-02 0:40 GMT+01:00 Matthias Klose d...@debian.org: Control: severity -1 normal On 08/02/2015 01:33 AM, Manuel A. Fernandez Montecelo wrote: 2015-08-01 22:36 GMT+01:00 Matthias Klose d...@debian.org: reopen 791165 severity 791165 serious tags 791165 + confirmed retitle 791165 libsdl-sge: library transition is needed when GCC 5 is the default thanks this is exactly what you should *not* do: libsdl-sge (030809dfsg-5) unstable; urgency=medium . * Bump Policy Standars-Version to 3.9.6 (no changes needed) * Rebuild against GCC-5 (Closes: #791165) * Enable parallel compilation with dh * Fix mispelling in d/copyright (detected by lintian) Please rename the library package (and add a proper library version). Why not? I already explained in the bug report why IMO we don't need a transition: - no packages in Debian use the functions sorry, didn't see this. please could you mention this with your next upload in the changelog and then close the issue? I do not understand very well the purpose of reuploading. It is not a problem at all to do it, it just surprised me that you ask for this, so just want to clarify. Do you want the next upload to be nowish, so it gets recompiled with GCC-5 in all arches (seems that it wasn't, even if the new GCC had been installed in all buildds), or can it be further down the road? (We often only upload changes to this package every year or more --last time was 2 years ago--, since this package has been dead upstream for more than a decade and there are no active forks --I asked recently--). Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794465: Bug fixes to be2net driver
Package: src:linux Version: 3.16.7-ckt11 Severity: important Don’t allow Skyhawk P1 firmware to be downloaded to Skyhawk P2 cards. Here I am submitting the patch set to fix this issue. These patches have been accepted upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794450: ITP: pb-consensuscore -- library of multiple nucleotide sequence consensus routines
Package: wnpp Severity: wishlist Owner: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Control: block 794447 by -1 * Package name: pb-consensuscore Version : 1.0.0 Upstream Author : Pacific Biosciences dev...@pacificbiosciences.com * URL : https://github.com/PacificBiosciences/ConsensusCore * License : BSD Programming Lang: C++, Python Description : library of multiple nucleotide sequence consensus routines ConsensusCore is a library of algorithms for Pacific Biosciences multiple sequence consensus that powers Quiver, a variant and consensus caller for single-molecule sequencing reads. This package is a dependency of pb-genomicconsensus (#794447), a component of the SMRTAnalysis suite (#787977). These are to be built and maintained by the Debian Med team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794403: flash-kernel: command update-initramfs -uk kver result in boot images in false version
On Mon, 2015-08-03 at 01:27 +0900, Roger Shimizu wrote: Package: flash-kernel Version: 3.45 Severity: normal Tags: patch Dear Maintainer, Hook script initramfs-hook/flash-kernel will be called when update-initramfs is invoked. However flash-kernel only build the latest kernel version it find, rather than the specific version passing from update-initramfs. For example, after running update-initramfs -uk , the is successfully passed to initramfs-hook/flash-kernel, and then flash-kernel script, but flash-kernel script simply ignore that version, except adding a --force flag, which is why this patch is here. The update-initramfs -uk kver command is intended to update the initramfs for kver, it is not intended to mean and boot kver next time, that is not update-initramfs's job (on other platforms it does not e.g. call grub-set-default or grub-reboot either). flash-kernel normally always tries to keep the latest kernel installed. It offers a command line override for this, but this is not expected to be used by automatic callers. Really this capability is more for debugging (by booting an older kernel once or twice) than anything else. If you want to permanently boot kver then at the moment you have to arrange that kver is the newest installed kernel. I think your patch will break things by automatically installing (via the initramfs hook in the kernel postinst) whatever kernel was most recently installed/upgraded, instead of the latest kernel by version. We do not want this: consider people who still have stable+testing in their sources.list and the stable+testing kernel's both installed, they are expecting to use the testing kernel and do not want to get a surprise stable kernel installed whenever a DSA is issued against the Linux package in stable. I also checked the log for initramfs-hook/flash-kernel, as commit 7bacb9 the kernel version was actually not passed to flash-kernel script, but from commit e05fc9, this has been changed, which I think it means the flash-kernel script need to honor what kernel version update-initramfs is working on. I'm afraid not, when called from the initramfs-hook flash-kernel should arrange for the update only if operating on the newest kernel. An acceptable alternative to your patch might be to add support for a new option in /etc/default/flash-kernel e.g. LINUX_KERNEL_VERSION which names an explicit version which is the one which should should always be installed in flash (unless overridden on the command line). Care would need to be taken that the kernel exists and to do the right thing if it is is removed. I think a suitable algorithm for determining the version would be to consider in order: 1. The version on the command line, if any. If one is given but doesn't exist then error out. 2. The version from /etc/default/flash -kernel:$LINUX_KERNEL_VERSION, if it doesn't exist then fall through to next option(*) with a big fat warning printed. 3. The currently installed version with the greatest version number. The fall through from option 2 to option 3 is important, otherwise a kernel removal/upgrade/install (which invokes flash-kernel) may find itself unable to complete if the desired kernel is missing and abort the whole operation, which will be potentially tricky to recover from since it will block further apt/dpkg operations until it is sorted out. Installing the latest kernel if the preferred option is not available seems better than failing in this case. People who then want to boot an older kernel could set LINUX_KERNEL_VERSION and call flash-kernel to make it take effect. Ian. Thanks and looking forward to your comments. Cheers, Roger -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (1, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 4.0.0-2-kirkwood Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.56 ii devio 1.2-1+b1 ii initramfs-tools0.120 ii linux-base 3.5 ii ucf3.0030 Versions of packages flash-kernel recommends: ii u-boot-tools 2014.10+dfsg1-5 flash-kernel suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794451: systemd openafs-client.service causes ordering cycles
Package: openafs-client Version: 1.6.13-1 /lib/systemd/system/openafs-client.service specifies Before=remote-fs.target It also has an implicit Requires=basic.target (at least on the jessie system on which I'm testing this; one can see this with systemctl show -p Requires openafs-client.service ). While the reverse dependency on remote-fs.target seems logical (the service does provide access to a remote filesystem), it causes trouble in practice since many scripts in /etc/init.d/ have a Required-Start: $remote_fs to signify that they need access to /usr (which, at least pre-systemd, could be on a remote filesystem; this is explained, e.g., in https://wiki.debian.org/LSBInitScripts/). sysinit.target depends on all scripts in /etc/init.d/ that do not have a systemd counterpart, and basic.target depends on sysinit.target. I'm filing this bug against openafs-client but for my environment I'm planning to work around the problem by changing $remote_fs to $local_fs in the other /etc/init.d/ scripts involved. (One of them is /etc/init.d/ferm and I do want my firewall rules to be in place before most services are started.) I can do this since I'm not NFS-mounting /usr but it may not be a satisfactory solution for everyone. Maybe openafs-client.service should consider dropping Requires=basic.target . To illustrate the problem, here is an excerpt from journalctl output that shows an undesirable sequence of events: systemd[1]: Found ordering cycle on basic.target/start systemd[1]: Found dependency on sysinit.target/start systemd[1]: Found dependency on ferm.service/start systemd[1]: Found dependency on remote-fs.target/start systemd[1]: Found dependency on openafs-client.service/start systemd[1]: Found dependency on basic.target/start systemd[1]: Breaking ordering cycle by deleting job ferm.service/start systemd[1]: Job ferm.service/start deleted to break ordering cycle starting with basic.target/start systemd[1]: Found ordering cycle on basic.target/start systemd[1]: Found dependency on sysinit.target/start systemd[1]: Found dependency on kbd.service/start systemd[1]: Found dependency on remote-fs.target/start systemd[1]: Found dependency on openafs-client.service/start systemd[1]: Found dependency on basic.target/start systemd[1]: Breaking ordering cycle by deleting job kbd.service/start systemd[1]: Job kbd.service/start deleted to break ordering cycle starting with basic.target/start systemd[1]: Found ordering cycle on basic.target/start systemd[1]: Found dependency on sysinit.target/start systemd[1]: Found dependency on console-setup.service/start systemd[1]: Found dependency on remote-fs.target/start systemd[1]: Found dependency on openafs-client.service/start systemd[1]: Found dependency on basic.target/start systemd[1]: Breaking ordering cycle by deleting job console-setup.service/start systemd[1]: Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus
On Mon, Aug 03, 2015 at 09:47:33AM +0200, Aurelien Jarno wrote: On 2015-04-30 23:10, Matthias Klose wrote: On 04/30/2015 10:43 PM, Daniel Serpell wrote: Currently, gcc-5 packages are really big because the files under /usr/lib/gcc/x86_64-linux-gnu/5 are not stripped, and each one of lto1, cc1 and cc1plus is about 130MB. Please, can those files be striped in the default installation? I'd like to avoid this, and only change that near the next Debian release. These binaries are linked against libbacktrace to provide a verbose backtrace on internal compiler errors, which you can't get with stripped binaries. If that's not possible could you please at least change these binaries to use compressed debug sections at least? That should save quite some space already. I would believe that is not easily possible. I don't know the detailed behavior of libbacktrace, but it is using parsing the DWARF debug information of the binaries (cc1, cc1plus, ...), so I guess you'll need to patch (significantly) libbacktrace to compress the debug sections. BTW, I don't see the size of cc1 etc... as an issue. Compilers are useful on development machines, and these are usually not very small (and have enought disk space). Cheers -- Basile Starynkevitchhttp://starynkevitch.net/Basile/ France basile at starynkevitch.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794452: python-sqlparse: Please update package to 0.1.14 or higher to satisfy pgcli/mycli dependency
Package: python-sqlparse Version: 0.1.13-2 Severity: wishlist Dear Maintainer, Please update the package to version 0.1.14 or the newest version 0.1.16 to satisfy the dependencies of the packages I am currently building for debian, pgcli (#794250) and mycli (#794251). Greetings, Lennart Weller -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (1000, 'stable'), (800, 'testing'), (700, 'unstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: [kde-full] Windows frames disappears!!!!
Package: kde-window-manager Version: 4:5.3.2-3 Followup-For: Bug #794102 Could it be that this is a duplicate of #793026? -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-window-manager depends on: ii kwin-x11 4:5.3.2-3 kde-window-manager recommends no packages. kde-window-manager 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#793281: sqlitebrowser: change of type in system_error might break with GCC-5
Control: block -1 by 793215 Matthias Klose d...@debian.org writes: GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. AFAICT sqlitebrowser inherits this issue from antlr, and thus that needs to be rebuilt before anything can be done for sqlitebrowser. Will libstdc++ generate tight enough dependencies to prevent partial upgrades, or would antlr need to do the Breaks dance with its rdeps? -- Arto Jantunen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794460: ITP: gb -- gb, the project based build tool for Go
Package: wnpp Severity: wishlist Owner: Tianon Gravi admwig...@gmail.com * Package name: gb Version : 0.0~git20150803.0.894195c-1 Upstream Author : constabulary (Dave Cheney) * URL : https://getgb.io * License : Expat Programming Lang: Go Description : gb, the project based build tool for Go gb is a proof of concept replacement build tool for the Go programming language. gb operates on the concept of a project. A gb project is a workspace for all the Go code that is required to build your project. A gb project is a folder on disk that contains a subdirectory named src/. That's it, no environment variables to set. For the rest of this document we'll refer to your gb project as $PROJECT. You can create as many projects as you like and move between them simply by changing directories. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793281: sqlitebrowser: change of type in system_error might break with GCC-5
On 08/03/2015 11:09 AM, Arto Jantunen wrote: Control: block -1 by 793215 Matthias Klose d...@debian.org writes: GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. AFAICT sqlitebrowser inherits this issue from antlr, and thus that needs to be rebuilt before anything can be done for sqlitebrowser. Will libstdc++ generate tight enough dependencies to prevent partial upgrades, or would antlr need to do the Breaks dance with its rdeps? no. not by default. so it's probably better if antlr breaks all libantlr-dev rdeps? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794435: nvidia-kernel-dkms: DKMS build failure on armhf
On Mon, 2015-08-03 at 11:58 +0200, Andreas Beckmann wrote: On 2015-08-03 02:21, Luca Boccassi wrote: Testing the build of nvidia-kernel-dkms in an armhf chroot (via qemu static binaries) results in build failure for kernels 3.16 (jessie) and 4.0 (sid). Cannot test 4.1 as the armhf build of linux-kbuild-4.1 is missing. Does any other of the armhf linux-headers-* work? Oh wait, there are not that many any more :-) yep, the only other one is armmp-lpae, but that only adds a couple more configs, the rest are all meta-packages. I already addressed 2 problems and committed to the SVN repo (patch nv-linux.h and enable dma_ops for arm in conftest.h, but the final problem is that the armhf kernel ships with CONFIG_XEN enabled [1], without CONFIG_PARAVIRT, and this is not supported. Sounds like a question for the kernel maintainers ... what about ignoring CONFIG_XEN on armhf in nv-linux.h: -#if defined(CONFIG_XEN) !defined(CONFIG_PARAVIRT) +#if defined(CONFIG_XEN) !defined(CONFIG_PARAVIRT) !defined(CONFIG_whatever_indicates_armhf) Thought about that, but that would probably cause havok in case the driver is actually ran in a VM on top of Xen, wouldn't it (however unlikely that might be)? It won't fail to load anymore since we don't support it, and probably die later. Nonetheless, I'll give it a shot and see how it behaves later tonight or tomorrow. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#794463: RM: apertium-tolk -- ROM; dead upstream
Package: ftp.debian.org
Severity: normal
Hi,
As discussed with Apertium upstream developers, apertium-tolk is
obsolete and has no upstream support or activity. Please go ahead and
remove it from Debian. Also, it FTBFS with new Apertium package.
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794464: RM: apertium-dbus -- ROM; dead upstream
Package: ftp.debian.org
Severity: normal
Hi,
As discussed with Apertium upstream developers, apertium-dbus is
obsolete and has no upstream support or activity. Please go ahead and
remove it from Debian. Also, it FTBFS with new Apertium package.
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791014: csound: library transition may be needed when GCC 5 is the default
Control: reopen -1 Control: user release.debian@packages.debian.org Control: usertag -1 + transition Control: block -1 by 790756 Control: reassign -1 release.debian.org Control: retitle -1 transition: csound (GCC 5) On 3 July 2015 at 10:09, Matthias Klose d...@debian.org wrote: Package: src:csound Version: 6.05~dfsg1-2 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org The changed package has been uploaded to experimental, and I have verified the only reverse dep (csoundqt) builds with it. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794440: xsd: Not build due to no codesynthesis/cli package in debian archive
Zhang Jingqiang zh...@outlook.com writes: cli is needed when building this package. But no package contains codesynthesis/cli XSD distribution (but not the git tree) includes pre-generated CLI files so you shoudn't need the CLI tool to be packaged for Debian (though I wouldn't mind at all if it gets packaged ;-)). So what most likely happens (provided you use the distribution), is that you do 'make clean' before building which removes those generated files. To avoid this, you can add the xsd_clean_gen=n to the make command line, e.g., 'make xsd_clean_gen=n clean'. Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794466: Virtualbox might not be suitable for Stretch
Source: virtualbox Version: 4.3.30-dfsg-1 Severity: critical X-Debbugs-CC: j...@inutil.org X-Debbugs-CC: r...@debian.org X-Debbugs-CC: frank.mehn...@oracle.com X-Debbugs-CC: klaus.espenl...@oracle.com (please cc people if needed As Said in many different threads [1 bottom of the mail], Upstream doesn't play in a really fair mode wrt CVEs in the package (it used to, but not for the current CVE list). This basically makes the package unsuitable for Stable Releases, since Upgrade to a newer release is not the correct answer, and cherry-picking patches without upstream support is just impossible/not easily feasible for such a huge codebase. I quote a mail from some Vbox upstream developers and Debian folks. Personal Maintainer opinion: I do not have anything against Virtualbox neither against Upstream, made by people competent who helped us a lot, and did a great work in merging patches (also my patches) and providing such a good tool for us, I love the package and I would like to see it in Debian, but since people working for Oracle might risk to get punished for not following the Oracle policy, I think we are not sure we can continue giving a CVE free package for Stable Releases. So, while Oracle employees tries to find out an Open Source friendly way to cooperate with us, I'm opening this bug, to let the community be aware of the status quo of the package. On Tuesday 28 July 2015 14:00:31 Ritesh Raj Sarraf wrote: I am writing to you seeking clarification on what the project's stance is for Security Vulnerabilities. As you know, for Debian, we package VirtualBox. Given the breadth of the Debian project (oldstable, stable, testing, LTS, derivatives), it is important for us to have access to security fixes in an easy format. https://security-tracker.debian.org/tracker/CVE-2015-2594 For example, for the above CVE, afaik all we have is a consolidated report. http://www.oracle.com/technetwork/topics/security/cpujul2015 -2367936.html With no broken down fixes in an easy format, it makes it difficult to backport those fixes to older versions. I'm aware of the problem. Unfortunately there is an Oracle policy which forbids us to provide relevant information about security bugs, see here: http://www.oracle.com/us/support/assurance/vulnerability-remediation/disclosure/index.html We are currently trying to find out what's possible to help you but this will take some more time. thanks folks for the help, I still hope we can solve it in a good way, to avoid disappear of Virtualbox there :) cheers! Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637627: hostname -A has multiple values
Hi,
this patch is wrong!
commit c2087b165bd0fdc6511df4c874390359b290b8bf
Author: Gianfranco Costamagna costamagnagianfra...@yahoo.it
Date: Mon Aug 3 11:15:11 2015 +0200
Use a hostname -A as fallback in case of -f fails (Closes: #637627)
thanks mapreri for the help
diff --git a/pbuilder-modules b/pbuilder-modules
index f28b2db..7568176 100644
--- a/pbuilder-modules
+++ b/pbuilder-modules
@@ -482,7 +482,7 @@ function extractbuildplace () {
exit 1
fi
log I: creating local configuration
- hostname -f $BUILDPLACE/etc/mailname
+ hostname -f || hostname -A $BUILDPLACE/etc/mailname
fi
copy_local_configuration
This is because hostname -A has multiple output:
tglase@tglase:~ $ hostname -A
tglase.lan.tarent.de tgwrk.ig42.org
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl
Eric, Do you have the TrustedQSL package installed? Do LoTW *uploads/exports* work okay? 73, Colin G8TMV -- Colin Tuckley | +44(0)1223 830814 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x38C9D903 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794404: icu ftbfs with GCC 5 on hurd-i386
Control: tags -1 + upstream patch
Hello,
Matthias Klose, le Sun 02 Aug 2015 18:44:25 +0200, a écrit :
simplethread.cpp:276:1: note: 'SimpleThread::SimpleThread()' previously
defined here
SimpleThread::SimpleThread()
This is dumb old code, erroneously included due to U_PF_CLASSIC_MACOS
not being defined any more (and thus assumed to be 0 by the
preprocessor), and thus
#elif U_PLATFORM == U_PF_CLASSIC_MACOS
erroneously succeeding (U_PLATFORM is here defined to U_PF_UNKNOWN,
which happens to be 0 too).
The attached trivial cleanup patch fixes it.
Could a fixed package be uploaded very soon? This is essentially
blocking all package builds on hurd-i386...
Alternatively, I can make a build with nocheck (the testsuite does go
fine).
Samuel
--- ./source/test/intltest/simplethread.cpp.orig2015-08-03
11:53:07.372942007 +0200
+++ ./source/test/intltest/simplethread.cpp 2015-08-03 11:53:10.54224
+0200
@@ -260,42 +260,6 @@
::Sleep(millis);
}
-//---
-//
-// class SimpleThread NULL Implementation
-//
-//---
-#elif U_PLATFORM == U_PF_CLASSIC_MACOS
-
-// since the Mac has no preemptive threading (at least on MacOS 8), only
-// cooperative threading, threads are a no-op. We have no yield() calls
-// anywhere in the ICU, so we are guaranteed to be thread-safe.
-
-#define HAVE_IMP
-
-SimpleThread::SimpleThread()
-{}
-
-SimpleThread::~SimpleThread()
-{}
-
-int32_t
-SimpleThread::start()
-{ return 0; }
-
-void
-SimpleThread::run()
-{}
-
-void
-SimpleThread::sleep(int32_t millis)
-{}
-
-UBool
-SimpleThread::isRunning() {
-return FALSE;
-}
-
#endif
--- ./source/tools/toolutil/udbgutil.cpp.orig 2015-08-03 11:53:13.788781812
+0200
+++ ./source/tools/toolutil/udbgutil.cpp2015-08-03 11:53:14.736758140
+0200
@@ -354,8 +354,6 @@
return Linux;
#elif U_PLATFORM == U_PF_ANDROID
return Android;
-#elif U_PLATFORM == U_PF_CLASSIC_MACOS
-return MacOS (Classic);
#elif U_PLATFORM == U_PF_OS390
return IBM z;
#elif U_PLATFORM == U_PF_OS400
Bug#794462: arcanist should depends on the exact same version of libphutil
Package: arcanist Version: 0~git20150613-1 Severity: important Dear Maintainer, I just updated (only) arcanist to v 0~git20150613-1 and $ arc diff failed with: PHP Fatal error: Call to undefined method PhutilTranslator::setLocale() in /usr/share/arcanist/scripts/__init_script__.php on line 57 Fatal error: Call to undefined method PhutilTranslator::setLocale() in /usr/share/arcanist/scripts/__init_script__.php on line 57 Updating libphutil from 0~git20150129-2 to 0~git20150613-1 fixed the issue. arcanist should depends on the same version of libphutil. Thanks, Sylvestre -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (600, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages arcanist depends on: ii libphutil 0~git20150613-1 ii php5-cli 5.6.5+dfsg-1 ii php5-curl 5.6.5+dfsg-1 arcanist recommends no packages. Versions of packages arcanist suggests: ii python 2.7.9-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794435: nvidia-kernel-dkms: DKMS build failure on armhf
On 2015-08-03 02:21, Luca Boccassi wrote: Testing the build of nvidia-kernel-dkms in an armhf chroot (via qemu static binaries) results in build failure for kernels 3.16 (jessie) and 4.0 (sid). Cannot test 4.1 as the armhf build of linux-kbuild-4.1 is missing. Does any other of the armhf linux-headers-* work? Oh wait, there are not that many any more :-) I already addressed 2 problems and committed to the SVN repo (patch nv-linux.h and enable dma_ops for arm in conftest.h, but the final problem is that the armhf kernel ships with CONFIG_XEN enabled [1], without CONFIG_PARAVIRT, and this is not supported. Sounds like a question for the kernel maintainers ... what about ignoring CONFIG_XEN on armhf in nv-linux.h: -#if defined(CONFIG_XEN) !defined(CONFIG_PARAVIRT) +#if defined(CONFIG_XEN) !defined(CONFIG_PARAVIRT) !defined(CONFIG_whatever_indicates_armhf) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793360: apt: APT::Never-MarkAuto-Sections not working as advertised
On Sat, Aug 01, 2015 at 01:19:33PM -0600, Adam Conrad wrote:
For the record, Raphael's patch is buggy and causes segfaults in some
corner cases. You can see https://pad.lv/1480592 for more details.
That is a fun one and could have been avoided if we would optimize more…
The fun here is that the check if the to-be installed version of
package P is in a never-auto section for every dependency of the to-be
installed version of package P – by calculating this once outside the
loop we could avoid the segfault:
The segfault comes into existence as while a dependency of P is
installed it can happen that P is marked for deletion, so that it loses
the to-be installed version information. After the depth-first style
dependency installation returned to install the next dependency of
P it will check again if the to-be installed version (which is now
a null pointer) is in a never-auto section… *boom*.
Exkurs: Why is it legal for a dependency D to remove its own dependee
P? This can happen e.g. in dist-upgrades where lib1 depends lib2 and
lib2 breaks lib1. If lib1 or lib2 will be installed after the upgrade is
decided much later by the pkgProblemResolver, not by pkgDepCache.
Adams patch while fixing the segfault leaves a (very small) problem: The
dependencies D2, D3, … after the dependency D which has removed P will
not be marked as manual as the check is now false as long as P isn't
installed (again).
My attached patch moves the check out of the loop in a region where
P.InstallVer is guarantied to be valid by the surroundings and as it is
checked only once D2, D3, … are marked as manual even if P is
temporarily removed.
Note that the removal of P by D has (depending on how the dependencies
are exactly) interesting effects: If e.g. P is itself a dependency of
a never-auto package the removal of P will clear the manual bit, so that
P will end up being auto-installed. In D | D1, D1 will probably not have
the auto-bit state you would expect either (See the included testcase
for an example and a description of both cases).
This isn't a new problem through. This exists since the dawn of this
feature in 2007, so given its undetected for 8 years I supposes its very
edgecasey and it could end up being a real pain to fix – so that
I haven't even tried to do it. Would be too big a fix for a stable
update anyhow…
At least, now that I know of this case I might be able to not introduce
the same problem in the above 'proposed' quasi replacement for
never-auto, so that wasn't all in vain.
Oh, and of course: This patch is as unlikely to cause a regression as
its (at least) three previous incarnations. ;P
It's unbelievable how much can go wrong in a single line of code…
Best regards
David Kalnischkies
commit d32010483fed74681bf9035a1c81adbcecbf1146
Author: David Kalnischkies da...@kalnischkies.de
Date: Mon Aug 3 07:00:33 2015 +0200
mark again deps of pkgs in APT::Never-MarkAuto-Sections as manual
In 50ef3344c3afaaf9943142906b2f976a0337d264 (and similar for other
branches), while 'fixing' the edgecase of a package being in multiple
sections (e.g. moved from libs to oldlibs in newer releases) I
accidently broke the feature itself completely by operating on the
package itself and no longer on its dependencies…
The behaviour isn't ideal in multiple ways, which we are hopefully able
to fix with new ideas as mentioned in the buglog, but until then the
functionality of this hack should be restored.
Reported-By: Raphaël Hertzog hert...@debian.org
Tested-By: Adam Conrad adcon...@ubuntu.com
Closes: 793360
LP: 1479207
Thanks: Raphaël Hertzog and Adam Conrad for detailed reports and initial patches
diff --git a/apt-pkg/depcache.cc b/apt-pkg/depcache.cc
index 16282df..14c709c 100644
--- a/apt-pkg/depcache.cc
+++ b/apt-pkg/depcache.cc
@@ -1103,7 +1103,12 @@ bool pkgDepCache::MarkInstall(PkgIterator const Pkg,bool AutoInst,
if (DebugMarker == true)
std::clog OutputInDepth(Depth) MarkInstall Pkg FU= FromUser std::endl;
- DepIterator Dep = P.InstVerIter(*this).DependsList();
+ VerIterator const PV = P.InstVerIter(*this);
+ if (unlikely(PV.end() == true))
+ return false;
+ bool const PinNeverMarkAutoSection = (PV-Section != 0 ConfigValueInSubTree(APT::Never-MarkAuto-Sections, PV.Section()));
+
+ DepIterator Dep = PV.DependsList();
for (; Dep.end() != true;)
{
// Grok or groups
@@ -1226,7 +1231,7 @@ bool pkgDepCache::MarkInstall(PkgIterator const Pkg,bool AutoInst,
continue;
}
// now check if we should consider it a automatic dependency or not
- if(InstPkg-CurrentVer == 0 InstVer-Section != 0 ConfigValueInSubTree(APT::Never-MarkAuto-Sections, InstVer.Section()))
+ if(InstPkg-CurrentVer == 0 PinNeverMarkAutoSection)
{
if(DebugAutoInstall == true)
std::clog OutputInDepth(Depth) Setting NOT as auto-installed (direct
diff --git a/test/integration/framework
Bug#794102: [kde-full] Windows frames disappears!!!!
Followup-For: Bug #794102 Package: kde-window-manager Version: 4:5.3.2-3 Could it be that this is a duplicate of #793026? -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-window-manager depends on: ii kwin-x11 4:5.3.2-3 kde-window-manager recommends no packages. kde-window-manager suggests no packages. -- no debconf information -- Max-Planck-Institute for Dynamics and Self-Organization Research Group Biomedical Physics Am Fassberg 17 D-37077 Goettingen (+49) 551 5176 373 You can obtain my public key 0xF197B128 from all keyservers, e.g. pgp.mit.edu Fingerprint: 9698 BDD4 71CC 1274 B7E2 2049 1EDD 012D F197 B128 signature.asc Description: This is a digitally signed message part.
Bug#794459: python-tablib: Provide Python3 package
Package: python-tablib Severity: wishlist Dear Maintainer, seeing that tablib supports Python 3, could you provide a python3-tablib package? Cheers, Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793897: gettext: library transition is needed when GCC 5 is the default
Hi. The package was uploaded yesterday and it's now waiting in NEW. No package depends on libasprintf0c2 so this is not a transition in the strict sense. I hope the FTP managers process this package soon. Note: In addition to the Breaks field, there is another little thing which I did differently from the proposed patch: gettext-base had a versioned Depends: libasprintf0c2 (= 0.18.1.1-6). This is because gettext-base used to contain this library and it was splitted out from gettext-base in version 0.18.1.1-6. Now gettext-base just Depends on the new library. There have never been a libasprintf0v5 package 0.18.1.1-6 so the versioned depends would be redundant here. Thanks a lot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761273: Use changelog release for control generation
Hi, just do the debian/rules control call in a session under the target release, e.g. under “cowbuilder --login”. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793094: pjproject: FTBFS: some symbols or patterns disappeared in the symbols file
Thanks for your report, On Tue, Jul 21, 2015 at 11:23:33AM +0200, Jakub Wilk wrote: Source: pjproject Version: 2.4~dfsg-1 Severity: serious Justification: fails to build from source pjproject FTBFS on 32-bit architectures: I originally thought it's a 32 bits issue. But what about s390x, alpha and ppc64? Specifically this is the second issue (see below). |dh_makeshlibs -a | dpkg-gensymbols: warning: some libraries disappeared in the symbols file: libpjsip-simple.so.2 libpjsua.so.2 libpjmedia-codec.so.2 libpjlib-util.so.2 libpjsip-ua.so.2 libpjsip.so.2 libpjnath.so.2 libpjmedia-videodev.so.2 libpjmedia.so.2 libpjmedia-audiodev.so.2 libpj.so.2 | dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below | dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libpjsua2-2/DEBIAN/symbols doesn't match completely debian/libpjsua2-2.symbols | --- debian/libpjsua2-2.symbols (libpjsua2-2_2.4~dfsg-1_i386) | +++ dpkg-gensymbols2_HFSS 2015-07-20 23:22:51.722478229 + | @@ -1,2152 +1,3 @@ | -libpj.so.2 libpjsua2-2 #MINVER# | - PJ_AF_INET6@Base 2.4~dfsg | - PJ_AF_INET@Base 2.4~dfsg | - PJ_AF_IRDA@Base 2.4~dfsg | - PJ_AF_PACKET@Base 2.4~dfsg Those symbols seem to actually come from libpj. I guess that the symbols file there is broken: it contains a host of symbols from other sub-packages. [SNIP - very long of multiple libraries that completely disappeared and their symbols] | libpjsua2.so.2 libpjsua2-2 #MINVER# | _ZN10PendingLog7executeEb@Base 2.4~dfsg | _ZN10PendingLogD0Ev@Base 2.4~dfsg | @@ -2744,12 +595,14 @@ | _ZNSt12_Destroy_auxILb0EE9__destroyIPSsEEvT_S3_@Base 2.4~dfsg | _ZNSt20__uninitialized_copyILb0EE13__uninit_copyIPN2pj12AuthCredInfoES4_EET0_T_S6_S5_@Base 2.4~dfsg | _ZNSt6vectorIN2pj12AuthCredInfoESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base 2.4~dfsg | - _ZNSt6vectorIN2pj12AuthCredInfoESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base 2.4~dfsg | + _ZNSt6vectorIN2pj12AuthCredInfoESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEjRKS1_@Base 2.4~dfsg-1 | +#MISSING: 2.4~dfsg-1# _ZNSt6vectorIN2pj12AuthCredInfoESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base 2.4~dfsg | _ZNSt6vectorIN2pj13CallMediaInfoESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base 2.4~dfsg | _ZNSt6vectorIN2pj16SipMultipartPartESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base 2.4~dfsg | _ZNSt6vectorIN2pj17ToneDigitMapDigitESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base 2.4~dfsg | _ZNSt6vectorIN2pj9SipHeaderESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base 2.4~dfsg | - _ZNSt6vectorIN2pj9SipHeaderESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base 2.4~dfsg | + _ZNSt6vectorIN2pj9SipHeaderESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEjRKS1_@Base 2.4~dfsg-1 | +#MISSING: 2.4~dfsg-1# _ZNSt6vectorIN2pj9SipHeaderESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base 2.4~dfsg | _ZNSt6vectorIN2pj9SipHeaderESaIS1_EED1Ev@Base 2.4~dfsg | _ZNSt6vectorIN2pj9SipHeaderESaIS1_EED2Ev@Base 2.4~dfsg | _ZNSt6vectorIN2pj9SipHeaderESaIS1_EEaSERKS3_@Base 2.4~dfsg | @@ -2764,10 +617,12 @@ | _ZNSt6vectorISsSaISsEED2Ev@Base 2.4~dfsg | _ZNSt6vectorISsSaISsEEaSERKS1_@Base 2.4~dfsg | _ZNSt6vectorIiSaIiEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPiS1_EERKi@Base 2.4~dfsg | - _ZNSt6vectorIiSaIiEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPiS1_EEmRKi@Base 2.4~dfsg | + _ZNSt6vectorIiSaIiEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPiS1_EEjRKi@Base 2.4~dfsg-1 | +#MISSING: 2.4~dfsg-1# _ZNSt6vectorIiSaIiEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPiS1_EEmRKi@Base 2.4~dfsg | _ZNSt6vectorIiSaIiEEaSERKS1_@Base 2.4~dfsg | + _ZNSt8_Rb_treeIP11pj_thread_tSt4pairIKS1_PA64_lESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE17_M_insert_unique_ESt23_Rb_tree_const_iteratorIS6_ERKS6_@Base 2.4~dfsg-1 | _ZNSt8_Rb_treeIP11pj_thread_tSt4pairIKS1_PA64_lESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE24_M_get_insert_unique_posERS3_@Base 2.4~dfsg | - _ZNSt8_Rb_treeIP11pj_thread_tSt4pairIKS1_PA64_lESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS6_ERS3_@Base 2.4~dfsg | +#MISSING: 2.4~dfsg-1# _ZNSt8_Rb_treeIP11pj_thread_tSt4pairIKS1_PA64_lESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS6_ERS3_@Base 2.4~dfsg | _ZNSt8_Rb_treeIP11pj_thread_tSt4pairIKS1_PA64_lESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE8_M_eraseEPSt13_Rb_tree_nodeIS6_E@Base 2.4~dfsg | _ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_ERKS6_S8_@Base
Bug#793210: libfontconfig1 missing in openjdk-8-jre-headless
Hi Emmanuel, Thank you for the followup. Looking forward to have libfontconfig1 added in the next version of openjdk-8-jre-headless, so that my projects and others' projects can run smoothly on the latest Java Docker container. Warmest Regards, Joel On 30 Jul 2015, at 9:30 pm, Emmanuel Bourg ebo...@apache.org wrote: Le 29/07/2015 21:22, Joel Chen a écrit : When openjdk-8-jre-headless is used under openjdk-8-jre Docker container, using Font in Java application triggers NullPointerException. Hi Joel, Thank you for the report. It looks like the IcedTea build used for the openjdk-7 package links explicitly against the system fontconfig, the INSTALL file has this mention |1] : * --enable-system-fontconfig: Build and link against the system installation of fontconfig instead of trying to dynamically open it at runtime. and the default value is yes. For the openjdk-8 package we didn't use IcedTea, and the upstream build still doesn't link against fontconfig. The library is simply detected and loaded dynamically in jdk/src/solaris/native/sun/awt/fontpath.c [2]. This explains why the -headless package is missing the dependency. The openjdk-8-jre package is also missing the libfontconfig1 dependency compared to openjdk-7-jre, but it gets it transitively through the dependency on libgtk2.0-0. Now I wonder if we want to add a font dependency on a headless package. It already depends on libfreetype6, so why not libfontconfig1 too after all. Emmanuel Bourg [1] http://icedtea.classpath.org/hg/icedtea7/file/58824316f50a/INSTALL#l120 [2] http://hg.openjdk.java.net/jdk8/jdk8/jdk/file/687fd7c7986d/src/solaris/native/sun/awt/fontpath.c#l595 -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ba26c7.50...@apache.org
Bug#794442: [kde-full] Windows frames disappears!!!!
Package: kde-full Version: 5:84 Severity: critical --- Please enter the report below this line. --- Hi, after the last upgrade session the applications in my KDE Plasma has lost the windows frames. Even if I use alt-tab it is not possible to switch from an application to another one. The only way to get the access to KDE menu' is closing all the applications. I have try to delete rm $HOME/.kde* -Rf without resolving the problem. I have not .xsession in my configuration. I have updated the system setting application (icon) because the previous was not executable. KDE openbox works fine with my previous settings. Command 502 of 4 #apt-show-versions kwin-x11 kwin-x11:amd64/testing 4:5.3.2-3 uptodate kwin-x11:i386 not installed If I install plasma-workspace apt-get removes automatically the following packages kde-plasma-netbook kde-workspace kde-workspace-bin kde-workspace-data kdeartwork-style kdeartwork-theme-window klipper kscreensaver kscreensaver-xsavers kscreensaver-xsavers-webcollage libkactivities-bin openbox-kde-session plasma-desktopthemes-artwork Consider that my kde was perfectly full-operating before some upgrades ago. Please write me if you think I can provide you informations. Thanks for your work Marco Righi --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable dl.google.com 500 stable apt.spideroak.com 500 sid linux.dropbox.com 500 debian packages.linuxmint.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794441: obnam: chunk ... does not exist
Package: obnam Version: 1.13-1 Severity: normal Dear Maintainer, The problem with nonexistent chunks still exists. I have tried to run Your software few times with options: --fsck-fix --fsck-rm-unused --no-fsck-ignore-chunks --no-fsck-skip-dirs --no-fsck-skip-files --no-fsck-skip-generations --no-fsck-skip-per-client-b-trees --no-fsck-skip-shared-b-trees fsck but every time there was a lot of messages like this: chunk ... does not exist checksum whole-file checksum mismatch This means that fsck command does nothing and repository remains broken. Why this command does not remove references pointing to nonexistent chunk when it finds such ones? And what to do with checksum mismatch? Does this mean the file is broken? If so, why do You not remove them? If there are no way to keep repository in consistent state, then we compelled to start new repository every time when it gets broken. This is bad methodology and if there are no other solutions, I am not sure that such backup software is usable at all. This is sad news. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages obnam depends on: ii libc6 2.19-19 ii python2.7.9-1 ii python-cliapp 1.20150701-1 ii python-fuse 2:0.2.1-11 ii python-larch 1.20131130-1 ii python-paramiko 1.15.2-1 ii python-tracing0.8-1 ii python-ttystatus 0.23-1 ii python-yaml 3.11-2 obnam recommends no packages. obnam 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#530671: #3242: mutt: does not want to open dot subdirs via imap anymore
#3242: mutt: does not want to open dot subdirs via imap anymore +--- Reporter: antonio@… | Owner: lucki2791 Type: task | Status: accepted Priority: major | Milestone: 2.0 Component: browser|Version: 1.5.21 Resolution: | Keywords: +--- Changes (by grawity): * cc: grawity@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3242#comment:7 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794441: obnam: chunk ... does not exist
On Mon, Aug 03, 2015 at 11:51:58AM +0300, Vladimir Stavrinov wrote: On Mon, Aug 03, 2015 at 09:53:03AM +0300, Lars Wirzenius wrote: fsck does, indeed, not remove references to missing chunks. It's a missing feature. That feature will be implemented when someone has the time and inclination to do it. Asking why it isn't done yet does not make it happen faster, I'm afraid. The question was not why it isn't done YET, but why they are not removing at all, thinking it is a bug. And Yes, if You treat bug as missing feature, then there are less chances that it happen faster to fix it. I don't understand what you're trying to say. OK, it is up to You how to treat it and what to do or not to do. But the question remains about checksum whole-file checksum mismatch. Is this problem related to non-existent chunks, as they appear all together, one next to other? In other words, should the both problems be solved with the same single fixing, or they are subject for different bug fixings? If a file is missing a chunk, then it's data cannot be restored correctly, and the checksum of the restored data does not match the original file. That's what it means, and yes, it's related to the missing chunk. -- sic transit disci mundi, ergo obnam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794298: asciinema: broken, Unable to upload
I’m attaching this simple patch (created with `git diff https.patch`). -- Marcin W dniu 3 sierpnia 2015 @ 04:29:36, gustavo panizzo (g...@zumbi.com.ar) napisał(a): On Sun, Aug 02, 2015 at 02:42:18 +0200, Marcin Kulik wrote: These issues (https, saving to tmp file) has been addressed in 0.9.9 (the latest version is 1.1.1 btw). Versions 0.9.8 also use documented, open format for the recordings. I have just re-enabled support for 0.9.8 on the server side to fix this problem, but I’d like to stop supporting it in the near future (unsafe http connection is the #1 reason). great, thanks Is there a chance to update this Debian package to the latest upstream version in not so distant future? the package is too old for 2 reasons - not long ago jessie was released, before that we were in freeze - 0.9.8 is the latest python version of asciinema. I never packaged a go application for debian before, it is on my TODO list but it will take more time (it is a new thing for me) Daniel, I'm sorry you found the program does not work, I haven't use it in a while so I wasn't aware of the breakage. Marcin, could you release a last python version, a patch is fine too, which uses https? I could upload that right away while I work on packaging the latest version -- Marcin -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa https.patch Description: Binary data
Bug#794444: python3-networkx should conflict with python3-pygraphviz
Package: python3-networkx Version: 1.9.1-1 Severity: normal Hi, python3-networkx is able to use python3-pygraphviz as wells as python3-pydot for drawing dot graphs. If both are installed, then the former will be used. Unfortunately it seems that python3-pygraphviz is unable to render graphs with vertex attributes which makes it unfit for drawing all but the most trivial graphs. Since the presence of python3-pygraphviz will make python3-networkx use it over python3-pydot (which does not suffer from this problem), I suggest that python3-networkx conflicts with python3-pygraphviz until the problem is either fixed in networkx or pygraphviz upstream. To test the problem yourself, try to do the following with python3-pygraphviz installed: python3 -c 'import networkx as nx; G=nx.Graph();G.add_node(1,foo=bar);nx.write_dot(G, out)' The command will never terminate. It on the other hand immediately finishes (as expected) if python3-pygraphviz is not installed but python3-pydot is. This bug is causing problems with my package botch which depends on python3-networkx for graph drawing. Instead of botch conflicting with python3-pygraphviz, I'd like to see this conflict in python3-networkx itself. Thanks! cheers, josch -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, arm64 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-networkx depends on: ii python3-decorator 3.4.0-2 pn python3:anynone Versions of packages python3-networkx recommends: pn python3-numpy none ii python3-pkg-resources 18.0.1-1 pn python3-scipy none ii python3-yaml 3.11-2 python3-networkx 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#794440: override_dh_auto_build needed to avoid the use of CLI
severity 794440 normal
thanks
There are files generated by CLI in the source code already.
So we just need to change those .cli file's timestamp to an
early time to avoid the calling of CLI at build time.
Add the following in rules file solve the problem:
override_dh_auto_build:
find $(CURDIR) -regex .*\.cli -exec touch -d 2000-01-01 00:00:00 {} \;
dh_auto_build
And some packages is needed at build time to generate pdf doc file:
ghostscript
html2ps
No problem encountered when building this package with gcc 5.2 and it's OK to
build libkolabxml.
Bug#794441: obnam: chunk ... does not exist
On Mon, Aug 03, 2015 at 09:30:06AM +0300, Vladmimir Stavrinov wrote: This means that fsck command does nothing and repository remains broken. Why this command does not remove references pointing to nonexistent chunk when it finds such ones? fsck does, indeed, not remove references to missing chunks. It's a missing feature. That feature will be implemented when someone has the time and inclination to do it. Asking why it isn't done yet does not make it happen faster, I'm afraid. -- sic transit disci mundi, ergo obnam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777778: [Aptitude-devel] Bug#794406: g++: Non-deterministic /usr/include/c++/5/bits/basic_string.h:121:53: internal compiler error: Segmentation fault when compiling aptitude 0.7-1
Hi Matthias, Matthias Klose wrote: I've just tried to build the upcoming aptitude 0.7-1 inside a pbuilder chroot. I've first recompiled the following source packages with gcc-5/5.2.1-14 respectively g++-5/5.2.1-14 and against libstdc++6/5.2.1-14 and installed the (necessary) packages built that way: [...] ok, both locally and on the Ubuntu buildds in a wily environment, I get another build failure. https://launchpad.net/~doko/+archive/ubuntu/toolchain/+packages however, this is with a rebuilt boost1.58, libsigc++2.0, libapt-pkg-dev, xapian-core, cppunit. Ok, so the difference to my (in the second run) successful build inside pbuilder are: * No rebuild of libsigc++2.0 * Boost 1.55 We (Manuel and me) expect potential issues with Boost 1.58 (as usual with Boost version bumps). Maybe it's them. I'll check as soon as I find time for such a rebuild-chain. xapian and boost were uploaded today, bug reports for libsigc++ I assume you mean libsigc++-2.0. (libsigc++ has been removed from Sid in 2014: https://bugs.debian.org/735559; reported by Manuel) Anyway, that will save me at least the xapian-core rebuild. :-) and cppunit exist I don't see any such bug for cppunit, actually I see no cppunit bug at all: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cppunit Ah, did you mean library transition bugs? Like https://bugs.debian.org/791013? (if maintainers don't reply, maybe you could coordinate these transitions?). I have no hands-on experience with library transitions and I can't code in C++. So I don't think, I'm a good choice for that. So I think unstable is not yet ready to do this rebuild. *nod* My current plan is to upload aptitude once all the reverse dependencies, I had to rebuild, are BinNMUed or had a fresh, gcc5-related upload (and are built on all architectures preferably). (Cc'ing aptitude's FTBFS-with-gcc5 bug #78 instead of just its maintainer mailing-list.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794420: Test file
I tried to send the test file as base64-encoded email yesterday (71KB, around 16 A4 pages when printed) but it never showed up in the bug report; I guess it might have been too large. Do you have any other means to upload test files? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793052: Info received (Bug#793052: Disconnected IMAP stops getting mail)
I upgraded these three packages to unstable and the problem still exists:
root@phalaris:~# dpkg -l | grep akonadi | grep 1.13 | awk '{print $2, $3}'
akonadi-backend-mysql 1.13.0-7
akonadi-server 1.13.0-7
libakonadiprotocolinternals1 1.13.0-7
Apparently interval mail check has no bearing on its presence, either.
On Saturday, August 01, 2015 08:51:04 PM you wrote:
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian/Kubuntu Qt/KDE Maintainers debian-qt-...@lists.debian.org
If you wish to submit further information on this problem, please
send it to 793...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794448: No user _apt, can not drop rights
Package: apt
Version: 1.1~exp8
Severity: grave
Hello,
this morning, apt started segfaulting out of blue. My current workaround
was to install the experimental version and run apt-cache gencaches
then, at least, apt-cache stopped segfaulting. But apt-get still cannot
run an update, see below, because apparently _apt user was not
created... and no idea why.
Note: I had to install manually, maybe this fact plays a role here.
I also kept the coredumps and /var/{cache,lib}/apt folder snapshots from
the segfaulting version for post-mortem analysis.
Regards,
Eduard.
zonk: /var/lib/apt $ dpkg -i /download/apt_1.1~exp8_amd64.deb
(Lese Datenbank ... 837600 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../apt_1.1~exp8_amd64.deb ...
Entpacken von apt (1.1~exp8) über (1.0.9.10) ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von apt:
apt hängt ab von libapt-pkg4.15 (= 1.1~exp5); aber:
Paket libapt-pkg4.15 ist nicht installiert.
dpkg: Fehler beim Bearbeiten des Paketes apt (--install):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
Trigger für man-db (2.7.0.2-5) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
apt
zonk: /var/lib/apt $ dpkg -i /download/libapt-pkg4.15_1.1~exp8_amd64.deb
Vormals nicht ausgewähltes Paket libapt-pkg4.15:amd64 wird gewählt.
(Lese Datenbank ... 837599 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libapt-pkg4.15_1.1~exp8_amd64.deb ...
Entpacken von libapt-pkg4.15:amd64 (1.1~exp8) ...
libapt-pkg4.15:amd64 (1.1~exp8) wird eingerichtet ...
Trigger für libc-bin (2.19-19) werden verarbeitet ...
zonk: /var/lib/apt $ apt-get update
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
E: Method gave invalid 400 URI Failure message: No user _apt, can not drop
rights
zonk: /var/lib/apt $ grep apt /etc/passwd
aptproxy:x:120:65534::/var/cache/apt-proxy:/bin/false
apt-cacher-ng:x:121:124::/var/cache/apt-cacher-ng:/bin/bash
-- Package-specific info:
-- apt-config dump --
APT ;
APT::Architecture amd64;
APT::Build-Essential ;
APT::Build-Essential:: build-essential;
APT::Install-Recommends 1;
APT::Install-Suggests 0;
APT::Sandbox ;
APT::Sandbox::User _apt;
APT::Update ;
APT::Update::Post-Invoke ;
APT::Update::Post-Invoke:: [ ! -x
/usr/lib/ia32-libs-tools/update-arch-all.list ] ||
/usr/lib/ia32-libs-tools/update-arch-all.list;
APT::Update::Post-Invoke-Success ;
APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] ||
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt
org.debian.apt.CacheChanged || true;
APT::Update::Post-Invoke-Success:: /usr/bin/test -e
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service
/usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call
--system --dest org.freedesktop.PackageKit --object-path
/org/freedesktop/PackageKit --timeout 4 --method
org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo
/dev/null;
APT::NeverAutoRemove ;
APT::NeverAutoRemove:: ^firmware-linux.*;
APT::NeverAutoRemove:: ^linux-firmware$;
APT::NeverAutoRemove:: ^linux-image-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-image-4\.1\.3+$;
APT::NeverAutoRemove:: ^linux-headers-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-headers-4\.1\.3+$;
APT::NeverAutoRemove:: ^linux-image-extra-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-image-extra-4\.1\.3+$;
APT::NeverAutoRemove:: ^linux-signed-image-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-signed-image-4\.1\.3+$;
APT::NeverAutoRemove:: ^kfreebsd-image-4\.1\.2+$;
APT::NeverAutoRemove:: ^kfreebsd-image-4\.1\.3+$;
APT::NeverAutoRemove:: ^kfreebsd-headers-4\.1\.2+$;
APT::NeverAutoRemove:: ^kfreebsd-headers-4\.1\.3+$;
APT::NeverAutoRemove:: ^gnumach-image-4\.1\.2+$;
APT::NeverAutoRemove:: ^gnumach-image-4\.1\.3+$;
APT::NeverAutoRemove:: ^.*-modules-4\.1\.2+$;
APT::NeverAutoRemove:: ^.*-modules-4\.1\.3+$;
APT::NeverAutoRemove:: ^.*-kernel-4\.1\.2+$;
APT::NeverAutoRemove:: ^.*-kernel-4\.1\.3+$;
APT::NeverAutoRemove:: ^linux-backports-modules-.*-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-backports-modules-.*-4\.1\.3+$;
APT::NeverAutoRemove:: ^linux-tools-4\.1\.2+$;
APT::NeverAutoRemove:: ^linux-tools-4\.1\.3+$;
APT::NeverAutoRemove:: ^postgresql-;
APT::VersionedKernelPackages ;
APT::VersionedKernelPackages:: linux-image;
APT::VersionedKernelPackages:: linux-headers;
APT::VersionedKernelPackages:: linux-image-extra;
APT::VersionedKernelPackages:: linux-signed-image;
APT::VersionedKernelPackages:: kfreebsd-image;
Bug#794426: [Aptitude-devel] Bug#794426: aptitude: Fails to update sources
Control: tag -1 + moreinfo Hi Javier, Javier Barroso wrote: $ LANG=C sudo apt update ... Des:8 http://ftp.fi.debian.org sid/main Sources 2015-08-02-2047.38.pdiff [19,5 kB] This is not the file which fails below: E: Could not open file /var/lib/apt/lists/ftp.fi.debian.org_debian_dists_sid_contrib_source_Sources.IndexDiff - open (2: No such file or directory) javi@Doraemon:~$ ls -l \ /var/lib/apt/lists/ftp.fi.debian.org_debian_dists_sid_contrib_source_Sources.diff_Index -rw-r--r-- 1 root root 7819 jul 29 22:52 /var/lib/apt/lists/ftp.fi.debian.org_debian_dists_sid_contrib_source_Sources.diff_Index [...] It should work, like on apt, apt-get or cupt Any chance that you have apt 1.1 from experimental installed? That one doesn't yet work well together with aptitude. This looks similar to https://bugs.debian.org/764506 but there are also other apt-1.1-related bugs. I suppose I can remove next line on sources.list: /etc/apt/sources.list:deb-src http://ftp.fi.debian.org/debian/ sid main No. This is the line for sid/main. What failed was the line for sid/contrib. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794447: ITP: pb-genomicconsensus -- Pacific Biosciences variant and consensus caller
Package: wnpp Severity: wishlist Owner: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Control: block 787977 by ! * Package name: pb-genomicconsensus Version : 1.0.0 Upstream Author : Pacific Biosciences dev...@pacificbiosciences.com * URL : https://github.com/PacificBiosciences/GenomicConsensus * License : BSD Programming Lang: Python Description : Pacific Biosciences variant and consensus caller The GenomicConsensus package provides Quiver, Pacific Biosciences' flagship consensus and variant caller. Quiver is an algorithm that finds the maximum likelihood template sequence given PacBio reads of the template. These reads are modeled using a conditional random field approach that prescribes a probability to a read given a template sequence. In addition to the base sequence of each read, Quiver uses several additional quality value covariates that the base caller provides. This package is part of the SMRTAnalysis suite (#787977), to be built and maintained by the Debian Med team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794446: FTBFS on most architectures
Package: afl Version: 1.83b-1+b2 Severity: serious Justification: fail to build from source Afl currently FTBFS: cut [*] Testing the CC wrapper and instrumentation output... unset AFL_USE_ASAN AFL_USE_MSAN AFL_DEFER_FORKSRV; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. AFL_CC=clang ../afl-clang-fast -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\/usr/lib/afl\ -DBIN_PATH=\/usr/bin\ -DVERSION=\1.83b\ ../test-instr.c -o test-instr -Wl,-z,relro error: unable to load plugin '../afl-llvm-pass.so': '../afl-llvm-pass.so: undefined symbol: _ZNK4llvm10ModulePass17createPrinterPassERNS_11raw_ostreamERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE' make[1]: *** [test_build] Error 1 /cut I'll go into that in a couple of days. DS -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages afl depends on: ii libc6 2.19-19 Versions of packages afl recommends: ii afl-clang 1.83b-1+b2 ii g++4:4.9.2-4 ii gcc4:4.9.2-4 afl 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#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus
On 2015-04-30 23:10, Matthias Klose wrote: On 04/30/2015 10:43 PM, Daniel Serpell wrote: Currently, gcc-5 packages are really big because the files under /usr/lib/gcc/x86_64-linux-gnu/5 are not stripped, and each one of lto1, cc1 and cc1plus is about 130MB. Please, can those files be striped in the default installation? I'd like to avoid this, and only change that near the next Debian release. These binaries are linked against libbacktrace to provide a verbose backtrace on internal compiler errors, which you can't get with stripped binaries. If that's not possible could you please at least change these binaries to use compressed debug sections at least? That should save quite some space already. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746491: vim: Ctrl+PgUp (and Down) does not switch beteen tabs
On Sun, Aug 02, 2015 at 08:49:49PM -0400, James McCoy wrote: Hmm. I thought gnome-terminal captured C-PgUp/C-PgDown, but I know xterm doesn't. True (I didn't know). Can you try with vim -u NONE -N -p ... and see if that works? I tried and, when I realized that without vimrc it worked, I started playing with my (bare) .vimrc and I found that I did place a colorscheme setting __before__ the syntax on. Swapping them makes Ctrl+PgUp||PGDown working (in xterm). I know my settings din't make any sense and I'm sorry for the inconvenience. However, this side-effect looks a bit awkward. Do you think it deserves some attention? Cheers, Alberto -- Alberto Maurizi a.maur...@isac.cnr.it ISAC-CNR Phone n. +39 051 639 9615 via Gobetti 101 Fax n. +39 051 639 9658 40129 Bologna, Italy home page: http://bolchem.isac.cnr.it/staff:alberto_maurizi.do bolchem project:http://bolchem.isac.cnr.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790327: openturns: FTBFS on mipsel package requires more than 1GB RAM; do not build on mips/mipsel. Stop.
Hi. Please, can you take a look on the patch? It is building ok on mips now. Thanks, Gustavo Prado Alkmim Bacharel em Ciência da Computação (UFLA) Doutorando em Ciência da Computação (UNICAMP) -- Do que adianta para o homem ganhar o mundo e perder sua alma??? 2015-07-22 4:49 GMT-03:00 Gustavo Prado Alkmim alk...@ic.unicamp.br: Hi. Did you have time to take a look on the patch? With this patch, openturns is building on mipsel. Thanks, Gustavo Prado Alkmim Bacharel em Ciência da Computação (UFLA) Doutorando em Ciência da Computação (UNICAMP) -- Do que adianta para o homem ganhar o mundo e perder sua alma??? 2015-07-11 18:12 GMT-03:00 Gustavo Prado Alkmim alk...@ic.unicamp.br: Hi. Attached is a patch with the fix for this bug. I enabled the build on mipsel. I made a test on my ci20 board and it built fine. Tooked 46 hours, ~6GB of space, 1 GB of RAM and ~500GB of swap memory 2015-06-28 3:31 GMT-03:00 Gustavo Prado Alkmim alk...@ic.unicamp.br: Package: openturns Version: 1.5-7 Severity: serious Justification: fails to build from source Dear Maintainer, Package is failing to build on buildd. I'm working on a fix and I will attach it as soon as possible. Full log is attached. Build Log tail: dpkg-buildpackage: source package openturns dpkg-buildpackage: source version 1.5-7 dpkg-buildpackage: source distribution unstable dpkg-source --before-build openturns-1.5 dpkg-buildpackage: host architecture mipsel fakeroot debian/rules clean DEB_BUILD_OPTIONS:environment=parallel=5 debian/rules:47: *** This package requires more than 1GB RAM; do not build on mips/mipsel. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus
On 2015-08-03 09:57, Basile Starynkevitch wrote: On Mon, Aug 03, 2015 at 09:47:33AM +0200, Aurelien Jarno wrote: On 2015-04-30 23:10, Matthias Klose wrote: On 04/30/2015 10:43 PM, Daniel Serpell wrote: Currently, gcc-5 packages are really big because the files under /usr/lib/gcc/x86_64-linux-gnu/5 are not stripped, and each one of lto1, cc1 and cc1plus is about 130MB. Please, can those files be striped in the default installation? I'd like to avoid this, and only change that near the next Debian release. These binaries are linked against libbacktrace to provide a verbose backtrace on internal compiler errors, which you can't get with stripped binaries. If that's not possible could you please at least change these binaries to use compressed debug sections at least? That should save quite some space already. I would believe that is not easily possible. I don't know the detailed behavior of libbacktrace, but it is using parsing the DWARF debug information of the binaries (cc1, cc1plus, ...), so I guess you'll need to patch (significantly) libbacktrace to compress the debug sections. compressed debug sections is kind of standard these days, so libbacktrace should support that. BTW, I don't see the size of cc1 etc... as an issue. Compilers are useful on development machines, and these are usually not very small (and have enought disk space). This adds roughly 1GB to the size of a chroot used on the Debian build daemons. As it is unpacked from a tarball for each package to build, it has a significant impact on the time needed to unpack the chroot. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794237: openconnect: Does not work with network-manager 1.0.4
On Sat, 2015-08-01 at 11:52 -0400, Mike Miller wrote: Control: tags -1 + moreinfo On Fri, Jul 31, 2015 at 16:59:00 +0300, Matti Koskimies wrote: Debian sid updated network-manager from 1.0.2 to 1.0.4 and after that openconnect didn't work. I downgraded network-manager to 1.0.2 and openconnect works again. Works for me. Can you define didn't work? Doesn't show up in NM? Shows up but doesn't connect? What versions of all OpenConnect and NM packages do you have? Didn't work means I couldn't connect to the addresses I expect to connect to using VPN. And almost no network connections worked. Versions: network-manager 1.0.4-1 openconnect: 7.06-2 I did a little research and found out that the routing table was different with different NM versions installed after starting openconnect. So I found a workaround: ip route add default dev tun0 scope link After that command all connections work as expected. What might be the reason for this? -- Matti K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794454: src:dh-make-golang has incorrect Vcs-*
Package: src:dh-make-golang Version: 0.0~git20150726.0.fc4210a-1 Tags: patch Vcs-Git and Vcs-Browser point to golang-github-debian-dh-make-golang instead of just dh-make-golang. I've attached a simple patch which could be used to correct these. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 From 882bd38e0f324991b0593270ff1151adc94b6e74 Mon Sep 17 00:00:00 2001 From: Tianon Gravi admwig...@gmail.com Date: Mon, 3 Aug 2015 01:25:29 -0700 Subject: [PATCH] Fix Vcs-* headers --- debian/control | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index 78fd304..59a4fa0 100644 --- a/debian/control +++ b/debian/control @@ -12,8 +12,8 @@ Build-Depends: debhelper (= 9), git Standards-Version: 3.9.6 Homepage: https://github.com/Debian/dh-make-golang -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-github-debian-dh-make-golang.git;a=summary -Vcs-Git: git://anonscm.debian.org/pkg-go/packages/golang-github-debian-dh-make-golang.git +Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/dh-make-golang.git +Vcs-Git: git://anonscm.debian.org/pkg-go/packages/dh-make-golang.git Package: dh-make-golang Architecture: any -- 2.4.6
Bug#794455: obnam: locked repository
Package: obnam Version: 1.13-1 Severity: normal Dear Maintainer, Every time obnam terminated by external signal (Ctrl-C for example) it remain repository locked. Is unlocking on termination is missing feature too, or leaving it locked is intent feature? I think locking only makes sense while obnam is running, does not it? -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages obnam depends on: ii libc6 2.19-19 ii python2.7.9-1 ii python-cliapp 1.20150701-1 ii python-fuse 2:0.2.1-11 ii python-larch 1.20131130-1 ii python-paramiko 1.15.2-1 ii python-tracing0.8-1 ii python-ttystatus 0.23-1 ii python-yaml 3.11-2 obnam recommends no packages. obnam 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#794441: obnam: chunk ... does not exist
On Mon, Aug 03, 2015 at 09:53:03AM +0300, Lars Wirzenius wrote: fsck does, indeed, not remove references to missing chunks. It's a missing feature. That feature will be implemented when someone has the time and inclination to do it. Asking why it isn't done yet does not make it happen faster, I'm afraid. The question was not why it isn't done YET, but why they are not removing at all, thinking it is a bug. And Yes, if You treat bug as missing feature, then there are less chances that it happen faster to fix it. OK, it is up to You how to treat it and what to do or not to do. But the question remains about checksum whole-file checksum mismatch. Is this problem related to non-existent chunks, as they appear all together, one next to other? In other words, should the both problems be solved with the same single fixing, or they are subject for different bug fixings? ### Vladimir Stavrinov ### -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794457: O: dnswalk -- Checks dns zone information using nameserver lookups
Package: wnpp This package did not receive any maintainer upload since 2003 (12 years!), and so is de-facto orphaned. The last upload done as QA upload: walk (2.0.2.dfsg.1-1) unstable; urgency=medium * QA upload orphaning the package. Closes: #452757 * Update package to modern standards. * Add a watch file. * Convert .diff.gz changes into fix-shebangs.patch. * Add fix-defined-array-is-deprecated.patch to fix warnings with recent Perl. Closes: #658998 * Add fix-warnings-about-soa-contact-name.patch to fix another problem reported in the upstream bug tracker (problem generated by behaviour change in Net::DNS 0.69). * Add Vcs-Git and Vcs-Browser fields pointing to collab-maint. -- Raphaël Hertzog hert...@debian.org Tue, 28 Jul 2015 21:38:51 +0200 The extended description: Description: Checks dns zone information using nameserver lookups dnswalk is a DNS debugger. It performs zone transfers of specified domains, and checks the database in numerous ways for internal consistency, as well as accuracy. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature
Bug#794445: menu item Resize bound to the item Move
Package: gnome Version: 1:3.14+3 Severity: important Tags: upstream menu item Resize bound to the item Move -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome depends on: ii alacarte 3.11.91-2 ii avahi-daemon 0.6.31-5 ii bijiben3.14.2-1+b1 ii brasero3.11.4-1.1 ii cheese 3.14.1-2 ii cups-pk-helper 0.2.5-2+b1 ii desktop-base 8.0.2 ii evolution 3.12.9~git20141130.241663-1+b1 ii evolution-plugins 3.12.9~git20141130.241663-1+b1 ii file-roller3.14.1-1 ii gedit 3.14.0-3 ii gedit-plugins 3.14.0-2 ii gimp 2.8.14-1+b1 ii gnome-clocks 3.14.1-1 ii gnome-color-manager3.14.1-1 ii gnome-core 1:3.14+3 ii gnome-documents3.14.2-1 ii gnome-games1:3.14+3 ii gnome-getting-started-docs 3.14.1-1 ii gnome-logs 3.14.2-1 ii gnome-maps 3.14.1.2-1 ii gnome-music3.14.1-1 ii gnome-nettool 3.8.1-1 ii gnome-orca 3.14.0-4 ii gnome-photos 3.14.2-1 ii gnome-shell-extension-weather 0~20140924.git7e28508-1 ii gnome-sound-recorder 3.14.0.1-1 ii gnome-tweak-tool 3.14.2-2 ii goobox 3.3.1-6 ii gstreamer1.0-libav 1.4.4-2 ii gstreamer1.0-plugins-ugly 1.4.4-2+b1 ii hamster-applet 2.91.3+git20120514.b9fec3e1-1 ii inkscape 0.48.5-3 ii libgtk2-perl 2:1.2492-4 ii libreoffice-calc 1:4.3.3-2+deb8u1 ii libreoffice-evolution 1:4.3.3-2+deb8u1 ii libreoffice-gnome 1:4.3.3-2+deb8u1 ii libreoffice-impress1:4.3.3-2+deb8u1 ii libreoffice-writer 1:4.3.3-2+deb8u1 ii nautilus-sendto3.8.2-1 ii network-manager-gnome 0.9.10.0-2 ii polari 3.14.1-1 ii rhythmbox 3.1-1 ii rhythmbox-plugin-cdrecorder3.1-1 ii rhythmbox-plugins 3.1-1 ii rygel-playbin 0.24.2-1+b1 ii rygel-tracker 0.24.2-1+b1 ii seahorse 3.14.0-2 ii simple-scan3.14.0-1 ii telepathy-gabble 0.18.3-1+b1 ii telepathy-rakia0.8.0-3 ii telepathy-salut0.8.1-4 ii totem-plugins 3.14.0-2 ii transmission-gtk 2.84-0.2 ii vinagre3.14.1-1 ii xdg-user-dirs-gtk 0.10-1 Versions of packages gnome recommends: pn gnome-software none Versions of packages gnome suggests: pn iceweasel-l10n-all none pn xul-ext-adblock-plus none pn xul-ext-gnome-keyring none Versions of packages gnome-core depends on: ii adwaita-icon-theme 3.14.0-2 ii at-spi2-core 2.14.0-1 ii baobab 3.14.1-1 ii caribou0.4.15-1 ii caribou-antler 0.4.15-1 ii dconf-gsettings-backend0.22.0-1 ii dconf-tools0.22.0-1 ii empathy3.12.7-1 ii eog3.14.1-1 ii evince 3.14.1-2 ii evolution-data-server 3.12.9~git20141128.5242b0-2+deb8u2 ii fonts-cantarell0.0.16-1 ii gdm3 3.14.1-7 ii gkbd-capplet 3.6.0-1 ii glib-networking2.42.0-2 ii gnome-backgrounds 3.14.1-1 ii gnome-bluetooth3.14.0-2 ii gnome-calculator 3.14.1-1 ii gnome-contacts 3.14.1-1 ii gnome-control-center 1:3.14.2-3 ii gnome-dictionary 3.14.1-1 ii gnome-disk-utility 3.12.1-1+b1 ii gnome-font-viewer 3.14.0-2 ii gnome-keyring 3.14.0-1+b1 ii gnome-menus3.13.3-6 ii gnome-online-accounts 3.14.2-1 ii gnome-online-miners3.14.0-2 ii gnome-packagekit 3.14.0-1 ii gnome-screenshot 3.14.0-1 ii gnome-session 3.14.0-2 ii gnome-settings-daemon 3.14.2-3 ii gnome-shell3.14.4-1~deb8u1 ii gnome-shell-extensions 3.14.2-1 ii gnome-sushi3.12.0-2+b1 ii gnome-system-log 3.9.90-2 ii gnome-system-monitor 3.14.1-1 ii gnome-terminal 3.14.1-1+deb8u1 ii gnome-themes-standard 3.14.2.2-1 ii gnome-user-guide 3.14.1-1
Bug#794449: broken for boolean values
Package: python-memcache Version: 1.56-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi the 1.56 release introduces failure when setting boolean values: https://github.com/linsomniac/python-memcached/issues/75 This has been fixed upstream: https://github.com/linsomniac/python-memcached/commit/664bd3e23fe500fbde4c70636e2d24c8fd2f35af And the fix is part of 1.57, can you please package it? - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-memcache depends on: ii python-six 1.9.0-3 pn python:any none python-memcache recommends no packages. Versions of packages python-memcache suggests: pn memcached none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVvxgpAAoJEJwnsxNCt1EdcUgP/0XvHjfdwO3sgxbfhbluEBcD 6RAG03KDuTg119nwXab+hfsT+/Me3lOs6w4GWe3Rb7x68udPig1lYAXOE16fSniv t884x2lr20uDVPQBk7VX+hn0S6qlSY4WxKsbzZMwmtj+6rQnflFxmW6WYTU29UuB HcEZlQDyy+jo8WS7zTRc1IOlJJVLWTUfNCZzfrg5fjrY6CPVaKbA24UnUso4UqXk yD6gW0om1DK7Iq7KYvGGjXcd+5dNt/0o5u21oOWXAdGQlU2w7lDgefukdqcKR7wN A0nxa299ifs2x2+PsK32ds0WSuPGESscEQQlRdJYFfOPoSyOopUzjo9WjVZy6f6h RozOfwE7w7qXkwCCzXJht80mvNmlNtsDA//r3Xx/6JLS3JeBubxVWKZiJdprY6c8 bvbaQlNByODhafL/KMHx/6Tm4p5LG8CJnggY72uvn7HT+0uLYA5At2GKImJx98rR PeqOA2fV5aFYT7OEnfln8vagD5+xa0H6HJMKfzzcFqup3J+GkeSkt2Z+a2ffKSvX 7HN1dx1auqvrkyv0c4Be9oTmJM+vkjKbQkpfjVqKncaow/fuiIVJW4FLDSi4o/1D CDgsIV+kSSPMM0n9URegiopmPmsPYIdiQ7oicPSfrm6V2ymv3q78VtbN8yOVxNFi SdKQEdcLcZafqXrdBJr7 =v7DQ -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#794451: systemd openafs-client.service causes ordering cycles
* Sergio Gelato [2015-08-03 09:53:12 +0200]: sysinit.target depends on all scripts in /etc/init.d/ that do not have a systemd counterpart Actually the problem only affects those scripts which also have # Default-Start: S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794443: octave: should not recommend libopenblas-base
Package: octave Version: 3.8.2-4 Severity: normal Dear Maintainer, Octave crashes when inverting matrices sized 10x10 or bigger if libopenblas-base is installed. And after I remove libopenblas-base, octave does not crash. Additional info: GNU Octave bug #45651 http://savannah.gnu.org/bugs/?45651#comment4 -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages octave depends on: ii default-jre-headless 2:1.7-52 ii libamd2.3.11:4.2.1-3 ii libarpack2 3.1.5-3 ii libblas3 [libblas.so.3]1.2.20110419-10 ii libc6 2.19-18 ii libcamd2.3.1 1:4.2.1-3 ii libccolamd2.8.01:4.2.1-3 ii libcholmod2.1.21:4.2.1-3 ii libcolamd2.8.0 1:4.2.1-3 ii libcxsparse3.1.2 1:4.2.1-3 ii libfftw3-double3 3.3.4-2 ii libfftw3-single3 3.3.4-2 ii libfltk-gl1.3 1.3.2-6+b1 ii libfltk1.3 1.3.2-6+b1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgcc11:4.9.2-10 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglpk36 4.55-1 ii libglu1-mesa [libglu1] 9.0.0-2 ii libgomp1 4.9.2-10 ii libgraphicsmagick++3 1.3.20-3+deb8u1 ii libgraphicsmagick3 1.3.20-3+deb8u1 ii liblapack3 [liblapack.so.3]3.5.0-4 ii liboctave2 3.8.2-4 ii libopenblas-base [liblapack.so.3] 0.2.12-1 ii libqhull6 2012.1-5 ii libqrupdate1 1.1.2-1 ii libqscintilla2-11 2.8.4+dfsg-1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libstdc++6 4.9.2-10 ii libumfpack5.6.21:4.2.1-3 ii libx11-6 2:1.6.2-3 ii octave-common 3.8.2-4 ii texinfo5.2.0.dfsg.1-6 Versions of packages octave recommends: ii gnuplot-x11 4.6.6-2 ii libopenblas-base 0.2.12-1 ii pstoedit 3.62-2+b1 Versions of packages octave suggests: ii octave-doc 3.8.2-4 pn octave-htmldoc none pn octave-info none -- no debconf information
Bug#794443: [Pkg-octave-devel] Bug#794443: octave: should not recommend libopenblas-base
Control: fixed -1 4.0.0-3 * Wang S wangs...@inhand.com.cn [2015-08-03 14:39]: Package: octave Version: 3.8.2-4 Severity: normal Octave crashes when inverting matrices sized 10x10 or bigger if libopenblas-base is installed. And after I remove libopenblas-base, octave does not crash. Additional info: GNU Octave bug #45651 http://savannah.gnu.org/bugs/?45651#comment4 I cannot reproduce this bug in Octave 4.0: $ dpkg -l libopenblas-base | grep ^ii ii libopenblas-base 0.2.14-1 i386 Optimized BLAS (linear algebra) library (shared library) $ octave-cli --version | grep version GNU Octave, version 4.0.0 $ echo 'inv(randn(12)); printf(Got here\n)' | octave-cli -q Got here I am hereby marking this bug as fixed in version 4.0.0-3. Should we actually close it? Rafael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793249: innoextract: change of type in system_error might break with GCC-5
tags 793249 + confirmed This will most likely be an issue if I undertood the issue correctly. On 2015-07-22 15:33, Matthias Klose wrote: Package: src:innoextract Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: gcc-pr66145 GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. See https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29 for further information. To build with GCC 5,install the gcc, g++, gfortran, ... packages from experimental (apt-get -t experimental install g++). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794456: icedove-dev: ABI defined by ical.h changes at every build
Package: icedove-dev
Version: 38.0.1-1
Severity: important
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
Hi!
During a build reproducibility test, it was found that the `ical.h`
header provided by the icedove-dev package defines an ABI that changes
with every build. That probably makes it quite unusable:
[…]
├── icedove-dev_38.0.1-1_amd64.deb
│ ├── control.tar.gz
│ │ ├── control.tar
│ │ │ ├── md5sums
│ │ │ │┄ Files in package differs
│ │ │ ╵
│ │ ╵
│ ├── data.tar.xz
│ │ ├── data.tar
│ │ │ ├── ./usr/include/icedove/ical.h
│ │ │ │ @@ -1055,44 +1055,44 @@
│ │ │ │ void icalvalue_set_attach (icalvalue *value, icalattach *attach);
│ │ │ │ icalattach *icalvalue_get_attach (const icalvalue *value);
│ │ │ │
│ │ │ │ void icalvalue_reset_kind(icalvalue* value);
│ │ │ │
│ │ │ │ typedef enum icalvalue_kind {
│ │ │ │ ICAL_ANY_VALUE=5000,
│ │ │ │ -ICAL_INTEGER_VALUE=5001,
│ │ │ │ -ICAL_URI_VALUE=5002,
│ │ │ │ -ICAL_BINARY_VALUE=5003,
│ │ │ │ -ICAL_DATETIME_VALUE=5004,
│ │ │ │ -ICAL_TRIGGER_VALUE=5005,
│ │ │ │ -ICAL_TEXT_VALUE=5006,
│ │ │ │ -ICAL_CALADDRESS_VALUE=5007,
│ │ │ │ -ICAL_XLICCLASS_VALUE=5008,
│ │ │ │ -ICAL_REQUESTSTATUS_VALUE=5009,
│ │ │ │ -ICAL_METHOD_VALUE=5010,
│ │ │ │ -ICAL_ACTION_VALUE=5011,
│ │ │ │ +ICAL_URI_VALUE=5001,
│ │ │ │ +ICAL_TEXT_VALUE=5002,
│ │ │ │ +ICAL_QUERYLEVEL_VALUE=5003,
│ │ │ │ +ICAL_UTCOFFSET_VALUE=5004,
│ │ │ │ +ICAL_XLICCLASS_VALUE=5005,
│ │ │ │ +ICAL_DATETIME_VALUE=5006,
│ │ │ │ +ICAL_STRING_VALUE=5007,
│ │ │ │ +ICAL_X_VALUE=5008,
│ │ │ │ +ICAL_STATUS_VALUE=5009,
│ │ │ │ +ICAL_TRANSP_VALUE=5010,
│ │ │ │ +ICAL_INTEGER_VALUE=5011,
│ │ │ │ ICAL_GEO_VALUE=5012,
[…]
Source:
https://reproducible.debian.net/dbdtxt/unstable/amd64/icedove_38.0.1-1.debbindiff.txt
This bug reminds a lot of #773916.
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Description: Digital signature
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates a disfonctionnement of any window kde
Followup-For: Bug #793026 Package: kde-window-manager Version: 4:5.3.2-3 I am not sure if it's the same bug, but: After apt-get update apt-get dist-upgrade I experienced the same symptoms. Upon trying to repeat the upgrade (hoping that the bug was fixed in the meantime, I noticed that several packages were held back, among them kde-standard. Also a few dozen packages (KDE-related) were removed byt `apt-get autoremove` and reinstalled by `apt-get dist- upgrade`, if I remember correctly Manually upgrading/installing the withheld packages with apt-get install kde-standard fixed the problem for me. A small excerpt from my /var/log/apt/history.log (showing the contradicting actions of dist-upgrade and autoremove before manual upgrade of kde-standard and the manual upgrade of the latter): Start-Date: 2015-08-03 09:10:36 Commandline: apt-get autoremove Remove: liboxygenstyle5-5:amd64 (5.3.2-3), kwin-style-qtcurve:amd64 (1.8.14-3+b2), libqapt3:amd64 (3.0.0-4), kde-style-breeze-qt4:amd64 (5.3.2-2), kdeartwork-style:amd64 (4.14.2-1), kwrit ed:amd64 (5.3.2-1), libkf5style5:amd64 (5.12.0-1), breeze-cursor-theme:amd64 (5.3.2-2), marble-data:amd64 (4.14.2-1), libopenobex1:amd64 (1.5-3), bluedevil:amd64 (5.3.2-1), qml-module-org -kde-kwindowsystem:amd64 (5.12.0-2), kdeartwork-theme-window:amd64 (4.14.2-1), kwin-style-breeze:amd64 (5.3.2-2), muon-discover:amd64 (5.3.2-3), libkfontinst5:amd64 (5.3.2-2), libshp2:amd 64 (1.3.0-4+b1), libkf5emoticons5:amd64 (5.12.0-1), kded5:amd64 (5.12.0-1), qml-module-org-kde-bluezqt:amd64 (5.3.1-1), libkf5people-data:amd64 (5.12.0-1), kde-style-breeze:amd64 (5.3.2-2 ), libkf5peoplebackend5:amd64 (5.12.0-1), muon-common:amd64 (5.3.2-3), kdesudo:amd64 (3.4.2.4-2), libqoauth1:amd64 (1.0.1-2), python3-software- properties:amd64 (0.92.25debian1), libkf5fil emetadata-data:amd64 (5.9.2-2), libkworkspace5-5:amd64 (5.3.2-4), libmuon:amd64 (5.3.2-3), libtaskmanager5:amd64 (5.3.2-4), libkf5bluezqt- data:amd64 (5.3.1-1), libkf5balooxapian1:amd64 (5 .9.2-3), muon-notifier:amd64 (5.3.2-3), libpoppler-qt5-1:amd64 (0.26.5-3), libqextserialport1:amd64 (1.2.0~rc1+git7-g3be3fbf-1+b1), apper-data:amd64 (0.9.2-2.1), libkf5filemetadata-bin:am d64 (5.9.2-2+b1), python3-pykde4:amd64 (4.14.0-1), breeze:amd64 (5.3.2-2), libssh-4:amd64 (0.6.3-4.1), libkf5people5:amd64 (5.12.0-1), libxcb- record0:amd64 (1.10-3+b1), kio-extras-data:am d64 (5.3.2-2), debconf-kde-data:amd64 (1.0.1-3), liblimba0:amd64 (0.5.0-1), libastro1:amd64 (4.14.2-1), liboxygenstyleconfig5-5:amd64 (5.3.2-3), libquazip1:amd64 (0.7-2), libmarblewidget1 9:amd64 (4.14.2-1), libkf5emoticons-data:amd64 (5.12.0-1), kde-config- sddm:amd64 (5.3.2-1), libkf5emoticons-bin:amd64 (5.12.0-1), libpackagekitqt4-0:amd64 (0.9.5-1), libkf5activitiesexper imentalstats1:amd64 (5.3.2-2), libqtlocation1:amd64 (1.2.0-3+b1), libqca- qt5-2-plugins:amd64 (2.1.0.3-3), libkf5baloo1:amd64 (5.9.2-3), oxygen- sounds:amd64 (5.3.2-3), libkf5bluezqt5:amd64 (5.3.1-1), obex-data-server:amd64 (0.4.5-1+b4), libkfontinstui5:amd64 (5.3.2-2), catdoc:amd64 (0.94.4-1.1), breeze-icon-theme:amd64 (5.3.2-2), libqapt3-runtime:amd64 (3.0.0-4), qml-modul e-qtquick-controls-styles-breeze:amd64 (5.3.2-2), qapt-batch:amd64 (3.0.0-4), marble-plugins:amd64 (4.14.2-1), kde-style-oxygen-qt5:amd64 (5.3.2-3), libkf5filemetadata3:amd64 (5.9.2-2+b1), libkf5dnssd5:amd64 (5.12.0-1), software-properties-kde:amd64 (0.92.25debian1), libqca-qt5-2:amd64 (2.1.0.3-3), software-properties-common:amd64 (0.92.25debian1), libdebconf- kde0:amd64 (0.3-2), libdebconf-kde1:amd64 (1.0.1-3), libkf5peoplewidgets5:amd64 (5.12.0-1), khotkeys:amd64 (5.3.2-2), khotkeys- data:amd64 (5.3.2-2), fonts-oxygen:amd64 (5.3.2-1), unattended-upgrades:amd64 (0.86.2), kio-extras:amd64 (5.3.2-2), libkf5dnssd-data:amd64 (5.12.0-1), muon- updater:amd64 (5.3.2-3), apper:amd64 (0.9.2-2.1) End-Date: 2015-08-03 09:12:18 Start-Date: 2015-08-03 09:32:48 Commandline: apt-get dist-upgrade Install: liboxygenstyle5-5:amd64 (5.3.2-3, automatic), libqapt3:amd64 (3.0.0-4, automatic), kde-style-breeze-qt4:amd64 (5.3.2-2, automatic), kwrited:amd64 (5.3.2-1, automatic), libkf5style5:amd64 (5.12.0-1, automatic), breeze-cursor-theme:amd64 (5.3.2-2, automatic), libopenobex1:amd64 (1.5-3, automatic), bluedevil:amd64 (5.3.2-1, automatic), qml-module-org-kde- kwindowsystem:amd64 (5.12.0-2, automatic), kwin-style-breeze:amd64 (5.3.2-2, automatic), muon-discover:amd64 (5.3.2-3, automatic), libkfontinst5:amd64 (5.3.2-2, automatic), libkf5emoticons5:amd64 (5.12.0-1, automatic), kded5:amd64 (5.12.0-1, automatic), qml-module-org-kde-bluezqt:amd64 (5.3.1-1, automatic), libkf5people-data:amd64 (5.12.0-1, automatic), kde-style- breeze:amd64 (5.3.2-2, automatic), libkf5peoplebackend5:amd64 (5.12.0-1, automatic), muon-common:amd64 (5.3.2-3, automatic), kdesudo:amd64 (3.4.2.4-2, automatic), python3-software-properties:amd64 (0.92.25debian1, automatic), libkf5filemetadata-data:amd64 (5.9.2-2, automatic),
Bug#792231: This needs examined as soon as possible
On 08/03/2015 10:41 AM, Tristan Seligmann wrote: Unfortunately there are some significant challenges with 2.0+. The primary issue is the dependency on tlslite, which was removed from Debian previously due to being insecure and unmaintained. In addition, quite a bit of the certificate handling code does things incorrectly (see eg. the certificate chain verification code[1] that does not check the certificate purpose, allowing anyone with a valid cert to sign a fraudulent cert as if they were a CA). I would very much welcome help with these issues, but be warned there is most likely a fair amount of work involved in either rewriting the cert-handling code to use another library (probably python-openssl/python-cryptography), or resurrecting and maintaining the tlslite package. [1] https://github.com/spesmilo/electrum/blob/master/lib/paymentrequest.py#L119 If that's the case, does it even remain feasible to keep this in Debian with a year-old version that has its own incompatibilities with future versions and its own problems? Based solely on what you've said (a dependency doesn't exist anymore, other handling codes being bad and thereby introducing a MITM problem, etc.), it *sounds* like it should be removed... Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791597: Remove apache2-mpm-worker from the depends list
On 08/03/2015 07:23 PM, Petter Reinholdtsen wrote: [Sunil Mohan] Looks like we simply have to remove the package from depends list. The attached patch (untested) should do it. I have vague memories of picking that one to ensure the dependency list had both a virtual and a concrete dependency to keep the autobuilders predictable (or was it to make sure debootstrap work?). I believe there is a reason to not have virtual dependencies alone, but no longer remember the specifics. This I suspect just removing the concrete dependency is the wrong fix, and believe it should be replaced with another concrete dependency instead. Here is my understanding: apache2 package used to and still ships with all the mpm modules. The extra mpm-* modules simply used to select one module or the other. Now, those packages are all gone. Depending on a package to select an MPM model is not possible now. The mod-php5 now does an 'a2enmod mpm_prefork' instead of depending on the package. I assume that this the preferred and only way to change apache's MPM now. Earlier we explicitly chose mpm-worker and switched to mpm-prefork when needed (ownCloud). With this patch we leave apache to pick its default MPM and switch to mpm-prefork when needed. In any case, mpm-* packages are gone and MPM is selected using a2(dis|en)mod. Perhaps I can test for something and make sure we are still good. If debootstrap doesn't work, it should be easy to catch. -- Sunil signature.asc Description: OpenPGP digital signature
Bug#778189: xracer: ftbfs with GCC-5
On Fri, 10 Jul 2015 21:55:59 +0800, Ying-Chun Liu (PaulLiu) wrote: I made a patch to fix this. Might not be good but just fix it in experimental. As attachment. Since GCC 5 is in unstable, it would be good to get the fixed package uploaded to sid soon. 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 `- NP: Beatles signature.asc Description: Digital Signature
Bug#778148: raise severity of GCC 5 issues
On Mon, 03 Aug 2015 13:20:22 +0200, Matthias Klose wrote: severity 778148 serious Was this on purpose or the fallout of a mass change? As I mentioned before (and confirmed now), the package does build with gcc 5. 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 `- NP: Beatles signature.asc Description: Digital Signature
Bug#794096: squashfs-tools: please add --numeric-uid-gid to unsquashfs
Control: tag -1 + patch
Hi,
On Thu, 30 Jul 2015 15:38:37 +0200 =?iso-8859-1?B?Suly6W15?= Bobbio
lu...@debian.org wrote:
Adding a `--numeric-uid-gid` (like cpio) or `--numeric-owner` (like Tar)
option
would be greatly appreciated.
`-
Attached patch fixes this by introducing a new option 'lns' which works
like 'lls' but instead of working like 'ls -l' it works like 'ls -n'.
Example output:
$ unsquashfs -lns ~/testfile.squashfs
Parallel unsquashfs: Using 4 processors
2 inodes (2 blocks) to write
drwxr-xr-x 1000/100048 2015-08-03 14:53 squashfs-root
-rw-r--r-- 1000/10005 2015-08-03 14:52 squashfs-root/testfile
-rw-r--r-- 1000/10004 2015-08-03 14:53 squashfs-root/testfile2
Kind regards,
akira
diff -Nru squashfs-tools-4.2+20130409/debian/changelog
squashfs-tools-4.2+20130409/debian/changelog
--- squashfs-tools-4.2+20130409/debian/changelog2013-09-18
10:22:27.0 +0200
+++ squashfs-tools-4.2+20130409/debian/changelog2015-08-03
16:15:27.0 +0200
@@ -1,3 +1,10 @@
+squashfs-tools (1:4.2+20130409-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Adding lns option to unsquashfs
+
+ -- akira marival...@gmail.com Mon, 03 Aug 2015 16:12:14 +0200
+
squashfs-tools (1:4.2+20130409-2) unstable; urgency=low
* New maintainer (closes: #723600).
diff -Nru squashfs-tools-4.2+20130409/debian/manpages/unsquashfs.1
squashfs-tools-4.2+20130409/debian/manpages/unsquashfs.1
--- squashfs-tools-4.2+20130409/debian/manpages/unsquashfs.12013-05-09
22:22:49.0 +0200
+++ squashfs-tools-4.2+20130409/debian/manpages/unsquashfs.12015-08-03
16:39:56.0 +0200
@@ -32,6 +32,8 @@
list filesystem, but don't unsquash.
.IP \-ll, \-lls 4
list filesystem with file attributes (like ls \-l output), but don't unsquash.
+.IP \-ln, \-lns 4
+list filesystem with file attributes (like ls \-n output), but don't unsquash.
.IP \-f, \-force 4
if file already exists then overwrite.
.IP \-s, \-stat 4
diff -Nru squashfs-tools-4.2+20130409/debian/patches/nousername
squashfs-tools-4.2+20130409/debian/patches/nousername
--- squashfs-tools-4.2+20130409/debian/patches/nousername 1970-01-01
01:00:00.0 +0100
+++ squashfs-tools-4.2+20130409/debian/patches/nousername 2015-08-03
17:11:11.0 +0200
@@ -0,0 +1,51 @@
+--- a/unsquashfs.c
b/unsquashfs.c
+@@ -62,7 +62,7 @@ char *file_data;
+ char *data;
+ unsigned int block_size;
+ unsigned int block_log;
+-int lsonly = FALSE, info = FALSE, force = FALSE, short_ls = TRUE;
++int lsonly = FALSE, info = FALSE, force = FALSE, short_ls = TRUE, numeric_ls
= FALSE;
+ int use_regex = FALSE;
+ char **created_inode;
+ int root_process;
+@@ -492,7 +492,7 @@ int print_filename(char *pathname, struc
+ }
+
+ user = getpwuid(inode-uid);
+- if(user == NULL) {
++ if(user == NULL || numeric_ls) {
+ int res = snprintf(dummy, 12, %d, inode-uid);
+ if(res 0)
+ EXIT_UNSQUASH(snprintf failed in print_filename()\n);
+@@ -506,7 +506,7 @@ int print_filename(char *pathname, struc
+ userstr = user-pw_name;
+
+ group = getgrgid(inode-gid);
+- if(group == NULL) {
++ if(group == NULL || numeric_ls) {
+ int res = snprintf(dummy2, 12, %d, inode-gid);
+ if(res 0)
+ EXIT_UNSQUASH(snprintf failed in print_filename()\n);
+@@ -2512,6 +2512,11 @@ int main(int argc, char *argv[])
+ strcmp(argv[i], -ll) == 0) {
+ lsonly = TRUE;
+ short_ls = FALSE;
++ } else if(strcmp(argv[i], -lns) == 0 ||
++ strcmp(argv[i], -ln) == 0) {
++ lsonly = TRUE;
++ short_ls = FALSE;
++ numeric_ls = TRUE;
+ } else if(strcmp(argv[i], -linfo) == 0 ||
+ strcmp(argv[i], -li) == 0) {
+ info = TRUE;
+@@ -2569,6 +2574,9 @@ options:
+ ERROR(\t-ll[s]\t\t\tlist filesystem with file
+ attributes (like\n);
+ ERROR(\t\t\t\tls -l output), but don't unsquash\n);
++ ERROR(\t-ln[s]\t\t\tlist filesystem with file
++ attributes (like\n);
++ ERROR(\t\t\t\tls -n output), but don't unsquash\n);
+ ERROR(\t-f[orce]\t\tif file already exists then
+ overwrite\n);
+ ERROR(\t-s[tat]\t\t\tdisplay filesystem superblock
diff -Nru squashfs-tools-4.2+20130409/debian/patches/series
squashfs-tools-4.2+20130409/debian/patches/series
--- squashfs-tools-4.2+20130409/debian/patches/series 2013-05-09
22:22:49.0 +0200
+++ squashfs-tools-4.2+20130409/debian/patches/series 2015-08-03
16:30:54.0 +0200
Bug#794492: systemd: Loginctl displays no sessions after waking up from suspend.
Package: systemd Version: 222-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Waking-up from a suspend. * What exactly did you do (or not do) that was effective (or ineffective)? Reboot is effective. And useless - I want a suspend, not a power off. Reproducing is simple - suspend, and wake up. Nothing in the loginctl list-sessions, so no suspend from GUI possible any more. * What was the outcome of this action? Of the reboot? Well - running system, what else? * What outcome did you expect instead? Before someone improves systemd even more - no, no, I wanted my system to tun after the reboot. Correct this utter c.r.a.p. some other way, possibly just mv it to /dev/null, please. *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod221-1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-2 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev222-2 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.20-1 ii libpam-systemd 222-2 Versions of packages systemd suggests: ii systemd-ui 3-4 -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleLidSwitch=ignore -- no debconf information [EXTENDED] /lib/systemd/system/rc-local.service - /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/clamav-daemon.socket - /etc/systemd/system/clamav-daemon.socket.d/extend.conf [EQUIVALENT] /etc/systemd/system/ipsec.service - /lib/systemd/system/ipsec.service 4 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/openvpn.service.dsh-also == /etc/systemd/system/multi-user.target.wants/openvpn.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/uuidd.service.dsh-also == /etc/systemd/system/sockets.target.wants/uuidd.socket == /var/lib/systemd/deb-systemd-helper-enabled/uuidd.socket.dsh-also == /etc/systemd/system/sockets.target.wants/uuidd.socket == /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/cron.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.socket.dsh-also == /etc/systemd/system/sockets.target.wants/acpid.socket == /var/lib/systemd/deb-systemd-helper-enabled/ipsec.service == == /var/lib/systemd/deb-systemd-helper-enabled/netfilter-persistent.service.dsh-also == /etc/systemd/system/multi-user.target.wants/netfilter-persistent.service == /var/lib/systemd/deb-systemd-helper-enabled/gfmd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/gfmd.service == /var/lib/systemd/deb-systemd-helper-enabled/clamav-freshclam.service.dsh-also == /etc/systemd/system/multi-user.target.wants/clamav-freshclam.service == /var/lib/systemd/deb-systemd-helper-enabled/mcstrans.service.dsh-also == /etc/systemd/system/multi-user.target.wants/mcstrans.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also == /etc/systemd/system/multi-user.target.wants/cups.path == /var/lib/systemd/deb-systemd-helper-enabled/gpsd.service.dsh-also == /etc/systemd/system/sockets.target.wants/gpsd.socket == /var/lib/systemd/deb-systemd-helper-enabled/tor.service.dsh-also == /etc/systemd/system/multi-user.target.wants/tor.service == /var/lib/systemd/deb-systemd-helper-enabled/vnstat.service.dsh-also == /etc/systemd/system/multi-user.target.wants/vnstat.service == /var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/accounts-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/krb5-kdc.service.dsh-also == /etc/systemd/system/multi-user.target.wants/krb5-kdc.service == /var/lib/systemd/deb-systemd-helper-enabled/virtlockd.socket.dsh-also == /etc/systemd/system/multi-user.target.wants/virtlockd.socket
Bug#794438: [Pkg-kde-extras] Bug#794438: Partition manager does not launch
On Sunday, August 02, 2015 10:03:50 PM Carlos Kosloff wrote: Package: partitionmanager Version: 1.0.3-2.1 Severity: grave Dear Maintainer, * What led up to the situation? I recently updated my KDE desktop to plasma5 which entails a lot of changes, lots of things not working yet, including this one. partitionmanager errors out saying that root password incorrect. This is a false positive, root password is correct. I tested it on other programs that depend on it, like Synaptic Package Manager. * What exactly did you do (or not do) that was effective (or ineffective)? I just launched partition manager from an icon in my desktop * What was the outcome of this action? http://i.imgur.com/79Qrvl7.png * What outcome did you expect instead? A normal launch like in plasma4 There is a Plasma 5 compatible version of partitionmanager available upstream. We just need to package it once the current gcc5 transition is done/far enough along. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794494: postfix: Uses obsolete and insecure ciphers and SSL versions
Package: postfix Version: 2.11.3-1 Severity: important This is the text of the upstream announcement: [An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.0.2.html] Postfix stable release 3.0.2 is available, as well as legacy releases 2.11.6, 2.10.8, and 2.9.14. With all supported Postfix releases, the default settings have been updated so that they no longer enable export-grade ciphers, and no longer enable the SSLv2 and SSLv3 protocols. These ciphers and protocols have little if any legitimate use today, and have instead become a vehicle for downgrade attacks. There are no other code changes. Postfix documentation has been updated to reflect the new default settings and their rationale; the RELEASE_NOTES give suggestions for how to enable the old ciphers and protocols if your infrastructure requires them. Finally, abandoning deprecated ciphers and protocols does not really improve TLS security without measures to better authenticate remote servers. Secure DNS and TLSA are steps in that direction. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl
On Mon, 03 Aug 2015 13:32:19 -0400 Eric Christensen e...@christensenplace.us wrote: On Monday, August 03, 2015 03:32:23 PM Colin Tuckley wrote: On 03/08/15 14:47, Eric Christensen wrote: No, that fails too. I *can* go directly to TrustedQSL with an .adi and have it sign and upload from there. Not sure why CQRLOG is failing. Can you please try the 1.9.0 package from testing. It installs and runs okay on a stable system without any problems. I still get the same error after upgrading to 1.9.0. Looking around at some of the other issues I've been having with CQRLOG (after moving to Debian) I think I see a pattern. It appears that CQRLOG doesn't recognize a connection to the Internet. Things like publishing the log to Clublog or using the DXCluster all seem to fail. From the log publishing feature: HamQTH: Uploading WA3GFZ HamQTH: Upload failed! Check Internet connection I clearly have an Internet connection. Why would CQRLOG not see it? 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719695: Prefer symlinks over Alias= for non-matching service names
Package: systemd Version: 223-2 Followup-For: Bug #719695 Hello, I am hit by the same problem. So far, we've shipped a SysV init script /etc/init.d/multipath-tools, whereas upstream ships the service file as multipathd.service I haven't read through all the details on this bug report, but I'd like your advise on how to proceed. Initially I created an Alias=multipath-tools.service, but that did not work. It did not sense the Alias= setting, and instead picked the init script. I think the manpage should be updated accordingly on whatever the conclusion is. And looking at this bug report, I'm not sure if this has been concluded. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.3+ (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod221-1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 223-2 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev222-2 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.20-1 ii libpam-systemd 223-2 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleLidSwitch=ignore LidSwitchIgnoreInhibited=yes -- 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#790536: FTBFS with GCC 5: comparison of constant '-1' with boolean expression is always false
Control: reassign -1 src:linux-tools 4.0.2-1
Control: tag -1 fixed-upstream patch
Hi,
Martin Michlmayr t...@hp.com (2015-06-29):
Package: linux-tools
Version: 4.0.2-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
This should have been “Source: linux-tools” rather than “Package:
linux-tools”, reassigning.
Looking upstream, it seems this has been fixed as a side effect of a
performance improvement:
| commit fefd2d9619de3bf0bf02a8622e9f445c3d19cc3f
| Author: He Kuang heku...@huawei.com
| Date: Sun Feb 15 10:33:37 2015 +0800
|
| perf report: Fix branch stack mode cannot be set
builtin-report.c: In function 'cmd_report':
builtin-report.c:769:23: error: comparison of constant '-1' with boolean
expression is always false [-Werror=bool-compare]
branch_call_mode == -1) {
^
cc1: all warnings being treated as errors
Makefile.perf:693: recipe for target
'/«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-report.o' failed
diff:
| if (((branch_mode == -1 has_br_stack) || branch_mode == 1)
| - branch_call_mode == -1) {
| + !branch_call_mode) {
| sort__mode = SORT_MODE__BRANCH;
| symbol_conf.cumulate_callchain = false;
| }
I'm attaching a source debdiff generated after having added a quilt
patch and generated an updated source package. I suppose some stripping
might be needed before committing that to svn…
Mraw,
KiBi.
diff -Nru linux-tools-4.0.2/debian/changelog linux-tools-4.0.2/debian/changelog
--- linux-tools-4.0.2/debian/changelog 2015-05-11 04:53:13.0 +0200
+++ linux-tools-4.0.2/debian/changelog 2015-08-03 20:14:33.0 +0200
@@ -1,3 +1,10 @@
+linux-tools (4.0.2-1.1) UNRELEASED; urgency=high
+
+ * Backport upstream commit fefd2d9619 (perf report: Fix branch stack
+mode cannot be set) to fix FTBFS with GCC 5 (Closes: #790536).
+
+ -- Cyril Brulebois k...@debian.org Mon, 03 Aug 2015 20:12:15 +0200
+
linux-tools (4.0.2-1) unstable; urgency=medium
* New upstream release
diff -Nru linux-tools-4.0.2/debian/control.md5sum linux-tools-4.0.2/debian/control.md5sum
--- linux-tools-4.0.2/debian/control.md5sum 2015-05-11 05:06:30.0 +0200
+++ linux-tools-4.0.2/debian/control.md5sum 2015-08-03 20:14:37.0 +0200
@@ -1,4 +1,4 @@
ac3acacf0cde6d2cc424f28241bb0857 debian/bin/gencontrol.py
-78da1757427bbfdfaa8e54c64e5d627a debian/changelog
+a9673d14f0c75dd3c35b7a3f96ead06d debian/changelog
711fd0ce9d080e6cf27efddb74863670 debian/templates/control.main.in
5205a9db9cb5241ea836fb20502bf045 debian/templates/control.source.in
diff -Nru linux-tools-4.0.2/debian/patches/fix-ftbfs-with-gcc5.patch linux-tools-4.0.2/debian/patches/fix-ftbfs-with-gcc5.patch
--- linux-tools-4.0.2/debian/patches/fix-ftbfs-with-gcc5.patch 1970-01-01 01:00:00.0 +0100
+++ linux-tools-4.0.2/debian/patches/fix-ftbfs-with-gcc5.patch 2015-08-03 20:14:16.0 +0200
@@ -0,0 +1,54 @@
+From fefd2d9619de3bf0bf02a8622e9f445c3d19cc3f Mon Sep 17 00:00:00 2001
+From: He Kuang heku...@huawei.com
+Date: Sun, 15 Feb 2015 10:33:37 +0800
+Subject: [PATCH] perf report: Fix branch stack mode cannot be set
+
+When perf.data file is obtained using 'perf record -b', perf report
+should use branch stack mode to generate output. But this function is
+broken by improper comparison between boolean and constant -1.
+
+before this patch:
+
+ $ perf report -b -i perf.data
+ Samples: 16 of event 'cycles', Event count (approx.): 3171896
+ Overhead Command Shared Object Symbol
+13.59% ls [kernel.kallsyms] [k] prio_tree_remove
+13.16% ls [kernel.kallsyms] [k] change_pte_range
+12.09% ls [kernel.kallsyms] [k] page_fault
+12.02% ls [kernel.kallsyms] [k] zap_pte_range
+ ...
+
+after this patch:
+
+ $ perf report -b -i perf.data
+ Samples: 256 of event 'cycles', Event count (approx.): 256
+ Overhead Command Source Shared Object Source Symbol Target Shared Object Target Symbol
+ 9.38% ls [unknown] [k] [unknown] [k]
+ 6.25% ls libc-2.19.so [.] _dl_addrlibc-2.19.so [.] _dl_addr
+ 6.25% ls [kernel.kallsyms] [k] zap_pte_range [kernel.kallsyms] [k] zap_pte_range
+ 6.25% ls [kernel.kallsyms] [k] change_pte_range[kernel.kallsyms] [k] change_pte_range
+ 0.39% ls [kernel.kallsyms] [k] prio_tree_remove[kernel.kallsyms] [k] prio_tree_remove
+ ...
+
+Signed-off-by: He Kuang heku...@huawei.com
+Tested-by: Arnaldo Carvalho de Melo a...@redhat.com
+Cc: Paul Mackerras pau...@samba.org
+Cc: Peter Zijlstra a.p.zijls...@chello.nl
+Cc: Wang Nan wangn...@huawei.com
+Link:
Bug#777548: none of the more recent (jessie+) packages are working at the moment
Hi, I have troubles with this on debian in general... None of the current versions of libguestfs-tools: virt-builder is working. stable 1:1.28.1-1: amd64 ...as per original description of this bug testing/sid 1:1.28.12-1: amd64 experimental 1:1.29.50-1: amd64 virt-resize: error: libguestfs error: part_set_mbr_id: sfdisk --part-type: You cannot change a partition into an extended one or vice versa. Delete it first. sfdisk: /dev/sdb: partition 2: failed to set partition type Marek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794430: [Cupt-devel] Bug#794430: cupt: Trying to install a uninstallable package, and not error is show
Hi Javier, Thank you for the report. Indeed, it's looks like a bug if cupt didn't print any reason. On 03.08.2015 01:26, Javier Barroso wrote: Currently on sid (last apt full-upgrade, removed gnome-shell, there is a dependency which cannot be satisfied). There is a verbose / debug flag on cupt? Yes, there is, add -o debug::resolver=yes for this case. Could you try it and send the log? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf(maildog)jabber.fsfe.org C++ GNU/Linux userspace developer, Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794497: ITP: golang-gopkg-eapache-go-resiliency.v1 -- Resiliency patterns for golang
Package: wnpp Severity: wishlist Owner: Alexandre Viau alexan...@alexandreviau.net * Package name: golang-gopkg-eapache-go-resiliency.v1 Version : 0.0~git20150213.0.6800482-1 Upstream Author : Evan Huus eapa...@gmail.com * URL : https://github.com/eapache/go-resiliency * License : Expat Programming Lang: Go Description : Resiliency patterns for golang -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790229: blackbox: FTBFS with glibc 2.21 and gcc-5
Control: retitle 790229 blackbox: FTBFS with and gcc-5 (symbols) Martin Michlmayr t...@hp.com (2015-07-07): retitle 790229 blackbox: FTBFS with and gcc-5 thanks * Daniel Schepler dschep...@gmail.com [2015-06-27 09:17]: From my pbuilder build log, using a setup preferring glibc and gcc-defaults from experimental: I see the same with glibc from unstable and GCC 5. Ditto in unstable now, adjusting title to mention the issue is symbols. Mraw, KiBi. signature.asc Description: Digital signature
Bug#787582: Info received (Bug#787582: VDPAU needed)
Hi, No problem, actually I thought it was simply a miss. Thanks ! :-) 2015-08-03 18:45 GMT+02:00 Luca Boccassi luca.bocca...@gmail.com: On Mon, 2015-08-03 at 18:36 +0200, Julien Aubin wrote: Hello, Actually things won't work until we also have the i386 flavour of libvdpau1 :-( Hello, Please be patient, the build elves are working as hard as they can! :-) All the supported architectures will pop up soon in the repositories. You can follow the progress on the buildd page [1], reachable as a link from the package's PTS [2]. Kind regards, Luca Boccassi [1] https://buildd.debian.org/status/package.php?p=libvdpausuite=jessie-backports [2]https://tracker.debian.org/pkg/libvdpau
Bug#794499: kdeconnect does not work with Plasma 5/KF5
Package: kdeconnect Version: 0.8-1 Severity: important Since the upgrade of various KDE packages to Plasma 5/KF5, kdeconnect stopped working. Upstream seems to support Plasma 5/KF5 and it looks like the Debian kdeconnect repo also has various things in place for Plasma 5/KF5, but (apparently) they're not enabled yet. See also https://lists.debian.org/debian-kde/2015/08/msg00028.html It would be great if kdeconnect is upgraded or a package which does support Plasma 5/KF5 is uploaded/added to the archives. TIA, Diederik -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdeconnect depends on: ii kde-runtime 4:14.12.3-1 ii libc6 2.19-19 ii libfakekey0 0.1-8.1 ii libgcc1 1:5.1.1-14 ii libkcmutils44:4.14.6-1 ii libkdecore5 4:4.14.6-1 ii libkdeui5 4:4.14.6-1 ii libkfile4 4:4.14.6-1 ii libkio5 4:4.14.6-1 ii libqca2 2.1.0.3-3 ii libqca2-plugins 2.1.0.3-3 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.7+dfsg-1 ii libqt4-declarative 4:4.8.7+dfsg-1 ii libqt4-network 4:4.8.7+dfsg-1 ii libqt4-svg 4:4.8.7+dfsg-1 ii libqt4-xml 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libstdc++6 5.1.1-14 ii libx11-62:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxext62:1.3.3-1 ii libxtst62:1.2.2-1+b1 ii sshfs 2.5-1 kdeconnect recommends no packages. kdeconnect 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#792231: electrum
On 08/03/2015 10:41 AM, Tristan Seligmann wrote: In addition, quite a bit of the certificate handling code does things incorrectly (see eg. the certificate chain verification code[1] that does not check the certificate purpose, allowing anyone with a valid cert to sign a fraudulent cert as if they were a CA). Instead of suggesting that there are quite a bit of incorrect things, and then citing one example, can you provide the full list of problems that you see? also, by certificate purpose, do you mean Key-Usage? thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769611: interested in packaging ganeti-instance-image
Control: retitle -1 ITP: ganeti-instance-image -- guest OS definition for Ganetiusing images Control: owner -1 mike.gabr...@das-netzwerkteam.de Hi all, I am interested in taking over this RFP/ITP for ganeti-instance-image. If not ok with anyone, please veto now... Thanks+Greets, Mike -- mike gabriel aka sunweaver (Debian Developer) fon: +49 (1520) 1976 148 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net signature.asc Description: Digital signature
Bug#794488: Piglit tests in Mesa crash, if radeonsi_dri.so is linked with libelf1 (libelfg0 works)
Mark Wielaard wrote on 03.08.2015 20:06:
On Mon, Aug 03, 2015 at 05:44:01PM +0200, Kai Wasserbäch wrote:
when I link my Mesa build against libelf1, some Piglit [0] tests start
throwing SIGSEGVs. Two of those tests are
spec@arb_gpu_shader_fp64@execution@fs-indirect-temp-double-{dst,src}.
When I link Mesa (or more specifically my driver, which is
radeonsi_dri.so) against libelfg0, the tests pass and run normally.
Is there an easy way to reproduce this? Which source code in particular
is build, where did it come from (debian source package or a particular
upstream release?), what are the specific build steps and how are the
particular testcases run? Can you show the steps that make things work
and which steps are different when things break?
The relevant difference between a failing and a working setup, is linking Mesa
with libelf1 vs. libelg0. I can give you both binary and source packages for
Mesa (one for a Mesa linked against a crashing libelf1 and one linked against a
working libelfg0). Let me know, if you want that.
The Mesa code is coming directly from upstream's Git and I've integrated that
into the Debian source package, ie. I build a Debian package with a newer
upstream source.
The build itself is happening in a clean pbuilder chroot (package sources in
that chroot: Debian unstable + LLVM packages from http://llvm.org/apt, which
are maintained by Debian's LLVM maintainer). (pbuiler --build
/path/to/my/mesa.dsc)
The full stack is (Debian testing as a base, eg. the libdrm is from Debian):
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/5d29eaef85
libdrm: 2.4.62-1
LLVM: SVN:trunk/r243678 (3.8 devel)
X.Org: 2:1.17.1-2
Linux: 4.1.3
Firmware: https://secure.freedesktop.org/~agd5f/radeon_ucode/hawaii/
286640da3d90d7b51bdb038b65addc47 hawaii_ce.bin
161105a73f7dfb2fca513327491c32d6 hawaii_mc.bin
d6195059ea724981c9acd3abd6ee5166 hawaii_me.bin
ad511d31a4fe3147c8d80b8f6770b8d5 hawaii_mec.bin
63eae3f33c77aadbc6ed1a09a2aed81e hawaii_pfp.bin
5b72c73acf0cbd0cbb639302f65bc7dc hawaii_rlc.bin
f00de91c24b3520197e1ddb85d99c34a hawaii_sdma1.bin
8e16f749d62b150d0d1f580d71bc4348 hawaii_sdma.bin
7b6ca5302b56bd35bf52804919d57e63 hawaii_smc.bin
9f2ba7e720e2af4d7605a9a4fd903513 hawaii_uvd.bin
b0f2a043e72fbf265b2f858b8ddbdb09 hawaii_vce.bin
libclc: Git:master/7958b0202b
DDX: Git:master/b6d871bf29
And depending on whether you build mesa with libelf1 or libelfg0 you get a crash
in the Piglit test.
Steps to reproduce:
- you need a AMD GPU powered by the radeonsi driver
- build Mesa with the radeonsi driver (it uses LLVM as a backend to generate
machine instructions, the compiled result is returned as an ELF, hence the
dependency on libelf) linked against a current libelf1 (or take my build, if you
wish)
- build Piglit
- run one of the two Piglit tests. Either one is fine and crashes with libelf1.
(e.g. PIGLIT_BUILD_DIR/bin/shader_runner
PIGLIT_SRC_DIR/tests/spec/arb_gpu_shader_fp64/execution/fs-indirect-temp-double-src.shader_test
-auto)
Cheers,
Kai
signature.asc
Description: OpenPGP digital signature
Bug#778106: rheolef: ftbfs with GCC-5
Hi,
I haven't touched this:
Matthias Klose d...@debian.org (2015-07-25):
after fixing
--- a/skit/plib2/load_chunk.h
+++ b/skit/plib2/load_chunk.h
@@ -28,7 +28,7 @@ load_chunk (std::istream s, RandomItera
{
while (iter != last)
if (!(s *iter++)) return false;
-return s;
+return bool(s);
}
template class RandomIterator, class GetFunction
inline
@@ -37,7 +37,7 @@ load_chunk (std::istream s, RandomItera
{
while (iter != last)
if (! get_element (s, *iter++)) return false;
-return s;
+return bool(s);
}
} // namespace rheolef
#endif // _RHEOLEF_LOAD_CHUNK_H
but I had to patch configure.ac because hardening-cc can get in the way
(binaries exist but can't compile anything if the relevant package isn't
installed):
| --- rheolef-6.5/configure.ac~
| +++ rheolef-6.5/configure.ac
| @@ -459,9 +459,9 @@ dnl-
| USER_CFLAGS=${CFLAGS--O2}
| USER_CXXFLAGS=$CXXFLAGS
|
| -AC_PROG_CC(gcc-4.5 gcc cc icc cl)
| +AC_PROG_CC(gcc cc icc cl)
| AC_PROG_CPP
| -AC_PROG_CXX(g++-4.5 g++ c++ cxx icpc KCC CC CC cc++ xlC aCC)
| +AC_PROG_CXX(g++ c++ cxx icpc KCC CC CC cc++ xlC aCC)
| AC_PROG_CXXCPP
|
| # when GNU C/C++ is recognized, force -O2 -g = skip it
I get: […]
I'm getting something similar in unstable right now, w/o wrapping:
| make all-am
| /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../../config -fno-strict-aliasing -I../../include -I/usr/include/suitesparse
-D_FORTIFY_SOURCE=2 -O3 -D_FORTIFY_SOURCE=2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -Wall
-Wno-unused -Werror -Wno-strict-aliasing -O2 -MT index_set.lo -MD -MP -MF
.deps/index_set.Tpo -c -o index_set.lo index_set.cc
| libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../config
-fno-strict-aliasing -I../../include -I/usr/include/suitesparse
-D_FORTIFY_SOURCE=2 -O3 -D_FORTIFY_SOURCE=2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -Wall
-Wno-unused -Werror -Wno-strict-aliasing -O2 -MT index_set.lo -MD -MP -MF
.deps/index_set.Tpo -c index_set.cc -fPIC -DPIC -o .libs/index_set.o
| In file included from /usr/include/boost/serialization/set.hpp:26:0,
| from ../../include/rheolef/index_set.h:38,
| from index_set.cc:21:
| /usr/include/boost/serialization/detail/stack_constructor.hpp: In constructor
'boost::serialization::detail::stack_constructArchive,
T::stack_construct(Archive, unsigned int)':
| /usr/include/boost/serialization/detail/stack_constructor.hpp:54:9: error:
'load_construct_data_adl' is not a member of 'boost::serialization'
| boost::serialization::load_construct_data_adl(
| ^
| Makefile:727: recipe for target 'index_set.lo' failed
One might need to take a closer look at this package anyway, given one
can see this in debian/rules:
| # Prepare the debian control files necessary for the creation of the
packages
| cat debian/shlibs.librheolef1.X | \
| sed -e s/\@LIBRHEOLEF\@/$(LIBRHEOLEF)/g \
| -e s/\@MAJOR_VERSION\@/$(MAJOR_VERSION)/g \
| -e s/\@MINOR_VERSION\@/$(MINOR_VERSION)/g \
| -e s/\@VERSION\@/$(VERSION)/g \
| -e s/\@SONAME\@/$(SONAME)/g debian/shlibs.$(LIBRHEOLEF)
| echo 'shlibs:Depends=libc6 (= 2.7-1), libgcc1 (= 1:4.3.1-9),
libstdc++6 (= 4.3.1-9)' debian/$(LIBRHEOLEF).substvars
and I'm not sure this is exactly correct…
This package looks like a good candidate for a removal if it gets in the
way.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Bug#778025: Proposed fixes for netrek-client-cow: ftbfs with GCC-5
On Mon, 03 Aug 2015 12:10:40 -0600, Thavatchai Makphaibulchoke wrote: Whereas the corresponding pattern in configure script does not quite match the above (gmp=.*2 vs gmp=.*[02-9]) as shown here, [..] Please let me know what you think about this discrepancy. It's patched; cf. debian/patches/001-configure-gmp-version.patch Regardless of how the configure script is created, I propose that we fix configure.in (not the configure script) Is configure.in recreated during the build? 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 `- NP: Joan Baez: I Shall Be Released signature.asc Description: Digital Signature
Bug#790703: Status moving forward?
On Friday, July 24, 2015 09:02:41 PM Nicola Chiapolini wrote: Control: severity -1 grave Control: thanks I am in the same situation as Matthew and run into this when upgrading my testing install. To get a usable KDE back, I had to downgrade. I raised the severity again, this way people with the listbugs in the default config at least get a warning. Now that plasma 5 is in Testing, how is this working (seems fine for most)? Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794498: reconserver: FTBFS (missing build-dep): librecon-1.9-dev (= 1.9.6)
Source: reconserver Version: 0.10.3-1 Severity: serious Justification: FTBFS Hi, Trying to look at #778103, things stopped quite soon since your package has a build-dep on librecon-1.9-dev while the archive only has librecon-1.10-dev. Recording this separately from #778103 to ease tracking. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793544: Severity is serious
control: severity -1 serious Justification, render wireless with newer kernel totally useless on a lot of laptop (at least my tow laptop). Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780905: fp-compiler-2.6.4: fpc fails to link programs using fpmkunit
On 21/03/15 12:00, Andrew Apted wrote: /usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T? /usr/bin/ld.bfd: skipping incompatible /usr/lib/i386-linux-gnu/crti.o when searching for /usr/lib/i386-linux-gnu/crti.o /usr/bin/ld.bfd: cannot find /usr/lib/i386-linux-gnu/crti.o --snip-- Architecture: amd64 (x86_64) Foreign Architectures: i386 I think this may be a multiarch related issue Do you have libc6-dev:i386 installed? if so can you try removing it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl
On Monday, August 03, 2015 03:32:23 PM Colin Tuckley wrote: On 03/08/15 14:47, Eric Christensen wrote: No, that fails too. I *can* go directly to TrustedQSL with an .adi and have it sign and upload from there. Not sure why CQRLOG is failing. Can you please try the 1.9.0 package from testing. It installs and runs okay on a stable system without any problems. I still get the same error after upgrading to 1.9.0. 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791818: emacs: 'emacs' metapackage doesn't remove what it installs
Package: emacs Version: 46.1 Followup-For: Bug #791818 Dear Maintainer, I'm not sure if this is the same problem chill3 describes, but no doubts it's something similiar. Running the command # apt-get install emacs installs both 'emacs' and 'emacs24' packages. But running # apt-get remove emacs removes just 'emacs' package for some reason. According to the output of $ aptitude why emacs24 the package is kept because it provides the mail-reader, which is suggested by another package. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages emacs depends on: ii emacs24 24.4+1-5 emacs recommends no packages. emacs 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#794496: postfix-mysql: commands out of sync when calling stored procedure
Package: postfix-mysql
Version: 2.11.3-1
Severity: normal
Dear Maintainer,
I attempted to implement all queries that my postfix install
asks the database as stored procedures in MySQL. Unfortunately,
I often get the common Commands out of sync error that I believe
comes from Postfix's mysql driver when query results are not
handled appropriately.
The code for the stored procedure is as follows:
SELECT `va`.`dst_email`
FROM `virtual_aliases` AS `va`
WHERE `va`.`src_email` = src_email
And the query is set in mysql-virtual_alias_maps.cf as this:
[...]
query = CALL `get_alias('%s')`
I thoroughly tested the routine, it does not seem to be the
source of the problem.
The log looks like this afterwards:
Aug 3 13:48:08 merlin postfix/smtpd[10872]: warning: mysql query failed:
Commands out of sync; you can't run this command now
I was able to implement some routines as functions; but some
need to return result-sets. Then stored procedures need to be
used and problems arise.
Otherwise the package is really great and does its job
perfectly. Thanks for maintenance and development efforts!
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postfix-mysql depends on:
ii libc6 2.19-18
ii libmysqlclient18 5.5.44-0+deb8u1
ii postfix 2.11.3-1
postfix-mysql recommends no packages.
postfix-mysql 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#794491: binNMUs needed for libstdc++6 follow-up transitions (tagcoll2 and libwibble)
Package: release.debian.org both tagcoll2 and libwibble build static libraries only, however changing their ABI triggered by the libstdc++6 transition. please - binNUM libwibble (using g++ (= 4:5.2)) - binNUM tagcoll2 (using g++ (= 4:5.2)) and the rebuilt libwibble. btw, shouldn't all reverse dependencies of these packages have a Built-Using attribute? After that, libept then hopefully do it's transition. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787582: Info received (Bug#787582: VDPAU needed)
Hello, Actually things won't work until we also have the i386 flavour of libvdpau1 :-( Thanks a lot and sorry again. 2015-08-01 18:00 GMT+02:00 Debian Bug Tracking System ow...@bugs.debian.org : Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 787...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 787582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#794493: Annual ping for John Stamp
Package: debian-maintainers Severity: normal This is my annual ping as a Debian Maintainer. I am still actively maintaining packages. Regards, John Stamp signature.asc Description: Digital signature
Bug#787582: Info received (Bug#787582: VDPAU needed)
On Mon, 2015-08-03 at 18:36 +0200, Julien Aubin wrote: Hello, Actually things won't work until we also have the i386 flavour of libvdpau1 :-( Hello, Please be patient, the build elves are working as hard as they can! :-) All the supported architectures will pop up soon in the repositories. You can follow the progress on the buildd page [1], reachable as a link from the package's PTS [2]. Kind regards, Luca Boccassi [1]https://buildd.debian.org/status/package.php?p=libvdpausuite=jessie-backports [2]https://tracker.debian.org/pkg/libvdpau signature.asc Description: This is a digitally signed message part
