Bug#816313: marked as done (dash: executes binary data as a shell script in case of ENOEXEC (Exec format error))

Your message dated Thu, 26 Jan 2017 07:18:55 + with message-id and subject line Bug#816313: fixed in dash 0.5.8-2.4 has caused the Debian Bug report #816313, regarding dash: executes binary data as a shell script in case of ENOEXEC (Exec format error) to

Bug#851834: [Pkg-pascal-devel] Bug#851834: mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out of range

The patch below adds line number information to the generated parconvert.s: --- a/dcm2nii/dcm2nii.lpi +++ b/dcm2nii/dcm2nii.lpi @@ -482,6 +482,7 @@ + Because of the additional lines, this changes the assembler messages to: (9009) Assembling

Bug#851834: [Pkg-pascal-devel] Bug#851834: mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out of range

I see the same failure with 0.20140804.1~dfsg.1-1. According to reproducible builds [1], the last successful build on armhf was on 2016-02-19. Can we request removal of the armhf binary, so this can at least migrate before the final freeze? I have some ideas on how to debug this further. [1]

Processed: severity 757343

Processing commands for cont...@bugs.debian.org: > severity 757343 normal Bug #757343 [src:gamera] gamera: inappropriate use of general exceptions Severity set to 'normal' from 'wishlist' > severity 812852 important Bug #812852 [src:libvigraimpex] libvigraimpex: fail of test_multiarray_chunked

Bug#777525: marked as done (rope: CVE-2014-3539)

Your message dated Thu, 26 Jan 2017 05:34:00 + with message-id and subject line Bug#777525: fixed in rope 0.10.3-1 has caused the Debian Bug report #777525, regarding rope: CVE-2014-3539 to be marked as done. This means that you claim that the problem has

Processed: severity of 852654 is serious

Processing commands for cont...@bugs.debian.org: > severity 852654 serious Bug #852654 [src:pbcopper] src:pbcopper: no point to releasing it without `unanimity` Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 852654:

Bug#850951: [pkg-go] Bug#850951: CVE-2016-9962

On 11 January 2017 at 07:21, Moritz Muehlenhoff wrote: > Please see: > https://bugzilla.suse.com/show_bug.cgi?id=1012568 > https://github.com/docker/docker/compare/v1.12.5...v1.12.6 > https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5 I've

Bug#852653: Grub install failed on encrypted LVM disk

Dear Maintainer: Problem solved. Mark "BOOT" flag in the encrypted disk. Then grub install completed successfully. Suggest to verify BOOT flag has been marked to allow proceeding to next installation stage. Regards, Alan

Bug#852653: Grub install failed on encrypted LVM disk

Package: installation-reports Version: jessie rc1 Severity: critical Justification: failed to install grub Dear Maintainer, * What led up to the situation? Failed installation of grub under KVM system with encrypted LVM disk. * What exactly did you do (or not do) that was

Bug#852631: marked as done (bzr-git: FTBFS: NotImplementedError:

Your message dated Thu, 26 Jan 2017 03:04:02 + with message-id and subject line Bug#852631: fixed in bzr-git 0.6.13-2 has caused the Debian Bug report #852631, regarding bzr-git: FTBFS: NotImplementedError:

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

On Wed, Jan 25, 2017 at 10:48:43PM +0100, Mathieu Parent wrote: > Will look at a fix inside lua-socket (preserving both > compatibilities), but please relax your rules to help find a fix for > all cases. I just opened a pull request[1] with upstream that adds backwards compatibility wrappers. It

Bug#852625: marked as done (unrar-free is useless and should be removed)

Your message dated Thu, 26 Jan 2017 01:53:23 +0200 with message-id <20170125235323.odiyuegn5tizdsjx@localhost> and subject line Re: Bug#852625: unrar-free is useless and should be removed has caused the Debian Bug report #852625, regarding unrar-free is useless and should be removed to be marked

Bug#852543: marked as done (Apache doesn't start anymore with sysvinit)

Your message dated Wed, 25 Jan 2017 23:49:41 + with message-id and subject line Bug#852543: fixed in apache2 2.4.25-3 has caused the Debian Bug report #852543, regarding Apache doesn't start anymore with sysvinit to be marked as done. This means that you

Bug#794466: VIrtualBox future in Debian

