Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

Control: retitle -1 O: gyrus -- GNOME tool for Cyrus-IMAP servers administration Control: noowner -1 I am cancelling the Intent to Adopt because the adopter posted comment 25 on https://bugs.debian.org/886065 Without a maintainer or adopter, I intend to remove gyrus from Debian very soon as part

Bug#914059: git-remote-gcrypt: fails without mentioning that the fingerprint for the RSA key sent by the remote host has changed

Hi Sean & moire, moire: > I was no longer able to use an encrypted git repo after the fingerprint > for the RSA key sent by the remote host changed, To be 100% clear, the key moire is referring to is the *SSH* host key. I've personally suggested moire reports this with severity=important

Bug#881620: ITP: arm-trusted-firmware -- reference implementation of secure world software for ARMv8-A

I've got this packaged from an upstream git commit sufficient to replace atf-allwinner; it even reliably powers off on the pinebook! https://salsa.debian.org/debian/arm-trusted-firmware It's currently only building the sun50i_a64 target, since that's the one I've tested on pinebook and

Bug#914097: libomp5-7: not multiarch compatible

Hello, Le 19/11/2018 à 12:40, Giacomo Mulas a écrit : Package: libomp5-7 Severity: wishlist Dear Maintainer, I have a number of amd64 machines on which I have perfectly working multiarch installations, namely main distro amd64, run time libraries in i386 versions as well, a bunch of i386

Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

> Given that Xul is still supported in Thunderbird, let maybe drop the support > for > Firefox/Iceweasel (with a NOTE telling people how to migrate their existing > secrets) and upgrade to 0.13? While upgrading to 0.13 would fix one problem, it still wouldn't be able to reach Testing since it

Bug#914099: mailman3-full: mailman3-web-qcluster causes high database load

Package: mailman3-full Version: 3.2.0-2 Severity: important Dear Maintainer, I installed the mailman3-full package from the buster repository. The qcluster component generates a high database load with these queries: [...] 2018-11-17 16:33:15.417 UTC [8304] mailman3web@mailman3web LOG:

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

Graham, I don't know if you saw this bug and Yavor's response at https://bugs.debian.org/885742 Are you interested in talking to upstream about getting access to the gtk3 port of linsmith? linsmith is one of the last packages using libgnome in Debian and the Debian GNOME would really like to

Bug#911793: autopkgtest regression: Segmentation fault

Dear Mattia and Paul, On 16/11/2018 11:08, Mattia Rizzolo wrote: On Fri, Nov 16, 2018 at 07:28:21AM +0100, Emmanuel Promayon wrote: Thanks to the (great work) of Gert  on vtk7 and gdcm packages, version 7.1.1+dfsg1-9 of vtk7 and version 2.8.8-2 of gdcm are now both in testing. I sent a retry

Bug#914093: [mediathekview] Mediathelview hangs in startup

Am 19.11.18 um 12:55 schrieb Reinhard Karcher: > Am Montag, 19. November 2018, 12:51:03 CET schrieb Markus Koschany: >> Am 19.11.18 um 10:26 schrieb Reinhard Karcher: >>> Package: mediathekview >>> Version: 13.2.1-1 >>> Severity: grave >> >>> mediathekview hangs in startup: >> [...] >> >> Hi, >>

Bug#914093: [mediathekview] Mediathelview hangs in startup

Am Montag, 19. November 2018, 12:51:03 CET schrieb Markus Koschany: > Am 19.11.18 um 10:26 schrieb Reinhard Karcher: > > Package: mediathekview > > Version: 13.2.1-1 > > Severity: grave > > > mediathekview hangs in startup: > [...] > > Hi, > > thanks for the report. It appears libguava-java

Bug#914093: [mediathekview] Mediathelview hangs in startup

Am 19.11.18 um 10:26 schrieb Reinhard Karcher: > Package: mediathekview > Version: 13.2.1-1 > Severity: grave > > mediathekview hangs in startup: [...] Hi, thanks for the report. It appears libguava-java must be added as a runtime dependency too. This will be fixed shortly. Regards, Markus

Bug#914098: RM: plexus-utils -- ROM; Replaced by plexus-utils2

Package: ftp.debian.org Severity: normal Hi, Please remove the src:plexus-utils, it has been replaced by src:plexus-utils2. Starting with the version 3.1.0-1 libplexus-utils2-java now provides the same artifacts installed by libplexus-utils-java. The libplexus-utils2-java package now declares a

