Bug#907559: Do you have any clue? [andr...@an3as.eu: cgview.jar does not find class from batik-util]
On Thu, Aug 30, 2018 at 10:00:52AM +0200, Emmanuel Bourg wrote: > On 29/08/2018 17:16, Markus Koschany wrote: > > https://mvnrepository.com/artifact/org.apache.xmlgraphics/batik-constants > > Technically batik-constants is not a new project but a new Maven module > of the batik project. It seems we already build it [1]. Maybe it's just > a matter of updating the classpath in the manifests? Thanks a lot - that's it. Kind regards Andreas. -- http://fam-tille.de
Bug#907561: Duplicate report
If someone could please remove this report. There's already a report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907466
Bug#907631: Problème de connexion avec OpenSSL v1.1.1~~pre9-1 / connection problem with OpenSSL v1.1.1~~pre9-1
Package: openssl Version: 1.1.1~~pre9-1 Avec OpenSSL v1.1.1~~pre9-1, je n'arrive plus à me connecter à mon réseau d'entreprise (Wifi, PEAP\MSCHAPv2). La tentative de connexion arrive au serveur Radius mais, visiblement, l'échange avec ce dernier est "perturbé" et génère l'erreur suivante : wlp60s0: deauthenticating from c0:62:6b:e4:c4:e1 by local choice (Reason: 3=DEAUTH_LEAVING) Si je fais un rollback d'OpenSSL en v1.1.0h-4 (celle de testig), tout rentre dans l'ordre. J'ai donc ajouté un pinning pour conserver la version OpenSSL de testing. With OpenSSL vv1.1.1~~pre9-1, I can't connect to my entreprise network (Wifi, PEAP\MSCHAPv2). The connection attempt arrives at the Radius server but, obviously, the exchange is "disturbed" and raises the following error: wlp60s0: deauthenticating from c0:62:6b:e4:c4:e1 by local choice (Reason: 3=DEAUTH_LEAVING) If I come back to OpenSSL v1.1.0h-4 (from testing), everything returns in order. So, I've added a pinning to keep the testing version of OpenSSL. David BERCOT.
Bug#905418: openmpi: elpa builds hang on multiple architectures
Hi Alastair On 30/08/2018 13:07, Alastair McKinstry wrote: Can you redo tests with openmpi 3.1.2 ? Thanks for the new upload. I'm redoing the tests on elpa, ligghts and arpack. I'll update the bugs in due course. I think this new release fixes the hang issues, i've done some tests on armhf that went ok Here's hoping! Regards Graham
Bug#907628: bugs.debian.org: dislpay resolution not detected correctly
Set display resolution with the display settings everything s ok now ! On Thu, 30 Aug 2018 13:28:20 +0300 kostas sismanis wrote: > Package: bugs.debian.org > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > an unattended update probably created this > did not do anything yet > xrandr reports the maximum resolution is 1024 > display is connected though vga > driver is i915 > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > >
Bug#905418: openmpi: elpa builds hang on multiple architectures
Hi Graham Can you redo tests with openmpi 3.1.2 ? I think this new release fixes the hang issues, i've done some tests on armhf that went ok regards Alastair On 27/08/2018 20:48, Graham Inggs wrote: Hi Alastair Elpa seems to be another package with builds timing out. Confirmed on reproducible builders for i386 [1] and armhf [2]. Regards Graham [1] https://tests.reproducible-builds.org/debian/history/i386/elpa.html [2] https://tests.reproducible-builds.org/debian/history/armhf/elpa.html -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Commander Vimes didn’t like the phrase “The innocent have nothing to fear,” believing the innocent had everything to fear, mostly from the guilty but in the longer term even more from those who say things like “The innocent have nothing to fear.” - T. Pratchett, Snuff
Bug#907630: ITP: python-channels-redis -- Redis channel layer backend for Django Channels
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-channels-redis Version : 2.3.0 Upstream Author : Django Software Foundation * URL : https://github.com/django/channels_redis/ * License : BSD-3-clause Programming Lang: Python Description : Redis channel layer backend for Django Channels A Django Channels channel layer that uses Redis as its backing store, and supports both a single-server and sharded configurations, as well as group support. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAluH0AoRHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90WqnOQgAmuYOZAr7N8SMSz5OIp/i25EqWEBmvFVz P9sbwfKTOEkseX+uQ55XhE6v3S4AWMVSA6zbQJO/W2BjjJnj4LtzvRUSjjcSwZPn BXkUzOIAIfEiu+oG8JTUob6DDi04Bq3ElBAfITTlQMjEor/e8lt9q01IN0npwaRJ cGfJFtdTBqJN9baCf20LezOYX4fyHqV36MWl1EJsTD/50xet6eVEzflA9TgutkoJ tJe2lBxI3xfx6lQlNOD93Q592RpZyJ5k2pKSgLD2893rBzURGx1d44r0NfyxfLkq wFd0nwS0GtAGgF26eVcsFp35HYkbzP/rvqeQ38jl8MnI1Us7nfSdGA== =y+az -END PGP SIGNATURE-
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
On Thu, 30 Aug 2018 at 09:34:09 +0100, David Mohammed wrote: > Not clear here. Should I submit an upload to experimental? Yes please. smcv
Bug#894618: diaspora-installer: diff for NMU version 0.7.4.0+nmu1
Control: tags 894618 + patch Control: tags 894618 + pending Dear maintainer, I've prepared an NMU for diaspora-installer (versioned as 0.7.4.0+nmu1) and uploaded it to unstable. Regards. diff -Nru diaspora-installer-0.7.4.0/debian/changelog diaspora-installer-0.7.4.0+nmu1/debian/changelog --- diaspora-installer-0.7.4.0/debian/changelog 2018-03-27 08:41:03.0 +0200 +++ diaspora-installer-0.7.4.0+nmu1/debian/changelog 2018-08-30 10:59:22.0 +0200 @@ -1,3 +1,10 @@ +diaspora-installer (0.7.4.0+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Switch to libssl 1.1 (Closes: #894618) + + -- Gianfranco Costamagna Thu, 30 Aug 2018 10:59:22 +0200 + diaspora-installer (0.7.4.0) unstable; urgency=medium [ Joseph Nuthalapati ] diff -Nru diaspora-installer-0.7.4.0/debian/control diaspora-installer-0.7.4.0+nmu1/debian/control --- diaspora-installer-0.7.4.0/debian/control 2018-03-27 08:41:03.0 +0200 +++ diaspora-installer-0.7.4.0+nmu1/debian/control 2018-08-30 10:59:20.0 +0200 @@ -23,7 +23,7 @@ libcurl4-openssl-dev, libmagickwand-dev, libpq-dev, - libssl1.0-dev, + libssl-dev, libxml2-dev, libxslt-dev, libffi-dev,
Bug#907629: librsvg: Embedded code copies: assorted Rust libraries
Source: librsvg Version: 2.44.1-1 Severity: normal Tags: help librsvg contains "vendored" copies of various Rust libraries. Ideally we would use the vendored copy or the system copy of each library, whichever is (compatible and) newer, but I don't know enough Rust to know how to do that (and set the right Built-Using) for a package that is not built with dh-cargo. We can't use dh-cargo because the Rust code here is only part of a larger package that uses an Autotools build system. Some of the vendored libraries are available in Debian, others are not: [x] aho-corasick [ ] alga [x] ansi_term [ ] approx [x] arrayvec [x] atty [ ] backtrace [ ] backtrace-sys (in NEW) [x] bitflags [ ] bitflags-0.9.1 [x] byteorder [ ] c_vec [ ] cairo-rs [ ] cairo-sys-rs [ ] cast [x] cc [ ] cfg-if [x] chrono [x] clap [x] cloudabi [ ] criterion [ ] criterion-plot [ ] criterion-stats [ ] crossbeam-deque [x] crossbeam-epoch [x] crossbeam-utils [ ] cssparser [ ] cssparser-macros [x] csv [x] csv-core [ ] downcast-rs [x] dtoa [ ] dtoa-short [x] either [ ] failure [x] failure_derive [ ] float-cmp [x] fuchsia-zircon [x] fuchsia-zircon-sys [x] generic-array [ ] glib [ ] glib-sys [ ] gobject-sys [ ] handlebars [x] itertools [ ] itertools-num [x] itoa [x] lazy_static [x] libc [x] log [x] matches [ ] matrixmultiply [x] memchr [x] memoffset [ ] nalgebra [x] nodrop [ ] num-complex [x] num-integer [x] num-traits [ ] num-traits-0.1.43 [x] num_cpus [ ] owning_ref [ ] pango [ ] pango-sys [ ] pangocairo [ ] pangocairo-sys [ ] pest [ ] pest_derive [ ] phf [ ] phf_codegen [ ] phf_generator [x] phf_shared [x] pkg-config [x] proc-macro2 [ ] procedural-masquerade [x] quick-error [x] quote [ ] quote-0.3.15 [x] rand [ ] rand-0.4.2 [x] rand_core [ ] rawpointer [ ] rayon [ ] rayon-core [x] redox_syscall [x] redox_termios [x] regex [x] regex-syntax [x] rustc-demangle [ ] scopeguard [x] serde [x] serde_derive [x] serde_json [ ] simplelog [x] siphasher [ ] smallvec [ ] stable_deref_trait [x] strsim [x] syn [ ] syn-0.11.11 [ ] synom [x] synstructure [ ] term [x] termion [x] textwrap [ ] thread-scoped [x] thread_local [x] time [x] typenum [x] ucd-util [x] unicode-width [x] unicode-xid [ ] unicode-xid-0.0.4 [x] unreachable [x] utf8-ranges [x] vec_map [x] void [x] winapi Some of the vendored libraries are only there as developer dependencies, but "cargo test" requires that we have them anyway, as far as I can see. Perhaps the solution is to not run "cargo test"; I don't know. smcv
Bug#907628: bugs.debian.org: dislpay resolution not detected correctly
Package: bugs.debian.org Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? an unattended update probably created this did not do anything yet xrandr reports the maximum resolution is 1024 display is connected though vga driver is i915 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#907583: php7.0-json: The file /usr/share/php/Services/JSON.php triggers PHP deprecation warnings, file /usr/share/php/Services/JSON.php
Thank you for this reassignment, Ondřej!
So things become clear to me, and I can attach the patch to fix the bug.
Best regards, Georges.
Ondřej Surý a écrit :
> Control: reassign -1 php-services-json
>
> The file belongs to php-services-json package.
>
> Ondrej
> --
> Ondřej Surý
> ond...@sury.org
>
>
>
> > On 29 Aug 2018, at 20:49, Georges Khaznadar wrote:
> >
> > Package: php7.0-json
> > Version: 7.0.29-1+b2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > When upgrading one server from PHP5 to PHP7.0, and fixing problems
> > which this could create, I found that one of the services throwed
> > lots of warnings like:
> > "Methods with the same name as their class will not be constructors in a
> > future
> > version of PHP"
> >
> > The fix (which I applied successfully by hand), is to use the functions
> > "__construct()" as per
> > the documentation of PHP:
> > http://www.php.net/manual/en/language.oop5.decon.php
> >
> > The version of PHP7.0 on the server touched by the bug is currently the last
> > one,
> > 7.0.31-1
> >
> > Unfortunately, I could not figure out easily how the faulty file,
> > /usr/share/php/Services/JSON.php
> > is created by the build process, so I do not know how to make a useful
> > patch to
> > fix this issue.
> >
> > Best regards, Georges.
> >
> >
> >
> > -- Package-specific info:
> > Additional PHP 7.0 information
> >
> > PHP @PHP_VERSION SAPI (php7.0query -S):
> >
> > PHP 7.0 Extensions (php7.0query -M -v):
> >
> > Configuration files:
> > /etc/php/7.0/mods-available/json.ini
> > extension=json.so
> >
> >
> > -- System Information:
> > Debian Release: buster/sid
> > APT prefers stable
> > APT policy: (900, 'stable'), (499, 'testing'), (400, 'unstable')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
> > LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages php7.0-json depends on:
> > ii libc6 2.27-5
> > ii php-common 1:61
> > ii php7.0-common 7.0.29-1+b2
> > ii ucf3.0038
> >
> > php7.0-json recommends no packages.
> >
> > php7.0-json suggests no packages.
> >
> > Versions of packages php7.0-common depends on:
> > ii libc6 2.27-5
> > ii libssl1.1 1.1.0h-4
> > ii php-common 1:61
> > ii ucf 3.0038
> >
> > Versions of packages php7.0-cli depends on:
> > ii libc62.27-5
> > ii libedit2 3.1-20180525-1
> > ii libmagic11:5.33-3
> > ii libpcre3 2:8.39-9
> > ii libssl1.11.1.0h-4
> > ii libxml2 2.9.4+dfsg1-7+b1
> > ii mime-support 3.61
> > ii php7.0-common7.0.29-1+b2
> > ii php7.0-opcache 7.0.29-1+b2
> > ii php7.0-readline 7.0.29-1+b2
> > ii tzdata 2018e-1
> > ii ucf 3.0038
> > ii zlib1g 1:1.2.11.dfsg-1
> >
> > Versions of packages php7.0-cli suggests:
> > ii php-pear 1:1.10.5+submodules+notgz-1
> >
> > Versions of packages php7.0-fpm depends on:
> > ii libapparmor12.13-8
> > ii libc6 2.27-5
> > ii libmagic1 1:5.33-3
> > ii libpcre32:8.39-9
> > ii libssl1.1 1.1.0h-4
> > ii libsystemd0 239-7
> > ii libxml2 2.9.4+dfsg1-7+b1
> > ii mime-support3.61
> > ii php7.0-cli 7.0.29-1+b2
> > ii php7.0-common 7.0.29-1+b2
> > ii php7.0-opcache 7.0.29-1+b2
> > ii procps 2:3.3.15-2
> > ii tzdata 2018e-1
> > ii ucf 3.0038
> > ii zlib1g 1:1.2.11.dfsg-1
> >
> > Versions of packages php7.0-fpm suggests:
> > ii php-pear 1:1.10.5+submodules+notgz-1
> >
> > -- no debconf information
> >
>
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
Description: fix for deprecated constructors inherited from PHP4
This patch uses the constructors which exist since PHP5, and avoid the
deprecation message:
"Methods with the same name as their class will not be constructors in
a future version of PHP"
Author: Georges Khaznadar
Bug-Debian: https://bugs.debian.org/907583
---
--- php-services-json-1.0.3.orig/Services_JSON-1.0.3/JSON.php
+++ php-services-json-1.0.3/Services_JSON-1.0.3/JSON.php
@@ -139,7 +139,7 @@ class Services_JSON
* strings or numbers, if you return an object, make sure it does
* not have a toJSON method, otherwise an error will occur.
*/
-function Services_JSON($use = 0)
+function __construct($use = 0)
{
$this->use = $use;
$this->_mb_strlen= function_exists('mb_strlen');
@@ -909,7 +909,7 @@ if (class_exists('PEAR_Error')) {
class Services_JSON_Error extends PEAR_Error
{
-
Bug#896023: bug 896023: autopkgtest: dependency issue triggered mismatch between package version and its test
On Fri, 22 Jun 2018 18:36:21 +0200 Paul Gevers wrote: > > This all seems quite a lot of workaround. It would be > > better to treat britney as free software that we can modify to DTRT. > > Yes, but it is more difficult there. Indeed, it is the Right Thing To > Do. It was in my summary email¹ as my second work item. I have a version of britney running parallel to the real one now which changes that are supposed to do this. Already in a couple of cases, it has come up with solutions that prevented apt-get fallback and thus also this issue. I now realize better that I agree with Ian that autopkgtest should not get in the user's way if the user asks to test suite version A on package version B. So I am considering to mark this bug as wontfix once the real britney knows what to do. Paul signature.asc Description: OpenPGP digital signature
Bug#907627: please enable running the testsuite during the build
Package: src:intel-processor-trace Version: 1.6.1-1 Tags: patch please enable running the testsuite during the build. patch at http://launchpadlibrarian.net/386013612/intel-processor-trace_1.6.1-1_1.6.1-1ubuntu1.diff.gz There's also a new upstream version available.
Bug#900493: This looks like fixed
Hi, This looks fixed in the Experimental version (didn't check others). So I can close this bug. Cheers, Thomas Goirand (zigo)
Bug#907626: release.debian.org: Release status of non-Rust architectures?
Package: release.debian.org Severity: normal X-Debbugs-Cc: libr...@packages.debian.org, ru...@packages.debian.org, debian-m...@lists.debian.org Affects: src:librsvg The librsvg package in testing/unstable is currently lagging behind upstream by 1 year (2.40.x vs. 2.44.x) and I'm concerned that if there are security vulnerabilities in the lifetime of buster, we will not necessarily be able to fix them. Since 2.40.20, the 2.40.x branch is no longer supported by its upstream developer "except for emergencies". After 2.40.x, upstream started converting the internals of librsvg from C to Rust, for better memory-safety in the many interlocking parsers involved in interpreting SVGs. However, Debian still has release architectures that do not have cargo/dh-cargo/rustc (namely the 32-bit mips ports, mips and mipsel), so we cannot update to 2.42 or 2.44. Many of the ports architectures also don't have Rust available. Debian's default web browser, firefox-esr, also requires Rust and is also unbuildable on the 32-bit mips ports. What's the plan for non-Rust architectures? Are mips and mipsel intended to be supported for the lifetime of buster? Would it be acceptable to the release team to do architecture-specific removals of librsvg and its (many) reverse dependencies from testing on mips and mipsel? Another possible solution would be to upload a separate librsvg-2.40 source package that only builds binaries for mips and mipsel (and any other non-Rust-capable ports that want it). However, the GNOME team do not have enough developer time or mips expertise to maintain such a package, it would become useless as soon as dependent packages start requiring features of newer librsvg versions, and it would have the same security, bug and upstream maintenance concerns as the current librsvg 2.40.x in unstable. I've been doing some triaging, and a lot of open librsvg bugs are present in unstable but fixed in experimental, so I'm keen to update to the new upstream release if we can. Lack of Rust on mips and mipsel is not the only blocker, but it is the main blocker. (We also have a FTBFS during "make check" on ppc64el, reported upstream, and endianness-related test failures on s390x, which will be selectively ignored in the next upload because the bug exhibited by those tests does not seem RC.) Thanks, smcv
Bug#896698: deprecating needs-recommends
Control: tags -1 - patch Control: notforwarded -1 Control: clone -1 -2 Control: tags -1 wontfix Control: reassign -2 src:autodep8 Control: retitle -2 autodep8: don't use needs-recommends restriction Hi all, I have just pushed commit 9fade8dcb501250f704da9c77af1f8e6165dc941 that documents that we want to remove the needs-recommends option as we discussed in https://lists.debian.org/debian-ci/2018/06/msg00016.html. It also means I will not fix this bug and I hope in the foreseeable future we can drop this restriction. For autodep8, which uses this in examples and and the perl generator, this means that the script should get the list of Recommends and merge it with the test depends. That shouldn't be too hard and makes the current behavior more reliable already. I'll request a Lintian check to warn against the use of this restriction. Paul signature.asc Description: OpenPGP digital signature
Bug#905334: ffindex : autopkgtest regression: Segmentation fault
Control: clone -1 -2 Control: retitle -1 ffindex: missing build dependency on cmake Control: retitle -2 ffindex: ffindex_modify segfaults during autopkgtest On Thu, Aug 30, 2018 at 10:12:23AM +0200, Paul Gevers wrote: > Control: retitle -1 ffindex: FTBFS everywhere and amd64 binary segfaults > Control: tags -1 ftbfs > Control: severity -1 serious > > On Fri, 3 Aug 2018 10:37:39 +0200 Paul Gevers wrote: > > Since the upload of version 0.9.9.7+soedinglab+git20180802-1 the > > autopkgtest of your package started to fail. I have copied the output below. > > Apart from this, the package fails to build on the Debian build > infrastructure, so the uploaded amd64 binary was probably build in a > less optimal environment: > https://buildd.debian.org/status/package.php?p=ffindex=unstable > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ffindex.html These two seem unrelated, the FTBFS is a missing build dependency. I'm splitting this into two bugs for the likely unrelated problems. > Paul cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#907317: Forgot attachment?
Hi Chris, Thanks, but it looks like you forgot the attachment. Cheers, Thomas Goirand (zigo)
Bug#907622: llvm-toolchain-6.0: Please backport patch to fix miscompiled code (alignment)
On 08/30/2018 11:27 AM, Sylvestre Ledru wrote: > Thanks, it will be fixed in 6.0.1-7 > > I also requested a backport to 7 Great, thank you! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#907622: llvm-toolchain-6.0: Please backport patch to fix miscompiled code (alignment)
Le 30/08/2018 à 11:05, John Paul Adrian Glaubitz a écrit : > Source: llvm-toolchain-6.0 > Version: 1:6.0.1-6 > Severity: normal > Tags: patch upstream > User: debian-sp...@lists.debian.org > Usertags: sparc64 > > Hi! > > LLVM has a bug in its SROA implementation which can cause > the generated code to contain unaligned accesses. This > was fixed in [1], the corresponding Rust issue is [2]. Hello Thanks, it will be fixed in 6.0.1-7 I also requested a backport to 7 Cheers S
Bug#907623: RFP: FileManager-Actions -- filemanager extension to configure programs to launch
Package: wnpp Severity: wishlist * Package name: filemanager-actions Version : 3.4-1 Upstream Author : Pierre Wieser * URL : http://nautilus-actions.org * License : GPL Programming Lang: (C) Description : filemanager extension to configure programs to launch FileManager-Actions is a file-manager extension whose principal function is to allow the user to add arbitrary actions to the file-manager context menus, graphically via the FileManager-Actions -Config-Tool. These actions may be organized in menus and submenus, exported and shared with other desktop environments. This is the successor of nautilus-actions, which now also works in Nemo and Caja. There already exist debian package sources at https://launchpad.net/~tomtomtom/+archive/ubuntu/filemanager-actions/+packages offical repository: https://gitlab.gnome.org/GNOME/filemanager-actions
Bug#907620: lintian: Bogus 'unknown-runtime-tests-feature' tags
tags 907620 + pending thanks Fixed in Git, pending upload: https://salsa.debian.org/lintian/lintian/commit/ada27e4a4be328938b6e2227a4315a7faf511460 checks/testsuite.pm | 3 ++- debian/changelog | 4 t/tests/testsuite-general/debian/debian/tests/control | 2 +- 3 files changed, 7 insertions(+), 2 deletions(-) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#907621: llvm-3.8: Compiler Error for wrong conversion in LLVM/include/llvm/IR/ValueMap.h while building KLEE
Hello,
Le 30/08/2018 à 10:59, Kaipeng Zeng a écrit :
> Package: llvm-3.8
> Version: 1:3.8.1-24
> Severity: normal
>
> Dear Maintainer,
>
> When i was building KLEE follow the documentation:
> http://klee.github.io/build-llvm38/
> I got the compiler error:
> /usr/lib/llvm-3.8/include/llvm/IR/ValueMap.h:102:31: error: cannot
> convert ‘const std::unique_ptr llvm::TrackingMDRef> >’ to ‘bool’ in return
> bool hasMD() const { return MDMap; }
> It seems to be the same error that has been discussed:
> https://github.com/digego/extempore/issues/318
> and has been fixed:
> https://github.com/digego/extempore/pull/322/commits
>
I don't think this will be ever get fixed.
3.8 is starting to be old and I don't think it is worth doing a stable upload
for that.
Cheers,
Sylvestre
Bug#907622: llvm-toolchain-6.0: Please backport patch to fix miscompiled code (alignment)
Source: llvm-toolchain-6.0 Version: 1:6.0.1-6 Severity: normal Tags: patch upstream User: debian-sp...@lists.debian.org Usertags: sparc64 Hi! LLVM has a bug in its SROA implementation which can cause the generated code to contain unaligned accesses. This was fixed in [1], the corresponding Rust issue is [2]. Can you backport the fix? It affects all architectures, not just sparc64. It's just that the compiled binaries crash immediately on sparc64 while on other architectures the incorrect behavior might be more subtle. Thanks, Adrian > [1] https://reviews.llvm.org/D51335 > [2] https://github.com/rust-lang/rust/issues/53181 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#907621: llvm-3.8: Compiler Error for wrong conversion in LLVM/include/llvm/IR/ValueMap.h while building KLEE
Package: llvm-3.8
Version: 1:3.8.1-24
Severity: normal
Dear Maintainer,
When i was building KLEE follow the documentation:
http://klee.github.io/build-llvm38/
I got the compiler error:
/usr/lib/llvm-3.8/include/llvm/IR/ValueMap.h:102:31: error: cannot convert
‘const std::unique_ptr >’ to ‘bool’ in return
bool hasMD() const { return MDMap; }
It seems to be the same error that has been discussed:
https://github.com/digego/extempore/issues/318
and has been fixed:
https://github.com/digego/extempore/pull/322/commits
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'testing'),
(500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages llvm-3.8 depends on:
ii libc6 2.27-3
ii libgcc1 1:8.2.0-4
ii libllvm3.81:3.8.1-24
ii libstdc++68.2.0-4
ii libtinfo5 6.0+20161126-1+deb9u2
ii llvm-3.8-runtime 1:3.8.1-24
ii zlib1g1:1.2.11.dfsg-1
Versions of packages llvm-3.8 recommends:
ii llvm-3.8-dev 1:3.8.1-24
Versions of packages llvm-3.8 suggests:
pn llvm-3.8-doc
-- no debconf information
Bug#907620: lintian: Bogus 'unknown-runtime-tests-feature' tags
Package: lintian Version: 2.5.99 Severity: minor According to https://salsa.debian.org/ci-team/autopkgtest/blob/master/doc/README.package-tests.rst, there is one defined feature, namely: test-name Set an explicit test name for the log heading and the summary file for a Test-Command: inline test. When not given, these are enumerated like command1 However lintian does not seem to know this, as it produces the following output while checking upx-ucl 3.95-1: P: upx-ucl source: unknown-runtime-tests-feature test-name=bug775451-check1 paragraph starting at line 3 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug775451-check2 paragraph starting at line 6 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug775455-check paragraph starting at line 9 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug873260-check paragraph starting at line 12 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug882401-check paragraph starting at line 15 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug899190-check1 paragraph starting at line 18 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug899190-check2 paragraph starting at line 21 P: upx-ucl source: unknown-runtime-tests-feature test-name=bug907426-check paragraph starting at line 24 Regards, robert -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (990, 'unstable-debug'), (990, 'stable-updates'), (990, 'unstable'), (990, 'testing'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.31.1-4 ii bzip2 1.0.6-9 ii diffstat 1.61-1+b1 ii dpkg 1.19.0.5+b1 ii file 1:5.34-2 ii gettext0.19.8.1-7 ii intltool-debian0.35.0+20060710.4 ii libapt-pkg-perl0.1.34 ii libarchive-zip-perl1.63-1 ii libclass-accessor-perl 0.51-1 ii libclone-perl 0.39-1 ii libdpkg-perl 1.19.0.5 ii libemail-valid-perl1.202-1 ii libfile-basedir-perl 0.08-1 ii libipc-run-perl20180523.0-1 ii liblist-moreutils-perl 0.416-1+b3 ii libparse-debianchangelog-perl 1.2.0-12 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.74-1 ii libxml-simple-perl 2.25-1 ii libyaml-libyaml-perl 0.72+repack-1 ii man-db 2.8.4-2 ii patchutils 0.3.4-2 ii perl [libdigest-sha-perl] 5.26.2-7 ii t1utils1.41-2 ii xz-utils 5.2.2-1.3 Versions of packages lintian recommends: pn libperlio-gzip-perl Versions of packages lintian suggests: pn binutils-multiarch ii dpkg-dev 1.19.0.5 ii libhtml-parser-perl3.72-3+b2 ii libtext-template-perl 1.53-1 -- no debconf information
Bug#907171: prometheus FTBFS:
On Mon, 2018-08-27 at 19:18 +0100, Martín Ferrari wrote: > On 27/08/18 17:08, Adrian Bunk wrote: > > > How often did you try? > > > > I would say the probability to hit is somewhere around 50%: > > https://tests.reproducible-builds.org/debian/history/prometheus.html > > I just tried 20 builds, while using desktop applications that put some > extra strain on tHE CPU, and none failed.. Port 9090 isn't reserved or privileged at all afaik so it's not out of the question that some other random outgoing socket connection might be using it as a source port (or listening on it) at any given point, whether it is prom running on the host or something else. Does `nc -l -p 9090` repro the test failure perhaps? Unless the tests are run in their own network namespace (which provides some guarantees over what else might be bound to a port, I can't seem to find logs which would confirm or deny if a netns was in use here though) probably the test needs to use a random port or otherwise be tollerant of 9090 not being available. Maybe there is (or should be) an autopkgtest flag to request a clean netns be used? Ian.
Bug#895723: librsvg: FTBFS on powerpc arches
Control: severity -1 serious Control: tags -1 + ftbfs On Sun, 15 Apr 2018 at 16:08:05 +1000, Tim Lunn wrote: > Building 2.42.3 on Debian experimental ppc64el. powerpc and ppc64 seem to > have the same issues. > > Possibly due to linking with --as-needed . However not sure why this only > affects the powerpc arches. ppc64el is a release architecture, so this is RC (although it doesn't affect testing/unstable, and version-tracking correctly reflects that). smcv
Bug#884850: librsvg: FTBFS on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image
Version: 2.44.1-1 On Wed, 20 Dec 2017 at 12:31:47 +, Simon McVittie wrote: > > # Storing test result image at /tmp/masking-mask-01-b-out.png > > # 661 pixels differ (with maximum difference of 2) from reference image > > > > # Storing test result image at /tmp/masking-mask-01-b-diff.png > > not ok 16 /rsvg/reftest/svg1.1/masking-mask-01-b.svg > > FAIL: rsvg-test 16 /rsvg/reftest/svg1.1/masking-mask-01-b.svg This seems to be fixed in experimental. smcv
Bug#907214: OMEMO-encrypted file is not unencrypted before saving
Hi lovetox,
On Sun, 26 Aug 2018 22:08:13 +0200 forenjunkie
wrote:
> Hi,
>
> I tried with pix-art and could not reproduce the problem.
>
> Could you please try starting gajim from console with "-v" switch and
> provide logs from the point on when you receive the message
I attached the log and hope I actually copied all the relevant parts.
P.S. When asking the submitter of a bug a question, you may want to send
your mail to nnn-submitter@bugs.d.o instead of plain nnn@bugs.d.o, that
way the submitter actually gets your message, even if they are not
subscribed to the bug.
Regards
Sven
30.08.2018 10:21:32 (I) nbxmpp.client_nb raising event from transport: :DATA RECEIVED
_
18296920180830_102132980_109c.jpgMwohBS9+Heej+IDPaT77PQi/mH3bM8Gg1ZlsiHpflPLgVyQKEAwYAiIgiskE/LP/iMI8J4mFb9z2mCEQeBkudPuCv09PEO0ELCp7y5WoOGpasg==MwohBebf9IuZu6eVZlkYNytYJ5efTZ/Hxvksu4aLpYyyJUVMEAUYBiIgpABH/5O520MmWpMuaU4A7EDSAkDIGfFQ0oZnmV1F0rwQoXcCReigdw==Wsn7RJX1Qy99lseopBlAwg==
_
30.08.2018 10:21:32 (D) gajim.c.ged stanza-received Args: (,)
30.08.2018 10:21:32 (D) gajim.c.p.bytestream IBBAllIqHandler called syn_id->CSYQH5dP10oT
30.08.2018 10:21:32 (D) gajim.c.ged raw-iq-received Args: (,)
30.08.2018 10:21:32 (I) nbxmpp.transports_nb Plugging fd 26, W:True, R:True
30.08.2018 10:21:32 (I) gajim.c.jingle_ft transport value:
30.08.2018 10:21:32 (I) gajim.c.jingle_ft FT request: None
30.08.2018 10:21:32 (I) gajim.c.jingle_ft ourjid: s...@jabber.credativ.com/Laptop
30.08.2018 10:21:32 (D) gajim.c.ged jingle-request-received Args: (,)
30.08.2018 10:21:32 (D) gajim.c.jingle_ft Jingle FT request received
30.08.2018 10:21:32 (D) gajim.c.ged file-request-received Args: (,)
30.08.2018 10:21:33 (I) nbxmpp.transports_nb pollout called, state == CONNECTED
30.08.2018 10:21:33 (I) nbxmpp.transports_nb Plugging fd 26, W:False, R:True
30.08.2018 10:21:33 (I) nbxmpp.client_nb raising event from transport: :DATA SENT
_
_
30.08.2018 10:21:33 (D) gajim.c.ged stanza-sent Args: (,)
30.08.2018 10:21:33 (I) gajim.c.idle Idle time: 18
30.08.2018 10:21:35 (I) gajim.c.idle Idle time: 20
Gtk-Message: 10:21:36.337: GtkDialog mapped without a transient parent. This is discouraged.
30.08.2018 10:21:37 (I) gajim.c.idle Idle time: 0
30.08.2018 10:21:39 (I) gajim.c.idle Idle time: 0
30.08.2018 10:21:40 (I) gajim.c.p.bytestream send_file_approval: jingle session accept
30.08.2018 10:21:40 (I) gajim.c.jingle_transport candidate dict, {'host': '2003:5b:203b:100:6e0b:84ff:feb4:9eaf', 'candidate_id': 'b46af08b-2119-4a60-8c15-c357f13e8245', 'port': 28011, 'type': 'direct', 'jid': 's...@jabber.credativ.com/Laptop', 'priority': 8257536}
30.08.2018 10:21:40 (D) gajim.c.ged jingle-connected-received Args: (,)
30.08.2018 10:21:40 (D) gajim.c.socks5 Start listening for socks5 connection
30.08.2018 10:21:40 (I) nbxmpp.transports_nb Plugging fd 26, W:True, R:True
30.08.2018 10:21:40 (I) nbxmpp.transports_nb pollout called, state == CONNECTED
30.08.2018 10:21:40 (I) nbxmpp.transports_nb Plugging fd 26, W:False, R:True
30.08.2018 10:21:40 (I) nbxmpp.client_nb raising event from transport: :DATA SENT
_
20180830_102132980_109c.jpg182969
_
30.08.2018 10:21:40 (D) gajim.c.ged stanza-sent Args: (,)
30.08.2018 10:21:41 (I) nbxmpp.transports_nb pollin called, state == CONNECTED
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout removed for fd 26
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 26 on 55 seconds
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 26 on 120 seconds with function >
30.08.2018 10:21:41 (I) nbxmpp.client_nb raising event from transport: :DATA RECEIVED
_
_
30.08.2018 10:21:41 (D) gajim.c.ged stanza-received Args: (,)
30.08.2018 10:21:41 (D) gajim.c.p.bytestream IBBAllIqHandler called syn_id->4b554384-3c2d-4eb0-bf2a-b891f8876484
30.08.2018 10:21:41 (D) gajim.c.ged raw-iq-received Args: (,)
30.08.2018 10:21:41 (I) gajim.c.jingle_ft __on_iq_result
30.08.2018 10:21:41 (D) gajim.c.socks5 Trying to connect as receiver to cid arbuq563ff
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 32 on 30 seconds
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout removed for fd 32
30.08.2018 10:21:41 (D) gajim.c.socks5 Connected to cid arbuq563ff
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout removed for fd 32
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 32 on 30 seconds
30.08.2018 10:21:41 (I) nbxmpp.transports_nb pollin called, state == CONNECTED
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout removed for fd 26
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 26 on 55 seconds
30.08.2018 10:21:41 (I) nbxmpp.idlequeue read timeout set for fd 26 on 120 seconds with function >
30.08.2018 10:21:41 (I) nbxmpp.client_nb raising event from transport: :DATA RECEIVED
_
_
30.08.2018 10:21:41 (D) gajim.c.ged stanza-received
Bug#884849: librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image
Version: 2.44.1-1 On Wed, 20 Dec 2017 at 12:23:14 +, Simon McVittie wrote: > https://buildd.debian.org/status/fetch.php?pkg=librsvg=i386=2.40.20-1=1513733588=0 > https://buildd.debian.org/status/fetch.php?pkg=librsvg=hurd-i386=2.40.20-1=1513734324=0 > > # Storing test result image at /tmp/masking-path-04-b-out.png > > # 213 pixels differ (with maximum difference of 19) from reference image > > > > # Storing test result image at /tmp/masking-path-04-b-diff.png > > not ok 22 /rsvg/reftest/svg1.1/masking-path-04-b.svg > > FAIL: rsvg-test 22 /rsvg/reftest/svg1.1/masking-path-04-b.svg This seems to be fixed in experimental. smcv
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
Simon Not clear here. Should I submit an upload to experimental? If so I will do that asap David On Thu, 30 Aug 2018, 09:21 Simon McVittie, wrote: > Source: budgie-desktop > Version: 10.4+git20171031.10.g9f71bb8-1.2 > Severity: serious > Justification: https://bugs.debian.org/906015 > > The version of budgie-desktop in testing/unstable is not compatible with > mutter 3.29.x/3.30, which is required by the corresponding GNOME Shell > version. These are currently in experimental, but should be uploaded to > unstable soon. > > The version in Ubuntu 'cosmic' appears to have already been patched to > be compatible with GNOME 3.30. > > smcv >
Bug#907619: a2enmod: --force option not documented
Package: apache2 Severity: minor Dear Maintainer, man a2enmod does not document the --force (-f) option. Please consider describing its use. -- Thanks, Feri.
Bug#859848: upstream URL gone
Package: libnetcf1 Version: 1:0.2.8-1+b2 Followup-For: Bug #859848 source has moved to https://pagure.io/netcf -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnetcf1 depends on: ii augeas-lenses 1.11.0-1 ii libaugeas0 1.11.0-1 ii libc6 2.27-5 ii libnl-3-2003.4.0-1 ii libnl-route-3-200 3.4.0-1 ii libxml22.9.4+dfsg1-7+b1 ii libxslt1.1 1.1.32-2 libnetcf1 recommends no packages. libnetcf1 suggests no packages. -- no debconf information
Bug#907618: hddemux FTBFS
Source: hddemux Version: 0.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=hddemux=sid ... cleaning up --- cleaning up working directory /tmp/tmp.bu60TW2ktI ./testsuite: line 50: 6762 Terminated systemd-socket-activate -l "$ip:8853" --fdname=tls /usr/sbin/kresd -c "$d/kresd.conf" "$d" 2> "$d/kresd.err" ./testsuite: line 50: 6764 Terminated systemd-socket-activate -l "$ip:2000" -E=HTTP_TARGET="$ip:8853" -E DNS_TARGET="$ip:8853" "$hddemux" 2> "$d/hddemux.err" make[1]: *** [Makefile:13: check] Error 1
Bug#907617: cylc binary-any FTBFS
Source: cylc Version: 7.7.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cylc=sid ... debian/rules override_dh_fixperms make[1]: Entering directory '/<>' # Delete after install. Use packages instead. for p in Pyro cherrypy markupsafe jinja2 ; do \ rm -rf debian/python-cylc/usr/lib/python2.7/dist-packages/$p ; \ done chmod +x debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion chmod: cannot access 'debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion': No such file or directory make[1]: *** [debian/rules:37: override_dh_fixperms] Error 1
Bug#841468: sorl-thumbnail: make test suite work for Python 3 and pgmagick
fixed 841468 12.3+git20170708-2 thanks Forgot to close the bug in yesterdays upload.
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
Source: budgie-desktop Version: 10.4+git20171031.10.g9f71bb8-1.2 Severity: serious Justification: https://bugs.debian.org/906015 The version of budgie-desktop in testing/unstable is not compatible with mutter 3.29.x/3.30, which is required by the corresponding GNOME Shell version. These are currently in experimental, but should be uploaded to unstable soon. The version in Ubuntu 'cosmic' appears to have already been patched to be compatible with GNOME 3.30. smcv
Bug#905334: ffindex : autopkgtest regression: Segmentation fault
Control: retitle -1 ffindex: FTBFS everywhere and amd64 binary segfaults Control: tags -1 ftbfs Control: severity -1 serious On Fri, 3 Aug 2018 10:37:39 +0200 Paul Gevers wrote: > Since the upload of version 0.9.9.7+soedinglab+git20180802-1 the > autopkgtest of your package started to fail. I have copied the output below. Apart from this, the package fails to build on the Debian build infrastructure, so the uploaded amd64 binary was probably build in a less optimal environment: https://buildd.debian.org/status/package.php?p=ffindex=unstable https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ffindex.html Paul signature.asc Description: OpenPGP digital signature
Bug#905114: gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29
Control: forwarded -1 https://github.com/spin83/multi-monitors-add-on/issues/70 Control: severity -1 serious Control: tags -1 - experimental On Tue, 31 Jul 2018 at 11:40:04 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. GNOME 3.30 will be released soon, and we're starting to upload the 3.29.92 release candidate to unstable, so I'm escalating this to serious severity. smcv
Bug#907615: lxc-console not getting prompt with debian template
Package: lxc Version: 1:2.0.9-6 Severity: normal Steps to reproduce: install lxc, create a container with debian template (backing store doesn't matter in this case) lxc-create -n deb2 -t debian -B zfs --zfsroot=ocz/lxc lxc-console -n deb2 -l trace -o console_deb2.lxc.log Connected to tty 1 Type to exit the console, to enter Ctrl+a itself Log file: cat console_deb2.lxc.log lxc-console 20180830074928.590 WARN lxc_confile - confile.c:set_config_pivotdir:2262 - lxc.pivotdir is ignored. It will soon become an error. lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd:290 - command get_init_pid tries to connect command socket lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd_send:222 - Command "get_init_pid" connected to command socket lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd_send:238 - Command "get_init_pid" requested data of length 0 lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd_rsp_recv:128 - Command "get_init_pid received response lxc-console 20180830074928.590 DEBUGlxc_commands - commands.c:lxc_cmd_rsp_recv:152 - command get_init_pid response data length is 0 lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd:290 - command get_cgroup tries to connect command socket lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd_send:222 - Command "get_cgroup" connected to command socket lxc-console 20180830074928.590 TRACElxc_commands - commands.c:lxc_cmd_send:238 - Command "get_cgroup" requested data of length 8 lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_rsp_recv:128 - Command "get_cgroup received response lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_get_cgroup_path:456 - command get_cgroup successful for container "deb2" lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd:290 - command get_state tries to connect command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:222 - Command "get_state" connected to command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:238 - Command "get_state" requested data of length 0 lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_rsp_recv:128 - Command "get_state received response lxc-console 20180830074928.591 DEBUGlxc_commands - commands.c:lxc_cmd_rsp_recv:152 - command get_state response data length is 0 lxc-console 20180830074928.591 DEBUGlxc_commands - commands.c:lxc_cmd_get_state:569 - Container "deb2" is in "RUNNING" state. lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd:290 - command console tries to connect command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:222 - Command "console" connected to command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:238 - Command "console" requested data of length 0 lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_rsp_recv:128 - Command "console received response lxc-console 20180830074928.591 DEBUGlxc_commands - commands.c:lxc_cmd_rsp_recv:152 - command console response data length is 0 lxc-console 20180830074928.591 INFO lxc_commands - commands.c:lxc_cmd_console:719 - tty 1 allocated fd 5 sock 4. lxc-console 20180830074928.591 INFO console - console.c:lxc_console:696 - already group leader lxc-console 20180830074928.591 DEBUGconsole - console.c:lxc_console_sigwinch_init:151 - process 13995 created signal fd 6 to handle SIGWINCH events lxc-console 20180830074928.591 DEBUGconsole - console.c:lxc_console_winsz:71 - set winsz dstfd:5 cols:211 rows:65 lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd:290 - command console_winch tries to connect command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:222 - Command "console_winch" connected to command socket lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_send:238 - Command "console_winch" requested data of length 0 lxc-console 20180830074928.591 TRACElxc_commands - commands.c:lxc_cmd_rsp_recv:128 - Command "console_winch received response lxc-console 20180830074928.591 DEBUGlxc_commands - commands.c:lxc_cmd_rsp_recv:152 - command console_winch response data length is 0 Ubuntu template works as expected: lxc-console -n ubutest -l trace -o console_ubutest.lxc.log Connected to tty 1 Type to exit the console, to enter Ctrl+a itself Ubuntu 16.04.5 LTS ubutest pts/0 ubutest login: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux
Bug#905113: gnome-shell-extension-taskbar: global.screen is not available in GNOME Shell 3.29
Control: forwarded -1 https://github.com/zpydr/gnome-shell-extension-taskbar/issues/197 Control: tags -1 - experimental Control: severity -1 serious On Tue, 31 Jul 2018 at 11:39:32 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. GNOME 3.30 will be released soon, and we're starting to upload the 3.29.92 release candidate to unstable, so I'm escalating this to serious severity. smcv
Bug#905110: gnome-shell-extension-dash-to-panel: global.screen is not available in GNOME Shell 3.29
Control: tags -1 = patch fixed-upstream Control: severity -1 serious On Tue, 31 Jul 2018 at 11:38:17 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. GNOME 3.30 will be released soon, and we're starting to upload the 3.29.92 release candidate to unstable, so I'm escalating this to serious severity. There seem to be fixes upstream: https://github.com/home-sweet-gnome/dash-to-panel/commit/62061950746975b92cb1b48ade99616fd3f49732 https://github.com/home-sweet-gnome/dash-to-panel/commit/a676bbdc22037913ac1ca8d7288592797a937df7 https://github.com/home-sweet-gnome/dash-to-panel/commit/38fc3ef15477b3d024ccb826d1c7f2e76aa94f90 (I have not reviewed or tested these.) Thanks, smcv
Bug#905112: gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29
Control: tags -1 = fixed-upstream Control: severity -1 serious On Tue, 31 Jul 2018 at 11:39:14 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. GNOME 3.30 will be released soon, and we're starting to upload the 3.29.92 release candidate to unstable, so I'm escalating this to serious severity. There seem to be fixes upstream in v47 (I have not tested or reviewed them). Thanks, smcv
Bug#906448: dolfin: autopkgtest regression
Control: affects -1 src:openmpi Hi all, On Fri, 17 Aug 2018 20:40:09 +0200 Paul Gevers wrote: > With the upload of 2018.1.0.post1-8 the autpkgtest of your package > started to fail in testing. I copied the first output below (there are > multiple of this). Interestingly, on 2018-08-25 testing was improved somehow and dolfin migrated and the references in testing are passing now. However, openmpi has a new version in unstable, and I am seeing the same errors when we trigger the dolfin's autopkgtest with this new version. It looks like there are missing versioned dependencies somewhere. However, I don't rule out that this may be caused by something we need to improve in the migration software. If you know of packages that we should include from unstable while testing dolfin in testing with openmpi from unstable, let me know and I can try if that helps. > CMake Error in documented/auto-adaptive-poisson/cpp/CMakeLists.txt: > Imported target "dolfin" includes non-existent path > > > "/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent" > > in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: > > * The path was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and references files it does not > provide. Actually, it seems these message aren't in principle causing the test to fail. Why it fails is because these messages are written to stderr and the test only fails because it doesn't allow that (which is extremely good in this case). So until the autopkgtest is improved, DON'T add the allow-stderr restriction, or the test would pass while it probably shouldn't. Because later we see: -- Generating done -- Build files have been written to: /tmp/autopkgtest-lxc.l183w429/downtmp/build.sKL/src/dolfin-demo Scanning dependencies of target demo_bcs Scanning dependencies of target demo_auto-adaptive-poisson [ 1%] Building CXX object documented/bcs/cpp/CMakeFiles/demo_bcs.dir/main.cpp.o [ 2%] Building CXX object documented/auto-adaptive-poisson/cpp/CMakeFiles/demo_auto-adaptive-poisson.dir/main.cpp.o In file included from /usr/include/dolfin/common/dolfin_common.h:9, from /usr/include/dolfin.h:6, from /tmp/autopkgtest-lxc.l183w429/downtmp/build.sKL/src/dolfin-demo/documented/auto-adaptive-poisson/cpp/main.cpp:14: /usr/include/dolfin/common/types.h:24:10: fatal error: petscsys.h: No such file or directory #include ^~~~ In file included from /usr/include/dolfin/common/dolfin_common.h:9, from /usr/include/dolfin.h:6, from /tmp/autopkgtest-lxc.l183w429/downtmp/build.sKL/src/dolfin-demo/documented/bcs/cpp/main.cpp:25: /usr/include/dolfin/common/types.h:24:10: fatal error: petscsys.h: No such file or directory #include ^~~~ compilation terminated. compilation terminated. make[2]: *** [documented/auto-adaptive-poisson/cpp/CMakeFiles/demo_auto-adaptive-poisson.dir/build.make:63: documented/auto-adaptive-poisson/cpp/CMakeFiles/demo_auto-adaptive-poisson.dir/main.cpp.o] Error 1 make[2]: *** [documented/bcs/cpp/CMakeFiles/demo_bcs.dir/build.make:63: documented/bcs/cpp/CMakeFiles/demo_bcs.dir/main.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:91: documented/auto-adaptive-poisson/cpp/CMakeFiles/demo_auto-adaptive-poisson.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs make[1]: *** [CMakeFiles/Makefile2:146: documented/bcs/cpp/CMakeFiles/demo_bcs.dir/all] Error 2 make: *** [Makefile:84: all] Error 2 running C++ demos (serial) Test project /tmp/autopkgtest-lxc.l183w429/downtmp/build.sKL/src/dolfin-demo No tests were found!!! running C++ demos (MPI) Test project /tmp/autopkgtest-lxc.l183w429/downtmp/build.sKL/src/dolfin-demo No tests were found!!! But it doesn't FAIL on that, exit code is 0. That doesn't look right. Paul signature.asc Description: OpenPGP digital signature
Bug#907614: vmdb2: please provide documentation
Package: vmdb2 Version: 0.13.2-1 Severity: normal Hi, I am a user of autopkgtest and vmdebootstrap and stumbled across #904972. I would like to come up with a good replacement of vmdebootstrap using vmdb2. So I installed the package and wanted to read it's man page. But there is none. Looking into the package contents there doesn't seem to be any other kind of documentation either. I'm at a loss now as to how to make use of the vmdb2 package. The only thing I found was its --help output but that just seems to suggest that I need to create a config file of unknown format. Could you please provide documentation of vmdb2 in its binary package? Thanks! cheers, josch
Bug#905109: gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29
Control: severity -1 serious Control: tags -1 = patch fixed-upstream Control: forwarded -1 https://github.com/deadalnix/pixel-saver/pull/174 On Tue, 31 Jul 2018 at 11:37:37 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. GNOME 3.30 is almost ready for release and we're starting to upload components of the 3.29.92 release candidate to unstable, so I'm raising the severity to serious. Upstream merged a pull request that claims to fix this, https://github.com/deadalnix/pixel-saver/pull/174 (I have not reviewed or tested it). smcv
Bug#905107: gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29
Control: severity -1 serious Control: tags -1 - experimental On Tue, 31 Jul 2018 at 11:35:37 +0100, Simon McVittie wrote: > According to codesearch.debian.net, this extension uses the MetaScreen > via global.screen. MetaScreen no longer exists in GNOME 3.29, which is > starting to become available in experimental. This extension will need > code changes to use the MetaDisplay (global.display), > MetaWorkspaceManager (global.workspace_manager), MetaMonitorManager > (Meta.MonitorManager.get()) or MetaX11Display > (global.display.get_x11_display()). > > Because GNOME 3.29/3.30 is not a stable release yet and is not in > Debian unstable yet, you'll probably need to condition on the GNOME > Shell version. > > It looks as though gnome-shell-extension-pomodoro needs to use > global.display.get_current_monitor() in GNOME 3.29+, or > global.shell.get_current_monitor() otherwise. GNOME 3.29 has reached hard code freeze and will be released as 3.30 soon, and the Debian GNOME team are starting to upload it to unstable, so I'm raising this to serious severity. I opened https://github.com/codito/gnome-pomodoro/issues/365 upstream. smcv
Bug#907600: diffoscope: add option to ignore timestamp differences in containers
Dear Felipe, > diffoscope has been a very useful tool for me, in comparing dumps of > various sorts spit out by several systems. It would be great to have an > option to ignore timestamps Does the --exclude-directory-metadata option match your requirements? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#906012: libxcursor: CVE-2015-9262
On 27/08/18 18:22, Moritz Muehlenhoff wrote: On Mon, Aug 27, 2018 at 05:40:01PM +0800, Bjoern wrote: -- Begin Quote: -- From: Chris Lamb To: 906...@bugs.debian.org Cc: t...@security.debian.org Subject: Re: libxcursor: CVE-2015-9262 Date: Mon, 13 Aug 2018 08:18:27 +0100 [Message part 1 (text/plain, inline)] Hi security team, libxcursor: CVE-2015-9262 I have prepared an update for stretch: libxcursor (1:1.1.14-1+deb9u2) stretch-security; urgency=high * Non-maintainer upload by the Security Team. * Fix a denial of service or potentially code execution via a one-byte heap overflow. (CVE-2015-9262) Closes: #906012) -- Chris Lamb Mon, 13 Aug 2018 09:09:13 +0200 Full debdiff attached. Permission to upload to stretch-security? -- End Quote: Hi Chris & Security Team: Has Chris' patch for "Stretch" gone to /dev/null ? "Stretch"/stable remains exposed whilst old-stable, testing, and unstable have been patched. May I seek your enlightenment on this matter? This turned out to be non-exploitable. A fix will be provided via the stretch 9.6 point release. Cheers, Moritz Hi. As I am clearly unfamiliar with your processes, I really would appreciate the clarification to better my understanding and perhaps quell my concerns: * How far away is the 9.6 point release (given that 9.5 was released just over 1.5 months ago)? * Why could the issue not be dealt with by simply supplying the fix in the nearer term as a security update? Would it not be better to err on the side of caution? * I still would like to be pointed to the reference(s) and/or criteria used by the Security Team to determine that the issue is non-exploitable and a minor issue. I have searched around to find references regarding CVE-2015-9262 being non-exploitable, but have so far not found anything suggesting such - hence my request for a pointer. I ask your forgiveness for my persistence on this matter and beg that you don't dismiss me out of hand. What may very well be clear to you - unfortunately is not currently clear to me, or perhaps other potential future contributors to the Debian project I might add. I notice that a similar protocol of "ignored security issue"/"minor issue" is applied to the recent security bug raised against libx11. I really would welcome constructive feedback here. Kindest regards, Bjoern.
Bug#907613: rawtherapee: please make the build reproducible
Source: rawtherapee
Version: 5.4-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that rawtherapee could not be built reproducibly.
This is because it ships a file containing, inter alia, the build flags
used when compiling. We need to ship this file for the splash screen so
a patch is attached that simply removes this field.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/AboutThisBuild.txt.in b/AboutThisBuild.txt.in
index f48d39b..e6a49a8 100644
--- a/AboutThisBuild.txt.in
+++ b/AboutThisBuild.txt.in
@@ -9,7 +9,6 @@ Bit depth: ${PROC_BIT_DEPTH}
Gtkmm: V${GTKMM_VERSION}
Lensfun: V${LENSFUN_VERSION}
Build type: ${BUILD_TYPE}
-Build flags: ${CXX_FLAGS}
Link flags: ${LFLAGS}
OpenMP support: ${OPTION_OMP}
MMAP support: ${WITH_MYFILE_MMAP}
Bug#907609: libtirpc: CVE-2018-14621: Infinite loop in EMFILE case in svc_vc.c
Control: notfound -1 0.2.5-1 Control: notfixed -1 1.0.2-0.1 On Thu, Aug 30, 2018 at 09:19:49AM +0200, Salvatore Bonaccorso wrote: > Source: libtirpc > Version: 0.2.5-1 > Severity: important > Tags: patch security upstream > Control: fixed -1 1.0.2-0.1 > > Hi, > > The following vulnerability was published for libtirpc. > > CVE-2018-14621[0]: > Infinite loop in EMFILE case in svc_vc.c Did wrongly triaged this. The issue is actually only introduced in 0.3.3-rc3 upstream, so we never had a vulnerable version in Debian as the experimental version did as well contain the fix. Closing this bug as invalid. Regards, Salvatore
Bug#907610: kde-standard: ALT-blank does not work, applet not removable
Package: kde-standard Version: 5:102 Severity: normal Dear Maintainer, After an upgrade last week I observed some problems with kde : - after ALT- it's possible to type the name of an application but after RETURN the application does not start. - right click on the desktop have no effect (right click on an application works well) - all the applets are listed as "not desinstallable" in the install applet dialog. These problems appear also with a newly created user. With these bugs it's impossible for me to use kde for normal work. Thank's in advance for your help. With my best regards François -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kde-standard depends on: ii akregator 4:17.12.3-1 ii ark4:18.04.1-1 ii dragonplayer 4:17.08.3-1 ii gwenview 4:18.04.0-1 ii juk4:18.04.0-1 ii kaddressbook 4:17.12.3-1 ii kate 4:18.04.0-1 ii kcalc 4:18.04.1-1 ii kde-plasma-desktop 5:102 ii kde-spectacle 18.04.0-1 ii khelpcenter4:18.04.0-1 ii kmail 4:17.12.3-1 ii knotes 4:17.12.3-1 ii kopete 4:17.08.3-1 ii korganizer 4:17.12.3-2 ii kwalletmanager 4:18.04.1-1 ii okular 4:17.12.2-2 ii plasma-dataengines-addons 4:5.13.4-1 ii plasma-pa 4:5.13.4-1 ii plasma-runners-addons 4:5.13.4-1 ii plasma-wallpapers-addons 4:5.13.4-1 ii plasma-widgets-addons 4:5.13.4-1 ii polkit-kde-agent-1 4:5.13.4-1 ii sweeper4:18.04.1-1 Versions of packages kde-standard recommends: ii konq-plugins 4:18.04.0-1 ii plasma-nm 4:5.13.4-1 Versions of packages kde-standard suggests: pn skanlite -- no debconf information
Bug#907611: firefox-esr: FTBFS with iso-codes 4.0-1: No such file or directory: '/usr/share/xml/iso-codes/iso_639_3.xml'
Package: src:firefox-esr
Version: 60.1.0esr-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
As can be seen on the reproducibile builds¹, firefox-esr fails to build with
iso-codes 4.0-1. Relevant change seems to be:
* New upstream version 4.0
- This new release does no longer include the XML data files.
Please use the JSON data files from now on.
The failing part is:
---
debian/rules debian/control TESTDIR=
make[2]: Entering directory '/<>'
python -B debian/l10n/gen ach af an ar as ast az be bg bn-BD bn-IN br bs ca cak
cs cy da de dsb el en-GB en-ZA eo es-AR es-CL es-ES es-MX et eu fa ff fi fr fy-N
L ga-IE gd gl gn gu-IN he hi-IN hr hsb hu hy-AM ia id is it ja ka kab kk km kn k
o lij lt lv mai mk ml mr ms my nb-NO ne-NP nl nn-NO oc or pa-IN pl pt-BR pt-PT
rm ro ru si sk sl son sq sr sv-SE ta te th tr uk ur uz vi xh zh-CN zh-TW >
debian/l10n/browser-l10n.control
Traceback (most recent call last):
File "debian/l10n/gen", line 34, in
parser.parse('/usr/share/xml/iso-codes/iso_639_3.xml')
File "/usr/lib/python2.7/xml/sax/expatreader.py", line 105, in parse
source = saxutils.prepare_input_source(source)
File "/usr/lib/python2.7/xml/sax/saxutils.py", line 349, in
prepare_input_source
f = urllib.urlopen(source.getSystemId())
File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
return opener.open(url)
File "/usr/lib/python2.7/urllib.py", line 213, in open
return getattr(self, name)(url)
File "/usr/lib/python2.7/urllib.py", line 469, in open_file
return self.open_local_file(url)
File "/usr/lib/python2.7/urllib.py", line 483, in open_local_file
raise IOError(e.errno, e.strerror, e.filename)
IOError: [Errno 2] No such file or directory:
'/usr/share/xml/iso-codes/iso_639_3.xml'
make[2]: *** [debian/rules:150: debian/l10n/browser-l10n.control] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:257: override_dh_auto_clean] Error 2
---
Full build log attached.
-- dam
¹
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/firefox-esr.html
firefox-esr_amd64-2018-08-30T05:53:32Z.build.xz
Description: application/xz
Bug#907612: firefox: FTBFS with iso-codes 4.0-1: No such file or directory: '/usr/share/xml/iso-codes/iso_639_3.xml'
Package: src:firefox
Version: 61.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
Same as firefox-esr, firefox fails to build in current sid with iso-codes
4.0-1. The failing part is:
--
debian/rules debian/control TESTDIR=
make[2]: Entering directory '/<>'
python -B debian/l10n/gen ach af an ar as ast az be bg bn-BD bn-IN br bs ca cak
cs cy da de dsb el en-GB en-ZA eo es-AR es-CL es-ES es-MX et eu fa ff fi fr fy-N
L ga-IE gd gl gn gu-IN he hi-IN hr hsb hu hy-AM ia id is it ja ka kab kk km kn k
o lij lt lv mai mk ml mr ms my nb-NO ne-NP nl nn-NO oc or pa-IN pl pt-BR pt-PT r
m ro ru si sk sl son sq sr sv-SE ta te th tr uk ur uz vi xh zh-CN zh-TW > debian
/l10n/browser-l10n.control
Traceback (most recent call last):
File "debian/l10n/gen", line 34, in
parser.parse('/usr/share/xml/iso-codes/iso_639_3.xml')
File "/usr/lib/python2.7/xml/sax/expatreader.py", line 105, in parse
source = saxutils.prepare_input_source(source)
File "/usr/lib/python2.7/xml/sax/saxutils.py", line 349, in prepare_input_sour
ce
f = urllib.urlopen(source.getSystemId())
File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
return opener.open(url)
File "/usr/lib/python2.7/urllib.py", line 213, in open
return getattr(self, name)(url)
File "/usr/lib/python2.7/urllib.py", line 469, in open_file
return self.open_local_file(url)
File "/usr/lib/python2.7/urllib.py", line 483, in open_local_file
raise IOError(e.errno, e.strerror, e.filename)
IOError: [Errno 2] No such file or directory: '/usr/share/xml/iso-codes/iso_639_
3.xml'
make[2]: *** [debian/rules:148: debian/l10n/browser-l10n.control] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:255: override_dh_auto_clean] Error 2
--
Фром iso-codes changelog:
* New upstream version 4.0
- This new release does no longer include the XML data files.
Please use the JSON data files from now on.
Full build log attached. Reproducible builds also fail in sid:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/firefox.html
-- dam
firefox_amd64-2018-08-30T05:48:51Z.build.xz
Description: application/xz
Bug#907609: libtirpc: CVE-2018-14621: Infinite loop in EMFILE case in svc_vc.c
Source: libtirpc Version: 0.2.5-1 Severity: important Tags: patch security upstream Control: fixed -1 1.0.2-0.1 Hi, The following vulnerability was published for libtirpc. CVE-2018-14621[0]: Infinite loop in EMFILE case in svc_vc.c If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-14621 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14621 [1] https://bugzilla.novell.com/show_bug.cgi?id=968175 [2] http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=fce98161d9815ea016855d9f00274276452c2c4b Regards, Salvatore
Bug#907608: libtirpc: CVE-2018-14622: Segmentation fault in makefd_xprt return value in svc_vc.c
Source: libtirpc Version: 0.2.5-1 Severity: important Tags: patch security upstream Hi, The following vulnerability was published for libtirpc. CVE-2018-14622[0]: Segmentation fault in makefd_xprt return value in svc_vc.c If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-14622 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14622 [1] https://bugzilla.novell.com/show_bug.cgi?id=968175 [2] http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=1c77f7a869bdea2a34799d774460d1f9983d45f0 Regards, Salvatore
Bug#907607: scilab-cli doesn't start
Package: scilab-cli Version: 6.0.1-5 Severity: important Hello scilab-cli is failing on startup. STR: $ sudo apt-get install scilab-cli $ scilab-cli commons module not found. graphic_objects module not found. ui_data module not found. graph module not found. history_browser module not found. slint module not found. coverage module not found. installing the scilab pkg does not fix the issue. Sylvestre -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages scilab-cli depends on: ii scilab-data 6.0.1-5 ii scilab-include 6.0.1-5 ii scilab-minimal-bin 6.0.1-5 Versions of packages scilab-cli recommends: pn scilab-sivp Versions of packages scilab-cli suggests: ii gcc 4:8.1.0-1 ii gfortran4:8.1.0-1 pn scilab-ann pn scilab-plotlib pn scilab-scimax pn scilab-swt -- no debconf information
Bug#907606: fsck takes hours to complete, just due to slow screen output
Package: initscripts Version: 2.88dsf-59.9 In case of an unclean shutdown or system crash fsck run at boot time can take several hours to complete, printing thousands of useless messages like Clearing orphaned inode 123456789 (uid=1000, gid=1000, mode=0100700, size=28) It depends of the speed of your console, of course, but using a terminal it is pretty unlikely that you get anything faster than 115200 bits/sec. Some VGA consoles are not noticeable faster than this, either. I had the chance to verify this problem on a master-backup system: - On the master the fsck is running for >16 hours and is not completed yet. It writes to a terminal with 9600 bits/sec. - On the backup (manually migrated to become the new master) the file system check of the same partition took about 30 minutes, using "fsck -y >& fsck.log". It wrote 54 MByte logfile. This could be improved. Init is sysvinit-core. Thanx in advance Harri
Bug#897764: possible patch
Hi Hilko,
* Hilko Bengen [Tue Aug 21, 2018 at 10:27:27PM +0200]:
> it turns out that the alignof macro can probably be replaced by a GCC
> builtin. The attached patch does that. I am not committing this to Salsa
> right away because I am not 100% sure that __alignof__ (t) is
> functionally equivalent to the macro that has become illegal in GCC 8:
> #define alignof(type) offsetof (struct { char c; type x; }, x)
[...]
Thanks for the patch! I've forwarded this to the upstream developer,
so I can get his ACK before applying it.
regards,
-mika-
signature.asc
Description: Digital signature
Bug#906115: gnucash: Possible ibus interaction problem?
Package: gnucash Version: 1:3.2-1 Followup-For: Bug #906115 I was actually looking around for a possible solution to bug 839159 which I've started to experience, and ended up installing ibus. After installing ibus, I get the behaviour described in this bug - any key press on an account entry will cause gnucash to crash. Removing ibus, it all starts to work again (except for the issues I'm seeing from bug 839159, but that's a sepoerate thing). I'm wondering if this might be related to the problem that Michael is seeing in bug 906115, and whether there might be some kind of compatibility issue there? All the best, -DH. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (550, 'testing'), (500, 'stable-updates'), (450, 'unstable'), (450, 'stable'), (445, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnucash depends on: ii gnucash-common 1:3.2-1 ii guile-2.22.2.4+1-1 ii guile-2.2-libs 2.2.4+1-1 ii libaqbanking35 5.7.8-2 ii libaqbanking35-plugins 5.7.8-2 ii libatk1.0-0 2.28.1-1 ii libboost-date-time1.62.0 1.62.0+dfsg-8 ii libboost-filesystem1.62.01.62.0+dfsg-8 ii libboost-locale1.62.01.62.0+dfsg-8 ii libboost-regex1.62.0 1.62.0+dfsg-8 ii libboost-system1.62.01.62.0+dfsg-8 ii libc62.27-5 ii libcairo-gobject21.15.12-1 ii libcairo21.15.12-1 ii libcrypt-ssleay-perl 0.73.06-1 ii libdate-manip-perl 6.72-1 ii libdbi1 0.9.0-5 ii libfinance-quote-perl1.47-1 ii libgc1c2 1:7.4.2-8.3 ii libgcc1 1:8.2.0-4 ii libgdk-pixbuf2.0-0 2.36.12-2 ii libglib2.0-0 2.56.1-2 ii libgtk-3-0 3.22.30-2 ii libgwenhywfar60 4.20.0-1 ii libhtml-tableextract-perl2.15-1 ii libhtml-tree-perl5.07-1 ii libicu60 60.2-6 ii libjavascriptcoregtk-4.0-18 2.20.5-dmo1 ii libktoblzcheck1v51.49-4 ii libofx7 1:0.9.13-2 ii libpango-1.0-0 1.42.4-1 ii libpangocairo-1.0-0 1.42.4-1 ii libsecret-1-00.18.6-1 ii libsoup2.4-1 2.62.2-2 ii libstdc++6 8.2.0-4 ii libwebkit2gtk-4.0-37 2.20.5-dmo1 ii libwww-perl 6.35-2 ii libxml2 2.9.4+dfsg1-7+b1 ii libxslt1.1 1.1.32-2 ii perl 5.26.2-7 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gnucash recommends: ii gnucash-docs 3.2-1 ii python3-gnucash 1:3.2-1 ii yelp 3.28.1-1 Versions of packages gnucash suggests: ii libdbd-mysql0.9.0-6 pn libdbd-pgsql pn libdbd-sqlite3 -- Configuration Files: /etc/gnucash/environment changed [not included] -- no debconf information
Bug#907605: developers-reference: Alioth references in README-contrib
Package: src:developers-reference Severity: minor Tags: patch Dear developers-reference maintainers, there is still a reference to alioth in the file README-contrib. I've preaded this MR for it: https://salsa.debian.org/debian/developers-reference/merge_requests/2 Cheers, -- tobi
Bug#783307: ITP: fzf -- General-purpose command-line fuzzy finder
control: owner ! the two original ITP submitters are either missing, or not interested in fzf anymore. I'm taking over this ITP and this is not any kind of ITP hijack. -- Best,
