Bug#918319: myspell-et: please provide a symlink from /usr/share/hyphen/hyph_et.dic to hyph_et_EE.dic

Package: myspell-et Version: 1:20030606-29 Severity: wishlist as seen in #918318 and #918305, we're trying to get language-generic symlinks added to hyphenation packages for the purposes of getting pyphen packaged without shipping duplicate hyphenation dictionaries. To acheive this, myspell-et

Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

Package: apparmor-profiles Version: 2.13.1-3 Followup-For: Bug #881460 I've created a patch to resolve this bug. After applying the patch you should link/copy the profile to /etc/apparmor.d, enforce the profile again (the kernel ring buffer will show a STATUS message) and restart NetworkManager.

Bug#918326: python-dfwinreg and python3-dfwinreg depend on cruft package dtfabric

package: python3-dfwinreg version: 20180712-1 severity: serious It seems that with the most recent upload the build-dependencies were fixed from "dtfabric" to "python-dtfabric" and "python3-dtfabric", but the binary dependencies for python-dfwinreg and python3-dtwinreg are still on "dtfabric",

Bug#918327: ERROR #80 extracting when an ISO file contains non-english characters.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: wit Version: 3.01a-2 It looks like that "wit" expects that everything is in English, and crashed when dealing with files that contain non-english entries. ===BEGIN OUTPUT=== pthfdr:/r/m/s/W/q>wit copy --fst test.iso Popn\

Bug#918316: nocache: FTBFS in sid

On 2019-01-04 22:49 +, Santiago Vila wrote: > Package: src:nocache > Version: 1.1-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in sid but it failed: > > > [...] >

Bug#918318: libreoffice-dictionaries s

Package: src:libreoffice-dictionaries Version: 6.1.3-1 In the course of looking into pyphen packaging with Scott Kitterman, i noticed that it expects symlinks from hyphenation files like hyph_af.dic to hyph_af_ZA.dic. I filed https://bugs.debian.org/918305 against hyphen-en-us for that package.

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

On Fri, 04 Jan 2019 15:54:01 -0500 Sam Hartman wrote: > There are no thread support changes between 1.16.1 and 1.16.2. > There is one ccache related change which I'll include below related to > memory ccaches. > Do you know what type of credential cache is being used here?

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

> "Adrian" == Adrian Bunk writes: latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) >> automount starts but dies immediately after accessing a >> automounter point. >> >> Automount is configured to authenticate via GSSAPI using system >> keytab. After the GSSAPI

Bug#917989: Probably can close

I rebuilt my (lxc/sid) container from scratch, and copied in the original asterisk config. Asterisk now works perfectly. I did a filesystem-wide `diff` between the container that is broken and the one that works. There’s no smoking gun, unfortunately. There are definitely no library

Bug#918259: idle-python3.6 is not installable in unstable

On 04.01.19 20:58, Adrian Bunk wrote: > Package: idle-python3.6 > Severity: serious > > The following packages have unmet dependencies: > idle-python3.6 : Depends: python3.6-tk but it is not installable it doesn't make sense to file this issue, with the python3.6 removal pending.

Bug#918316: nocache: FTBFS in sid

tags 918316 + patch thanks The patch below works for me: --- a/debian/rules +++ b/debian/rules @@ -18,5 +18,5 @@ override_dh_auto_test: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) # -NOCACHE_NR_FADVISE=2 dh_auto_test -v ## #916415 - timeout 11 ./nocache apt show coreutils

Bug#918317: ITP: ruby-selenium-webdriver -- Browser automation framework and ecosystem

Package: wnpp Severity: wishlist Owner: Utkarsh Gupta * Package name : ruby-selenium-webdriver Version : 3.141.0 Upstream Author : Selenium HQ * URL : https://github.com/SeleniumHQ/selenium * License : Apache-2.0 Programming Lang : Ruby

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85, 13] cannot find symbol

On Wed, Jan 02, 2019 at 01:05:40PM +0100, Emmanuel Bourg wrote: > Le 30/12/2018 à 17:29, tony mancill a écrit : > > > Given that there aren't many (or any?) r-deps for the openhft libraries, > > I'm tempted to pull the versions in experimental into unstable so we > > have the libraries in buster.

Bug#918101: cfengine3: Please package new LTS release (3.12) before Buster freezes