Bug#914097: libomp5-7: not multiarch compatible

Package: libomp5-7 Severity: wishlist Dear Maintainer, I have a number of amd64 machines on which I have perfectly working multiarch installations, namely main distro amd64, run time libraries in i386 versions as well, a bunch of i386 applications. The libomp5-7 packages, both amd64 and i386

Bug#913911: larry6: a strange menu entry for larry-doc

I've deleted installed packages of larry6 and larry6-svga-data builds successfully.

Bug#913948: segfault, apparently not always at the same location?

> Sounds a lot like #913573 . Could you try upgrading libasound2 and > libasound2-plugins? Seems so As a matter of fact, the new libasound2 & co. landed in testing as of today, so a simple update later, and sound is working again. Thanks! Clayton

Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

Hi Gaudenz On Mon, 19 Nov 2018 at 07:51 Gaudenz Steinlin wrote: [...] > I did the same and the build hanged as well. Retrying the hanging > call with all the -O2 arguments removed succeeds. So this seems to > be a bug in GCC with optimizations. I'm unsure on how to proceeed > from here. It's

Bug#913911: Re: Bug#913911: larry6: a strange menu entry for larry-doc

Control: tags -1 - pending On Mon, 19 Nov 2018 at 16:26:31 +0700, Roma Tentser wrote: > The package builds fine from both larry6 installers with "-p larry-doc" > specifier. But it can't be configured because it's depends on some > larry-series-data package. That's (now) a virtual package

Bug#914095: Could not load image 'gtimelog.png': Failed to open file ?/usr/share/gtimelog/gtimelog.png?: No such file or directory

Package: gtimelog Followup-For: Bug #914095 Hi again, I think there is a bigger issue with the installation of the icons. IMVHO, the gtimelog.png icon should be installed /usr/share/icons/hicolor/48x48/apps/ (in addition to /usr/share/gtimelog/) and gtimelog-large.png should be installed in

Bug#914095: Could not load image 'gtimelog.png': Failed to open file ?/usr/share/gtimelog/gtimelog.png?: No such file or directory

Package: gtimelog Version: 0.11.1-2 Severity: minor Hi, When starting gtimelog it complains about: Could not load image 'gtimelog.png': Failed to open file "/usr/share/gtimelog/gtimelog.png": No such file or directory The only downside I'm seeing is the missing icon in the about dialog. Kind

Bug#913093: ruby-i18n: CVE-2014-10077

On Mon, Nov 19, 2018 at 03:17:48AM -0500, Chris Lamb wrote: > Chris Lamb wrote: > > > Security team, I would be more than happy to prepare and upload a > > stable security upload of this package when addressing it in jessie > > LTS. Please let me know and I will come back with a debdiff. > > > >

Bug#911963: qemu build fails with proxy_cmd: parameter not set

Control: tag -1 pending Hello Antoine, Antoine Beaupre [2018-10-26 13:46 -0400]: > There seems to be some sort of interoperability issue between > autopkgtest and recent versions of APT which leads the build to > completely fail: > > $ sudo autopkgtest-build-qemu stretch

Bug#913837: transition: hdf5

On 19/11/2018 07:35, Sebastiaan Couwenberg wrote: > On 11/17/18 2:06 PM, Gilles Filippini wrote: >> Emilio Pozuelo Monfort a écrit le 17/11/2018 à 11:54 : >>> Control: tags -1 confirmed >>> >>> On 15/11/2018 21:37, Gilles Filippini wrote: Package: release.debian.org Severity: normal

Bug#913911: Re: Bug#913911: larry6: a strange menu entry for larry-doc

Everything works fine (thanks!) except larry-doc. The package builds fine from both larry6 installers with "-p larry-doc" specifier. But it can't be configured because it's depends on some larry-series-data package. Without the specifier larry-doc fails to build from vga installer. It

Bug#845715: Required targets must not write outside of the source package tree

Sean Whitton: > Hello, > > On Sun 11 Nov 2018 at 09:10PM +0100, Bill Allombert wrote: > >> Package support for TMPDIR can be introduced as a general requirement, >> outside of the build process. > > Okay. > >> Maybe the proposal could be rewritten in a way that does not need to >> cover the

