Bug#851828: oclgrind FTBFS on armhf: test failures

Source: oclgrind Version: 16.10-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=oclgrind=armhf=16.10-1=1484675768=0 ... Start 75: uninitialized/uninitialized_local_array Start 76: uninitialized/uninitialized_local_ptr 73/86 Test #76:

Bug#849836: zekr: Missing dependency on libwebkitgtk-1.0-0

Christoph Biedl wrote... > That's indeed a no-brainer. I've prepared an NMU as below and will > upload it to DELAYED/2 tomorrow. Now uploaded, with a small fix: > + * Add install dependency on xserver-xorg-input-all. Closes: #849836 s/xserver-xorg-input-all/libwebkitgtk-1.0-0/ Christoph

Processed: And re-add the fixed (sorry for the noise...)

Processing commands for cont...@bugs.debian.org: > fixed 806917 16.04.0-1 Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package Bug #810050 [src:ktp-call-ui] kde-telepathy-call-ui: can't install kde-telepathy-call-ui in sid (dependency conflicts) Marked as fixed in versions

Processed: And do the merge properly...

Processing commands for cont...@bugs.debian.org: > reassign 810050 src:ktp-call-ui Bug #810050 [kde-telepathy-call-ui] kde-telepathy-call-ui: can't install kde-telepathy-call-ui in sid (dependency conflicts) Bug reassigned from package 'kde-telepathy-call-ui' to 'src:ktp-call-ui'. No longer

Processed: I forgot to re-add the version

Processing commands for cont...@bugs.debian.org: > found 806917 0.9.0-2 Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package Marked as found in versions ktp-call-ui/0.9.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 806917:

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

On Wed, Jan 18, 2017 at 02:21:04PM -0500, Lincoln Stein wrote: > Yes, I'll remove it immediately and apply the patches to bio::graphics as > well. Fine. Do you intend to do a micro release (say 2.56.1) after this change or should I remove the file here locally for the time beeing? Both would be

Processed (with 2 errors): Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 806917 src:ktp-call-ui Bug #806917 [ktp-call-ui] ktp-call-ui: build-depends on cruft package Bug reassigned from package 'ktp-call-ui' to 'src:ktp-call-ui'. No longer marked as found in versions 0.9.0-2. No longer marked as fixed in

Bug#851726: liggghts: FTBFS on single-CPU machines (not enough slots available)

See #850229.

Processed: bug 851016 is forwarded to https://github.com/beetbox/beets/issues/2153

Processing commands for cont...@bugs.debian.org: > forwarded 851016 https://github.com/beetbox/beets/issues/2153 Bug #851016 [src:beets] beets: FTBFS: Test failures Set Bug forwarded-to-address to 'https://github.com/beetbox/beets/issues/2153'. > thanks Stopping processing here. Please contact

Bug#851016: beets: FTBFS: Test failures

This looks like https://github.com/beetbox/beets/issues/2153 i.e. that the current version of mutagen that we have in Debian (1.36) is incompatible with the version of beets (1.3.19). Quoting from that issue: > when beets 1.3.19 was released, Mutagen 1.33 didn't exist yet. > When that was

Bug#850230: marked as done (fabric: FTBFS (sbuild hangs))

Your message dated Thu, 19 Jan 2017 03:48:52 + with message-id and subject line Bug#850230: fixed in fabric 1.13.1-2 has caused the Debian Bug report #850230, regarding fabric: FTBFS (sbuild hangs) to be marked as done. This means that you claim that the

Bug#850230: fabric: FTBFS (sbuild hangs)

On Thu, Jan 5, 2017 at 5:05 AM, Santiago Vila wrote: > The bug should be reproducible with sbuild on a single CPU virtual machine. > It always fail for me (I tried 10 times in different autobuilders), and > it also fails here: > >

Bug#851634: marked as done (chromium: Chromium does not start after update)

Your message dated Thu, 19 Jan 2017 03:06:47 + with message-id and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5 has caused the Debian Bug report #851634, regarding chromium: Chromium does not start after update to be marked as done.

Bug#851652: marked as done (chromium: syntax error reported in /usr/bin/chromium shell)