On Thu, Jan 03, 2019 at 11:16:46AM +0100, Moritz Schlarb wrote: > Source: cfengine3 > Severity: wishlist > > Dear Maintainer, > > please consider packaging the latest LTS release (3.12.1) before the Buster > freezes begin. > > IMHO this makes sense if you look at the upstream support timeline

Bug#905877: regression in 1.4: upgrades random packages from testing to experimental (doesn't respect pinning?)

Package: unattended-upgrades Version: 1.9 On Sat, 11 Aug 2018 10:40:33 +0800 Paul Wise wrote: > Recently I have had unattended-upgrades upgrade random packages from > testing to experimental. I thought this had been fixed but recently I got git upgraded to experimental for some reason. I've

Bug#851189: keyboard-configuration: ALT+Cursor-Left switches consoles instead of working on app in focus

This started happening to me recently, not sure what change could be to blame but I found a lengthy thread on the ubuntu bug tracker that seems to confirm things. Copying the relevant post: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/comments/66 --- In my case, I traced

Bug#918323: unattended-upgrades: tried to upgrade package with conffile prompt

Package: unattended-upgrades Version: 1.9 Severity: serious unattended-upgrades tried to upgrade a package (lvm2) with a conffile prompt and failed because conffile prompts require user input. This meant that the upgrade of lvm2 failed and was the system was left in a partially broken state.

Bug#914236: ibus-chewing: Should we upgrade to v1.6.1?

Control: fixed -1 1.6.1-1 On Tue, Nov 20, 2018 at 03:14:58PM -0500, Boyuan Yang wrote: > Source: ibus-chewing > Version: 1.5.1-3 > Severity: normal > X-Debbugs-CC: m...@debian.org czc...@debian.org > > I noticed that ibus-chewing is tagging some new releases but didn't > explicitly list them on

Bug#918188: linux: FTBFS on arm64

On Fri, Jan 04, 2019 at 06:57:21AM +0100, Salvatore Bonaccorso wrote: > > LD vmlinux.o > > MODPOST vmlinux.o > > GEN .version > > CHK include/generated/compile.h > > UPD include/generated/compile.h > > CC init/version.o > > LD init/built-in.o > >

Bug#832355: ktap: module FTBFS for Linux 4.6: error: '__GFP_WAIT' undeclared

> But it looks like ktap is dead upstream now, so perhaps we should just > remove it from the archive instead? Sadly, but yes. So agree, should be just removed from the archive. Regards, Azat.

Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

Package: apparmor-profiles Version: 2.13.1-3 Followup-For: Bug #881460 I've created a patch to resolve this bug. After applying the patch you should link/copy the profile to /etc/apparmor.d, enforce the profile again (the kernel ring buffer will show a STATUS message) and restart NetworkManager.

Bug#894285: android-framework-23 FTBFS with openjdk-9

I had a go at this and it looks like the package simply is not ready for Java 9+. The unmappable character error is bogus. Rather issues like using an underscore character as a variable name (which is forbidden in Java 9) or naming a package java.lang ... are the root cause of the FTBFS. Markus

Bug#918305: hyphen-en-us: please provide fallback symlink from hyph_en.dic to hyph_en_US.dic

On Fri 2019-01-04 17:47:20 -0500, Daniel Kahn Gillmor wrote: > Control: tags 918305 + patch attached is a revised patch, which includes a en_Latn_US.dic symlink. the merge request has already been updated. regards, --dkg >From f8f0902e757b65b2bfcc6e2e3faaa844e9c00780 Mon Sep 17

Bug#918320: openvswitch-switch: ifupdown integration can't work (obsolete/buggy scripts)

Package: openvswitch-switch Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-10 Severity: important Tags: patch Dear Maintainer, Just configured openvswitch 2.10 on a newly-upgraded Buster machine (fresh install with Stretch/9.6, immediately dist-upgraded to Buster). When raising the interfaces

Bug#918246: dune-common: FTBFS for armhf on arm64, fails tests

On Fri, Jan 04, 2019 at 08:37:24PM +0200, Graham Inggs wrote: >This sounds like #918157. Nod. I'm seeing similar behaviour in a few more packages since tihs point, too. :-( -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait:

Bug#914607: closed by Hilko Bengen (Bug#914607: fixed in dfwinreg 20181214-2)

