Bug#918848: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#918841: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#919002: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

Control: severity -1 important Control: tag -1 + moreinfo unreproducible I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace? X Josh Triplett: > Package: cargo > Version: 0.31.1-1 > Severity: grave

Bug#919064: scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute

Hi Java team, I realised that there is no comment on this bug yet. Since several of my packages got a "removal from testing warning": Can I help somehow? Not that I had the slightest idea what to do about this bug but may be you have some idea I could test? I've seen that there is a new

Bug#919856: gpg-agent: agent refuses operation again

On Sun, 20 Jan 2019, Norbert Preining wrote: > Any suggestions how to debug this? Enabling logging for gpg-agent I see: 2019-01-20 15:44:08 gpg-agent[25582] gpg-agent (GnuPG) 2.2.12 starting in supervised mode. 2019-01-20 15:44:08 gpg-agent[25582] using fd 3 for browser socket

Bug#919856: gpg-agent: agent refuses operation again

Package: gpg-agent Version: 2.2.12-1 Severity: important Hi all some recent changes (not sure whether this is gpg, X, systemd, or some other player like dbus) broke ssh functionality for gpg. Whenever I try to connect somewhere, I get: sign_and_send_pubkey: signing failed: agent

Bug#919855: s390x executables crash

Source: klibc Version: 2.0.5-1 Severity: serious While investigating some test failures on klibc upstream, I found that the new Debian version crashes on s390x. It looks like this is due to an address collision between the build ID in the shared library and the code in the executables. The

Bug#759130: Urgent translation update for camlidl

Hello Américo, you provided a man page translation for camlidl some time ago. I'm intending to update camlidl to include your translation. Unfortunately the man page does not build as your translation is out of date. I attached the current pt.po to this e-mail. If you update the file by

Bug#863533: Urgent translation update for camlidl

Hello Chris, you provided a man page translation for camlidl some time ago. I'm intending to update camlidl to include your translation. Unfortunately the man page does not build as your translation is out of date. I attached the current de.po to this e-mail. If you update the file by 2019-01-31

Bug#913027: ITP: hblock -- Improve your security and privacy by blocking ads, tracking and malware domains

Control: retitle -1 ITP: hblock -- Improve your security and privacy by blocking ads, tracking and malware domains Control: owner -1 Kun-Hung Tsai (蔡昆宏) Thanks! To Héctor, Hi Héctor, I am intending to package this good work. Is it OK to reference files you create for debian package under

Bug#919853: debhelper: should strip lead/trail white space when parsing a list of filenames

On 20-Jan-2019, Ben Finney wrote: > Tags: patch > > […] > Instead, the ‘Debian::Debhelper::Dh_Lib::filedoublearray’ function > should strip leading/trailing white space from each input line, and > only then decude whether to skip the input line:: > > # … > while () { >

Bug#919853: debhelper: should strip lead/trail white space when parsing a list of filenames

Package: debhelper Version: 12 Severity: normal Tags: patch When parsing a list of filenames from a config file, Debhelper should strip leading/trailing white space from each input line before deciding whether to skip that line. The current function ‘Debian::Debhelper::Dh_Lib::filedoublearray’

Bug#919721: [Pkg-fonts-devel] Bug#919721: fonts-firacode: looks broken on at least kitty and hexchat

Em 19 de janeiro de 2019 17:43:20 BRST, Fabian Greffrath escreveu: >Control: severity -1 normal > >Hi Antonio, > >thanks for the report, but I fail to see how a change in vertical >spacing could justify grave severity for a font package. Well this issue does make the package unusable, and

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

Santiago Vila 於 2019/1/20 上午1:35 寫道: > Package: src:libjstun-java > Version: 0.7.3+dfsg-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > >

Bug#198507: debhelper: fails if file name containing spaces are referenced in config files

Control: retitle -1 debhelper: fails if file name containing spaces are referenced in config files On 23-Jun-2018, Niels Thykier wrote: > retitle 198507 debhelper: config files cannot reference files with spaces That's a little ambiguous (spaces in the file contents, is one reasonable way to

Bug#919852: python-skimage-doc: broken symlink: /usr/share/doc/python-skimage-doc/html/_static/css/bootstrap-responsive.css -> ../../../../../javascript/bootstrap/css/bootstrap-responsive.css