Your message dated Thu, 19 Jan 2017 03:06:47 + with message-id and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5 has caused the Debian Bug report #851634, regarding chromium: syntax error reported in /usr/bin/chromium shell to be marked

Bug#851767: marked as done (chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.)

Your message dated Thu, 19 Jan 2017 03:06:47 + with message-id and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5 has caused the Debian Bug report #851634, regarding chromium: Line 21 in the startup script /usr/bin/chromium is missing a

Bug#851779: marked as done (chromium: crashes at startup)

Your message dated Thu, 19 Jan 2017 03:06:47 + with message-id and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5 has caused the Debian Bug report #851634, regarding chromium: crashes at startup to be marked as done. This means that you

Bug#851820: libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36 test programs. 20/242 subtests failed.

Source: libmojolicious-plugin-assetpack-perl Version: 1.30-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, libmojolicious-plugin-assetpack-perl

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 851634 851767 851779 851652 Bug #851634 [chromium] chromium: Chromium does not start after update Bug #851767 [chromium] chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote. Added tag(s) patch. Bug

Bug#851817: Vendoring libraries

Package: prometheus Version: 1.2.3+ds2-5 Severity: serious X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org Dear maintainers, Prometheus depends on many libraries, including source codes located into vendor directory. Is this a violation for Debian Policy 4.13 ? "4.13 Convenience copies

Processed: severity of 810050 is serious, severity of 851513 is serious

Processing commands for cont...@bugs.debian.org: > severity 810050 serious Bug #810050 [kde-telepathy-call-ui] kde-telepathy-call-ui: can't install kde-telepathy-call-ui in sid (dependency conflicts) Severity set to 'serious' from 'important' > severity 851513 serious Bug #851513 [zfs-dkms]

Bug#851790: installation-reports: DNS not working

Cyril Brulebois (2017-01-19): > Summing up things from IRC: > - in an uptodate sid chroot (both development version and minimal one >with daily-build script): no DNS issues with the generated mini.iso >(amd64, tested within stable's kvm on amd64). My image was also >

Bug#851814: apt-build: Broken postinst by less permissive sed

Package: apt-build Version: 0.12.45 Severity: serious Tags: patch Dear QA Group: Installing apt-build results in this error: Setting up apt-build (0.12.45) ... sed: character class syntax is [[:space:]], not [:space:] dpkg: error processing package apt-build (--configure): subprocess installed

Bug#851790: installation-reports: DNS not working

Cyril Brulebois (2017-01-19): > You can try downgrading the kernel, but I'd usually look at glibc first > for DNS related issues. Summing up things from IRC: - in an uptodate sid chroot (both development version and minimal one with daily-build script): no DNS issues with

Bug#850970: marked as done (pvpgn: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Thu, 19 Jan 2017 00:19:30 + with message-id and subject line Bug#850970: fixed in pvpgn 1.8.5-2.1 has caused the Debian Bug report #850970, regarding pvpgn: switch to build depend on the metapackage default-libmysqlclient-dev to be

Bug#845830: marked as done (cl-sql: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Thu, 19 Jan 2017 00:03:51 + with message-id and subject line Bug#845830: fixed in cl-sql 6.7.0-1.1 has caused the Debian Bug report #845830, regarding cl-sql: switch to build depend on the metapackage default-libmysqlclient-dev to be

Bug#851812: seed-webkit2 autoreconf FTBFS

Source: seed-webkit2 Version: 4.0.0+20161014+6c77960+dfsg1-3 Severity: serious https://buildd.debian.org/status/package.php?p=seed-webkit2=sid ... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore

Processed: tag 783615 pending

Processing commands for cont...@bugs.debian.org: > tag 783615 pending Bug #783615 {Done: Michael Shuler } [ca-certificates] "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates Added tag(s) pending. > thanks Stopping

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

Hi, 2017-01-14 23:54 GMT+01:00 Adrian Bunk : > Control: retitle -1 ffmpeg: ChromaprintContext FTBFS > Control: forwarded -1 https://trac.ffmpeg.org/ticket/5997 > Control: tags -1 fixed-upstream > > On Sat, Jan 14, 2017 at 06:47:02AM +0100, Carl Eugen Hoyos wrote: >> The relevant

Bug#851790: installation-reports: DNS not working

Steve McIntyre (2017-01-18): > For the sake of completeness, I can confirm that the same problem > shows up when running on a different network too. I also see this > using the oldest amd64 daily I can grab (from 2017-01-17) which has > the 4.9 kernel too. > > I'll see if I can

Bug#850998: marked as done (erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl)

Your message dated Wed, 18 Jan 2017 23:03:47 + with message-id and subject line Bug#850998: fixed in erlang-ranch 1.2.1-3 has caused the Debian Bug report #850998, regarding erlang-ranch: FTBFS: a2x: ERROR: missing configuration file:

Bug#850998: [Pkg-leofs-devel] Bug#850998: erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

Hi Nobuhiro, I have uploaded the fix but the packaging repo does not contain your latest upload. In case you have it offline please upload it or we can import the history from the .dsc Cheers, Balint 2017-01-11 20:07 GMT+01:00 Lucas Nussbaum : > Source: erlang-ranch > Version:

Processed: Re: zekr: Missing dependency on libwebkitgtk-1.0-0

Processing control commands: > tags 849836 confirmed patch pending Bug #849836 [zekr] zekr: Missing dependency on libwebkitgtk-1.0-0 Added tag(s) confirmed, patch, and pending. -- 849836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849836 Debian Bug Tracking System Contact

Bug#849836: zekr: Missing dependency on libwebkitgtk-1.0-0

Control: tags 849836 confirmed patch pending Awtul wrote... > Installing "libwebkitgtk-1.0-0" solves the problem. I thought it may > be a dependency missing issue. That's indeed a no-brainer. I've prepared an NMU as below and will upload it to DELAYED/2 tomorrow. Regards, Christoph diff

Bug#851803: ntp: FTBFS (mv: cannot stat 'debian/tmp/usr/bin/ntpdate': No such file or directory)

Package: src:ntp Version: 1:4.2.8p9+dfsg-2 Severity: serious Tags: patch Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] Installing stand-alone HTML