Bug#914094: bugs.debian.org: Enabling Bluetooth distorts audio playback

Package: bugs.debian.org Severity: normal Dear Maintainer, Enabling after boot or booting PC with the Bluetooth dongle enabled (using kde plasma) makes the audio playback heavily (inaudible) distorted. The audio (that gets distorted) is comming from an external (usb) sound cart Workaround:

Bug#914085: soundscaperenderer: failed to cofigure cleanly

Control: severity -1 grave Hi, On 19/11/2018 08:03, Jean-Luc Coulon (f5ibh) wrote: > Package: soundscaperenderer > Version: 0.5.0~dfsg-1 > Severity: important > > Hi, > > While upgrading from 0.4.2~dfsg-7 to 0.5.0~dfsg-1, I get the following error: > > > Setting up soundscaperenderer

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

On 2018-11-19 09:58:04 +0100, Vincent Lefevre wrote: > On 2018-11-17 10:42:36 +0100, Marc Haber wrote: > > If this is a repeat occurrence, I don't have the slightest idea what > > might be happening here other than asking you to try running atop with > > debug info and trying to obtain a

Bug#800998: wagon: depends on obsolete libcommons-httpclient-java library

Control: fixed -1 3.0.0-1 Control: close -1 This issue has been fixed when the package was upgraded from the version 1.x to 3.x.

Bug#914093: [mediathekview] Mediathelview hangs in startup

Package: mediathekview Version: 13.2.1-1 Severity: grave mediathekview hangs in startup: . Portable Mode: false . Proxy Authentication: not configured WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by mediathek.Main (file:/usr/share/

Bug#914053: boost1.67: Please use binary-indep target to build doc package

Hi Giovanni! On 11/19/18 9:10 AM, Giovanni Mascellani wrote: > Thanks for the report of the patch, that is very helpful and I wanted to > do somthing like this (this problem is actually causing some > intermittent FTBFS on some arcitectures). I will review and upload ASAP. Sure :-). There are

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

On 2018-11-19 09:58:04 +0100, Vincent Lefevre wrote: > > I have not seen this on any of my systems. > > I can reproduce this problem on at least 2 machines. But not on a 3rd machine. The reason might be that it is older or that it doesn't use systemd. -- Vincent Lefèvre - Web:

Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

On Wed, 14 Nov 2018 at 13:45:59 +0100, Michael Biebl wrote: > Am 14.11.18 um 13:18 schrieb Michael Biebl: > > I.e. AC_PATH_PROG return the wrong path when built in a merged-usr > > system. > > I suspect that this particular problem is very widespread, so i was > > wondering if we couldn't just

Bug#902974: [#118118] Bug#902974: mirror.yellowfiber.net issues