reassign 914607 dfwinreg found 914607 20180712-1 fixed 914607 20181214-2 thanks Britney gets confused when a bug is closed by a package other than the one it is filed against, so I am reassinging the bug to the package that closed it. On 01/01/19 23:09, Debian Bug Tracking System wrote: This

Bug#911399: Using --append-to-version without --make-binNMU may lead to broken packages

Hi Marga, On Fri, 19 Oct 2018 19:08:45 +0200 Marga Manterola wrote: > sbuild includes a handy --append-to-version parameter. This is what the > current manpage says: > >--append-to-version=string > This option is similar to --make-binNMU except that it > allows the user

Bug#918321: postbooks: Segfault after connecting to DB and OKing the too-new PGSQL warning

Package: postbooks Version: 4.11.3-1~bpo9+1 Severity: important Dear Maintainer, I just tried upgrading from the version of Postbooks in Stretch to the one in Stretch-Backports (4.11.3-1) and the backports version hits a segmentation fault after I log in to the database and click to proceed

Bug#918322: More info

Seems like I failed to add additional info: Picture of error: https://mega.nz/#!LehDlKbB!x_pFGX3wlq-Kgo6v5jUC6ydbqTQ4R43bft7mAC6j_ms This seems to be realted to initrd since when I ran update-initramfs on an older kernel that one started showing the same symptoms as the new one.

Bug#918325: RM: ktap -- RoQA; kernel module not usable; dead upstream

Package: ftp.debian.org Severity: normal As discussed in bug #832355, the ktap kernel module hasn't been buildable since Linux 4.6 due to kernel API changes. The project is dead upstream, so this is unlikely ever to be fixed. The maintainer has acknowledged this. Ben.

Bug#918328: aptitude: symbol lookup error: aptitude: undefined symbol: _ZN6Xapian4MSetC1EOS0_

Package: aptitude Version: 0.8.11-3 Severity: important Starting aptitude fails due to a missing Xapian symbol: $ aptitude aptitude: symbol lookup error: aptitude: undefined symbol: _ZN6Xapian4MSetC1EOS0_ This is probably a bug in the syms in the applicable xapian library package causing

Bug#917782: [gimp] Missing symbol