Bug#850026: marked as done (vmtk: transitive B-D on both libssl-dev and libssl1.0-dev)

Your message dated Wed, 18 Jan 2017 22:06:10 + with message-id and subject line Bug#850026: fixed in vmtk 1.3+dfsg-2.1 has caused the Debian Bug report #850026, regarding vmtk: transitive B-D on both libssl-dev and libssl1.0-dev to be marked as done. This

Bug#851726: marked as done (liggghts: FTBFS on single-CPU machines (not enough slots available))

Your message dated Wed, 18 Jan 2017 22:04:34 + with message-id and subject line Bug#851726: fixed in liggghts 3.5.0+repack1-9 has caused the Debian Bug report #851726, regarding liggghts: FTBFS on single-CPU machines (not enough slots available) to be

Bug#783615: "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates

On 01/18/2017 03:25 PM, Adrian Bunk wrote: > after a discussion with someone who ran into this bug in stable I have > set the severity to serious, since this should IMHO also be fixed in > stable. This does look like a good patch to backport to stable. I'll get this commited to git and work on

Processed: severity of 851795 is serious

Processing commands for cont...@bugs.debian.org: > severity 851795 serious Bug #851795 [src:systemd] [MIPS] Forced local symbol rearranging messes up GOT Ignoring request to change severity of Bug 851795 to the same value. > thanks Stopping processing here. Please contact me if you need

Bug#783615: "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates

Hi, after a discussion with someone who ran into this bug in stable I have set the severity to serious, since this should IMHO also be fixed in stable. It is a very nasty bug when something works on the first execution of a command but not on subsequent executions, and the fix looks really

Bug#850885: marked as done (apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc)

Your message dated Wed, 18 Jan 2017 21:19:01 + with message-id and subject line Bug#850885: fixed in dwww 1.13.3 has caused the Debian Bug report #850885, regarding apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc

Processed: tor: IPv6 connections through tor do not appear to work

Processing control commands: > block 849845 with -1 Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore Bug #850606 [dirmngr] dirmngr: can't resolve ipv6 addresses when use-tor is enabled 849845 was not blocked by any bugs. 849845 was not blocking any bugs. Added blocking

Processed: Unarchive and mark RC

