Bug#859660: [Debian-med-packaging] Bug#859660: artemis running issue

Hello, على الأربعاء 5 نيسـان 2017 ‫12:32، كتب Jerome: > When running artemis package, get this issue : > > $ art > bash: /usr/bin/art: cannot execute binary file: Exec format error Hmm, it works for me on jessie. I'll continue to try to reproduce the problem (maybe this weekend) and report

Bug#859421: python-tz orphaning

On 03.04.2017 16:29, Alastair McKinstry wrote: > Hi, > > Looking closer I realize you didn't mean _you_ were orphaning python-tz, > but looking for others to do so. > > I see its technically managed by the Zope team (but in practice not). > Looking at #858133 I see you've been working on it. >

Bug#857926: Building the fglrx kernel module untested beyond Linux 4.4

Package description for fglrx-driver version 1:15.12-2~bpo8+3 (current jessie-backports) says: "Building the kernel module has been tested up to Linux 4.4" Looks like we just did the testing - I confirm your results.

Processed (with 1 error): Re: Bug#859692: initramfs-tools: should depend on busybox

Processing control commands: > forcemerge 855094 -1 Bug #855094 [initramfs-tools-core] initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Unable to merge bugs because: package of #859692 is 'initramfs-tools' not 'initramfs-tools-core' Failed to

Bug#788585: dsh: overwrites host list with a symlink

Hi, On Sun, Nov 22, 2015 at 04:32:34PM +0100, Andreas Bombe wrote: > The symlink is not marked as a conffile because debhelper (specifically > dh_installdeb) does not mark symlinks to be installed in /etc as > conffiles. According to #421346 this is intentional as dpkg does not > work correctly

Bug#859656: Bug#858898: supermin: FTBFS on mips*

On Wed, 5 Apr 2017 16:48:09 +0200 Matthias Klose wrote: > Control: severity -1 important > > downgrading. There's a possible work around building with the standard C > library. > > Hi Hilko, Don't know if you have seen it, but the GCC maintainers cloned and reassigned this

Bug#795055: marked as done (libtirpc: Files licensed under BSD-4-clause)

Your message dated Thu, 6 Apr 2017 22:50:48 +0200 with message-id <20170406205045.ga26...@ugent.be> and subject line Re: Any progress or updates? has caused the Debian Bug report #795055, regarding libtirpc: Files licensed under BSD-4-clause to be marked as done. This means that you claim that

Bug#859752: marked as done (please re-enable arm64 arch)

Your message dated Thu, 06 Apr 2017 20:49:05 + with message-id and subject line Bug#859752: fixed in khmer 2.0+dfsg-10 has caused the Debian Bug report #859752, regarding please re-enable arm64 arch to be marked as done. This means that you claim that the

Processed: your mail

Processing commands for cont...@bugs.debian.org: > clone 851830 -1 Bug #851830 [src:khmer] khmer FTBFS on arm64: test failures Bug 851830 cloned as bug 859752 > retitle 851830 arm64 has flaky tests Bug #851830 [src:khmer] khmer FTBFS on arm64: test failures Changed Bug title to 'arm64 has flaky

Bug#859463: ruby-unf-ext FTBFS on ppc64el: unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to 'char' inside { } [-Wnarrowing]

On Tue, Apr 04, 2017 at 02:26:00PM +, Niels Thykier wrote: > On Mon, 03 Apr 2017 23:38:48 +0300 Adrian Bunk wrote: > > Source: ruby-unf-ext > > Version: 0.0.7.2-2 > > Severity: serious > > > > ruby-unf-ext FTBFS on ppc64el (originally reported by Frederic Bonnard): > > > >

Bug#851830: khmer FTBFS on arm64: test failures

Hi Maintainer You disabled arm64 for khmer and liboxli1 binary packages, but not for liboxli-dev. This prevented khmer from migrating [1] for the following reason: liboxli-dev/arm64 unsatisfiable Depends: liboxli1 (= 2.0+dfsg-9) However, I suspect that the build failure on arm64 was transient

Bug#857298: Salvaging python-cassandra for Stretch

On 04/06/2017 08:39 PM, Ondrej Novy wrote: > And auto -dbgsym doesn't support python-dbg. So it's wrong for Python C > modules. I guess I need to read more about this then. On 04/06/2017 06:31 PM, Dmitry Shachnev wrote: > In my opinion a better solution (for Stretch) would be just adding an >

Processed: khmer FTBFS on arm64: test failures

Processing commands for cont...@bugs.debian.org: > unarchive 851830 Bug #851830 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} [src:khmer] khmer FTBFS on arm64: test failures Unarchived Bug 851830 > reopen 851830 Bug #851830 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} [src:khmer]

Bug#839840: ghci segfaults on armel, related to doctest failure