Package: python-skimage-doc Version: 0.14.1-3 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m33.2s ERROR: FAIL: Broken symlinks:

Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1

Package: python3-link-grammar Version: 5.5.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m41.0s ERROR: FAIL: Broken

Bug#919851: reproducible: re-deploy jtx1c

Package: jenkins.debian.org Severity: normal jtx1c-armhf-rb.debian.net had a disk failure, and thus needed to be re-installed. It has now been reinstalled, awaiting configuration. New ssh keys: 256 SHA256:V8CIP3rzxgTHDjzhhVFPbTcfB+hHwppvcjbhQEfFTGQ root@jtx1c (ECDSA) 256

Bug#919849: salt-doc: broken symlinks: /usr/share/doc/salt/html/_static/*/bootstrap* -> ../../../../../twitter-bootstrap/files/*/bootstrap*

Package: salt-doc Version: 2018.3.3+dfsg1-2 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m29.8s ERROR: FAIL: Broken symlinks:

Bug#919848: tclxml-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtclxmlstub.a -> libtclxmlstub3.2.a

Package: tclxml-dev Version: 1:3.2.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m28.5s ERROR: FAIL: Broken symlinks:

Bug#919847: ruby-rails-assets-markdown-it: missing Depends: libjs-markdown-it

Package: ruby-rails-assets-markdown-it Version: 8.4.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m28.5s ERROR: FAIL:

Bug#858855: gpodder: subscribing to https://requestforcomments.de/feed raises an ssl error

On Sat, Apr 15, 2017 at 10:18:27AM -0700, tony mancill wrote: > On Fri, Apr 14, 2017 at 09:52:37PM +0200, Thomas Perl wrote: > > This seems to be the following upstream bug: > > https://github.com/gpodder/gpodder/issues/265 > > > > A fix would be to upgrade to Python 2.7.9, as indicated here: > >

Bug#821057:

Control: fixed -1 18.04.5-1 This bug seems to no longer occur in 18.04.5-1.

Bug#919846: ruby-rails-assets-highlightjs: missing Depends: libjs-highlight.js

Package: ruby-rails-assets-highlightjs Version: 9.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m30.0s ERROR: FAIL:

Bug#919845: python-mongoengine-doc: missing Depends: ${sphinxdoc:Depends}

Package: python-mongoengine-doc Version: 0.15.3-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m27.5s ERROR: FAIL: Broken

Bug#919844: changetrack: "find2perl" is missing and thus breaks filename patterns prefixed with "@"