Sorry for the long post, but it does give a walkthrough of how this is working now in Stretch… I installed Debian Stretch today using the January 23 weekly netinstall image. I installed to a VirtualBox guest (the host is Ubuntu 17.04 Alpha). The install went well except for two issues. 1. I

Bug#852645: dafny: FTBFS

Package: src:dafny Version: 1.9.7-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --with cli

Bug#852643: libbfio FTBFS on armel/armhf/mips*: bfio_test_handle.c:803 result (1) != -1

Source: libbfio Version: 20170123-1 Severity: serious https://buildd.debian.org/status/package.php?p=libbfio ... make check-TESTS make[3]: Entering directory '/«PKGBUILDDIR»/tests' make[4]: Entering directory '/«PKGBUILDDIR»/tests' FAIL: test_library.sh PASS: test_write_functions.sh

Bug#850983: marked as done (gvpe: FTBFS: configure: error: OpenSSL depends on libz.)

Your message dated Wed, 25 Jan 2017 22:49:05 + with message-id and subject line Bug#850983: fixed in gvpe 2.25-3.1 has caused the Debian Bug report #850983, regarding gvpe: FTBFS: configure: error: OpenSSL depends on libz. to be marked as done. This means

Bug#839300: marked as done (gnustep-make: FTBFS: dh_install: missing files, aborting)

Your message dated Wed, 25 Jan 2017 22:40:02 + with message-id and subject line Bug#838278: fixed in gnustep-make 2.6.8-2.1 has caused the Debian Bug report #838278, regarding gnustep-make: FTBFS: dh_install: missing files, aborting to be marked as done.

Bug#838278: marked as done (gnustep-make: FTBFS in testing (@setcontentsaftertitlepage no longer works))

Your message dated Wed, 25 Jan 2017 22:40:02 + with message-id and subject line Bug#838278: fixed in gnustep-make 2.6.8-2.1 has caused the Debian Bug report #838278, regarding gnustep-make: FTBFS in testing (@setcontentsaftertitlepage no longer works) to

Bug#834063: marked as done (gosa: GOsa setup complains about missing php mysql module even if php-mysql is installed)

Your message dated Wed, 25 Jan 2017 21:49:03 + with message-id and subject line Bug#834063: fixed in gosa 2.7.4+reloaded2-13 has caused the Debian Bug report #834063, regarding gosa: GOsa setup complains about missing php mysql module even if php-mysql is

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

2017-01-25 22:15 GMT+01:00 Michael Meskes : > Control: reassign -1 lua-socket > > I don't think this is the way to go. There is no grave bug in prosody-modules, > it's lua-socket that changed its API during freeze. The way I understand our > freeze policy this is a no-go, but

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

Hi Felipe, On Wed, Jan 25, 2017 at 03:00:29PM -0300, Felipe Sateler wrote: > > It is plenty usable, just not if you are using systemd. Yes, I am aware > > policy at this point requires systemd support. > > OK, sorry. The impression I had from your earlier message is that it > didn't work[1].

Processed: Bug#834063 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 834063 pending Bug #834063 [gosa] gosa: GOsa setup complains about missing php mysql module even if php-mysql is installed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 834063:

Bug#834063: marked as pending

tag 834063 pending thanks Hello, Bug #834063 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=debian-edu/pkg-team/gosa.git;a=commitdiff;h=8a46523 --- commit

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

Control: reassign -1 lua-socket I don't think this is the way to go. There is no grave bug in prosody-modules, it's lua-socket that changed its API during freeze. The way I understand our freeze policy this is a no-go, but feel free to check with the release team. Michael -- Michael Meskes

Processed: Re: Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

Processing control commands: > reassign -1 lua-socket Bug #852250 [prosody-modules] [lua-socket] luasocket was not compiled with UNIX sockets support Bug reassigned from package 'prosody-modules' to 'lua-socket'. Ignoring request to alter found versions of bug #852250 to the same values

Bug#852261: profanity FTBFS on armel/armhf/mips/mipsel: prof_whole_occurrences_tests failed

I created an upstream bug report at: https://github.com/boothj5/profanity/issues/901 Greetings, Jack signature.asc Description: OpenPGP digital signature

Bug#852625: unrar-free is useless and should be removed

Let me say more clear. unrar-free currently isn't useless. Many GUI programs are still calling /usr/bin/unrar And unrar-free converts those calls to unar. Unless all the programs in main callls unar or unar provides a compatible /usr/bin/unrar, unrar-free are still useful. Please correct me

