Bug#856487: marked as done (libsbc1: compiling with gcc > 4.9 causes stack corruption)

Your message dated Mon, 08 May 2017 05:19:02 + with message-id and subject line Bug#856487: fixed in sbc 1.3-2 has caused the Debian Bug report #856487, regarding libsbc1: compiling with gcc > 4.9 causes stack corruption to be marked as done. This means

Bug#856487: libsbc1: compiling with gcc > 4.9 causes stack corruption

Hi, all. Thanks for your comments. >On Mon, Apr 17, 2017 at 05:02:32PM +0100, Paul Brook wrote: >> Package: libsbc1 >> Version: 1.3-1+b2 >> Followup-For: Bug #856487 >> >> Not a stack corruption. >> >> This is miscompilation of sbc_analyze_4b_8s_armv6. gcc appears to look >> into the asm

Bug#862027: marked as done (serf: FTBFS in stretch ("There were 14 failures"))

Your message dated Mon, 08 May 2017 03:39:17 + with message-id and subject line Bug#862027: fixed in serf 1.3.9-2 has caused the Debian Bug report #862027, regarding serf: FTBFS in stretch ("There were 14 failures") to be marked as done. This means that

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

Am 06.05.2017 um 10:43 schrieb Christoph Biedl: > Michael Biebl wrote... > >> Am 06.05.2017 um 00:00 schrieb Christoph Biedl: > >>> I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to >>> DELAYED/5 will follow in a few hours. Please feel free to tell me if I >>> should delay it

Bug#858250: Bug#861953: unblock: runc/0.1.1+dfsg1-3