Hi, Am Mittwoch, den 05.04.2017, 11:01 + schrieb Niels Thykier: > > We got a double RC buggy ghc on armel (this bug plus #851373, which also > affects armhf).  Unfortunately, I cannot see any progress on these bugs > (this one has been without updates since Oct 2016 and the other one > since

Bug#857298: Salvaging python-cassandra for Stretch

Hi, sry for second email. 2017-04-06 17:49 GMT+02:00 Thomas Goirand : > Attached is the debdiff. As you can see, I'm attempting to use the new > system that creates -dbgsym, and transitioning to it. cite from: https://release.debian.org/stretch/freeze_policy.html Some

Bug#858372: marked as done (mono-fpm-server: dependency on arch:any package libfpm-helper0 is not binNMU-safe)

Your message dated Thu, 06 Apr 2017 18:34:34 + with message-id and subject line Bug#858372: fixed in xsp 4.2-2.1 has caused the Debian Bug report #858372, regarding mono-fpm-server: dependency on arch:any package libfpm-helper0 is not binNMU-safe to be

Bug#857298: Salvaging python-cassandra for Stretch

Hi, 2017-04-06 17:49 GMT+02:00 Thomas Goirand : > I'll NMU. > because you are part of DPMT, why are you going to do NMU and not team upload? -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B

Bug#806879: marked as done (xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails))

Your message dated Thu, 06 Apr 2017 18:34:34 + with message-id and subject line Bug#806879: fixed in xsp 4.2-2.1 has caused the Debian Bug report #806879, regarding xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails) to be marked as done.

Bug#859725: x11-common: Each time my screen standby, system crash

Hi John Paul Adrian Glaubitz, > Nothing from your syslog excerpt indicates a problem with your X server. > Yep, but it was just a supposition.  > Is there a reason why you are using Debian pre-release kernel? The official > kernel for Debian Stretch and Sid is still based on the 4.9 series. >

Bug#857298: Salvaging python-cassandra for Stretch

On Thu, 06 Apr 2017 at 17:49:15 +0200, Thomas Goirand wrote: > Attached is the debdiff. As you can see, I'm attempting to use the new > system that creates -dbgsym, and transitioning to it. Sorry, I don't think this is a correct solution. For non-Python packages, foo-dbg traditionally contained

Bug#859725: x11-common: Each time my screen standby, system crash

Control: tags -1 moreinfo Hi Alexandre! > In my syslog i have this lines : Nothing from your syslog excerpt indicates a problem with your X server. > Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) Is there a reason why you are using Debian pre-release kernel? The official kernel for

Processed: Re: x11-common: Each time my screen standby, system crash

Processing control commands: > tags -1 moreinfo Bug #859725 [x11-common] x11-common: Each time my screen standby, system crash Added tag(s) moreinfo. -- 859725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#857298: Salvaging python-cassandra for Stretch

Hi Sandro and others, Sandro Tosi has left python-cassandra-driver in a bad state, which leads me to attempt to salvage it before it's too late. No harsh feeling, this happened to everyone of us, and we can all be busy. Though something must be done. Indeed, python-cassandra-driver suffers from

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

> This is a bug that will hit everyone who wants to use libntirpc > on mips or mipsel: And powerpc and powerpcspe :). And possibly more. I would suggest linking with --as-needed which resolves in a more generic way as compared to adding "-latomic" to a whitelist of architectures. Please see the

Processed: Re: libntirpc must be linked with libatomic on mips and mipsel

Processing control commands: > tags -1 patch Bug #859689 [libntirpc1.4] libntirpc must be linked with libatomic on mips and mipsel Added tag(s) patch. -- 859689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Control: tags -1 patch > I will report separate bug for nfs-ganesha, linking with latomic > library should solve this issue as well. Whoops, I overlooked your mail. Yes, this looks like the proper fix and I suggest using this solution for the aforementioned reasons. Thanks for the quick action!

Bug#859581: marked as done (quagga-core: fails to upgrade from 'jessie' - trying to overwrite /etc/pam.d/quagga)

Your message dated Thu, 06 Apr 2017 15:08:33 + with message-id and subject line Bug#859581: fixed in quagga 1.1.1-3 has caused the Debian Bug report #859581, regarding quagga-core: fails to upgrade from 'jessie' - trying to overwrite /etc/pam.d/quagga to

Bug#859725: Acknowledgement (x11-common: Each time my screen standby, system crash)

In my syslog i have this lines : Apr 6 13:42:58 debian gvfsd-network[3909]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: L'emplacement indiqué n'est pas monté Apr 6 14:07:50 debian kernel: [15855.529860] usb 1-2: new full-speed USB device number 5 using

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Hi, I have created and attached a patch that enables linking with latomic library as needed. When ntirpc package is recompiled with this patch, the above-mentioned problem is solved, but after that, new problem occurs on ganesha.nfsd linking: > /usr/bin/ld: libMainServices.a(client_mgr.c.o):

Bug#859725: x11-common: Each time my screen standby, system crash

Package: x11-common Version: 1:7.7+18 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Just when my screen go in standby (after 2minutes for examples) each time my system crash. If i want get back my computer i need to press power button to reboot. Thank you --

Bug#859710: marked as done (lhapdf FTBFS due to Build-Conflicts: automake)