Bug#852530: marked as done (terminix: Terminix fails to start)

Your message dated Wed, 25 Jan 2017 21:00:24 + with message-id and subject line Bug#852530: fixed in terminix 1.4.2-3 has caused the Debian Bug report #852530, regarding terminix: Terminix fails to start to be marked as done. This means that you claim

Bug#852216: marked as done (kodi FTBFS with libcec 4)

Your message dated Wed, 25 Jan 2017 20:56:45 + with message-id and subject line Bug#852216: fixed in kodi 2:17.0~rc3+dfsg1-2 has caused the Debian Bug report #852216, regarding kodi FTBFS with libcec 4 to be marked as done. This means that you claim that

Bug#852625: unrar-free is useless and should be removed

Exactly, But the problem is how many other programs depends on unrar's command line. unar doesn't support unrar and that means other programs has to re-program. Take an example, Package "unp" doesn't call unar but call unrar. Yours, Paul On Thu, Jan 26, 2017 at 2:00 AM, Adrian Bunk

Bug#852216: marked as pending

tag 852216 pending thanks Hello, Bug #852216 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-multimedia/kodi.git;a=commitdiff;h=b1c2bed --- commit

Processed: Bug#852216 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 852216 pending Bug #852216 [src:kodi] kodi FTBFS with libcec 4 Ignoring request to alter tags of bug #852216 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 852216:

Bug#852608: closing 852608

close 852608 2.1.18-2 thanks

Processed: closing 852608

Processing commands for cont...@bugs.debian.org: > close 852608 2.1.18-2 Bug #852608 [gnupg-agent] gnupg-agent: double-free in gpg-agent during heavily concurrent use Marked as fixed in versions gnupg2/2.1.18-2; no longer marked as fixed in versions 2.1.18-2. Bug #852608 [gnupg-agent]

Processed: Bug#852530 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 852530 pending Bug #852530 [terminix] terminix: Terminix fails to start Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 852530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852530

Bug#852530: marked as pending

tag 852530 pending thanks Hello, Bug #852530 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-gnome/terminix.git;a=commitdiff;h=f799eaf --- commit

Bug#852631: bzr-git: FTBFS: NotImplementedError:

Source: bzr-git Version: 0.6.13-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, bzr-git fails to build from source in unstable/amd64: […]

Bug#852543: apache and sysvinit

apache2ctl should check for "/run/systemd/system" not for "/run/systemd"

Processed: severity of 852543 is grave

Processing commands for cont...@bugs.debian.org: > severity 852543 grave Bug #852543 [apache2] Apache doesn't start anymore with sysvinit Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 852543:

Bug#833327: marked as done (xmldiff: maintainer address bounces)

Your message dated Wed, 25 Jan 2017 19:51:30 + with message-id and subject line Bug#833327: fixed in xmldiff 0.6.10-3 has caused the Debian Bug report #833327, regarding xmldiff: maintainer address bounces to be marked as done. This means that you claim

Bug#833331: marked as done (Updating the xmldiff Uploaders list)

Your message dated Wed, 25 Jan 2017 19:51:30 + with message-id and subject line Bug#833327: fixed in xmldiff 0.6.10-3 has caused the Debian Bug report #833327, regarding Updating the xmldiff Uploaders list to be marked as done. This means that you claim

Bug#848748: marked as done (blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Wed, 25 Jan 2017 19:48:36 + with message-id and subject line Bug#848748: fixed in blockdiag 1.5.3+dfsg-1.1 has caused the Debian Bug report #848748, regarding blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of

Processed: Re: Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

Processing control commands: > reassign -1 prosody-modules Bug #852250 [lua-socket] [lua-socket] luasocket was not compiled with UNIX sockets support Bug reassigned from package 'lua-socket' to 'prosody-modules'. No longer marked as found in versions luasocket/3.0~rc1+git+ac3201d-2. Ignoring

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

Control: reassign -1 prosody-modules Control: tag -1 + patch upstream confirmed On Wed, 25 Jan 2017 13:04:02 +0100 Enrico Tassi wrote: > On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote: > > > Hopefully somebody is prepared to fix all rdepends. > > > >

Bug#844886: libalog is waiting for binutils testing migration

libalog is waiting for gcc-6 testing migration, which itself depends on binutils testing migration. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