First of all sorry for the late answer, Google tought your answer were spam. :( Il 30/12/18 15:51, Simon McVittie ha scritto: > Control: tags -1 + moreinfo > > On Sun, 30 Dec 2018 at 11:45:12 +0100, Paolo Redaelli wrote: >> gimp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: >>

Bug#917850: Fwd: Server Error (500) on nm.d.o

Hi, El vie., 4 de ene. de 2019 a la(s) 17:17, Jonathan McDowell ( nood...@earth.li) escribió: > On Fri, Jan 04, 2019 at 09:56:10AM -0300, eamanu15 wrote: > > El lun., 31 de dic. de 2018 a la(s) 05:02, Jonathan McDowell ( > > nood...@earth.li) escribió: > > > On Sun, Dec 30, 2018 at 11:29:33PM

Bug#918324: Error: Permission denied (/home/user/Downloads/torrent file)

Package: transmission-daemon Version: 2.94-2 Severity: important Dear Maintainer, I have been using transmission-daemon for an extended time without any problems. Today, shortly after adding a torrent file I get an error stating permission denied to my downloads folder in my home directory. The

Bug#918329: apriltag ftbfs on release architectures

Package: src:apriltag Version: 0.10.0-1 Severity: serious Tags: sid buster apriltag ftbfs on release architectures, where it built before. Looks like the build system is exaggerating optimization flags, using -O4 nonsense.

Bug#918312: salt-{master,minion} fail to purge

Source: salt Version: 2018.3.3+dfsg1-1 Severity: serious Control: affects -1 salt-master salt-minion https://piuparts.debian.org/sid/source/s/salt.html Purging configuration files for salt-master (2018.3.3+dfsg1-1) ... rmdir: failed to remove '/var/lib/salt/pki': No such file or directory

Bug#918311: stormbaancoureur FTCBFS: uses the wrong compiler

Source: stormbaancoureur Version: 2.1.6-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap stormbaancoureur fails to cross build from source, because it does not pass cross tools to make. The easiest way of doing so - using dh_auto_build - makes stormbaancoureur cross buildable. Please

Bug#907624: What ffindex do we want to package

On Fri, Jan 04, 2019 at 07:17:24PM +0200, Michael Crusoe wrote: > I think 0.9.9.7+sog+git20160415.14274c9-1 is the source of the recent FTBFS > of hhsuite: https://bugs.debian.org/917495 as our packaged version is > missing the "ffsort_index" function. > > The hh-suite github repo contains a

Bug#918313: RM: bfgminer -- RoQA; RC-buggy, orphaned, not in stable

Package: ftp.debian.org Severity: normal Please remove bfgminer, it's RC-buggy, orphaned for almost a year without an adopter and already missed the previous stable release. Cheers, Moritz

Bug#908524: pipewire: Section should not be “libs”

Ben or Laurent, do one of you want to submit the follow-up bug report to fully change the section? Thanks, Jeremy Bicha

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

On Fri, Jan 04, 2019 at 08:13:53PM +0100, Alexander Meyer wrote: > Would this warrant to add "affects" tags for firefox and chromium to > this bug? Not sure about the Debian policy here. In this case, the no - see https://www.debian.org/Bugs/server-control#affects (since you're the only one to

Bug#826069: libghemical5v5: breaks color rendering and atom generation in ghemical

Hello: I think that I have found the origin of this bug. It is in the liboglappth2 package. This package has only one reverse dependency, that is ghemical. The package has remained the same (MD5 sum) since at least wheezy and something in the compilation dependencies has changed so that

Bug#918314: gmp: please add NEON-optimized variant for armhf

Source: gmp Version: 2:6.1.2+dfsg-1 Severity: wishlist Tags: patch Dear Maintainer, As --enable-fat works only on i386^1, on armhf neon-optimized code is never used, rendering gmp much slower than it can be. As a workaround, I suggest to compile and install separate neon-optimized library

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 21:49 schrieb Patrick Häcker: > I think the state to see the problem is quite reproducible: First install > systemd 239 and afterwards install systemd 240, i.e. I can recreate whatever > state you need. It is indeed reproducible easily, which is why I raised this upstream

Bug#918316: nocache: FTBFS in sid

Package: src:nocache Version: 1.1-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 dh_update_autotools_config -a

Bug#918315: hyphen should import upstream changes that are lingering in git

Package: src:hyphen Version: 2.8.8-5 Severity: wishlist the hyphen package hasn't had a release in several years. however, there are several useful-looking changes (including cleanup in the build scripts) in git (upstream uses https://github.com/hunspell/hyphen for hosting, afaict). It might be

Bug#918305: hyphen-en-us: please provide fallback symlink from hyph_en.dic to hyph_en_US.dic

Control: tags 918305 + patch I've just submitted https://salsa.debian.org/libreoffice-team/hyphen/merge_requests/1, which includes the fix attached here for #918305. Thanks for maintaining the hyphen package! --dkg From 62aeebfc6a75d6b11abbd319ff22f8dc17af78a3 Mon Sep 17 00:00:00 2001

Bug#918301: libgdk-pixbuf2.0-dev: pkg-config reports version 2.10.14 when installed version is 2.36.5-2+deb9u2

On Fri, Jan 04, 2019 at 04:49:30PM -0500, Jeremy Bicha wrote: > On Fri, Jan 4, 2019 at 4:33 PM wrote: > > pkg-config gtk+-3.0 --libs > > > > I get > > > > Package 'gdk-3.0' requires 'gdk-pixbuf-2.0 >= 2.30.0' but version of > > gdk-pixbuf-2.0 is 2.10.14 > > > > In fact version 2.36.5-2+deb9u2 is

Bug#917468: Please add 'stappers' to PAPT

On Sat, Jan 05, 2019 at 12:58:49AM +0300, Dmitry Shachnev wrote: > Hi Geert! Hi Dmitry, Hi Python list, Hi Bugreport 917468, > On Fri, Jan 04, 2019 at 10:16:20PM +0100, Geert Stappers wrote: > > Hello, > > > > Here Debian Developer 'stappers'. > > > > I'm working on

Bug#907624: What ffindex do we want to package

Heya, I have replied, at least I had typed it :o/ So, yes, I had chosen that version of ffsort_index to get hhsuite to compile. I have no idea if there are other reverse dependencies on ffindex, my priority is on hhsuite. Cheers, Steffen On 04.01.19 18:17, Michael Crusoe wrote: I think

Bug#918251: d-shlibs: devlibs error: There is no package matching [libsvm3-dev] and noone provides it

Hi Michael, On Fri, Jan 04, 2019 at 11:10:42AM -0800, Michael R. Crusoe wrote: > Package: d-shlibs > Version: 0.83 > Severity: normal > > Dear Maintainer, > > While fixing the missing linkage to libsvm in libpsortb I received the > following message: > > devlibs error: There is no package

Bug#918192: No email notification of autopkgtest failure

Package: tracker.debian.org,debci https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation says autopkgtest failures trigger an automatic email. When theano recently started failing [0] (#918090), no such email was received, either to its maintainer list [1] or to me

Bug#899595: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2019-01-04 at 08:39 +0900, Hideki Yamane wrote: > Hi, > > With Bugs search "Cleaner view", I've found those bugs are not closed > in unstable but are done in experimental. Hi, I am well aware of these, thanks. > Do you have a plan to

Bug#917323: transition: gdal

On 04/01/2019 10:57, Sebastiaan Couwenberg wrote: > On 1/4/19 10:36 AM, Emilio Pozuelo Monfort wrote: >> On 03/01/2019 17:44, Sebastiaan Couwenberg wrote: >>> On 1/3/19 4:39 PM, Sebastiaan Couwenberg wrote: On 1/3/19 4:23 PM, Emilio Pozuelo Monfort wrote: > On 02/01/2019 21:10, Sebastiaan

Bug#918211: ovito: depends on obsolete libnetcdf11

Package: ovito Version: 2.8.1+dfsg2-5 Severity: normal Hello, in the current testing suite, ovito 2.8.1+dfsg2-5 depends on libnetcdf11, which is an old library, and conflicts with other software, e.g. the dependences of the grace package. The unstable version of ovito, 2.9.0+dfsg1-5,

Bug#918212: python-pbcore: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-pbcore Version: 1.5.0+git20180606.43fcd9d+dfsg-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix

Bug#918213: python-skbio: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-skbio Version: 0.5.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your

Bug#918210: python-astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-astropy Version: 2.0.9-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: >> Package: linux-image-4.18.0-0.bpo.3-amd64 >> Version: 4.18.20-2~bpo9+1 >> Severity: normal >> Tags: upstream >> >> Dear Maintainer, >> >> I reported an upstream bug at >>

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > Once a version uploaded to sid, migrates to testing, it can be > prepared for stable-backports based on that. > > So what will need to happen here: upload of 4.19.13-2 to unstable > (actually possibly only >= 4.19.14-1 if we do not have pressure to > upload 4.19.13-2), then wait it

Bug#918220: securefs: Typo in debian/watch file

Source: securefs Version: 0.8.2+ds-3 Severity: minor Dear securefs maintainer, uscan reports error due to unrecognized option "repackasuffix=+ds". It is obviously a typo. Please consider fixing it in the next upload. Thanks! -- Regards, Boyuan Yang signature.asc Description: This is a

Bug#911979: fails on chown in autopkgtest-qemu backend

Hi, On Fri, 26 Oct 2018 15:33:32 -0400 Antoine Beaupre wrote: > I have tried to use the autopkgtest backend with the qemu server but it > completely failed to launch the build: > > [...] > > chown: invalid user: 'sbuild:sbuild' > E: Failed to set sbuild:sbuild ownership on /build > Failed to set

Bug#913003: already fixed

Control: fixed -1 2.0.6-1 Really add fixed version. signature.asc Description: OpenPGP digital signature

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

> > unfortunately davmail fails to build from source with > > libjackrabbit-java 2.18.0. Long deprecated methods have been removed. > > Your package build-depends on a very old version of jackrabbit (2.4.3). This is too much work and I'm afraid if I do not get help I'll miss the 2019-02-12 -

Bug#918225: pasystray: prefer GtkStatusIcon over Appindicator

Package: pasystray Version: 0.7.0-1 Severity: normal Tags: patch Current implementation of AppIndicator does not handle click events or modifiers. A middle click on the icon of pasystray is supposed to toggle mute, but this is not possible with the AppIndicator implementation. I filed a bug to

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

Hello Alex, Am 04.01.19 um 13:16 schrieb Alexandre Rossi: >>> unfortunately davmail fails to build from source with >>> libjackrabbit-java 2.18.0. Long deprecated methods have been removed. >>> Your package build-depends on a very old version of jackrabbit (2.4.3). > > This is too much work and

Bug#918226: gcc-snapshot.prerm yields error messages - incorrect paths?

Package: gcc-snapshot Version: 1:20190102-1 Severity: normal I can see the following error messages on upgrade or removal: find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory They come from

Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386

Hi, On Thu, Dec 20, 2018 at 6:46 AM Bastien ROUCARIES wrote: > > On Wed, Dec 19, 2018 at 12:09 PM Balint Reczey > wrote: > > > > Package: imagemagick > > Version: 8:6.9.10.14+dfsg-1 > > Severity: grave > > Control: forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31 > > Control:

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Fri, Jan 04, 2019 at 11:34:04AM +, Steve McIntyre wrote: >On Thu, Jan 03, 2019 at 07:43:03AM -0500, James McCoy wrote: >>On Wed, Jan 02, 2019 at 06:53:29PM +, Steve McIntyre wrote: >>> >>> amdahl is the arm64 porterbox, and I've just checked - it has armel >>> and armhf schroots

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

Hi Cyril, Can you please confirm that this error does not exist in the current version of prosody 0.11.1-1? Thanks, Victor Seva

Bug#918203: ccdproc: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: ccdproc Version: 1.3.0-5 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918200: astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: astropy Version: 3.0.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which block the gdal transition. Please fix the autopkgtest of your package.

Bug#918201: astropy-healpix: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: astropy-healpix Version: 0.4-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your

Bug#918215: skimage: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: skimage Version: 0.14.1-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918216: sunpy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: sunpy Version: 0.9.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918217: theano: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: theano Version: 1.0.2+dfsg-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Hello, > Can you post the output of > ls -ld /var/lib/systemd/timesync > ls -la /var/lib/private/systemd/ root@mmm /h/pat# ls -ld /var/lib/systemd/timesync lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../ private/systemd/timesync/ root@mmm /h/pat# ls -la

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi Ralf, On Fri, Jan 04, 2019 at 11:42:26AM +0100, Ralf Jung wrote: > Hi, > > > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > >> Package: linux-image-4.18.0-0.bpo.3-amd64 > >> Version: 4.18.20-2~bpo9+1 > >> Severity: normal > >> Tags: upstream > >> > >> Dear Maintainer, > >> > >>

Bug#911977: how do we correctly guess the VM name in autopkgtest?

Control: tag -1 + moreinfo Hi, On Fri, 26 Oct 2018 15:23:01 -0400 Antoine Beaupre wrote: > One of the nice things with the schroot backend is that it automatically > guesses which schroot to use based on internal sbuild logic. If I build a > stretch-security update, it will find my stretch

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 12:22 schrieb Michael Biebl: > For completeness sake, can you also post the output of > stat /var/lib/systemd/timesync/clock Make that stat /var/lib/private/systemd/timesync/clock (I missed that you already deleted /var/lib/systemd/timesync/) -- Why is it that all of the

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Thu, Jan 03, 2019 at 07:43:03AM -0500, James McCoy wrote: >On Wed, Jan 02, 2019 at 06:53:29PM +, Steve McIntyre wrote: >> >> amdahl is the arm64 porterbox, and I've just checked - it has armel >> and armhf schroots configured too. That should hopefully cover what >> you need - shout if you

Bug#918221: ftp.debian.org: Please add aceept-with-bug to DAK process-new

Package: ftp.debian.org Severity: wishlist Hi! I was just discussing a REJECT with a FTP team member and he told me that currently DAK-process-new does not has the option to ACCEPT a package and file a bug against it. There are certain cases in which accepting a package with a bug makes sense,

Bug#845223: 0ad: Crashes on startup with cache.cpp(43): Assertion failed: "cache.Validate()"

Hello Cacatoes, I just uploaded 0ad version 0.0.23.1 to unstable. Can you check your problem is still present in this version? if the problem is still present I suggest you to add a comment on your upstream bug http://trac.wildfiregames.com/ticket/4360 to let them know the problem is not yet

Bug#918138: qtox: Add AppArmor profile

Vincas Dargis 于2019年1月4日周五 上午2:36写道： > > Dear Maintainer, > > I'm happy to see that we now have qTox in Debian! Thanks to Maintainer! > > It would be even cooler to have it confined with AppArmor. qTox > maintains connections to various untrusted peers over the world, and so > it is important do

Bug#918223: ioctl[SIOCSIWENCODEEXT]: Invalid argument

Package: wpasupplicant Version: 2:2.7-2 Severity: minor wpa_supplicant connects fine, however I always get these two warnings, with various hardware, always the same. # wpa_supplicant -D wext,nl80211 -dd -i $i -c $co -B wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0

Bug#917850: Fwd: Server Error (500) on nm.d.o

Hi, El lun., 31 de dic. de 2018 a la(s) 05:02, Jonathan McDowell ( nood...@earth.li) escribió: > On Sun, Dec 30, 2018 at 11:29:33PM -0300, eamanu15 wrote: > > I joined to NM and in my personal web I have on *pending *the next line: > > "This is a new entry that requires confirmation before Jan.

Bug#918080: breeze-gtk: symlink /usr/share/themes/Breeze/{gtk-3.20,gtk-3.0}/

¡Hola Simon! El 2019-01-02 a las 21:25 -0600, Simon Quigley escribió: Package: breeze-gtk Severity: normal Version: 5.14.3-1 It was raised to my attention from LXQt users that the Breeze GTK theme cannot be used under LXQt as packaged. This is because the theme exists in

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

Hi Victor, Victor Seva (2019-01-04): > Can you please confirm that this error does not exist in the current > version of prosody 0.11.1-1? I'm running stretch so I can't really confirm. I could try the 0.11.1-1~bpo9+1 backport but before that I would need to check what specific modules were

Bug#898696: Similar problem with version 4:18.08.1

For me this behavior starts after upgrading to 4:18.08.1 Thanks for any help signature.asc Description: This is a digitally signed message part.

Bug#918202: caffe: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: caffe Version: 1.0.0+git20180821.99bd997-21.0.0+git20180821.99bd997-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition.

Bug#918222: calamares-settings-debian: Typo in package description

Package: calamares-settings-debian Severity: minor Dear Maintainer, I noticed a typo in the calamares-settings-debian package description. Indeed, "genereic" should be spelled "generic". Thanks a lot for your work on calamares-setting-debian! Thomas -- System Information: Debian Release: 9.6

Bug#918224: ITP: ruby-mini-mime: A lightweight mime type implementation

Package: wnpp Owner: Lucas Kanashiro Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org * Package name    : ruby-mini-mime   Version : 1.0.1   Upstream Author : Discourse Construction Kit, Inc. * URL : https://github.com/discourse/mini_mime * License :

Bug#864082: Next steps for a reproducible Fontconfig?

[Adding 864...@bugs.debian.org to CC] Dear fontconfig maintainers, I've just spent a coffee-or-two unpicking this to get the latest status and to load the history back into my brain. As a bit of background, I'm working on the Reproducible Builds effort and fontconfig — in its usual usage, or at

Bug#918204: dask: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: dask Version: 1.0.0+dfsg-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your

Bug#918205: hipspy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: hipspy Version: 0.2-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pandas Version: 0.23.3-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918207: pyregion: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pyregion Version: 2.0-6 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#876060: vit's error messages makes its output blow up.

Package: vit Version: 1.2-4 Followup-For: Bug #876060 Dear all, The bug is rooted in the upstream version, where it has been reported [1] and solved [since 2] from the pre-release v1.3.beta1 [3]. Best regards. ~~ 1. https://github.com/scottkosty/vit/issues/153 2.

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 11:48 schrieb Patrick Häcker: > Hello, > >> Can you post the output of >> ls -ld /var/lib/systemd/timesync >> ls -la /var/lib/private/systemd/ > > root@mmm /h/pat# ls -ld /var/lib/systemd/timesync > lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../ >

Bug#909378: Re: Bug#909378: sbuild: sbuild-createchroot must not consider “lost+found” for non empty directory

Hi Daniel, On Sun, 23 Sep 2018 13:21:38 +0200 Johannes Schauer wrote: > Quoting Daniel Dehennin (2018-09-22 19:52:55) > > I'm trying to setup an LVM schroot but I got the following error: > > > > #+begin_src > > /srv/chroot/sid-amd64-sbuild is not empty at /usr/bin/sbuild-createchroot > > line

  1   2   3   4   >