Your message dated Thu, 06 Apr 2017 13:18:58 + with message-id and subject line Bug#859710: fixed in lhapdf 5.9.1-5 has caused the Debian Bug report #859710, regarding lhapdf FTBFS due to Build-Conflicts: automake to be marked as done. This means that you

Bug#858199: marked as done (broken /usr/include/libreoffice/sal/typesizes.h symlink on !amd64)

Your message dated Thu, 06 Apr 2017 12:21:28 + with message-id and subject line Bug#858199: fixed in libreoffice 1:5.3.2-1 has caused the Debian Bug report #858199, regarding broken /usr/include/libreoffice/sal/typesizes.h symlink on !amd64 to be marked as

Bug#859581: quagga-core: fails to upgrade from 'jessie' - trying to overwrite /etc/pam.d/quagga

On Wed, 05 Apr 2017 01:18:09 +0200 Andreas Beckmann wrote: > Package: quagga-core > Version: 1.1.1-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. > It

Bug#859712: vnstat sometimes FTBFS due to missing dependency

Source: vnstat Version: 1.15-1 Severity: serious Tags: patch vnstat sometimes FTBFS (originally reported by Frederic Bonnard): ... make[1]: Entering directory '/home/bunk/build2/vnstat-1.15' Making install in . make[2]: Entering directory '/home/bunk/build2/vnstat-1.15' make[3]: Entering

Bug#859710: lhapdf FTBFS due to Build-Conflicts: automake

Source: lhapdf Version: 5.9.1-4 Severity: serious Build-Depends: dh-autoreconf, automake1.11 Build-Conflicts: automake After #857556 got fixed this doesn't work anymore, the build dependencies cannot be fulfilled. Please replace the Build-Conflicts: automake with the following in debian/rules:

Bug#859709: x2goserver binary-all FTBFS: x2goserver-x2goagent.features: No such file or directory

Source: x2goserver Version: 4.0.1.20-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=x2goserver=all=4.0.1.20-2=1491419610=0 ... dh_install chmod 0755 debian/x2goserver-x2goagent/usr/share/x2go/x2gofeature.d/x2goserver-x2goagent.features chmod: cannot access

Bug#858553: [Lazarusdev] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

On Wed, 5 Apr 2017 21:13:59 +0200 Paul Gevers wrote: > Control: tags -1 pending Means? > Hi Mattias, > > On 05-04-17 11:51, Mattias Gaertner wrote: > > The Lazarus fixes branch now runs the build_html.sh without errors > > using fpdoc from FPC 3.0.0. > > svn path: > >

Processed: RC

Processing control commands: > severity -1 serious Bug #831007 [tar] tar 1.29 silently ignores previously-supported --exclude options Severity set to 'serious' from 'normal' -- 831007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831007 Debian Bug Tracking System Contact

Bug#749991: Wrong kernel in debian-installer package

Alexander Sosedkin (2017-04-06): > That's one way to think about it. Got it, keeping old modules is hard. > But I wasn't asking about keeping old modules, I see no point in this. > I was asking about generating and publishing a matching > dists/testing/main/installer-/current

Bug#859703: tendermint-go-merkle: FTBFS: go_level_db.go:7:2: cannot find package "github.com/syndtr/goleveldb/leveldb"

Source: tendermint-go-merkle Version: 0.1~20170131~0git7a86b44-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, tendermint-go-merkle fails to

Bug#859704: golang-github-lunny-nodb: FTBFS: batch.go:4:2: cannot find package "github.com/syndtr/goleveldb/leveldb"

Source: golang-github-lunny-nodb Version: 0.0~git20160621.0.fc1ef06-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, golang-github-lunny-nodb

Processed: libjs-jquery-hotkeys: Incompatible ABI change

Processing control commands: > severity -1 serious Bug #740893 [libjs-jquery-hotkeys] libjs-jquery-hotkeys: jquery.hotkeys changes break python-coverage html reports. Severity set to 'serious' from 'normal' -- 740893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740893 Debian Bug Tracking

Bug#749991: Wrong kernel in debian-installer package

On Thu, Apr 06, 2017 at 10:01:41AM +0700, Alexander Sosedkin wrote: > On Thu, 6 Apr 2017 00:05:17 +0200 > Cyril Brulebois wrote: > > > That's unfortunate, yes, but there's no easy way to keep old packages > > around in a given repository. > > That's one way to think about it.

Processed: reassign 859679 to heaptrack, forcibly merging 859512 859679

Processing commands for cont...@bugs.debian.org: > reassign 859679 heaptrack heaptrack/1.0.0-1 Bug #859679 [src:heaptrack] heaptrack: frontends miss dependencies on libheaptrack Bug reassigned from package 'src:heaptrack' to 'heaptrack'. No longer marked as found in versions heaptrack/1.0.0-1.

Bug#856720: diaspora{, -installer}: fails to install: Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp

On Fri, 31 Mar 2017 00:37:12 +0200 Andreas Beckmann wrote: > Followup-For: Bug #856720 > Control: found -1 0.6.3.0+debian4 > > Hi, > > and there we go again ... But the tracker shows it was tested fine in piuparts