On Wed, 25 Jan 2017 13:37:41 +0100 Enrico Tassi wrote: > On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote: > > > Hopefully somebody is prepared to fix all rdepends. > > > > Or better reverts the API change. > > I gave a quick look at the problem. > > I

Processed: Re: Bug#852627: lcms2: CVE-2016-10165: heap OOB read parsing crafted ICC profile

Processing control commands: > severity -1 grave Bug #852627 [src:lcms2] lcms2: CVE-2016-10165: heap OOB read parsing crafted ICC profile Severity set to 'grave' from 'important' -- 852627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852627 Debian Bug Tracking System Contact

Bug#844918: libncursesada is waiting for binutils testing migration

libncursesada is waiting for gcc-6 testing migration, which itself depends on binutils testing migration. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Bug#851162: marked as done (FTBFS: issues with longdouble precision on ppc)

Your message dated Wed, 25 Jan 2017 18:18:45 + with message-id and subject line Bug#851162: fixed in h5py 2.7.0~rc3-1 has caused the Debian Bug report #851162, regarding FTBFS: issues with longdouble precision on ppc to be marked as done. This means that

Processed: (no subject)

Processing commands for cont...@bugs.debian.org: > tags 848742 + jessie Bug #848742 {Done: Mike Gabriel } [src:libmateweather] libmateweather: FTBFS: configure: error: Can't find zoneinfo directory. Use --with-zoneinfo-dir Added tag(s) jessie. > End of message, stopping

Processed: Works for me and no feedback from the submitter

Processing commands for cont...@bugs.debian.org: > severity 802954 important Bug #802954 [gnu-smalltalk-el] gnu-smalltalk-el: Prevents upgrade of emacs24 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 802954:

Bug#852622: marked as done (xcffib FTBFS in stretch)

Your message dated Wed, 25 Jan 2017 20:01:45 +0200 with message-id <20170125180145.7mxiaz4443tokhyc@localhost> and subject line This is already fixed in unstable has caused the Debian Bug report #852622, regarding xcffib FTBFS in stretch to be marked as done. This means that you claim that the

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

On 25 January 2017 at 14:36, Jacob Luna Lundberg wrote: > > Hi Felipe, > > On Wed, Jan 25, 2017 at 11:50:33AM -0300, Felipe Sateler wrote: >> Apparently, fcow-utils as currently packaged is not usable in >> debian. > > It is plenty usable, just not if you are using systemd.

Bug#852625: unrar-free is useless and should be removed

Package: unrar-free Version: 1:0.0.1+cvs20140707-1 Severity: serious Tags: stretch sid unrar-free itself supports only ancient versions of the RAR format, and for any archives created with WinRAR during the past 15 years all it does is to call unar.

Bug#852622: xcffib FTBFS in stretch

Source: xcffib Version: 0.3.6-1 Severity: serious ... Building xcffib-0.3.6... Preprocessing library xcffib-0.3.6... [1 of 2] Compiling Data.XCB.Python.PyHelpers ( generator/Data/XCB/Python/PyHelpers.hs, dist/build/Data/XCB/Python/PyHelpers.o ) generator/Data/XCB/Python/PyHelpers.hs:90:25:

Bug#852452: marked as done (obmenu: Uninstallable due to dependency on "2.7" (should be "python2.7"))

Your message dated Wed, 25 Jan 2017 17:49:48 + with message-id and subject line Bug#852452: fixed in obmenu 1.0-4 has caused the Debian Bug report #852452, regarding obmenu: Uninstallable due to dependency on "2.7" (should be "python2.7") to be marked as

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

Hi Felipe, On Wed, Jan 25, 2017 at 11:50:33AM -0300, Felipe Sateler wrote: > Apparently, fcow-utils as currently packaged is not usable in > debian. It is plenty usable, just not if you are using systemd. Yes, I am aware policy at this point requires systemd support. > Jacob Luna Lundberg,

Bug#852597: marked as done (iio-sensor-proxy: process keeps running after package purge)

Your message dated Wed, 25 Jan 2017 17:04:41 + with message-id and subject line Bug#852597: fixed in iio-sensor-proxy 2.0-3 has caused the Debian Bug report #852597, regarding iio-sensor-proxy: process keeps running after package purge to be marked as