Peter Palfrader Acknowledged {Please allow us time to complete this request regards Jeffrey Stewart Tier 1 NOC technician jstew...@atlanticmetro.net 212-792-9950 x 5 Atlantic Metro Communications 4 Century Drive, Parsippany NJ 07054 Cloud Hosting • Colocation • Network Connectivity • Managed

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

Control: severity -1 grave Raising to grave, because as soon as the system is slightly loaded (e.g. executing a "configure" script), atop fails. On 2018-11-17 10:42:36 +0100, Marc Haber wrote: > If this is a repeat occurrence, I don't have the slightest idea what > might be happening here other

Bug#914091: googletest: please make the build reproducible

Source: googletest Version: 1.8.1-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that googletest could not be

Bug#913645: Oldstable also affected

Hi, > this is not differing between the Debian releases(, unfortunately). > Debian hasn't touched any code here. > ... > First we/you need to check please if this behavior is also existing in > the upstream binaries. To check this you can simply download the > pre-compiled binary and start the

Bug#914092: monitoring-plugins: wrong apt path when built on a merged-/usr system and run on a non-merged-/usr system

Source: monitoring-plugins Version: 2.2-4 Severity: important User: m...@linux.it Usertags: usrmerge X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Steps to reproduce: * Have two chroots, containers or complete systems, one with merged /usr and one not * Build monitoring-plugins on

Bug#914090: k3d: build is not reproducible: *.module.proxy contain build system's kernel version

Source: k3d Version: 0.8.0.6-8 Severity: normal User: reproducible-b...@lists.alioth.debian.org Usertags: uname X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org k3d is not built reproducibly in the logs at . The

Bug#914074: work-around until package is updated

apt purge iptables && apt install iptables

Bug#914089: paricfg.h, pari.cfg: wrong gzip, zcat paths when built on a merged-/usr system and run on a non-merged-/usr system

Source: pari Version: 2.11.0-1 Severity: important User: m...@linux.it Usertags: usrmerge X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Steps to reproduce: * Have two chroots, containers or complete systems, one with merged /usr and one not * Build pari on the system with merged /usr

Bug#914088: sympow: wrong sed, rm paths when built on a merged-/usr system and run on a non-merged-/usr system

Source: sympow Version: 2.023.3-1 Severity: important User: m...@linux.it Usertags: usrmerge X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Steps to reproduce: * Have two chroots, containers or complete systems, one with merged /usr and one not * Build sympow on the system with merged

Bug#914087: mk_cmds: wrong SED path when built on a merged-/usr system and run on a non-merged-/usr system

Hi Simon et al., > Actual result: > > * /usr/bin/mk_cmds contains SED="/usr/bin/sed" FYI I'm tagging some related issues/differences here: https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html Regards, -- ,''`. : :' : Chris

Bug#844762: amarok: Same crash occures since update to version 2.9.0 (Qt: 4.8.7; KDE: 4.14.38)

Package: amarok Version: 2.9.0-1+b1 Followup-For: Bug #844762 Dear Maintainer, I just upgraded my system and therefore Amarok to version 2.9.0 (Qt: 4.8.7; KDE: 4.14.38). Before the upgrade it was working well. Now I get the same error (Amarok crashes at startup). $ amarok QDBusConnection:

Bug#914087: mk_cmds: wrong SED path when built on a merged-/usr system and run on a non-merged-/usr system

Source: e2fsprogs Version: 1.44.4-2 Severity: normal User: m...@linux.it Usertags: usrmerge X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Steps to reproduce: * Have two chroots, containers or complete systems, one with merged /usr and one not * Build e2fsprogs on the system with

Bug#914086: /usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr system and run on a non-merged-/usr system

Source: wxwidgets3.0 Version: 3.0.4+dfsg-4 Severity: normal User: m...@linux.it Usertags: usrmerge X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Steps to reproduce: * Have two chroots, containers or complete systems, one with merged /usr and one not * Build wxwidgets3.0 on the system

Bug#913093: ruby-i18n: CVE-2014-10077

Chris Lamb wrote: > Security team, I would be more than happy to prepare and upload a > stable security upload of this package when addressing it in jessie > LTS. Please let me know and I will come back with a debdiff. > > Ruby team, I could easily upload to sid at the same time. Let me > know

Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack

Chris Lamb wrote: > Security team, like ruby-i18n, I would be more than happy to prepare > and upload a stable security upload of this package when addressing > it in jessie LTS. […] > Ruby team, again, I could easily upload to sid at the same time. Let > me know here too. Gentle ping on the

Bug#899454: boost-defaults: Invalid maintainer address pkg-boost-de...@lists.alioth.debian.org

Hi, Il 18/11/18 02:20, Dimitri John Ledkov ha scritto: > Hmmm so i'm not sure what to do about this. > > Is it allowed to use Debian Boost Team > as the maintainer field? Yes, we had already discussed this and it is ok. We do the same for boost1.62 and boost1.67. I'd say the bug is already

Bug#914053: boost1.67: Please use binary-indep target to build doc package

Hi, Il 18/11/18 21:47, John Paul Adrian Glaubitz ha scritto: > Currently, the debian/rules file of the boost1.67 package contains the > following code in the override_dh_auto_build target: > > ifneq (,$(filter nodoc,$(DEB_BUILD_OPTIONS))) > mkdir -p doc > else > $(JAM_DOC)

Bug#914085: soundscaperenderer: failed to cofigure cleanly

Package: soundscaperenderer Version: 0.5.0~dfsg-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While upgrading from 0.4.2~dfsg-7 to 0.5.0~dfsg-1, I get the following error: Setting up soundscaperenderer (0.5.0~dfsg-1) ... update-alternatives: error: alternative path

Bug#914084: nmu: why3_1.1.0-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu why3_1.1.0-1 . ANY . unstable . -m "rebuild against menhir 20181113" -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

<    1   2   3