[ CC: original Bug #858250 ] On Sun, 07 May 2017 21:02:00 + Niels Thykier wrote: > Roger Shimizu: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > Please unblock package runc > > > >

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

Hi, On 07/05/17 19:38, Adrian Bunk wrote: > Control: reassign -1 libghc-glut-dev 2.7.0.10-3 > Control: fixed -1 2.7.0.10-4 > Control: affects -1 src:raincat > > On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote: >> ... >> With haskell-glut 2.7.0.10-4 this should be fixed

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: Bug#861484: Bug#861484: julia: FTBFS on arm64

Julia builds successfully on a Raspberry Pi 3 running an image prepared by xylnao, dated 2016-04-14 [1] with kernel 4.5.0. It fails in the same way as on arm-arm-04 and arm-conova-01 on a Raspberry Pi 3 running an image prepared by Michael Stapelberg, dated 2017-03-22 [2] with kernel 4.9.18-1.

Processed: Re: Bug#861953: unblock: runc/0.1.1+dfsg1-3

Processing control commands: > tags -1 moreinfo Bug #861953 [release.debian.org] unblock: runc/0.1.1+dfsg1-3 Added tag(s) moreinfo. > forcemerge 858250 861966 Bug #858250 [runc] Fails to build for stretch, build-depends not strict enough Bug #858250 [runc] Fails to build for stretch,

Bug#839575: Tinyca is incompatible with openssl 1.1 and some 1.0.2 versions

Edit: The working openssl-version 1.02g-2 was not from jessie-backports. It was from an older stretch version. Now I tried the current version 1.0.2k-1~bpo8+1 from jessie-backports: Tinyca hangs with this version, too - when creating a CA. openssl version 1.0.1t-1+deb8u6 works as expected...

Bug#861112: xsane: always crashes on start

Hi, On Fri, May 05, 2017 at 08:04:26PM +0200, John Paul Adrian Glaubitz wrote: > On 05/05/2017 07:16 PM, Aaro Koskinen wrote: > > I think Jörg Frings-Fürst has analyzed and fixed this bug already - he > > provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline > > for testing

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

Of course, no problem, but it will have to wait a day or so. I didn't notice that there was a new version in /unstable or /experimental when I checked the other day so it is likely fairly recent. /Sebastian

Bug#861736:

activating the NXError reporting we got filenamenxs.h5 5 ERROR: cannot open file: filenamenxs.h5 0 and looking for this errormessage, we found it in the napi5.c file NXstatus NX5open(CONSTCHAR *filename, NXaccess am, NXhandle* pHandle) { hid_t

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

On Mon, 8 May 2017 03:51:45 +0800 Sebastian Rasmussen wrote: > Package: slim > Version: 1.3.6-5 > Severity: serious > > When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my > window manager appeared to suddenly "crash" and logged me out. However > I had > not

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

Package: slim Version: 1.3.6-5 Severity: serious When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my window manager appeared to suddenly "crash" and logged me out. However I had not changed anything related to that but I had recently upgraded slim so I investigated it a bit. I

Bug#861736:

Herethe code ofthismethod /**/ static NXstatus NXinternalopen(CONSTCHAR *userfilename, NXaccess am, pFileStack fileStack); /*--*/ NXstatus

Bug#861736:

in the napi.h files we saw this. define CONCAT(__a,__b) __a##__b/* token concatenation */ #ifdef __VMS #define MANGLE(__arg) __arg #else #define MANGLE(__arg) CONCAT(__arg,_) #endif #define NXopen MANGLE(nxiopen) /** * Open a NeXus

Bug#857573: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

On Fri, May 05, 2017 at 08:31:07AM +0200, Christoph Biedl babbled thus: > The issues here are pretty similar so I guess it's the same thing: Up to > and including jessie(sic!), networking wasn't brought down if there is > something mounted using AoE. This issue was definitely present in jessie -

Processed: limit source to debhelper, tagging 862049

Processing commands for cont...@bugs.debian.org: > limit source debhelper Limiting to bugs with field 'source' containing at least one of 'debhelper' Limit currently set to 'source':'debhelper' > tags 862049 + pending Bug #862049 [debhelper] dh_missing aborts with "dh_missing: unknown option;

Processed: Re: Bug#862008: crashes, segmentation fault

Processing commands for cont...@bugs.debian.org: > # Version was from at-spi2-core instead of pyatspi... > found 862008 2.20.3+dfsg-1 Bug #862008 [python-pyatspi] crashes, segmentation fault Marked as found in versions pyatspi/2.20.3+dfsg-1. > notfound 862008 2.22.0-5 Bug #862008 [python-pyatspi]

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

Control: reassign -1 libghc-glut-dev 2.7.0.10-3 Control: fixed -1 2.7.0.10-4 Control: affects -1 src:raincat On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote: >... > With haskell-glut 2.7.0.10-4 this should be fixed in unstable. I am reassigning it so that version

Processed: Re: Bug#861957 closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

Processing control commands: > reassign -1 libghc-glut-dev 2.7.0.10-3 Bug #861957 {Done: Joachim Breitner } [raincat] raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit) Bug reassigned from package 'raincat' to 'libghc-glut-dev'. No longer marked as found

Bug#851909: Problems disappear after downgrade

Dear Adrian On 05/07/2017 10:38 AM, Adrian Bunk wrote: > could you ask to get your fix included into the next jessie point release? > > "reportbug release.debian.org" -> jessie-pu The jessie-pu bug is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856240 I will ask my sponsor for

Bug#861979: marked as done (ufoai: crashes with signal 11 at mission start)

Your message dated Sun, 07 May 2017 18:18:41 + with message-id and subject line Bug#861979: fixed in ufoai 2.5-3 has caused the Debian Bug report #861979, regarding ufoai: crashes with signal 11 at mission start to be marked as done. This means that you

Bug#837510: marked as done (mozart: Please replace build dependency on sp with opensp)

Your message dated Sun, 07 May 2017 18:09:19 + with message-id and subject line Bug#862018: Removed package(s) from unstable has caused the Debian Bug report #837510, regarding mozart: Please replace build dependency on sp with opensp to be marked as done.

Bug#728441: marked as done (mozart: FTBFS on 5 architectures where it built in the past)

Your message dated Sun, 07 May 2017 18:09:19 + with message-id and subject line Bug#862018: Removed package(s) from unstable has caused the Debian Bug report #728441, regarding mozart: FTBFS on 5 architectures where it built in the past to be marked as

Bug#842208: marked as done (mozart-stdlib: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: mozart (>= 1.4.0))

Your message dated Sun, 07 May 2017 18:09:05 + with message-id and subject line Bug#862020: Removed package(s) from unstable has caused the Debian Bug report #842208, regarding mozart-stdlib: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies:

Bug#822002: marked as done (mozart: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Sun, 07 May 2017 18:09:19 + with message-id and subject line Bug#862018: Removed package(s) from unstable has caused the Debian Bug report #822002, regarding mozart: Build arch:all+arch:any but is missing build-{arch,indep} targets to

Bug#754020: marked as done (mozart: please switch to emacs24)

Your message dated Sun, 07 May 2017 18:09:19 + with message-id and subject line Bug#862018: Removed package(s) from unstable has caused the Debian Bug report #754020, regarding mozart: please switch to emacs24 to be marked as done. This means that you

Processed: Re: Bug#862008: crashes, segmentation fault

Processing commands for cont...@bugs.debian.org: > reassign 862008 python-pyatspi Bug #862008 [gnome-orca] crashes, segmentation fault Bug reassigned from package 'gnome-orca' to 'python-pyatspi'. No longer marked as found in versions gnome-orca/3.22.2-3. Ignoring request to alter fixed versions

Processed: Re: Bug#861979: ufoai: crashes with signal 11 at mission start

Processing control commands: > severity -1 serious Bug #861979 [ufoai] ufoai: crashes with signal 11 at mission start Severity set to 'serious' from 'normal' > tags -1 pending Bug #861979 [ufoai] ufoai: crashes with signal 11 at mission start Added tag(s) pending. -- 861979:

Bug#862008: crashes, segmentation fault

Ok, thanks for the info :-) _ Mika On 05/07/2017 05:49 PM, Joanmarie Diggs wrote: I am looking at the line of code which caused the crash and it is the same line of code as in the bug I reported. So you might have been doing something different, but it appears to be the same bug which

Bug#861826: marked as done (heaptrack FTBFS on mips: tst_trace (Failed))

Your message dated Sun, 07 May 2017 17:20:15 + with message-id and subject line Bug#861826: fixed in heaptrack 1.0.1~20170503.git4da8c45-2 has caused the Debian Bug report #861826, regarding heaptrack FTBFS on mips: tst_trace (Failed) to be marked as done.

Bug#861592: marked as done (node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC')

Your message dated Sun, 07 May 2017 16:04:10 + with message-id and subject line Bug#861592: fixed in node-dateformat 1.0.11-3 has caused the Debian Bug report #861592, regarding node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC'

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

Hi Ben, On Sun, May 07, 2017 at 03:44:14PM +0100, Ben Hutchings wrote: > > On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote: > > > Files: > > >  6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional > > > rar_5.4.0+dfsg.1-0.1.dsc > > >  d02b8742478d5e6428c12ee14b2a678d

Bug#862008: crashes, segmentation fault

I am looking at the line of code which caused the crash and it is the same line of code as in the bug I reported. So you might have been doing something different, but it appears to be the same bug which needs to be fixed in AT-SPI2. --joanie On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote: > >

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

On Sun, 2017-05-07 at 15:29 +0200, Ivo De Decker wrote: > Hi Ben, > > On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote: > > Files: > >  6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional > > rar_5.4.0+dfsg.1-0.1.dsc > >  d02b8742478d5e6428c12ee14b2a678d 531782

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

Processing control commands: > tags 860224 + patch Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;" Ignoring request to alter tags of bug #860224 to the same tags previously set > tags

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

Processing control commands: > tags 860224 + patch Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;" Added tag(s) patch. > tags 860224 + pending Bug #860224 [src:bind9] bind9:

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

Processing control commands: > tags 860224 + patch Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;" Ignoring request to alter tags of bug #860224 to the same tags previously set > tags

Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

Control: tags 860224 + patch Control: tags 860224 + pending Control: tags 860225 + pending Control: tags 860226 + patch Control: tags 860226 + pending Dear maintainer, I've prepared an NMU for bind9 (versioned as 1:9.10.3.dfsg.P4-12.3) and uploaded it to DELAYED/5. Please feel free to tell me if

Processed: gufw should depend on net-tools (crashes without it)

Processing commands for cont...@bugs.debian.org: > severity 855400 serious Bug #855400 [gufw] gufw should depend on net-tools (crashes without it) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 855400:

Bug#862027: serf: FTBFS in stretch ("There were 14 failures")

Package: src:serf Version: 1.3.9-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -B" but it failed: [...] debian/rules build-arch QUILT_PATCHES=debian/patches

Bug#861074: cryptsetup: cryptroot-hook doesn't honor initramfs-tools' (>= 0.129) logic for resume devices

Package: cryptsetup Version: 2:1.7.3-3 Followup-For: Bug #861074 Applying the fix from the cryptsetup git also eliminates a 30sec sleep during boot when the resume device is not found. +1 from me. -- Package-specific info: -- /proc/cmdline root=UUID=0556bb4e-09e2-48ee-ba4c-729e7a22eee3 ro quiet

Processed: tagging -ignore

Processing commands for cont...@bugs.debian.org: > # arch:all failure on i386 which builds fine on amd64 > tags 860687 stretch-ignore Bug #860687 [src:cross-toolchain-base] cross-toolchain-base: FTBFS on i386: configure: error: cannot compute suffix of object files: cannot compile Added tag(s)

Processed: Re: Bug#860650: zookeeper: FTBFS on i386: java.io.FileNotFoundException: /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No such file or directory)

Processing commands for cont...@bugs.debian.org: > # arch:all failure on i386, which builds fine on amd64 > tags 860650 stretch-ignore Bug #860650 [src:zookeeper] zookeeper: FTBFS on i386: java.io.FileNotFoundException:

Bug#862008: crashes, segmentation fault

When I read the discussion in Gnome bug page I see that some people have regular Orca crashes which happen often e.g when they close some application. Luckily I have not noticed problem like that. Orca crashes do not happen often or regularly on my computer, just sometimes. I also have not had

Bug#861957: marked as done (raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit))

Your message dated Sun, 07 May 2017 09:16:21 -0400 with message-id <1494162981.1219.1.ca...@debian.org> and subject line Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3 has caused the Debian Bug report #861957, regarding raincat: Raincat doesn't run: user

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

Hi Ben, On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote: > Files: > 6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional > rar_5.4.0+dfsg.1-0.1.dsc > d02b8742478d5e6428c12ee14b2a678d 531782 non-free/utils optional > rar_5.4.0+dfsg.1.orig-amd64.tar.gz >

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

Hi, On Sun, May 07, 2017 at 12:51:00PM +0200, Florian Vessaz wrote: > > If you can't reproduce, feel feel to close... > > Could you try a build on your system with the above Dockerfile? Please note that this message (and the one before) was sent to the wrong bug. It was meant for #861523 (which

Bug#862008: crashes, segmentation fault

If it is the same bug then I have to say I did not close any application when Orca crashed. I also did not do anythything particularly fast. I am not 100% sure what I Was doing but If I remember correctly I just switched between virtual Gnome desktops which did have some application windows

Bug#862008: crashes, segmentation fault

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074 --joanie On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote: > Package: gnome-orca > Version: 3.22.2-3 > Severity: grave > > Orca seems to sometime crash suddenly without any warning. This is not good > because blind users

Processed: Tinyca is incompatible with openssl 1.1

Processing commands for cont...@bugs.debian.org: > severity 839575 serious Bug #839575 [tinyca] hangs waiting for openssl Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 839575:

Bug#860225: bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

Same here. Multi/redundant DNS servers do not help, the culprit recursive query being sent multiple times by client as each DNS server falls in turn. And multi- firewall/IPS doesn't help catching the faulty packets :-( I may state the obvious, but only workaround so far is (already saved

Processed: Add tags and change severity

Processing commands for cont...@bugs.debian.org: > tags 861975 = moreinfo unreproducible Bug #861975 [audacity] audacity doesn't start Added tag(s) moreinfo and unreproducible. > severity 861975 important Bug #861975 [audacity] audacity doesn't start Severity set to 'important' from 'grave' >

Bug#861305: marked as done (python-cairo-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

Your message dated Sun, 07 May 2017 12:04:38 + with message-id and subject line Bug#861305: fixed in pycairo 1.8.8-2.2 has caused the Debian Bug report #861305, regarding python-cairo-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

Bug#862008: crashes, segmentation fault

Package: gnome-orca Version: 3.22.2-3 Severity: grave Orca seems to sometime crash suddenly without any warning. This is not good because blind users like me have to rely on screen reader working reliably. This, or similar, problem also existed before the latest update to Orca in Debian Stretch,

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

Christoph Biedl wrote... > Michael Biebl wrote... > > > Seems to be missing doc/ > > That's not obvious for me. Besides, I haven't uploaded yet due to a > technical problem on my side. Want to take over? Now uploaded to delayed+5 without further changes. Christoph, from the Zürich BSP

Bug#862001: in apt marked as pending

Control: tag 862001 pending Hello, Bug #862001 in apt reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=315d6aa (this message was generated automatically

Processed: Bug#862001 in apt marked as pending

Processing control commands: > tag 862001 pending Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found. Added tag(s) pending. -- 862001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862001 Debian Bug Tracking

Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

severity 861523 important thanks Chris Lamb wrote... > If you can't reproduce, feel feel to close... In spite of many efforts, nobody here at the Zürich BSP was able to reproduce the issue. Attempts included several different build systems (sbuild, pbuilder, docker, manual chroots etc.),

Processed: Re: Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

Processing commands for cont...@bugs.debian.org: > severity 861523 important Bug #861523 [src:bup] bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

Chris Lamb wrote: > Whilst I don't have a _minimal_ Dockerfile, looking at my setup I think > the "non-standard" things I do are: > > $ docker \ > --tty --user=$(id -u) \ > --group-add=$(id -g) \ > --volume=/tmp:/tmp \ > --volume=/home:/home > > .. particularly the last two. >

Processed: found 862001 in 1.4.1

Processing commands for cont...@bugs.debian.org: > found 862001 1.4.1 Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found. Ignoring request to alter found versions of bug #862001 to the same values previously set >

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

Control: found -1 1.4~beta1 On Sun, May 07, 2017 at 11:30:04AM +0200, Laurent Bigonville wrote: > Package: libapt-pkg5.0 > Version: 1.4.2 > Severity: serious > > Hi, > > When upgrading my system today I saw the following line in the output: > > Dépaquetage de libapt-pkg5.0:amd64 (1.4.2) sur

Processed: Re: Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

Processing control commands: > found -1 1.4~beta1 Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found. Marked as found in versions apt/1.4~beta1. -- 862001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862001

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

Le 07/05/17 à 12:16, Julian Andres Klode a écrit : Control: found -1 1.4~beta1 On Sun, May 07, 2017 at 11:30:04AM +0200, Laurent Bigonville wrote: Package: libapt-pkg5.0 Version: 1.4.2 Severity: serious Hi, When upgrading my system today I saw the following line in the output: Dépaquetage

Bug#861736:

Let's instrument the code print filename, mode, _ref(self.handle) status = nxlib.nxiopen_(filename,mode,_ref(self.handle)) print status $ python bug.py filenamenxs.h5 5 0

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

Hi Florian, > > If you can't reproduce, feel feel to close... I think you should just close the bug; my system is perhaps a little too strange, etc. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Processed: found 862001 in 1.4.1

Processing commands for cont...@bugs.debian.org: > found 862001 1.4.1 Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found. Marked as found in versions apt/1.4.1. > thanks Stopping processing here. Please contact me if

Processed: Re: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

Processing commands for cont...@bugs.debian.org: > retitle 857573 No longer umounts AoE/NBD-based file systems, causing data loss Bug #857573 [ifupdown] systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot Changed Bug title to 'No longer umounts AoE/NBD-based file systems,

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

Package: libapt-pkg5.0 Followup-For: Bug #862001 Hi, It seems that the fix is pretty trivial, see attached patch. Cheers, Laurent Bigonville -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,

Processed: tagging 862001

Processing commands for cont...@bugs.debian.org: > tags 862001 + patch Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

Package: libapt-pkg5.0 Version: 1.4.2 Severity: serious Hi, When upgrading my system today I saw the following line in the output: Dépaquetage de libapt-pkg5.0:amd64 (1.4.2) sur (1.4.1) ... Paramétrage de libapt-pkg5.0:amd64 (1.4.2) ... Failed to try-restart apt-daily-upgrade.timer: Unit

Bug#861736:

Hello here the napi code which cause some trouble. # Convert open mode from string to integer and check it is valid if mode in _nxopen_mode: mode = _nxopen_mode[mode] if mode not in _nxopen_mode.values(): raise ValueError, "Invalid open mode %s",str(mode)

Bug#861878: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

Hello, Lumin, on dim. 07 mai 2017 02:29:46 +, wrote: > I'm not sure whether this bug should be marked as serious. Since your test > cases are mixing the default cc (GCC-6) and clang-3.8 together. Well, there is no choice about this: not doing so leads to: cc-c -o test.o test.c nvcc -c

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: Bug#861484: julia: FTBFS on arm64

On 7 May 2017 at 10:26, Graham Inggs wrote: > Always succeeds on: > Linux 3.16.0-4-arm64 armhf (aarch64) I just noticed this line has armhf and I thought that was a bit odd. It seems arm-linaro-01 and arm-linaro-03 have machine architecture: armhf and host and build

Bug#851909: Problems disappear after downgrade

On Thu, Feb 02, 2017 at 10:06:42PM +0100, Roger Kalt wrote: > Yes, I can confirm I was able to reproduce and it was the patch which was not > correctly backported for deb8u1. > > Please test the UNRELEASED deb8u2 version available from here and give > feedback: >

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: julia: FTBFS on arm64

On 2 May 2017 at 13:10, Graham Inggs wrote: > I've been unable to reproduce this failure on asachi.debian.org. > It built without failure ten times yesterday, and again once today. I requested a give back by mailing debian-wb-team, but it hasn't happened yet. If it is

Bug#861693: swftools: CVE-2017-8400 CVE-2017-8401

Control: clone -1 -2 Control: retitle -1 swftools: CVE-2017-8400: out-of-bound write of heap data issue can occur in function png_load() Control: forwarded -1 https://github.com/matthiaskramm/swftools/issues/13 Control: severity -2 important Control: retitle -2 swftools: CVE-2017-8401:

Processed: Re: Bug#861693: swftools: CVE-2017-8400 CVE-2017-8401

Processing control commands: > clone -1 -2 Bug #861693 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401 Bug 861693 cloned as bug 861998 > retitle -1 swftools: CVE-2017-8400: out-of-bound write of heap data issue can > occur in function png_load() Bug #861693 [src:swftools] swftools:

Bug#861994: live-wrapper: Lacks dependency on python-pycurl

Package: live-wrapper Version: 0.6 Severity: serious lwr seems to require pycurl: $ lwr --help Traceback (most recent call last): File "/usr/bin/lwr", line 11, in load_entry_point('live-wrapper==0.6', 'console_scripts', 'lwr')() File

Processed: your mail

Processing commands for cont...@bugs.debian.org: > # totally broken on at least some hardware > severity 857591 serious Bug #857591 [libclc-amdgcn] libclc-amdgcn: apply upstream Mesa patch Severity set to 'serious' from 'important' > severity 861986 serious Bug #861986 [libclc-amdgcn] unsupported

Bug#861592: node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC'

Dear maintainer, Whether the issue arises or not depends on the timezone of the system. For instance the test suite fails in the following timezones: Etc/GMT, Etc/GMT+1 or Pacific/Tahiti (and ina lot of others too). I couldn't find a reliable way to set the timezone after node has started. I've