Bug#852597: iio-sensor-proxy: process keeps running after package purge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2017-01-25 at 16:41 +0100, Michael Biebl wrote: > > Dear Debian Systemd Team, > >  > > For a static service, upon package de-install, how do we ensure the service > is > > killed. Should this be done manually and individually in a package's

Bug#852597: iio-sensor-proxy: process keeps running after package purge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Laurent, On Wed, 2017-01-25 at 17:00 +0100, Laurent Bigonville wrote: > Package: iio-sensor-proxy > Followup-For: Bug #852597 > > Hi, > > The patch attached here seems to do the job. Thank you for the quick patch you provided. Appreciate

Bug#852516: marked as done (request-tracker4: prompting due to modified conffiles which were not modified by the user: /etc/request-tracker4/RT_SiteConfig.pm)

Your message dated Wed, 25 Jan 2017 16:09:27 + with message-id and subject line Bug#852516: fixed in request-tracker4 4.4.1-3 has caused the Debian Bug report #852516, regarding request-tracker4: prompting due to modified conffiles which were not modified

Bug#852546: marked as done (bowtie2 build-depends on non-free libmath-random-perl)

Your message dated Wed, 25 Jan 2017 16:03:51 + with message-id and subject line Bug#852546: fixed in bowtie2 2.3.0-2 has caused the Debian Bug report #852546, regarding bowtie2 build-depends on non-free libmath-random-perl to be marked as done. This means

Processed: tagging 852597

Processing commands for cont...@bugs.debian.org: > tags 852597 + patch Bug #852597 [iio-sensor-proxy] iio-sensor-proxy: process keeps running after package purge Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 852597:

Bug#852597: iio-sensor-proxy: process keeps running after package purge

Package: iio-sensor-proxy Followup-For: Bug #852597 The patch... -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures:

Bug#852597: iio-sensor-proxy: process keeps running after package purge

Package: iio-sensor-proxy Followup-For: Bug #852597 Hi, The patch attached here seems to do the job. Cheers, Laurent Bigonville -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,

Processed: limit source to request-tracker4, tagging 852522, tagging 852516

Processing commands for cont...@bugs.debian.org: > limit source request-tracker4 Limiting to bugs with field 'source' containing at least one of 'request-tracker4' Limit currently set to 'source':'request-tracker4' > tags 852522 + pending Bug #852522 [request-tracker4] request-tracker4:

Bug#852597: iio-sensor-proxy: process keeps running after package purge

Am 25.01.2017 um 16:27 schrieb Ritesh Raj Sarraf: > So a "static" service is: > > The state will usually be "enabled", "disabled", "static", or "masked". In > this > context, static means that the unit file does not contain an "install" > section, > which is used to enable a unit. As such,

Bug#852374: marked as done (sagemath FTBFS on i386: recipe for target 'had-few-failures' failed)

Your message dated Wed, 25 Jan 2017 15:37:44 + with message-id and subject line Bug#852374: fixed in sagemath 7.4-8 has caused the Debian Bug report #852374, regarding sagemath FTBFS on i386: recipe for target 'had-few-failures' failed to be marked as

Bug#734385: marked as done (cardstories: Package installation fails if /etc/apache2/conf.d does not exist)

Your message dated Wed, 25 Jan 2017 15:29:41 + with message-id and subject line Bug#852541: Removed package(s) from unstable has caused the Debian Bug report #734385, regarding cardstories: Package installation fails if /etc/apache2/conf.d does not exist

Bug#753195: marked as done (cardstories: FTBFS: make[3]: virtualenv: Command not found)

Your message dated Wed, 25 Jan 2017 15:29:41 + with message-id and subject line Bug#852541: Removed package(s) from unstable has caused the Debian Bug report #753195, regarding cardstories: FTBFS: make[3]: virtualenv: Command not found to be marked as

Bug#735761: marked as done (cardstories: FTBFS: Tries to write outside build dir)

Your message dated Wed, 25 Jan 2017 15:29:41 + with message-id and subject line Bug#852541: Removed package(s) from unstable has caused the Debian Bug report #735761, regarding cardstories: FTBFS: Tries to write outside build dir to be marked as done.

Bug#852597: iio-sensor-proxy: process keeps running after package purge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2017-01-25 at 20:05 +0530, Ritesh Raj Sarraf wrote: > > I just purged iio-sensor-proxy, but: > > > > $ ps 574 > >   PID TTY  STAT   TIME COMMAND > >   574 ?    Ssl    4:10 /usr/sbin/iio-sensor-proxy > > > > The process should stop