Processing commands for cont...@bugs.debian.org: > unarchive 783615 Bug #783615 {Done: Michael Shuler } [ca-certificates] "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates Unarchived Bug 783615 > severity 783615

Bug#839443: bcron: some failing test disabled for now

control: severity -1 important Hi, I'm downgrading this one, to make the current bcron have chances to migrated. I think tests should be fixed, but disabling a couple of them "fixed" the build, and will probably make it go in Stretch G. signature.asc Description: OpenPGP digital signature

Processed: bcron: some failing test disabled for now

Processing control commands: > severity -1 important Bug #839443 [src:bcron] bcron: FTBFS: tests failures Severity set to 'important' from 'serious' -- 839443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Tag

Processing commands for cont...@bugs.debian.org: > tags 762400 stretch sid Bug #762400 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0 has a direct Build-Depends on itself Bug #824982 {Done: Michael Biebl } [src:gtk+3.0] src:gtk+3.0: unsatisfiable dependency on

Bug#828468: marked as done (openhpi: FTBFS with openssl 1.1.0)

Your message dated Wed, 18 Jan 2017 20:53:05 + with message-id and subject line Bug#828468: fixed in openhpi 3.6.1-2.1 has caused the Debian Bug report #828468, regarding openhpi: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Bug#851792: palo ships binary in the sources

Package: palo Version: 1.95 Severity: serious >From debian/rules: @if [ `dpkg --print-architecture` = hppa ]; \ then \ echo "Regenerating iplboot."; \ $(MAKE) realclean; \ $(MAKE) iplboot; \ else \ echo

Bug#805988: aboot : include the binaries in source to build on amd64