Package: changetrack Version: 4.7-5 Severity: normal Tags: patch upstream Dear Maintainer, changetrack allows the specification of patterns for "find" to be used in /etc/changetrack. A use case is the exclusion of specific files below /etc/ from the change tracking. Example (excluding daily

Bug#894260: Abbiamo bisogno di Content writer

Buongiorno , non avendo ricevuto risposta alla precedente email, le forniamo qualche dettaglio sul nostro portale. ProntoPro è il primo sito per numero di utenti che mette in contatto domanda e offerta di lavoro professionale e artigianale. oltre 500'000 clienti hanno già usato ProntoPro e

Bug#919843: lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> /build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*

Package: lirc-doc Version: 0.10.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m24.4s ERROR: FAIL: Broken symlinks:

Bug#919808: forensics-extra: please don't depend on pxz which shall be removed for buster

Em sáb, 19 de jan de 2019 às 16:58, Holger Levsen escreveu: > > forensics-extra currently depends on pxz, however even xz in Stretch now > supports parallel compression with the -T switch. Therefore I would like > to remove pxz from Buster, which is only possible if forensics-extra > (and

Bug#919842: Jetson-tx1: successful, but required customized boot media

implementation lacks some features (SMP, SATA). Once booted with the USB firmware blob loaded and correct .dtb loaded, the install worked fine. live well, vagrant -- Package-specific info: Boot method: microSD Image version: https://d-i.debian.org/daily-images/arm64/20190119-02:06/netboot

Bug#919841: node-istanbul: broken symlinks: /usr/lib/nodejs/istanbul/lib/assets/vendor/prettify.{css,js} -> ../../../../../../share/javascript/prettify.{css,js}

Package: node-istanbul Version: 0.4.5+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m33.0s ERROR: FAIL: Broken symlinks:

Bug#919834: libmono-btls-shared.so: undefined symbols: needs -pthread

I'll try to get around to forwarding this upstream As you guessed, it's not directly an issue because mono-btls-shared is a plugin used by /usr/bin/mono-sgen, which is linked adequately. On 19/01/2019 20:35, Paul Wise wrote: > Package: mono-runtime-common > Version: 5.18.0.240+dfsg-1 > Severity:

Bug#919840: sqwebmail: leaves broken symlink after purge: /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf

Package: sqwebmail Version: 6.0.0+1.0.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m54.4s ERROR: FAIL: Broken symlinks:

Bug#919839: lintian: package-contains-real-file-outside-usr false positives in /lib

Package: lintian Version: 2.5.122 Severity: normal X: mariadb-server-10.3: package-contains-real-file-outside-usr lib/systemd/ X: mariadb-server-10.3: package-contains-real-file-outside-usr lib/systemd/system/ X: mariadb-server-10.3: package-contains-real-file-outside-usr

Bug#908783: ITP: firmware-microbit-micropython -- MicroPython runtime for the BBC micro:bit

On Sat, 19 Jan 2019 at 07:57, Petter Reinholdtsen wrote: > > [Nick Morrott] > > It is being reviewed at the moment. > > Very good. Any estimate on when this part is done? firmware-microbit-micropython is now in NEW, so hopefully the next response you get from this ITP will be that it is closed

Bug#919838: supercollider-common: broken symlinks: /usr/share/SuperCollider/HelpSource/lib/codemirror*.min.js -> ../../../javascript/codemirror/*.js

Package: supercollider-common Version: 1:3.10.0+repack-0.1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m29.1s ERROR: FAIL:

Bug#919837: libcamomile-ocaml-dev: broken symlinks: /usr/share/man/man1/camomile*.{byte,opt}.1.gz -> camomile*.1.gz

Package: libcamomile-ocaml-dev Version: 1.0.1-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m42.3s ERROR: FAIL: Broken

Bug#132542: sysvinit: please make /etc/init.d/rcS a conffile

> That's not what my argument is -- what I mean, is that there's many > more components that need to stick strictly to files not on /usr > during that phase of the boot, sysv-rc being only a single one. > Efforts to keep it working are a waste of time, not because you won't > get to simplify

Bug#919836: jupyter-sphinx-theme-common: broken symlinks: /usr/share/jupyter_sphinx_theme/jupyter/static/boots{trap,watch}-2

Package: jupyter-sphinx-theme-common Version: 0.0.6+ds1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m30.4s ERROR: FAIL:

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

Thanks but one still must forbid # aptitude search ~U iFA libilmbase23 iFA libopenexr23 if gimp is to start on experimental.

Bug#919835: mgba; AppStream metadata isn't being used because of its license

Source: mgba Version: 0.6.3+dfsg1-2 X-Debbugs-CC: sergio_...@yahoo.com.br The AppStream metadata that was added to the Debian package isn't being used because its metadata_license isn't on the short list of approved licenses. I encourage you to consider relicensing your metadata as CC0-1.0. From

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Le dim. 20 janv. 2019 à 02:12, Andreas Beckmann a écrit : > Followup-For: Bug #905415 > Control: reopen -1 > Control: reassign -1 libnode-dev 10.15.0~dfsg-8 > Control: retitle -1 libnode-dev: broken symlinks: > /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} > > Hi, > >

Bug#919752: mu-editor: Explain better what is wrong when micropython firmware is missing?

The root cause of this issue rests with the way mu-editor is currently packaged. Upstream, mu-editor contains not just the editor but also uflash and the compiled MicroPython hex, so flashing the micro:bit works out of the box. In Debian, such bundling is not permitted, hence I have split out

Bug#919834: libmono-btls-shared.so: undefined symbols: needs -pthread

Package: mono-runtime-common Version: 5.18.0.240+dfsg-1 Severity: minor File: /usr/lib/libmono-btls-shared.so User: debian...@lists.debian.org Usertags: undefined-symbol adequate libmono-btls-shared.so needs to compile and link with -pthread, see the output of adequate, symtree and objdump below.

Bug#919743: RFS: rumur/2019.01.12-1 [ITP]

On Fri, Jan 18, 2019 at 06:43:13PM -0800, Matthew Fernandez wrote: > * Package name: rumur > Version : 2019.01.12-1 > dget -x > https://mentors.debian.net/debian/pool/main/r/rumur/rumur_2019.01.12-1.dsc > Changes since the last upload: > > Initial release. Closes #919220. The

Bug#919819: RFS: knowthelist/2.3.1

On Sat, Jan 19, 2019 at 10:21:42PM +0100, Mario Stephan wrote: > * Package name: knowthelist > Version : 2.3.1 >dget -x > https://mentors.debian.net/debian/pool/main/k/knowthelist/knowthelist_2.3.1.dsc May I ask why did you convert the package to native? * the upstream package

Bug#919833: 90% of shell scripts probably don't have a .sh extension

Package: bash-completion Version: 1:2.8-5 Severity: wishlist File: /usr/share/bash-completion/completions/sh I think 90% of shell scripts don't have a .sh extension. Therefore $ sh anyf should still complete to $ sh anyfile Thanks.

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important The only solution is to revert to 4.17. Jan 19 18:14:35 vhost004 kernel: INFO: task btrfs-transacti:691 blocked for more than 120 seconds. Jan 19 18:14:35 vhost004 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Yes, the btrfs hung task problem still exists in the latest kernel. Jan 19 18:40:41 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:40:41 vhost003 kernel: Tainted: G I E

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Followup-For: Bug #905415 Control: reopen -1 Control: reassign -1 libnode-dev 10.15.0~dfsg-8 Control: retitle -1 libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} Hi, the package reorganisation changed th eissue but did not completely resolve

Bug#660687: Update on ITA: xml-core

Hi guys, I haven't had much time to work on this over the last few weeks. Other priorities have showed up. I'll get back to this when I get more time. In the meantime if someone else wants to get on, take care of the bug reports and adopt the package, go ahead. If not, I'll finish that later.

Bug#919832: gap-table-of-marks: broken symlink: /usr/share/doc/gap-table-of-marks/doc -> ../../gap/pkg/Tomlib/doc

Package: gap-table-of-marks Version: 1.2.7-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + gap-libs Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m24.4s

Bug#919831: libcds-moc-java: FTBFS (The code being documented uses packages in the unnamed module)

Package: src:libcds-moc-java Version: 5.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper

Bug#919747: gnome-keysign: please package gnome-keysign 1.0.0

On Sat 2019-01-19 18:53:28 +0100, Sascha Steinbiss wrote: > as you may not have noticed, I have prepared packaging for 1.0.0 in the > gnome-keysign repo on Salsa [1]. It took some work because I had to > switch everything to Python 3 due to dependency requirements (some > Python modules newly

Bug#919614: RFS: note/1.3.26-2 [ITA]

Hello Dmitry, > Uploaded. There is some things you may want to address in next revision: > > * debian/watch uses plain http. Any chance for https? > * there is a lot of spelling errors. Please fix them and submit patch >upstream. > * /usr/share/perl5/NOTEDB/README is bad. Move it into

Bug#132542: sysvinit: please make /etc/init.d/rcS a conffile

On Sat, Jan 19, 2019 at 07:34:26PM +, Dmitry Bogatov wrote: > [2019-01-18 02:20] Adam Borowski > > That ship has long since sailed. What's the point of making sysv-rc support > > non-/usr early boot if the rest of the system doesn't? It may still work on > > some simple installs, but even

Bug#919830: ansible-doc: missing Depends: ${sphinxdoc:Depends}

Package: ansible-doc Version: 2.7.5+dfsg-2 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m26.3s ERROR: FAIL: Broken symlinks:

Bug#919827: asterisk-espeak: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

Package: src:asterisk-espeak Version: 5.0~1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules dh_testroot

Bug#919829: libatteanx-store-sparql-perl: FTBFS (failing tests)

Package: src:libatteanx-store-sparql-perl Version: 0.010-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch test -x debian/rules

Bug#919828: asterisk-opus: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

Package: src:asterisk-opus Version: 13.7+20171009-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

On Sat, Jan 19, 2019 at 04:51:02PM -0500, Abdelhakim Qbaich wrote: > Hi, > > I've attached a patch and made an upstream pull request. Hello Abdelhakim Qbaich, Thank you for the patch. I have applied it and a few other misc packaging changes and uploaded to the archive. Cheers, tony

Bug#919826: linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic

Package: linux-image-4.19.0-1-arm64 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading kernel in Buster from 4.18.0-3-arm64 via apt-get

Bug#919758: [Pkg-xen-devel] Bug#919758: xen-hypervisor-4.8-amd64: Wrong examples provided in GRUB config file

Hi Gergely, On 1/19/19 9:32 AM, root wrote: > Package: src:xen > Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11 > Severity: minor > > Dear Maintainer, > > the GRUB configuration file /etc/defaults/grub.d/xen.cfg contains incorrect > examples: > > 1. Bad syntax for dom0 memory allocation settings:

Bug#919395: Heads up to release team about MariadB 10.3

On 2019-01-19 21:14, Andreas Beckmann wrote: > Getting back to the current case: I assume this is caused by > libmariadbclient-dev being turned into a virtual package provided by > libmariadb-dev. I'll test whether reintroducing a transitional package > would improve the situation. Might require a

Bug#910627: closed by Louis-Philippe Véronneau (Bug#910627: fixed in nostalgy 0.2.36-1.1)

On 19.01.19 22:06, Debian Bug Tracking System wrote: > It has been closed by Louis-Philippe Véronneau . Thanks, Louis-Philippe, one less package I have to take care about in a private repository. Great work. Thanks so much!!! Best, Daniel signature.asc Description: OpenPGP digital signature

Bug#919507: Reboot required patch for Debian policy

On Sat, 19 Jan 2019 11:10:09 -0700 Sean Whitton wrote: > On Fri 18 Jan 2019 at 12:04PM -0600, Karl O. Pinc wrote: > > +Maintainer scripts can signal that a reboot is required to fully > > apply +the changes to the system by touching > > ``/run/reboot-required`` and +adding the package name to >

Bug#919824: [Pkg-opencl-devel] Bug#919824: clblas: under pocl-opencl-icd, aborts with !"PIC Level"

On 2019-01-20 00:16, Rebecca N. Palmer wrote: > Source: pocl,clblas Which version? Which architecture? If you suspect caching to be a problem, try something like this: export POCL_CACHE_DIR=$(mktemp -d -p $(pwd)) Andreas

Bug#919824: clblas: under pocl-opencl-icd, aborts with !"PIC Level"

Source: pocl,clblas (Probably really only one of them, but I don't know which.) When using pocl-opencl-icd, clblas sometimes exits with module flag identifiers must be unique (or of 'require' type) !"PIC Level" LLVM ERROR: Broken module found, compilation aborted! The test suites of both

Bug#919765: dolphin not starting

I just wanted to say that with the following updates baloo-kf5:amd64 5.51.0-1 default-mysql-client-core:amd64 1.0.4 default-mysql-server-core:amd64 1.0.4 kio:amd64 5.51.0-1 kpackagetool5:amd64 5.51.0-1 kwayland-data:amd64 4:5.51.0-1 libkf5archive5:amd64 5.51.0-1 libkf5attica5:amd64 5.51.0-1

Bug#900918: debian-installer: Please make the generated images reproducible

date as well.) Checking all MINIISO occurrences might also make sense > I suppose? FWIW, dropping all fontconfig-related bits (see attached patch) makes it possible to confirm only mini.iso (regular and gtk ones) are showing differences now: installer-amd64/20190119/images/MD5SUMS installer

Bug#918366: FTBFS for armhf on arm64, fails some tests

On Mon, 07 Jan 2019 21:10:31 +0200, Steve McIntyre wrote: > base/NSInvocation/general.m: > Failed test: general.m:208 ... Can send/return NSRect I tried to reproduce this on gcc117 (an AMD Opteron 1100 machine from the GCC Compile Farm, which should be able to run 32-bit executables according

Bug#904657: voltron: fails to install with Python 3.7 (was: Re: update)

On 2019-01-19 21:55, Kienan Stewart wrote: > I tested a proposed patch from the upstream github repository which allows > the package to build and run : https://github.com/snare/voltron/pull/243 > > I'm not sure if there are other side-effects to the patch, since the async > (now asynchronous)

Bug#917161: pulseaudio: Pulseaudio takes longer to start than default systemd timeout (again)

Thanks for letting me know. I just checked and I do have 240-4 installed now for udev (and libudev1). So i timed a restart of pulseaudio through systemd again and this is the result: $ time systemctl --user restart pulseaudio.service real    0m1.660s user    0m0.003s sys 0m0.000s So it

Bug#919806: sbcl: FTBFS randomly (failing tests)

retitle 919806 sbcl: FTBFS randomly (failing tests) severity 919806 important thanks The build does not always fail. Thanks.

Bug#914466: RM: icu4j-49 -- ROM; Obsolete, no longer used

Control: tags -1 - moreinfo Le 27/11/2018 à 08:20, Scott Kitterman a écrit : > Checking reverse dependencies... > # Broken Build-Depends: > lucene4.10: libicu4j-49-java Good catch, thank you. It's now removed in lucene4.10/4.10.4+dfsg-4

Bug#916977: snoopy w/ ld preload enabled breaks "apt upgrade" jessie-to-buster

Hello, I use testing and updated hundreds of package without any trouble. Please, could you give an example of a package that fails to upgrade? Greetings, Marcos. On 11/1/19 18:52, Adrian Bunk wrote: > On Thu, Dec 20, 2018 at 05:26:25PM -0500, deb...@mailinator.com wrote: >> Package: snoopy

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

tags 919737 - unreproducible moreinfo thanks Based on the last message by Jonas, I'm removing those tags which do not apply here. Thanks.

Bug#919795: thunderbird: cannot save changes to addressbook

Few more data points (3rd being most important): 1) while I can't edit or create new contacts under "Personal Address Book", I: - can create new list - via "New List" button - can add/remove members on existing list by right clicking on the list, selecting "Edit List" - but can't add

Bug#919823: harp: FTBFS in sid (ERROR: CODA library and/or header file not found)

Package: src:harp Version: 1.5+data-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch --with python3

Bug#900918: debian-installer: Please make the generated images reproducible

ple times in the same sid devel chroot: installer-amd64/20190119/images/cdrom/gtk/initrd.gz installer-amd64/20190119/images/hd-media/boot.img.gz installer-amd64/20190119/images/hd-media/gtk/initrd.gz installer-amd64/20190119/images/MD5SUMS installer-amd64/20190119/images/netboot/g

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

user debian-rele...@lists.debian.org usertag 919737 + bsp-2019-01-ca-montreal tags 919737 + unreproducible moreinfo thank you Hi, I tried building this package (underscore-1.8.3~dfsg) in a clean buster chroot (with sbuild) and a clean unstable chroot (also with sbuild), and it worked in both

Bug#901982: diffoscope: crash comparing ext4 filesystems: AttributeError: 'FsImageContainer' object has no attribute 'g'

ainer' object has no attribute 'g' FWIW I'm also seeing this in unstable when trying to compare two boot.img.gz files produced as part of a debian-installer builder: (sid-amd64-devel)kibi@wodi:~/debian-installer$ diffoscope d-i-[89]/extract/installer-amd64/20190119/images/hd-media/boot.img.gz

Bug#912087: reassign to systemd #912087 | openssh-server: Slow startup after the upgrade to 7.9p1

Follow up report: Bare metal install onto an APM Mustang board (see debian arm64 buildds) of debian-buster-DI-alpha4-arm64-DVD-1.iso [1] sshd takes > 7 min to start [2] This is clearly going to be a problem for Buster as things stand... /Andy [1] DI alpha4 uses kernel 4.18.20-2

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

Control: tags -1 +patch On Sat, 19 Jan 2019 16:51:02 -0500 Abdelhakim Qbaich wrote: > Hi, > > I've attached a patch and made an upstream pull request. > > On Thu, 27 Dec 2018 22:52:58 + Santiago Vila > wrote: > > Package: src:jhove > > Version: 1.20.1-4 > > Severity: serious > > Tags:

Bug#919822: gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import

Source: gitlab Version: 11.5.6+dfsg-1 Severity: grave Tags: security upstream fixed-upstream Justification: user security hole Hi, The following vulnerability was published for gitlab, and fixed in 11.6.4, 11.5.7, and 11.4.14. CVE-2019-6240[0]: RESERVED If you fix the vulnerability please also

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

Hi, I've attached a patch and made an upstream pull request. On Thu, 27 Dec 2018 22:52:58 + Santiago Vila wrote: > Package: src:jhove > Version: 1.20.1-4 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > >

Bug#795442: (no subject)

Hi Tiago, >So, waiting from upstream answer. thanks for looking into this… I talked to upstream about this a while ago and it ended with that they don’t have much interest in the /etc/papersize thing, which is pretty distro-specific, but would merge a patch if someone would write it. I looked

Bug#915856: sphinx: Failed cross building with Build-Depends on python3-sphinx

Hi Kaliko! Sorry that it took so long for me to reply. I was putting most of my Sphinx time into preparing the Sphinx 1.8 transition for sid. On Fri, Dec 07, 2018 at 11:42:09AM +0100, kaliko wrote: > here is a follow up of a discussion started on irc:debian-devel with > mitya57. > > I'm trying

Bug#919821: New upstream version available

Package: amsynth Version: 1.6.4-2 Severity: wishlist Hello, there seems to be a new version (1.8.0) for this software at amsynth.github.io Would it be possible to update the package? Thanks

Bug#919820: mysql-connector-python: CVE-2019-2435

Source: mysql-connector-python Version: 8.0.11-1 Severity: grave Tags: security upstream Control: found -1 2.1.6-1 Hi, The following vulnerability was published for mysql-connector-python. CVE-2019-2435[0]: | Vulnerability in the MySQL Connectors component of Oracle MySQL | (subcomponent:

Bug#919529: CVE-2019-6256

Hey! On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote: > Control: found -1 2016.11.28-1 > > On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote: > > Source: liblivemedia > > Severity: grave > > Tags: security > > > > Please see

Bug#919819: RFS: knowthelist/2.3.1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "knowthelist" * Package name: knowthelist Version : 2.3.1 Upstream Author : Mario Stephan * URL : http://knowthelist.github.io/knowthelist * License :

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

Hello from the Montreal BSP! I tested the latest release of the upstream version (0.2.36) and it worked fine for me on the latest Thunderbird in testing. I migrated the nostalgy VCS from the Alioth archive to Salsa and updated it to the latest release:

Bug#887750: pam-python: diff for NMU version 1.0.6-1.1

Dear maintainer, I've prepared an NMU for pam-python (versioned as 1.0.6-1.1) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. -- diff -Nru pam-python-1.0.6/debian/changelog pam-python-1.0.6/debian/changelog --- pam-python-1.0.6/debian/changelog

Bug#919818: ruby-net-ssh breaks test-kitchen autopkgtest

Source: ruby-net-ssh, test-kitchen Control: found -1 ruby-net-ssh/1:5.1.0-1 Control: found -1 test-kitchen/1.23.2-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of ruby-net-ssh the autopkgtest of

Bug#919747: gnome-keysign: please package gnome-keysign 1.0.0

Hi Sascha, I was able to reproduce the error that you faced. The wormhole test didn't import the required key, so it failed if the testing private key wasn't already in the keyring. I wrote a fix [1] and very soon (probably even tomorrow) we should release a hotfix release 1.0.1 of

Bug#919817: mysql-5.7: Security fixes from the January 2019 CPU

Source: mysql-5.7 Version: 5.7.24-3 Severity: grave Tags: security upstream Justification: user security hole Hi Details at https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL Regards, Salvatore

Bug#802211: sulogin --force patch for d-i

Hello, FYI a completely untested patch for debian-installer component "user-setup" now exists that should be able to add the needed overrides to enable "sulogin --force" when installs are made with root account locked. (Note: This needs systemd >= v240.) (This doesn't take care of already

Bug#900918: debian-installer: Please make the generated images reproducible

Hi Chris, Chris Lamb (2019-01-19): > > * 0c19a29645a6a3136f3a51da5d5cf1cfcec5fdfb mentions file system > >ordering only, but that's just the sort part > > I've split this commit and it is much clearer now. Perfect, thanks. > > * 71391967763708055a65ed68999db8f4ea6fc6e6 sets “deb1”

  1   2   3   >