Processed: Set astroplan bug forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 851437 https://github.com/astropy/astroplan/issues/282 Bug #851437 [src:astroplan] astroplan: FTBFS (requires Internet to build) Set Bug forwarded-to-address to 'https://github.com/astropy/astroplan/issues/282'. > End of message,

Bug#794316: several bug reports involving inability to unlock desktop

This bug report seems to be mixing up several distinct situations that all have the common symptom "I can't unlock the screen shield". That makes it much less likely that any of them will get solved, so I'm trying to disentangle them. When reporting bugs against a commonly-used component, please

Processed: severity of 852603 is grave, severity of 852604 is grave

Processing commands for cont...@bugs.debian.org: > severity 852603 grave Bug #852603 [src:virglrenderer] virglrenderer: CVE-2016-10163 Severity set to 'grave' from 'important' > severity 852604 grave Bug #852604 [src:virglrenderer] virglrenderer: CVE-2017-5580 Severity set to 'grave' from

Processed: cloning 794316 ..., severity of -2 is normal, retitle -3 to lock screen becomes unresponsive ...

Processing commands for cont...@bugs.debian.org: > clone 794316 -2 -3 Bug #794316 [gdm3] can't unlock desktop Bug 794316 cloned as bugs 852606-852607 > retitle 794316 can't unlock desktop: Too many open files (inotify fds leaked > on unsuccessful login) Bug #794316 [gdm3] can't unlock desktop

Processed: gnupg-agent: double-free in gpg-agent during heavily concurrent use

Processing control commands: > fixed -1 2.1.18-2 Bug #852608 [gnupg-agent] gnupg-agent: double-free in gpg-agent during heavily concurrent use There is no source info for the package 'gnupg-agent' at version '2.1.18-2' with architecture '' Unable to make a source version for version '2.1.18-2'

Bug#852608: gnupg-agent: double-free in gpg-agent during heavily concurrent use

Package: gnupg-agent Version: 2.1.17-2 Severity: grave Justification: renders package unusable Control: fixed -1 2.1.18-2 There is a crash in gpg-agent under heavily concurrent use. See: https://lists.gnupg.org/pipermail/gnupg-devel/2017-January/032499.html This is reproducible on debian with:

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

Hello Sylvain Costard, On 20 January 2017 at 09:10, Sylvain Costard wrote: > > Hello, > > Here is in attachment the latest patch we made for > fcoe-utils-1.0.29+git20140505 version for Debian. > > All is working and ifdown/ifup is no longer necessary to see

Processed: Re: Bug#852557: Acknowledgement (bucklespring: FTBFS on non-linux architectures)

Processing control commands: > severity -1 normal Bug #852557 [src:bucklespring] bucklespring: FTBFS on non-linux architectures Severity set to 'normal' from 'serious' -- 852557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852557 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#852557: Acknowledgement (bucklespring: FTBFS on non-linux architectures)

Control: severity -1 normal Not RC because no supported architectures. -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of

Processed: Re: Bug#852597: iio-sensor-proxy: process keeps running after package purge

Processing control commands: > tag -1 help Bug #852597 [iio-sensor-proxy] iio-sensor-proxy: process keeps running after package purge Added tag(s) help. -- 852597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#852597: iio-sensor-proxy: process keeps running after package purge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: tag -1 help Hello On Wed, 2017-01-25 at 14:59 +0100, Julien Cristau wrote: > Package: iio-sensor-proxy > Severity: serious > Version: 2.0-1 > Is this severity justified ? > I just purged iio-sensor-proxy, but: > > $ ps 574 >   PID

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

On Wed, 25 Jan 2017 at 12:52:13 +, Simon McVittie wrote: > With that incompatibility out of the way, there's another one: > > Jan 25 12:28:31 host gdm-session-worker.really[11355]: > pam_unix(gdm-password:auth): conversation failed > Jan 25 12:28:31 host

Bug#852597: iio-sensor-proxy: process keeps running after package purge

Package: iio-sensor-proxy Severity: serious Version: 2.0-1 I just purged iio-sensor-proxy, but: $ ps 574 PID TTY STAT TIME COMMAND 574 ?Ssl4:10 /usr/sbin/iio-sensor-proxy The process should stop running on removing the package. Cheers, Julien