On Wed, Jan 18, 2017 at 06:54:10PM +0100, Santiago Vila wrote: > On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote: > > > I wonder if the following solution would be accepted (see the two patches > > attached) : let the source package ship the two binaries (bootlx and > >

Bug#851790: installation-reports: DNS not working

On Wed, Jan 18, 2017 at 06:43:33PM +, Wookey wrote: >Package: installation-reports >Severity: grave >Tags: d-i >Justification: renders package unusable > >Dear Maintainer, > >The current installer, with the new 4.9 kernel, is unable to resolve >domains, so is quite seriously broken. hosts,

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

Yes, I'll remove it immediately and apply the patches to bio::graphics as well. Lincoln On Wed, Jan 18, 2017 at 11:58 AM, Andreas Tille wrote: > On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote: > > > > > >

Processed: tagging 851039

Processing commands for cont...@bugs.debian.org: > tags 851039 + help Bug #851039 [src:python-apt] python-apt: FTBFS: Test failures Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 851039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851039

Bug#851579: marked as done (lcdproc: fails to install: post-installation script returned error exit status 10)

Your message dated Wed, 18 Jan 2017 19:03:59 + with message-id and subject line Bug#851579: fixed in lcdproc 0.5.8~rc2-1 has caused the Debian Bug report #851579, regarding lcdproc: fails to install: post-installation script returned error exit status 10

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

On martes, 17 de enero de 2017 22:21:51 ART Rebecca N. Palmer wrote: [snip] > This suggests the fix (warning: untested and not my area of expertise - > and if it is using that line, why is there no -Wl,--no-whole-archive in > the build log?): This part I don't know. > ---

Bug#851790: installation-reports: DNS not working

Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, The current installer, with the new 4.9 kernel, is unable to resolve domains, so is quite seriously broken. This was noted during install on an arm64 gigabyte MP30-AR1

Bug#838665: /usr/lib/python3/dist-packages/speechd_config/config.py: runs argparse on Python module import

On Mon, Sep 26, 2016 at 02:16:45PM +0200, Sebastian Humenda wrote: > Hi Hi Sebastian, > I'll provide a patch to upstream shortly and attach it here as well, so that > it > is fixed both upstream and downstream. any news regarding that? > Sebastian Thanks Adrian -- "Is there not

Bug#811945: marked as done (ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal operator)

Your message dated Wed, 18 Jan 2017 20:14:12 +0200 with message-id <20170118181412.xh64oottft7jewcr@localhost> and subject line Fixed in 2.10.11-3 has caused the Debian Bug report #811945, regarding ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal operator to be marked as done.

Bug#749661: marked as done (ifuse: Segfault)

Your message dated Wed, 18 Jan 2017 19:57:32 +0200 with message-id <20170118175732.nwmnfecckaxvyibo@localhost> and subject line Re: Bug#749661: ifuse: Segfault has caused the Debian Bug report #749661, regarding ifuse: Segfault to be marked as done. This means that you claim that the problem has

Bug#805988: aboot : include the binaries in source to build on amd64

On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote: > I wonder if the following solution would be accepted (see the two patches > attached) : let the source package ship the two binaries (bootlx and > net_aboot.nh). [...] Hmm, but this is like removing a hack and creating another one

Processed: Re: Bug#789407: unable to send openpgp messages

Processing control commands: > tags 789407 unreproducible Bug #789407 [pidgin-openpgp] unable to send openpgp messages Added tag(s) unreproducible. > severity 789407 normal Bug #789407 [pidgin-openpgp] unable to send openpgp messages Severity set to 'normal' from 'grave' -- 789407:

Bug#789407: unable to send openpgp messages

Control: tags 789407 unreproducible Control: severity 789407 normal Lowering severity as this problem was not reproducible, and the original submitter did not provide additional information upon request. Christoph signature.asc Description: Digital signature

Bug#832656: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)

Your message dated Wed, 18 Jan 2017 17:33:27 + with message-id and subject line Bug#832656: fixed in bcron 0.10-4 has caused the Debian Bug report #832656, regarding runit: breaks users of runit: ln: failed to create symbolic link

Bug#805988: aboot : include the binaries in source to build on amd64

Hi, I wonder if the following solution would be accepted (see the two patches attached) : let the source package ship the two binaries (bootlx and net_aboot.nh). One can build aboot-base on amd64 then. The two binaries are generated from source if the source package is built on alpha. (The

Bug#733433: marked as done (tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision)

Your message dated Wed, 18 Jan 2017 17:20:28 + with message-id and subject line Bug#223915: fixed in tk-brief 5.10-0.1 has caused the Debian Bug report #223915, regarding tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)':

Bug#223915: marked as done (tk-brief: Please don't package it as a native package)

Your message dated Wed, 18 Jan 2017 17:20:28 + with message-id and subject line Bug#223915: fixed in tk-brief 5.10-0.1 has caused the Debian Bug report #223915, regarding tk-brief: Please don't package it as a native package to be marked as done. This

Bug#851779: chromium: crashes at startup

Package: chromium Version: 55.0.2883.75-4 Severity: grave Justification: renders package unusable Dear Maintainer, Since last recent release, chromium does not start anymore. Wen typing the command in a shell, I get the following message: --- chromium /usr/bin/chromium: 122:

Bug#851741: python-jinja2: New major version breaks ansible templates

On 18 January 2017 at 06:29, Piotr Ożarowski wrote: > could you check if this commit fixes it for you? > https://github.com/pallets/jinja/commit/c6ddeb7d5f64789ed0bbc1ffef8596a79bc06fd9 Thanks for the quick response. I'm still getting the KeyError: undefined variable after I

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote: > > > > > > https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches > > Oh, cool, adding the (build)-dep is really enough, no patching > required. Nice. Yes, we needed this for another package ... > For

Processed: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

Processing control commands: > affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj Bug #851775 [libgcj-bc] libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable Added indication that 851775 affects libecj-java-gcj, ecj1, ecj-gcj, ant-gcj, and ant-optional-gcj --

Bug#851775: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

Package: libgcj-bc Version: 6.2.1-1 Severity: grave Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj $ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs libgcj_bc 1 libgcj-bc (>= 6.2.1-3~) $ That seems to be the reason why several packages can currently not be installed

Bug#847577: marked as done (Embeds dietlibc (GPL) but does not have a Built-Using field)

Your message dated Wed, 18 Jan 2017 16:48:31 + with message-id and subject line Bug#847577: fixed in integrit 4.1-1.1 has caused the Debian Bug report #847577, regarding Embeds dietlibc (GPL) but does not have a Built-Using field to be marked as done.

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

On Wed, 18 Jan 2017 17:27:21 +0100, Andreas Tille wrote: > > Cool. In Debian terminology this means a new "Build-Depends" and after > > adding > > libbio-coordinate-perl package to this the tests succeeded. Thanks a lot > > for > > your help and patience! > > > > I now need to sort out some

Bug#848236: marked as done (src:gbrowse: Fails to build from source since bioperl upgrade has broken libbio-graphics-perl)

Your message dated Wed, 18 Jan 2017 16:34:04 + with message-id and subject line Bug#848236: fixed in gbrowse 2.56+dfsg-1 has caused the Debian Bug report #848236, regarding src:gbrowse: Fails to build from source since bioperl upgrade has broken

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[droping debian-perl list from CC] On Wed, Jan 18, 2017 at 02:30:32PM +0100, Andreas Tille wrote: > Hi Lincoln, > > On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote: > > > > There appears to be a new dependency on libbio-coordinate. Probably best to > > add a "use Bio::Coordinate"

Bug#851771: php-gettext: CVE-2016-6175

Source: php-gettext Version: 1.0.11-1 Severity: grave Tags: security upstream Forwarded: https://bugs.launchpad.net/php-gettext/+bug/1606184 Hi, the following vulnerability was published for php-gettext. CVE-2016-6175[0]: Use of eval too unrestrictive If you fix the vulnerability please also

Bug#851770: php-gettext: CVE-2015-8980

Source: php-gettext Version: 1.0.11-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for php-gettext. CVE-2015-8980[0]: |Arbitrary code execution in select_string, ngettext and npgettext |count parameter If you fix the vulnerability please also make sure

Processed: forcibly merging 648208 794849

Processing commands for cont...@bugs.debian.org: > forcemerge 648208 794849 Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm instances Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted inside a VM Bug #806273 [os-prober] os-prober: remove or

Bug#851769: 389-ds-base: CVE-2017-2591

Source: 389-ds-base Version: 1.3.5.15-1 Severity: grave Tags: security upstream patch Justification: user security hole Hi, the following vulnerability was published for 389-ds-base. Choosed severity > important, since possibly as well triggerable by unauthenticated attackers, but I'm not too

Bug#835189: python-pyrax: FTBFS (failing tests)

thx for the update. I try to handle it asap. I'm only short of time at the moment. Regards Sascha Am 17.01.2017 um 01:50 schrieb Santiago Vila: > retitle 835189 python-pyrax: FTBFS (failing tests) > thanks > > Hi. > > After building this package many times today, it always fail > and not just

Bug#737167: marked as done (xfonts-wqy: prompting due to modified conffiles which were not modified by the user)

Your message dated Wed, 18 Jan 2017 16:06:02 + with message-id and subject line Bug#737167: fixed in xfonts-wqy 1.0.0~rc1-3 has caused the Debian Bug report #737167, regarding xfonts-wqy: prompting due to modified conffiles which were not modified by the

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

- car...@debian.org wrote: > Hi Lars, > > On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote: > > > > - car...@debian.org wrote: > > > > > > > > >With that fixed, and build with -sa (to include the orig > tarball) > > > > >please do upload to security-master. > > > > Do we

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

Le 17/01/2017 à 14:01, Felipe Sateler a écrit : Hi Yann, On 17 January 2017 at 06:54, Yann Richard wrote: Hi, We have made a package from fcoe-utils source version 1.0.31 which fix init bug : https://github.com/DSI-Universite-Rennes2/fcoe-utils Tested on HP

Bug#851767: chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.

Package: chromium Version: 55.0.2883.75-4 Severity: grave Justification: renders package unusable Dear Maintainer, I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser would not run. I browsed the starting script /usr/bin/chromium and noticed that the string in line

Bug#851714: marked as done (gitlab: Cannot push to gitlab repositories with git >= 2.11.0)

Your message dated Wed, 18 Jan 2017 15:33:49 + with message-id and subject line Bug#851714: fixed in gitlab 8.13.11+dfsg-1 has caused the Debian Bug report #851714, regarding gitlab: Cannot push to gitlab repositories with git >= 2.11.0 to be marked as

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Hi Lars, On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote: > > - car...@debian.org wrote: > > > > > >With that fixed, and build with -sa (to include the orig tarball) > > > >please do upload to security-master. > > > Do we have access to upload here? I think the security team

Bug#845899: marked as done (python-mysqldb: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Wed, 18 Jan 2017 15:08:44 + with message-id and subject line Bug#845899: fixed in python-mysqldb 1.3.7-1.1 has caused the Debian Bug report #845899, regarding python-mysqldb: switch to build depend on the metapackage

Bug#851293: marked as done (CVE-2016-9590)

Your message dated Wed, 18 Jan 2017 15:08:39 + with message-id and subject line Bug#851293: fixed in puppet-module-swift 9.4.4-1 has caused the Debian Bug report #851293, regarding CVE-2016-9590 to be marked as done. This means that you claim that the

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

- car...@debian.org wrote: > > >With that fixed, and build with -sa (to include the orig tarball) > > >please do upload to security-master. > > Do we have access to upload here? I think the security team have > handled the > > upload in the past. > > yes it nees to be a key in the DD

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

On Wed, 18 Jan 2017 14:00:47 +, Lincoln Stein wrote: > Glad to be of help. No source changes to bio::graphics needed then? Probably that too :) I'll take a look later today. Thanks for your efforts and your enormous help! Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian

Bug#845829: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

Control: tag -1 pending On 2017-01-17 02:21, Andreas Beckmann wrote: > attached is a patch to fix this (and another) issue. > If you need help, I could also upload this as a NMU. I now uploaded this as a NMU to DELAYED/2 since cfengine3 is the last (fixable) package in stretch blocking the

Processed: Re: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

Processing control commands: > tag -1 pending Bug #845829 [cfengine3] cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev Added tag(s) pending. -- 845829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845829 Debian Bug Tracking System Contact

Processed: retitle 851755 to mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318 ...

Processing commands for cont...@bugs.debian.org: > # including CVE-2016-6664 as well in list > retitle 851755 mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 > CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 > CVE-2017-3312 CVE-2017-3317 CVE-2017-3318 Bug #851755

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

Glad to be of help. No source changes to bio::graphics needed then? At some point in near future I will be making changes to the exception reporting in bio::graphics so that the error messages are more informative. Lincoln On Wed, Jan 18, 2017 at 8:30 AM Andreas Tille wrote:

Processed: Re: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

Processing control commands: > block -1 with 851131 Bug #841583 [src:ruby-dataobjects-mysql] ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force' 841583 was not blocked by any bugs. 841583 was not blocking any bugs. Added blocking bug(s) of 841583: 851131 --

Bug#841583: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

Followup-For: Bug #841583 Control: block -1 with 851131 The --force problem is specific to mysql, it does not happen with mariadb. But it fails differently on mariadb: [...] 2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld 10.1.20-MariaDB-3) starting as process 3768 ...

Bug#851759: mariadb-10.1: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

Source: mariadb-10.1 Version: 10.1.20-3 Severity: grave Tags: upstream security fixed-upstream Justification: user security hole Hi The following CVEs were fixed with a new upstream version 10.1.21, whereas CVE-2016-6664 has already a separate bug in the BTS: CVE-2016-6664 CVE-2017-3238

Processed: tagging 851755

Processing commands for cont...@bugs.debian.org: > tags 851755 + fixed-upstream Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318 Added tag(s) fixed-upstream. >

Bug#851755: mariadb-10.0: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

Source: mariadb-10.0 Version: 10.0.16-1 Severity: grave Tags: security upstream Hi The following CVE's were addressed in 10.0.29 upstream, whereas CVE-2016-6664 has already a seprate bug in the BTS: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Hi Lars, On Wed, Jan 18, 2017 at 12:45:45PM +0100, Lars Tangvald wrote: > Hi, > > On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote: > >Hi Lars, > > > >On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote: > >>Hi, > >> > >>The update builds and passes testing. > >>I've attached debdiff

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

Hi Lincoln, On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote: > > There appears to be a new dependency on libbio-coordinate. Probably best to > add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the > problem will disappear. Cool. In Debian terminology this

Bug#851549: marked as done (dbus: Segmentation fault in dbus.postinst on mips64el)

Your message dated Wed, 18 Jan 2017 13:20:18 + with message-id and subject line Bug#851412: fixed in systemd 232-11 has caused the Debian Bug report #851412, regarding dbus: Segmentation fault in dbus.postinst on mips64el to be marked as done. This means

  1   2   >