Bug#848287: marked as done (python-testing.mysqld: (build-)depends on mysql-{client,server})

Your message dated Wed, 25 Jan 2017 13:51:18 + with message-id and subject line Bug#848287: fixed in python-testing.mysqld 1.4.0-2 has caused the Debian Bug report #848287, regarding python-testing.mysqld: (build-)depends on mysql-{client,server} to be

Bug#852557: bucklespring: FTBFS on non-linux architectures

Source: bucklespring Version: 1.4.0-1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) Control: forwarded -1 https://github.com/zevv/bucklespring/issues/44 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 bucklespring only implements

Processed: bucklespring: FTBFS on non-linux architectures

Processing control commands: > forwarded -1 https://github.com/zevv/bucklespring/issues/44 Bug #852557 [src:bucklespring] bucklespring: FTBFS on non-linux architectures Set Bug forwarded-to-address to 'https://github.com/zevv/bucklespring/issues/44'. -- 852557:

Processed: Bug#848287 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 848287 pending Bug #848287 [src:python-testing.mysqld] python-testing.mysqld: (build-)depends on mysql-{client,server} Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 848287:

Bug#848287: marked as pending

tag 848287 pending thanks Hello, Bug #848287 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-testing.mysqld.git;a=commitdiff;h=027f21f --- commit

Bug#851437: astroplan: FTBFS (requires Internet to build)

There are quite a couple of problems, some of which are due to bugs in astropy (namely #852550), and others already solved upstream: https://github.com/astropy/astroplan/pull/273 https://github.com/astropy/astroplan/pull/274 https://github.com/astropy/astroplan/pull/281

Processed: Fixed in openmpi, so close the bug properly

Processing commands for cont...@bugs.debian.org: > notfound 842881 mpich/3.2-7 Bug #842881 {Done: Alastair McKinstry } [src:mpich] libmpich12: extraneous - and possibly wrong - symbolic link: /usr/lib/libmpich.so.12 -> libmpi.so No longer marked as found in versions

Bug#852356: marked as done (ck builds with -sse2 on i386)

Your message dated Wed, 25 Jan 2017 13:18:52 + with message-id and subject line Bug#852356: fixed in ck 0.5.2-2.1 has caused the Debian Bug report #852356, regarding ck builds with -sse2 on i386 to be marked as done. This means that you claim that the

Bug#852344: marked as done (ck: FTBFS on i386 (fatal error: sys/cdefs.h: No such file or directory))

Your message dated Wed, 25 Jan 2017 13:18:52 + with message-id and subject line Bug#852344: fixed in ck 0.5.2-2.1 has caused the Debian Bug report #852344, regarding ck: FTBFS on i386 (fatal error: sys/cdefs.h: No such file or directory) to be marked as

Bug#840789: #840789: ruby-gettext: FTBFS: Error: test_relative ... undefined method `stub

reopen 840789 thanks On Mon, 23 Jan 2017, Christian Hofstaedtler wrote: > Hi Chris, > > I've just tried to repro this in unstable today, but haven't been > successful. I imagine a dependency change has fixed this. If you're > still seeing this FTBFS, please reopen. This is still happening,

Processed: Re: #840789: ruby-gettext: FTBFS: Error: test_relative ... undefined method `stub

Processing commands for cont...@bugs.debian.org: > reopen 840789 Bug #840789 {Done: Christian Hofstaedtler } [src:ruby-gettext] ruby-gettext: FTBFS: Error: test_relative(TestToolsXGetText::TestReference): NoMethodError: undefined method `stub' for # Bug reopened Ignoring

Bug#852552: ocserv: Build fail on arm patch inc

Package: ocserv Version: 0.11.6-1~bpo8+1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, build is failing for arm have tested this patch on armhf, on backported package results in installable package, fails on other

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

On Sun, 11 Oct 2015 at 15:48:10 -0700, Josh Triplett wrote: > I just encountered this problem again, and in addition to the repeated > authentication failure messages, I also saw a message on the lock screen > matching this one I later found in logs: > > gnome-session[551]: (gnome-shell:956):

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote: > > Hopefully somebody is prepared to fix all rdepends. > > Or better reverts the API change. I gave a quick look at the problem. I don't know why Mathieu packaged a new upstream snapshot exactly, I hope it is not for the new

  1   2   >